linux-kernel - Re: 2.6.20-rc4-mm1 USB (asix) problem

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]

Message-id: <20070116225909.GA6932@pool-71-123-123-29.spfdma.east.verizon.net>
Date:	Tue, 16 Jan 2007 17:59:15 -0500
From:	Eric Buddington <ebuddington@...izon.net>
To:	David Hollis <dhollis@...ehollis.com>
Cc:	ebuddington@...leyan.edu, linux-kernel@...r.kernel.org
Subject: Re: 2.6.20-rc4-mm1 USB (asix) problem

On Mon, Jan 15, 2007 at 08:32:17PM +0000, David Hollis wrote:
> Interesting.  It would really be something if your devices happen to
> work better with 0.  Wouldn't make much sense at all unfortunately.  If
> 0 works, could you also try setting it to 2 or 3?  The PHY select value
> is a bit field with the 0 bit being to select the onboard PHY, and 1 bit
> being to 'auto-select' the PHY based on link status.  The data sheet
> indicates that 3 should be the default, but all of the literature I have
> seen from ASIX says to write a 1 to it.

My hardware is ver. B1.

0, 2, and 3 all worked for me. 1, as before, does not.

'rmmod asix' takes a really long time (45-80s) with any setting, and
sometimes coincides with ksoftirqd pegging (99.9% CPU) for several
seconds.

-Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/