From owner-freebsd-stable@FreeBSD.ORG Sat Apr 21 14:29:26 2007 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F2D2116A400; Sat, 21 Apr 2007 14:29:25 +0000 (UTC) (envelope-from beni@brinckman.info) Received: from lmailproxy02.edpnet.net (lmailproxy02.edpnet.net [212.71.1.195]) by mx1.freebsd.org (Postfix) with ESMTP id 8A88C13C468; Sat, 21 Apr 2007 14:29:25 +0000 (UTC) (envelope-from beni@brinckman.info) Received: from [192.168.1.100] (212.71.9.188.adsl.dyn.edpnet.net [212.71.9.188]) by lmailproxy02.edpnet.net (8.13.1/8.13.1) with ESMTP id l3LEXCZu031547; Sat, 21 Apr 2007 16:33:13 +0200 From: Beni To: Ganbold Date: Sat, 21 Apr 2007 16:29:19 +0200 User-Agent: KMail/1.9.6 References: <200704182205.52028.beni@brinckman.info> <200704200105.22646.michaelnottebrock@gmx.net> <46281DAC.7090508@micom.mng.net> In-Reply-To: <46281DAC.7090508@micom.mng.net> X-Face: %*c?V7%A[c.}s2rI*TaRWm-[I-, ZLpBKmmC-@)J}KGbr)=a, TsXSA=:ArC(<=?utf-8?q?v=5C/=5F=25BaB=24K=0A=09=24=60E=7D6=7EyjIqu/SN=3A=24Pb=7DGngR+8=3D?= =?utf-8?q?dE=60?=)V~48zl6) =?utf-8?q?BhEtfQ2=3D=7ChScx=3Frn30d!QMd=3F=2E=60/hR!l+=0A=09x?=(]+zXesMf?'W[>46aPKMAAwd7eT{X_O9besb[u]'Y(DAe MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200704211629.20998.beni@brinckman.info> X-Virus-Scanned: ClamAV version 0.90.1, clamav-milter version 0.90.1 on lmailproxy02.edpnet.net X-Virus-Status: Clean X-Spam-Status: No, score=-0.5 required=5.0 tests=ALL_TRUSTED, BAYES_50, INFO_TLD autolearn=disabled version=3.1.8 X-Spam-Checker-Version: SpamAssassin 3.1.8 (2007-02-13) on lmailproxy02.edpnet.net Cc: stable@freebsd.org, kde@freebsd.org, current@freebsd.org, Adriaan de Groot , Robert Marella Subject: Re: [kde-freebsd] problem hal - k3b ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Apr 2007 14:29:26 -0000 On Friday 20 April 2007 03:55:56 Ganbold wrote: > Michael Nottebrock wrote: > > I forwarded my mail to gnome@ (the HAL maintainers) after sending it and > > Joe Marcus Clarke from gnome@ had this to say on the issue: > > > > --- snip > > > > This should have been fixed a while ago by jylefort when he set the > > default device for ATAPI access to be the ATAPICAM device (as opposed to > > the ATA device). Assuming you have not undone that change, and are > > running the latest version of HAL, these panics should not be occurring. > > > > Even still, you're right that these are not HAL bugs, but rather an > > issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and > > I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, > > and dvd-utils under the covers to do the actual device work. Not sure > > what k3b is using, but maybe it diddles something it shouldn't. > > > > Joe > > > > --- snip > > > > Beni, Robert, Ganbold, are you all in fact running the latest version of > > the hal port and do you all have atapicam enabled in your kernel? If not, > > making sure of both might help avoiding the problem. > > I see. I know I have updated my system last Saturday (14th April 2007) and > I think I updated both hal and kdelibs ports. I have atapicam enabled in > kernel. > Let me double check it this weekend and I will let you know. > > thanks, > > Ganbold > > > ------------------------------------------------------------------------ > > > > Subject: > > Re: Fwd: Re: [kde-freebsd] problem hal - k3b ? > > From: > > Joe Marcus Clarke > > Date: > > Thu, 19 Apr 2007 12:49:26 -0400 > > To: > > Michael Nottebrock > > > > To: > > Michael Nottebrock > > CC: > > gnome@freebsd.org > > > > Michael Nottebrock wrote: > >> I forgot to cc gnome@ on my reply. I don't think this is a HAL bug, but > >> just FYI. > >> > >> > >> > >> ------------------------------------------------------------------------ > >> > >> Subject: > >> Re: [kde-freebsd] problem hal - k3b ? > >> From: > >> Michael Nottebrock > >> Date: > >> Thu, 19 Apr 2007 18:12:46 +0200 > >> To: > >> kde@freebsd.org > >> > >> To: > >> kde@freebsd.org > >> CC: > >> Beni , h.eichmann@gmx.de, current@freebsd.org, > >> stable@freebsd.org > >> > >> On Wednesday, 18. April 2007, Beni wrote: > >>> Hi List, > >>> > >>> I think I have a problem with hal(d) and k3b (version 1.0 from ports) : > >>> my whole system freezes when starting up k3b. I get the splash screen > >>> and then it all stops and a ctrl-alt-del is the only way out. > >> > >> Other people have reported kernel panics. It looks to me like k3b's > >> device probing and hald's device probing at the same time manages to > >> tickle a bug in ata(4). > >> > >> Ref: > >> http://lists.freebsd.org/pipermail/freebsd-current/2007-April/070753.htm > >>l > >> http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034486.html > >> > >> I'm afraid a true kernel hacker will have to inconvenince themselves > >> with running k3b and hal in order to have this one fixed. FWIW, I > >> haven't seen in happening on 5.5. > > > > This should have been fixed a while ago by jylefort when he set the > > default device for ATAPI access to be the ATAPICAM device (as opposed to > > the ATA device). Assuming you have not undone that change, and are > > running the latest version of HAL, these panics should not be occurring. > > > > Even still, you're right that these are not HAL bugs, but rather an > > issue in the kernel. I use nautilus-cd-burner to burn CDs in GNOME, and > > I have never had such a panic on 6-STABLE. n-c-b uses cdrecord, cdrao, > > and dvd-utils under the covers to do the actual device work. Not sure > > what k3b is using, but maybe it diddles something it shouldn't. > > > > Joe Could it all be related to this : http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034553.html and the "solution" from Shane Bell in http://lists.freebsd.org/pipermail/freebsd-stable/2007-April/034602.html : "I believe the culprit is somewhere in a recent MFC to atapi-cam.c (rev 1.42.2.3) reverting to rev 1.42.2.2 fixes both the k3b system hangs and "INQUIRY ILLEGAL REQUEST" errors here." Beni.