On Thu, 2009-03-26 at 15:29 -0700, Edwin Lam wrote: > Package: linux-image-2.6.26-1-686 > Version: 2.6.26-13lenny2 > Severity: critical > Justification: breaks the whole system > > > when vlan is enabled, following error occurs: > (after a while, it'll completely overwhelm the system and render the whole > system unresponsive, this also happens on amd64 systems) These messages are rate-limited. If the system becomes unresponsive, I think that's a separate issue. > (excerpt from syslog) > .... > Mar 26 14:54:22 TestRT kernel: [ 363.750492] sky2 eth0: rx length error: status 0xae2300 length 174 > Mar 26 14:54:26 TestRT kernel: [ 367.642292] sky2 eth0: rx length error: status 0x3c2300 length 60 > Mar 26 14:54:29 TestRT kernel: [ 370.816289] sky2 eth0: rx length error: status 0x3c2100 length 60 > Mar 26 14:54:31 TestRT kernel: [ 372.866325] sky2 eth0: rx length error: status 0x5a2100 length 90 > Mar 26 14:54:42 TestRT kernel: [ 384.054210] sky2 eth0: rx length error: status 0x3c2300 length 60 > Mar 26 14:55:05 TestRT kernel: [ 407.315136] sky2 eth0: rx length error: status 0x662300 length 102 > .... It looks like the NIC is receiving non-tagged frames after being configured to receive only VLAN-tagged frames. Perhaps the driver should support receiving a mixture, but this is an unusual network configuration. Ben. -- Ben Hutchings It is impossible to make anything foolproof because fools are so ingenious.
Attachment:
signature.asc
Description: This is a digitally signed message part