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]

Date:	Mon, 15 Jan 2007 14:50:29 -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 07:27:56PM +0000, David Hollis wrote:
> Do you happen to have a Rev. B1 DLink adapter?  If so, the only change
> that was put in (PHY Select fix) should actually make these devices
> work.  Can you check the top of the ax88772_bind() call in your file and
> see if it has this bit:
> 
>         if ((ret = asix_write_cmd(dev, AX_CMD_SW_PHY_SELECT,
>                                 1, 0, 0, buf)) < 0) {
>                 dbg("Select PHY #1 failed: %d", ret);
>                 goto out2;
>         }
> 
> 
> That '1' after the AX_CMD_SW_PHY_SELECT was the key to that patch.  If
> yours is 1, you could try setting it to 0, though that should make
> things not work.  I'd very interested if it made things work for you.
> BTW, the ramifications of this bug were similar to what you describe:
> the interface would come up, look fine but just wouldn't send or receive
> any packets. The hard lock-ups and such are likely from something else.

I don't know the Rev number of the adapter; I can't get to it physically
today, and I don't see it in dmesg.

The asix_write_cmd argument in question did indeed change from 0 to 1
between 2.6.20-rc3-mm1 and -rc4-mm1. I'll change it back, rebuild,
and test. Probably tomorrow.

Thanks.

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