https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #15 from Marko Kohtala ---
I tried with Ubuntu 13.10 live, and the screen corruption appeared. So it was
not a BIOS fix.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=44800
Marko Kohtala changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #13 from Marko Kohtala 2012-08-19
18:09:19 UTC ---
I applied "drm/radeon: cleanup and fix crtc while programming mc" and
"drm/radeon: fence virtual address and free it once idle [3.5] v2" on top of
3.5.2.
Did not change this. I saw
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #13 from Marko Kohtala marko.koht...@gmail.com 2012-08-19
18:09:19 UTC ---
I applied drm/radeon: cleanup and fix crtc while programming mc and
drm/radeon: fence virtual address and free it once idle [3.5] v2 on top of
3.5.2.
Did not
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #12 from Marko Kohtala 2012-08-14
15:44:40 UTC ---
I have also tried booting in BIOS mode using Ubuntu 12.04 live USB. It does not
help.
The board is "New P67 B3 Revision".
I have since upgraded to BIOS 3602. Same problem is still
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #11 from Reartes Guillermo 2012-08-14
13:16:04 UTC ---
@Marko Kohtala
Currently you are bootin in UEFI mode.
Can you boot in BIOS mode to test?
Your board is P8P67-M with BIOS 1701
Is your board "Rev B"?
Also check asus website,
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #11 from Reartes Guillermo rtgui...@gmail.com 2012-08-14 13:16:04
UTC ---
@Marko Kohtala
Currently you are bootin in UEFI mode.
Can you boot in BIOS mode to test?
Your board is P8P67-M with BIOS 1701
Is your board Rev B?
Also
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #12 from Marko Kohtala marko.koht...@gmail.com 2012-08-14
15:44:40 UTC ---
I have also tried booting in BIOS mode using Ubuntu 12.04 live USB. It does not
help.
The board is New P67 B3 Revision.
I have since upgraded to BIOS 3602.
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #10 from Alexandre Demers
2012-08-10 20:07:23 UTC ---
May or may not be related, but I've seen similar corruption with CAYMAN related
to bug 45018 from time to time. But about comment 3, I was tempted to point at
bug 42373.
Marko,
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #10 from Alexandre Demers alexandre.f.dem...@gmail.com 2012-08-10
20:07:23 UTC ---
May or may not be related, but I've seen similar corruption with CAYMAN related
to bug 45018 from time to time. But about comment 3, I was tempted to
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #9 from Marko Kohtala 2012-01-16
11:43:20 PST ---
Created attachment 55651
--> https://bugs.freedesktop.org/attachment.cgi?id=55651
Artefacts in X, screencapture
This capture was with the enable_mtrr_cleanup mtrr_spare_reg_nr=1
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #8 from Marko Kohtala 2012-01-16
11:26:00 PST ---
Created attachment 55650
--> https://bugs.freedesktop.org/attachment.cgi?id=55650
dmesg with enable_mtrr_cleanup
Attached the dmesg with The /proc/mtrr is
reg00:
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #7 from Michel D?nzer 2012-01-16 03:23:43
PST ---
The panic backtrace doesn't look obviously related to the radeon driver ? all
the symptoms sound like something might be scribbling more or less randomly
over memory.
I wonder if
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #7 from Michel Dänzer mic...@daenzer.net 2012-01-16 03:23:43 PST
---
The panic backtrace doesn't look obviously related to the radeon driver — all
the symptoms sound like something might be scribbling more or less randomly
over
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #8 from Marko Kohtala marko.koht...@gmail.com 2012-01-16 11:26:00
PST ---
Created attachment 55650
-- https://bugs.freedesktop.org/attachment.cgi?id=55650
dmesg with enable_mtrr_cleanup
Attached the dmesg with The /proc/mtrr is
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #9 from Marko Kohtala marko.koht...@gmail.com 2012-01-16 11:43:20
PST ---
Created attachment 55651
-- https://bugs.freedesktop.org/attachment.cgi?id=55651
Artefacts in X, screencapture
This capture was with the enable_mtrr_cleanup
https://bugs.freedesktop.org/show_bug.cgi?id=44800
Marko Kohtala changed:
What|Removed |Added
Attachment #55600|application/octet-stream|text/plain
mime type|
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #6 from Marko Kohtala 2012-01-15
06:13:16 PST ---
Created attachment 55604
--> https://bugs.freedesktop.org/attachment.cgi?id=55604
X server log, before panic if I remember right
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #4 from Marko Kohtala 2012-01-15
05:58:36 PST ---
Created attachment 55600
--> https://bugs.freedesktop.org/attachment.cgi?id=55600
lspci -vvnn
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
---
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #3 from Marko Kohtala 2012-01-15
05:57:38 PST ---
Created attachment 55599
--> https://bugs.freedesktop.org/attachment.cgi?id=55599
A kernel panic
To test the card, I usually booted with "text" on kernel command line to
prevent
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #2 from Alex Deucher 2012-01-15 05:56:22 PST
---
Please attach your xorg log and dmesg output.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You are
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #1 from Marko Kohtala 2012-01-15
05:55:53 PST ---
Created attachment 55598
--> https://bugs.freedesktop.org/attachment.cgi?id=55598
Artefacts in text console
The artefacts seem to come during scrolling. If scrolling a lot, like
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #5 from Marko Kohtala 2012-01-15
06:00:41 UTC ---
Created attachment 55601
--> https://bugs.freedesktop.org/attachment.cgi?id=55601
dmesg output to text console
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #1 from Marko Kohtala marko.koht...@gmail.com 2012-01-15 05:55:53
PST ---
Created attachment 55598
-- https://bugs.freedesktop.org/attachment.cgi?id=55598
Artefacts in text console
The artefacts seem to come during scrolling. If
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #2 from Alex Deucher ag...@yahoo.com 2012-01-15 05:56:22 PST ---
Please attach your xorg log and dmesg output.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
--- You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #3 from Marko Kohtala marko.koht...@gmail.com 2012-01-15 05:57:38
PST ---
Created attachment 55599
-- https://bugs.freedesktop.org/attachment.cgi?id=55599
A kernel panic
To test the card, I usually booted with text on kernel
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #4 from Marko Kohtala marko.koht...@gmail.com 2012-01-15 05:58:36
PST ---
Created attachment 55600
-- https://bugs.freedesktop.org/attachment.cgi?id=55600
lspci -vvnn
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #5 from Marko Kohtala marko.koht...@gmail.com 2012-01-15 06:00:41
UTC ---
Created attachment 55601
-- https://bugs.freedesktop.org/attachment.cgi?id=55601
dmesg output to text console
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=44800
--- Comment #6 from Marko Kohtala marko.koht...@gmail.com 2012-01-15 06:13:16
PST ---
Created attachment 55604
-- https://bugs.freedesktop.org/attachment.cgi?id=55604
X server log, before panic if I remember right
--
Configure bugmail:
https://bugs.freedesktop.org/show_bug.cgi?id=44800
Marko Kohtala marko.koht...@gmail.com changed:
What|Removed |Added
Attachment #55600|application/octet-stream|text/plain
30 matches
Mail list logo
