[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1287005808.2649.46.camel@edumazet-laptop>
Date: Wed, 13 Oct 2010 23:36:48 +0200
From: Eric Dumazet <eric.dumazet@...il.com>
To: Keith Mannthey <kmannth@...ibm.com>
Cc: netdev@...r.kernel.org, mchan@...adcom.com
Subject: Re: bnx2 is spamming dmesg
Le mercredi 13 octobre 2010 à 14:30 -0700, Keith Mannthey a écrit :
> Hello All,
> For the last couple of months (since at least 2.6.35 somewhere) I have
> been seeing
>
> "
> ....
> [698612.423825] Device 0000:0b:00.0 unmapping: pfn ffc74-ffc74
> [698612.423831] Device 0000:0b:00.0 unmapping: pfn ff96d-ff96d
> [698612.639262] Device 0000:0b:00.0 unmapping: pfn ffc74-ffc74
> [698612.639269] Device 0000:0b:00.0 unmapping: pfn ff96d-ff96d
> ....
> "
> in my dmesg output.
>
> "
> lspci -s 0000:0b:00.0
> 0b:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5709
> Gigabit Ethernet (rev 20)
> "
>
> The bnx2 driver is loaded on my system. I am presently on 2.6.36-rc3
> kernels but like I mentioned I have been seeing this for a while.
>
>
> Any ideas? I would rather not have this endless message in my kernel
> logs.
>
drivers/pci/intel-iommu.c line 2737
pr_debug("Device %s unmapping: pfn %lx-%lx\n",
pci_name(pdev), start_pfn, last_pfn);
So you asked/activated some debugging, because pr_debug() is not default
enabled...
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists