Subject: Re: Kernel oops on setting sky2 interfaces down

From: Stephen Hemminger <[email-masked]>
Date: Wed, 19 Aug 2009 17:46:29 -0700

On Thu, 20 Aug 2009 07:05:03 +0900
Mike McCormack <[email-masked]> wrote:

> 2009/8/20 Rene Mayrhofer <[email-masked]>:
> 
> > Pulling the latest sky2.c and sky2.h from net-next-2.6 and applying the patch
> > rids me of the oops - it is unreproducible right now. However, a networking
> > restart (i.e. all interfaces attached to sky2) leaves the devices in a state
> > where they no longer receive any network packets (at least nothing visible in
> > tcpdump). In this state, rmmod sky2 / modprobe sky2 gives:
> 
> After you've got it into that state, does "rmmod sky2; modprobe sky2"
> change anything?
> 
> thanks,
> 
> Mike

Please send (I forget) the hardware info (lspci) and the register values
from ethtool -d ethX.

Some part of the power control doesn't work on Rene's system, so
device falls off the bus. Probably no auxilary +5 supplied, the register
values will tell whether driver is at fault (turning on aux when not
available), or hardware is lying about vaux.