[Bug 51081] [ivb] i915 insertion hangs machine

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Thu Dec 13 08:15:29 PST 2012


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





--- Comment #4 from alupu at verizon.net  2012-12-13 16:15:28 ---
(In reply to comment #3)
> Any update Alex?

Hi Jesse,

Same situation on 3.6.9
(no, I haven't looked at 3.6.10.  And I will look at 3.6.11 as well, as soon as
it comes out).  I don't expect (good) surprizes because Murphy's law is as 100%
valid and powerful now as when it was first stated:
"Left by themselves, things go from bad to worse."

And this bug has surely been left by itself.

> This will be tough to debug unless we can get more information
> information.  One way we debug hangs or graphics corruption is by using
> netconsole to direct kernel messages at another machine.
> https://wiki.ubuntu.com/Kernel/Netconsole has some info on that.
> 
> If you can modprobe i915 after setting drm.debug=0xf and capture the output
> from netconsole, we might be able to figure out where it hangs and what's
> causing it.

I'm presenting here a summary from the original Bug submission:
<<
In console/text mode (runlevel 3) [at] the command
modprobe i915 ... the keyboard and mouse become dead.

Note:  the system remains active "behind the scenes":
"magic-sysrq" works [and] remoting from another host (ssh/scp) works (thus the
attached dmesg log)

Created an attachment [with the dmesg] for
modprobe drm debug=6; modprobe i915
>>

QUESTIONS for you:

1.1.
Wasn't my dmesg attachment an example of the use of how "to direct kernel
messages at another machine"?

1.2.  Like I said, "remoting from another host (ssh/scp) works", so
why do I have to read instructions from a distribution I don't use (nor do I
intend to).
For the record, I've always used "BLFS" (Beyond Linux From Scratch).

2.  From your review of the "kernel messages" in my attachment, what was
missing so you haven't been able to proceed with the analysis, debug and fix?

3.  Was my 'drm debug=6' not informative enough, so that you want now
drm debug=0xf (or 15, as they say)?  

4.  What was it on 'drm debug=6' that was missing (in plain English so I
can get an idea)?

Thanks,
-- Alex

-- 
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.


More information about the intel-gfx-bugs mailing list