On Monday 17 November 2008, David Miller wrote: > Some driver module is unloading without releasing it's held I/O > resources, then something does cat on /proc/iomem or /proc/ioport > and we go splat accessing unmapped memory from that unloaded > driver module. Hmm. Strange. I cannot relate that to what I was doing at that point in the installation. Ah, hang on (imagine me waking up; should maybe have breakfast first...). We also collect info for a hardware summary at that point. It could well be that one of the commands there caused it. ... And that does indeed include a cat of /proc/iomem and /proc/ioports. Now for the difficult part: how do we find out which driver this was? I'll see if I can reproduce while keeping a watch on loaded mods. Cheers, FJP -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
