Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 23287 - orinoco_pci wireless driver (WiFi) causes kupdated to consume 100% CPU and stop network from responding
Summary: orinoco_pci wireless driver (WiFi) causes kupdated to consume 100% CPU and st...
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: x86 Linux
: High critical (vote)
Assignee: Peter Johanson (RETIRED)
Depends on:
Reported: 2003-06-22 13:44 UTC by Michael LeMay
Modified: 2003-12-22 07:43 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Note You need to log in before you can comment on or make changes to this bug.
Description Michael LeMay 2003-06-22 13:44:24 UTC
The orinoco_pci driver that comes with both the gentoo-sources kernel and
xfs-sources kernel causes kupdated to frequently start (and never stop until
/etc/init.d/net.eth0 stop; rmmod orinoco_pci; modprobe orinoco_pci) consuming
100% CPU and also causes the network to stop responding.  When I had xfs-sources
installed, I patched the kernel with the latest available orinoco_pci drivers
(can't remember from where) which displayed the same problem.  However, the 2.5
series devel kernels do NOT display this problem, so it most likely lies
somewhere in the kernel besides the driver itself, but the driver somehow breaks
that other area.

Reproducible: Always
Steps to Reproduce:
1. run the orinoco_pci wireless driver
2. use network for anywhere from several minutes to hours
3. see CPU usage hit 100% by kupdated
4. /etc/init.d/net.eth0 stop
5. rmmod orinoco_pci
6. modprobe orinoco_pci
7. goto 1

happens with any variation of software usage, network load, etc. as long as
network resources are at least somewhat frequently accessed (normal WWW browsing
satisfies this)
Comment 1 Andrew Cooks (RETIRED) gentoo-dev 2003-12-04 12:58:48 UTC
This bug hasn't received all the attention it could have. It's been inactive for more than 3 months now. Could you test with the latest kernels, please?

I'm resolving this as TEST-REQUEST. Please reopen if the problem persists.
Comment 2 Michael LeMay 2003-12-22 07:43:08 UTC
This bug has been resolved in kernel v.2.6