From: Markus <M4rkusXXL@web.de>
To: linux-kernel@vger.kernel.org
Cc: Borislav Petkov <bp@alien8.de>
Subject: Re: BUG: unable to handle kernel paging request
Date: Sun, 23 May 2010 22:44:41 +0200 [thread overview]
Message-ID: <201005232244.41977.M4rkusXXL@web.de> (raw)
In-Reply-To: <20100523183851.GA20229@liondog.tnic>
Hi!
It is 0000000001912178.
http://img256.imageshack.us/img256/4370/shotn.gif
Serial console is no option, but this "netconsole"-thing looks
promising. I'll set that up and try to catch the next one with this.
Thanks, so far
Markus
> From: Markus <M4rkusXXL@web.de>
> Date: Sun, May 23, 2010 at 06:29:32PM +0200
>
> > Hello!
> >
> > I have a system running, now its running a 2.6.34 but it also
> > happend with 2.6.33.x and 2.6.32.x.
> > I hit a BUG and the whole system hang. I had to reboot and the
> > console was to small to show the full BUG.
> > But now I got the framebuffer setup and could write the following
> > dump down (by hand, so there might be some typos or so, I have a
> > "screenshot" if you have a specific question)
> >
> > The system is a amd64 phenom X4 with 2 x 4GB non-ECC RAM and a
> > raid6 for / and a data-partition as well as a raid1 for swap.
> > I ran memtest86+ 4.0 and it showed no errors for two passes.
> >
> > An hour before that BUG I saw a lot of async-processes.
> > It happens round about once a day, will check if its the same or
> > similar the next time.
> >
> > But any hints are greatly appreciated! (How to solve or how to get
> > needed informations.)
> >
> > Thanks,
> > Markus
> >
> > PS: Please CC me.
> >
> >
> > [64112.493940] BUG: unable to handle kernel paging request at
> > 0000000001912178
>
> Ok, I'm looking at that oops and am trying to follow what happens but
> in order for all to fit the 0000000001912178 value above should
> actually be 0000000001912a78, if I'm not mistaken.
>
> Can you please check if that's the case or send me that screenshot
> you mention above. Better yet, can you catch that oops over a serial
> console or a netconsole or similar?
>
> Thanks.
next prev parent reply other threads:[~2010-05-23 20:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-23 16:29 Markus
2010-05-23 18:38 ` Borislav Petkov
2010-05-23 20:44 ` Markus [this message]
2010-05-23 21:17 ` Borislav Petkov
2010-05-23 21:48 ` Markus
2010-05-24 11:44 ` Markus
2010-05-25 13:09 ` Markus
2010-05-25 14:31 ` Borislav Petkov
2010-05-25 14:54 ` Markus
-- strict thread matches above, loose matches on Subject: below --
2011-03-27 9:16 Anca Emanuel
2011-03-27 15:37 ` Linus Torvalds
2011-03-27 16:00 ` Américo Wang
2011-03-27 17:44 ` Anca Emanuel
2011-03-27 17:52 ` Stephen Wilson
2010-05-31 1:24 Thomas Fjellstrom
2008-05-05 22:33 thomas
2008-05-07 6:55 ` Andrew Morton
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=201005232244.41977.M4rkusXXL@web.de \
--to=m4rkusxxl@web.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome