Date: Tue, 13 Sep 2005 03:37:21 +0000 From: Ben Kaduk <minimarmot@gmail.com> To: Alexander Leidinger <Alexander@leidinger.net>, freebsd-current@freebsd.org Subject: Re: panic upon kldunload snd_ich (lor # 159) Message-ID: <47d0403c050912203737fd5f37@mail.gmail.com> In-Reply-To: <47d0403c050912190015fa9273@mail.gmail.com> References: <47d0403c05091121047a037946@mail.gmail.com> <20050912204405.14437629@Magellan.Leidinger.net> <47d0403c050912190015fa9273@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 9/13/05, Ben Kaduk <minimarmot@gmail.com> wrote: >=20 >=20 >=20 > On 9/12/05, Alexander Leidinger <Alexander@leidinger.net> wrote: > >=20 > > On Mon, 12 Sep 2005 04:04:48 +0000 > > Ben Kaduk <minimarmot@gmail.com> wrote: > >=20 > > > Booting to single user and issuing: > > > # kldload snd_ich > > > # kldunload snd_ich=20 > > > > > > are sufficient to trigger the panic on my system. I know that=20 > > Alexander > > > Leidinger has recently committed some bits to current in the sound=20 > > code, but > > > it is unclear if it will fix my panic; I'm currently cvsup-ing and=20 > > building=20 > > > world to find out. > > > > > > The machine in question is: > > > > > > bash-2.05b$ uname -a > > > FreeBSD prolepsis.math.uiuc.edu <http://prolepsis.math.uiuc.edu>; <htt= p://prolepsis.math.uiuc.edu > > > > > > 7.0-CURRENTFreeBSD > > > 7.0-CURRENT #9: Thu Aug 25 06:22:00 UTC 2005 > > > kaduk@prolepsis.math.uiuc.edu:/usr/obj/usr/src/sys/PROLEPSIS > > > i386 > >=20 > > You should update to a -current which has:=20 > > ---snip--- > > $FreeBSD: src/sys/dev/sound/pcm/sound.c,v 1.96 2005/09/12 18:33:33=20 > > netchild Exp $ > > $FreeBSD: src/sys/dev/sound/pcm/dsp.c,v 1.84 2005/09/12 18:33:33=20 > > netchild Exp $ > > ---snip--- > >=20 > > If it still panics we need to get a backtrace (please have a look at=20 > > the kernel-debugging chapter in the handbook; taking a backtrace isn't > > hard). > >=20 > > Bye, > > Alexander. > >=20 > > -- > > 0 and 1. Now what could be so hard about that? > >=20 > > http://www.Leidinger.net Alexander @ Leidinger.net<http://Leidinger.net= > > > GPG fingerprint =3D C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7 > >=20 >=20 > I upgraded to todays current, with=20 > $FreeBSD: src/sys/dev/sound/pcm/sound.c,v 1.96 2005/09/12 18:33:33=20 > netchild Exp $ and > $FreeBSD: src/sys/dev/sound/pcm/dsp.c,v 1.84 2005/09/12 18:33:33 netchild= =20 > Exp $, > and the panic still occurs, even in single-user. I can dump without=20 > complaints, but since my /var is only 256 M, I have been manually running= =20 > savecore in single user, saving cores in /usr/crash (perhaps I should try= =20 > with hw.physmem=3D200M); this latest core seems to have problems: > prolepsis# kgdb /usr/obj/usr/src/sys/PROLEPSIS/kernel.debug=20 > /usr/crash/vmcore.0 > results in a (infinite) loop of: > kgdb: kvm_read: invalid address (0xf0) >=20 > so this could be tough to debug. I will try to get an automatic dump on= =20 > /var, and if that fails, set up a serial console and leave the machine in= =20 > the debugger. >=20 > Ben Kaduk >=20 >=20 Bad news: the dump on /var, though it seems to complete successfully,=20 exhibits the same looping behaviour of the bigger dump, namely: kgdb: kvm_read: invalid address (0xf0) Also, I seem to be incompotent at reading documentation, in that I have yet= =20 to get a working serial console. I tried both booting with a serial console and switching to gdb over serial= =20 console from ddb. In both cases I have a null-modem cable connecting sio0 o= n=20 the problem box (prolepsis) to sio0 on an older 5.3-beta3 box (pleonasm). To try to boot from a serial console, I dropped to the loader prompt on=20 prolepsis (the box that panics), and tried "boot -h". This did not seem to= =20 have any affect, as console output was still directed to the video console,= =20 even after the system hit multiuser. I also tried dropping to the loader an= d=20 typing "set console=3Dcomconsole", which resulted in a (infinite) wait on= =20 prolepsis. I then tried various "tip" commands on pleonasm, such as "tip=20 /dev/cuaa0" and "tip com1", the latter of which was the only one which=20 seemed to have any affect, namely that the terminal on pleonasm printed out= =20 "connected" and then ceased to respond to anything at all, and nothing=20 happened on prolepsis, either. I also tried to enter the debugger on prolepsis and then switch to gdb over= =20 serial console, along the lines of: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kernel= debug-online-gdb.html I panic()ed prolepsis, then ran "kgdb -r /dev/cuaa0 kernel.debug" on=20 pleonasm, where kernel.debug was copied from prolepsis. This seemed to=20 connect, but typing "gdb" at the debugger prompt on prolepsis resulted in a= n=20 error along the lines of "gdb remote protocol is not active now", which=20 presumably means that I need to set a flag on the serial port, but I don't= =20 know where or what. In summary, I am unclear on how to use tip to access a serial console, and= =20 on serial port flags for console use. I hope someone can point out my errors, so I can get a useable stack trace. Thanks Ben Kaduk
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47d0403c050912203737fd5f37>