Re: KERNEL: assertion (!sk->sk_forward_alloc) failed

On 2/10/06, Boris B. Zhmurov <[email protected]> wrote:
> Hello, Jesse Brandeburg.
>
> On 08.02.2006 23:07 you said the following:
>
> > whats the relevance of e1000?
> >
> > I though Herbert had fixed these
>
> Nope :( I had this messages on 2.6.14.2 and now I have it on 2.6.15.3.
>
For what it's worth I had these messages for a while and they got
fixed 2 or 3 weeks ago from memory in Dave's 2.6.16 net tree or net2.6
tree.

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

Ian
--
Ian McDonald
http://wand.net.nz/~iam4
WAND Network Research Group
University of Waikato
New Zealand
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: KERNEL: assertion (!sk->sk_forward_alloc) failed
    • From: "Boris B. Zhmurov" <[email protected]>

• References:
  • KERNEL: assertion (!sk->sk_forward_alloc) failed
    • From: Yoseph Basri <[email protected]>
  • Re: KERNEL: assertion (!sk->sk_forward_alloc) failed
    • From: Jesse Brandeburg <[email protected]>
  • Re: KERNEL: assertion (!sk->sk_forward_alloc) failed
    • From: "Boris B. Zhmurov" <[email protected]>

• Prev by Date: Re: [PATCH v2 02/07] cpuset use combined atomic_inc_return calls
• Next by Date: Fwd: How to call a function in a module from the kernel code !!! (Linux kernel)
• Previous by thread: Re: KERNEL: assertion (!sk->sk_forward_alloc) failed
• Next by thread: Re: KERNEL: assertion (!sk->sk_forward_alloc) failed
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]