[Bug 112051] Got call trace message "eDP powered off while attempting aux channel communication" while boot up

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Fri Oct 25 05:03:01 UTC 2019


https://bugs.freedesktop.org/show_bug.cgi?id=112051

--- Comment #11 from Cyrus <cyrus.lien at canonical.com> ---
(In reply to Imre Deak from comment #10)
> (In reply to Cyrus from comment #8)
> > Created attachment 145804 [details]
> > dmesg with patch on Vostro
> > 
> > I have got bad news, the patch causes black screen issue on another one
> > specific machine.
> 
> Nothing obvious from the log, the only issue I see is 
> 
> [    2.020663] irq 45: nobody cared (try booting with the "irqpoll" option)
> [    2.020667] CPU: 3 PID: 0 Comm: swapper/3 Not tainted 5.4.0-rc3+ #1
> [    2.020671] Hardware name: Dell Inc. Vostro 3681/06CV2N, BIOS 0.6.13
> 10/07/2019
> [    2.020673] Call Trace:
> [    2.020679]  <IRQ>
> [    2.020683]  dump_stack+0x63/0x85
> [    2.020685]  __report_bad_irq+0x35/0xc0
> [    2.020687]  note_interrupt+0x24b/0x2a0
> [    2.020689]  handle_irq_event_percpu+0x54/0x80
> [    2.020690]  handle_irq_event+0x3b/0x60
> [    2.020691]  handle_fasteoi_irq+0x7c/0x130
> [    2.020693]  do_IRQ+0x54/0xe0
> [    2.020695]  common_interrupt+0xf/0xf
> [    2.020696]  </IRQ>
> 
> but that's in both logs.
> 
> Did you try this with the latest drm-tip and then with the patch reverted on
> top top of that?
Tried the patch on top of drm-tip (commit 54d0d8863278).
With the patch that Vostro machine got black screen after boot and it become
normal after revert the patch.

> 
> Is it 100% reproducible?
Yes

> 
> Do you get an FB console? (booting to bootlevel 3 adding "3" to the kernel
> parameters).
Yes, can get to console in runlevel 3.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20191025/1e9dd25c/attachment-0001.html>


More information about the intel-gfx-bugs mailing list