From: "Éric Brunet" <Eric.Brunet@lps.ens.fr>
To: linux-kernel@vger.kernel.org
Cc: eric.brunet@lps.ens.fr
Subject: Some problem with nouveau
Date: Fri, 7 May 2010 15:57:15 +0200 [thread overview]
Message-ID: <201005071557.15728.Eric.Brunet@lps.ens.fr> (raw)
Hello,
I have HP Z400 desktop computer running in x86_64 mode with a fedora 12
installed on it. The computer has an nvidia (NV96) card, for which I am
using the nouveau driver.
Everything (meaning 2D acceleration) was working fine up to
kernel-2.6.31.12-174.2.22, and when fedora updated to 2.6.32.xxx (now
kernel-2.6.32.11-99) it stopped working. I also tried a vanilla 2.6.33.3
and it doesn't work either (I wouldn't dream bothering LKML without trying
a vanilla kernel...) Here are the symptoms:
when X is launched, the computer reboots instantaneously to the BIOS
greeting screen, leaving the computer in such a state that the BIOS is
enable to work (it never reaches grub, but keeps on rebooting after a few
seconds). Shutting down the computer is necessary to recover. I have no
useful log as the buffer have not been flushed: /var/log/Xorg.0.log is
found empty on the next reboot.
I filled a bug with fedora with more info (dmesg, lspci) on
https://bugzilla.redhat.com/show_bug.cgi?id=578108
but I had zero response.
So to sum up:
2.6.31.12 + fedora patches is working
2.6.32.xx + fedora patches is crashing horribly
2.6.33.xx vanilla is crashing in the same way.
Does that count as a regression ? I am a little bit at a loss as how to
provide debugging information on that one.
Thanks,
Éric Brunet
reply other threads:[~2010-05-07 14:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201005071557.15728.Eric.Brunet@lps.ens.fr \
--to=eric.brunet@lps.ens.fr \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®