Martin Loschwitz <[email protected]> wrote:
>
> On Fri, Aug 05, 2005 at 03:40:26PM -0400, linux-os (Dick Johnson) wrote:
> >
> > On Fri, 5 Aug 2005, Martin Loschwitz wrote:
> >
> > > Hi folks,
> > >
> > > 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?
> > >
> > > Ooops and ksymoops-output is attached.
> > >
> >
> > This can happen if a module is unloaded that doesn't free its
> > resources! Been there, done that.
> >
>
> "This can happen" is not an acceptable explanation, I think.
It's a very accurate one though.
The most common cause of this bug is that some buggy kernel module has been
unloaded. It forgot to release its I/O region. When you later come along
to look in /proc/ioports the kernel goes to fetch information from the
memory which is "owned" by the module which isn't there any more. Crash.
So if you can identify which kernel module was loaded and then unloaded,
we'll fix it up.
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |