Re: satalink at cardbus

[KIYOHARA Takashi <kiyohara%kk.iij4u.or.jp@localhost>]

Hi! Tom,


From: Tom Spindler <dogcow%babymeat.com@localhost>
Date: Wed, 6 Aug 2008 05:11:15 -0700

> OK, I've found something a little disturbing: when the card is
> inserted after the system boots up, everything is fine. If the card
> is present at boot time, however, I get an NMI and a drop into the
> debugger. If I continue, then everything works as mostly normal - but
> there's sometimes a hang during reboot.
> 
> Sounds like the interrupts are wrong somewhere?

> satalink0 at cardbus0 function 0
> satalink0: Silicon Image SATALink 3512 (rev. 0x01)
> satalink0: SATALink BA5 register space enabled
> cardbus_mapreg_map called: cardbus0 0
> cardbus_mapreg_map: physaddr 40000000
> satalink0: bus-master DMA support presentcardbus_mapreg_map called: cardbus0 1
> cardbus_mapreg_map: physaddr 4300
> 
> satalink0: primary channel wired to native-PCI mode
> cardbus_mapreg_map called: cardbus0 1
> cardbus_mapreg_map: physaddr 4700
> cardbus_mapreg_map called: cardbus0 1
> cardbus_mapreg_map: physaddr 4b00
> atabus2 at satalink0 channel 0
> satalink0: secondary channel wired to native-PCI mode
> cardbus_mapreg_map called: cardbus0 1
> cardbus_mapreg_map: physaddr 4f00
> cardbus_mapreg_map called: cardbus0 1
> cardbus_mapreg_map: physaddr 5300
> atabus3 at satalink0 channel 1
> satalink0: port 0: device present, speed: 1.5Gb/s

> wd1 at atabus2 drive 0: <ST3750640AS>
> wd1: quirks 2<FORCE_LBA48>
> wd1: drive supports 16-sector PIO transfers, LBA48 addressing
> wd1: 698 GB, 1453521 cyl, 16 head, 63 sec, 512 bytes/sect x 1465149168 sectors
> wd1: 32-bit data port
> wd1: drive supports PIO mode 4, DMA mode 2, Ultra-DMA mode 6 (Ultra/133)
> wd1(satalink0:0:0): using PIO mode 4, Ultra-DMA mode 6 (Ultra/133) (using DMA)

> NMI ... going to debugger
> Stopped in pid 0.2 (system) at  netbsd:x86_stihlt+0x5:  leave
> db{0}> bt
> x86_stihlt(ca287be0,0,c0257ed7,ca287be0,0,0,c046e7c8,ca287be0,c0250e00,ca287be0)
>  at netbsd:x86_stihlt+0x5
> idle_loop(ca287be0,0k,c01002cd,0,c01002cd,0,0,0,0,0) at netbsd:idle_loop+0x176
> db{0}> c
> boot device: wd0

hmm...
I do not understand the cause of NMI.  Will you see this problem when
there is no satalink?

Thanks,
--
kiyohara