[E1000-devel] e1000e 0000:00:19.0: DMA-API: device driver tries to free DMA memory it has not allocated [device address=0x0000000052ff084a] [size=90 bytes]

2009-03-18 Thread Ingo Molnar
( e1000e Cc:s added. A new debug feature, CONFIG_DMA_API_DEBUG=y, has triggered the warning below in e1000_put_txbuf(). ) * Joerg Roedel joerg.roe...@amd.com wrote: On Wed, Mar 18, 2009 at 10:38:47AM +0100, Ingo Molnar wrote: e1000e :00:19.0: irq 30 for MSI/MSI-X e1000e

[E1000-devel] forcedeth 0000:00:0a.0: DMA-API: device driver frees DMA memory with wrong function [device address=0x0000000035992232] [size=42 bytes] [mapped as single] [unmapped as page]

2009-03-18 Thread Ingo Molnar
There's a similar-looking warning triggering for the forcedeth driver as well on another test-system (see the details below). Does anyone know whether there's a fix for this too, or is it a new warning? Ingo - Forwarded message from Ingo Molnar mi...@elte.hu - Date: Wed, 18

Re: [E1000-devel] e1000e 0000:00:19.0: DMA-API: device driver tries to free DMA memory it has not allocated [device address=0x0000000052ff084a] [size=90 bytes]

2009-03-18 Thread Brandeburg, Jesse
Ingo Molnar wrote: * Lubomir Rintel lkund...@v3.sk wrote: On Wed, March 18, 2009 8:04 am, Ingo Molnar wrote: ( e1000e Cc:s added. A new debug feature, CONFIG_DMA_API_DEBUG=y, has triggered the warning below in e1000_put_txbuf(). ) http://lkml.org/lkml/2009/3/2/318 We are still

Re: [E1000-devel] e1000e 0000:00:19.0: DMA-API: device driver tries to free DMA memory it has not allocated [device address=0x0000000052ff084a] [size=90 bytes]

2009-03-18 Thread Ingo Molnar
* Brandeburg, Jesse jesse.brandeb...@intel.com wrote: Ingo Molnar wrote: * Lubomir Rintel lkund...@v3.sk wrote: On Wed, March 18, 2009 8:04 am, Ingo Molnar wrote: ( e1000e Cc:s added. A new debug feature, CONFIG_DMA_API_DEBUG=y, has triggered the warning below in

Re: [E1000-devel] IGMP Join dropping multicast packets

2009-03-18 Thread Brandeburg, Jesse
On Tue, 17 Mar 2009, Dave Boutcher wrote: Eric, based on your inability to recreate this, I tried on some other hardware I had lying around that has an AMD chipset built-in NIC. I could not recreate the problem on that hardware. I'm starting to think this is an e1000 problem. In both the

Re: [E1000-devel] e1000e 0000:00:19.0: DMA-API: device driver tries to free DMA memory it has not allocated [device address=0x0000000052ff084a] [size=90 bytes]

2009-03-18 Thread Brandeburg, Jesse
On Wed, 18 Mar 2009, Ingo Molnar wrote: http://lkml.org/lkml/2009/3/2/318 We are still looking for more testing from the general community of this patch, in particular if any tx hangs are reported. Thanks in advance for any reports.-- Yeah - already picked it up into

[E1000-devel] Returned mail: see transcript for details

2009-03-18 Thread Mail Delivery Subsystem
Hi. This is the MAILNARA program at mail.asiaeconomy.co.kr. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. j...@asiae.co.kr: Sorry, no mailbox here by that name. (#5.1.1) See the copy of the mail

Re: [E1000-devel] IGMP Join dropping multicast packets

2009-03-18 Thread Dave Boutcher
On Wed, Mar 18, 2009 at 12:24 PM, Brandeburg, Jesse jesse.brandeb...@intel.com wrote: On Tue, 17 Mar 2009, Dave Boutcher wrote: Eric, based on your inability to recreate this, I tried on some other hardware I had lying around that has an AMD chipset built-in NIC. I could not recreate the

Re: [E1000-devel] IGMP Join dropping multicast packets

2009-03-18 Thread Dave Boutcher
On Wed, Mar 18, 2009 at 12:24 PM, Brandeburg, Jesse jesse.brandeb...@intel.com wrote: On Tue, 17 Mar 2009, Dave Boutcher wrote: Eric, based on your inability to recreate this, I tried on some other hardware I had lying around that has an AMD chipset built-in NIC. I could not recreate the

[E1000-devel] Returned mail: see transcript for details

2009-03-18 Thread Mail Delivery Subsystem
Hi. This is the MAILNARA program at mail.asiaeconomy.co.kr. I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out. r...@asiae.co.kr: Sorry, no mailbox here by that name. (#5.1.1) See the copy of the mail