diff for duplicates of <20160530110753.61846b70@pluto.restena.lu> diff --git a/a/1.txt b/N1/1.txt index ffd6c68..e05787e 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -22,16 +22,16 @@ So your patch to allow including ISA devices in vga arbitration would not change anything here. Is it known at what time the lockup happens? -From the kernel trace the lockup only happens during write() and not +>From the kernel trace the lockup only happens during write() and not already at open time. Thus the command written to /dev/vga_arbiter would be helpful for proper understanding. -From kernel side code I think it's a call related to radeon and not +>From kernel side code I think it's a call related to radeon and not intel in Xorg that calls out to vga_arbiter, but please provide more details (either strace&/backtrace on Xorg or kernel with pr_debug active for vgaargb and corresponding kernel log). -From the bug report, comment #11 I don't understand this part: +>From the bug report, comment #11 I don't understand this part: I boot Linux directly via rEFInd. I got the radeon xorg drivers installed, but neither intel nor fbdev or kms. @@ -53,7 +53,7 @@ would be helpful as well. I think here userspace and kernel-side parts are getting mixed-up. -From the failing kernel log, both i915 and radeon are loaded long before +>From the failing kernel log, both i915 and radeon are loaded long before the lock happens (with vgaarb being loaded yet earlier). The only one having trouble is Xorg (would it be possible to get a diff --git a/a/content_digest b/N1/content_digest index b5139fa..a8636d5 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -32,16 +32,16 @@ "not change anything here.\n" "\n" "Is it known at what time the lockup happens?\n" - "From the kernel trace the lockup only happens during write() and not\n" + ">From the kernel trace the lockup only happens during write() and not\n" "already at open time. Thus the command written to /dev/vga_arbiter would\n" "be helpful for proper understanding.\n" - "From kernel side code I think it's a call related to radeon and not\n" + ">From kernel side code I think it's a call related to radeon and not\n" "intel in Xorg that calls out to vga_arbiter, but please provide\n" "more details (either strace&/backtrace on Xorg or kernel with pr_debug\n" "active for vgaargb and corresponding kernel log).\n" "\n" "\n" - "From the bug report, comment #11 I don't understand this part:\n" + ">From the bug report, comment #11 I don't understand this part:\n" " I boot Linux directly via rEFInd. I got the radeon xorg drivers\n" " installed, but neither intel nor fbdev or kms.\n" "\n" @@ -63,7 +63,7 @@ "\n" "I think here userspace and kernel-side parts are getting mixed-up.\n" "\n" - "From the failing kernel log, both i915 and radeon are loaded long before\n" + ">From the failing kernel log, both i915 and radeon are loaded long before\n" "the lock happens (with vgaarb being loaded yet earlier).\n" "\n" "The only one having trouble is Xorg (would it be possible to get a\n" @@ -104,4 +104,4 @@ "\n" Bruno -84656f77dc98c3890c6aefc0d4edb0f42d19741a1abb29302675bf7a19d63e1a +199368063bf084db42d448297086407f79d62dfea223e5692792a347e151dbc4
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.