From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 22572] New: X doesn't start: "Prepare for strangeness..."
Date: Wed, 1 Jul 2009 00:19:01 -0700 (PDT) [thread overview]
Message-ID: <bug-22572-8800@http.bugs.freedesktop.org/> (raw)
http://bugs.freedesktop.org/show_bug.cgi?id=22572
Summary: X doesn't start: "Prepare for strangeness..."
Product: xorg
Version: unspecified
Platform: Other
URL: https://bugzilla.redhat.com/show_bug.cgi?id=504464
OS/Version: All
Status: NEW
Severity: major
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: shahamit-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
CC: shahamit-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
I've reported this bug at the Red Hat bugzilla for the issue I face in Fedora
11.
I've given the details at the link:
https://bugzilla.redhat.com/show_bug.cgi?id=504464
Some kernel messages I see are:
nouveau: nouveau_fifo_free: freeing fifo 1
nouveau: Failed to idle channel 1. Prepare for strangeness..
nouveau: PFIFO_DMA_PUSHER - Ch 1
nouveau: nouveau_fifo_free: freeing fifo 0
nouveau: PFIFO_DMA_PUSHER - Ch 1
The Xorg.0.log files are attached in the bugzilla link mentioned above.
driver version: xorg-x11-drv-nouveau-0.0.12-36.20090514git9656762.fc11.x86_64
--
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:[~2009-07-01 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-01 7:19 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-22572-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2010-10-13 18:49 ` [Bug 22572] X doesn't start: "Prepare for strangeness..." 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-22572-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.