I just compiled 2.6.22.1 on my Kubuntu 7.0.4 system.
As before, I get errors using my Seagate SATA drives, and setting adma=0
fixes the problem. I've posted the exact error/reset messages several times
before.
However, I would like to note that it happens far less often with 2.6.22.1
than it
I just compiled 2.6.22.1 on my Kubuntu 7.0.4 system.
As before, I get errors using my Seagate SATA drives, and setting adma=0
fixes the problem. I've posted the exact error/reset messages several times
before.
However, I would like to note that it happens far less often with 2.6.22.1
than it
A system I was using a few minutes ago dumped this to the syslog:
Jul 9 17:50:38 daydream kernel: [76022.613000] BUG: unable to handle
kernel NUL
L pointer dereference at virtual address 0010
Jul 9 17:50:38 daydream kernel: [76022.613000] printing eip:
Jul 9 17:50:38 daydream kernel:
A system I was using a few minutes ago dumped this to the syslog:
Jul 9 17:50:38 daydream kernel: [76022.613000] BUG: unable to handle
kernel NUL
L pointer dereference at virtual address 0010
Jul 9 17:50:38 daydream kernel: [76022.613000] printing eip:
Jul 9 17:50:38 daydream kernel:
Following this post is output from Linux kernel 2.6.21 showing ADMA timeouts.
2.6.21 has improved the situation over earlier kernels, but the problems do
still occur.
nforce4 chipset, Seagate Barracuda SATA drives.
This is meant mainly as an additional data point in case it helps someone
Following this post is output from Linux kernel 2.6.21 showing ADMA timeouts.
2.6.21 has improved the situation over earlier kernels, but the problems do
still occur.
nforce4 chipset, Seagate Barracuda SATA drives.
This is meant mainly as an additional data point in case it helps someone
My system has issues running adma mode with sata_nv. I have an nforce4
motherboard.
What is the current status of this problem?
Is there any information I can provide to help debug it?
I gave up trying various fixes about 6 months ago, and put "sata_nv.adma=0" on
the kernel command line
My system has issues running adma mode with sata_nv. I have an nforce4
motherboard.
What is the current status of this problem?
Is there any information I can provide to help debug it?
I gave up trying various fixes about 6 months ago, and put sata_nv.adma=0 on
the kernel command line in
On Fri, 16 Mar 2007 17:44:25 -0600
Robert Hancock <[EMAIL PROTECTED]> wrote:
> Charles Shannon Hendrix wrote:
> > I normally run a modified 2.6.19 kernel and it works great.
> >
> > I recently tried 2.6.20 and had severe SATA problems with it.
> >
On Fri, 16 Mar 2007 11:58:21 -0400
Jeff Garzik <[EMAIL PROTECTED]> wrote:
> Charles Shannon Hendrix wrote:
> > I normally run a modified 2.6.19 kernel and it works great.
> >
> > I recently tried 2.6.20 and had severe SATA problems with it.
> >
> > Yeste
I normally run a modified 2.6.19 kernel and it works great.
I recently tried 2.6.20 and had severe SATA problems with it.
Yesterday I tried 2.6.20.3, and the problems are still there.
Relevant /var/log/messages entries:
Mar 14 20:45:11 daydream kernel: ata3: EH in ADMA mode, notifier 0x0
I normally run a modified 2.6.19 kernel and it works great.
I recently tried 2.6.20 and had severe SATA problems with it.
Yesterday I tried 2.6.20.3, and the problems are still there.
Relevant /var/log/messages entries:
Mar 14 20:45:11 daydream kernel: ata3: EH in ADMA mode, notifier 0x0
On Fri, 16 Mar 2007 11:58:21 -0400
Jeff Garzik [EMAIL PROTECTED] wrote:
Charles Shannon Hendrix wrote:
I normally run a modified 2.6.19 kernel and it works great.
I recently tried 2.6.20 and had severe SATA problems with it.
Yesterday I tried 2.6.20.3, and the problems are still
On Fri, 16 Mar 2007 17:44:25 -0600
Robert Hancock [EMAIL PROTECTED] wrote:
Charles Shannon Hendrix wrote:
I normally run a modified 2.6.19 kernel and it works great.
I recently tried 2.6.20 and had severe SATA problems with it.
Yesterday I tried 2.6.20.3, and the problems are still
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
>
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
16 matches
Mail list logo
