Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 17 May 2009 21:06:06 +0100
From:      Chris Whitehouse <cwhiteh@onetel.com>
To:        FreeBSD Questions <questions@freebsd.org>
Subject:   Re: run_interrupt_driven_hooks: still waiting... for xpt_config
Message-ID:  <4A106E2E.9040807@onetel.com>
In-Reply-To: <4A0F457F.6010606@onetel.com>
References:  <4A0F457F.6010606@onetel.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Chris Whitehouse wrote:

> 
> I can build a debug kernel on 7.2R or any recommended version onto a 
> spare hard disk and use it to boot this machine to get debugging info.
> 
> Much thanks
> 
> Chris
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to 
> "freebsd-questions-unsubscribe@freebsd.org"
> 

Well I've got 7.2R booting on this motherboard so I guess it's safe to 
keep it.

After some trial and error the problem seems to be device sbp in the 
kernel config file. Comment that out and rebuild kernel and it boots.

Here's a backtrace from 7.2R using a GENERIC kernel (with sbp enabled) 
with debug options added.

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 0 ]
stopped at   kdb_enter_why+0x3a:    movl   $0,kdb_why
db> bt
Tracing pid 0 tid 0 td 0xc0cc1b40
kdb_enter_why(c0b87110,c0b87110,c0b89425,c1020d0c,0,...) at
kdb_enter_why+0x3a
panic(c0b89425,0,c0b893c0,71,ea60,...) at panic+0x136
run_interrupt_driven_config_hooks(0,101ec00,101ec00,101e000,1025000,...)
at run_interrupt_driven_config_hooks+0x1b7
mi_startup() at mi_startup+0x96
begin()at begin+0x2c
db>

Chris




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4A106E2E.9040807>