From: Rob Allen <ra-kernel@hotmail.co.uk>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Clemens Ladisch <clemens@ladisch.de>,
Yinghai Lu <yinghai@kernel.org>, Ram Pai <linuxram@us.ibm.com>,
linux1394-devel@lists.sourceforge.net, linux-pci@vger.kernel.org
Subject: Re: [Bug 43244] New: firewire_ohci prevents boot
Date: Thu, 24 May 2012 19:43:18 +0100 [thread overview]
Message-ID: <BLU0-SMTP129FFE755310932B1C36438B7000@phx.gbl> (raw)
In-Reply-To: <20120524202610.5c561d99@stein>
On 24/05/12 19:26, Stefan Richter wrote:
> On May 24 bugzilla-daemon@bugzilla.kernel.org wrote:
>> https://bugzilla.kernel.org/show_bug.cgi?id=43244
>>
>> --- Comment #3 from Rob Allen<ra-kernel@hotmail.co.uk> 2012-05-24 17:30:12 ---
>> Created an attachment (id=73381)
>> --> (https://bugzilla.kernel.org/attachment.cgi?id=73381)
>> dmesg from v3.4 with CONFIG_PCI_DEBUG
This dmesg is the result of following Clemens's advice: boot with
firewire_ohci blacklisted, increase the log level and then manually load it.
I was unable to boot with 'debug', because each time I did so, I got a
backtrace (*).
Please let me know if there's anything else I can provide to help.
--
(*) When booting with 'debug', I experienced repeatable crashes: 1 oops
and several bugs at kernel/timer.c:1085. Crashes also occurred without
'debug', but not 100% of the time. The stack trace varied, so I'm
suspicious (I intend to check the machine's memory). I also reproduced
the crash on a stock Ubuntu 3.4 kernel, but failed to do so on a stock
Ubuntu 3.2.16 kernel.
Assuming this isn't my machine being unreliable, what's my next step for
this issue?
Thanks,
Rob
next prev parent reply other threads:[~2012-05-24 18:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-43244-4803@https.bugzilla.kernel.org/>
[not found] ` <20120513221357.7574ae79@stein>
2012-05-14 6:32 ` [Bug 43244] New: firewire_ohci prevents boot Clemens Ladisch
2012-05-14 6:39 ` Yinghai Lu
2012-05-16 13:12 ` Rob Allen
2012-05-16 13:53 ` Clemens Ladisch
2012-05-21 19:33 ` Rob Allen
2012-05-21 20:08 ` Stefan Richter
2012-05-21 20:20 ` Clemens Ladisch
2012-05-24 18:26 ` Stefan Richter
2012-05-24 18:43 ` Rob Allen [this message]
2012-06-04 23:59 ` Yinghai Lu
[not found] ` <4FBE8146.1030803@hotmail.co.uk>
2012-06-04 11:00 ` Rob Allen
2012-06-05 2:54 ` Ram Pai
2012-06-19 21:11 ` Rob Allen
[not found] ` <BAY153-W382DF41517C8EA770817E4B7EB0@phx.gbl>
2012-07-01 20:56 ` Yinghai Lu
2012-07-05 19:53 ` Rob Allen
[not found] ` <4FF5F09C.5020507@hotmail.co.uk>
2012-07-21 11:31 ` Rob Allen
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=BLU0-SMTP129FFE755310932B1C36438B7000@phx.gbl \
--to=ra-kernel@hotmail.co.uk \
--cc=clemens@ladisch.de \
--cc=linux-pci@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=linuxram@us.ibm.com \
--cc=stefanr@s5r6.in-berlin.de \
--cc=yinghai@kernel.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;
as well as URLs for NNTP newsgroup(s).