Re: `panic: run_interrupt_driven_config_hooks: waited too long' on HP DV8
On Mon, Mar 14, 2011 at 2:34 AM, Matthew Jacob m...@feral.com wrote: On 3/13/2011 5:03 PM, Yuri Pankov wrote: On Sun, Mar 13, 2011 at 04:41:58PM -0700, Matthew Jacob wrote: Yes they are. The full messages from the failed boot would be helpful. Looks like we have ATA in CAM now, so it's possible that the disk reset failed, etc... What are my options for saving the output from failed boot other than handtyping it (no serial ports, no serial USB adapters)? None that I can think of :-( Well, there's always the digital camera / posting pictures solution... -- Daniel Nebdal ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: `panic: run_interrupt_driven_config_hooks: waited too long' on HP DV8
On Mon, Mar 14, 2011 at 02:01:38AM +0300, Yuri Pankov wrote: Hi, I'm getting the following panic trying to boot March 5 snapshot on HP Pavilion DV8 notebook (8.2-RELEASE GENERIC kernel seems to boot on the same hardware just fine): run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config panic: run_interrupt_driven_config_hooks: waited too long cpuid = 0 KDB: enter: panic [ thread pid 0 tid 10 ] Stopped atkdb_enter+03xb: movq$0,0x800ab2(%rip) db bt Tracing pid 0 tid 10 td 0x80ee83e30 kdb_enter() at kdb_enter+0x3b panic() at panic+0x180 boot_run_interrupt_driven_config_hooks() at boot_run_interrupt_driven_config_hooks+0xb3 mi_startup() at mi_startup+0x77 btext() at btext+0x2c Any hints or additional information I should provide to troubleshoot this? Hi Yuri, If I remember correctly, the problem came from the sbp driver (SCSI over firewire). Can't tell why it happens though, as I didn't need it I just disabled it. Regards, Olivier ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: `panic: run_interrupt_driven_config_hooks: waited too long' on HP DV8
On Mon, Mar 14, 2011 at 11:14:31AM +0100, Olivier Houchard wrote: On Mon, Mar 14, 2011 at 02:01:38AM +0300, Yuri Pankov wrote: Hi, I'm getting the following panic trying to boot March 5 snapshot on HP Pavilion DV8 notebook (8.2-RELEASE GENERIC kernel seems to boot on the same hardware just fine): run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config panic: run_interrupt_driven_config_hooks: waited too long cpuid = 0 KDB: enter: panic [ thread pid 0 tid 10 ] Stopped at kdb_enter+03xb: movq$0,0x800ab2(%rip) db bt Tracing pid 0 tid 10 td 0x80ee83e30 kdb_enter() at kdb_enter+0x3b panic() at panic+0x180 boot_run_interrupt_driven_config_hooks() at boot_run_interrupt_driven_config_hooks+0xb3 mi_startup() at mi_startup+0x77 btext() at btext+0x2c Any hints or additional information I should provide to troubleshoot this? Hi Yuri, If I remember correctly, the problem came from the sbp driver (SCSI over firewire). Can't tell why it happens though, as I didn't need it I just disabled it. Regards, Olivier Indeed, disabling sbp helped. Thanks, Olivier! Yuri ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: `panic: run_interrupt_driven_config_hooks: waited too long' on HP DV8
This usually has to do with a hung SCSI command. That this is a notebook indicates to me that it's possibly a USB device. A boot -v with 8.2RELEASE and then a boot -v with this snapshot might tell us what's up. Hi, I'm getting the following panic trying to boot March 5 snapshot on HP Pavilion DV8 notebook (8.2-RELEASE GENERIC kernel seems to boot on the same hardware just fine): run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config panic: run_interrupt_driven_config_hooks: waited too long cpuid = 0 KDB: enter: panic [ thread pid 0 tid 10 ] Stopped at kdb_enter+03xb: movq$0,0x800ab2(%rip) db bt Tracing pid 0 tid 10 td 0x80ee83e30 kdb_enter() at kdb_enter+0x3b panic() at panic+0x180 boot_run_interrupt_driven_config_hooks() at boot_run_interrupt_driven_config_hooks+0xb3 mi_startup() at mi_startup+0x77 btext() at btext+0x2c Any hints or additional information I should provide to troubleshoot this? TIA, Yuri ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: `panic: run_interrupt_driven_config_hooks: waited too long' on HP DV8
On Mon, Mar 14, 2011 at 02:01:38AM +0300, Yuri Pankov wrote: Hi, I'm getting the following panic trying to boot March 5 snapshot on HP Pavilion DV8 notebook (8.2-RELEASE GENERIC kernel seems to boot on the same hardware just fine): run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config run_interrupt_driven_hooks: still waiting after 300 seconds for xpt_config panic: run_interrupt_driven_config_hooks: waited too long cpuid = 0 KDB: enter: panic [ thread pid 0 tid 10 ] Stopped atkdb_enter+03xb: movq$0,0x800ab2(%rip) db bt Tracing pid 0 tid 10 td 0x80ee83e30 kdb_enter() at kdb_enter+0x3b panic() at panic+0x180 boot_run_interrupt_driven_config_hooks() at boot_run_interrupt_driven_config_hooks+0xb3 mi_startup() at mi_startup+0x77 btext() at btext+0x2c Any hints or additional information I should provide to troubleshoot this? Not sure if these are useful: http://darklight.org.ru/misc/dv8.dmesg.boot http://darklight.org.ru/misc/dv8.pciconf Yuri ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: `panic: run_interrupt_driven_config_hooks: waited too long' on HP DV8
Yes they are. The full messages from the failed boot would be helpful. Looks like we have ATA in CAM now, so it's possible that the disk reset failed, etc... Not sure if these are useful: http://darklight.org.ru/misc/dv8.dmesg.boot http://darklight.org.ru/misc/dv8.pciconf Yuri ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: `panic: run_interrupt_driven_config_hooks: waited too long' on HP DV8
On Sun, Mar 13, 2011 at 04:41:58PM -0700, Matthew Jacob wrote: Yes they are. The full messages from the failed boot would be helpful. Looks like we have ATA in CAM now, so it's possible that the disk reset failed, etc... What are my options for saving the output from failed boot other than handtyping it (no serial ports, no serial USB adapters)? Not sure if these are useful: http://darklight.org.ru/misc/dv8.dmesg.boot http://darklight.org.ru/misc/dv8.pciconf Yuri ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: `panic: run_interrupt_driven_config_hooks: waited too long' on HP DV8
On 3/13/2011 5:03 PM, Yuri Pankov wrote: On Sun, Mar 13, 2011 at 04:41:58PM -0700, Matthew Jacob wrote: Yes they are. The full messages from the failed boot would be helpful. Looks like we have ATA in CAM now, so it's possible that the disk reset failed, etc... What are my options for saving the output from failed boot other than handtyping it (no serial ports, no serial USB adapters)? None that I can think of :-( ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
