linux-kernel - Re: [HANG] Trouble with NEC-based USB adapter in PCMCIA slot on E7110

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: <52075079.2060405@rus.uni-stuttgart.de>
Date:	Sun, 11 Aug 2013 10:51:05 +0200
From:	Thomas Richter <richter@....uni-stuttgart.de>
To:	Alan Stern <stern@...land.harvard.edu>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [HANG] Trouble with NEC-based USB adapter in PCMCIA slot on E7110

On 11.08.2013 03:46, Alan Stern wrote:
> On Sat, 10 Aug 2013, Thomas Richter wrote:
>
>> Sorry, need to look further. I replaced ehci-pci from 2.6.31.14, and
>> yenta_socket as well. No changes were necessary. Also replaced ehci-hcd,
>
> Do you mean that you took the source code for ehci-hcd from the 2.6.31
> kernel, copied it into the source directory for the 2.6.32 kernel, and
> built it there?

Exactly that, yes. Two minor patches were necessary in ehci-hcd, but I 
doubt that this is the source of the problem (just one administration 
structure was pulled out in 2.6.32).

>> but that required two minor changes because in 2.6.32, apparently, one
>> hardware related structure was pulled out of the ehci structure.
>>
>> Still did not make any difference, still locks up.
>>
>> What's the next module up in the call chain I should be looking at?
>
> Have you tried comparing a usbmon trace from 2.6.31 with a comparable
> trace from 2.6.32?  I doubt there will be any important differences,
> but you never know until you try.

Not yet, good idea, thanks.

Thanks,
	Thomas


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