Re: Nouveau regression between 3.6 and 3.7-rc3: driver stuck at"running init tables"

From: Ben Skeggs
Date: Mon Oct 29 2012 - 19:16:39 EST


On Tue, 2012-10-30 at 00:06 +0100, Mathieu Chouquet-Stringer wrote:
> Hi Ben,
Hey Mathieu,

>
> I haven't been able to boot any 3.7 kernels since there's a regression
> which freezes my machine hard (a lenovo t530 with the dreaded optimus
> thing).
>
> 3.6 used to work but 3.7 get stuck at (copied by hand but I have an ugly
> screenshot if you'd like):
> nouveau [ VBIOS][0000:01:00.0] running init tables
Are you able to go back to the current master, and get me a
log/screenshot with "nouveau.debug=trace" appended to your kernel
options?

Thanks,
Ben.

>
> Note my uefi settings weren't modified during the whole thing.
>
> I've bisected the issue and git found that commit 4196fa is the one
> causing trouble (looking at the diff, it's pretty big):
>
> Author: Ben Skeggs <bskeggs@xxxxxxxxxx>
> Date: Tue Jul 10 14:36:38 2012 +1000
>
> drm/nouveau/i2c: port to subdev interfaces
>
> v2/v3: Ben Skeggs <bskeggs@xxxxxxxxxx>
> - fix typo in default bus selection
> - fix accidental loss of destructor
>
> v4: Dmitry Eremin-Solenikov <dmitry_eremin@xxxxxxxxxx>
> - fix typo causing incorrect default i2c port settings when no BMP data
>
> While bisecting the matter, I had a couple of messages like the
> following (6 actually). The addresses were always different (I could
> send another ugly screenshot if you'd like).
>
> Condition still not met after 2000ms, skipping following opcodes
>
> followed by:
>
> Parsing VBIOUS init table 1 at offset 0x8183
>
> At this point, the kernel was frozen hard (sysrq wasn't working)...
>
> I'm attaching the output of lspci and my kernel config.
>
> If you'd like me to add some debug statements or if you need more info,
> feel free, I'd love to help.
>
> Cheers,
>


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/