From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 96351] New: System hangs up after update to any kernel newer than 3.12*
Date: Wed, 08 Apr 2015 18:34:53 +0000 [thread overview]
Message-ID: <bug-96351-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=96351
Bug ID: 96351
Summary: System hangs up after update to any kernel newer than
3.12*
Product: Drivers
Version: 2.5
Kernel Version: 3.19.3-100.fc20.i686
Hardware: x86-64
OS: Linux
Tree: Fedora
Status: NEW
Severity: normal
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: georgechebanmk@gmail.com
Regression: No
Good day to you, comrades!
Have some problems with my notebook Packard Bell Easynote lj-71.
It has an old graphic HD 4650.
Now working on Fedora 20 with kernel 3.12.7-300.fc20.i686.
After update to any newer kernel, for example 3.17*/3.19* with any distro
(*buntu, fedora), 4.0* on Fedora 22 Alpha, system starts for a few minutes and
then always hangs up with black screen, especially when running video on
youtube for example. Alt+Ctrl+F2 doesn't work, only hard reset
Can start with "nomodeset" parameter, so I think that it's a radeon driver
problems.
Works normally only with stock kernel 3.12.
Also, described method in this topic
https://bugzilla.kernel.org/show_bug.cgi?id=71891 with radeon.dpm=0 doesn't
solves my problem.
Please advice, what else outputs I need to provide for more detailed
information? Working with linux for a few months, so don't have enough skills
to solve this problem on my own.
lspci -k | grep -A3 VGA
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI]
RV730/M96 [Mobility Radeon HD 4650/5165]
Subsystem: Acer Incorporated [ALI] Device 027e
Kernel driver in use: radeon
Kernel modules: radeon
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-04-08 18:34 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 18:34 bugzilla-daemon [this message]
2015-04-08 19:31 ` [Bug 96351] System hangs up after update to any kernel newer than 3.12* bugzilla-daemon
2015-04-09 7:54 ` bugzilla-daemon
2015-04-09 8:19 ` bugzilla-daemon
2015-04-09 8:26 ` bugzilla-daemon
2015-04-09 13:08 ` bugzilla-daemon
2015-04-09 13:17 ` bugzilla-daemon
2015-04-09 13:18 ` bugzilla-daemon
2015-04-09 13:18 ` bugzilla-daemon
2015-04-09 13:21 ` bugzilla-daemon
2015-04-09 13:28 ` bugzilla-daemon
2015-04-09 14:30 ` bugzilla-daemon
2015-04-09 14:31 ` bugzilla-daemon
2015-04-09 14:32 ` bugzilla-daemon
2015-04-09 14:34 ` bugzilla-daemon
2015-04-09 15:41 ` bugzilla-daemon
2015-04-20 13:52 ` bugzilla-daemon
2015-04-20 14:31 ` bugzilla-daemon
2015-04-21 2:04 ` bugzilla-daemon
2015-04-29 13:15 ` bugzilla-daemon
2015-04-29 13:17 ` bugzilla-daemon
2015-04-29 13:18 ` bugzilla-daemon
2015-04-29 14:57 ` bugzilla-daemon
2015-04-29 15:01 ` bugzilla-daemon
2015-04-29 15:15 ` bugzilla-daemon
2015-04-29 15:21 ` bugzilla-daemon
2015-04-29 15:30 ` bugzilla-daemon
2015-04-29 15:34 ` bugzilla-daemon
2015-04-29 16:27 ` bugzilla-daemon
2015-04-29 16:31 ` bugzilla-daemon
2015-04-30 2:30 ` bugzilla-daemon
2015-04-30 8:04 ` bugzilla-daemon
2015-04-30 8:05 ` bugzilla-daemon
2015-04-30 8:14 ` bugzilla-daemon
2015-05-01 1:46 ` bugzilla-daemon
2015-05-01 19:08 ` bugzilla-daemon
2015-05-01 22:08 ` bugzilla-daemon
2015-05-02 19:59 ` bugzilla-daemon
2015-05-02 20:40 ` bugzilla-daemon
2015-05-07 7:15 ` 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-96351-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox