From: Roy Sindre Norangshol <norrs@tihlde.org>
To: linux-kernel@vger.kernel.org
Subject: Re: BUG: unable to handle kernel NULL pointer dereference - 2.6.25.7
Date: Tue, 22 Jul 2008 02:35:49 +0200 [thread overview]
Message-ID: <48852B65.9060907@tihlde.org> (raw)
In-Reply-To: <48840021.60001@tihlde.org>
Roy Sindre Norangshol wrote:
> I tried upgrading to 2.6.26 release - but server died again on
> saturday, so going to check
> logs later today (Monday) to see if it's another kernel bug popping up.
No logs after second crash with 2.6.26 kernel, and nothing useful to
pickup from screen since it frooze..
Back to 2.6.18 I go..
> *snip*
> motherboard of type P35 chipset, motherboard P35C-DS3 [3] (I think) by
> Gigabyte.
> *snip*
It was EP35-DS3R by Gigabyte.
>
> I'll provide more hardware information when I reboot the server, so I
> can run lspci, lshw, dpkg -l to provide
> you guys with more information as I guess that would be nice. Anything
> else I should run?
lshw,lspci and such are available here: http://norrs.no/kroton2/
Hope it is of any use.
--
Roy Sindre Norangshol
prev parent reply other threads:[~2008-07-22 0:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 3:18 BUG: unable to handle kernel NULL pointer dereference - 2.6.25.7 Roy Sindre Norangshol
2008-07-22 0:35 ` Roy Sindre Norangshol [this message]
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=48852B65.9060907@tihlde.org \
--to=norrs@tihlde.org \
--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