* Martin Loschwitz ([EMAIL PROTECTED]) wrote: > I just ran into the following problem: Having updated my box to 2.6.12.3, > I tried to start YaST2 and noticed a kernel panic (see below). Some quick > debugging brought the result that the kernel crashes while some user (not > even root ...) tries to access /proc/ioports. Is this a known problem and > if so, is a fix available?
First I've heard of it. I can't trigger here with simple cat /proc/ioports. Must be specific to your setup. What was the last working kernel, and what's that ioport output look like? thanks, -chris - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
