That was when the USB-power/HDMI/DP adapter was plugged in the other side. The
relevant log entries from lower down are:
```
[622581.193592] usb 3-8: new high-speed USB device number 71 using xhci_hcd
[622581.342507] usb 3-8: device descriptor read/all, error -71
[622581.469590] usb 3-8: new high-
Public bug reported:
I have a MS LifeCam Cinema, which is known to work with Ubuntu in the
past, though forum posts show it no longer working as of ~18.04.
I recently went back to Ubuntu as an actual desktop OS with 20.04 on a
dell xps 13, which has a somewhat average webcam in the lid, so tried
Can confirm the Azure kernel also fixes enhanced sessions when combined
with appropriate windows side metadata shenanigans.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1766857
Tit
Just created a new VM and wondered why enhanced mode logins in hyper-V
weren't working and encountered this.
$ uname -a
Linux cognite-lifeless 5.3.0-45-generic #37-Ubuntu SMP Thu Mar 26 20:41:27 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux
$ lsb_release -a
No LSB modules are available.
Distributor ID
** Description changed:
- Photo of failed machine at https://photos.app.goo.gl/UGofDoh2DdDvNTMM8
+ Photo of failed machine, and video of a second lockup at
+ https://photos.app.goo.gl/9qUxysZ4LN1NRdrA7
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-43-generic 4.1
Public bug reported:
Sorry that this is a little vague, I ran into it and didn't run it down
to ground; this was on the cosmic daily server installer build.
hardware: 4 HDD;s, 1 NVMe SSD.
configuration: 1x 512MB ESP per drive, then for the HDDs the second partition
for an mdraid raid5 set.
la
hint if testing this - add module_blacklist=bcache to your kernel boot
line to boot and reset the metadata :)
--
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/1809748
Title:
8k bcache NULL
Public bug reported:
Photo of failed machine at https://photos.app.goo.gl/UGofDoh2DdDvNTMM8
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-43-generic 4.15.0-43.46
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic x86_64
NonfreeKerne
after doing a wipefs on the cache drive the BUG still occured; wipefs's
the backing drive corrected that. I haven't yet tried wiping just the
backing drive.
** Summary changed:
- 8k bcache cache NULL pointer deref on mount / can't boot
+ 8k bcache NULL pointer deref on mount / can't boot
--
You
cache superblock info - sb.magicok
sb.first_sector 8 [match]
sb.csum 5A3217E583DB5B86 [match]
sb.version 0 [cache device]
dev.label (empty)
dev.uuid2a9e0dfd-acd0-4750-85ae-b347d7580e2b
dev.sectors_per_block 16
dev
Public bug reported:
After creating a bcache cache device with an 8k block size (see
#1662407), a kernel oops happens every time device is probed.
I'm not sure that there is any userspace bug present in #1662407 at all
- it may just be kernel. I've attached a dmesg there, but can't actually
get i
I've reproduced this recently with saucy, without the --max-resize
option, but only resizing to 20-30G from a 2G base, which is well within
the heuristics ext4 has.
** Changed in: linux (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Kerne
Steven's report is with saucy as well.
--
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/1233075
Title:
resizefs failure with raring
Status in “linux” package in Ubuntu:
Incomplete
Bug
We may have found some more data on the situation: bug 1233024 reports
on a failure to resize with the same images..
--
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/1233075
Title:
resizef
Nuts, wrong reference...
We may have found some more data on the situation: bug 1233008 reports
on a failure to resize with the same images..
--
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
huh,
root@undercloud-notcompute-jws3awlsb2kh:/home/heat-admin# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:00 1.8T 0 disk
��sda1 8:1020G 0 part /
interestingly quantal didn't resize, but it didn't lockup either.
Definitely more investigation warranted.
--
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/1233075
Title:
resizefs failure
Public bug reported:
Deploying a raring cloud image with a 2.7G filesystem to 2TB hard disk
crashes in resizefs
[ 143.673885] 0800 880bd4b87f60 880bca8b7d00 8125b
e47
[ 143.673945] Call Tra
http://lists.gnu.org/archive/html/qemu-devel/2013-04/msg02662.html
--
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/1180021
Title:
I/O errors seen on tmpfs
Status in “linux” package in Ub
19 matches
Mail list logo
