On 24/05/12 19:26, Stefan Richter wrote:
On May 24 bugzilla-daemon@xxxxxxxxxxxxxxxxxxx wrote:
https://bugzilla.kernel.org/show_bug.cgi?id=43244
--- Comment #3 from Rob Allen<ra-kernel@xxxxxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-pci" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
