* RE: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface? [not found] <1081671742.2844.0.camel@dhcppc4> @ 2004-04-11 20:09 ` Shawn Starr 2004-04-11 21:01 ` Jeff Garzik 0 siblings, 1 reply; 5+ messages in thread From: Shawn Starr @ 2004-04-11 20:09 UTC (permalink / raw) To: 'Len Brown'; +Cc: linux-kernel, netdev Ok, this is strange, I put in an external 10/100 PRO S Adaptor, and im not getting anymore eth0 timeouts, I would only get eth0 timeouts on the ONBOARD nic if I enabled the lm80 sensor driver.. I don't know what to say, the onboard nic would work fine without lm80 being loaded? Is there some sort of race condition that the onboard 10/100 PRO is doing ? I'm confused -----Original Message----- From: Len Brown [mailto:len.brown@intel.com] Sent: Sunday, April 11, 2004 04:22 AM To: Shawn Starr Subject: RE: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface? it could be that i2c is hooked up to the NIC for some management purpose -- maybe Scott knows. On Sun, 2004-04-11 at 03:32, Shawn Starr wrote: > No, something else is causing problem, don't know why i2c is? > > -----Original Message----- > From: Brown, Len [mailto:len.brown@intel.com] > Sent: Sunday, April 11, 2004 01:22 AM > To: Shawn Starr > Subject: RE: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout - > Related to i2c interface? > > > So ACPI enabled/disabled doesn't make any difference? > > >-----Original Message----- > >From: Shawn Starr [mailto:shawn.starr@rogers.com] > >Sent: Saturday, April 10, 2004 2:23 AM > >To: Feldman, Scott; Brown, Len > >Cc: linux-kernel@vger.kernel.org; netdev@oss.sgi.com > >Subject: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG > >Timeout - Related to i2c interface? > > > > > >Ok, did disable ACPI but still get these errors. I have noticed that > >if I start loading/unloading any i2c drivers I start getting eth0 > >timeouts....the > >question is why? > > > >coredump kernel: i2c_adapter i2c-2: Transaction (post): CNT=08, > >CMD=3a, > >ADD=50, DAT0=3e, DAT1=00 Apr 10 01:56:44 coredump kernel: i2c-core: > >unregister_driver - looking for > >clients. > >Apr 10 01:56:44 coredump kernel: i2c_adapter i2c-2: examining adapter > >Apr 10 01:56:44 coredump kernel: i2c-core.o: detaching client lm80: > >Apr 10 01:56:44 coredump kernel: i2c-core.o: detaching client lm80: > >Apr 10 01:56:44 coredump kernel: i2c-core: driver unregistered: lm80 > >Apr 10 01:56:48 coredump kernel: i2c_adapter i2c-2: Adapter > >unregistered > >Apr 10 01:56:48 coredump kernel: i2c_adapter i2c-2: adapter > >unregistered > >Apr 10 01:56:55 coredump kernel: eth0: wait_for_cmd_done timeout! > >Apr 10 01:56:55 coredump kernel: Command 00ff never accepted > >(201 polls)! > >Apr 10 01:56:55 coredump kernel: Command 0006 was not accepted > >after 20001 > >polls! Current status ffffffff. > >Apr 10 01:56:55 coredump kernel: Command 00ff never accepted > >(201 polls)! > >Apr 10 01:56:55 coredump kernel: Command 0060 was not accepted > >after 20001 > >polls! Current status ffffffff. > >Apr 10 01:56:55 coredump kernel: eth0: wait_for_cmd_done timeout! > >Apr 10 01:56:55 coredump kernel: Command 00ff never accepted > >(201 polls)! > >Apr 10 01:56:55 coredump kernel: Command 0001 was not accepted > >after 20001 > >polls! Current status ffffffff. > >Apr 10 01:56:55 coredump kernel: Command 00ff never accepted > >(201 polls)! > >Apr 10 01:56:56 coredump kernel: Command 0070 was not accepted > >after 20001 > >polls! Current status ffffffff. > >Apr 10 01:56:56 coredump kernel: eth0: wait_for_cmd_done timeout! > >Apr 10 01:57:27 coredump last message repeated 26 times > >Apr 10 01:57:29 coredump last message repeated 3 times > > > >-----Original Message----- > >From: Feldman, Scott [mailto:scott.feldman@intel.com] > >Sent: Wednesday, April 07, 2004 02:31 PM > >To: Brown, Len; Shawn Starr > >Subject: RE: [BUG][2.6.5 final][e100] NETDEV_WATCHDOG Timeout > >- Was not a > >problem with 2.6.5-rc3 > > > > > >> >Shawn, try turning off ACPI for interrupt routing. Load the > >> >kernel > >> >with the kernel parameter "noapci" set. > >> > >> You mean "acpi=off", or "pci=noacpi". If either of these fix the > >> problem, please let me know. (and send me the dmesg and > >> /proc/interrupts for both cases) > > > >Yes, sorry. Can't believe I posted that to lkml. Oh well. > > > >-scott > > > > > ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface? 2004-04-11 20:09 ` [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface? Shawn Starr @ 2004-04-11 21:01 ` Jeff Garzik 2004-04-13 5:16 ` Shawn Starr 2004-04-13 5:16 ` [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface? Shawn Starr 0 siblings, 2 replies; 5+ messages in thread From: Jeff Garzik @ 2004-04-11 21:01 UTC (permalink / raw) To: Shawn Starr; +Cc: 'Len Brown', linux-kernel, netdev Shawn Starr wrote: > Ok, this is strange, I put in an external 10/100 PRO S Adaptor, and im not > getting anymore eth0 timeouts, I would only get eth0 timeouts on the ONBOARD > nic if I enabled the lm80 sensor driver.. I don't know what to say, the > onboard nic would work fine without lm80 being loaded? > > Is there some sort of race condition that the onboard 10/100 PRO is doing ? If i2c is killing the network, sounds like it's diddling something on the motherboard it shouldn't... Jeff ^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface? 2004-04-11 21:01 ` Jeff Garzik @ 2004-04-13 5:16 ` Shawn Starr 2003-12-02 5:34 ` Fragmentation issue krupa 2004-04-13 5:16 ` [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface? Shawn Starr 1 sibling, 1 reply; 5+ messages in thread From: Shawn Starr @ 2004-04-13 5:16 UTC (permalink / raw) To: 'Jeff Garzik'; +Cc: 'Len Brown', linux-kernel, netdev Might be, I have since not had any issues with timeouts. Though, I don't know where it is doing this. It is an IBM machine so some things are proprietary. -----Original Message----- From: Jeff Garzik Sent: Sunday, April 11, 2004 05:02 PM To: Shawn Starr Cc: 'Len Brown'; linux-kernel@; netdev@ Subject: Re: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface? Shawn Starr wrote: > Ok, this is strange, I put in an external 10/100 PRO S Adaptor, and im > not getting anymore eth0 timeouts, I would only get eth0 timeouts on > the ONBOARD nic if I enabled the lm80 sensor driver.. I don't know > what to say, the onboard nic would work fine without lm80 being > loaded? > > Is there some sort of race condition that the onboard 10/100 PRO is > doing ? If i2c is killing the network, sounds like it's diddling something on the motherboard it shouldn't... Jeff ^ permalink raw reply [flat|nested] 5+ messages in thread
* Fragmentation issue 2004-04-13 5:16 ` Shawn Starr @ 2003-12-02 5:34 ` krupa 0 siblings, 0 replies; 5+ messages in thread From: krupa @ 2003-12-02 5:34 UTC (permalink / raw) To: linux-kernel, netdev Hi, Anybody.........could you help me. Steps followed. 1. insmod module.o // inserting module 2. iwconfig eth1 essid <access point> // associating with AP 3. iwconfig eth1 frag 512 // setting fragmentation 4. ping <ip of access point> -s 700 The problem here is ..............when I ping to that AP with packect size more that Frag value,69 packets it will send then it will hang. How to overcome this ----- Original Message ----- From: "Shawn Starr" <shawn.starr@rogers.com> To: "'Jeff Garzik'" <jgarzik@pobox.com> Cc: "'Len Brown'" <len.brown@intel.com>; <linux-kernel@vger.kernel.org>; <netdev@oss.sgi.com> Sent: Tuesday, April 13, 2004 10:46 AM Subject: RE: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface? > Might be, I have since not had any issues with timeouts. Though, I don't > know where it is doing this. It is an IBM machine so some things are > proprietary. > > -----Original Message----- > From: Jeff Garzik > Sent: Sunday, April 11, 2004 05:02 PM > To: Shawn Starr > Cc: 'Len Brown'; linux-kernel@; netdev@ > Subject: Re: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout > -Related to i2c interface? > > > Shawn Starr wrote: > > Ok, this is strange, I put in an external 10/100 PRO S Adaptor, and im > > not getting anymore eth0 timeouts, I would only get eth0 timeouts on > > the ONBOARD nic if I enabled the lm80 sensor driver.. I don't know > > what to say, the onboard nic would work fine without lm80 being > > loaded? > > > > Is there some sort of race condition that the onboard 10/100 PRO is > > doing ? > > If i2c is killing the network, sounds like it's diddling something on > the motherboard it shouldn't... > > Jeff > ^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface? 2004-04-11 21:01 ` Jeff Garzik 2004-04-13 5:16 ` Shawn Starr @ 2004-04-13 5:16 ` Shawn Starr 1 sibling, 0 replies; 5+ messages in thread From: Shawn Starr @ 2004-04-13 5:16 UTC (permalink / raw) To: 'Jeff Garzik'; +Cc: 'Len Brown', linux-kernel, netdev Might be, I have since not had any issues with timeouts. Though, I don't know where it is doing this. It is an IBM machine so some things are proprietary. -----Original Message----- From: Jeff Garzik Sent: Sunday, April 11, 2004 05:02 PM To: Shawn Starr Cc: 'Len Brown'; linux-kernel@; netdev@ Subject: Re: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface? Shawn Starr wrote: > Ok, this is strange, I put in an external 10/100 PRO S Adaptor, and im > not getting anymore eth0 timeouts, I would only get eth0 timeouts on > the ONBOARD nic if I enabled the lm80 sensor driver.. I don't know > what to say, the onboard nic would work fine without lm80 being > loaded? > > Is there some sort of race condition that the onboard 10/100 PRO is > doing ? If i2c is killing the network, sounds like it's diddling something on the motherboard it shouldn't... Jeff ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2004-04-13 5:16 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1081671742.2844.0.camel@dhcppc4>
2004-04-11 20:09 ` [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface? Shawn Starr
2004-04-11 21:01 ` Jeff Garzik
2004-04-13 5:16 ` Shawn Starr
2003-12-02 5:34 ` Fragmentation issue krupa
2004-04-13 5:16 ` [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface? Shawn Starr
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).