Aloha!
I know it has been discussed before, but I must express my feelings
about this issue nonetheless. I find it a major pain in the back that
/proc/$pid/mem isn't readable by an unrelated process without doing a
PTRACE_ATTACH first.
I mainly want to ask: is there a good reason to not drop th
Scott Feldman wrote:
Would you mind giving this patch a try against 2.6.11? I think it's
equivalent to Jesse's patch, but less intrusive to the driver.
looks good, no more memory corruption errors. thanks for this.
cheers
richard
-
To unsubscribe from this list: send the line "unsubscribe linux-k
Scott Feldman wrote:
On Mar 5, 2005, at 11:10 AM, Richard Fuchs wrote:
looks like you are right, enabling NAPI in 2.6.7 does trigger this.
what exactly is this?
A bug in the driver. I have a hunch: please try this patch with 2.6.9
or higher:
http://marc.theaimsgroup.com/?l=linux-netdev&a
Scott Feldman wrote:
Was NAPI turned on for e100 in 2.6.7? If not, turn NAPI on in the 2.6.7
driver and see if you get the same result. If you do, it's very likely
the bug is in the e100 driver's NAPI implementation.
looks like you are right, enabling NAPI in 2.6.7 does trigger this.
what exact
Matt Mackall wrote:
Doh. 'ethtool -k' is what's needed, sorry.
doh myself. :) this won't be very helpful though, as i get the same on
all machines (with both drivers):
Offload parameters for eth0:
Cannot get device rx csum settings: Operation not supported
Cannot get device tx csum settings: Oper
_correction_ to my previous mail, this does _not_ happen with the
eepro100 driver. (sorry for the confusion, i got the kernel images mixed
up with all the testing i've been doing.)
could this affect the e1000 driver as well?
Matt Mackall wrote:
Send the output of ethtool, please.
box 1, affected
Matt Mackall wrote:
Which card/driver is this? Is this the same card that's showing ssh
troubles? My theory about your ssh trouble only applies to cards with
checksum offload.
i got the same on all three machines i was testing with, with both the
e100 and the eepro100 driver. one of those three ma
Richard Fuchs wrote:
> [e100]
i will try again the eepro100 driver and see if it does the same...
yes, the same thing happens with the eepro100 driver.
cheers
richard
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PR
Dave Jones wrote:
Which network drivers are in use on the box that gets the corruption ?
all three that i tested it on are using the e100 driver. the boxes with
pci id 8086:1039 and 8086:1229 are seeing corruptions, the one with pci
id 8086:2449 is not.
i will try again the eepro100 driver and s
Andrew Morton wrote:
I guess it could be hardware. But given that disabling DMA _causes_ the
problem, rather than fixes it, it seems unlikely.
Could you enable CONFIG_DEBUG_PAGEALLOC in .config and see it that triggers
an oops?
by now, i could reproduce this on two different machines with quite
d
hello all!
the memory allocation debugger gives me the following messages under a
vanilla 2.6.10 and 2.6.11 kernel when doing
1) hdparm -d0 on my hard disk
2) tar c / > /dev/null
3) sending lots of network traffic to the machine (e.g. close to 100
mbit/s udp packets)
---
11 matches
Mail list logo
