All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Tilman Schmidt <tilman@imap.cc>
Cc: Greg KH <greg@kroah.com>,
	linux-usb@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: Status of Bug 8094 -  ipaq oops on connecting "Vodafone VPA-II" ?
Date: Sun, 20 Sep 2009 18:37:44 +0200	[thread overview]
Message-ID: <20090920183744.395fc407@infradead.org> (raw)
In-Reply-To: <4AB6581F.5040908@imap.cc>

On Sun, 20 Sep 2009 18:28:15 +0200
Tilman Schmidt <tilman@imap.cc> wrote:

> Greg KH schrieb:
> > Can you provide a log message that shows the problem you are having
> > with the 2.6.31 kernel?
> 
> Attached. Currently only from an Nvidia-tainted kernel, though.
> If you need it reproduced on an untainted kernel it'll have to
> wait until I can reboot the machine.
> 
> The Oops location according to gdb is:
> 
> (gdb) info line *ipaq_open+0x1cf
> Line 656 of "drivers/usb/serial/ipaq.c" starts at address 0x986
> <ipaq_open+457> and ends at 0x98f <ipaq_open+466>.
> 

btw this is what scripts/markup_oops.pl is for... it gives a very nice
diagnostic

  reply	other threads:[~2009-09-20 16:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-20 13:39 Status of Bug 8094 - ipaq oops on connecting "Vodafone VPA-II" ? Tilman Schmidt
2009-09-20 15:05 ` Greg KH
2009-09-20 16:28   ` Tilman Schmidt
2009-09-20 16:37     ` Arjan van de Ven [this message]
2009-09-20 16:51       ` Tilman Schmidt
2009-09-20 17:32         ` Arjan van de Ven
2009-09-20 17:01   ` Tilman Schmidt
2009-09-20 21:13     ` Marcin Slusarz
2009-09-20 17:12   ` Alan Stern
2009-09-20 18:11     ` Greg KH
2009-09-21  1:59       ` Alan Stern
2009-09-21 23:03         ` Tilman Schmidt
2009-09-28 17:42         ` Status of Bug 8094 - ipaq oops on connecting "Vodafone VPA-II"? Matthias Geissert

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=20090920183744.395fc407@infradead.org \
    --to=arjan@infradead.org \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=tilman@imap.cc \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.