From: Alex Riesen <raa.lkml@gmail.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: linux-usb@vger.kernel.org, Oliver Neukum <oliver@neukum.name>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartman <greg@kroah.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Oops in CDC ACM after an Openmoko phone (neo1973) changes its usb interface from ACM to Ethernet
Date: Sun, 2 Aug 2009 22:39:28 +0200 [thread overview]
Message-ID: <81b0412b0908021339s739c07edvd4d5eb4c21cfa167@mail.gmail.com> (raw)
In-Reply-To: <81b0412b0908021125x654fd337hf03a67385302d6e4@mail.gmail.com>
On Sun, Aug 2, 2009 at 20:25, Alex Riesen<raa.lkml@gmail.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?
next prev parent reply other threads:[~2009-08-02 20:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-02 16:40 Alex Riesen
2009-08-02 17:19 ` Oliver Neukum
2009-08-02 18:25 ` Alex Riesen
2009-08-02 20:39 ` Alex Riesen [this message]
2009-08-02 20:50 ` Alan Stern
2009-08-02 21:09 ` Alex Riesen
2009-08-02 21:22 ` Oliver Neukum
2009-08-02 21:25 ` Alex Riesen
2009-08-03 9:17 ` Alex Riesen
2009-08-03 13:04 ` Oliver Neukum
2009-08-03 13:22 ` Alex Riesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81b0412b0908021339s739c07edvd4d5eb4c21cfa167@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.name \
--cc=oliver@neukum.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®