Date: Wed, 10 Jun 2009 10:35:10 +0530 From: wahjava.ml@gmail.com (Ashish SHUKLA) To: "Paul B. Mahol" <onemda@gmail.com> Cc: freebsd-questions@freebsd.org Subject: Re: 7.2-RELEASE panics with snd_ds1 loaded. Message-ID: <861vpsllvd.fsf@chateau.d.lf> In-Reply-To: <3a142e750906090634w10e275d3wcaf76f5f117c8f9f@mail.gmail.com> (Paul B. Mahol's message of "Tue, 9 Jun 2009 13:34:56 %2B0000") References: <86skifqn2x.fsf@chateau.d.lf> <200906081647.15069.mel.flynn%2Bfbsd.questions@mailing.thruhere.net> <20090609111703.GA98742@chateau.d.lf> <3a142e750906090634w10e275d3wcaf76f5f117c8f9f@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--=-=-= Content-Transfer-Encoding: quoted-printable Paul B Mahol writes: > On 6/9/09, Ashish SHUKLA <wahjava.ml@gmail.com> wrote: >> Hi Mel, >>=20 >> Thanks for responding. >>=20 >> In <200906081647.15069.mel.flynn+fbsd.questions@mailing.thruhere.net>, M= el >> Flynn wrote: >>=20 >> [...] >>=20 >>> Nothing points to the sound module specifically. The first trace is >>> unusable >>> (frames missing) and the second trace panics in sleep, which maybe poin= ts >>> to >>> the sound module and interrupts. Are you not able to panic the system >>> without >>> that sound module loaded? It looks too random to blame one module, more >>> hardware, but it's possible the module exposes a bug elsewhere. From th= is >>> though, it is hard to tell. >>=20 >> Yes, I noticed myself, that there is no reason why to blame 'sound' modu= le >> for >> it. But I noticed my box only panics when there is some activity going on >> with >> sound device, like at one time, it paniced when I was trying to record a= udio >> using gnome-sound-recorder, and another it paniced when I was playing au= dio >> using ogg123. And that it too, it didn't panic immediately after start of >> operation (playing/recording), but only after some time has elapsed. And= the >> system doesn't panic without snd_ds1 loaded even after building ports (l= ike >> openjdk6 and libxul) and using GNOME for 4 hours. BtW, I forgot to menti= on >> in >> last post, but I'm running the GENERIC kernel bundled with 7.2-RELEASE D= VD. >>=20 >> I don't know how to resolve and whether this is some kind of memory issu= e or >> something else. I also experienced something similar panic situation[1] = with >> 8.0-CURRENT which no one else is able to reproduce except me, after whic= h I >> installed 7.2-RELEASE. Any ideas how to trace this problem, it is >> discouraging >> me to continue using FreeBSD for my regular desktop use ? >>=20 >> References: >> [1] - >> http://lists.freebsd.org/pipermail/freebsd-gnome/2009-April/022048.html > Does same problem happens on i386? I've not installed i386 versions of any versions of FreeBSD, as I don't have any spare box. So I can't say if those problems are reproducible on i386 also. > --=20 > Paul Thanks =2D-=20 Ashish SHUKLA --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.11 (FreeBSD) iEYEARECAAYFAkovPwsACgkQHy+EEHYuXnQ+lwCgmmjX8HpRZu0vucaR0e0BrBED fDgAmgMIoxJk1DGyHuxN9/sqmsWDDzIZ =w85s -----END PGP SIGNATURE----- --=-=-=--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?861vpsllvd.fsf>