Public bug reported:
I have reproduced this multiple times on both Ubuntu 19.10 (5.3.0-16)
and Ubuntu 20.04 beta (5.4.0-24)
sudo duperemove --lookup-extents=yes -d -r --hashfile /mnt/storage/hashes
[...]
0x556dfa962980] Dedupe 2 extents (id: b285a8ff) with target: (0, 2255716352),
"/mnt/storage/
** Attachment added: "one of the early errors reported by duperemove"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873555/+attachment/5356421/+files/dedupe-error
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Reported upstream: (didn't show up on linux-xfs mailing list yet)
https://lore.kernel.org/lkml/f6c749739dc135ebd7a9321195a616b15c772082.ca...@etorok.net/#r
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launc
Feb 4 15:22:03 mama-tata-laptop kernel: [1.81]
[drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO
underrun
Feb 4 15:22:03 mama-tata-laptop kernel: [1.822564] [drm] RC6 disabled,
disabling runtime PM support
Feb 4 15:22:03 mama-tata-laptop kernel: [1.82260
I tried to file a bug, but launchpad keeps timing out (see
https://bugs.launchpad.net/ubuntu/+bug/1814585).
I think I have the same problem on Ubuntu 18.10.
4.18.0-13 was fine, 4.18.0-14 always crashes with BUG on boot.
--
You received this bug notification because you are a member of Kernel
Pac
>From older, working kernels. Note that the FIFO underrun error is
present in these successful boots too (I've been seeing it for years),
but it never crashes before on that.
** Attachment added: "good kern.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1813657/+attachment/5235956/+
If you still have the 4.18.0-13-generic kernel try booting that, it
helped me get a working screen again.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1813509
Title:
[i915] NULL
I confirm that 4.18.0-15.16 has fixed the problem for me too on a Lenovo
X300, thanks.
--
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/1814555
Title:
Ubuntu boot failure. 4.18.0-14 boot s
Hi,
I've been running Ubuntu 18.04 for a while now on this machine, so I do not
know whether 16.04 would work, it certainly didn't work at all when I filed
this bugreport.
I would suggest that if anyone else runs into this issue they should upgrade to
18.04 or 18.10.
--
You received this bug
Unfortunately I am not able to reproduce this anymore.
On the day I reported the bug I was able to reproduce it multiple times, next
day I tried the mainline kernel, it worked, installed back the old kernel and
again it worked. That was the only package that changed.
Tried a few more times to rep
Public bug reported:
This is a regression from Ubuntu 16.10. I have upgraded this Lenovo X300
yesterday, and noticed this bug:
Steps to reproduce:
* turn laptop off completely, unplug power
* plug in power
* turn on laptop, and boot Xubuntu 17.04
* Login
Expected results:
* Connected to int
** Attachment added: "dmesg IOMMU=soft"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1696240/+attachment/4890325/+files/log
--
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/169624
Public bug reported:
Using 4.10.0-22-generic from Ubuntu and running any of the Unigine benchmarks
(Heaven-4.0, Valley-1.0, Superposition-1.0) causes the screen to go black and
the graphics system to crash.
The graphics card's fan stops working and sensors reports 511C, clearly wrong.
I can sti
Ubuntu 4.10.0-22-generic: crash
mainline 4.10.17: crash
mainline 4.11.3: OK
** Tags added: kernel-bug-exists-upstream
** Changed in: linux (Ubuntu Zesty)
Status: Incomplete => Confirmed
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notific
*** This bug is a duplicate of bug 1674838 ***
https://bugs.launchpad.net/bugs/1674838
Public bug reported:
Installed Ubuntu 17.04 beta, was logged in to Mate, had Chromium, Thunderbird,
and a terminal with Vim running.
I was switching back and forth between Vim and the browser when the whol
*** This bug is a duplicate of bug 1674838 ***
https://bugs.launchpad.net/bugs/1674838
Possible related to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1674838 and
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1677611
** This bug has been marked a duplicate of bug 1674838
k
Apparently 4.8.0-34-generic detects my Latitude E7470 touchpad/stick as
ALPS instead of BYD (4.8.0-32-generic detects as BYD). I don't know
which would be the correct one, but by default ALPS is way too sensitive
and I have to apply those xprops changes before it is usable again
(basically I can't
17 matches
Mail list logo