BUG in sched.c: 698 / Oops in test9-pre7

Amazing quantity of oopsen in test9-pre7. Acres of addresses are printk-ed to my serial terminal, while one oops after another happens. Usually, it happens when Netscape tries talking to our NNTP server over the Tulip (Linux Tulip driver version 0.9.10 (September 6, 2000)) card. It takes about

BUG in sched.c: 698 / Oops in test9-pre7

Amazing quantity of oopsen in test9-pre7. Acres of addresses are printk-ed to my serial terminal, while one oops after another happens. Usually, it happens when Netscape tries talking to our NNTP server over the Tulip (Linux Tulip driver version 0.9.10 (September 6, 2000)) card. It takes about

EEPRO Problems in 2.2.17 (sorry!)

got that message for years now with the eepro driver. If anyone familiar with this driver wishes to work with me in an attempt to reproduce this problem, I'd be happy to help. Thanks, Brian Hayward - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of

Re: GPL violations: make it harder

e an example that's not the same as this one, but brings out issues related to patches and bugfixes ] Say you voluntarily send a patch to a commercial software vendor without specifying any restrictions on using it at that time. I seriously doubt the courts would rule that you are now a part ow

Re: GPL violations: make it harder

s not the same as this one, but brings out issues related to patches and bugfixes ] Say you voluntarily send a patch to a commercial software vendor without specifying any restrictions on using it at that time. I seriously doubt the courts would rule that you are now a part owner of their progr

UPDATE: [Re: eepro driver broke in 2.2.16... (at least for me!)]

I just downloaded the 2.2.17 kernel. This problem seems to be resolved in that version of the eepro driver. Thanks for the new kernel, Alan, Brian Hayward On Mon, 4 Sep 2000 [EMAIL PROTECTED] wrote: > >Hello, > >I just upgraded to the 2.2.16 kernel (from 2.2.14) and compiled a new

eepro driver broke in 2.2.16... (at least for me!)

2.2.16 with the one from 2.2.14 and now it is working perfectly. I'm running the eepro as eth1, irq10, 0x300. I'm running 3c503 as eth0, irq9, 0x330. Has anyone else had this problem? -- Brian Hayward - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of

eepro driver broke in 2.2.16... (at least for me!)

2.2.16 with the one from 2.2.14 and now it is working perfectly. I'm running the eepro as eth1, irq10, 0x300. I'm running 3c503 as eth0, irq9, 0x330. Has anyone else had this problem? -- Brian Hayward - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of

UPDATE: [Re: eepro driver broke in 2.2.16... (at least for me!)]

I just downloaded the 2.2.17 kernel. This problem seems to be resolved in that version of the eepro driver. Thanks for the new kernel, Alan, Brian Hayward On Mon, 4 Sep 2000 [EMAIL PROTECTED] wrote: Hello, I just upgraded to the 2.2.16 kernel (from 2.2.14) and compiled a new kernel. I