Re: Oops in rtl8139, and more

2001-01-15 Thread Manfred Spraul
The problem is clear: rtl8139_resume() unconditionally restarts the hardware, even if the network was not yet started. The hardware immediately notices something, and sends an interrupt. The oops happens during rtl8139_open(): the function calls request_irq(), but assumes that the interrupts are

Re: Oops in rtl8139, and more

2001-01-15 Thread Manfred Spraul
The problem is clear: rtl8139_resume() unconditionally restarts the hardware, even if the network was not yet started. The hardware immediately notices something, and sends an interrupt. The oops happens during rtl8139_open(): the function calls request_irq(), but assumes that the interrupts are

Oops in rtl8139, and more ...

2001-01-14 Thread Konstantin Cherenkoff
Hello: I have an ADSL Internet connection and use dhcpcd (ver. 1.3.19-pl2) as DHCP client. Everything works OK, but in one particular situation I always get a kernel Oops. Here's how: 1) Boot into runlevel 1 2) Put computer into suspend mode (it wakes up immediately) 3) Change to runlevel 3

Oops in rtl8139, and more ...

2001-01-14 Thread Konstantin Cherenkoff
Hello: I have an ADSL Internet connection and use dhcpcd (ver. 1.3.19-pl2) as DHCP client. Everything works OK, but in one particular situation I always get a kernel Oops. Here's how: 1) Boot into runlevel 1 2) Put computer into suspend mode (it wakes up immediately) 3) Change to runlevel 3