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 (d
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.2
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
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 eith
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
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 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 nfor
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:
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
>
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
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
> > [...]
> >
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 p
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/
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
14 matches
Mail list logo
