From: Marc Ballarin <Ballarin.Marc@gmx.de>
To: Martin Loschwitz <madkiss@madkiss.org>
Cc: chrisw@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: local DDOS? Kernel panic when accessing /proc/ioports
Date: Sat, 6 Aug 2005 01:29:09 +0200 [thread overview]
Message-ID: <20050806012909.618810dd.Ballarin.Marc@gmx.de> (raw)
In-Reply-To: <20050805215247.GA25652@minerva.local.lan>
On Fri, 5 Aug 2005 23:52:47 +0200
Martin Loschwitz <madkiss@madkiss.org> wrote:
>
> The situation in this case is somewhat obscene ... Originally, I had exactly
> this problem while using the Knoppix standard kernel (2.6.11 vanilla SMP). I
> then went to compile 2.6.12.3, also with SMP, and it showed exactly the same
> problem. I disable SMP, tried again -- voila, it worked.
>
> The kernel that I am encountering this error again now is 2.6.12.3 -- without
> SMP or whatsoever. I'm just out of ideas on how to fix it this time.
Did you always use the same machine? If so, can you rule out hardware
issues? Can you reproduce this Oops at will?
I can't reproduce this on various machines (all X86, kernels 2.6.11.9,
2.6.12.2, 2.6.13-rc4-mm1, no SMP)
Regards
next prev parent reply other threads:[~2005-08-05 23:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 19:26 local DDOS? Kernel panic when accessing /proc/ioports Martin Loschwitz
2005-08-05 19:40 ` linux-os (Dick Johnson)
2005-08-05 21:49 ` Martin Loschwitz
2005-08-05 22:33 ` Andrew Morton
2005-08-05 22:42 ` Martin Loschwitz
2005-08-08 6:53 ` Jan Engelhardt
2005-08-08 11:19 ` linux-os (Dick Johnson)
2005-08-05 19:50 ` Chris Wright
2005-08-05 21:52 ` Martin Loschwitz
2005-08-05 23:29 ` Marc Ballarin [this message]
2005-08-05 23:43 ` Martin Loschwitz
2005-08-05 20:03 ` Lee Revell
2005-08-05 21:53 ` Martin Loschwitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050806012909.618810dd.Ballarin.Marc@gmx.de \
--to=ballarin.marc@gmx.de \
--cc=chrisw@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=madkiss@madkiss.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox