https://bugs.freedesktop.org/show_bug.cgi?id=109206
--- Comment #35 from JerryD ---
Well, I just ran Fedora updates which brought kernel to 5.0.7-200.fc29 and
there was also an update to mesa-dri-drivers.x86_64 18.3.6-1.fc29. My laptop
failed to boot with or without the raven_dmcu.bin file after
https://bugs.freedesktop.org/show_bug.cgi?id=110416
Bug ID: 110416
Summary: Newly installed Kubuntu 18.04 brokes after try to
install amdgpu for RX 550
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
https://bugs.freedesktop.org/show_bug.cgi?id=110117
--- Comment #7 from Craig ---
tested the kernel from here today with the same result:
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.1-rc4/
generic amd64
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=110258
--- Comment #6 from Hin-Tak Leung ---
A me-too. Although I have something to add: if I switch to a VT, I can suspend
and resume. However, Xorg after suspend is still f*cked - i.e. I can switch to
a text VT, suspend, resume in the VT and still ha
https://bugs.freedesktop.org/show_bug.cgi?id=110199
Maxim Ivanov changed:
What|Removed |Added
Version|XOrg git|unspecified
--
You are receiving this m
On Sat, Apr 13, 2019 at 08:24:14PM +0200, Noralf Trønnes wrote:
> @@ -844,6 +816,17 @@ static int bcm2835_spi_prepare_message(struct spi_master
> *master,
> struct spi_device *spi = msg->spi;
> struct bcm2835_spi *bs = spi_master_get_devdata(master);
> u32 cs = bcm2835_rd(bs, BCM
/commits/Bartlomiej-Zolnierkiewicz/video-fbdev-gbefb-add-COMPILE_TEST-support/20190413-072821
config: arm-allyesconfig (attached as .config)
compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin
Am 12.04.19 um 18:04 schrieb Thomas Hellstrom:
> Add a pointer to the struct vm_operations_struct in the bo_device, and
> assign that pointer to the default value currently used.
>
> The driver can then optionally modify that pointer and the new value
> can be used for each new vma created.
>
> Cc:
From: Meghana Madhyastha
Remove chunk splitting in tinydrm_spi_transfer in tinydrm-helpers as
spi-bcm2835 now can handle large buffers using DMA, automatic byte
swapping in tinydrm_spi_transfer as it doesn't have users.
Remove the spi_max module argument that now has lost its cause.
The 16kB bu
spi_split_transfers_maxsize() can be used to split a transfer. This
function uses spi_res to lifetime manage the added transfer structures.
So in order to finalize the current message while it contains the split
transfers, spi_res_release() must be called after finalizing.
Signed-off-by: Noralf Tr
From: Meghana Madhyastha
Split spi transfers into chunks of <=65532 to enable the driver to
perform DMA transfer on big buffers. The DLEN register specifies the
number of bytes to transfer in DMA mode. It is 16-bit wide and thus the
maximum DMA transfer is 65535 bytes. Set the maximum to 65532 (4
spi-bcm2835 has a ~64kB upper limit on DMA transfers. Drivers in
drivers/gpu/drm/tinydrm work around this limitation by splitting the
buffer into multiple transfers. This patchset lifts this driver
limitation by splitting affected transfers using
spi_split_transfers_maxsize().
Based on the feedbac
Don't warn about splitting transfers, the info is available in the
statistics if needed.
Signed-off-by: Noralf Trønnes
---
drivers/spi/spi.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
index 9a7def7c3237..05875e63be43 100644
--- a/drivers/spi/spi
https://bugs.freedesktop.org/show_bug.cgi?id=110199
--- Comment #9 from Eduardo Saporski ---
Can confirm. My GPU is MSI RX580 Armor 8G OC and my monitor Asus VP247QG
(FreeSync, 48Hz to 75Hz).
I'm on Solus 4 using the open source drivers (POLARIS10 DRM 3.27.0
5.0.5-113.current LLVM 7.0.0, OpenGL
https://bugs.freedesktop.org/show_bug.cgi?id=109695
a...@tutanota.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #13 from Mauro Gaspari ---
Status update: I updated the BIOS and now disabled all kernel parameters I
previously used. It might take some time to make sure the system is stable.
Regarding your frustrations,
AMD released open source
https://bugs.freedesktop.org/show_bug.cgi?id=110413
--- Comment #9 from Rémi Verschelde ---
Created attachment 143961
--> https://bugs.freedesktop.org/attachment.cgi?id=143961&action=edit
Xorg.1.log after GPU crash in game Northgard with kernel 5.0.7-desktop from
Mageia 7
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=110413
--- Comment #8 from Rémi Verschelde ---
Created attachment 143960
--> https://bugs.freedesktop.org/attachment.cgi?id=143960&action=edit
Xorg.0.log after GPU crash in game Northgard with kernel 5.0.7-desktop from
Mageia 7
This seems to only co
https://bugs.freedesktop.org/show_bug.cgi?id=110413
--- Comment #7 from Rémi Verschelde ---
Created attachment 143959
--> https://bugs.freedesktop.org/attachment.cgi?id=143959&action=edit
journalctl -b output after GPU crash in game Northgard with kernel
5.0.7-desktop from Mageia 7
As can be s
https://bugs.freedesktop.org/show_bug.cgi?id=110413
--- Comment #6 from Rémi Verschelde ---
Created attachment 143958
--> https://bugs.freedesktop.org/attachment.cgi?id=143958&action=edit
dmesg output after GPU crash in game Northgard with kernel 5.0.7-desktop from
Mageia 7
Worth noting: North
https://bugs.freedesktop.org/show_bug.cgi?id=102322
--- Comment #81 from Jaap Buurman ---
(In reply to Alex Deucher from comment #14)
> (In reply to dwagner from comment #13)
> >
> > Much lower shader clocks are used only if I lower the refresh rate of the
> > screen. Is there a reason why the s
https://bugs.freedesktop.org/show_bug.cgi?id=110413
--- Comment #5 from Rémi Verschelde ---
Tried another game (Northgard) today, same issue. I manually enabled the
performance CPU governor, but it didn't prevent the GPU crash which happened
~10 min in game.
I'm attaching the dmesg, journalctl a
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #12 from Jaap Buurman ---
My Vega64 was also 100% stable on the exact same build under Windows 10. So I
am also not getting my hopes up, but I am really frustrated. I am hoping it is
some kind of incompatibility problem. I have hones
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #11 from Mauro Gaspari ---
You are right. MSI tools do not offer any BIOS update for GPU.
I downloaded the utility and filtered BIOS by vendor and DeviceID, I saw the 3
BIOS version and the one that, as you said was released 2 days
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #10 from Jaap Buurman ---
You will have to flash using Atiflash:
https://www.techpowerup.com/download/ati-atiflash/
And downloading the latest bios for your card from Techpowerup as well:
https://www.techpowerup.com/vgabios/
Bios
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #9 from Mauro Gaspari ---
Interesting catch the one about the BIOS of the card.
I have a separate SSD with windows10 I use to test this card stability. I will
check my windows MSI update tool, see if it offers me an updated BIOS. If
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #8 from Jaap Buurman ---
I guess we can rule out a multi-monitor issue then. But I find is VERY
interesting that you also run the exact same bios version, that was replaced
two days later, so it should be fairly rare. Perhaps it is b
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #7 from Mauro Gaspari ---
@ Jaap Buurman
I run a single monitor, ultra-wide 3440xx1440 @100hz.
my bios version: 113-D0500100-103
--
You are receiving this mail because:
You are the assignee for the bug.___
Hi, Ralph,
On Fri, 2019-04-12 at 11:52 -0700, Ralph Campbell wrote:
> On 4/12/19 9:04 AM, Thomas Hellstrom wrote:
> > Add two utilities to a) write-protect and b) clean all ptes
> > pointing into
> > a range of an address space
>
> A period at the end, please.
>
> > The utilities are intended to
Hi, Jérôme
On Fri, 2019-04-12 at 17:07 -0400, Jerome Glisse wrote:
> On Fri, Apr 12, 2019 at 04:04:18PM +, Thomas Hellstrom wrote:
> > This is basically apply_to_page_range with added functionality:
> > Allocating missing parts of the page table becomes optional, which
> > means that the funct
30 matches
Mail list logo
