All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 65827] New: computer often fails to boot with nouveau and GeForce GT 425M on newest Linux kernel
Date: Sun, 16 Jun 2013 13:49:33 +0000	[thread overview]
Message-ID: <bug-65827-8800@http.bugs.freedesktop.org/> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2856 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=65827

          Priority: medium
            Bug ID: 65827
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: computer often fails to boot with nouveau and GeForce
                    GT 425M on newest Linux kernel
          Severity: critical
    Classification: Unclassified
                OS: Linux (All)
          Reporter: j.pertres-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: 9.1
         Component: Drivers/DRI/nouveau
           Product: Mesa

Created attachment 80911
  --> https://bugs.freedesktop.org/attachment.cgi?id=80911&action=edit
screen shot of my screen on boot

When I turn my computer on, at some point of the booting process I get an
endless cascade of almost-identical error messages like "[   45.935830] nouveau
E(   PFIFO][0000:01:00.0] SUBFIFO0: (unknown bits 0x00004000)" (see image
attached). Apparently the computer doesn't respond to any input, so the only
thing I can do is force it to shut down by pressing the power button long.

Most of the times, the system boots OK at the second try, but not even always.
If I'm not successful after several attempts, I choose the LTS kernel (3.0.82
instead of 3.9.6) from my GRUB and then this won't happen.

It looks like these error logs messages are not properly kept as log files,
probably because I have to interrupt the boot process this way. A 'grep -R
"unknown bits"' from /var/log only finds matches in five *.journal binary files
in the directory /var/log/journal. This is why I attach a real-world picture of
my screen instead of a log file.

One of the last times that I managed to boot with the 3.9 kernel, I noticed
that in the file /proc/fb I only had "0 inteldrmfb". Now I am on the 3.0 kernel
and I have
"0 inteldrmfb
1 nouveaufb"

On the other hand, the command 'lspci -v | grep VGA' returns similar output on
both kernels:
- On 3.9 kernel:
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated
Graphics Controller (rev 02) (prog-if 00 [VGA controller])
01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 425M]
(rev ff) (prog-if ff)

- And on 3.0 kernel:
00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated
Graphics Controller (rev 02) (prog-if 00 [VGA controller])
01:00.0 VGA compatible controller: NVIDIA Corporation GF108M [GeForce GT 425M]
(rev a1) (prog-if 00 [VGA controller])

This has been happening for several months already, so the problem didn't start
with kernel 3.9 but earlier.

All this said, even if I manage to boot, it looks like my NVIDIA card is never
used by any program, only the Intel one. GPU never seems to be available.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 4313 bytes --]

[-- Attachment #2: Type: text/plain, Size: 181 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2013-06-16 13:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-16 13:49 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-65827-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-06-16 17:53   ` [Bug 65827] computer often fails to boot with nouveau and GeForce GT 425M on newest Linux kernel bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-27  0:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-27  0:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-04 20:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-04 20:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-27 15:23   ` 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-65827-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.