From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 56541] New: Sony VAIO VPCZ23A4R: Oops or panic on radeon in error path
Date: Fri, 12 Apr 2013 15:49:03 +0000 (UTC) [thread overview]
Message-ID: <bug-56541-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=56541
Summary: Sony VAIO VPCZ23A4R: Oops or panic on radeon in error
path
Product: Drivers
Version: 2.5
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
AssignedTo: drivers_video-dri@kernel-bugs.osdl.org
ReportedBy: patrakov@gmail.com
CC: aaron.lu@intel.com
Regression: No
Created an attachment (id=98431)
--> (https://bugzilla.kernel.org/attachment.cgi?id=98431)
Dmesg from 3.9-rc5
This is a fork of bug #56501 and bug #55611. A separate bug is needed because a
decision was made to limit these two bugs to non-rescanning of the PCI bus.
Feel free, however, to refer to any relevant files (e.g. kernel configs and
DSDT dump) or comments attached to these bugs.
Due to yet another bug (#56531), the kernel fails to assign PCI resources to
the radeon card in the dock station. As you can see from the attached dmesg, it
causes an oops or even a panic in the radeon driver, among other bad things.
Please fix the radeon driver so that it doesn't dereference a kernel NULL
pointer even when given bad PCI resources.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2013-04-12 15:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-12 15:49 bugzilla-daemon [this message]
2013-04-12 23:19 ` [Bug 56541] Sony VAIO VPCZ23A4R: Oops or panic on radeon in error path bugzilla-daemon
2013-04-13 7:43 ` bugzilla-daemon
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-56541-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.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.