From: "JaniD++" <djani22@dynamicweb.hu>
To: <linux-kernel@vger.kernel.org>
Subject: Fw: 14-rc2 +RC4 !!! : kernel BUG at net/ipv4/tcp_output.c:438! #2 !!!
Date: Thu, 10 Nov 2005 18:07:28 +0100 [thread overview]
Message-ID: <004401c5e619$3d52e1e0$ae00a8c0@dcccs> (raw)
Herbert!
Sorry, but i cannot send direct mail for you. :(
Janos
----- Original Message -----
From: "JaniD++" <djani22@dynamicweb.hu>
To: "Herbert Xu" <herbert@gondor.apana.org.au>
Sent: Thursday, November 10, 2005 1:54 PM
Subject: Re: 14-rc2 +RC4 !!! : kernel BUG at net/ipv4/tcp_output.c:438! #2
!!!
> i have CTRL-C the cat process, and the system dies!
>
> look full.log
>
> cheers
>
>
> Doh!
> My stupid ISP is missconfig the DNS, and i cannot send you this mail
> yesterday.
>
> Janos
>
> ----- Original Message -----
> From: "Herbert Xu" <herbert@gondor.apana.org.au>
> To: "JaniD++" <djani22@dynamicweb.hu>
> Sent: Thursday, November 10, 2005 2:58 AM
> Subject: Re: 14-rc2 +RC4 !!! : kernel BUG at net/ipv4/tcp_output.c:438! #2
> !!!
>
>
> > On Thu, Nov 10, 2005 at 02:52:45AM +0100, JaniD++ wrote:
> > >
> > > Another info:
> > > The deadlock more often comes on slower system!
> >
> > Makes sense since that probably increases the window where the nbd
> > server can send the reply back to free the request.
> >
> > > The GNBD deadlock is VERY similar.
> > > Sample:
> > > Jul 17 23:05:10 dy-base kernel: ------------[ cut here ]------------
> > > Jul 17 23:05:10 dy-base kernel: kernel BUG at mm/highmem.c:183!
> >
> > One would presume that it's the same race condition.
> >
> > Cheers,
> > --
> > 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
>
reply other threads:[~2005-11-10 17:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='004401c5e619$3d52e1e0$ae00a8c0@dcccs' \
--to=djani22@dynamicweb.hu \
--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