https://bugzilla.kernel.org/show_bug.cgi?id=60523
--- Comment #51 from Alex Belykh ---
And not here. Applying this patch on top of latest drm-next
(786a7828bc74b9b1466e83abb200b75f80f94121) resulted in the same kind of lockups
ending with reboot.
--
You are receiving this mail because:
You are
https://bugzilla.kernel.org/show_bug.cgi?id=68571
--- Comment #34 from Mihai Coman ---
Is there a compiled kernel available for ubuntu that includes this patch?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71891
Bug ID: 71891
Summary: 3.13 fails to boot with the radeon module
Product: Drivers
Version: 2.5
Kernel Version: 3.13.6-1-ARCH
Hardware: x86-64
OS: Linux
Tree: M
https://bugzilla.kernel.org/show_bug.cgi?id=71891
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #1 fr
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #2 from sdh ---
Booting with 3.12 kernel gives no such error. Using 3.13, booting from the Arch
install iso gives the above errors.
The only difference with radeon.dpm=0 is that the line
"rv770_restrict_performance_levels_before_switc
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #3 from Alex Deucher ---
if 3.12 works, can you use git to bisect?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #4 from sdh ---
Have never done it before. Will attempt to do it when I have some free time and
report back :)
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #11 from Tom Yan ---
One of my other machines with an HD6450 shows similar issue. I unplugged the
DVI connector before boot up and I can't get any display when I connect it
again afterwards.
--
You are receiving this mail because:
Yo
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #12 from Alex Deucher ---
Does booting with radeon.runpm=0 on the kernel command line in grub help?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #13 from Tom Yan ---
Unfortunately, no.
Yet it seems that now (with kernel 3.13.6) disconnecting HDMI and DVI doesn't
shows a problem anymore. Only DisplayPort still got issue. (Though, if I don't
have anything connected before boot,
https://bugzilla.kernel.org/show_bug.cgi?id=46711
Andrew Engelbrecht changed:
What|Removed |Added
CC||sudoman at ninthfloor.org
--- Commen
https://bugzilla.kernel.org/show_bug.cgi?id=70171
Andreas changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=70171
Andreas changed:
What|Removed |Added
Summary|kernel/time/tick-broadcast. |3.13.x:
|c:668 exception and
https://bugzilla.kernel.org/show_bug.cgi?id=72701
Bug ID: 72701
Summary: Screen freeze when using radeon driver
Product: Drivers
Version: 2.5
Kernel Version: 3.13 and 3.14
Hardware: All
OS: Linux
Tree: Mainlin
https://bugzilla.kernel.org/show_bug.cgi?id=72701
klod changed:
What|Removed |Added
Hardware|All |x86-64
Severity|normal
https://bugzilla.kernel.org/show_bug.cgi?id=72701
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #1 fr
https://bugzilla.kernel.org/show_bug.cgi?id=72701
--- Comment #2 from klod ---
Yes, it does. Thank you :)
I can't find any documentation on radeon parameters, but I guess that has
something to do with power management. I tried radeon.dpm=0 earlier, but it
didn't work. I hope this issue will be re
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #14 from Tom Yan ---
The problem with DisplayPort seems to related to DPMS. All I need to do to get
back the display is to make sure that there is a state change after the monitor
is turned on again.
--
You are receiving this mail be
https://bugzilla.kernel.org/show_bug.cgi?id=71461
--- Comment #15 from Tom Yan ---
(In reply to Tom Yan from comment #14)
> The problem with DisplayPort seems to related to DPMS. All I need to do to
> get back the display is to make sure that there is a state change after the
> monitor is turned
https://bugzilla.kernel.org/show_bug.cgi?id=72701
--- Comment #3 from Alex Deucher ---
These patches should fix it:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=9babd35ad72af631547c7ca294bc2e931cc40e58
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/com
https://bugzilla.kernel.org/show_bug.cgi?id=72701
--- Comment #4 from klod ---
Just a few questions:
1. - What are "PX" and "non-PX" cards?
2. - Aren't these going to disable power management in my GPU? What's the
difference between applying those and using "radeon.runpm=0" in grub?
3. - How
https://bugzilla.kernel.org/show_bug.cgi?id=72701
--- Comment #5 from Alex Deucher ---
(In reply to klod from comment #4)
> Just a few questions:
>
> 1. - What are "PX" and "non-PX" cards?
PX = PowerXpress. PX systems are laptops with two GPUs, an integrated and a
discrete GPU.
>
> 2. - Aren
https://bugzilla.kernel.org/show_bug.cgi?id=72701
--- Comment #6 from klod ---
Well, "radeon.runpm=0" allows me to boot and use the system, but with much
higher temperature and shorter battery life. I wouldn't call that "fixing the
issue", as it's still worse than what I have with 3.12 and "radeo
https://bugzilla.kernel.org/show_bug.cgi?id=66731
Eric Blackwell changed:
What|Removed |Added
Component|Video(DRI - non Intel) |Other
Product|Drivers
https://bugzilla.kernel.org/show_bug.cgi?id=22312
Chris Nystrom changed:
What|Removed |Added
CC||cnystrom at gmail.com
--- Comment #8 from
https://bugzilla.kernel.org/show_bug.cgi?id=22312
--- Comment #9 from Alex Deucher ---
(In reply to Chris Nystrom from comment #8)
> Yes. I am having this exact error message with a live Fedora 20 DVD on a
> Dell OptiPlex 780 with a PCIe ASUS Radeon R7 240 video card. The desktop
> never comes up
https://bugzilla.kernel.org/show_bug.cgi?id=22312
--- Comment #10 from Alex Deucher ---
If you are running a 3.13 or newer kernel, try appending radeon.runpm=0 to the
kernel command line in grub.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=68571
--- Comment #35 from kilobug at kilobug.org ---
So, I finally could perform some tests. Two notes first :
1. Meanwhile I upgraded to Mesa 10.1.0.
2. The patch seemed to be already included in the drm-fixes-3.14 branch, so I
just tested with the l
https://bugzilla.kernel.org/show_bug.cgi?id=68571
--- Comment #36 from Mihai Coman ---
With DPM=1 I still get gpu lockups with 3.14rc8 and mesa 10.2~git1403270730. It
locks up with black screen or a pattern after a few minutes of playing OpenGL
games or playing videos with VDPAU. I don't recall e
https://bugzilla.kernel.org/show_bug.cgi?id=73291
Bug ID: 73291
Summary: Kernel 3.13.7 boots with hybrid Intel/ATI but to blank
graphical screen
Product: Drivers
Version: 2.5
Kernel Version: 3.13.7
Hardware: x86-64
https://bugzilla.kernel.org/show_bug.cgi?id=73291
--- Comment #1 from Mike Cloaked ---
Created attachment 131081
--> https://bugzilla.kernel.org/attachment.cgi?id=131081&action=edit
xorg log for kernel 3.13.6
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=73291
--- Comment #2 from Mike Cloaked ---
Created attachment 131091
--> https://bugzilla.kernel.org/attachment.cgi?id=131091&action=edit
systemd journal for current boot with kernel 3.13.7
--
You are receiving this mail because:
You are watching th
https://bugzilla.kernel.org/show_bug.cgi?id=73291
--- Comment #3 from Mike Cloaked ---
Created attachment 131101
--> https://bugzilla.kernel.org/attachment.cgi?id=131101&action=edit
xorg log for kernel 3.13.7
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=73291
--- Comment #4 from Mike Cloaked ---
The system is dual boot arch linux and Windows 8.1, boot is UEFI using the
rEFInd boot manager, but that should not be relevant to the fail mode reported
in this bugzilla.
--
You are receiving this mail becau
https://bugzilla.kernel.org/show_bug.cgi?id=73291
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #5 fr
https://bugzilla.kernel.org/show_bug.cgi?id=73291
--- Comment #6 from Mike Cloaked ---
Perhaps this warning will not occur when kernel 3.14.x is used when it is
released to arch in the near future. I presume that new patches in kernel
3.13.7 makes the difference between a successful boot to graph
https://bugzilla.kernel.org/show_bug.cgi?id=73291
--- Comment #7 from Alex Deucher ---
(In reply to Mike Cloaked from comment #6)
> Perhaps this warning will not occur when kernel 3.14.x is used when it is
> released to arch in the near future. I presume that new patches in kernel
> 3.13.7 makes
https://bugzilla.kernel.org/show_bug.cgi?id=73291
--- Comment #8 from Mike Cloaked ---
What I am seeing seems to be the same as in the Fedora bug at:
https://bugzilla.redhat.com/show_bug.cgi?id=1070219
I don't have the system set up for bisecting. However I will boot with the
radeon driver blac
https://bugzilla.kernel.org/show_bug.cgi?id=73291
--- Comment #9 from Mike Cloaked ---
Booting with modprobe.blacklist=radeon added to the kernel line in the rEFInd
boot manager gives a successful boot to a graphical screen. So thank you, this
is a workaround for the present.
I can upload the s
https://bugzilla.kernel.org/show_bug.cgi?id=73291
--- Comment #10 from Mike Cloaked ---
Created attachment 13
--> https://bugzilla.kernel.org/attachment.cgi?id=13&action=edit
systemd journal with 3.13.7 booted with radeon module blacklisted
--
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=73291
--- Comment #11 from Mike Cloaked ---
For completeness I removed the radeon module from the initial ramdisk, and
added:
install radeon /bin/false
to the file /etc/modprobe.d/blacklist.conf
Now the system boots to a working graphical screen for
https://bugzilla.kernel.org/show_bug.cgi?id=73291
Mike Cloaked changed:
What|Removed |Added
Regression|No |Yes
--
You are receiving this mail becaus
https://bugzilla.kernel.org/show_bug.cgi?id=70651
--- Comment #12 from Fabio Sangiovanni ---
hi, thank you Alex.
To be clear, I absolutely didn't mean to rush you, just making myself available
for testing and helping out as much as I can.
I understand the fact that it's not possible to access as
https://bugzilla.kernel.org/show_bug.cgi?id=75211
--- Comment #1 from Michel D?nzer ---
(In reply to Darren Salt from comment #0)
> I'm seeing a divide error during X startup, causing X to hang (requiring
> reboot to clear). The trigger is a commit in xserver git:
>
> commit 4c3932620c29c91dfbbc
https://bugzilla.kernel.org/show_bug.cgi?id=75211
Christian K?nig changed:
What|Removed |Added
CC||deathsimple at vodafone.de
--- Comment
https://bugzilla.kernel.org/show_bug.cgi?id=75241
Bug ID: 75241
Summary: radeon_compute_pll_avivo broken in 3.15-rc3
Product: Drivers
Version: 2.5
Kernel Version: 3.15-rc3
Hardware: All
OS: Linux
Tree: Mainlin
https://bugzilla.kernel.org/show_bug.cgi?id=75211
--- Comment #3 from Darren Salt ---
I didn't rebuild the DDX. (May be worth doing just to see if the kernel bug is
still triggered.)
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=75241
Christian K?nig changed:
What|Removed |Added
CC||deathsimple at vodafone.de
--- Comment
https://bugzilla.kernel.org/show_bug.cgi?id=75211
--- Comment #4 from Darren Salt ---
It appears that you do actually need mismatched builds of xserver git and
xf86-video-ati git, the latter built against (ideally) 1.15.99.902, to trigger
this kernel bug... I wonder why it's gone apparently unnot
https://bugzilla.kernel.org/show_bug.cgi?id=75211
--- Comment #5 from Christian K?nig ---
(In reply to Darren Salt from comment #4)
> It appears that you do actually need mismatched builds of xserver git and
> xf86-video-ati git, the latter built against (ideally) 1.15.99.902, to
> trigger this k
https://bugzilla.kernel.org/show_bug.cgi?id=75241
--- Comment #2 from Christian K?nig ---
Created attachment 134611
--> https://bugzilla.kernel.org/attachment.cgi?id=134611&action=edit
Possible fix.
Please try the attached patch, it might fix the issue.
--
You are receiving this mail because
https://bugzilla.kernel.org/show_bug.cgi?id=75211
--- Comment #6 from Christian K?nig ---
And please provide the output of:
gdb /lib/modules/$(uname -r)/kernel/drivers/gpu/drm/radeon/radeon.ko -ex 'list
*(radeon_compute_pll_avivo+0xb6)' -ex q
Thanks in advance,
Christian.
--
You are receiving
https://bugzilla.kernel.org/show_bug.cgi?id=75241
--- Comment #3 from Clemens Ladisch ---
3.14:
16205, pll dividers - fb: 135.8 ref: 2, post 6
With the patch:
162000 - 161990, pll dividers - fb: 271.5 ref: 4, post 6
And the patch indeed fixes this.
--
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=75211
--- Comment #7 from Darren Salt ---
Can't do that (radeon module is built in, and no debug symbols ? should switch
that on), but ksymoops output (below) is clear enough for me to determine that
the marked line is where the bug makes itself known:
https://bugzilla.kernel.org/show_bug.cgi?id=74911
--- Comment #5 from Michel D?nzer ---
(In reply to Ivan Bulatovic from comment #3)
> Apologies, it opts out after a minute just like you've said it would.
Yep, that timeout is one of the biggest downsides of building the driver into
the kernel in
https://bugzilla.kernel.org/show_bug.cgi?id=74911
--- Comment #6 from Michel D?nzer ---
(In reply to Ivan Bulatovic from comment #2)
> Don't mean to be rude or anything, but I don't know if it is recommended (or
> desirable) to commit a piece of code to mainline that will _require_ a blob
> that
https://bugzilla.kernel.org/show_bug.cgi?id=75211
--- Comment #8 from Christian K?nig ---
Created attachment 134701
--> https://bugzilla.kernel.org/attachment.cgi?id=134701&action=edit
Possible fix.
Please try to reproduce the issue with the attached patch applied.
It would still not work cor
https://bugzilla.kernel.org/show_bug.cgi?id=75241
--- Comment #4 from Christian K?nig ---
(In reply to Clemens Ladisch from comment #3)
> 3.14:
> 16205, pll dividers - fb: 135.8 ref: 2, post 6
>
> With the patch:
> 162000 - 161990, pll dividers - fb: 271.5 ref: 4, post 6
>
> And the patch indee
https://bugzilla.kernel.org/show_bug.cgi?id=75211
--- Comment #9 from Darren Salt ---
No crash now.
However, the kernel log is spammed with
[drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:14]
I did notice what looked like some X spam too, but that's been lost over an X
re
https://bugzilla.kernel.org/show_bug.cgi?id=75241
--- Comment #5 from Clemens Ladisch ---
It's an Eizo S2100, but this should not matter because the clocks seen by the
monitor are always about the same (162MHz/75kHz/60Hz). If some were out of
range, the monitor would show an error message, but w
https://bugzilla.kernel.org/show_bug.cgi?id=75241
--- Comment #6 from Christian K?nig ---
(In reply to Clemens Ladisch from comment #5)
> It's an Eizo S2100, but this should not matter because the clocks seen by the
> monitor are always about the same (162MHz/75kHz/60Hz). If some were out of
> r
https://bugzilla.kernel.org/show_bug.cgi?id=75211
--- Comment #10 from Christian K?nig ---
(In reply to Darren Salt from comment #9)
> No crash now.
Good, thanks for testing.
> However, the kernel log is spammed with
> [drm:drm_crtc_helper_set_config] *ERROR* failed to set mode on [CRTC:14]
https://bugzilla.kernel.org/show_bug.cgi?id=75401
Bug ID: 75401
Summary: vgaswtitcheroo doesn't work for AMD Radeon 8870m
(possibly due to "wrong" PCI class)
Product: Drivers
Version: 2.5
Kernel Version: 3.11.10
Hardwar
https://bugzilla.kernel.org/show_bug.cgi?id=75401
--- Comment #1 from drill87 at gmail.com ---
Created attachment 134941
--> https://bugzilla.kernel.org/attachment.cgi?id=134941&action=edit
Output of "lspci -nn" command
This log has wring revision number for radeon 8870m (rev ff), because right
https://bugzilla.kernel.org/show_bug.cgi?id=75401
drill87 at gmail.com changed:
What|Removed |Added
Summary|vgaswtitcheroo doesn't work |vgaswitcheroo doesn't work
https://bugzilla.kernel.org/show_bug.cgi?id=68571
creich changed:
What|Removed |Added
CC||creich at linux.com
--- Comment #38 from creich
https://bugzilla.kernel.org/show_bug.cgi?id=75471
Bug ID: 75471
Summary: Black screen with frequency out of range with kernel
3.15-rc3 on radeon RS880
Product: Drivers
Version: 2.5
Kernel Version: 3.15-rc3
Hardware: x86
https://bugzilla.kernel.org/show_bug.cgi?id=75471
--- Comment #1 from Tasev Nikola ---
Created attachment 135081
--> https://bugzilla.kernel.org/attachment.cgi?id=135081&action=edit
dmesg working 3.15-rc2 kernel
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=75471
Christian K?nig changed:
What|Removed |Added
CC||deathsimple at vodafone.de
--- Comment
https://bugzilla.kernel.org/show_bug.cgi?id=75471
--- Comment #3 from Tasev Nikola ---
Oop's
Ignore my first post, i must made a copy paste error somewhere !
The first bad commit is indeed this one :
c2fb3094669a3205f16a32f4119d0afe40b1a1fd is the first bad commit
commit c2fb3094669a3205f16a32
https://bugzilla.kernel.org/show_bug.cgi?id=75471
--- Comment #4 from Tasev Nikola ---
Created attachment 135091
--> https://bugzilla.kernel.org/attachment.cgi?id=135091&action=edit
git bisect 3.15-rc3 3.15-rc2 log
--
You are receiving this mail because:
You are watching the assignee of the b
https://bugzilla.kernel.org/show_bug.cgi?id=75471
Tasev Nikola changed:
What|Removed |Added
Regression|No |Yes
--
You are receiving this mail becaus
https://bugzilla.kernel.org/show_bug.cgi?id=51381
newgarry at mail.ru changed:
What|Removed |Added
CC||newgarry at mail.ru
--- Comment #8 f
https://bugzilla.kernel.org/show_bug.cgi?id=51381
--- Comment #9 from newgarry at mail.ru ---
Created attachment 135131
--> https://bugzilla.kernel.org/attachment.cgi?id=135131&action=edit
kernel log
Kernel log includes suspend-resume info and error messages.
--
You are receiving this mail be
https://bugzilla.kernel.org/show_bug.cgi?id=51381
newgarry at mail.ru changed:
What|Removed |Added
Attachment #135131|text/x-log |text/plain
mime type|
https://bugzilla.kernel.org/show_bug.cgi?id=74631
--- Comment #2 from tigrangab at gmail.com ---
I may be able to, but not for a couple weeks unfortunately.
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=51381
--- Comment #10 from Alex Deucher ---
(In reply to newgarry from comment #8)
>
> Without parameter "runpm=0" my system rusumes immediately. Please let me
> know if you need additional information. Thank you!
Are you saying that everything is wor
https://bugzilla.kernel.org/show_bug.cgi?id=75401
Alex Deucher changed:
What|Removed |Added
CC||alexdeucher at gmail.com
--- Comment #2 fr
https://bugzilla.kernel.org/show_bug.cgi?id=74751
--- Comment #17 from Tasev Nikola ---
Hi,
I just tested 3.15-rc4 today and the bug is still there.
Is it something that i could do/test to help debug this ?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=51381
--- Comment #11 from newgarry at mail.ru ---
(In reply to Alex Deucher from comment #10)
> Are you saying that everything is working properly without runpm=0?
Yes, it is. System resumes immediately and without error messages.
--
You are receivin
https://bugzilla.kernel.org/show_bug.cgi?id=75401
drill87 at gmail.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #30 from sdh ---
Hi. Any update on this?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=75401
--- Comment #4 from Alex Deucher ---
Created attachment 135221
--> https://bugzilla.kernel.org/attachment.cgi?id=135221&action=edit
fix for rom fetching
Does this patch fix the issue?
--
You are receiving this mail because:
You are watching t
https://bugzilla.kernel.org/show_bug.cgi?id=75651
Bug ID: 75651
Summary: resume from suspend failing 3.15(rc1,rc2,rc3,rc4)
bisected
Product: Drivers
Version: 2.5
Kernel Version: 3.15
Hardware: All
OS: Li
https://bugzilla.kernel.org/show_bug.cgi?id=75701
Bug ID: 75701
Summary: Radeon: GPU recovery is unable to recover from GPU
lockups (HD5770 - OpenCL example).
Product: Drivers
Version: 2.5
Kernel Version: 3.15-rc4
Hardw
https://bugzilla.kernel.org/show_bug.cgi?id=75711
Bug ID: 75711
Summary: Radeon: GPU recovery is unable to recover from GPU
lockups (R9 270 - error in VDPAU).
Product: Drivers
Version: 2.5
Kernel Version: 3.15-rc4
Hardw
https://bugzilla.kernel.org/show_bug.cgi?id=68571
--- Comment #39 from kilobug at kilobug.org ---
I still have the problem with 3.14.2. Are you sure you enabled dpm ? Due to
this bug, dpm is disabled by default on 3.14 for this chipset, you need to
force it enabled.
--
You are receiving this mai
https://bugzilla.kernel.org/show_bug.cgi?id=75401
--- Comment #5 from drill87 at gmail.com ---
I guess it fixes. At least, I can see no errors for radeon module in dmesg.
Vgaswitcheroo, as I aforementioned, works too (I can turn off the card, so
notebook heats less).
However, I cannot say any mo
https://bugzilla.kernel.org/show_bug.cgi?id=75401
--- Comment #6 from drill87 at gmail.com ---
Created attachment 135541
--> https://bugzilla.kernel.org/attachment.cgi?id=135541&action=edit
dmesg after applying "fix for rom fetching" patch
--
You are receiving this mail because:
You are watchi
https://bugzilla.kernel.org/show_bug.cgi?id=75401
Pali Roh?r changed:
What|Removed |Added
CC||pali.rohar at gmail.com
--- Comment #7 from
https://bugzilla.kernel.org/show_bug.cgi?id=75401
--- Comment #8 from Alex Deucher ---
ATRM is an acpi method for fetching the rom on certain systems. If your system
was able to fetch the rom via another method, it may not use ATRM.
I'm not sure if the ATRM method is required in drill87's case
https://bugzilla.kernel.org/show_bug.cgi?id=75401
--- Comment #9 from drill87 at gmail.com ---
Oh, I'm sorry, it seems I didn't write it clear enough. I mentioned file
"radeon_bios.c" only because I saw there too goes PCI class checl only against
PCI_CLASS_DISPLAY_VGA, but there wasn't additional
https://bugzilla.kernel.org/show_bug.cgi?id=75401
--- Comment #10 from drill87 at gmail.com ---
Created attachment 135561
--> https://bugzilla.kernel.org/attachment.cgi?id=135561&action=edit
dmesg before applying "fix for rom fetching" patch
--
You are receiving this mail because:
You are watc
https://bugzilla.kernel.org/show_bug.cgi?id=75401
--- Comment #11 from Alex Deucher ---
Looks like it works fine without the patch as well. That said, the ATRM patch
shouldn't hurt anything if there ever ends up being a case where the ATRM
method is hung off a non-VGA display device.
--
You ar
https://bugzilla.kernel.org/show_bug.cgi?id=66281
Gaurav Shukla changed:
What|Removed |Added
CC||areyaargaurav at gmail.com
--- Comment #2
https://bugzilla.kernel.org/show_bug.cgi?id=66281
--- Comment #3 from Ilia Mirkin ---
Make sure that
(a) You're using a kernel 3.14 or higher (3.13 introduced modesetting but not
the firmware required for acceleration for the gk208)
(b) You're not using bumblebee (3.12 introduced runtime pm supp
https://bugzilla.kernel.org/show_bug.cgi?id=66281
--- Comment #4 from Gaurav Shukla ---
(In reply to Ilia Mirkin from comment #3)
> Make sure that
>
> (a) You're using a kernel 3.14 or higher (3.13 introduced modesetting but
> not the firmware required for acceleration for the gk208)
> (b) You'r
https://bugzilla.kernel.org/show_bug.cgi?id=66281
Ilia Mirkin changed:
What|Removed |Added
CC||imirkin at alum.mit.edu
--- Comment #5 from
https://bugzilla.kernel.org/show_bug.cgi?id=75841
Bug ID: 75841
Summary: radeon (radeonsi): GPU crash and resulting kernel
problems (hangs etc.)
Product: Drivers
Version: 2.5
Kernel Version: 3.15-rc3
Hardware: x86-64
https://bugzilla.kernel.org/show_bug.cgi?id=75841
--- Comment #1 from darkbasic ---
The same with TAHITI (HD 7950).
--
You are receiving this mail because:
You are watching the assignee of the bug.
3101 - 3200 of 5870 matches
Mail list logo
