Date: Sat, 11 Apr 2009 19:20:29 -0400 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Ashish SHUKLA <wahjava.ml@gmail.com> Cc: freebsd-gnome@freebsd.org Subject: Re: PulseAudio causing kernel panic with GNOME 2.26 Message-ID: <1239492029.4933.997.camel@shumai.marcuscom.com> In-Reply-To: <1239487341.4933.994.camel@shumai.marcuscom.com> References: <20090411042335.GA2148@chateau.d.lf> <1239487177.4933.993.camel@shumai.marcuscom.com> <1239487341.4933.994.camel@shumai.marcuscom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-ZElZraHuUhYMbS/Q2JfW Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Sat, 2009-04-11 at 18:02 -0400, Joe Marcus Clarke wrote: > On Sat, 2009-04-11 at 17:59 -0400, Joe Marcus Clarke wrote: > > On Sat, 2009-04-11 at 09:53 +0530, Ashish SHUKLA wrote: > > > Hi everyone, > > >=20 > > > I'm running FreeBSD 8.0-CURRENT (amd64). After portupgrade-ing to GNO= ME 2.26=20 > > > today, I'm not able to boot into GNOME. As soon as gnome-settings-dae= mon gets=20 > > > started, I get a kernel panic. Being in X11, I'm not able to see any = messages=20 > > > printed on the screen. And also there is no dump getting saved on swa= p device. > > >=20 > > > I also have Xmonad installed, so after booting into Xmonad, I started= =20 > > > gnome-settings-daemon on terminal, and I noticed after loading pulsea= udio=20 > > > related stuff, I got a kernel panic. > > >=20 > > > You'll notice in the log that I'm using an extended partition as swap= (shared=20 > > > between GNU/Linux and FreeBSD) and FreeBSD is not dumping on it. So I= created a new=20 > > > 'freebsd-swap' partition in disklabel, but no still dumps. > > >=20 > > > Anyways, there is some information related to the fault is logged in = the=20 > > > dmesg[1]. > > >=20 > > > BtW, prior to writing this mail, I've already ran memtest86+ on my bo= x and it=20 > > > has passed all the 8 tests without any errors. > >=20 > > Looks like I can now reproduce on i386 -CURRENT from yesterday. > > However, things are still good on my amd64 -CURRENT from Apr 4. So > > something was committed between 4/4 and 4/8 to break pulse. I'm trying > > to get a back trace. >=20 > If you can, try backing out this commit: >=20 > http://svn.freebsd.org/viewvc/base/head/sys/dev/kbdmux/kbdmux.c?r1=3D1886= 03&r2=3D190857 >=20 > See if it fixes the panic. Come to think of it, I don't think you have this commit yet. Robert Noland is running -CURRENT from 4/6, and he is not seeing the panic. So, something happened between 4/6 and 4/8 to cause this. I'm in worse shape than you. The problem appears as a hard lock on my system. I can't even get any clue as to what's going on. I have ruled out pulseaudio, though. I can start pulse by itself just fine. Joe --=20 PGP Key : http://www.marcuscom.com/pgp.asc --=-ZElZraHuUhYMbS/Q2JfW Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (FreeBSD) iEYEABECAAYFAknhJbsACgkQb2iPiv4Uz4dFFACfflc6RNFQlVfyVBWNINZ/yNei BKsAn1mTx64ffb0sEPRHsgJxShCzausf =dDOX -----END PGP SIGNATURE----- --=-ZElZraHuUhYMbS/Q2JfW--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1239492029.4933.997.camel>