** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1691991
Title:
Xorg Segmentation fault on Hisilicon D05 board (arm64)
To manage
Hi Mao,
Thanks for that.
You are right, this should be split into two kernel issues.
I have opened:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698700 - "pci:" prefix in
bus ID
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1698706 - Quirk for vga
card and bridge
I have
Hi Mao,
I have done more work on the HiSilicon board. I have talked with the SEG
team and our conclusion is that the hardware is not compliant with the
specification, but that it is appropriate to include a workaround in
software.
I have developed a patch that adds a workaround or 'quirk' to the
Hi Mao,
OK, that sounds reasonable. I will follow up on this.
Regards,
Daniel
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1691991
Title:
Xorg Segmentation fault on Hisilicon D05 board
Hi Mao,
I have installed a version of the kernel which ignores the capabilities
of the PCI bridge when determining whether a device can be the boot
device. With this patched kernel, X starts without needing a config
file.
This confirms:
- that the vga card is not marked as boot device because
Hi Mao,
I have successfully verified that with the patched kernel and the Xorg
config, X starts fine.
Do you need assistance getting that patch upstream, or is that something
HiSilicon/the HWE team can do?
Regards,
Daniel
--
You received this bug notification because you are a member of
Hi Dann,
Ignore that, I didn't realise I needed the -extra package.
Regards,
Daniel
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1691991
Title:
Xorg Segmentation fault on Hisilicon D05
Hi Dann,
I have tried to boot the HiSilicon board with a zesty kernel (and with a
patched zesty kernel) and it boots, gets to the following, and then
hangs without displaying a prompt:
[9.900239] async_tx: api initialized (async)
[9.991929] Btrfs loaded, crc32c=crc32c-arm64-hw
[
Hi Mao,
I have looked at the PCI setup a bit more closely: the VGA card is
behind a PCI bridge which does not advertise the PCI_BRIDGE_CTL_VGA
capability, so it is not being picked up by the kernel as the
default/boot card.
Is there anything special about the bridge or the hardware in this
** Changed in: xorg (Ubuntu)
Assignee: (unassigned) => Daniel Axtens (daxtens)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1691991
Title:
Xorg Segmentation fault on Hisilicon D05 bo
Hi,
I can get xorg working if I do these 2 things:
1) Edit memory with gdb to add "pci:" to bus id. This is what the kernel
patch should do. I will test the patch soon, I am just waiting for the
kernel to build.
2) Install this /etc/X11/xorg.conf:
Section "ServerFlags"
Option
Ok, so I think part of the problem is that the kernel hibmc driver needs
to use a set_busid function from the drm core. I've simulated this
change in the debugger, and it seems to at least prevent the crash. (It
doesn't seem to be enough for the server to work, still working on
that.)
Here's a
OK, I have made some progress on this:
The busid reported by libdrm on the arm64 system is "0007:a1:00.0"
The busid reported by libdrm on a amd64 system is "pci::00:02.0"
The "pci:" prefix is missing on arm64. I think this leads to the
segfault on arm64 as X tests for the prefix.
This
Hi Mao,
Yes, remote access would be the fastest way to debug this.
You can contact me by email - daniel.axt...@canonical.com.
Regards,
Daniel
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in Ubuntu.
Hi,
This is what I have figured out so far.
For some reason the initial probing done by the modesetting driver
fails. This is part of the platform device probing stage. This failure
means the device is not claimed by the modesetting driver as a 'regular'
screen. Instead it is claimed by the
15 matches
Mail list logo
