Date: Wed, 15 Jun 2005 12:43:22 -0700 From: Julian Elischer <julian@elischer.org> To: Norbert Koch <NKoch@demig.de> Cc: "Freebsd-Hackers@Freebsd.Org" <freebsd-hackers@freebsd.org> Subject: Re: kernel panic in usb0; was: RE: using vkbd device Message-ID: <42B084DA.7040702@elischer.org> In-Reply-To: <000f01c57173$12f8cc40$4801a8c0@ws-ew-3.W2KDEMIG> References: <000f01c57173$12f8cc40$4801a8c0@ws-ew-3.W2KDEMIG>
next in thread | previous in thread | raw e-mail | index | archive | help
Norbert Koch wrote: >>>>When quickly connecting/disconnecting >>>> >>>> >>>i guess you mean here unplug the keyboard and then immediately plug it >>>back, right? >>> >>> >>> >>sounds like he means "repeatedly." >> >> > >yes > > > >>booting with -gd drops you into the (gdb) debugger immediatly.. >> >>I presume you have a gdb looking at the serial port and have a >>serial debug port defined then? >> >> > >Yes. >That's what I did: > >boot -gd && gdb -k kernel.debug && target remote /dev/cuaa0 > >In gdb "bt" only shows two entries. The function where the panic >occurred and 0x0! > > that is normal you don't want to jump into gdb that soon. there is hardly anything set up. use the sysctl to enter gdb later. >BTW, after boot -gd, when gdb attaches I have a kernel panic too. >But I can just enter "continue" and the kernel continues booting. >Is that ok? > > what do you mean "panic"? I never use -gd, just -g then hitting ^ALT-ESC or using th esysctl makes me enter the debugger when I need to.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?42B084DA.7040702>