Messages in this thread | | | Date | Wed, 3 Mar 2010 17:08:16 +0800 | Subject | Re: 2.6.33 dies on modprobe | From | Américo Wang <> |
| |
On Wed, Mar 3, 2010 at 4:58 PM, Américo Wang <xiyou.wangcong@gmail.com> wrote: > On Mon, Mar 1, 2010 at 5:07 PM, M G Berberich > <berberic@fmi.uni-passau.de> wrote: >> Hello, >> >> Am Montag, den 01. März schrieb Américo Wang: >>> On Mon, Mar 1, 2010 at 6:12 AM, M G Berberich >>> <berberic@fmi.uni-passau.de> wrote: >> >>> > I tried to build a 2.6.33 kernel but on boot it dies on modprobe >>> > (kernel-Oops). This might be the result of faulty config, but I'm >>> > totaly clueless what's the fault. >>> > >>> > The kernel starts up fine and mounts the root-filesystem, but then >>> > dies on the first modprobe executed. I can boot it with init=/bin/bash >>> > and get a working bash (until I do modprobe on any module). >>> > >>> > System is a Gigabyte M55S-S3 rev 2.0 (nForce 550) with an AMD Athlon64 >>> > X2 5000+ and amd64-kernel architecture. kernel-sources are from >>> > kernel.org. >> >>> It seems something is wrong with forcedeth code or PCI code. >>> Adding some Cc's. >> >> I don't think it's forcedeth. forcedeth just happens to be the first >> module that get's loaded in startup. It crashes with any other module >> too (I tried ohci_hcd). >> > > Ok, below is my patch, I am not sure it could fix the BUG for you, > but it could fix the WARNING. But perhaps they are related. > > Please give it a try. >
Oops! Ignore the patch, it should not be correct, I will send a correct version soon. Sorry. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |