freebsd stable - May 2006 - SATA Failure Introduced between 6.0 and 6.1-RC1

Hi -stable!

I'd like to bring something to the attention of -stable that was posted 
to -amd64 but has not yet being resolved:

http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/95554

I'm unable to test to see if this occurs on i386 aswell so am unsure if 
this is the right list to post to. But it appears to me that it would be 
something that should be addressed prior to 6.1-RELEASE.

I am experiencing the same problem as described in the original PR, but 
with Western Digital hard drives and the latest  BIOS version (1001) 
which is known to fix the ACPI DSDT bugs that have plagued these boards.

I have not liased with the mailling lists before if you need any more 
information please ask and I'll supply what I can as best I can. But the 
original PR is well written.

I will also see if RC-2 resolves this when cvsup has RC2 and I can build 
an RC2 world/kernel.

Cheers
and Thanks for a great operating system

Jared

Just a follow up.

-RC2 did not resolve this problem, nor did 6.1-STABLE (as of around 8hrs 
ago).

I am eager to work with the community in resolving these issues.

I have applied the patches described at:

http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/nve/if_nve.c.diff?r1=1.18&r2=1.19&f=h
and
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/dev/nve/if_nvereg.h.diff?r1=1.6&r2=1.7&f=h

in order to get the Onboard ethernet to work. These problems exist even 
without applying that patch however.

Below is a dmesg and uname of an affected machine:

Cheers
J



[jared@aoi ~]$ dmesg
Copyright (c) 1992-2006 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
         The Regents of the University of California. All rights reserved.
FreeBSD 6.1-STABLE #1: Mon May  8 11:49:24 EST 2006
     root@aoi:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: AMD Athlon(tm) 64 Processor 3700+ (2210.07-MHz K8-class CPU)
   Origin = "AuthenticAMD"  Id = 0x30f72  Stepping = 2
 
Features=0x78bfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2>
   Features2=0x1<SSE3>
   AMD Features=0xe2500800<SYSCALL,NX,MMX+,FFXSR,LM,3DNow+,3DNow>
   AMD Features2=0x1<LAHF>
real memory  = 1056702464 (1007 MB)
avail memory = 1008156672 (961 MB)
kbd1 at kbdmux0
acpi0: <A M I OEMRSDT> on motherboard
acpi0: Power Button (fixed)
Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x508-0x50b on acpi0
cpu0: <ACPI CPU> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pci0: <memory, RAM> at device 0.0 (no driver attached)
pci0: <memory, RAM> at device 0.1 (no driver attached)
pci0: <memory, RAM> at device 0.2 (no driver attached)
pci0: <memory, RAM> at device 0.3 (no driver attached)
pci0: <memory, RAM> at device 0.4 (no driver attached)
pci0: <memory, RAM> at device 0.5 (no driver attached)
pci0: <memory, RAM> at device 0.6 (no driver attached)
pci0: <memory, RAM> at device 0.7 (no driver attached)
pcib1: <ACPI PCI-PCI bridge> at device 2.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> at device 3.0 on pci0
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> at device 4.0 on pci0
pci3: <ACPI PCI bus> on pcib3
pci0: <display, VGA> at device 5.0 (no driver attached)
pci0: <memory, RAM> at device 9.0 (no driver attached)
isab0: <PCI-ISA bridge> at device 10.0 on pci0
isa0: <ISA bus> on isab0
pci0: <serial bus, SMBus> at device 10.1 (no driver attached)
ohci0: <OHCI (generic) USB controller> mem 0xfebde000-0xfebdefff irq 5 
at device 11.0 on pci0
ohci0: [GIANT-LOCKED]
usb0: OHCI version 1.0, legacy support
usb0: SMM does not respond, resetting
usb0: <OHCI (generic) USB controller> on ohci0
usb0: USB revision 1.0
uhub0: nVidia OHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 8 ports with 8 removable, self powered
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xfebdfc00-0xfebdfcff irq 
7 at device 11.1 on pci0
ehci0: [GIANT-LOCKED]
usb1: EHCI version 1.0
usb1: companion controller, 8 ports each: usb0
usb1: <EHCI (generic) USB 2.0 controller> on ehci0
usb1: USB revision 2.0
uhub1: nVidia EHCI root hub, class 9/0, rev 2.00/1.00, addr 1
uhub1: 8 ports with 8 removable, self powered
atapci0: <nVidia nForce MCP51 UDMA133 controller> port 
0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 13.0 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
atapci1: <nVidia nForce MCP51 SATA300 controller> port 
0xe800-0xe807,0xe480-0xe483,0xe400-0xe407,0xe080-0xe083,0xe000-0xe00f 
mem 0xfebdd000-0xfebddfff irq 11 at device 14.0 on pci0
ata2: <ATA channel 0> on atapci1
ata3: <ATA channel 1> on atapci1
atapci2: <nVidia nForce MCP51 SATA300 controller> port 
0xdc00-0xdc07,0xd880-0xd883,0xd800-0xd807,0xd480-0xd483,0xd400-0xd40f 
mem 0xfebdc000-0xfebdcfff irq 10 at device 15.0 on pci0
ata4: <ATA channel 0> on atapci2
ata5: <ATA channel 1> on atapci2
pcib4: <ACPI PCI-PCI bridge> at device 16.0 on pci0
pci4: <ACPI PCI bus> on pcib4
nve0: <NVIDIA nForce MCP13 Networking Adapter> port 0xd080-0xd087 mem 
0xfebdb000-0xfebdbfff irq 7 at device 20.0 on pci0
nve0: Ethernet address 00:15:f2:5e:58:09
miibus0: <MII bus> on nve0
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-FDX, auto
nve0: Ethernet address: 00:15:f2:5e:58:09
acpi_button0: <Power Button> on acpi0
fdc0: <floppy drive controller (FDE)> port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 
on acpi0
fdc0: [FAST]
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: [GIANT-LOCKED]
psm0: model IntelliMouse Explorer, device ID 4
ppc0: cannot reserve I/O port range
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0: configured irq 4 not in bitmap of probed irqs 0
sio0: port may not be enabled
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 8250 or not responding
sio1: configured irq 3 not in bitmap of probed irqs 0
sio1: port may not be enabled
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
ugen0: Powerware Powerware UPS, rev 0.20/0.50, addr 2
Timecounter "TSC" frequency 2210072188 Hz quality 800
Timecounters tick every 1.000 msec
module_register_init: MOD_LOAD (amr_linux, 0xffffffff806205d0, 0) error 6
ad0: 152627MB <WDC WD1600SB-01KBC0 08.02D08> at ata0-master UDMA100
ad1: 152627MB <WDC WD1600SB-01KBC0 08.02D08> at ata0-slave UDMA100
ad4: 238475MB <WDC WD2500KS-00MJB0 02.01C03> at ata2-master SATA300
GEOM_MIRROR: Device gm0 created (id=124972809).
GEOM_MIRROR: Device gm0: provider ad0 detected.
GEOM_MIRROR: Device gm0: provider ad1 detected.
GEOM_MIRROR: Device gm0: provider ad1 activated.
GEOM_MIRROR: Device gm0: provider ad0 activated.
GEOM_MIRROR: Device gm0: provider mirror/gm0 launched.
ad8: 238475MB <WDC WD2500KS-00MJB0 02.01C03> at ata4-master SATA300
Trying to mount root from ufs:/dev/mirror/gm0s1a
nve0: device timeout (1)
nve0: link state changed to DOWN
nve0: link state changed to UP

