From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 15017] New: kexec regression, radeon/kms irq related (bisected)
Date: Sat, 9 Jan 2010 18:49:52 GMT [thread overview]
Message-ID: <bug-15017-2300@http.bugzilla.kernel.org/> (raw)
http://bugzilla.kernel.org/show_bug.cgi?id=15017
Summary: kexec regression, radeon/kms irq related (bisected)
Product: Drivers
Version: 2.5
Kernel Version: 2.6.33-rc3
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: markus@trippelsdorf.de
Regression: Yes
Commit d8f60cfc93452d0554f6a701aa8e3236cbee4636 (drm/radeon/kms: Add support
for interrupts on r6xx/r7xx chips) breaks kexec on my machine (amd64, RS780).
The computer just hangs right after the kexec call and I have to press the
reset button to get it running again.
2.6.32 worked flawlessly.
--
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
------------------------------------------------------------------------------
This SF.Net email is sponsored by the Verizon Developer Community
Take advantage of Verizon's best-in-class app development support
A streamlined, 14 day to market process makes app distribution fast and easy
Join now and get one step closer to millions of Verizon customers
http://p.sf.net/sfu/verizon-dev2dev
--
next reply other threads:[~2010-01-09 18:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 18:49 bugzilla-daemon [this message]
2010-01-13 22:10 ` [Bug 15017] kexec regression, radeon/kms irq related (bisected) bugzilla-daemon
2010-01-13 22:11 ` bugzilla-daemon
2010-01-15 13:50 ` bugzilla-daemon
2010-01-15 13:50 ` bugzilla-daemon
2010-01-15 13:51 ` bugzilla-daemon
2010-01-15 14:30 ` bugzilla-daemon
2010-01-25 21:05 ` bugzilla-daemon
2010-01-26 12:16 ` 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-15017-2300@http.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/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.