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

Date:	Wed, 17 Jan 2007 08:54:58 -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 Wed, Jan 17, 2007 at 07:00:48AM -0500, David Hollis wrote:
> > 'rmmod asix' takes a really long time (45-80s) with any setting, and
> > sometimes coincides with ksoftirqd pegging (99.9% CPU) for several
> > seconds.
> 
> This I haven't seen before.  Does it occur even when the device is able
> to work (using 0 or the like from above)?  This may be due to something
> else in the USB subsystem or something.

Yes, the delay occurs even when the device works fine, and it results
in no suspicious dmesg's (just a couple of 'unregistering' messages).

I have no case when this delay doesn't occur; it's only in this
testing that I've had occasion to rmmod the driver at all. In and of
itself, it's not a big problem.

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