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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 30 Oct 2012 00:06:48 +0100
From:	Mathieu Chouquet-Stringer <mathieu@...tco.com>
To:	bskeggs@...hat.com
Cc:	dri-devel@...ts.freedesktop.org, linux-kernel@...r.kernel.org
Subject: Nouveau regression between 3.6 and 3.7-rc3: driver stuck at "running
 init tables"

	Hi Ben,

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

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@...hat.com>
Date:   Tue Jul 10 14:36:38 2012 +1000

    drm/nouveau/i2c: port to subdev interfaces

    v2/v3: Ben Skeggs <bskeggs@...hat.com>
    - fix typo in default bus selection
    - fix accidental loss of destructor

    v4: Dmitry Eremin-Solenikov <dmitry_eremin@...tor.com>
    - 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,

-- 
Mathieu Chouquet-Stringer                         mathieu@...tco.com
            The sun itself sees not till heaven clears.
	             -- William Shakespeare --

View attachment "lspci" of type "text/plain" (31704 bytes)

View attachment "config" of type "text/plain" (110211 bytes)