Subject: Re: SATA Controllers Conflict
To: Manuel Bouyer <bouyer@antioche.eu.org>
From: the carlos <speed_daemon@the-carlos.net>
List: port-amd64
Date: 01/13/2007 21:48:40
lapic_delay() at netbsd:lapic_delay+0x36
bge_miibus_readreg() at netbsd:bge_miibus_readreg+0x7b
brgphy_status() at netbsd:brgphy_status+0x46
mii_phy_status() at netbsd:mii_phy_status+0xe
brgphy_service() at netbsd:brgphy_service+0x40
mii_phy_auto_timeout() at netbsd:mii_phy_auto_timeout+0x48
softclock() at netbsd:softclock+0x2c9
softintr_dispatch() at netbsd:softintr_dispatch+0x99
DDB lost frame for netbsd:Xsoftclock+0x2d, trying 0xffffffff80a2cd00
Xsoftclock() at netbsd:Xsoftclock+0x2d
--- interrupt ---
0x246:

That trace came out of the 3.1 recently patched DEBUG kernel...  What
does ddb.onpanic do?

<<carlos>>
<<nvllvmmagnvmingenivmsinemixtvradementiae>>

On Jan 13, 2007, at 4:28 PM, Manuel Bouyer wrote:

> On Fri, Jan 12, 2007 at 01:55:19AM -0500, the carlos wrote:
>> Greetings all.  Long-time reader, first time poster.
>>
>> I can't seem to get my Silicon Image SI-3114 sata controller
>> (satalink driver) to play nicely with the 3ware 9550SX-8-LP (twa) in
>> netbsd 3.1 amd64.  If I disable one or the other in the BIOS, the
>> lone device works fine*.  Everything works* in 3.0 (presumably
>> because there is no twa driver) and the 4.0beta LiveCD.  If both are
>> enabled under 3.1, I get a "fatal protection fault in supervisor
>> mode" hang, and the system reboots.
>>
>> My motherboard is a Tyan Thunder K8S-D Pro (S2882-D).
>>
>> with the recently patched 3.1 GENERIC kernel, I have a few moments to
>> capture dmesg, etc. before the following comes up.
>> with the recently patched 3.1 GENERIC.MP kernel, the following comes
>> up instantly, then reboots.
>>
>> fatal protection fault in supervisor mode
>> trap type 4 code 38b rip ffffffff8043e01b cs 8 rflags 10206 cr2
>> 52f000 cpl 7 rs
>> p ffff800046cabe00
>> panic: trap
>> syncing disks... satalink0:1:0: lost interrupt
>> 	type: ata tc_bcount: 16384 tc_skip: 0
>
> Do you have ddb compiled in your kernel, and ddb.onpanic set to 0 ?
> Having a stack trace from ddb would be usefull here.
>
> --
> Manuel Bouyer <bouyer@antioche.eu.org>
>      NetBSD: 26 ans d'experience feront toujours la difference
> --