| Message ID | 20090319165842.GA10819@xw6200.broadcom.net |
|---|---|
| State | RFC, archived |
| Delegated to: | David Miller |
| Headers | show |
On Thu, Mar 19, 2009 at 09:58:42AM -0700, Matt Carlson wrote: Hello Matt, > Hi Bernhard. I talked to Michael about this and we'd like you to try > two things. > > 1) Can you disable iLo2 and see if you can still reproduce the problem? That will take a few days, I'll ask the on-site guys to check whether we have an external IP-KVM available. Would switching the uplink connection to eth1 (and not use eth0 in Linux) give some more clue as well? > 2) Can you apply the following patch to get more information on when > MMIO gets disabled? Applied, I'll send you the information as soon as it happens again (which seems to be happening rather often the last couple of days). Bernhard -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Mar 19, 2009 at 11:06:44AM -0700, Bernhard Schmidt wrote: > On Thu, Mar 19, 2009 at 09:58:42AM -0700, Matt Carlson wrote: > > Hello Matt, > > > Hi Bernhard. I talked to Michael about this and we'd like you to try > > two things. > > > > 1) Can you disable iLo2 and see if you can still reproduce the problem? > > That will take a few days, I'll ask the on-site guys to check whether we > have an external IP-KVM available. > > Would switching the uplink connection to eth1 (and not use eth0 in > Linux) give some more clue as well? Sure, let's try that. Maybe this is the better way to go anyways. I just learned that disabling iLo2 doesn't necessarily disable the management firmware on the network device. For this to be a meaningful test though, we need to verify that the driver sign-on messages have a line that reads "ASF[0]" on eth1. Can you confirm? > > 2) Can you apply the following patch to get more information on when > > MMIO gets disabled? > > Applied, I'll send you the information as soon as it happens again > (which seems to be happening rather often the last couple of days). Thanks. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Mar 19, 2009 at 11:15:36AM -0700, Matt Carlson wrote: > > Would switching the uplink connection to eth1 (and not use eth0 in > > Linux) give some more clue as well? > Sure, let's try that. Maybe this is the better way to go anyways. I just > learned that disabling iLo2 doesn't necessarily disable the management > firmware on the network device. > > For this to be a meaningful test though, we need to verify that the > driver sign-on messages have a line that reads "ASF[0]" on eth1. Can > you confirm? Yes: [1186598.218205] eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[1] WireSpeed[1] TSOcap[1] [1186598.281314] eth1: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] WireSpeed[1] TSOcap[1] I'll keep the traffic on eth0 now until it breaks again, hopefully spewing out more debugging info with your patch and then I'll switch to eth1. Bernhard -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Mar 19, 2009 at 09:58:42AM -0700, Matt Carlson wrote: Hello Matt, > Hi Bernhard. I talked to Michael about this and we'd like you to try > two things. > > 1) Can you disable iLo2 and see if you can still reproduce the problem? > 2) Can you apply the following patch to get more information on when > MMIO gets disabled? Not sure this is going to help you. NIC crashed two times tonight, logs look like this Mar 22 04:06:46 svr02 kernel: [1392136.468921] PCI Memory Mapped IO Disabled!!!! Mar 22 04:06:47 svr02 kernel: [1392137.520288] PCI Memory Mapped IO Disabled!!!! Mar 22 04:06:48 svr02 kernel: [1392138.568267] PCI Memory Mapped IO Disabled!!!! Mar 22 04:06:49 svr02 kernel: [1392139.616266] PCI Memory Mapped IO Disabled!!!! Mar 22 04:06:50 svr02 kernel: [1392140.664266] PCI Memory Mapped IO Disabled!!!! Mar 22 04:06:51 svr02 kernel: [1392141.712276] PCI Memory Mapped IO Disabled!!!! Mar 22 04:06:52 svr02 kernel: [1392142.760297] PCI Memory Mapped IO Disabled!!!! Mar 22 04:06:53 svr02 kernel: [1392143.808258] PCI Memory Mapped IO Disabled!!!! Mar 22 04:06:54 svr02 kernel: [1392144.856256] PCI Memory Mapped IO Disabled!!!! Mar 22 04:06:55 svr02 kernel: [1392145.904266] PCI Memory Mapped IO Disabled!!!! Mar 22 04:06:56 svr02 kernel: [1392146.952276] PCI Memory Mapped IO Disabled!!!! Mar 22 04:06:57 svr02 kernel: [1392148.000267] PCI Memory Mapped IO Disabled!!!! Mar 22 04:06:58 svr02 kernel: [1392149.048271] PCI Memory Mapped IO Disabled!!!! Mar 22 04:06:59 svr02 kernel: [1392150.096268] PCI Memory Mapped IO Disabled!!!! Mar 22 04:07:00 svr02 kernel: [1392151.144277] PCI Memory Mapped IO Disabled!!!! Mar 22 04:07:01 svr02 kernel: [1392152.192287] PCI Memory Mapped IO Disabled!!!! Mar 22 04:07:02 svr02 kernel: [1392153.240268] PCI Memory Mapped IO Disabled!!!! Mar 22 04:07:03 svr02 kernel: [1392154.288267] PCI Memory Mapped IO Disabled!!!! Mar 22 04:07:04 svr02 kernel: [1392155.336267] PCI Memory Mapped IO Disabled!!!! Mar 22 04:07:05 svr02 kernel: [1392156.384268] PCI Memory Mapped IO Disabled!!!! Mar 22 04:07:07 svr02 kernel: [1392157.432267] PCI Memory Mapped IO Disabled!!!! Mar 22 04:07:08 svr02 kernel: [1392158.480266] PCI Memory Mapped IO Disabled!!!! Mar 22 04:07:09 svr02 kernel: [1392159.528289] PCI Memory Mapped IO Disabled!!!! Mar 22 04:07:10 svr02 kernel: [1392160.576297] PCI Memory Mapped IO Disabled!!!! Mar 22 04:07:11 svr02 kernel: [1392161.624277] PCI Memory Mapped IO Disabled!!!! Mar 22 04:07:12 svr02 kernel: [1392162.672267] PCI Memory Mapped IO Disabled!!!! Mar 22 04:07:13 svr02 kernel: [1392163.720266] PCI Memory Mapped IO Disabled!!!! Mar 22 04:07:14 svr02 kernel: [1392164.768266] PCI Memory Mapped IO Disabled!!!! at this point the "watchdog" kicked in and did rmmod/modprobe, so I think the only thing you can read out of this debugging log is that there was no kernel message right before MMIO got disabled and it takes quite a while to fire the Tx timeout. Mar 22 04:07:15 svr02 kernel: [1392165.540078] tg3 0000:03:04.1: PCI INT B disabled Mar 22 04:07:16 svr02 kernel: [1392166.817125] tg3: tg3_abort_hw timed out for eth0, TX_MODE_ENABLE will not clear MAC_TX_MODE=ffffffff Mar 22 04:07:18 svr02 kernel: [1392168.398844] tg3: eth0: No firmware running. Mar 22 04:07:29 svr02 kernel: [1392179.793309] tg3: eth0: Link is down. Mar 22 04:07:31 svr02 kernel: [1392181.896030] tg3 0000:03:04.0: PCI INT A disabled Mar 22 04:07:33 svr02 kernel: [1392183.957132] tg3.c:v3.94 (August 14, 2008) Mar 22 04:07:33 svr02 kernel: [1392184.020034] tg3 0000:03:04.0: enabling device (0000 -> 0002) Mar 22 04:07:33 svr02 kernel: [1392184.086083] tg3 0000:03:04.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 I'm now switching to eth1. Bernhard -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sun, Mar 22, 2009 at 06:21:21AM -0700, Bernhard Schmidt wrote: > On Thu, Mar 19, 2009 at 09:58:42AM -0700, Matt Carlson wrote: > > Hello Matt, > > > Hi Bernhard. I talked to Michael about this and we'd like you to try > > two things. > > > > 1) Can you disable iLo2 and see if you can still reproduce the problem? > > 2) Can you apply the following patch to get more information on when > > MMIO gets disabled? > > Not sure this is going to help you. NIC crashed two times tonight, logs > look like this Actually, it does. :) > Mar 22 04:06:46 svr02 kernel: [1392136.468921] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:47 svr02 kernel: [1392137.520288] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:48 svr02 kernel: [1392138.568267] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:49 svr02 kernel: [1392139.616266] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:50 svr02 kernel: [1392140.664266] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:51 svr02 kernel: [1392141.712276] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:52 svr02 kernel: [1392142.760297] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:53 svr02 kernel: [1392143.808258] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:54 svr02 kernel: [1392144.856256] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:55 svr02 kernel: [1392145.904266] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:56 svr02 kernel: [1392146.952276] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:57 svr02 kernel: [1392148.000267] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:58 svr02 kernel: [1392149.048271] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:59 svr02 kernel: [1392150.096268] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:00 svr02 kernel: [1392151.144277] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:01 svr02 kernel: [1392152.192287] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:02 svr02 kernel: [1392153.240268] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:03 svr02 kernel: [1392154.288267] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:04 svr02 kernel: [1392155.336267] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:05 svr02 kernel: [1392156.384268] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:07 svr02 kernel: [1392157.432267] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:08 svr02 kernel: [1392158.480266] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:09 svr02 kernel: [1392159.528289] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:10 svr02 kernel: [1392160.576297] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:11 svr02 kernel: [1392161.624277] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:12 svr02 kernel: [1392162.672267] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:13 svr02 kernel: [1392163.720266] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:14 svr02 kernel: [1392164.768266] PCI Memory Mapped IO Disabled!!!! > > at this point the "watchdog" kicked in and did rmmod/modprobe, so I > think the only thing you can read out of this debugging log is that > there was no kernel message right before MMIO got disabled and it takes > quite a while to fire the Tx timeout. So traffic on this box must be pretty light for the watchdog to fire off 30 seconds after the MMIO problem was detected, right? Interesting. > Mar 22 04:07:15 svr02 kernel: [1392165.540078] tg3 0000:03:04.1: PCI INT B disabled > Mar 22 04:07:16 svr02 kernel: [1392166.817125] tg3: tg3_abort_hw timed out for eth0, TX_MODE_ENABLE will not clear MAC_TX_MODE=ffffffff > Mar 22 04:07:18 svr02 kernel: [1392168.398844] tg3: eth0: No firmware running. > Mar 22 04:07:29 svr02 kernel: [1392179.793309] tg3: eth0: Link is down. > Mar 22 04:07:31 svr02 kernel: [1392181.896030] tg3 0000:03:04.0: PCI INT A disabled > Mar 22 04:07:33 svr02 kernel: [1392183.957132] tg3.c:v3.94 (August 14, 2008) > Mar 22 04:07:33 svr02 kernel: [1392184.020034] tg3 0000:03:04.0: enabling device (0000 -> 0002) > Mar 22 04:07:33 svr02 kernel: [1392184.086083] tg3 0000:03:04.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > > I'm now switching to eth1. O.K. I eagerly await your results. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On 23.03.2009 19:18, Matt Carlson wrote: Hello Matt, >> Mar 22 04:06:46 svr02 kernel: [1392136.468921] PCI Memory Mapped IO Disabled!!!! [...] >> Mar 22 04:07:14 svr02 kernel: [1392164.768266] PCI Memory Mapped IO Disabled!!!! >> at this point the "watchdog" kicked in and did rmmod/modprobe, so I >> think the only thing you can read out of this debugging log is that >> there was no kernel message right before MMIO got disabled and it takes >> quite a while to fire the Tx timeout. > So traffic on this box must be pretty light for the watchdog to fire off > 30 seconds after the MMIO problem was detected, right? Interesting. Just to make sure I didn't confuse you, the "watchdog" I was talking about here is a shellscript like this, executed every minute --- /bin/ping -q -c 5 <defaultgw> > /dev/null RC=$? if [ ${RC} -ne 0 ]; then rmmod tg3; sleep 5; modprobe tg3; sleep 5; ifup --force eth0 fi --- at :46 MMIO was disabled, at :00 the cronjob started which took until :15 before detecting the network was dead and reloaded the modules >> Mar 22 04:07:15 svr02 kernel: [1392165.540078] tg3 0000:03:04.1: PCI INT B disabled >> Mar 22 04:07:16 svr02 kernel: [1392166.817125] tg3: tg3_abort_hw timed out for eth0, TX_MODE_ENABLE will not clear MAC_TX_MODE=ffffffff >> Mar 22 04:07:18 svr02 kernel: [1392168.398844] tg3: eth0: No firmware running. >> Mar 22 04:07:29 svr02 kernel: [1392179.793309] tg3: eth0: Link is down. >> Mar 22 04:07:31 svr02 kernel: [1392181.896030] tg3 0000:03:04.0: PCI INT A disabled >> Mar 22 04:07:33 svr02 kernel: [1392183.957132] tg3.c:v3.94 (August 14, 2008) >> Mar 22 04:07:33 svr02 kernel: [1392184.020034] tg3 0000:03:04.0: enabling device (0000 -> 0002) >> Mar 22 04:07:33 svr02 kernel: [1392184.086083] tg3 0000:03:04.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 The tg3 watchdog (tg3: eth0: transmit timed out, resetting) did not appear at all in this circle, so I guess the checkscript killed the module before. Yes, the NIC is very lightly loaded, around 100kbps / 70pps in each direction with a few occasional spikes. >> I'm now switching to eth1. > O.K. I eagerly await your results. So far so good, but it has only been running ~36 hours, that's not really a stability spree yet :-) I'll keep you updated. Bernhard -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sun, Mar 22, 2009 at 06:21:21AM -0700, Bernhard Schmidt wrote: > On Thu, Mar 19, 2009 at 09:58:42AM -0700, Matt Carlson wrote: > > Hello Matt, > > > Hi Bernhard. I talked to Michael about this and we'd like you to try > > two things. > > > > 1) Can you disable iLo2 and see if you can still reproduce the problem? > > 2) Can you apply the following patch to get more information on when > > MMIO gets disabled? > > Not sure this is going to help you. NIC crashed two times tonight, logs > look like this > > Mar 22 04:06:46 svr02 kernel: [1392136.468921] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:47 svr02 kernel: [1392137.520288] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:48 svr02 kernel: [1392138.568267] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:49 svr02 kernel: [1392139.616266] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:50 svr02 kernel: [1392140.664266] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:51 svr02 kernel: [1392141.712276] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:52 svr02 kernel: [1392142.760297] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:53 svr02 kernel: [1392143.808258] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:54 svr02 kernel: [1392144.856256] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:55 svr02 kernel: [1392145.904266] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:56 svr02 kernel: [1392146.952276] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:57 svr02 kernel: [1392148.000267] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:58 svr02 kernel: [1392149.048271] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:06:59 svr02 kernel: [1392150.096268] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:00 svr02 kernel: [1392151.144277] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:01 svr02 kernel: [1392152.192287] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:02 svr02 kernel: [1392153.240268] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:03 svr02 kernel: [1392154.288267] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:04 svr02 kernel: [1392155.336267] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:05 svr02 kernel: [1392156.384268] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:07 svr02 kernel: [1392157.432267] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:08 svr02 kernel: [1392158.480266] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:09 svr02 kernel: [1392159.528289] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:10 svr02 kernel: [1392160.576297] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:11 svr02 kernel: [1392161.624277] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:12 svr02 kernel: [1392162.672267] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:13 svr02 kernel: [1392163.720266] PCI Memory Mapped IO Disabled!!!! > Mar 22 04:07:14 svr02 kernel: [1392164.768266] PCI Memory Mapped IO Disabled!!!! > > at this point the "watchdog" kicked in and did rmmod/modprobe, so I > think the only thing you can read out of this debugging log is that > there was no kernel message right before MMIO got disabled and it takes > quite a while to fire the Tx timeout. > > Mar 22 04:07:15 svr02 kernel: [1392165.540078] tg3 0000:03:04.1: PCI INT B disabled > Mar 22 04:07:16 svr02 kernel: [1392166.817125] tg3: tg3_abort_hw timed out for eth0, TX_MODE_ENABLE will not clear MAC_TX_MODE=ffffffff > Mar 22 04:07:18 svr02 kernel: [1392168.398844] tg3: eth0: No firmware running. > Mar 22 04:07:29 svr02 kernel: [1392179.793309] tg3: eth0: Link is down. > Mar 22 04:07:31 svr02 kernel: [1392181.896030] tg3 0000:03:04.0: PCI INT A disabled > Mar 22 04:07:33 svr02 kernel: [1392183.957132] tg3.c:v3.94 (August 14, 2008) > Mar 22 04:07:33 svr02 kernel: [1392184.020034] tg3 0000:03:04.0: enabling device (0000 -> 0002) > Mar 22 04:07:33 svr02 kernel: [1392184.086083] tg3 0000:03:04.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > > I'm now switching to eth1. Bernhard, any word on what happened? -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Mar 31, 2009 at 09:26:17AM -0700, Matt Carlson wrote: > > I'm now switching to eth1. > Bernhard, any word on what happened? So far so good. In the last week my watchdog (cannot reach the default gateway) triggered once, but since there were no "PCI Memory Mapped IO Disabled!!!!" messages in the logfile I assume that was a real network problem. Since the box ran fine for months initially and the first two occurances of this issue were two weeks apart I cannot say for sure, but it definitely feels better than the "once in two days" in the end. Bernhard -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi Matt, >>> I'm now switching to eth1. >> Bernhard, any word on what happened? > > So far so good. In the last week my watchdog (cannot reach the default > gateway) triggered once, but since there were no "PCI Memory Mapped IO > Disabled!!!!" messages in the logfile I assume that was a real network > problem. Since the box ran fine for months initially and the first two > occurances of this issue were two weeks apart I cannot say for sure, but > it definitely feels better than the "once in two days" in the end. No crashes in the last two weeks. Do you have any further suggestions how to debug this or should we accept that portsharing doesn't work very well? This is the second problem we can directly attribute to the sharing with the iLO (the first one being the "no IPv6 unless the port is in promiscous mode", we had a thread about this here on netdev a few months ago). Bernhard -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, Apr 13, 2009 at 02:54:40PM -0700, Bernhard Schmidt wrote: > Hi Matt, > > >>> I'm now switching to eth1. > >> Bernhard, any word on what happened? > > > > So far so good. In the last week my watchdog (cannot reach the default > > gateway) triggered once, but since there were no "PCI Memory Mapped IO > > Disabled!!!!" messages in the logfile I assume that was a real network > > problem. Since the box ran fine for months initially and the first two > > occurances of this issue were two weeks apart I cannot say for sure, but > > it definitely feels better than the "once in two days" in the end. > > No crashes in the last two weeks. > > Do you have any further suggestions how to debug this or should we > accept that portsharing doesn't work very well? This is the second > problem we can directly attribute to the sharing with the iLO (the first > one being the "no IPv6 unless the port is in promiscous mode", we had a > thread about this here on netdev a few months ago). No, I think we need to get this to work with portsharing. We just need to figure out what it is about it that causes these types of errors. I talked to the firmware maintainer here. We have a couple ideas that might uncover what is happening. Our next step is to develop a set of tests that will show under what assumptions the firmware is operating. Once we have that, I'll ask you to patch your driver so that we can see what is happening from your end. Stay tuned. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
diff -Nrup 1/drivers/net/tg3.c 2/drivers/net/tg3.c --- 1/drivers/net/tg3.c 2009-02-20 14:41:27.000000000 -0800 +++ 2/drivers/net/tg3.c 2009-03-19 09:51:17.000000000 -0700 @@ -7799,6 +7799,12 @@ static void tg3_timer(unsigned long __op /* This part only runs once per second. */ if (!--tp->timer_counter) { + u16 pci_cmd; + + pci_read_config_word(tp->pdev, PCI_COMMAND, &pci_cmd); + if (!(pci_cmd & PCI_COMMAND_MEMORY)) + printk( KERN_WARNING "PCI Memory Mapped IO Disabled!!!!\n" ); + if (tp->tg3_flags2 & TG3_FLG2_5705_PLUS) tg3_periodic_fetch_stats(tp);