Re: eepro100 + 2.2.18 + laptop problems
On Tue, Feb 13, 2001 at 09:26:38AM +0800, Andrey Savochkin wrote: > On Sun, Feb 11, 2001 at 10:40:33PM +1100, CaT wrote: > [snip] > > Feb 11 22:30:18 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout >with(0x70)! > > Please try the attached patch. > Actually, it's designed to solve another problem, but may be your one has the > same origin as that other. > Index: eepro100.c Patch appears to have worked. After 2 weeks of actually using the right module (*sheepish grin*) I've not had the card popup the above error message. woo. So thanks for that. :) Majorly happy about things now. :) And now... to put ext3 on my laptop. -- CaT ([EMAIL PROTECTED])*** Jenna has joined the channel. speaking of mental giants.. me, a giant, bullshit And i'm not mental - An IRC session, 20/12/2000 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Tue, Feb 13, 2001 at 09:26:38AM +0800, Andrey Savochkin wrote: On Sun, Feb 11, 2001 at 10:40:33PM +1100, CaT wrote: [snip] Feb 11 22:30:18 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout with(0x70)! Please try the attached patch. Actually, it's designed to solve another problem, but may be your one has the same origin as that other. Index: eepro100.c Patch appears to have worked. After 2 weeks of actually using the right module (*sheepish grin*) I've not had the card popup the above error message. woo. So thanks for that. :) Majorly happy about things now. :) And now... to put ext3 on my laptop. -- CaT ([EMAIL PROTECTED])*** Jenna has joined the channel. cat speaking of mental giants.. Jenna me, a giant, bullshit Jenna And i'm not mental - An IRC session, 20/12/2000 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Tue, Feb 20, 2001 at 02:00:31AM -0800, Ion Badulescu wrote: > Are you sure this driver has my patch applied? There is no way you could > have gotten these messages without getting the other printk as well.. > > Can you check it again, please? *sigh* too much kernel bouncing. I got the right kernel this time. applied the patch and I'm off again. sorry about that. whacky day. :/ -- CaT ([EMAIL PROTECTED])*** Jenna has joined the channel. speaking of mental giants.. me, a giant, bullshit And i'm not mental - An IRC session, 20/12/2000 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Tue, 20 Feb 2001, CaT wrote: > > patched, old removed, new installed, waiting for fubar. :) > > Ok. this is what I got in my kern.log. this is on a fresh reboot. > > Feb 20 18:31:49 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout >with(0x70)! > Feb 20 18:31:49 theirongiant kernel: eepro100: cmd_wait for(0x10) timedout >with(0x10)! > Feb 20 18:31:49 theirongiant kernel: eepro100: cmd_wait for(0xff90) timedout >with(0xff90)! > Feb 20 18:32:21 theirongiant last message repeated 29 times > Feb 20 18:33:15 theirongiant last message repeated 31 times Are you sure this driver has my patch applied? There is no way you could have gotten these messages without getting the other printk as well.. Can you check it again, please? Thanks, Ion -- It is better to keep your mouth shut and be thought a fool, than to open it and remove all doubt. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Tue, 20 Feb 2001, CaT wrote: patched, old removed, new installed, waiting for fubar. :) Ok. this is what I got in my kern.log. this is on a fresh reboot. Feb 20 18:31:49 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout with(0x70)! Feb 20 18:31:49 theirongiant kernel: eepro100: cmd_wait for(0x10) timedout with(0x10)! Feb 20 18:31:49 theirongiant kernel: eepro100: cmd_wait for(0xff90) timedout with(0xff90)! Feb 20 18:32:21 theirongiant last message repeated 29 times Feb 20 18:33:15 theirongiant last message repeated 31 times Are you sure this driver has my patch applied? There is no way you could have gotten these messages without getting the other printk as well.. Can you check it again, please? Thanks, Ion -- It is better to keep your mouth shut and be thought a fool, than to open it and remove all doubt. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Tue, Feb 20, 2001 at 02:00:31AM -0800, Ion Badulescu wrote: Are you sure this driver has my patch applied? There is no way you could have gotten these messages without getting the other printk as well.. Can you check it again, please? *sigh* too much kernel bouncing. I got the right kernel this time. applied the patch and I'm off again. sorry about that. whacky day. :/ -- CaT ([EMAIL PROTECTED])*** Jenna has joined the channel. cat speaking of mental giants.. Jenna me, a giant, bullshit Jenna And i'm not mental - An IRC session, 20/12/2000 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Tue, Feb 20, 2001 at 11:31:52AM +1100, CaT wrote: > On Mon, Feb 19, 2001 at 04:18:40PM -0800, Ion Badulescu wrote: > > > In my experiments wait_for_cmd timeouts almost always were related to > > > DumpStats command. > > > I think, we need to investigate what time constraints are related to this > > > command. > > > > Nothing documented... > > > > CaT, can you apply this debugging patch and let us know what you get in the > > logs? It should allow us to pinpoint the error a bit more precisely. > > patched, old removed, new installed, waiting for fubar. :) Ok. this is what I got in my kern.log. this is on a fresh reboot. Feb 20 18:31:49 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout with(0x70)! Feb 20 18:31:49 theirongiant kernel: eepro100: cmd_wait for(0x10) timedout with(0x10)! Feb 20 18:31:49 theirongiant kernel: eepro100: cmd_wait for(0xff90) timedout with(0xff90)! Feb 20 18:32:21 theirongiant last message repeated 29 times Feb 20 18:33:15 theirongiant last message repeated 31 times Feb 20 18:33:16 theirongiant kernel: eth0: Transmit timed out: status 0c90 at 0/63 command 0001a000. Feb 20 18:33:16 theirongiant kernel: eth0: Tx ring dump, Tx queue 63 / 0: Feb 20 18:33:16 theirongiant kernel: eth0: * 0 0001a000. Feb 20 18:33:16 theirongiant kernel: eth0: 1 0002. Feb 20 18:33:16 theirongiant kernel: eth0: 2 0003. Feb 20 18:33:16 theirongiant kernel: eth0: 3 0003. Feb 20 18:33:16 theirongiant kernel: eth0: 4 0003. Feb 20 18:33:16 theirongiant kernel: eth0: 5 0003. Feb 20 18:33:16 theirongiant kernel: eth0: 6 0003. Feb 20 18:33:16 theirongiant kernel: eth0: 7 0003. Feb 20 18:33:16 theirongiant kernel: eth0: 8 0002. Feb 20 18:33:16 theirongiant kernel: eth0: 9 0003. Feb 20 18:33:16 theirongiant kernel: eth0:10 0003. Feb 20 18:33:16 theirongiant kernel: eth0:11 0003. Feb 20 18:33:16 theirongiant kernel: eth0:12 0003. Feb 20 18:33:16 theirongiant kernel: eth0:13 000c. Feb 20 18:33:16 theirongiant kernel: eth0:14 000c. Feb 20 18:33:16 theirongiant kernel: eth0:15 0003. Feb 20 18:33:16 theirongiant kernel: eth0:16 200c. Feb 20 18:33:16 theirongiant kernel: eth0:17 000c. Feb 20 18:33:16 theirongiant kernel: eth0:18 0003. Feb 20 18:33:16 theirongiant kernel: eth0:19 000c. Feb 20 18:33:16 theirongiant kernel: eth0:20 000c. Feb 20 18:33:16 theirongiant kernel: eth0:21 0003. Feb 20 18:33:16 theirongiant kernel: eth0:22 0003. Feb 20 18:33:16 theirongiant kernel: eth0:23 0003. Feb 20 18:33:16 theirongiant kernel: eth0:24 0003. Feb 20 18:33:16 theirongiant kernel: eth0:25 0003. Feb 20 18:33:16 theirongiant kernel: eth0:26 0003. Feb 20 18:33:16 theirongiant kernel: eth0:27 0003. Feb 20 18:33:16 theirongiant kernel: eth0:28 0003. Feb 20 18:33:16 theirongiant kernel: eth0:29 0003. Feb 20 18:33:16 theirongiant kernel: eth0:30 0003. Feb 20 18:33:16 theirongiant kernel: eth0:31 0003. Feb 20 18:33:16 theirongiant kernel: eth0:32 0003. Feb 20 18:33:16 theirongiant kernel: eth0:33 0003. Feb 20 18:33:16 theirongiant kernel: eth0:34 0003. Feb 20 18:33:16 theirongiant kernel: eth0:35 0003. Feb 20 18:33:16 theirongiant kernel: eth0:36 0003. Feb 20 18:33:16 theirongiant kernel: eth0:37 0003. Feb 20 18:33:16 theirongiant kernel: eth0:38 0003. Feb 20 18:33:16 theirongiant kernel: eth0:39 0003. Feb 20 18:33:16 theirongiant kernel: eth0:40 0003. Feb 20 18:33:16 theirongiant kernel: eth0:41 0003. Feb 20 18:33:16 theirongiant kernel: eth0:42 0003. Feb 20 18:33:16 theirongiant kernel: eth0:43 0003. Feb 20 18:33:16 theirongiant kernel: eth0:44 0003. Feb 20 18:33:16 theirongiant kernel: eth0:45 0003. Feb 20 18:33:16 theirongiant kernel: eth0:46 0003. Feb 20 18:33:16 theirongiant kernel: eth0:47 0003. Feb 20 18:33:16 theirongiant kernel: eth0:48 0003. Feb 20 18:33:16 theirongiant kernel: eth0:49 0003. Feb 20 18:33:16 theirongiant kernel: eth0:50 0003. Feb 20 18:33:16 theirongiant kernel: eth0:51 0003. Feb 20 18:33:16 theirongiant kernel: eth0:52 0003. Feb 20 18:33:16 theirongiant kernel: eth0:53 0003. Feb 20 18:33:16 theirongiant kernel: eth0:54 0003. Feb 20 18:33:16 theirongiant kernel: eth0:55 000c. Feb 20 18:33:16 theirongiant kernel: eth0:56 000c. Feb 20 18:33:16 theirongiant kernel: eth0:57 0003. Feb 20 18:33:16 theirongiant kernel: eth0:58 000c. Feb 20 18:33:16 theirongiant kernel: eth0:59 000c. Feb 20 18:33:16 theirongiant kernel: eth0:60 0003. Feb 20 18:33:16 theirongiant kernel: eth0:61 0003. Feb 20 18:33:16 theirongiant kernel: eth0:62 4003. Feb 20 18:33:16 theirongiant kernel: eth0: =63 . Feb 20
Re: eepro100 + 2.2.18 + laptop problems
On Mon, Feb 19, 2001 at 04:18:40PM -0800, Ion Badulescu wrote: > > In my experiments wait_for_cmd timeouts almost always were related to > > DumpStats command. > > I think, we need to investigate what time constraints are related to this > > command. > > Nothing documented... > > CaT, can you apply this debugging patch and let us know what you get in the > logs? It should allow us to pinpoint the error a bit more precisely. patched, old removed, new installed, waiting for fubar. :) still with 2.2.18 -- CaT ([EMAIL PROTECTED])*** Jenna has joined the channel. speaking of mental giants.. me, a giant, bullshit And i'm not mental - An IRC session, 20/12/2000 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Mon, 19 Feb 2001 14:49:35 -0800, Andrey Savochkin <[EMAIL PROTECTED]> wrote:
> On Tue, Feb 20, 2001 at 09:21:06AM +1100, CaT wrote:
>>
>> It happened again. Same deal. Once was after a reboot and this time
>> was after a resume. :/
>
> In my experiments wait_for_cmd timeouts almost always were related to
> DumpStats command.
> I think, we need to investigate what time constraints are related to this
> command.
Nothing documented...
CaT, can you apply this debugging patch and let us know what you get in the
logs? It should allow us to pinpoint the error a bit more precisely.
Thanks,
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
--
--- /mnt/3/linux-2.2.19pre/drivers/net/eepro100.c Thu Feb 15 16:09:19 2001
+++ linux-2.2.18/drivers/net/eepro100.c Mon Feb 19 16:13:45 2001
@@ -368,9 +368,16 @@
#define outl writel
#endif
+static char *cmdwait_string = "wait_for_cmd_done timed out at %s:%d\n";
+#define wait_for_cmd_done(ioaddr) \
+ do { \
+if (do_wait_for_cmd_done(ioaddr)) \
+ printk(cmdwait_string, __FUNCTION__, __LINE__); \
+ } while (0)
+
/* How to wait for the command unit to accept a command.
Typically this takes 0 ticks. */
-static inline void wait_for_cmd_done(long cmd_ioaddr)
+static inline int do_wait_for_cmd_done(long cmd_ioaddr)
{
int wait = 2;
char cmd_reg1, cmd_reg2;
@@ -383,10 +390,10 @@
if(cmd_reg2){
printk(KERN_ALERT "eepro100: cmd_wait for(%#2.2x) timedout
with(%#2.2x)!\n",
cmd_reg1, cmd_reg2);
-
+ return 1;
}
}
-
+ return 0;
}
/* Offsets to the various registers.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
Hi, On Tue, Feb 20, 2001 at 09:21:06AM +1100, CaT wrote: > On Tue, Feb 13, 2001 at 03:14:09PM +1100, CaT wrote: > > On Tue, Feb 13, 2001 at 09:26:38AM +0800, Andrey Savochkin wrote: > > > On Sun, Feb 11, 2001 at 10:40:33PM +1100, CaT wrote: > > > [snip] > > > > Feb 11 22:30:18 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout >with(0x70)! > > > > > > Please try the attached patch. > > > Actually, it's designed to solve another problem, but may be your one has the > > > same origin as that other. > > > > Cool. Thanks. I recompiled the module and am trying it now. So far the > > ethernet connection is fine but the above problem isn't reproducable with > > 100% accuracy and so it'll take me a wee while before I decide ' > > a... that rocks my boat. it's fixed.'. :) > > It happened again. Same deal. Once was after a reboot and this time > was after a resume. :/ In my experiments wait_for_cmd timeouts almost always were related to DumpStats command. I think, we need to investigate what time constraints are related to this command. Best regards Andrey - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Mon, Feb 19, 2001 at 03:44:10PM -0800, Dragan Stancevic wrote: > On Tue, Feb 20, 2001, CaT <[EMAIL PROTECTED]> wrote: > ; > ; None. This is before any traffic gets put through it. At worst the > ; card has the wrong IP for the network but that is not always the case > ; from memory. > > So where does that card get the address from, are you doing DHCP? Set manually. In debian-speak: ifup eth0 where: iface eth0 inet static address 10.1.1.2 netmask 255.255.255.0 network 10.1.1.0 broadcast 10.1.1.255 gateway 10.1.1.1 So basically that does an ifconfig and route command I believe (or the equivalent) -- CaT ([EMAIL PROTECTED])*** Jenna has joined the channel. speaking of mental giants.. me, a giant, bullshit And i'm not mental - An IRC session, 20/12/2000 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Tue, Feb 20, 2001, CaT <[EMAIL PROTECTED]> wrote: ; ; None. This is before any traffic gets put through it. At worst the ; card has the wrong IP for the network but that is not always the case ; from memory. So where does that card get the address from, are you doing DHCP? -- No Kernel Hackers were harmed during writing of this email. -Dragan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Mon, Feb 19, 2001 at 03:37:02PM -0800, Dragan Stancevic wrote: > On Tue, Feb 20, 2001, CaT <[EMAIL PROTECTED]> wrote: > ; > 100% accuracy and so it'll take me a wee while before I decide ' > ; > a... that rocks my boat. it's fixed.'. :) > ; > ; It happened again. Same deal. Once was after a reboot and this time > ; was after a resume. :/ > > What kind of trafic are you running? None. This is before any traffic gets put through it. At worst the card has the wrong IP for the network but that is not always the case from memory. -- CaT ([EMAIL PROTECTED])*** Jenna has joined the channel. speaking of mental giants.. me, a giant, bullshit And i'm not mental - An IRC session, 20/12/2000 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Tue, Feb 20, 2001, CaT <[EMAIL PROTECTED]> wrote: ; > 100% accuracy and so it'll take me a wee while before I decide ' ; > a... that rocks my boat. it's fixed.'. :) ; ; It happened again. Same deal. Once was after a reboot and this time ; was after a resume. :/ What kind of trafic are you running? -- No Kernel Hackers were harmed during writing of this email. -Dragan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Tue, Feb 13, 2001 at 03:14:09PM +1100, CaT wrote: > On Tue, Feb 13, 2001 at 09:26:38AM +0800, Andrey Savochkin wrote: > > On Sun, Feb 11, 2001 at 10:40:33PM +1100, CaT wrote: > > [snip] > > > Feb 11 22:30:18 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout >with(0x70)! > > > > Please try the attached patch. > > Actually, it's designed to solve another problem, but may be your one has the > > same origin as that other. > > Cool. Thanks. I recompiled the module and am trying it now. So far the > ethernet connection is fine but the above problem isn't reproducable with > 100% accuracy and so it'll take me a wee while before I decide ' > a... that rocks my boat. it's fixed.'. :) It happened again. Same deal. Once was after a reboot and this time was after a resume. :/ Help? -- CaT ([EMAIL PROTECTED])*** Jenna has joined the channel. speaking of mental giants.. me, a giant, bullshit And i'm not mental - An IRC session, 20/12/2000 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Tue, Feb 13, 2001 at 03:14:09PM +1100, CaT wrote: On Tue, Feb 13, 2001 at 09:26:38AM +0800, Andrey Savochkin wrote: On Sun, Feb 11, 2001 at 10:40:33PM +1100, CaT wrote: [snip] Feb 11 22:30:18 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout with(0x70)! Please try the attached patch. Actually, it's designed to solve another problem, but may be your one has the same origin as that other. Cool. Thanks. I recompiled the module and am trying it now. So far the ethernet connection is fine but the above problem isn't reproducable with 100% accuracy and so it'll take me a wee while before I decide ' a... that rocks my boat. it's fixed.'. :) It happened again. Same deal. Once was after a reboot and this time was after a resume. :/ Help? -- CaT ([EMAIL PROTECTED])*** Jenna has joined the channel. cat speaking of mental giants.. Jenna me, a giant, bullshit Jenna And i'm not mental - An IRC session, 20/12/2000 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Tue, Feb 20, 2001, CaT [EMAIL PROTECTED] wrote: ; 100% accuracy and so it'll take me a wee while before I decide ' ; a... that rocks my boat. it's fixed.'. :) ; ; It happened again. Same deal. Once was after a reboot and this time ; was after a resume. :/ What kind of trafic are you running? -- No Kernel Hackers were harmed during writing of this email. -Dragan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Mon, Feb 19, 2001 at 03:37:02PM -0800, Dragan Stancevic wrote: On Tue, Feb 20, 2001, CaT [EMAIL PROTECTED] wrote: ; 100% accuracy and so it'll take me a wee while before I decide ' ; a... that rocks my boat. it's fixed.'. :) ; ; It happened again. Same deal. Once was after a reboot and this time ; was after a resume. :/ What kind of trafic are you running? None. This is before any traffic gets put through it. At worst the card has the wrong IP for the network but that is not always the case from memory. -- CaT ([EMAIL PROTECTED])*** Jenna has joined the channel. cat speaking of mental giants.. Jenna me, a giant, bullshit Jenna And i'm not mental - An IRC session, 20/12/2000 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Tue, Feb 20, 2001, CaT [EMAIL PROTECTED] wrote: ; ; None. This is before any traffic gets put through it. At worst the ; card has the wrong IP for the network but that is not always the case ; from memory. So where does that card get the address from, are you doing DHCP? -- No Kernel Hackers were harmed during writing of this email. -Dragan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Mon, Feb 19, 2001 at 03:44:10PM -0800, Dragan Stancevic wrote: On Tue, Feb 20, 2001, CaT [EMAIL PROTECTED] wrote: ; ; None. This is before any traffic gets put through it. At worst the ; card has the wrong IP for the network but that is not always the case ; from memory. So where does that card get the address from, are you doing DHCP? Set manually. In debian-speak: ifup eth0 where: iface eth0 inet static address 10.1.1.2 netmask 255.255.255.0 network 10.1.1.0 broadcast 10.1.1.255 gateway 10.1.1.1 So basically that does an ifconfig and route command I believe (or the equivalent) -- CaT ([EMAIL PROTECTED])*** Jenna has joined the channel. cat speaking of mental giants.. Jenna me, a giant, bullshit Jenna And i'm not mental - An IRC session, 20/12/2000 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
Hi, On Tue, Feb 20, 2001 at 09:21:06AM +1100, CaT wrote: On Tue, Feb 13, 2001 at 03:14:09PM +1100, CaT wrote: On Tue, Feb 13, 2001 at 09:26:38AM +0800, Andrey Savochkin wrote: On Sun, Feb 11, 2001 at 10:40:33PM +1100, CaT wrote: [snip] Feb 11 22:30:18 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout with(0x70)! Please try the attached patch. Actually, it's designed to solve another problem, but may be your one has the same origin as that other. Cool. Thanks. I recompiled the module and am trying it now. So far the ethernet connection is fine but the above problem isn't reproducable with 100% accuracy and so it'll take me a wee while before I decide ' a... that rocks my boat. it's fixed.'. :) It happened again. Same deal. Once was after a reboot and this time was after a resume. :/ In my experiments wait_for_cmd timeouts almost always were related to DumpStats command. I think, we need to investigate what time constraints are related to this command. Best regards Andrey - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Mon, 19 Feb 2001 14:49:35 -0800, Andrey Savochkin [EMAIL PROTECTED] wrote:
On Tue, Feb 20, 2001 at 09:21:06AM +1100, CaT wrote:
It happened again. Same deal. Once was after a reboot and this time
was after a resume. :/
In my experiments wait_for_cmd timeouts almost always were related to
DumpStats command.
I think, we need to investigate what time constraints are related to this
command.
Nothing documented...
CaT, can you apply this debugging patch and let us know what you get in the
logs? It should allow us to pinpoint the error a bit more precisely.
Thanks,
Ion
--
It is better to keep your mouth shut and be thought a fool,
than to open it and remove all doubt.
--
--- /mnt/3/linux-2.2.19pre/drivers/net/eepro100.c Thu Feb 15 16:09:19 2001
+++ linux-2.2.18/drivers/net/eepro100.c Mon Feb 19 16:13:45 2001
@@ -368,9 +368,16 @@
#define outl writel
#endif
+static char *cmdwait_string = "wait_for_cmd_done timed out at %s:%d\n";
+#define wait_for_cmd_done(ioaddr) \
+ do { \
+if (do_wait_for_cmd_done(ioaddr)) \
+ printk(cmdwait_string, __FUNCTION__, __LINE__); \
+ } while (0)
+
/* How to wait for the command unit to accept a command.
Typically this takes 0 ticks. */
-static inline void wait_for_cmd_done(long cmd_ioaddr)
+static inline int do_wait_for_cmd_done(long cmd_ioaddr)
{
int wait = 2;
char cmd_reg1, cmd_reg2;
@@ -383,10 +390,10 @@
if(cmd_reg2){
printk(KERN_ALERT "eepro100: cmd_wait for(%#2.2x) timedout
with(%#2.2x)!\n",
cmd_reg1, cmd_reg2);
-
+ return 1;
}
}
-
+ return 0;
}
/* Offsets to the various registers.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Mon, Feb 19, 2001 at 04:18:40PM -0800, Ion Badulescu wrote: In my experiments wait_for_cmd timeouts almost always were related to DumpStats command. I think, we need to investigate what time constraints are related to this command. Nothing documented... CaT, can you apply this debugging patch and let us know what you get in the logs? It should allow us to pinpoint the error a bit more precisely. patched, old removed, new installed, waiting for fubar. :) still with 2.2.18 -- CaT ([EMAIL PROTECTED])*** Jenna has joined the channel. cat speaking of mental giants.. Jenna me, a giant, bullshit Jenna And i'm not mental - An IRC session, 20/12/2000 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Tue, Feb 20, 2001 at 11:31:52AM +1100, CaT wrote: On Mon, Feb 19, 2001 at 04:18:40PM -0800, Ion Badulescu wrote: In my experiments wait_for_cmd timeouts almost always were related to DumpStats command. I think, we need to investigate what time constraints are related to this command. Nothing documented... CaT, can you apply this debugging patch and let us know what you get in the logs? It should allow us to pinpoint the error a bit more precisely. patched, old removed, new installed, waiting for fubar. :) Ok. this is what I got in my kern.log. this is on a fresh reboot. Feb 20 18:31:49 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout with(0x70)! Feb 20 18:31:49 theirongiant kernel: eepro100: cmd_wait for(0x10) timedout with(0x10)! Feb 20 18:31:49 theirongiant kernel: eepro100: cmd_wait for(0xff90) timedout with(0xff90)! Feb 20 18:32:21 theirongiant last message repeated 29 times Feb 20 18:33:15 theirongiant last message repeated 31 times Feb 20 18:33:16 theirongiant kernel: eth0: Transmit timed out: status 0c90 at 0/63 command 0001a000. Feb 20 18:33:16 theirongiant kernel: eth0: Tx ring dump, Tx queue 63 / 0: Feb 20 18:33:16 theirongiant kernel: eth0: * 0 0001a000. Feb 20 18:33:16 theirongiant kernel: eth0: 1 0002. Feb 20 18:33:16 theirongiant kernel: eth0: 2 0003. Feb 20 18:33:16 theirongiant kernel: eth0: 3 0003. Feb 20 18:33:16 theirongiant kernel: eth0: 4 0003. Feb 20 18:33:16 theirongiant kernel: eth0: 5 0003. Feb 20 18:33:16 theirongiant kernel: eth0: 6 0003. Feb 20 18:33:16 theirongiant kernel: eth0: 7 0003. Feb 20 18:33:16 theirongiant kernel: eth0: 8 0002. Feb 20 18:33:16 theirongiant kernel: eth0: 9 0003. Feb 20 18:33:16 theirongiant kernel: eth0:10 0003. Feb 20 18:33:16 theirongiant kernel: eth0:11 0003. Feb 20 18:33:16 theirongiant kernel: eth0:12 0003. Feb 20 18:33:16 theirongiant kernel: eth0:13 000c. Feb 20 18:33:16 theirongiant kernel: eth0:14 000c. Feb 20 18:33:16 theirongiant kernel: eth0:15 0003. Feb 20 18:33:16 theirongiant kernel: eth0:16 200c. Feb 20 18:33:16 theirongiant kernel: eth0:17 000c. Feb 20 18:33:16 theirongiant kernel: eth0:18 0003. Feb 20 18:33:16 theirongiant kernel: eth0:19 000c. Feb 20 18:33:16 theirongiant kernel: eth0:20 000c. Feb 20 18:33:16 theirongiant kernel: eth0:21 0003. Feb 20 18:33:16 theirongiant kernel: eth0:22 0003. Feb 20 18:33:16 theirongiant kernel: eth0:23 0003. Feb 20 18:33:16 theirongiant kernel: eth0:24 0003. Feb 20 18:33:16 theirongiant kernel: eth0:25 0003. Feb 20 18:33:16 theirongiant kernel: eth0:26 0003. Feb 20 18:33:16 theirongiant kernel: eth0:27 0003. Feb 20 18:33:16 theirongiant kernel: eth0:28 0003. Feb 20 18:33:16 theirongiant kernel: eth0:29 0003. Feb 20 18:33:16 theirongiant kernel: eth0:30 0003. Feb 20 18:33:16 theirongiant kernel: eth0:31 0003. Feb 20 18:33:16 theirongiant kernel: eth0:32 0003. Feb 20 18:33:16 theirongiant kernel: eth0:33 0003. Feb 20 18:33:16 theirongiant kernel: eth0:34 0003. Feb 20 18:33:16 theirongiant kernel: eth0:35 0003. Feb 20 18:33:16 theirongiant kernel: eth0:36 0003. Feb 20 18:33:16 theirongiant kernel: eth0:37 0003. Feb 20 18:33:16 theirongiant kernel: eth0:38 0003. Feb 20 18:33:16 theirongiant kernel: eth0:39 0003. Feb 20 18:33:16 theirongiant kernel: eth0:40 0003. Feb 20 18:33:16 theirongiant kernel: eth0:41 0003. Feb 20 18:33:16 theirongiant kernel: eth0:42 0003. Feb 20 18:33:16 theirongiant kernel: eth0:43 0003. Feb 20 18:33:16 theirongiant kernel: eth0:44 0003. Feb 20 18:33:16 theirongiant kernel: eth0:45 0003. Feb 20 18:33:16 theirongiant kernel: eth0:46 0003. Feb 20 18:33:16 theirongiant kernel: eth0:47 0003. Feb 20 18:33:16 theirongiant kernel: eth0:48 0003. Feb 20 18:33:16 theirongiant kernel: eth0:49 0003. Feb 20 18:33:16 theirongiant kernel: eth0:50 0003. Feb 20 18:33:16 theirongiant kernel: eth0:51 0003. Feb 20 18:33:16 theirongiant kernel: eth0:52 0003. Feb 20 18:33:16 theirongiant kernel: eth0:53 0003. Feb 20 18:33:16 theirongiant kernel: eth0:54 0003. Feb 20 18:33:16 theirongiant kernel: eth0:55 000c. Feb 20 18:33:16 theirongiant kernel: eth0:56 000c. Feb 20 18:33:16 theirongiant kernel: eth0:57 0003. Feb 20 18:33:16 theirongiant kernel: eth0:58 000c. Feb 20 18:33:16 theirongiant kernel: eth0:59 000c. Feb 20 18:33:16 theirongiant kernel: eth0:60 0003. Feb 20 18:33:16 theirongiant kernel: eth0:61 0003. Feb 20 18:33:16 theirongiant kernel: eth0:62 4003. Feb 20 18:33:16 theirongiant kernel: eth0: =63 . Feb 20 18:33:16 theirongiant
Re: eepro100 + 2.2.18 + laptop problems
On Tue, Feb 13, 2001 at 09:26:38AM +0800, Andrey Savochkin wrote: > On Sun, Feb 11, 2001 at 10:40:33PM +1100, CaT wrote: > [snip] > > Feb 11 22:30:18 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout >with(0x70)! > > Please try the attached patch. > Actually, it's designed to solve another problem, but may be your one has the > same origin as that other. Cool. Thanks. I recompiled the module and am trying it now. So far the ethernet connection is fine but the above problem isn't reproducable with 100% accuracy and so it'll take me a wee while before I decide ' a... that rocks my boat. it's fixed.'. :) As such I'll try to give you a holler either in a few weeks time (if nothing happens) or as soon as it breaks again. -- CaT ([EMAIL PROTECTED])*** Jenna has joined the channel. speaking of mental giants.. me, a giant, bullshit And i'm not mental - An IRC session, 20/12/2000 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://vger.kernel.org/lkml/
Re: eepro100 + 2.2.18 + laptop problems
On Sun, Feb 11, 2001 at 10:40:33PM +1100, CaT wrote: [snip] > Feb 11 22:30:18 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout >with(0x70)! Please try the attached patch. Actually, it's designed to solve another problem, but may be your one has the same origin as that other. Best regards Andrey Index: eepro100.c === RCS file: /home/oursoft/eepro100/eepro100.c,v retrieving revision 1.20.2.13 diff -u -r1.20.2.13 eepro100.c --- eepro100.c 2000/09/14 04:41:58 1.20.2.13 +++ eepro100.c 2001/02/13 01:22:07 @@ -726,6 +726,7 @@ This takes less than 10usec and will easily finish before the next action. */ outl(PortReset, ioaddr + SCBPort); + inl(ioaddr + SCBPort); /* Honor PortReset timing. */ udelay(10); @@ -814,6 +815,7 @@ #endif /* kernel_bloat */ outl(PortReset, ioaddr + SCBPort); + inl(ioaddr + SCBPort); /* Honor PortReset timing. */ udelay(10); @@ -1037,6 +1039,9 @@ /* Set the segment registers to '0'. */ wait_for_cmd_done(ioaddr + SCBCmd); outl(0, ioaddr + SCBPointer); + /* impose a delay to avoid a bug */ + inl(ioaddr + SCBPointer); + udelay(10); outb(RxAddrLoad, ioaddr + SCBCmd); wait_for_cmd_done(ioaddr + SCBCmd); outb(CUCmdBase, ioaddr + SCBCmd); @@ -1298,6 +1303,7 @@ end_bh_atomic(); /* Reset the Tx and Rx units. */ outl(PortReset, ioaddr + SCBPort); + inl(ioaddr + SCBPort); /* We may get spurious interrupts here. But I don't think that they may do much harm. 1999/12/09 SAW */ udelay(10);
Re: eepro100 + 2.2.18 + laptop problems
On Sun, Feb 11, 2001 at 10:40:33PM +1100, CaT wrote: [snip] Feb 11 22:30:18 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout with(0x70)! Please try the attached patch. Actually, it's designed to solve another problem, but may be your one has the same origin as that other. Best regards Andrey Index: eepro100.c === RCS file: /home/oursoft/eepro100/eepro100.c,v retrieving revision 1.20.2.13 diff -u -r1.20.2.13 eepro100.c --- eepro100.c 2000/09/14 04:41:58 1.20.2.13 +++ eepro100.c 2001/02/13 01:22:07 @@ -726,6 +726,7 @@ This takes less than 10usec and will easily finish before the next action. */ outl(PortReset, ioaddr + SCBPort); + inl(ioaddr + SCBPort); /* Honor PortReset timing. */ udelay(10); @@ -814,6 +815,7 @@ #endif /* kernel_bloat */ outl(PortReset, ioaddr + SCBPort); + inl(ioaddr + SCBPort); /* Honor PortReset timing. */ udelay(10); @@ -1037,6 +1039,9 @@ /* Set the segment registers to '0'. */ wait_for_cmd_done(ioaddr + SCBCmd); outl(0, ioaddr + SCBPointer); + /* impose a delay to avoid a bug */ + inl(ioaddr + SCBPointer); + udelay(10); outb(RxAddrLoad, ioaddr + SCBCmd); wait_for_cmd_done(ioaddr + SCBCmd); outb(CUCmdBase, ioaddr + SCBCmd); @@ -1298,6 +1303,7 @@ end_bh_atomic(); /* Reset the Tx and Rx units. */ outl(PortReset, ioaddr + SCBPort); + inl(ioaddr + SCBPort); /* We may get spurious interrupts here. But I don't think that they may do much harm. 1999/12/09 SAW */ udelay(10);
Re: eepro100 + 2.2.18 + laptop problems
On Tue, Feb 13, 2001 at 09:26:38AM +0800, Andrey Savochkin wrote: On Sun, Feb 11, 2001 at 10:40:33PM +1100, CaT wrote: [snip] Feb 11 22:30:18 theirongiant kernel: eepro100: cmd_wait for(0x70) timedout with(0x70)! Please try the attached patch. Actually, it's designed to solve another problem, but may be your one has the same origin as that other. Cool. Thanks. I recompiled the module and am trying it now. So far the ethernet connection is fine but the above problem isn't reproducable with 100% accuracy and so it'll take me a wee while before I decide ' a... that rocks my boat. it's fixed.'. :) As such I'll try to give you a holler either in a few weeks time (if nothing happens) or as soon as it breaks again. -- CaT ([EMAIL PROTECTED])*** Jenna has joined the channel. cat speaking of mental giants.. Jenna me, a giant, bullshit Jenna And i'm not mental - An IRC session, 20/12/2000 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://vger.kernel.org/lkml/
