linux-kernel - Re: Oops in CDC ACM after an Openmoko phone (neo1973) changes its usb interface from ACM to Ethernet

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 2 Aug 2009 22:39:28 +0200
From:	Alex Riesen <raa.lkml@...il.com>
To:	Oliver Neukum <oliver@...kum.org>
Cc:	linux-usb@...r.kernel.org, Oliver Neukum <oliver@...kum.name>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Greg Kroah-Hartman <greg@...ah.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: Oops in CDC ACM after an Openmoko phone (neo1973) changes its usb 
	interface from ACM to Ethernet

On Sun, Aug 2, 2009 at 20:25, Alex Riesen<raa.lkml@...il.com> wrote:
> I shall try to find the -rc2 which oopses (I suspect it is the one
> just before -rc3).
>

And this is after I put "for(;;);" at the end of dump_stack in v2.6.31-rc3:
http://home.arcor.de/fork0/bug/neocrash.jpg (~110k)

And this one is with v2.6.31-rc5 (it has usb_disconnect in it):
http://home.arcor.de/fork0/bug/neocrash-rc5.jpg (~86k)
(config: http://home.arcor.de/fork0/bug/neocrash-config-rc5.txt)

I couldn't find the -rc2 which didn't lock up. They all do now. I don't know
anymore how I made that -rc2 where I got the previous oops from.

Any idea how to disable stack dumps so that there is more place
for other output on a laptop screen? (no chance for serial console)
Or maybe a high-speed video camera can stand a chance?
--
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/