netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Snook <csnook@redhat.com>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Jay Cliburn <jacliburn@bellsouth.net>,
	Luca Tettamanti <kronos.it@gmail.com>,
	Jeff Garzik <jeff@garzik.org>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
	Christoph Lameter <clameter@sgi.com>,
	torvalds@osdl.org
Subject: Re: atl1 64-bit => 32-bit DMA borkage (reproducible, bisected)
Date: Mon, 21 Apr 2008 14:42:42 -0400	[thread overview]
Message-ID: <480CE022.2080601@redhat.com> (raw)
In-Reply-To: <20080420205500.GA4762@martell.zuzino.mipt.ru>

Alexey Dobriyan wrote:
> On Sun, Apr 20, 2008 at 01:37:04PM -0500, Jay Cliburn wrote:
>> On Sun, 20 Apr 2008 16:26:31 +0400
>> Alexey Dobriyan <adobriyan@gmail.com> 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@gmail.com> 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@gmail.com> 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?
> 
> Yup!
> 
>> Can you duplicate the problem if you
>> simply ifconfig down instead of rebooting after the transfer?  
> 
> Aha, ifconfig down is enough. Here is how reproducer looks like now:
> 
> 	./sync-linux-linus && ssh core2 "sudo /sbin/ifconfig eth0 down"
> 
> where first script is basically scp(1).
> 
> Also, booting with 1G or 2G of RAM (mem=1024m) makes issue go away.
> 
> printk at dev_close() time shows that NETIF_F_HIGHDMA was not somehow
> enabled.
> 

Does the problem go away with iommu=nomerge?  If so, I suspect we're not 
properly flushing an iowrite somewhere.

-- Chris

  reply	other threads:[~2008-04-21 18:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080410203354.f0a6f464.akpm@linux-foundation.org>
     [not found] ` <20080413204422.GA5136@martell.zuzino.mipt.ru>
     [not found]   ` <84144f020804140901p1c076fd2q73e3effe7cd96da3@mail.gmail.com>
     [not found]     ` <Pine.LNX.4.64.0804141050550.6296@schroedinger.engr.sgi.com>
     [not found]       ` <20080414183221.GA5234@martell.zuzino.mipt.ru>
2008-04-14 19:56         ` 2.6.25-rc8-mm2: FIX kmalloc-2048 (was Re: 2.6.25-rc8-mm2: IP: [<ffffffff802868f9>] __kmalloc+0x69/0x110) Alexey Dobriyan
2008-04-14 20:05           ` Christoph Lameter
2008-04-19 11:17             ` Alexey Dobriyan
2008-04-19 14:45               ` atl1 64-bit => 32-bit DMA borkage (reproducible, bisected) Alexey Dobriyan
2008-04-20  2:54                 ` Jay Cliburn
2008-04-20 11:14                   ` Alexey Dobriyan
2008-04-20 11:06                     ` Jay Cliburn
2008-04-20 12:26                       ` Alexey Dobriyan
2008-04-20 18:37                         ` Jay Cliburn
2008-04-20 20:55                           ` Alexey Dobriyan
2008-04-21 18:42                             ` Chris Snook [this message]
2008-04-21 19:56                               ` Alexey Dobriyan
2008-04-22  2:08                             ` Jay Cliburn
2008-04-22 19:02                               ` Alexey Dobriyan
2008-04-26  0:57                               ` Jay Cliburn
2008-04-28  6:42                                 ` Alexey Dobriyan
2008-05-04 21:15                                 ` Alexey Dobriyan
2008-05-05  0:31                                   ` Jay Cliburn
2008-05-05  0:34                                     ` Jay Cliburn
2008-05-06 16:02                                   ` Jay Cliburn
2008-05-09 19:51                                     ` Alexey Dobriyan
2008-05-09 18:56                                       ` Chris Snook
2008-05-09 20:07                                         ` Alexey Dobriyan
2008-05-09 19:38                                           ` Jay Cliburn
2008-05-10 19:31                                             ` [PATCH] " Alexey Dobriyan
2008-05-11  1:58                                               ` Jay Cliburn

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=480CE022.2080601@redhat.com \
    --to=csnook@redhat.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=jacliburn@bellsouth.net \
    --cc=jeff@garzik.org \
    --cc=kronos.it@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=torvalds@osdl.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).