netdev - Re: sky2: unsupported chip type 0xff failure

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] [day] [month] [year] [list]

Message-ID: <20100103111330.06df6c50@nehalam>
Date:	Sun, 3 Jan 2010 11:13:30 -0800
From:	Stephen Hemminger <shemminger@...tta.com>
To:	Gregory Petrosyan <gregory.petrosyan@...il.com>
Cc:	netdev@...r.kernel.org
Subject: Re: sky2: unsupported chip type 0xff failure

On Sun, 3 Jan 2010 01:48:58 +0300
Gregory Petrosyan <gregory.petrosyan@...il.com> wrote:

> I've got an HP ProBook 5310m laptop with Marvell Ethernet controller. sky2 reports
> 
> [14252.318867] sky2 driver version 1.23
> [14252.318904] sky2 0000:03:00.0: setting latency timer to 64
> [14252.318951] sky2 0000:03:00.0: unsupported chip type 0xff
> [14252.318960] sky2: probe of 0000:03:00.0 failed with error -95
> 
> (this is captured after 'modprobe -r' + 'modprobe') and I've seen it working
> only 1 time (probably after a reboot).

The chip id is one of the first things read from the device. If the PCI
read gets an error, then the value is all-ones.

The issue is not directly in the driver, but with the power control for
that device. 

Try the latest kernel (even 2.6.33-rc2) to make sure the problem isn't
already fixed. 

-- 
--
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