> Does every packet from A trigger the crash?
In my last test the crash was triggered after 300MB of http output (on
the fifth run of a script downloading the same 60MB of data).
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More
On Fri, Feb 08, 2008 at 11:45:33AM +0100, Beschorner Daniel wrote:
> > No I meant the exact output of ip x p and ip x s.
>
> I know, but as I end up every time with a tainted kernel on our
> production server I didn't turn ipcomp on, but now I got it.
Hmm, that's pretty much what I've got (but I'
> No I meant the exact output of ip x p and ip x s.
I know, but as I end up every time with a tainted kernel on our
production server I didn't turn ipcomp on, but now I got it.
src Net_B dst A
dir in priority 2088
tmpl src B dst A
proto comp reqid 16394 mode tunne
On Thu, Feb 07, 2008 at 07:01:32PM +0100, Beschorner Daniel wrote:
>
> > Could you show me the exact policies/SAs of the tunnel involved
> > in the crash?
>
> esp/cbc(aes128)/hmac(sha1)
No I meant the exact output of ip x p and ip x s.
Thanks,
--
Visit Openswan at http://www.openswan.org/
Email
> OK, so are you now able to reproduce this crash without waiting
> for hours? That would be really helpful in tracking it down.
Yes, I can reproduce it in minutes now.
> Could you show me the exact policies/SAs of the tunnel involved
> in the crash?
esp/cbc(aes128)/hmac(sha1)
--
On Wed, Feb 06, 2008 at 09:55:03PM +0100, Beschorner Daniel wrote:
>
> A is the oopsing 2.6.24, B is 2.6.23.
> I didn't change anything in the scenario recently, till 2.6.23 all
> worked fine.
OK, so are you now able to reproduce this crash without waiting
for hours? That would be really helpful i
>> Net_A - GW_A --- GW_B - Net_B
>> The Net_A - Net_B ESP/AES/IPComp tunnel works fine, the tunnel
between
>> Net_B and the external IP address of GW_A triggers the oops in GW_A.
> That's interesting. So which one out of A and B is running 2.6.24?
A is the oopsing 2.6.24, B is 2.6.23.
I didn't c
On Wed, Feb 06, 2008 at 03:43:25PM +0100, Beschorner Daniel wrote:
>
> Net_A - GW_A --- GW_B - Net_B
>
> The Net_A - Net_B ESP/AES/IPComp tunnel works fine, the tunnel between
> Net_B and the external IP address of GW_A triggers the oops in GW_A.
That's interesting. So which one out of A and B
> Unable to handle kernel paging request at c20fb000 RIP:
> [] deflate_slow+0x40/0x400
Here is some more information about the scenario in which I can easily
reproduce the oops now:
Net_A - GW_A --- GW_B - Net_B
The Net_A - Net_B ESP/AES/IPComp tunnel works fine, the tunnel between
Net
Nope! Right now it happened again, something must have changed with
2.6.24.
Unable to handle kernel paging request at c20fb000 RIP:
[] deflate_slow+0x40/0x400
PGD 7f845067 PUD 7f846067 PMD 7f847067 PTE 0
Oops: [1] SMP
CPU 0
Modules linked in:
Pid: 11055, comm: httpd Not tainted 2.6.2
>> Unable to handle kernel paging request at c20fb000 RIP:
>> [] 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
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
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.
Daniel
Unable to handle kernel paging request at c20
13 matches
Mail list logo
