2.6.20 SATA error
hello, Can someone tell me what this means? ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x40 action 0x2 frozen ata1.00: cmd 35/00:00:40:a6:23/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288 out res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) ata1: port is slow to respond, please be patient (Status 0xd0) ata1: port failed to respond (30 secs, Status 0xd0) ata1: soft resetting port ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: configured for UDMA/100 ata1: EH complete SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA -- Gerhard Mack [EMAIL PROTECTED] <>< As a computer I find your faith in technology amusing. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20 SATA error
On Wed, 28 Feb 2007, Robert Hancock wrote: > Gerhard Mack wrote: > > hello, > > Can someone tell me what this means? > > ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x40 action 0x2 frozen > > ata1.00: cmd 35/00:00:40:a6:23/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288 > > out > > res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > > ata1: port is slow to respond, please be patient (Status 0xd0) > > ata1: port failed to respond (30 secs, Status 0xd0) > > ata1: soft resetting port > > ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > > ata1.00: configured for UDMA/100 > > ata1: EH complete > > SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) > > sda: Write Protect is off > > sda: Mode Sense: 00 3a 00 00 > > SCSI device sda: write cache: enabled, read cache: enabled, doesn't support > > DPO > > or FUA > > Some command timed out, apparently. From this one can't easily say why. Please > send full dmesg. > Linux version 2.6.20 ([EMAIL PROTECTED]) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #10 SMP PREEMPT Mon Feb 26 14:48:53 EST 2007 Command line: root=/dev/sda3 ro BIOS-provided physical RAM map: BIOS-e820: - 0009f000 (usable) BIOS-e820: 0009f000 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 3def (usable) BIOS-e820: 3def - 3def3000 (ACPI NVS) BIOS-e820: 3def3000 - 3df0 (ACPI data) BIOS-e820: 3e00 - 4000 (reserved) BIOS-e820: e000 - f000 (reserved) BIOS-e820: fec0 - 0001 (reserved) Entering add_active_range(0, 0, 159) 0 entries of 256 used Entering add_active_range(0, 256, 253680) 1 entries of 256 used end_pfn_map = 1048576 DMI 2.4 present. ACPI: RSDP (v002 Nvidia) @ 0x000f7560 ACPI: XSDT (v001 Nvidia ASUSACPI 0x42302e31 AWRD 0x) @ 0x3def30c0 ACPI: FADT (v003 Nvidia ASUSACPI 0x42302e31 AWRD 0x) @ 0x3defb3c0 ACPI: SSDT (v001 PTLTD POWERNOW 0x0001 LTP 0x0001) @ 0x3defb5c0 ACPI: HPET (v001 Nvidia ASUSACPI 0x42302e31 AWRD 0x0098) @ 0x3defb840 ACPI: MCFG (v001 Nvidia ASUSACPI 0x42302e31 AWRD 0x) @ 0x3defb8c0 ACPI: MADT (v001 Nvidia ASUSACPI 0x42302e31 AWRD 0x) @ 0x3defb500 ACPI: DSDT (v001 NVIDIA ASUSACPI 0x1000 MSFT 0x010e) @ 0x Entering add_active_range(0, 0, 159) 0 entries of 256 used Entering add_active_range(0, 256, 253680) 1 entries of 256 used Zone PFN ranges: DMA 0 -> 4096 DMA324096 -> 1048576 Normal1048576 -> 1048576 early_node_map[2] active PFN ranges 0:0 -> 159 0: 256 -> 253680 On node 0 totalpages: 253583 DMA zone: 56 pages used for memmap DMA zone: 1831 pages reserved DMA zone: 2112 pages, LIFO batch:0 DMA32 zone: 3412 pages used for memmap DMA32 zone: 246172 pages, LIFO batch:31 Normal zone: 0 pages used for memmap ACPI: PM-Timer IO Port: 0x4008 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 (Bootup-CPU) ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) Processor #1 ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: INT_SRC_OVR (bus 0 bus_irq 14 global_irq 14 high edge) ACPI: INT_SRC_OVR (bus 0 bus_irq 15 global_irq 15 high edge) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. ACPI: IRQ14 used by override. ACPI: IRQ15 used by override. Setting APIC routing to flat ACPI: HPET id: 0x10de8201 base: 0xfefff000 Using ACPI (MADT) for SMP configuration information Nosave address range: 0009f000 - 000a Nosave address range: 000a - 000f Nosave address range: 000f - 0010 Allocating PCI resources starting at 5000 (gap: 4000:a000) PERCPU: Allocating 33152 bytes of per cpu data Built 1 zonelists. Total pages: 248284 Kernel command line: root=/dev/sda3 ro Initializing CPU#0 PID hash table entries: 4096 (order: 12, 32768 bytes) Console: colour VGA+ 80x25 Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes) Inode-cache hash table entries: 65536 (order: 7, 524288 bytes) Checking aperture... CPU 0: aperture @ fa9c00 size 32 MB Aperture too small (32 MB) No AGP bridge found Memory: 991204k/1014720k available (3834k kernel code, 22888k reserved, 2637k data, 256k init) Calibrating delay using timer specific routine.. 4413.54 BogoMIPS (lpj=2206772) Security Framework v1.0.0 initialized Capability LSM initialized Failure register
Re: 2.6.20 SATA error
Gerhard Mack wrote: hello, Can someone tell me what this means? ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x40 action 0x2 frozen ata1.00: cmd 35/00:00:40:a6:23/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288 out res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) ata1: port is slow to respond, please be patient (Status 0xd0) ata1: port failed to respond (30 secs, Status 0xd0) ata1: soft resetting port ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: configured for UDMA/100 ata1: EH complete SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB) sda: Write Protect is off sda: Mode Sense: 00 3a 00 00 SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA Some command timed out, apparently. From this one can't easily say why. Please send full dmesg. -- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [EMAIL PROTECTED] Home Page: http://www.roberthancock.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20 SATA error
Gerhard Mack wrote: ata1.00: configured for UDMA/100 [...] ata1.00: configured for UDMA/66 [...] ata1.00: configured for UDMA/44 [...] ata1.00: configured for UDMA/33 [...] ata1.00: configured for UDMA/25 [...] ata1.00: configured for UDMA/16 [...] ata1.00: configured for PIO4 I have the same problem, though it appears randomly. It seems like the chances for this happening are bigger if I do heavy disk I/O. The only way to fix that is to shut down the computer and wait a few seconds before rebooting (if I don't wait, the problem doesn't go away). I bought new harddrives, so it's most likely not caused by the drives, I also tried putting the drives onto a different controller (I have four on-board SATA controller and two harddrives), that didn't help either, so I suspect its the cable - SATA cables are very error-prone, I don't trust them as they don't hold that tightly in the socket. tom - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20 SATA error
On Wed, 28 Feb 2007, Tomas Carnecky wrote: > Gerhard Mack wrote: > > ata1.00: configured for UDMA/100 > > [...] > > ata1.00: configured for UDMA/66 > > [...] > > ata1.00: configured for UDMA/44 > > [...] > > ata1.00: configured for UDMA/33 > > [...] > > ata1.00: configured for UDMA/25 > > [...] > > ata1.00: configured for UDMA/16 > > [...] > > ata1.00: configured for PIO4 > > I have the same problem, though it appears randomly. It seems like the chances > for this happening are bigger if I do heavy disk I/O. The only way to fix that > is to shut down the computer and wait a few seconds before rebooting (if I > don't wait, the problem doesn't go away). I bought new harddrives, so it's > most likely not caused by the drives, I also tried putting the drives onto a > different controller (I have four on-board SATA controller and two > harddrives), that didn't help either, so I suspect its the cable - SATA cables > are very error-prone, I don't trust them as they don't hold that tightly in Well that's the strange thing.. I've done heavy I/O on this with no trouble. This happened overnight when my system should have been mostly idle Gerhard -- Gerhard Mack [EMAIL PROTECTED] <>< As a computer I find your faith in technology amusing. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20 SATA error
Ralf Müller wrote: I had the same type of problem using an unstable power supply - after replacing it the problems were gone ... Hm.. my shuttle box has only a 350W power supply, that could indeed be the problem, as I have an Athlon 64 X2 4400+ CPU (dual core), two SATA-II 500GB harddrives and a GeForce 7800GTX. Damn.. I thought I payed attention to the power supply when I bought the components for my computer :( tom - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20 SATA error
On Wed, 28 Feb 2007 07:40:23 -0500 (EST) Gerhard Mack <[EMAIL PROTECTED]> wrote: > hello, > > Can someone tell me what this means? > ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x40 action 0x2 frozen > ata1.00: cmd 35/00:00:40:a6:23/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288 > out > res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > ata1: port is slow to respond, please be patient (Status 0xd0) > ata1: port failed to respond (30 secs, Status 0xd0) > ata1: soft resetting port > ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > ata1.00: configured for UDMA/100 I am fairly certain this is a bug in the 2.6.20 kernel. I never see it in 2.6.19*, just 2.6.20. It is some kind of but in the SATA code paths, or at least that's all it appears to affect on my system. What chipset do you have? I have an nforce4 chipset. In another thread, I think they were saying it was either a SATA chipset driver bug, or a problem in libata core. -- shannon | governorrhea: | a contagious disease that spreads from | the governor of a state downward through other | offices and his corporate sponsors - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20 SATA error
On Wed, 28 Feb 2007, Charles Shannon Hendrix wrote: > On Wed, 28 Feb 2007 07:40:23 -0500 (EST) > Gerhard Mack <[EMAIL PROTECTED]> wrote: > > > hello, > > > > Can someone tell me what this means? > > ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x40 action 0x2 frozen > > ata1.00: cmd 35/00:00:40:a6:23/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288 > > out > > res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) > > ata1: port is slow to respond, please be patient (Status 0xd0) > > ata1: port failed to respond (30 secs, Status 0xd0) > > ata1: soft resetting port > > ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > > ata1.00: configured for UDMA/100 > > I am fairly certain this is a bug in the 2.6.20 kernel. > > I never see it in 2.6.19*, just 2.6.20. > > It is some kind of but in the SATA code paths, or at least that's all it > appears to affect on my system. > > What chipset do you have? > > I have an nforce4 chipset. > > In another thread, I think they were saying it was either a SATA chipset > driver bug, or a problem in libata core. I also have an nforce4. Gerhard -- Gerhard Mack [EMAIL PROTECTED] <>< As a computer I find your faith in technology amusing. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20 SATA error
Charles Shannon Hendrix wrote: On Wed, 28 Feb 2007 07:40:23 -0500 (EST) Gerhard Mack <[EMAIL PROTECTED]> wrote: hello, Can someone tell me what this means? ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x40 action 0x2 frozen ata1.00: cmd 35/00:00:40:a6:23/00:04:00:00:00/e0 tag 0 cdb 0x0 data 524288 out res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) ata1: port is slow to respond, please be patient (Status 0xd0) ata1: port failed to respond (30 secs, Status 0xd0) ata1: soft resetting port ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) ata1.00: configured for UDMA/100 I am fairly certain this is a bug in the 2.6.20 kernel. I never see it in 2.6.19*, just 2.6.20. It is some kind of but in the SATA code paths, or at least that's all it appears to affect on my system. What chipset do you have? I have an nforce4 chipset. In another thread, I think they were saying it was either a SATA chipset driver bug, or a problem in libata core. There's a known issue with sata_nv on nForce4 controllers running in ADMA mode in 2.6.20 (the first released kernel with ADMA support) where commands can time out when switching between NCQ commands and non-NCQ commands. Hopefully this is fixed in 2.6.21-rc. This doesn't seem to be the issue here, since his system isn't using ADMA mode, for reasons unclear to me.. -- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [EMAIL PROTECTED] Home Page: http://www.roberthancock.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20 SATA error
On Wed, 28 Feb 2007, Robert Hancock wrote: > Gerhard Mack wrote: > > On Wed, 28 Feb 2007, Charles Shannon Hendrix wrote: > > > > > On Wed, 28 Feb 2007 13:25:00 -0500 (EST) > > > Gerhard Mack <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > In another thread, I think they were saying it was either a SATA > > > > > chipset > > > > > driver bug, or a problem in libata core. > > > > I also have an nforce4. > > > On another mailing list, someone with an Intel chipset is reporting the > > > same > > > problem, and also that others without nforce chipsets are seeing it. > > > > I was reaching inside my computer to check something and heared the thing > > click and got the same error message. > > > > Turns out the adaptor that goes between SATA drive and the old style power > > connector was loose on the drive side. Doesn't seem to me like it was very > > snug fitting to begin with. I changed it to one of the proper SATA > > connectors comming off the power supply and it doesn't do that anymore. > > > > Sorry for the false alarm, > > There is one thing that seems odd, if you do have an nForce4 chipset, the > kernel should be running the SATA controller in ADMA mode in 2.6.20, but it > doesn't seem like it is from your dmesg output. Can you post the output of > "lspci -vvn"? Also what kind of motherboard is that? > Sure thing. It's an Asus m2npv-vm. Gerhard mgerhard:/home/gmack# lspci -vvn 00:00.0 0500: 10de:02f0 (rev a2) Subsystem: 1043:81c0 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR+ TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- Reset- FastB2B- Capabilities: [40] Subsystem: 10de: Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable+ Address: fee0300c Data: 4141 Capabilities: [60] HyperTransport: MSI Mapping Capabilities: [80] Express Root Port (Slot+) IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s <512ns, L1 <4us Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ Device: MaxPayload 128 bytes, MaxReadReq 512 bytes Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 2 Link: Latency L0s <512ns, L1 <4us Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch- Link: Speed 2.5Gb/s, Width x1 Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug- Surpise- Slot: Number 0, PowerLimit 0.00 Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- Slot: AttnInd Off, PwrInd On, Power- Root: Correctable- Non-Fatal- Fatal- PME- Capabilities: [100] Virtual Channel 00:03.0 0604: 10de:02fd (rev a1) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- Reset- FastB2B- Capabilities: [40] Subsystem: 10de: Capabilities: [48] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1+,D2+,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [50] Message Signalled Interrupts: Mask- 64bit+ Queue=0/1 Enable+ Address: fee0300c Data: 4149 Capabilities: [60] HyperTransport: MSI Mapping Capabilities: [80] Express Root Port (Slot+) IRQ 0 Device: Supported: MaxPayload 128 bytes, PhantFunc 0, ExtTag- Device: Latency L0s <512ns, L1 <4us Device: Errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ Device: RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ Device: MaxPayload 128 bytes, MaxReadReq 512 bytes Link: Supported Speed 2.5Gb/s, Width x1, ASPM L0s L1, Port 1 Link: Latency L0s <512ns, L1 <4us Link: ASPM Disabled RCB 64 bytes CommClk- ExtSynch- Link: Speed 2.5Gb/s, Width x1 Slot: AtnBtn- PwrCtrl- MRL- AtnInd- PwrInd- HotPlug- Surpise- Slot: Number 0, PowerLimit 0.00 Slot: Enabled AtnBtn- PwrFlt- MRL- PresDet- CmdCplt- HPIrq- Slot: AttnInd Off, PwrInd On, Power- Root: Correctable- Non-Fatal- Fatal- PME- Capabilities: [100] Virtual Channel 00:04.0 0604: 10de
Re: 2.6.20 SATA error
Gerhard Mack wrote: Sorry for the false alarm, There is one thing that seems odd, if you do have an nForce4 chipset, the kernel should be running the SATA controller in ADMA mode in 2.6.20, but it doesn't seem like it is from your dmesg output. Can you post the output of "lspci -vvn"? Also what kind of motherboard is that? Sure thing. It's an Asus m2npv-vm. Ah, that would be why, it's not one of the original nForce4 (CK804/MCP04) chipsets, it's the newer nForce 430 (MCP51) chipset which doesn't support ADMA. NVidia said they'd be sending some patches to allow NCQ support on MCP51 and MCP61 chipsets back in October, but I haven't seen any, or information required to implement same.. -- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [EMAIL PROTECTED] Home Page: http://www.roberthancock.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20 SATA error
On Wed, 28 Feb 2007, Robert Hancock wrote: > Date: Wed, 28 Feb 2007 18:21:48 -0600 > From: Robert Hancock <[EMAIL PROTECTED]> > To: Gerhard Mack <[EMAIL PROTECTED]> > Cc: linux-kernel , > Charles Shannon Hendrix <[EMAIL PROTECTED]> > Subject: Re: 2.6.20 SATA error > > Gerhard Mack wrote: > > > > Sorry for the false alarm, > > > There is one thing that seems odd, if you do have an nForce4 chipset, the > > > kernel should be running the SATA controller in ADMA mode in 2.6.20, but > > > it > > > doesn't seem like it is from your dmesg output. Can you post the output of > > > "lspci -vvn"? Also what kind of motherboard is that? > > > > > Sure thing. It's an Asus m2npv-vm. > > Ah, that would be why, it's not one of the original nForce4 (CK804/MCP04) > chipsets, it's the newer nForce 430 (MCP51) chipset which doesn't support > ADMA. NVidia said they'd be sending some patches to allow NCQ support on MCP51 > and MCP61 chipsets back in October, but I haven't seen any, or information > required to implement same.. fun stuff.. I guess it's back to trying to get the onboard ethernet card to work in debian. Gerhard -- Gerhard Mack [EMAIL PROTECTED] <>< As a computer I find your faith in technology amusing. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.6.20 SATA error
Tomas Carnecky wrote (ao): > Ralf M??ller wrote: > >I had the same type of problem using an unstable power supply - after > >replacing it the problems > >were gone ... > > Hm.. my shuttle box has only a 350W power supply, that could indeed be > the problem, as I have an Athlon 64 X2 4400+ CPU (dual core), two > SATA-II 500GB harddrives and a GeForce 7800GTX. > Damn.. I thought I payed attention to the power supply when I bought the > components for my computer :( FWIW, my system currently lurks around 300W from the outlet. This is including one 21" LCD (some 30W - 50W). System is a dual dual-core Opteron, 8x Raptor and 2x XFX 7950GT. Full pull it does a bit above 400W. If the PSU has 80% efficiency then it delivers around 320W to all components. I'm pretty sure your 350W PSU is adequate. With kind regards, Sander -- Humilis IT Services and Solutions http://www.humilis.net - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
solved Re: 2.6.20 SATA error
On Wed, 28 Feb 2007, Charles Shannon Hendrix wrote: > On Wed, 28 Feb 2007 13:25:00 -0500 (EST) > Gerhard Mack <[EMAIL PROTECTED]> wrote: > > > > > In another thread, I think they were saying it was either a SATA chipset > > > driver bug, or a problem in libata core. > > > > I also have an nforce4. > > On another mailing list, someone with an Intel chipset is reporting the same > problem, and also that others without nforce chipsets are seeing it. I was reaching inside my computer to check something and heared the thing click and got the same error message. Turns out the adaptor that goes between SATA drive and the old style power connector was loose on the drive side. Doesn't seem to me like it was very snug fitting to begin with. I changed it to one of the proper SATA connectors comming off the power supply and it doesn't do that anymore. Sorry for the false alarm, Gerhard -- Gerhard Mack [EMAIL PROTECTED] <>< As a computer I find your faith in technology amusing. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: solved Re: 2.6.20 SATA error
Gerhard Mack wrote: On Wed, 28 Feb 2007, Charles Shannon Hendrix wrote: On Wed, 28 Feb 2007 13:25:00 -0500 (EST) Gerhard Mack <[EMAIL PROTECTED]> wrote: In another thread, I think they were saying it was either a SATA chipset driver bug, or a problem in libata core. I also have an nforce4. On another mailing list, someone with an Intel chipset is reporting the same problem, and also that others without nforce chipsets are seeing it. I was reaching inside my computer to check something and heared the thing click and got the same error message. Turns out the adaptor that goes between SATA drive and the old style power connector was loose on the drive side. Doesn't seem to me like it was very snug fitting to begin with. I changed it to one of the proper SATA connectors comming off the power supply and it doesn't do that anymore. Sorry for the false alarm, There is one thing that seems odd, if you do have an nForce4 chipset, the kernel should be running the SATA controller in ADMA mode in 2.6.20, but it doesn't seem like it is from your dmesg output. Can you post the output of "lspci -vvn"? Also what kind of motherboard is that? -- Robert Hancock Saskatoon, SK, Canada To email, remove "nospam" from [EMAIL PROTECTED] Home Page: http://www.roberthancock.com/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
