Re: atl1 64-bit => 32-bit DMA borkage (reproducible, bisected)
From: Jay Cliburn
Date: Sun Apr 20 2008 - 14:37:25 EST
On Sun, 20 Apr 2008 16:26:31 +0400
Alexey Dobriyan <adobriyan@xxxxxxxxx> wrote:
> On Sun, Apr 20, 2008 at 06:06:07AM -0500, Jay Cliburn wrote:
> > On Sun, 20 Apr 2008 15:14:53 +0400
> > Alexey Dobriyan <adobriyan@xxxxxxxxx> wrote:
> >
> > > On Sat, Apr 19, 2008 at 09:54:44PM -0500, Jay Cliburn wrote:
> > > > On Sat, 19 Apr 2008 18:45:35 +0400
> > > > Alexey Dobriyan <adobriyan@xxxxxxxxx> wrote:
[...]
> > > > > So, it's enough to scp 200 MB git archive and immediately
> > > > > start rebooting sequence for horrors described above to
> > > > > appear. It's not 100% reproducible but more like 90%.
> > > >
> > > > Do I understand correctly that these failures occur only while
> > > > the network interface is going down?
> > >
> > > Yep. During up or running there were no problems with this card.
> > >
> >
> > One more question: Does it happen whether or not you're using atl1
> > as a netconsole?
>
> Without netconsole bugs happens too.
>
I can't duplicate this error, but it's probably because my machine
doesn't have 4GB of memory.
I have one report in Febroary 2008 of another user encountering strange
oopses in 2.6.23.12 and 2.6.24 whenever he downed the interface. I
suspect your experience is a repeat of that.
Just to be clear, you transfer about 200MB to the NIC (Rx direction),
then immediately reboot, right? Can you duplicate the problem if you
simply ifconfig down instead of rebooting after the transfer?
Thanks for your help.
Jay
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/