Re: nForce 4, SATA Drive only runs at UDMA33?

--- Søren Schmidt <sos_at_freebsd.org> wrote:
> >> Yes, I've done quite a bit of changes that
affects
> >> this on -current.
> >> However its done blindfolded since I dont have a
> >> nForce4 based system
> >> here yet (but should soon).
> >>
> >> - Søren

> OK, let me know, I'll be away from mail Thurday to
> Sunday, so if I  
> dont respond as quickly as usual you know why...
> 
> - Søren

Here's the results from -Current:

atapici0: <nVidia nForce4 UDMA133 controller> port
0x1f0-0x1f7, 0x3f6, 0x170-0x177, 0x376, 0xf000-0xf00f
at device 6.0 on pci0
ata0: <ATA channel 0> on atapici0
ata1: <ATA channel 1> on atapici0

atapici1: <nVidia nForce4 SATA150 controller> port
0x9f0-0x9f7, 0xbf0-0xbf3, 0x970-0x977, 0xb70-0xb73,
0xd800-0xd80f mem 0xd8102000-0xd8102fff irq 23 at
device 7.0 on pci0
ata2: <ATA channel 0> on atapici1
ata3: <ATA channel 1> on atapici1

atapici2: <nVidia nForce4 SATA150 controller> port
0x9e0-0x9e7, 0xbe0-0xbe3, 0x960-0x967, 0xb60-0xb63,
0xc400-0xc40f mem 0xd8101000-0xd8101fff irq 21 at
device 8.0 on pci0
ata4: <ATA channel 0> on atapici2
ata5: <ATA channel 1> on atapici2

pcib1: <ACPI PCI-PCI bridge> at device 9.0 on pci0
pci_link19: BIOS IRQ 23 for 0.7.INTA is invalid

And it IS still doing the ATTACH/DETACH repeating
thing as earlier.  A bit later in the bootup process
(after the above) it panics.  The good news is that
everything seems to be detected now but the bad is
that it still dies.  

Does this help at all?  I'm confused by the IRQ23 is
invalid statement, not sure what that means.  If
there's anything else I can do or data I can provide
to help get this figured out please let me know.  I
now have a spare SATA disk I can swap to try out
things so I don't have to worry about messing up my
system anymore.

--Alan


		
__________________________________ 
Discover Yahoo! 
Get on-the-go sports scores, stock quotes, news and more. Check it out! 
http://discover.yahoo.com/mobile.html