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>,
Matthew Wilcox <matthew@wil.cx>
Subject: Re: Status of Bug 8094 - ipaq oops on connecting "Vodafone VPA-II" ?
Date: Sun, 20 Sep 2009 19:32:47 +0200 [thread overview]
Message-ID: <20090920193247.1d0e49cd@infradead.org> (raw)
In-Reply-To: <4AB65D83.1080506@imap.cc>
On Sun, 20 Sep 2009 18:51:15 +0200
Tilman Schmidt <tilman@imap.cc> wrote:
> > btw this is what scripts/markup_oops.pl is for... it gives a very
> > nice diagnostic
>
> Unfortunately that script doesn't work on my machine:
>
> ts@xenon:~/kernel/linux-2.6.31-work> ./scripts/markup_oops.pl
> < /tmp/mdabug.txt No vmlinux specified,
> assuming /lib/modules/2.6.31-vanilla/build/vmlinux Can't locate
> object method "from_hex" via package "Math::BigInt"
> at ./scripts/markup_oops.pl line 176, <STDIN> line 98.
>
> And as it's openSUSE based I can't simply update my Perl packages
> from CPAN. But I can live with the gdb method.
hmm Matthew added that....
should we undo that change??
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2009-09-20 17:32 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
2009-09-20 16:51 ` Tilman Schmidt
2009-09-20 17:32 ` Arjan van de Ven [this message]
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=20090920193247.1d0e49cd@infradead.org \
--to=arjan@infradead.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=matthew@wil.cx \
--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.