All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Boris B. Zhmurov" <bb@kernelpanic.ru>
To: Ian McDonald <imcdnzl@gmail.com>
Cc: Jesse Brandeburg <jesse.brandeburg@gmail.com>,
	Yoseph Basri <yoseph.basri@gmail.com>,
	linux-kernel@vger.kernel.org,
	NetDEV list <netdev@vger.kernel.org>
Subject: Re: KERNEL: assertion (!sk->sk_forward_alloc) failed
Date: Thu, 09 Feb 2006 22:32:00 +0300	[thread overview]
Message-ID: <43EB98B0.4@kernelpanic.ru> (raw)
In-Reply-To: <cbec11ac0602091125w5a5a7c6em8462131e9f9b24dc@mail.gmail.com>

Hello, Ian McDonald.

On 09.02.2006 22:25 you said the following:

> Is it possible for you to download 2.6.16-rc2 or similar and see if it
> goes away?

It'll be better, if I get only patch fixs that problem, not all 2.6.16-rc2.

-- 
Boris B. Zhmurov
mailto: bb@kernelpanic.ru
"wget http://kernelpanic.ru/bb_public_key.pgp -O - | gpg --import"


  reply	other threads:[~2006-02-09 19:32 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-07  9:46 KERNEL: assertion (!sk->sk_forward_alloc) failed Yoseph Basri
2006-02-07 10:32 ` Boris B. Zhmurov
2006-02-08  3:02   ` Yoseph Basri
2006-02-08 20:07 ` Jesse Brandeburg
2006-02-08 22:12   ` David S. Miller
2006-02-09  2:10     ` Jesse Brandeburg
2006-03-10 10:59       ` David S. Miller
2006-02-09 19:17   ` Boris B. Zhmurov
2006-02-09 19:25     ` Ian McDonald
2006-02-09 19:32       ` Boris B. Zhmurov [this message]
2006-02-09 19:37         ` Ian McDonald
2006-03-10 10:59           ` David S. Miller
2006-03-10 15:51             ` Krzysztof Oledzki
2006-03-12 10:30               ` Michal Feix
2006-02-16 21:02         ` Jan-Frode Myklebust
  -- strict thread matches above, loose matches on Subject: below --
2006-03-03  6:12 Johan Lundgren
2005-11-28 12:36 Mark Nipper
2005-11-28 13:44 ` Miquel van Smoorenburg
2005-11-28 16:44   ` Jesse Brandeburg

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=43EB98B0.4@kernelpanic.ru \
    --to=bb@kernelpanic.ru \
    --cc=imcdnzl@gmail.com \
    --cc=jesse.brandeburg@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=yoseph.basri@gmail.com \
    /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.