Search String: Display: Description: Sort:

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[vortex\]\s+can\'t\s+unload\s+module\s*$/: 14 ]

Total 14 documents matching your query.

1. Re: [vortex] can't unload module (score: 1)
Author: xxxxxx>
Date: Fri, 22 Sep 2000 23:36:30 +1100
[ added netdev ] This is unfamiliar and it does sound like a driver problem. Does it do this under kernel 2.2? Could you please do some further investigation? Try increasing the driver debug level, l
/archives/netdev/2000-09/msg00108.html (10,430 bytes)

2. Re: [vortex] can't unload module (score: 1)
Author: xxxxxx>
Date: Sat, 23 Sep 2000 02:35:21 +1100
Duh. schedule() drops the BKL.
/archives/netdev/2000-09/msg00109.html (7,699 bytes)

3. Re: [vortex] can't unload module (score: 1)
Author: xxxxxx>
Date: Fri, 22 Sep 2000 15:39:00 -0500
yes I'm going to say there are two problems, 'net drop out' and 'unregister_netdevice'. 'net drop out' problem, There are two stages, reduced network and no network. For example when I do a `ping -s
/archives/netdev/2000-09/msg00110.html (14,853 bytes)

4. Re: [vortex] can't unload module (score: 1)
Author: xxxxxx>
Date: Fri, 22 Sep 2000 22:41:20 -0500
It looks like I have to unload the network modules in the opposite order I loaded them. That doesn't sound right. That doesn't look like the case. I implimented the histogram and in boomerang_rx I co
/archives/netdev/2000-09/msg00111.html (10,420 bytes)

5. Re: [vortex] can't unload module (score: 1)
Author: xxxxxx>
Date: Sat, 23 Sep 2000 23:30:59 +1100
This is consistent with an interrupt controller failure. However if this was the case you should be seeing "NETDEV WATCHDOG: eth0: transmit timed out" messages and "interrupt posted but not delivered
/archives/netdev/2000-09/msg00113.html (12,792 bytes)

6. Re: [vortex] can't unload module (score: 1)
Author: xxxxxx>
Date: Sun, 24 Sep 2000 00:46:17 -0500
I've included my latest patch. I've narrowed it do to in boomerange_rx if there is a status field non-null in the entry before says they are completed uploading and set the status fields of all the r
/archives/netdev/2000-09/msg00115.html (17,585 bytes)

7. Re: [vortex] can't unload module (score: 1)
Author: xxxxxx>
Date: Sun, 24 Sep 2000 23:37:52 +1100
It's possible that the NIC is getting into the upload-stalled state when it shouldn't. So the "unneeded" outw(UpUnstall, ioaddr + EL3_CMD); is bringing it back to life. This could be caused by incorr
/archives/netdev/2000-09/msg00117.html (9,378 bytes)

8. Re: [vortex] can't unload module (score: 1)
Author: Andrew Morton <andrewm@xxxxxxxxxx>
Date: Fri, 22 Sep 2000 23:36:30 +1100
[ added netdev ] This is unfamiliar and it does sound like a driver problem. Does it do this under kernel 2.2? Could you please do some further investigation? Try increasing the driver debug level, l
/archives/netdev/2000-09/msg00252.html (10,487 bytes)

9. Re: [vortex] can't unload module (score: 1)
Author: Andrew Morton <andrewm@xxxxxxxxxx>
Date: Sat, 23 Sep 2000 02:35:21 +1100
Duh. schedule() drops the BKL.
/archives/netdev/2000-09/msg00253.html (7,781 bytes)

10. Re: [vortex] can't unload module (score: 1)
Author: David Fries <dfries@xxxxxxx>
Date: Fri, 22 Sep 2000 15:39:00 -0500
yes I'm going to say there are two problems, 'net drop out' and 'unregister_netdevice'. 'net drop out' problem, There are two stages, reduced network and no network. For example when I do a `ping -s
/archives/netdev/2000-09/msg00254.html (15,003 bytes)

11. Re: [vortex] can't unload module (score: 1)
Author: David Fries <dfries@xxxxxxx>
Date: Fri, 22 Sep 2000 22:41:20 -0500
It looks like I have to unload the network modules in the opposite order I loaded them. That doesn't sound right. That doesn't look like the case. I implimented the histogram and in boomerang_rx I co
/archives/netdev/2000-09/msg00255.html (10,602 bytes)

12. Re: [vortex] can't unload module (score: 1)
Author: Andrew Morton <andrewm@xxxxxxxxxx>
Date: Sat, 23 Sep 2000 23:30:59 +1100
This is consistent with an interrupt controller failure. However if this was the case you should be seeing "NETDEV WATCHDOG: eth0: transmit timed out" messages and "interrupt posted but not delivered
/archives/netdev/2000-09/msg00257.html (12,971 bytes)

13. Re: [vortex] can't unload module (score: 1)
Author: David Fries <dfries@xxxxxxx>
Date: Sun, 24 Sep 2000 00:46:17 -0500
I've included my latest patch. I've narrowed it do to in boomerange_rx if there is a status field non-null in the entry before says they are completed uploading and set the status fields of all the r
/archives/netdev/2000-09/msg00259.html (17,814 bytes)

14. Re: [vortex] can't unload module (score: 1)
Author: Andrew Morton <andrewm@xxxxxxxxxx>
Date: Sun, 24 Sep 2000 23:37:52 +1100
It's possible that the NIC is getting into the upload-stalled state when it shouldn't. So the "unneeded" outw(UpUnstall, ioaddr + EL3_CMD); is bringing it back to life. This could be caused by incorr
/archives/netdev/2000-09/msg00261.html (9,636 bytes)


This search system is powered by Namazu