From: Chuck Ebbert <76306.1226@compuserve.com>
To: Udo van den Heuvel <udovdh@xs4all.nl>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Oops / BUG? (2.6.17.2 on VIA Epia CL6000)
Date: Sun, 2 Jul 2006 15:51:07 -0400 [thread overview]
Message-ID: <200607021553_MC3-1-C400-31EE@compuserve.com> (raw)
In-Reply-To: <44A7AADB.8040106@xs4all.nl>
On Sun, 02 Jul 2006 13:15:39 +0200, Udo van den Heuvel wrote:
> On my otherwise stable Via EPIA CL6000 I experienced an OOPS.
> Hardware should be OK. I was unable to reproduce the event, so far.
> In what part of the kernel did things go wrong?
Your kernel stack has been overwritten with seemingly-random data.
This is impossible to diagnose -- some module possibly scribbled
over the stack.
> Process named (pid: 1431, threadinfo=dd070000 task=ddf61a90)
> EIP: [<52786fdd>] 0x52786fdd SS:ESP 0068:dd071f38
Threadinfo is at dd070000 so end-of-stack is at dd071ff8
dd071ff8 - dd071f38 = 192 (decimal) so there are 192 bytes on the
kernel stack. We can see 192 bytes and there is no sensible regs
information at the end, just random junk.
> What can I do to help fix the bug? (if it is indeed a bug)
Where did these modules come from?
ipt_TARPIT
vt1211
--
Chuck
"You can't read a newspaper if you can't read." --George W. Bush
next reply other threads:[~2006-07-02 19:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-02 19:51 Chuck Ebbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-02 11:15 Oops / BUG? (2.6.17.2 on VIA Epia CL6000) Udo van den Heuvel
2006-07-02 11:21 ` Arjan van de Ven
2006-07-02 11:24 ` Udo van den Heuvel
2006-07-02 11:38 ` Arjan van de Ven
2006-07-02 11:46 ` Udo van den Heuvel
2006-07-02 21:15 ` Jan Engelhardt
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=200607021553_MC3-1-C400-31EE@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=linux-kernel@vger.kernel.org \
--cc=udovdh@xs4all.nl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.