Re: 2.4.1: Abnormal interrupt from RTL8139

2001-02-12 Thread Christian Ullrich
* Jeff Garzik wrote on Sunday, 2001-02-11: > Christian Ullrich wrote: > > I'm getting some of these messages in syslog: > > Feb 6 07:38:35 christian kernel: eth0: Abnormal interrupt, status 0010. > > Feb 6 07:38:35 christian kernel: eth0: Abnormal interrupt, stat

2.4.1: Abnormal interrupt from RTL8139

2001-02-11 Thread Christian Ullrich
bridge PIRQA (link 0x01): irq 10 PIRQB (link 0x02): irq 15 PIRQC (link 0x03): irq 11 PIRQD (link 0x05): irq 9 -- Christian UllrichRegistrierter Linux-User #125183 "Sie können nach R'ed'mond fliegen -- aber Sie werden sterben" - To unsubs

Problem with devfs and Unix98 pty

2001-01-07 Thread Christian Ullrich
HANGE ^pts/.* IGNORE CREATE ^pts/.* IGNORE This fixed the problem for me. If you know a better solution, please let me know. -- Christian UllrichRegistrierter Linux-User #125183 "Sie können nach R'ed'mond fliegen -- aber Sie

Re: Even slower NFS mounting with 2.4.0

2001-01-06 Thread Christian Ullrich
* Christian Ullrich wrote on Saturday, 2000-01-06: > Using 2.2.18, every [NFS] mount took about 15 seconds, now, using 2.4.0, > every mount takes exactly five minutes, which is way too long. Ok, it's fixed now. Thanks to all of you, and especially the (right now) three people who

Even slower NFS mounting with 2.4.0

2001-01-05 Thread Christian Ullrich
ailed, error=-5 Jan 6 00:21:26 c kernel: portmap: server localhost not responding, timed out I called the mount command five minutes before the final message above. I tried NFS with and without NFSv3 code, with no change at all. Please help me. -- Christian UllrichRegistri

Re: insmod problem after modutils upgrading

2000-12-13 Thread Christian Ullrich
parameter debug not found. > how can i make insmod load the network module again pls? I "fixed" the same problem in 2.2.18 by commenting out the line MODULE_PARM (debug, "i"); near the end of drivers/net/8139too.c. Since I run modutils 2.3.22 as well, it can'

Slow NFS mounting with 2.2.18

2000-12-13 Thread Christian Ullrich
.0.2 The server's clock is about one second ahead, so it looks as if the server completed the job in the same second, and the client slept for a while. The mount process stayed in D state all the time. -- Christian UllrichRegistrierter Linux-User #125183 "Sie kön