Re: kernel panic on boot, acpica related?
sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x8:0xc4109ac1 stack pointer = 0x10:0xd6855ce4 frame pointer = 0x10:0xd6855d0c code segment = base0x0, limit 0xf, type 0x16 = DPL 0, pres 1, def 32, gran 1 processor eflags = interrupt enabled, resume, IOPL=0 current process = 21 (irq10:fxp0 sn0+++*) kernel: type 9 trap, code=0 Stopped at0xc4109ac1: lcall $0xc410,0xa040c410 db trace _end (c158d300,d6855d48,c04897b1,356,0) at 9xc4109ac1 fork_exit (c02ae2c0,c158d300,d6855d48) at fork_exit+0xaf fork_trampoline () at fork_trampoline+0x1a Hmmm, I don't think so. How about typing unset acpi_load in loader prompt, and see if this panic disappear or still happen? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel panic on boot, acpica related?
Mitsuru IWASAKI wrote: sc0: System console at flags 0x100 on isa0 sc0: VGA 16 virtual consoles, flags=0x300 vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec Fatal trap 9: general protection fault while in kernel mode instruction pointer = 0x8:0xc4109ac1 stack pointer = 0x10:0xd6855ce4 frame pointer = 0x10:0xd6855d0c code segment = base0x0, limit 0xf, type 0x16 = DPL 0, pres 1, def 32, gran 1 processor eflags = interrupt enabled, resume, IOPL=0 current process = 21 (irq10:fxp0 sn0+++*) kernel: type 9 trap, code=0 Stopped at0xc4109ac1: lcall $0xc410,0xa040c410 db trace _end (c158d300,d6855d48,c04897b1,356,0) at 9xc4109ac1 fork_exit (c02ae2c0,c158d300,d6855d48) at fork_exit+0xaf fork_trampoline () at fork_trampoline+0x1a Hmmm, I don't think so. How about typing unset acpi_load in loader prompt, and see if this panic disappear or still happen? Hm, right, doesn't go away, slightly different panic now ... Fatal trap 1, but basically same spot. Regards, -- Michael Nottebrock The circumstance ends uglily in the cruel result. - Babelfish msg41575/pgp0.pgp Description: PGP signature
Re: kernel panic on boot, acpica related?
On Thu, Aug 01, 2002 at 10:14:34PM +0900, Mitsuru IWASAKI wrote: Hmmm, I don't think so. How about typing unset acpi_load in loader prompt, and see if this panic disappear or still happen? Where is it documented what to do to stop the autoloading of acpi.ko? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: kernel panic on boot, acpica related?
Terry Lambert wrote: Michael Nottebrock wrote: I tweaked my BIOS to assign a different irq (9) to the NIC and now the kernel boots and runs my old userland quite nicely. The old kernel ran perfectly well with the NIC on irq10 ... strange. None of your other postings identified the devices also on IRQ10. If I had to guess... USB? Almost everything. sym0, csa0, bktr0, atapci1, drm0 ... and USB, but since I can only change IRQs per 'pin', fxp0 still shares its IRQ with USB now. :] Regards, -- Michael Nottebrock The circumstance ends uglily in the cruel result. - Babelfish msg41610/pgp0.pgp Description: PGP signature
Re: kernel panic on boot, acpica related?
Michael Nottebrock wrote: I tweaked my BIOS to assign a different irq (9) to the NIC and now the kernel boots and runs my old userland quite nicely. The old kernel ran perfectly well with the NIC on irq10 ... strange. None of your other postings identified the devices also on IRQ10. If I had to guess... USB? Almost everything. sym0, csa0, bktr0, atapci1, drm0 ... and USB, but since I can only change IRQs per 'pin', fxp0 still shares its IRQ with USB now. :] I know it's work, but it'd probably be worthwhile to track down which device(s), when sharing the same IRQ, cause the problem, so that it can be fixed, instead of the next person having to work around it, too. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
