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

--- Comment #50 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
(In reply to comment #49)
> (In reply to comment #48)
> > Actually wait, there's an easier way of achieving this.
> > 
> > boot both the kernel from the last attempt (with hdaminv-4.patch) and a
> > working kernel, e.g. 3.7.10 with a "nouveau.config=PDISP=spam" parameter.
> > This should produce a very large quantity of logs in your dmesg. In fact it
> > might overflow your dmesg buffer, but it should all go through syslog. Let
> > me know if that boot parameter doesn't cause the logs to show up...
> 
> Hi Ilia,
> 
> I'm back in action.
> Are you talking about hdminva_3_-4.patch?
> Anyway, please quickly clarify the two(?) configurations you want me to test
> and compare (?) (I said I was back in action;  I didn't say I was fully
> awake).

Sorry, I should have been clearer.

1. 8e9e3d2deacc460fbb8a4691140318f6e85e6891 + hdmi-1.patch + hdminva3.patch +
hdminva3-4.patch

2. f7960736d0b8647fd149687d15deb79e47122d69

The second one is the revision without the two problematic commits that are the
reason for the patches. This should ensure that they are as similar as
possible.

> 
> BTW, (informational) speaking of dmesg overflow, you may have noticed I
> routinely started the kernel with "log_buf_len=1M" lately.

Ah, that's good. BTW, you might consider going into #nouveau on freenode IRC to
avoid some of this back-and-forth.

-- 
You are receiving this mail because:
You are the assignee for the bug.