[jared@aoi ~]$ uname -a
FreeBSD aoi 6.1-STABLE FreeBSD 6.1-STABLE #1: Mon May  8 11:49:24 EST 
2006     root@aoi:/usr/obj/usr/src/sys/GENERIC  amd64



Jared wrote:
> Hi -stable!
> 
> I'd like to bring something to the attention of -stable that was posted
> to -amd64 but has not yet being resolved:
> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/95554
> 
> I'm unable to test to see if this occurs on i386 aswell so am unsure if
> this is the right list to post to. But it appears to me that it would be 
> something that should be addressed prior to 6.1-RELEASE.
> 
> I am experiencing the same problem as described in the original PR, but 
> with Western Digital hard drives and the latest  BIOS version (1001) 
> which is known to fix the ACPI DSDT bugs that have plagued these boards.
> 
> I have not liased with the mailling lists before if you need any more 
> information please ask and I'll supply what I can as best I can. But
the
> original PR is well written.
> 
> I will also see if RC-2 resolves this when cvsup has RC2 and I can build 
> an RC2 world/kernel.
> 
> Cheers
> and Thanks for a great operating system
> 
> Jared
> 
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to
"freebsd-stable-unsubscribe@freebsd.org"

Jared wrote:
> Hi -stable!
> 
> I'd like to bring something to the attention of -stable that was posted
> to -amd64 but has not yet being resolved:
> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=amd64/95554
> 
> I'm unable to test to see if this occurs on i386 aswell so am unsure if
> this is the right list to post to. But it appears to me that it would be 
> something that should be addressed prior to 6.1-RELEASE.
Hi all. This does indeed occur on i386 also. I had a drive die in a 
machine this past week and replaced it with two brand new Seagate 80GB 
SATA 300 drives to do mirroring, but 6.1-RELEASE only detects one of the 
drives (and only the one on the primary SATA channel even if I switch 
them around).

Upon finding this PR, I tried 6.0-RELEASE and it detected both drives on 
the install, so I went ahead and installed 6.0 to use until there is a 
fix since this is a production workstation. Unfortunately, I forgot that 
I was running 6.1-PRERELEASE on the previous install because none of the 
controllers on my board (MSI K8NGM2 - nForce4) are detected in 6.0, and 
instead run as "GENERIC" at UDMA33.

I don't have the latest BIOS since it requires Windows to update, but 
the summary for all updates show mainly CPU things...nothing related to 
ATA/SATA/RAID.

I'm trying to decide if I should use 6.0 with the "GENERIC"
controller
and reduced speeds since it needs to be operational, or try the nve 
patches to fix the onboard LAN so I can free up a PCI slot and then put 
in a known working SATA controller that would be recognized and at full 
speeds. Not meant as pressure in any to the developers, but I'm 
wondering if you guys think it will be a while before this is fixed so I 
can make an informed decision on hardware purchases or not and get this 
machine back up.

Thanks in advance!

-Mark
> I am experiencing the same problem as described in the original PR, but 
> with Western Digital hard drives and the latest  BIOS version (1001) 
> which is known to fix the ACPI DSDT bugs that have plagued these boards.
> 
> I have not liased with the mailling lists before if you need any more 
> information please ask and I'll supply what I can as best I can. But
the
> original PR is well written.
> 
> I will also see if RC-2 resolves this when cvsup has RC2 and I can build 
> an RC2 world/kernel.
> 
> Cheers
> and Thanks for a great operating system
> 
> Jared
> 
> _______________________________________________
> freebsd-stable@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to
"freebsd-stable-unsubscribe@freebsd.org"
> 
> 
> 

-- 
GnuPG Public Key:
http://www.mkproductions.org/mk_pubkey.asc

Internet Radio:
Party107 (Trance/Electronic) - http://www.party107.com
Rock 101.9 The Edge (Rock) - http://www.rock1019.net

IRC:
MIXXnet IRC Network - irc.mixxnet.net (Nick: MIXX941)