> > [<c01c9e91>] pci_read_bases+0x161/0x340
> > [<c01ca2a6>] pci_setup_device+0x1b6/0x3d0
> > [<c0105109>] init+0x79/0x200
> > [<c0105090>] init+0x0/0x200
> > [<c01073e5>] kernel_thread_helper+0x5/0x10
> >Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 48 c3 8d b4
>
> Something has corrupted your kernel image. Those 16 0x00 bytes are
> definitely not the right code, looks like an errant memset() through a
> wild pointer cleared it or something.
>
> Is this repeatable? Does it happen with current BK?
It is repeatable, it does happen with current BK (well, as of couple
of hours ago) and reverting pci/probe.c change apparently cures it.
-
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/