From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 36248] New: Kernel 2.6.39-rc2: Boot logo causes Nouveau crash
Date: Thu, 14 Apr 2011 15:54:05 -0700 (PDT) [thread overview]
Message-ID: <bug-36248-8800@http.bugs.freedesktop.org/> (raw)
https://bugs.freedesktop.org/show_bug.cgi?id=36248
Summary: Kernel 2.6.39-rc2: Boot logo causes Nouveau crash
Product: xorg
Version: unspecified
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Driver/nouveau
AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
ReportedBy: nigel-jrkICu/7yk3k1uMJSBkQmQ@public.gmane.org
QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
Created an attachment (id=45640)
--> (https://bugs.freedesktop.org/attachment.cgi?id=45640)
Photo of oops
With the 2.6.39-rc2 kernel with Nouveau (KMS), I get an oops at boot if I have
the Boot Logo configuration option enabled, with the following backtrace:
nouveau_bo_wr32
nouveau_fbcon_sync
cfb_imageblit
snprintf
drm_crtc_helper_set_config
nouveau_fbcon_imageblit
fb_show_logo
fbcon_switch
redraw_screen
bind_con_driver
(I'll attach the screenshot, which has full details).
After some testing of disabling various configuration options, I found that
toggling CONFIG_LOGO stopped the oops.
The last kernel which I could successfully boot was 2.6.37. I could not boot
2.6.38, but couldn't get a backtrace then.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2011-04-14 22:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 22:54 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
[not found] ` <bug-36248-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-04-22 14:28 ` [Bug 36248] Kernel 2.6.39-rc2: Boot logo causes Nouveau crash bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-04-22 14:36 ` 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-36248-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.