Summary: | ping: sendmsg: No buffer space available | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | aidar <the.aidar> |
Component: | [OLD] Core system | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
aidar
2009-11-18 18:12:37 UTC
I've heard that this problem might by caused by faulty hardware or that resetting the BIOS helps. Does this problem also occur with older Kernels? You're using an RC-Kernel which we don't support. (In reply to comment #1) > I've heard that this problem might by caused by faulty hardware or that > resetting the BIOS helps. > > Does this problem also occur with older Kernels? You're using an RC-Kernel > which we don't support. > I used some stable kernels (gentoo-sources) in portage - the same thing. What can I do about bios and my hardware - nothing. But I really doubt that it is the HW or BIOS as the same machine can ping anytime in Windows. I reported upstream here > http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2129 those shitheads are useless :) I mean there are bunch of people struggling just like me, and they think it is with specific AP type...what a load of shitheads @ intel.... (In reply to comment #2) > I reported upstream here > > http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2129 > > those shitheads are useless :) I mean there are bunch of people struggling just > like me, and they think it is with specific AP type...what a load of shitheads > @ intel.... Honestly, how is that kind of language going to help? Indeed, it won't help them at all. In fact nothing is going to help them. I have to say this, reported at the bug report also, I had to disable CONFIG_IPV6 in the kernel for the bug to go. Interesting, right ? it never happened on the wired interface, however on wifi with iwlfifi you never get a solid network. However if I set it on again guess what happens ? Nothing changed - same bug. Anyway, I am not able to test those settings any more, so I say it is up to "UPSTREAM", hence the new status. thanks, Aidar Just for someones information, I'm getting the same error on a wired network second NIC. Both NIC's are on-board. When I stop and start the first NIC, the second NIC starts working again. |