* 2.6.33.2 networking regression
@ 2010-04-25 3:16 Dave Jones
2010-04-25 3:19 ` David Miller
0 siblings, 1 reply; 2+ messages in thread
From: Dave Jones @ 2010-04-25 3:16 UTC (permalink / raw)
To: netdev; +Cc: stable
Something odd happened when I upgraded my router
from 2.6.33.1 to .33.2. Its internal NIC (a VIA Velocity)
stopped recieving packets.
dmesg was getting flooded with..
[ 188.919957] via-velocity 0000:00:0e.0: BAR 0: set to [io 0xf800-0xf8ff] (PCI address [0xf800-0xf8ff]
[ 188.920002] via-velocity 0000:00:0e.0: BAR 1: set to [mem 0xfdffe000-0xfdffe0ff] (PCI address [0xfdffe000-0xfdffe0ff]
[ 203.913967] via-velocity 0000:00:0e.0: BAR 0: set to [io 0xf800-0xf8ff] (PCI address [0xf800-0xf8ff]
[ 203.914181] via-velocity 0000:00:0e.0: BAR 1: set to [mem 0xfdffe000-0xfdffe0ff] (PCI address [0xfdffe000-0xfdffe0ff]
every so often for some reason.
rebooting back to .1, it works fine.
There don't appear to be any direct changes to via-velocity.c in the
diff, so I'm really confused. Any clues ? I'll bisect it, but it
probably won't be until Monday..
Dave
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: 2.6.33.2 networking regression
2010-04-25 3:16 2.6.33.2 networking regression Dave Jones
@ 2010-04-25 3:19 ` David Miller
0 siblings, 0 replies; 2+ messages in thread
From: David Miller @ 2010-04-25 3:19 UTC (permalink / raw)
To: davej; +Cc: netdev, stable
From: Dave Jones <davej@redhat.com>
Date: Sat, 24 Apr 2010 23:16:57 -0400
> There don't appear to be any direct changes to via-velocity.c in the
> diff, so I'm really confused. Any clues ? I'll bisect it, but it
> probably won't be until Monday..
Looks like some x86/PCI/ACPI change causes this, rather than a
networking change.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-04-25 3:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2010-04-25 3:16 2.6.33.2 networking regression Dave Jones
2010-04-25 3:19 ` David Miller
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).