From: Herbert Xu <herbert@gondor.apana.org.au>
To: Beschorner Daniel <Daniel.Beschorner@facton.com>
Cc: netdev@vger.kernel.org
Subject: Re: oops with ipcomp
Date: Sat, 2 Feb 2008 15:42:54 +1100 [thread overview]
Message-ID: <20080202044254.GA27792@gondor.apana.org.au> (raw)
In-Reply-To: <3C59DB883F7B0B4D8096010D45ACCD134F209E@exch.facton.local>
On Fri, Feb 01, 2008 at 11:09:22AM +0100, Beschorner Daniel wrote:
> One more issue with 2.6.24, some hours after I reactivated ipcomp with
> Herb's 2 patches.
> The httpd log shows a http request per esp tunnel at oops time.
> Don't know whether it is for network or compression guys, so I started
> posting here.
>
> Unable to handle kernel paging request at ffffc200000fb000 RIP:
> [<ffffffff8031b8f0>] deflate_slow+0x40/0x400
I'm not able to get much information out of this crash dump. Nor
can I reproduce this bug on my 32-bit machines and I'm currently
away from my 64-bit machines.
How long have you been using IPComp in the past and what was the
last kernel version which was stable with IPComp?
Thanks,
--
Visit Openswan at http://www.openswan.org/
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2008-02-02 4:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-01 10:09 oops with ipcomp Beschorner Daniel
2008-02-02 4:42 ` Herbert Xu [this message]
2008-02-04 9:35 ` Beschorner Daniel
-- strict thread matches above, loose matches on Subject: below --
2008-02-04 10:39 Beschorner Daniel
2008-02-06 14:43 Beschorner Daniel
2008-02-06 17:07 ` Herbert Xu
2008-02-06 20:55 ` Beschorner Daniel
2008-02-07 15:44 ` Herbert Xu
2008-02-07 18:01 ` Beschorner Daniel
2008-02-08 8:58 ` Herbert Xu
2008-02-08 10:45 ` Beschorner Daniel
2008-02-08 18:31 ` Herbert Xu
2008-02-11 15:03 Beschorner Daniel
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=20080202044254.GA27792@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=Daniel.Beschorner@facton.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox