From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Mark Nipper" <nipsy@bitgnome.net>
Cc: linux-kernel@vger.kernel.org, Netdev <netdev@vger.kernel.org>
Subject: Re: BUG: unable to handle kernel NULL pointer dereference<1>
Date: Sat, 8 Sep 2007 01:48:36 +0200 [thread overview]
Message-ID: <6bffcb0e0709071648y3e18fe23s24fdff3923690448@mail.gmail.com> (raw)
In-Reply-To: <20070907052720.GA3122@king.bitgnome.net>
Hi Mark,
[Adding netdev to CC]
On 07/09/2007, Mark Nipper <nipsy@bitgnome.net> wrote:
> I've received two oopses now from my kernel while running
> the 2.6.22 series. The first was with 2.6.22.1 back in July and
> the second which happened just within the last day is 2.6.22.5.
> They both appear to be the same bug and I don't think it's
> hardware related. I'm attaching the entries from logcheck which
> I received when they happened.
>
> I'm not subscribed to the mailing list, so please make
> sure to copy me directly on any replies. And let me know if
> anyone needs any additional information to try to track this
> down. Thanks for reading...
Regards,
Michal
--
LOG
http://www.stardust.webpages.pl/log/
parent reply other threads:[~2007-09-07 23:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20070907052720.GA3122@king.bitgnome.net>]
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=6bffcb0e0709071648y3e18fe23s24fdff3923690448@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nipsy@bitgnome.net \
/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