From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 61321] New: [regression][NV4c] System hang while loading gdm on 3.7 kernel (works on 3.6)
Date: Sat, 23 Feb 2013 00:18:49 +0000 [thread overview]
Message-ID: <bug-61321-8800@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2305 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=61321
Priority: medium
Bug ID: 61321
Keywords: regression
Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Summary: [regression][NV4c] System hang while loading gdm on
3.7 kernel (works on 3.6)
QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Severity: major
Classification: Unclassified
OS: Linux (All)
Reporter: cesarb-PWySMVKUnqmsTnJN9+BGXg@public.gmane.org
Hardware: x86-64 (AMD64)
Status: NEW
Version: unspecified
Component: Driver/nouveau
Product: xorg
Since upgrading from a 3.6.10 kernel to a 3.7.9 kernel (Fedora 18), the system
started hanging while loading gdm. Going back to the 3.6 kernel works, going to
a 3.8 kernel hangs the same way.
The hang manifests first as the gdm spinning "loading" cursor stopping,
followed a few seconds later by a screen full of a repeated noise pattern
(different for each boot, but looks like a small block of noise tiled all over
the screen). The machine does not answer to the keyboard (num lock/caps lock
LEDs) or the network (by this point NetworkManager already started the
interface, so I can get a few pings before it hangs).
In particular, it is not the initial modeset when loading the module which
hangs; it is only gdm. If I boot with systemd.unit=multi-user.target, I can
boot without any hangs, load netconsole, and isolate graphical.target to load
gdm to see it hang. I used that to capture the kernel messages until the hang
for the Fedora 3.7.9 kernel.
I also managed to capture the Xorg.0.log for the attempt with the 3.8 kernel
(booting directly into graphical.target).
The relevant version numbers are:
kernel-3.6.10-4.fc18.x86_64 (works)
kernel-3.7.9-201.fc18.x86_64 (hangs)
Upstream 3.8 kernel with a Fedora config (hangs)
xorg-x11-server-Xorg-1.13.2-2.fc18.x86_64
xorg-x11-drv-nouveau-1.0.6-1.fc18.x86_64
libdrm-2.4.42-1.fc18.x86_64
mesa-dri-drivers-9.0.1-4.fc18.x86_64
I also attempted once booting 3.7.9 with nouveau.config=NvPCIE=0 as suggested
at bug #58776; it did not make any visible difference.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 3833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 181 bytes --]
_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau
next reply other threads:[~2013-02-23 0:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-23 0:18 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-61321-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-02-23 0:20 ` [Bug 61321] [regression][NV4c] System hang while loading gdm on 3.7 kernel (works on 3.6) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-23 0:21 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-23 0:22 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-23 0:25 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-23 0:28 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-23 18:27 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-23 18:35 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-23 19:34 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-23 19:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-23 19:37 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-23 20:38 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-29 10:54 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-04-10 8:18 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04 8:32 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-61321-8800@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
--cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.