Bug 136327 - [sbp] [boot] Asus M3N78-EM motherboard cannot boot with generic kernel.
Summary: [sbp] [boot] Asus M3N78-EM motherboard cannot boot with generic kernel.
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: 7.2-RELEASE
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords: crash
Depends on:
Blocks:
 
Reported: 2009-07-04 18:20 UTC by Chris
Modified: 2022-10-13 06:35 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris 2009-07-04 18:20:02 UTC
Motherboard will not boot with standard kernel, eg installation CD.

I'm trying to install on a new motherboard ASUS M3N78-EM. While booting from FreeBSD installation CD I'm getting

run_interrupts_driven_hooks: still waiting after 60 seconds for xpt_config

This is repeated a few times then installation stops and the machine stops responding.

I've tried various versions, including 6.4R, 7.0R 7.2R and
8.0-CURRENT-200905-i386-disc1.iso. I've also tried SATA mode and AHCI mode for the SATA controller.

I get a panic from the 8-CURRENT snapshot. The others might be panicking but I guess their standard kernel doesn't have debug stuff

Backtrace from 8-CURRENT (typed by hand).

panic: run_interrupt_driven_hooks: waited too long
cpuid=0
KDB: enter: panic
[thread pid 0 tid 100000 ]
stopped at   kdb_enter+0x3a: movl   $0,kdb_why
db> bt
Tracing pid 0 tid 100000 td 0xc0d88fd0
kdb_enter(c0c3d8cf,c0c3d8cf,c0c3feac,c1820d08,0,...) at kdb_enter+0x3a
panic(c0c3feac,0,c0c3fe43,70,ea60,...) at panic+0x136
run_interrupt_driven_config_hooks(0,181ec00,181ec00,181e000,1825000,...) at run_interrupt_driven_config_hooks+0x1c7
mi_startup() at mi_startup+0x96
begin()at begin+0x2c
db>

=============================================================

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>

Fix: 

Workaround:

Disable firewire in BIOS
Install from a standard CD
Reboot to hard disk
Build and install a custom kernel with device spb disabled
Reboot and enable firewire in the BIOS.

kldload sbp if required (I have tested that it loads, not whether it works.)
How-To-Repeat: Boot the motherboard with any of the standard kernels listed above.
Comment 1 Jaakko Heinonen freebsd_committer freebsd_triage 2011-11-11 19:48:49 UTC
State Changed
From-To: open->feedback

Can you still reproduce this on recent FreeBSD versions?
Comment 2 Jaakko Heinonen freebsd_committer freebsd_triage 2011-11-12 20:08:20 UTC
State Changed
From-To: feedback->open

Still a problem on 9.0-CURRENT. 


Comment 3 Jaakko Heinonen freebsd_committer freebsd_triage 2011-11-12 20:08:20 UTC
Responsible Changed
From-To: freebsd-bugs->freebsd-firewire

Reassign.
Comment 4 seanbru 2011-11-12 20:34:08 UTC
Can you put this machine up somewhere that I can get into it and have
root access?

This is a long standing issue with firewire that I'd like to fix if
possible.

Sean
Comment 5 Chris 2011-11-12 23:48:35 UTC
On 12/11/2011 20:34, Sean Bruno wrote:
> Can you put this machine up somewhere that I can get into it and have
> root access?
>
> This is a long standing issue with firewire that I'd like to fix if
> possible.
>
> Sean
>
>
I should be able to but I need to check as I don't own my internet 
connection. Also I need to set up a fresh install but that won't take long.

How would we arrange restarts since the machine needs to be physically 
turned off and turned on again after a hang and we are in different time 
zones? Best I can imagine is you would have to email me and I do it as 
soon as I receive it, which could be a while. Or would you be able to 
avoid restarts?

Chris
Comment 6 seanbru 2011-11-13 17:16:31 UTC
On Sat, 2011-11-12 at 15:48 -0800, Chris Whitehouse wrote:
> On 12/11/2011 20:34, Sean Bruno wrote:
> > Can you put this machine up somewhere that I can get into it and have
> > root access?
> >
> > This is a long standing issue with firewire that I'd like to fix if
> > possible.
> >
> > Sean
> >
> >
> I should be able to but I need to check as I don't own my internet 
> connection. Also I need to set up a fresh install but that won't take long.
> 
> How would we arrange restarts since the machine needs to be physically 
> turned off and turned on again after a hang and we are in different time 
> zones? Best I can imagine is you would have to email me and I do it as 
> soon as I receive it, which could be a while. Or would you be able to 
> avoid restarts?
> 
> Chris

Well, I was going to try and use a kernel without sbp and load sbp as a
kmod.  I had hoped that I could get a serial console on it as well, but
I'd like to see what the machine is like first.

Sean
Comment 7 Chris 2011-11-13 21:16:57 UTC
On 13/11/2011 17:16, Sean Bruno wrote:
> On Sat, 2011-11-12 at 15:48 -0800, Chris Whitehouse wrote:
>> On 12/11/2011 20:34, Sean Bruno wrote:
>>> Can you put this machine up somewhere that I can get into it and have
>>> root access?
>>>
>>> This is a long standing issue with firewire that I'd like to fix if
>>> possible.
>>>
>>> Sean
>>>
>>>
>> I should be able to but I need to check as I don't own my internet
>> connection. Also I need to set up a fresh install but that won't take long.
>>
>> How would we arrange restarts since the machine needs to be physically
>> turned off and turned on again after a hang and we are in different time
>> zones? Best I can imagine is you would have to email me and I do it as
>> soon as I receive it, which could be a while. Or would you be able to
>> avoid restarts?
>>
>> Chris
>
> Well, I was going to try and use a kernel without sbp and load sbp as a
> kmod.  I had hoped that I could get a serial console on it as well, but
> I'd like to see what the machine is like first.
>
> Sean
>
>
Hi,

should be up now, I'm sending details offlist.

Firewire is enabled in BIOS and I rebuilt the kernel with device sbp 
disabled.

#kldload sbp
seems to work, as in it loads and doesn't crash the machine but I don't 
have any devices to hand to test further than that.

Chris
Comment 8 seanbru 2011-11-15 00:27:49 UTC
Can you post the very verbose version of pciconf?

also, can you post the output when loading sbp.ko and the dmesg from the
box?

Sean
Comment 9 Chris 2011-11-15 11:46:33 UTC
On 15/11/2011 00:27, Sean Bruno wrote:
> Can you post the very verbose version of pciconf?
>
> also, can you post the output when loading sbp.ko and the dmesg from the
> box?
>
> Sean
>
>
http://www.fishercroft.plus.com

dmesg_-a.txt is dmesg -a

pciconf_-lv.txt is pciconf -lv

#kldload sbp
#tail -2 /var/log/messages
Nov 15 11:29:09 sbpi386 su: chrisw to root on /dev/pts/0
Nov 15 11:31:43 sbpi386 kernel: sbp0: <SBP-2/SCSI over FireWire> on 
firewire0

cheers

Chris
Comment 10 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 08:00:38 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped