linux-kernel - Re: Reboot problem with nouveau

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 29 May 2013 10:47:00 -0400
From:	Marc Dionne <marc.c.dionne@...il.com>
To:	Ben Skeggs <skeggsb@...il.com>, Dave Airlie <airlied@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Reboot problem with nouveau - bisected

On Thu, Apr 18, 2013 at 2:14 PM, Marc Dionne <marc.c.dionne@...il.com> wrote:
> My machine has been getting stuck when rebooting during the current
> 3.9 cycle, and yesterday I took the time to bisect the problem to this
> commit:
>
> 32256c87ead3edec86bed5023a0ff96a6d907931:  drm/nouveau/fifo/nvc0:
> improve interrupt handler somewhat
>
>     Logs extra info for interrupts that have a sub-status register, and
>     handles the "special" ack from INTR bit 31.
>
>     Signed-off-by: Ben Skeggs <bskeggs@...hat.com>
>
> The symptom when rebooting is that the console starts spitting out a
> continuous stream of identical messages like this (transcribed by
> hand):
>
>     nouveau W[   PFIFO][0000:03:00.0] INTR 0x01000000: 0x00000005
>
> The system is then unresponsive until it is reset.  Just commenting
> out the corresponding nv_warn() in
> drivers/gpu/drm/nouveau/core/engine/fifo/nvc0.c is enough to allow the
> system to reboot normally.
>
> Video card in this system is (from lspci -v):
>
> 03:00.0 VGA compatible controller: NVIDIA Corporation GF119 [GeForce
> GT 520] (rev a1) (prog-if 00 [VGA controller])
>     Subsystem: Micro-Star International Co., Ltd. Device 2630
>     Flags: bus master, fast devsel, latency 0, IRQ 16
>     Memory at fa000000 (32-bit, non-prefetchable) [size=16M]
>     Memory at d8000000 (64-bit, prefetchable) [size=128M]
>     Memory at d6000000 (64-bit, prefetchable) [size=32M]
>     I/O ports at bc00 [size=128]
>     Expansion ROM at fbb80000 [disabled] [size=512K]
>     Capabilities: <access denied>
>     Kernel driver in use: nouveau
>
> Marc

Ping..

Any ideas on this one?  This machine still needs a hard reset to
reboot as of 3.10-rc3, with the same symptoms as described above.

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