From: "Justin P. Mattock" <justinmattock@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org
Subject: Re: BUG: unable to handle kernel NULL pointer dereference at 00000000000000a0
Date: Wed, 23 Jun 2010 07:41:07 -0700 [thread overview]
Message-ID: <4C221D03.9050006@gmail.com> (raw)
In-Reply-To: <20100623141622.GC15205@tuxdriver.com>
On 06/23/2010 07:16 AM, John W. Linville wrote:
> On Tue, Jun 22, 2010 at 04:16:53PM -0700, Justin Mattock wrote:
>> I remember ipsec was able to work cleanly on my machines probably
>> about 4/6 months ago
>> now I get this:
>
> <snip>
>
> Perhaps netdev would be a more appropriate list than linux-wireless
> for this?
>
> John
alright added the cc's..
almost done bisecting..hopefully this points to
the right area..(if not I'll re-bisect until I get this).
as for the troubled machines I've a macbookpro2,2(no proprietary
stuff) and an imac9,1 with broadcom-sta(blah) both
seem to hit this right when the ipsec transaction starts
with ssh, vncviewer..(last good kernel I have is
2.6.33-rc5-01007-ge9449d8).
Justin P. Mattock
next prev parent reply other threads:[~2010-06-23 14:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-22 23:16 BUG: unable to handle kernel NULL pointer dereference at 00000000000000a0 Justin Mattock
2010-06-22 23:16 ` Justin Mattock
2010-06-23 14:16 ` John W. Linville
2010-06-23 14:41 ` Justin P. Mattock [this message]
2010-06-23 17:00 ` Justin P. Mattock
2010-06-23 17:29 ` Eric Dumazet
2010-06-23 18:10 ` Timo Teräs
2010-06-23 18:20 ` Justin P. Mattock
2010-06-23 20:34 ` Timo Teräs
2010-06-23 21:44 ` Justin P. Mattock
2010-06-24 5:45 ` [PATCH] xfrm: check bundle policy existance before dereferencing it Timo Teräs
2010-06-24 5:45 ` Timo Teräs
2010-06-24 21:35 ` David Miller
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=4C221D03.9050006@gmail.com \
--to=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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 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.