From: Tobias Karnat <tobias.karnat@googlemail.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: linux-acpi@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
richard.coe@med.ge.com, jslaby@novell.com
Subject: Re: acpi_button: random oops on boot
Date: Tue, 07 Dec 2010 16:02:02 +0100 [thread overview]
Message-ID: <1291734122.29072.14.camel@Tobias-Karnat> (raw)
In-Reply-To: <20101207051521.GA16804@helgaas.com>
Am Montag, den 06.12.2010, 22:15 -0700 schrieb Bjorn Helgaas:
> In addition to the isolation ideas I suggested above, you might
> boot with "maxcpus=1" and turn on all the Kconfig memory debug
> switches.
Booting with mminit_loglevel=4 maxcpus=1 causes this to show up:
[ 17.364026] usb 1-6: device descriptor read/64, error -110
[ 32.579024] usb 1-6: device descriptor read/64, error -110
[ 32.794012] usb 1-6: new high speed USB device using ehci_hcd and address 6
[ 47.907019] usb 1-6: device descriptor read/64, error -110
[ 63.121019] usb 1-6: device descriptor read/64, error -110
[ 63.335022] usb 1-6: new high speed USB device using ehci_hcd and address 7
[ 73.748031] usb 1-6: device not accepting address 7, error -110
[ 73.861018] usb 1-6: new high speed USB device using ehci_hcd and address 8
[ 84.274018] usb 1-6: device not accepting address 8, error -110
[ 84.285143] hub 1-0:1.0: unable to enumerate USB device on port 6
I have nothing connected to 1-6:
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 046d:c20a Logitech, Inc. WingMan RumblePad
Bus 004 Device 002: ID 03eb:3301 Atmel Corp. at43301 4-Port Hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 046d:c062 Logitech, Inc.
Bus 002 Device 002: ID 413c:2105 Dell Computer Corp. Model L100 Keyboard
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 0dda:2026 Integrated Circuit Solution, Inc. USB2.0 Card Reader
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
It shows up at the same time as the crash happens without maxcpus.
However SysRq does work in this case.
-Tobias
next prev parent reply other threads:[~2010-12-07 15:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-04 15:49 Tobias Karnat
2010-12-06 16:28 ` Bjorn Helgaas
2010-12-06 23:01 ` Tobias Karnat
2010-12-06 23:26 ` Bjorn Helgaas
2010-12-06 23:54 ` Tobias Karnat
2010-12-07 0:22 ` Tobias Karnat
2010-12-07 5:15 ` Bjorn Helgaas
2010-12-07 14:44 ` Rich Coe
2010-12-07 15:02 ` Tobias Karnat [this message]
2010-12-07 15:35 ` Tobias Karnat
2010-12-07 15:52 ` Tobias Karnat
2011-01-24 13:03 ` Thomas Renninger
2011-01-24 18:13 ` Tobias Karnat
2011-01-24 18:48 ` Rich Coe
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=1291734122.29072.14.camel@Tobias-Karnat \
--to=tobias.karnat@googlemail.com \
--cc=bjorn.helgaas@hp.com \
--cc=jslaby@novell.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.coe@med.ge.com \
/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®