netdev - Re: Kernel oops on setting sky2 interfaces down

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 19 Aug 2009 17:46:29 -0700
From:	Stephen Hemminger <shemminger@...ux-foundation.org>
To:	Rene Mayrhofer <rene.mayrhofer@...raltar.at>
Cc:	Mike McCormack <mikem@...g3k.org>, netdev@...r.kernel.org,
	Richard Leitner <leitner@...s.at>
Subject: Re: Kernel oops on setting sky2 interfaces down

On Thu, 20 Aug 2009 07:05:03 +0900
Mike McCormack <mikem@...g3k.org> wrote:

> 2009/8/20 Rene Mayrhofer <rene.mayrhofer@...raltar.at>:
> 
> > 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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html