Messages in this thread | | | Date | Mon, 1 Mar 2010 10:07:08 +0100 | From | M G Berberich <> | Subject | Re: 2.6.33 dies on modprobe |
| |
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).
To repeat myself: This might be the result of faulty config
MfG bmg
-- „Des is völlig wurscht, was heut beschlos- | M G Berberich sen wird: I bin sowieso dagegn!“ | berberic@fmi.uni-passau.de (SPD-Stadtrat Kurt Schindler; Regensburg) | www.fmi.uni-passau.de/~berberic -- 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/
| |