@Scott, it seems that if you only have one additional SATA card in your
system then the error is annoying but benign. But, if you have more than
one SATA expansion card then you would have a real problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is
I will add that this new ASM1064 SATA card is a 4-port SATA controller
that does not use any additional JMicron chip as a port multiplier (like
a JBM575). My original JMicron card was only a two port model, so why it
needed a port multiplier is beyond me. Basically, what all this means is
avoid JMi
My workaround for this problem was to eject the JMicron SATA controller
from the chassis and replace it with one that uses an ASM1064 controller
instead.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchp
Output of inxi.
** Attachment added: "inxi.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970074/+attachment/5594979/+files/inxi.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.n
Output of lspci.
** Attachment added: "lspci.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970074/+attachment/5594980/+files/lspci.txt
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1970074
Title:
UBSAN: array-index-out-of-bounds in
/build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
Status in linux package
Maybe we can figure out what's common between our systems since I
imagine if everyone were getting this error then this bug would be
getting more attention.
I'll also note this started for me with 5.15. 5.13 and earlier did not
exhibit this error. System seems to run fine though. No noticeable
deg
Happens on every boot with this kernel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1970074
Title:
UBSAN: array-index-out-of-bounds in
/build/linux-9H675w/linux-5.15.0/drivers/ata/li
Another occurrence:
[4.410322] =
[4.410323] UBSAN: array-index-out-of-bounds in
/build/linux-hwe-5.15-scdIe0/linux-hwe-5.15-5.15.0/drivers/ata/libahci.c:968:41
[4.410326] index 15 is out of range for type 'ahci_em_priv [8]'
[4.410327] CPU: 1
I'll also add that this problem is still present in kernel 5.8 (no
matter if you use "modesetting" or "intel" driver for the Braswell GPU.
My current setup:
System:Kernel: 5.4.0-58-generic x86_64 bits: 64 compiler: gcc v: 9.3.0
Desktop: Cinnamon 4.6.7
wm: muffin dm: LightDM Distr
@tonypanduru
I'd like to share a slightly improved workaround on this for those still
dealing with the issue. The core problem seems to be that the mouse
cursor can go into a negative X position by one pixel when moved to the
far left of the screen. With either the now obsolete intel proprietary
d
I did not apply the patch in #13, but I did try disabling highdma with
ethtool (essentially what the patch makes permanent) and that had no
effect for me (at least not on the kernel I was using at the time). I
did try the patch in #40 and that had no effect for me either. The only
thing I've found
I'll also add that though I had previously tried iommu=soft with no
luck, trying iommu=pt as suggested by chithanh in post 70 does seem to
workaround the issue successfully. I'm not sure as to why that would be
the case as this is neither a VM nor a VM host, but since adding the
parameter to my ker
Problem still exists with kernel 5.3.0-59-generic. Same machine I
reported on previously. Multiple kernel releases since then. Only change
with more recent kernels is that the connection recovers on its own
after a few minutes (as opposed to requiring a reboot). Still, the only
workaround that has
I can confirm that the problem is present with both the intel and the
modesetting driver on Braswell systems. The exact symptoms differ for
each, but in both cases it is triggered when the mouse touches the left
limit of the screen. With modesetting, it seems to "stick" until you
move the mouse awa
@paulo.guedes
Yes, removing and re-adding the modules as you describe does at least
recover eno1 without rebooting. Still, hardly a solution for what was
intended to be a headless Plex server. This happens every time I start
an mpeg2 tv stream through my plex box which is only about a 20mbps
load.
Also, on the last crash, I caught it while it was happening and RX/TX
errors and collisions all went through the roof right before it went
"no-carrier".
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpa
Confirmed that this is still an issue on 18.04.1. I have an HP 705 G1
with the Broadcom 5762. In my case it's a Plex server. Whenever I try to
stream something the interface goes "NO-CARRIER" and the only way to
recover is to reboot. I've tried disabling highdma, tso and gso using
ethtool, iommu=so
18 matches
Mail list logo
