Re: was there some weird issue with the second last rawhide kernel? [DIAGNOSED?]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 2014-06-20 at 16:16 -0400, Robert P. J. Day wrote:
> On Fri, 20 Jun 2014, Adam Williamson wrote:
> 
> > On Fri, 2014-06-20 at 14:32 -0400, Robert P. J. Day wrote:
> >
> > >   if, however, i simply unplug the external monitor from HDMI, no
> > > problem, and i can plug in the monitor after booting. oh, and as
> > > before, once i'm running under this new (but clearly broken) kernel,
> > > when i go to shut down, massive kernel panic and stack trace.
> > >
> > >   i can do more testing tomorrow, but this has now been an issue for
> > > the last three rawhide kernel releases. is no one else seeing
> > > something like this? more later ...
> >
> > Issues like this are very hardware specific; it'd be very unusual
> > for there to be a bug which affected *any* system with an HDMI
> > display, because the code for dealing with HDMI displays attached to
> > NVIDIA adapters is entirely different from the code for dealing with
> > HDMI displays attached to Intel adapters or AMD adapters.
> 
>   ... snip ...
> 
> i'll see what kind of debugging i can do this weekend based on the
> rest of your note, but here's one more brief data point related to my
> current 3.16.0-0.rc1.git3.1.fc21.x86_64 kernel.
> 
>   if i boot without HDMI connected to external monitor, it works. i
> can then plug in external monitor but when i reboot, the shutdown
> dumps a kernel stack trace.
> 
>   *however*, if i boot successfully without an external monitor, and
> subsequently never plug one in, then i can reboot just fine. so the
> problem rears its ugly head either:
> 
> 1) booting with HDMI-connected monitor, or
> 2) shutting down after having, at some point, connected a monitor via
> HDMI to the running system.
> 
>   in short, there's something about HDMI that's screwed, apparently
> related to this nouveau driver. more later as i debug further.

Yep, that sounds like an accurate summary. It would be interesting for
you to get logs from both the broken cases, and check whether you're
hitting the *same* traceback in each case.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net

-- 
test mailing list
test@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test





[Index of Archives]     [Fedora Desktop]     [Fedora SELinux]     [Photo Sharing]     [Yosemite Forum]     [KDE Users]

  Powered by Linux