Re: USB mouse/keyboard causes kernel panic during boot sequence
> > > There is one last thing you can do: put > > > options DDB > > > in your kernel config file. Recompile. Reproduce. > > > ddb> trace > > > ... > > > ddb> continue > > > ... > > > ddb> continue > > > Uptime - 0s > > > Rebooting... > > > > > > -- Josh Next time it involves this much typing... don't tell me... :P uhci_idone(0,c2e17180,c2e18000,c2e17180,c0494d6c) at +0xc uhci_waitintr(c2e18000,c2e17180,c2e17180,8,c0494d7c) at +0xb6 uhci_device_ctrl_start(c2e17180,0,c0494da4,c026f219,c2e17180) at +0x2c uhci_device_ctrl_transfer(c2e,17180,0,c2e17180,c0494e0c,c026fc12) at +0x1f usbd_transfer(c2e17180,c0494dd4,c026fc1b,c2e17180,c2e17130) at +0xd1 usbd_sync_transfer(c2e17180,c2e17130,c2e17100,c2e17130,c2e0daf0) at +0x10 usbd_request_flags(c2e17100,c0494e0c,c2e17130,0,0) at +0x5f usbd_do_request(c2e17100,c0494e0c,c2e17130,c2e17100,0) at +0x18 usbd_get_desc(c2e17100,1,0,8,c2e17130) at +0x67 usbd_new_device(c2e17300,c2e18000,1,200,1,c2e17260) at +0x148 uhub_explore(c2e17480,c2e17500,c2e17c00,0,c0494ea0) at +0x2be usb_attach(c2e17500,c0494ebc,c0186f0f,c2e17500,c2e18000) at +0x112 DEVICE_ATTACH(c2e17500,c2e18000,c2e17c00,0,1) at +0x2e device_probe_and_attach(c2e17500) at +0x63 uhci_pci_attach(c2e17c00,c0494f08,c0186f0f,c2e17c00,c2e17c00) at +0x2c6 DEVICE_ATTACH(c2e17c00,c2e17c00,c2e16280,0,0) at +0x2e device_probe_and_attach(c2e17c00) at +0x63 bus_generic_attach(c2e16100,c0494f40,c0186f0f,c2e16100,c2e16100) at +0x16 DEVICE_ATTACH(c2e16100,c2e16100,c2e16400,0,1) at +0x2e device_probe_and_attach(c2e16100) at +0x63 bus_generic_attach(c2e16280,c0494f78,c0186f0f,c2e16280,c2e16280) at +0x16 DEVICE_ATTACH(c2e16280,c2e16280,c1454880,0,1) at +0x2e device_probe_and_attach(c2e16280) at +0x63 bus_generic_attach(c2e16400,c2e16400,c0494fa4,c012dd6e,c2e16400) at +0x16 nexus_attach(c2e16400,c0494fc0,c0186f0f,c2e16400,c2e16400) at +0xd DEVICE_ATTACH(c2e16400,c2e16400,c0386ad0,49c000,1) at +0x2e device_probe_and_attach(c2e16400) at +0x63 root_bus_configure(c1454880,c035e6ec,0) at +0x16 configure(0,491c00,49c00,0,c012d660) at +0x2a mi_startup(0,0,0,0,0) at +0x69 begin() at +0x47 That's it... hope I read my writing correctly :) Michael ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB mouse/keyboard causes kernel panic during boot sequence
On Wed, Jul 09, 2003 at 04:38:09PM -0400 or thereabouts, Michael E. Mercer wrote: > Josh, > > Is there an easy way to capture this without me having to handwrite all > that info down myself? Unless you have a serial console, no. However, some kernel programmer on this list may be able to give a function that enables dumping on a certain device (as a ddb call). Anyone? -- Josh > > Michael Mercer > > On Wed, 2003-07-09 at 13:19, Joshua Oreman wrote: > > On Tue, Jul 08, 2003 at 01:05:18PM -0400 or thereabouts, Michael E. Mercer wrote: > > > On Tue, 2003-07-08 at 12:11, Joshua Oreman wrote: > > > > On Mon, Jul 07, 2003 at 11:43:21PM -0400 or thereabouts, Michael E. Mercer > > > > wrote: > > > > > Alrighty then, > > > > > > > > > > Ok, after following FAQ 18.13 on the freebsd web site, > > > > > I've been struggling for the last 4 hours trying to get this thing to > > > > > dump core but it just won't! I added ad2s1b to the dumpdev in rc.conf > > > > > and also read about kernel init problems need to have dumpdev added to > > > > > the loader. So I added it to loader.conf as well. > > > > > > > > Your swap partition must be at least a few megs bigger than your physical > > > > RAM. > > > > > > > My swap is 1 Gig. I also changed MAXMEM in my kernel to a much smaller > > > size... still can not get a dump... > > > > Ah, silly me. Since this is a device probe panic, rc.conf setting dumpdev > > won't ever happen. > > > > There is one last thing you can do: put > > options DDB > > in your kernel config file. Recompile. Reproduce. > > ddb> trace > > ... > > ddb> continue > > ... > > ddb> continue > > Uptime - 0s > > Rebooting... > > > > -- Josh > > > > > > > > Any ideas? > > > > > > > > > > > > > Anyways, the method it points to is uhci_idone. > > > > > > > > Thanks! > > > > > > No, thank you for your help! > > > > > > Michael > > > > > > > > -- Josh > > > > > > > > > > > > > > That's all I can find out at the moment, unless someone can inform me of > > > > > what I am doing wrong. > > > > > > > > > > Thanks > > > > > Michael > > > > > > > > > > > > > > > > > > > > On Mon, 2003-07-07 at 13:03, Joshua Oreman wrote: > > > > > > On Mon, Jul 07, 2003 at 12:34:48PM -0400 or thereabouts, Michael E. Mercer > > > > > > wrote: > > > > > > > Anybody?!?!?! > > > > > > > > > > > > > > > > > > > > > > > > > > > > Hello peoples, > > > > > > > > > > > > > > I have posted this before and unfortunately I still have this problem. > > > > > > > During the boot sequence, when it probes for the USB devices, it causes > > > > > > > a kernel panic (page fault) if there is either (or both) a USB mouse > > > > > > > and/or keyboard attached. > > > > > > > > > > > > > > If I remove the mouse and keyboard and let it boot up, then connect > > > > > > > them, they work just fine. > > > > > > > > > > > > > > Any ideas? > > > > > > > > > > > > > Fatal trap 12: page fault while in kernel mode > > > > > > > mp_lock = 0024; cpuid = 0; lapic.id = > > > > > > > fault virtual address = 0x4 > > > > > > > fault code = supervisor read, page not present > > > > > > > instruction pointer = 0x8: 0xc02583c4 > > > > > > > > > > > > > stack pointer = 0x10: 0xc045fd20 > > > > > > > frame pointer = 0x10: 0xc045fd3c > > > > > > > code segment= base 0x0, limit 0xf, type 0x1b > > > > > > > = DPL 0, pres 1, def 32 1, gran 1 > > > > > > > processor eflags= interrupt enabled, resume, IOPC=0 > > > > > > > current process = 0(swapper) > > > > > > > interrupt mask = none <- SMP: XXX > > > > > > > trap number = 12 > > > > > > > panic: page fault > > > > > > > mp_lock = 0024; cpuid = 0; lapic.id = > > > > > > > Uptime - 0s > > > > > > > > > > > > That pointer I highlighted is important; it is also kernel-dependent. > > > > > > Please read FAQ #18.13 to find out how to give us some useful function > > > > > > names, > > > > > > or better yet, a backtrace. > > > > > > > > > > > > -- Josh > > > > > > > > > > > > > > > > > > > > Thanks > > > > > > > Michael Mercer > > > > > > > > > > > > > > > > > > > > > ___ > > > > > > > [EMAIL PROTECTED] mailing list > > > > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > > > > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB mouse/keyboard causes kernel panic during boot sequence
Josh, Is there an easy way to capture this without me having to handwrite all that info down myself? Michael Mercer On Wed, 2003-07-09 at 13:19, Joshua Oreman wrote: > On Tue, Jul 08, 2003 at 01:05:18PM -0400 or thereabouts, Michael E. Mercer wrote: > > On Tue, 2003-07-08 at 12:11, Joshua Oreman wrote: > > > On Mon, Jul 07, 2003 at 11:43:21PM -0400 or thereabouts, Michael E. Mercer wrote: > > > > Alrighty then, > > > > > > > > Ok, after following FAQ 18.13 on the freebsd web site, > > > > I've been struggling for the last 4 hours trying to get this thing to > > > > dump core but it just won't! I added ad2s1b to the dumpdev in rc.conf > > > > and also read about kernel init problems need to have dumpdev added to > > > > the loader. So I added it to loader.conf as well. > > > > > > Your swap partition must be at least a few megs bigger than your physical > > > RAM. > > > > > My swap is 1 Gig. I also changed MAXMEM in my kernel to a much smaller > > size... still can not get a dump... > > Ah, silly me. Since this is a device probe panic, rc.conf setting dumpdev > won't ever happen. > > There is one last thing you can do: put > options DDB > in your kernel config file. Recompile. Reproduce. > ddb> trace > ... > ddb> continue > ... > ddb> continue > Uptime - 0s > Rebooting... > > -- Josh > > > > > Any ideas? > > > > > > > > > > Anyways, the method it points to is uhci_idone. > > > > > > Thanks! > > > > No, thank you for your help! > > > > Michael > > > > > > -- Josh > > > > > > > > > > > That's all I can find out at the moment, unless someone can inform me of > > > > what I am doing wrong. > > > > > > > > Thanks > > > > Michael > > > > > > > > > > > > > > > > On Mon, 2003-07-07 at 13:03, Joshua Oreman wrote: > > > > > On Mon, Jul 07, 2003 at 12:34:48PM -0400 or thereabouts, Michael E. Mercer > > > > > wrote: > > > > > > Anybody?!?!?! > > > > > > > > > > > > > > > > > > > > > > > > Hello peoples, > > > > > > > > > > > > I have posted this before and unfortunately I still have this problem. > > > > > > During the boot sequence, when it probes for the USB devices, it causes > > > > > > a kernel panic (page fault) if there is either (or both) a USB mouse > > > > > > and/or keyboard attached. > > > > > > > > > > > > If I remove the mouse and keyboard and let it boot up, then connect > > > > > > them, they work just fine. > > > > > > > > > > > > Any ideas? > > > > > > > > > > > Fatal trap 12: page fault while in kernel mode > > > > > > mp_lock = 0024; cpuid = 0; lapic.id = > > > > > > fault virtual address = 0x4 > > > > > > fault code = supervisor read, page not present > > > > > > instruction pointer = 0x8: 0xc02583c4 > > > > > > > > > > > stack pointer = 0x10: 0xc045fd20 > > > > > > frame pointer = 0x10: 0xc045fd3c > > > > > > code segment= base 0x0, limit 0xf, type 0x1b > > > > > > = DPL 0, pres 1, def 32 1, gran 1 > > > > > > processor eflags= interrupt enabled, resume, IOPC=0 > > > > > > current process = 0(swapper) > > > > > > interrupt mask = none <- SMP: XXX > > > > > > trap number = 12 > > > > > > panic: page fault > > > > > > mp_lock = 0024; cpuid = 0; lapic.id = > > > > > > Uptime - 0s > > > > > > > > > > That pointer I highlighted is important; it is also kernel-dependent. > > > > > Please read FAQ #18.13 to find out how to give us some useful function names, > > > > > or better yet, a backtrace. > > > > > > > > > > -- Josh > > > > > > > > > > > > > > > > > Thanks > > > > > > Michael Mercer > > > > > > > > > > > > > > > > > > ___ > > > > > > [EMAIL PROTECTED] mailing list > > > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > > > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB mouse/keyboard causes kernel panic during boot sequence
On Tue, Jul 08, 2003 at 01:05:18PM -0400 or thereabouts, Michael E. Mercer wrote: > On Tue, 2003-07-08 at 12:11, Joshua Oreman wrote: > > On Mon, Jul 07, 2003 at 11:43:21PM -0400 or thereabouts, Michael E. Mercer wrote: > > > Alrighty then, > > > > > > Ok, after following FAQ 18.13 on the freebsd web site, > > > I've been struggling for the last 4 hours trying to get this thing to > > > dump core but it just won't! I added ad2s1b to the dumpdev in rc.conf > > > and also read about kernel init problems need to have dumpdev added to > > > the loader. So I added it to loader.conf as well. > > > > Your swap partition must be at least a few megs bigger than your physical > > RAM. > > > My swap is 1 Gig. I also changed MAXMEM in my kernel to a much smaller > size... still can not get a dump... Ah, silly me. Since this is a device probe panic, rc.conf setting dumpdev won't ever happen. There is one last thing you can do: put options DDB in your kernel config file. Recompile. Reproduce. ddb> trace ... ddb> continue ... ddb> continue Uptime - 0s Rebooting... -- Josh > > Any ideas? > > > > > > > Anyways, the method it points to is uhci_idone. > > > > Thanks! > > No, thank you for your help! > > Michael > > > > -- Josh > > > > > > > > That's all I can find out at the moment, unless someone can inform me of > > > what I am doing wrong. > > > > > > Thanks > > > Michael > > > > > > > > > > > > On Mon, 2003-07-07 at 13:03, Joshua Oreman wrote: > > > > On Mon, Jul 07, 2003 at 12:34:48PM -0400 or thereabouts, Michael E. Mercer > > > > wrote: > > > > > Anybody?!?!?! > > > > > > > > > > > > > > > > > > > > Hello peoples, > > > > > > > > > > I have posted this before and unfortunately I still have this problem. > > > > > During the boot sequence, when it probes for the USB devices, it causes > > > > > a kernel panic (page fault) if there is either (or both) a USB mouse > > > > > and/or keyboard attached. > > > > > > > > > > If I remove the mouse and keyboard and let it boot up, then connect > > > > > them, they work just fine. > > > > > > > > > > Any ideas? > > > > > > > > > Fatal trap 12: page fault while in kernel mode > > > > > mp_lock = 0024; cpuid = 0; lapic.id = > > > > > fault virtual address = 0x4 > > > > > fault code = supervisor read, page not present > > > > > instruction pointer = 0x8: 0xc02583c4 > > > > > > > > > stack pointer = 0x10: 0xc045fd20 > > > > > frame pointer = 0x10: 0xc045fd3c > > > > > code segment= base 0x0, limit 0xf, type 0x1b > > > > > = DPL 0, pres 1, def 32 1, gran 1 > > > > > processor eflags= interrupt enabled, resume, IOPC=0 > > > > > current process = 0(swapper) > > > > > interrupt mask = none <- SMP: XXX > > > > > trap number = 12 > > > > > panic: page fault > > > > > mp_lock = 0024; cpuid = 0; lapic.id = > > > > > Uptime - 0s > > > > > > > > That pointer I highlighted is important; it is also kernel-dependent. > > > > Please read FAQ #18.13 to find out how to give us some useful function names, > > > > or better yet, a backtrace. > > > > > > > > -- Josh > > > > > > > > > > > > > > Thanks > > > > > Michael Mercer > > > > > > > > > > > > > > > ___ > > > > > [EMAIL PROTECTED] mailing list > > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB mouse/keyboard causes kernel panic during boot sequence
On Tue, 2003-07-08 at 12:11, Joshua Oreman wrote: > On Mon, Jul 07, 2003 at 11:43:21PM -0400 or thereabouts, Michael E. Mercer wrote: > > Alrighty then, > > > > Ok, after following FAQ 18.13 on the freebsd web site, > > I've been struggling for the last 4 hours trying to get this thing to > > dump core but it just won't! I added ad2s1b to the dumpdev in rc.conf > > and also read about kernel init problems need to have dumpdev added to > > the loader. So I added it to loader.conf as well. > > Your swap partition must be at least a few megs bigger than your physical > RAM. > My swap is 1 Gig. I also changed MAXMEM in my kernel to a much smaller size... still can not get a dump... Any ideas? > > > > Anyways, the method it points to is uhci_idone. > > Thanks! No, thank you for your help! Michael > > -- Josh > > > > > That's all I can find out at the moment, unless someone can inform me of > > what I am doing wrong. > > > > Thanks > > Michael > > > > > > > > On Mon, 2003-07-07 at 13:03, Joshua Oreman wrote: > > > On Mon, Jul 07, 2003 at 12:34:48PM -0400 or thereabouts, Michael E. Mercer wrote: > > > > Anybody?!?!?! > > > > > > > > > > > > > > > > Hello peoples, > > > > > > > > I have posted this before and unfortunately I still have this problem. > > > > During the boot sequence, when it probes for the USB devices, it causes > > > > a kernel panic (page fault) if there is either (or both) a USB mouse > > > > and/or keyboard attached. > > > > > > > > If I remove the mouse and keyboard and let it boot up, then connect > > > > them, they work just fine. > > > > > > > > Any ideas? > > > > > > > Fatal trap 12: page fault while in kernel mode > > > > mp_lock = 0024; cpuid = 0; lapic.id = > > > > fault virtual address = 0x4 > > > > fault code = supervisor read, page not present > > > > instruction pointer = 0x8: 0xc02583c4 > > > > > > > stack pointer = 0x10: 0xc045fd20 > > > > frame pointer = 0x10: 0xc045fd3c > > > > code segment= base 0x0, limit 0xf, type 0x1b > > > > = DPL 0, pres 1, def 32 1, gran 1 > > > > processor eflags= interrupt enabled, resume, IOPC=0 > > > > current process = 0(swapper) > > > > interrupt mask = none <- SMP: XXX > > > > trap number = 12 > > > > panic: page fault > > > > mp_lock = 0024; cpuid = 0; lapic.id = > > > > Uptime - 0s > > > > > > That pointer I highlighted is important; it is also kernel-dependent. > > > Please read FAQ #18.13 to find out how to give us some useful function names, > > > or better yet, a backtrace. > > > > > > -- Josh > > > > > > > > > > > Thanks > > > > Michael Mercer > > > > > > > > > > > > ___ > > > > [EMAIL PROTECTED] mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB mouse/keyboard causes kernel panic during boot sequence
On Mon, Jul 07, 2003 at 11:43:21PM -0400 or thereabouts, Michael E. Mercer wrote: > Alrighty then, > > Ok, after following FAQ 18.13 on the freebsd web site, > I've been struggling for the last 4 hours trying to get this thing to > dump core but it just won't! I added ad2s1b to the dumpdev in rc.conf > and also read about kernel init problems need to have dumpdev added to > the loader. So I added it to loader.conf as well. Your swap partition must be at least a few megs bigger than your physical RAM. > > Anyways, the method it points to is uhci_idone. Thanks! -- Josh > > That's all I can find out at the moment, unless someone can inform me of > what I am doing wrong. > > Thanks > Michael > > > > On Mon, 2003-07-07 at 13:03, Joshua Oreman wrote: > > On Mon, Jul 07, 2003 at 12:34:48PM -0400 or thereabouts, Michael E. Mercer wrote: > > > Anybody?!?!?! > > > > > > > > > > > > Hello peoples, > > > > > > I have posted this before and unfortunately I still have this problem. > > > During the boot sequence, when it probes for the USB devices, it causes > > > a kernel panic (page fault) if there is either (or both) a USB mouse > > > and/or keyboard attached. > > > > > > If I remove the mouse and keyboard and let it boot up, then connect > > > them, they work just fine. > > > > > > Any ideas? > > > > > Fatal trap 12: page fault while in kernel mode > > > mp_lock = 0024; cpuid = 0; lapic.id = > > > fault virtual address = 0x4 > > > fault code = supervisor read, page not present > > > instruction pointer = 0x8: 0xc02583c4 > > > > > stack pointer = 0x10: 0xc045fd20 > > > frame pointer = 0x10: 0xc045fd3c > > > code segment= base 0x0, limit 0xf, type 0x1b > > > = DPL 0, pres 1, def 32 1, gran 1 > > > processor eflags= interrupt enabled, resume, IOPC=0 > > > current process = 0(swapper) > > > interrupt mask = none <- SMP: XXX > > > trap number = 12 > > > panic: page fault > > > mp_lock = 0024; cpuid = 0; lapic.id = > > > Uptime - 0s > > > > That pointer I highlighted is important; it is also kernel-dependent. > > Please read FAQ #18.13 to find out how to give us some useful function names, > > or better yet, a backtrace. > > > > -- Josh > > > > > > > > Thanks > > > Michael Mercer > > > > > > > > > ___ > > > [EMAIL PROTECTED] mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB mouse/keyboard causes kernel panic during boot sequence
Alrighty then, Ok, after following FAQ 18.13 on the freebsd web site, I've been struggling for the last 4 hours trying to get this thing to dump core but it just won't! I added ad2s1b to the dumpdev in rc.conf and also read about kernel init problems need to have dumpdev added to the loader. So I added it to loader.conf as well. Anyways, the method it points to is uhci_idone. That's all I can find out at the moment, unless someone can inform me of what I am doing wrong. Thanks Michael On Mon, 2003-07-07 at 13:03, Joshua Oreman wrote: > On Mon, Jul 07, 2003 at 12:34:48PM -0400 or thereabouts, Michael E. Mercer wrote: > > Anybody?!?!?! > > > > > > > > Hello peoples, > > > > I have posted this before and unfortunately I still have this problem. > > During the boot sequence, when it probes for the USB devices, it causes > > a kernel panic (page fault) if there is either (or both) a USB mouse > > and/or keyboard attached. > > > > If I remove the mouse and keyboard and let it boot up, then connect > > them, they work just fine. > > > > Any ideas? > > > Fatal trap 12: page fault while in kernel mode > > mp_lock = 0024; cpuid = 0; lapic.id = > > fault virtual address = 0x4 > > fault code = supervisor read, page not present > > instruction pointer = 0x8: 0xc02583c4 > > > stack pointer = 0x10: 0xc045fd20 > > frame pointer = 0x10: 0xc045fd3c > > code segment= base 0x0, limit 0xf, type 0x1b > > = DPL 0, pres 1, def 32 1, gran 1 > > processor eflags= interrupt enabled, resume, IOPC=0 > > current process = 0(swapper) > > interrupt mask = none <- SMP: XXX > > trap number = 12 > > panic: page fault > > mp_lock = 0024; cpuid = 0; lapic.id = > > Uptime - 0s > > That pointer I highlighted is important; it is also kernel-dependent. > Please read FAQ #18.13 to find out how to give us some useful function names, > or better yet, a backtrace. > > -- Josh > > > > > Thanks > > Michael Mercer > > > > > > ___ > > [EMAIL PROTECTED] mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: USB mouse/keyboard causes kernel panic during boot sequence
On Mon, Jul 07, 2003 at 12:34:48PM -0400 or thereabouts, Michael E. Mercer wrote: > Anybody?!?!?! > > > > Hello peoples, > > I have posted this before and unfortunately I still have this problem. > During the boot sequence, when it probes for the USB devices, it causes > a kernel panic (page fault) if there is either (or both) a USB mouse > and/or keyboard attached. > > If I remove the mouse and keyboard and let it boot up, then connect > them, they work just fine. > > Any ideas? > Fatal trap 12: page fault while in kernel mode > mp_lock = 0024; cpuid = 0; lapic.id = > fault virtual address = 0x4 > fault code = supervisor read, page not present > instruction pointer = 0x8: 0xc02583c4 > stack pointer = 0x10: 0xc045fd20 > frame pointer = 0x10: 0xc045fd3c > code segment= base 0x0, limit 0xf, type 0x1b > = DPL 0, pres 1, def 32 1, gran 1 > processor eflags= interrupt enabled, resume, IOPC=0 > current process = 0(swapper) > interrupt mask = none <- SMP: XXX > trap number = 12 > panic: page fault > mp_lock = 0024; cpuid = 0; lapic.id = > Uptime - 0s That pointer I highlighted is important; it is also kernel-dependent. Please read FAQ #18.13 to find out how to give us some useful function names, or better yet, a backtrace. -- Josh > > Thanks > Michael Mercer > > > ___ > [EMAIL PROTECTED] mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
USB mouse/keyboard causes kernel panic during boot sequence
Anybody?!?!?! Hello peoples, I have posted this before and unfortunately I still have this problem. During the boot sequence, when it probes for the USB devices, it causes a kernel panic (page fault) if there is either (or both) a USB mouse and/or keyboard attached. If I remove the mouse and keyboard and let it boot up, then connect them, they work just fine. Any ideas? Thanks Michael Mercer uname -a FreeBSD dual.mmercer.com 4.8-STABLE FreeBSD 4.8-STABLE #0: Tue Jul 1 11:44:10 EDT 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/dualII_4_8 i386 snippet from dmesg uhci0: port 0xef80-0xef9f irq 2 at device 7.2 on pci0 uhci0: LegSup = 0x003a usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ERROR MESSAGE uhub2: 2 ports with 2 removable, self powered Fatal trap 12: page fault while in kernel mode mp_lock = 0024; cpuid = 0; lapic.id = fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8: 0xc02583c4 stack pointer = 0x10: 0xc045fd20 frame pointer = 0x10: 0xc045fd3c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def 32 1, gran 1 processor eflags= interrupt enabled, resume, IOPC=0 current process = 0(swapper) interrupt mask = none <- SMP: XXX trap number = 12 panic: page fault mp_lock = 0024; cpuid = 0; lapic.id = Uptime - 0s ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
USB mouse/keyboard causes kernel panic during boot sequence
Hello peoples, I have posted this before and unfortunately I still have this problem. During the boot sequence, when it probes for the USB devices, it causes a kernel panic (page fault) if there is either (or both) a USB mouse and/or keyboard attached. If I remove the mouse and keyboard and let it boot up, then connect them, they work just fine. Any ideas? Thanks Michael Mercer uname -a FreeBSD dual.mmercer.com 4.8-STABLE FreeBSD 4.8-STABLE #0: Tue Jul 1 11:44:10 EDT 2003 [EMAIL PROTECTED]:/usr/src/sys/compile/dualII_4_8 i386 snippet from dmesg uhci0: port 0xef80-0xef9f irq 2 at device 7.2 on pci0 uhci0: LegSup = 0x003a usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ERROR MESSAGE uhub2: 2 ports with 2 removable, self powered Fatal trap 12: page fault while in kernel mode mp_lock = 0024; cpuid = 0; lapic.id = fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8: 0xc02583c4 stack pointer = 0x10: 0xc045fd20 frame pointer = 0x10: 0xc045fd3c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def 32 1, gran 1 processor eflags= interrupt enabled, resume, IOPC=0 current process = 0(swapper) interrupt mask = none <- SMP: XXX trap number = 12 panic: page fault mp_lock = 0024; cpuid = 0; lapic.id = Uptime - 0s ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
USB mouse/keyboard causes kernel panic during boot sequence
Hello peoples, I have posted this before and unfortunately I still have this problem. During the boot sequence, when it probes for the USB devices, it causes a kernel panic (page fault) if there is either (or both) a USB mouse and/or keyboard attached. If I remove the mouse and keyboard and let it boot up, then connect them, they work just fine. Any ideas? Thanks Michael Mercer uhub2: 2 ports with 2 removable, self powered Fatal trap 12: page fault while in kernel mode mp_lock = 0024; cpuid = 0; lapic.id = fault virtual address = 0x4 fault code = supervisor read, page not present instruction pointer = 0x8: 0xc02583c4 stack pointer = 0x10: 0xc045fd20 frame pointer = 0x10: 0xc045fd3c code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def 32 1, gran 1 processor eflags= interrupt enabled, resume, IOPC=0 current process = 0(swapper) interrupt mask = none <- SMP: XXX trap number = 12 panic: page fault mp_lock = 0024; cpuid = 0; lapic.id = Uptime - 0s ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
