On the 2.6.7-r13 and 2.6.7-r14 of the gentoo-dev-sources for the AMD64 platform gives and oops when you "modprobe tg3". Once that happens, you can't ever load teh tg3 module (it is a partial load, and gets stuck). When "tg3" is put in the /etc/kernel-autoload.d/.., driver is never loaded. But, if you "modprobe dummy" or load the dummy driver in /etc/kernel-autoload.d/.. then the tg3 driver loads correctly and functions normally. Reproducible: Always Steps to Reproduce: 1.boot 2.modprobe tg3 3.lsmod Actual Results: get 2 pages of debugging info. Shows module is loaded. Hardware doesn't work. Can't remove or retry loading module. Expected Results: No debugging info. Module should load. Hardware should work. System is a dual opteron 240, 2 GB ram, using Tyan S2880 (Thunder K8S) board, U320 SCSI drive. Loaded with 2004.2 LiveCD. Bare minimal installed, not even X. Can reboot system into Gentoo. Don't have it up and running on an accessible network (currently on an isolated install network) or I would provide the "oops" messages for you.
*** Bug 60273 has been marked as a duplicate of this bug. ***
I have the same problem, but loading dummy in 2.6.9-rc2 does NOT help. It also appears to have been reported at http://bugzilla.kernel.org/show_bug.cgi?id=3131
is this still an issue with 2.6.10? otherwise i'd like to close this bug
I am not seeing the problem in the 2.6.10 kernel.
ok, so i'm closing this
