Am Thu, 16 Aug 2007 19:53:35 +0900
schrieb Tejun Heo <[EMAIL PROTECTED]>:
> I don't think this is driver issue. I have the same controller and
> I've never seen similar thing happening and I have plenty of drives
> and test them often. Error reports also point to transmission
> problems. Your
Andreas Radke wrote:
[on ahci]
> Aug 13 18:00:33 workstation64 ata1.00: exception Emask 0x10 SAct 0x0 SErr
> 0x400101 action 0x2 frozen
> Aug 13 18:00:33 workstation64 ata1.00: (irq_stat 0x0800, interface fatal
> error)
> Aug 13 18:00:33 workstation64 ata1.00: cmd
>
Andreas Radke wrote:
[on ahci]
Aug 13 18:00:33 workstation64 ata1.00: exception Emask 0x10 SAct 0x0 SErr
0x400101 action 0x2 frozen
Aug 13 18:00:33 workstation64 ata1.00: (irq_stat 0x0800, interface fatal
error)
Aug 13 18:00:33 workstation64 ata1.00: cmd
Am Thu, 16 Aug 2007 19:53:35 +0900
schrieb Tejun Heo [EMAIL PROTECTED]:
I don't think this is driver issue. I have the same controller and
I've never seen similar thing happening and I have plenty of drives
and test them often. Error reports also point to transmission
problems. Your drive
Andreas Radke wrote:
> already tried different ports, several SATA cables on that mainboard and
> psu works well. the Samsung drive works well no matter where
> connected. never had any issues with the Raptor drive when it was
> connected to the "old" Intel P965 board before. what's the difference
Andreas Radke wrote:
already tried different ports, several SATA cables on that mainboard and
psu works well. the Samsung drive works well no matter where
connected. never had any issues with the Raptor drive when it was
connected to the old Intel P965 board before. what's the difference
form
Am Tue, 14 Aug 2007 19:15:52 +0900
schrieb Tejun Heo <[EMAIL PROTECTED]>:
> Most likely a hardware issue.
>
> * Please try a different harddrive/cable and connect to a different
> port.
>
> * Get a different power supply and see whether that changes anything.
>
already tried different ports,
Michal Piotrowski wrote:
> Hi Andreas,
>
> [Adding Jeff and linux-ide to CC]
>
> On 13/08/07, Andreas Radke <[EMAIL PROTECTED]> wrote:
>> running ArchLinux kernel 2.6.22.2 on a Abit IP35 Pro motherboard with
>> Pro Intel P35 chipset (ICH9R + Jmicron) i have these entries all few
>> minutes:
>>
Michal Piotrowski wrote:
Hi Andreas,
[Adding Jeff and linux-ide to CC]
On 13/08/07, Andreas Radke [EMAIL PROTECTED] wrote:
running ArchLinux kernel 2.6.22.2 on a Abit IP35 Pro motherboard with
Pro Intel P35 chipset (ICH9R + Jmicron) i have these entries all few
minutes:
ata1.00:
Am Tue, 14 Aug 2007 19:15:52 +0900
schrieb Tejun Heo [EMAIL PROTECTED]:
Most likely a hardware issue.
* Please try a different harddrive/cable and connect to a different
port.
* Get a different power supply and see whether that changes anything.
already tried different ports, several
Hi Andreas,
[Adding Jeff and linux-ide to CC]
On 13/08/07, Andreas Radke <[EMAIL PROTECTED]> wrote:
> running ArchLinux kernel 2.6.22.2 on a Abit IP35 Pro motherboard with
> Pro Intel P35 chipset (ICH9R + Jmicron) i have these entries all few
> minutes:
>
> ata1.00: exception Emask 0x10 SAct 0x0
running ArchLinux kernel 2.6.22.2 on a Abit IP35 Pro motherboard with
Pro Intel P35 chipset (ICH9R + Jmicron) i have these entries all few
minutes:
ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x400101 action 0x2 frozen
ata1.00: (irq_stat 0x0800, interface fatal error)
ata1.00: cmd
running ArchLinux kernel 2.6.22.2 on a Abit IP35 Pro motherboard with
Pro Intel P35 chipset (ICH9R + Jmicron) i have these entries all few
minutes:
ata1.00: exception Emask 0x10 SAct 0x0 SErr 0x400101 action 0x2 frozen
ata1.00: (irq_stat 0x0800, interface fatal error)
ata1.00: cmd
Hi Andreas,
[Adding Jeff and linux-ide to CC]
On 13/08/07, Andreas Radke [EMAIL PROTECTED] wrote:
running ArchLinux kernel 2.6.22.2 on a Abit IP35 Pro motherboard with
Pro Intel P35 chipset (ICH9R + Jmicron) i have these entries all few
minutes:
ata1.00: exception Emask 0x10 SAct 0x0 SErr
14 matches
Mail list logo
