[Bug 51921] Screen black, no action possible

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Tue Jan 8 09:11:14 PST 2013


https://bugzilla.kernel.org/show_bug.cgi?id=51921





--- Comment #7 from stathis <stathis at npcglib.org>  2013-01-08 17:11:14 ---
I just tried: drm-intel-901593f2bf221659a605bdc1dcb11376ea934163, but it still
freezes. I tried setting up netconsole, but I am uncertain if it is my setup,
as it doesn't log anything on the remote machine. 

Doesn't netconsole require that a working interface is configured? 
Bear in mind that my box freezes very early...

I tried to use netconsole by supplying nomodeset, so that I can figure out what
is going on with it. Turns out that drm is loaded before the netconsole at the
boot sequence, and (probably due to misconfiguration??) I see:

Jan  8 16:03:22 commell kernel: netpoll: netconsole: local port 6665
Jan  8 16:03:22 commell kernel: netpoll: netconsole: local IP 192.168.77.1   
Jan  8 16:03:22 commell kernel: netpoll: netconsole: interface 'eth1' 
Jan  8 16:03:22 commell kernel: netpoll: netconsole: remote port 6666
Jan  8 16:03:22 commell kernel: netpoll: netconsole: remote IP 192.168.77.100
Jan  8 16:03:22 commell kernel: netpoll: netconsole: remote ethernet address
00:25:22:a6:c0:e8   
Jan  8 16:03:22 commell kernel: netpoll: netconsole: eth1 doesn't exist,
aborting
Jan  8 16:03:22 commell kernel: netconsole: cleaning up

I read around about netconsole, but I run out of time, so let me know if it is
essential that I get netconsole to work in this case (since it appears to be
loaded after KMS). 

I am reading in the netconsole.txt documentation:

"As a built-in, netconsole initializes immediately after NIC cards and will
bring up the specified interface as soon as possible. While this doesn't allow
capture of early kernel panics, it does capture most of the boot process."

so probably this is not going to help much here?

thanks,
stathis

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the intel-gfx-bugs mailing list