From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 15131] New: After a short period there is a lockup (fifo)
Date: Wed, 19 Mar 2008 10:11:27 -0700 (PDT) [thread overview]
Message-ID: <bug-15131-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=15131
Summary: After a short period there is a lockup (fifo)
Product: xorg
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: debian-c6jxCJM9TyuJnvDnx1genB2eb7JE58TQ@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=15304)
--> (http://bugs.freedesktop.org/attachment.cgi?id=15304)
The X.org-log
As I was asked on IRC by marcheu to file a bug, I'll do it. attached you'll
find my Xorg.0.log and my kern.log. The xorg.conf looked like:
Section "Module"
#Load "GLcore"
Load "bitmap"
Load "dbe"
Load "ddc"
#Load "dri"
Load "extmod"
Load "freetype"
Load "glx"
Load "int10"
Load "record"
Load "speedo"
#Load "type1"
Load "vbe"
EndSection
Section "Device"
Identifier "nVidia Corporation NV10DDR [GeForce 256 DDR]"
Driver "nouveau"
BusID "PCI:1:0:0"
EndSection
First everthing was fine and X started. But after a while it started to switch
back and forth between tty1 and tty7 (on which the X server is running) and I
could glimpse at the things logged to kern.log. This cycle could only be broken
by Ctrl+Alt+Del or a hard reset. The first time I noticed that, was with
Randr12 enabled, but after I deactivated it and started again without Randr12
it lockedup also.
Please feel free to askt for any information, test or the like you'd like to
have. It's very likley that I haven't provided every information you might need
because it's my first bug for nouveau/randr12.
--
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2008-03-19 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-19 17:11 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-15131-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-03-19 17:12 ` [Bug 15131] After a short period there is a lockup (fifo) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-09-23 9:43 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-09-27 18:59 ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-09-27 21:12 ` 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-15131-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.