Fragmentation issue
Subsystems (2)
A message that is not in the archive (sent off-list or not yet received): 1081671742.2844.0.camel@dhcppc4
RE: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface?
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:[email protected]]
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.
Quoted 88 lines · Shawn Starr
No, something else is causing problem, don't know why i2c is?
-----Original Message-----
From: Brown, Len [mailto:[email protected]]
Sent: Sunday, April 11, 2004 01:22 AM
To: Shawn Starr
Subject: RE: [BUG][2.6.5 final][e100/ee100pro]NETDEV_WATCHDOGTimeout - Related to i2c interface?So ACPI enabled/disabled doesn't make any difference?
Quoted 75 lines
-----Original Message-----
From: Shawn Starr [mailto:[email protected]]
Sent: Saturday, April 10, 2004 2:23 AM
To: Feldman, Scott; Brown, Len
Cc: [email protected]; [email protected]
Subject: [BUG][2.6.5 final][e100/ee100pro]NETDEV_WATCHDOGTimeout - 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_adapteri2c-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:[email protected]]
Sent: Wednesday, April 07, 2004 02:31 PM
To: Brown, Len; Shawn Starr
Subject: RE: [BUG][2.6.5 final][e100]NETDEV_WATCHDOGTimeout
- Was not a
problem with 2.6.5-rc3Quoted 7 lines
Quoted 3 lines
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/interruptsfor both cases)Yes, sorry. Can't believe I posted that to lkml. Oh well.
-scott
Re: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface?
Quoted 6 lines · Shawn Starr
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
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?
Quoted 8 lines · Shawn Starr
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
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" <[email protected]>
To: "'Jeff Garzik'" <[email protected]>
Cc: "'Len Brown'" <[email protected]>; <[email protected]>; <[email protected]>
Sent: Tuesday, April 13, 2004 10:46 AM
Subject: RE: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface?
Quoted 28 lines
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_WATCHDOGTimeout -Related to i2c interface?Quoted 8 lines · Shawn Starr
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
RE: [BUG][2.6.5 final][e100/ee100pro] NETDEV_WATCHDOG Timeout -Related to i2c interface?
In reply to Jeff GarzikMight 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?
Quoted 8 lines · Shawn Starr
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