Summary: | e1000 fails on alloc pages (VMware) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stefan de Konink <stefan> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED INVALID | ||
Severity: | major | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Stefan de Konink
2009-02-26 08:29:34 UTC
I found this patch: http://lkml.org/lkml/2008/4/2/62 Although backtrace is different it looks like the reason is still the same. As I see patch was never applied. Looks like these messages are harmless in e1000... or did you see some negative side effects of this? (In reply to comment #2) > Looks like these messages are harmless in e1000... or did you see some negative > side effects of this? Only crashes of the filesystems... Can you post details of those? They are probably unrelated... this message is printed when the e1000 driver encounters a condition that it deals with just fine, and are to be expected now and then. It's only a cosmetic bug that these messages look scary and exist at all. (In reply to comment #4) > Can you post details of those? > They are probably unrelated... this message is printed when the e1000 driver > encounters a condition that it deals with just fine, and are to be expected now > and then. It's only a cosmetic bug that these messages look scary and exist at > all. It is the other bug you just commented on. 257739 NFS breaks, and the scsi stuff does, I still think it is something buggy in VMware though. OK. The e1000 thing is definitely just a spammy warning, and can be ignored. thanks for reporting anyhow :) (In reply to comment #6) > OK. The e1000 thing is definitely just a spammy warning, and can be ignored. > thanks for reporting anyhow :) Then why not apply the patch? ask upstream, we go with their decisions |