[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2014-10-20 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 Len Brown l...@kernel.org changed: What|Removed |Added Status|RESOLVED|CLOSED CC|

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2014-01-16 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 Adam Williamson awill...@redhat.com changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2014-01-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 --- Comment #14 from Alan a...@lxorguk.ukuu.org.uk --- See the apic one here with 3.13-rc7, but not 3.12 on Asus TA100T Trying to pin down the bad patch (bug 68291) -- You are receiving this mail because: You are watching the assignee of the

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2014-01-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 --- Comment #15 from Adam Williamson awill...@redhat.com --- Should we close this as a dupe of that, then, or vice versa? -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2014-01-08 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 Bastien Nocera bugzi...@hadess.net changed: What|Removed |Added CC||bugzi...@hadess.net

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2014-01-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 --- Comment #12 from Alan a...@lxorguk.ukuu.org.uk --- There are several species of Baytrail, the relevant one for the tablets is Baytrail/T. I'm not sure what the Yocto enabling folk are working with but that tree seems to be a general dump of

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2014-01-06 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 --- Comment #13 from Adam Williamson awill...@redhat.com --- well, they said they'd got KMS video working with that tree. I haven't tried it myself yet, though. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2014-01-05 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 --- Comment #11 from Adam Williamson awill...@redhat.com --- Someone commented on my G+ (where I've been blogging about this tablet) that there's a Yocto branch with a bunch of baytrail fixes:

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2013-12-31 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 Jani Nikula jani.nik...@intel.com changed: What|Removed |Added CC|

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2013-12-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 Alan a...@lxorguk.ukuu.org.uk changed: What|Removed |Added CC||a...@lxorguk.ukuu.org.uk

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2013-12-30 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 --- Comment #10 from Adam Williamson awill...@redhat.com --- I've already captured the other traceback. Once I realized neither actually prevented boot, but the v8p just has weird issues booting Linux from USB multiple times in succession or

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2013-12-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 --- Comment #5 from Adam Williamson awill...@redhat.com --- Created attachment 120181 -- https://bugzilla.kernel.org/attachment.cgi?id=120181action=edit full journal from a successful boot on the affected system, including traceback So the

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2013-12-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 --- Comment #6 from Adam Williamson awill...@redhat.com --- Looks like the earlier trace that causes this one to be tainted is a warn_slowpath_common in ACPI setup or something. I'll file that separately. -- You are receiving this mail because:

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2013-12-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 --- Comment #7 from Adam Williamson awill...@redhat.com --- Here's the bug snipped out of the log, for ease of reference: Dec 29 11:11:34 localhost kernel: BUG: unable to handle kernel paging request at 41003230 Dec 29 11:11:34 localhost kernel:

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2013-12-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 --- Comment #8 from Adam Williamson awill...@redhat.com --- Created attachment 120191 -- https://bugzilla.kernel.org/attachment.cgi?id=120191action=edit acpidump from affected system -- You are receiving this mail because: You are watching the

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2013-12-29 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 Adam Williamson awill...@redhat.com changed: What|Removed |Added Attachment #120031|0 |1 is

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2013-12-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 --- Comment #1 from Adam Williamson awill...@redhat.com --- Forgot to mention - I've actually tested with the stock current Rawhide kernel with no patches, and it does the same thing. -- You are receiving this mail because: You are watching the

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2013-12-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 --- Comment #2 from Adam Williamson awill...@redhat.com --- Testing a build with pinctrl: baytrail: lock IRQs when starting them patch from LKML to see if that helps... -- You are receiving this mail because: You are watching the assignee of the

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2013-12-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 --- Comment #3 from Adam Williamson awill...@redhat.com --- Nope, same with that kernel. :/ -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 67861] Venue 8 Pro (valleyview): 'unable to handle kernel paging request' error and trace in __add_pin_to_irq_node on boot

2013-12-28 Thread bugzilla-daemon
https://bugzilla.kernel.org/show_bug.cgi?id=67861 --- Comment #4 from Adam Williamson awill...@redhat.com --- Hum, looks like this error may not be directly causing the boot fail, if I leave it for a long time it drops to a dracut emergency shell complaining it can't find some disks. Have to look