On Fri, Aug 05, 2005 at 04:03:07PM -0400, Lee Revell wrote: > On Fri, 2005-08-05 at 21:26 +0200, Martin Loschwitz wrote: > > Ooops and ksymoops-output is attached. > > Also, don't use ksymoops for 2.6, it's redundant at best and at worst > actually removes information. Check oops-tracing.txt, the docs have > been updated. > Well, in this case, ksymoops output told me what I wanted to know -- the thing explodes when reading /proc/ioports. I need to know why it does, if the problem might be reproducible for others (that is the possible ddos thing ...) and how to fix it ... > Lee > > - > 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/ -- .''`. Martin Loschwitz Debian GNU/Linux developer : :' : [email protected] [email protected] `. `'` http://www.madkiss.org/ people.debian.org/~madkiss/ `- Use Debian GNU/Linux 3.0! See http://www.debian.org/
Attachment:
signature.asc
Description: Digital signature
- References:
- local DDOS? Kernel panic when accessing /proc/ioports
- From: Martin Loschwitz <[email protected]>
- Re: local DDOS? Kernel panic when accessing /proc/ioports
- From: Lee Revell <[email protected]>
- local DDOS? Kernel panic when accessing /proc/ioports
- Prev by Date: Re: mthca and LinuxBIOS
- Next by Date: RE: [RFC] Demand faulting for large pages
- Previous by thread: Re: local DDOS? Kernel panic when accessing /proc/ioports
- Next by thread: [PATCH] Minor fix to kernel/workqueue.c
- Index(es):
