** Changed in: linux-raspi2 (Ubuntu)
Assignee: Ryan Finnie (fo0bar) => (unassigned)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1652270
Title:
Could not boot into R
With the regression fix tested, I've gone ahead and fixed the core
problem on my system, switching the backing device to 4k. Documented
below and worked for me, but PLEASE don't take it at face value, since
part of it is literally destroying the bcache header area of the backing
disk.
# WARNING!
Works on focal, thank you
--
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/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Status in Linux:
Confirmed
Statu
On 6/2/20 10:19 AM, Mauricio Faria de Oliveira wrote:
> Do you remember specifying a block size of 512 kB for 'make-bcache' when
> creating it?
>
> e.g., make-bcache --bdev|-B /dev/mdN --block|-w 512k # or similarly.
My set was created by hand, and it's entirely possible I specified
"--block 512k
Works on focal!
Linux nibbler 5.4.0-34-generic #38+lp1867916b1 SMP Sun May 31 21:41:06
-03 2020 x86_64 x86_64 x86_64 GNU/Linux
Thanks! I'm curious to see the patch; I tried root causing it myself
and suspected it had to do with something like an overflow in an
unanticipated block size, but never
Sure, done.
--
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/1867916
Title:
Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Status in Linux:
Unknown
Status in linux packa
** Attachment added: "lp1867916-lsblk"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5378817/+files/lp1867916-lsblk
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/
Done, please see attached. (The sd* devices do tend to move around; the
bcache backing device is currently at sdb1.)
--
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/1867916
Title:
Regres
** Attachment added: "lp1867916-bcache-super-show.sd"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5378589/+files/lp1867916-bcache-super-show.sd
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
** Attachment added: "lp1867916-bcache-super-show.md"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5378590/+files/lp1867916-bcache-super-show.md
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubunt
** Attachment added: "lp1867916-queue_block_size"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+attachment/5378588/+files/lp1867916-queue_block_size
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https
Here's a crashdump from the working kernel, with everything enabled:
https://www.finnie.org/stuff/lp1867916-crashdump-20200528.tar.xz
--
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/1867916
The bcache device is raid+bcache, with luks below it (and then lvm), so
it's not directly mountable. Do you just want the stack set up and
functional like normal?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bu
Mike: Sorry, that is not related. I'd suggest filing a new bug.
Mauricio: Any update on this? This also affects the 5.4 line, so after
upgrading to focal I needed to remain on 4.15.0-88.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to l
I've bisected the problem down to commit
c35a4a858d0616e7817026d88f377c7201ad449a ("block: fix an integer
overflow in logical block size", upstream
ad6bf88a6c19a39fb3b0045d78ea880325dfcf15).
I don't know what the exact problem is with the commit, but seems to be
in the area of fs/block_dev.c set_i
BTW, for future searchers, I've uploaded dmesg.202004081903 separately,
and pasted the crash here:
[ 194.36] bcache: bch_journal_replay() journal replay done, 3 keys in 6
entries, seq 23285862
[ 194.444622] bcache: register_cache() registered cache device sdb1
[ 194.448381] bcache: registe
Here you go: https://www.finnie.org/stuff/lp1867916-crashdump.tar.xz
(138MB)
Some notes on the process:
- Also blacklisted it87 (DKMS) so the running kernel wasn't "tainted"
- Also disabled the relevant crypttab entry for this group
- 768M produced "crashkernel reservation failed - No suitable are
I can confirm going from 4.15.0-88 to 4.15.0-91 on my bcache system
panics in the same way. Here's my layout:
-> sd{c,d,f,g,h}: each 4TB gpt, sd{c,d,f,g,h}1: each type linux_raid_member
--> md0: raid6, sd{c,d,f,g,h}1
--> sda: 512GB gpt, sda1: type bcache
---> bcache0: md0 + sda1
> whatadisk_c
The fix was bikeshedded a tiny bit on LKML, but is now accepted upstream
and AIUI will be in linux-next soon:
https://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi.git/commit/?id=0d98ba8d70b0070ac117452ea0b663e26bbf46bf
This change is tested as backwards compatible with Ubuntu 4.15, and
would
Public bug reported:
Discovered on bionic, arm64 (Moonshot, verified on multiple swirlix
cartridges), 4.15.0-22-generic.
After deploying the nova-compute Juju charm, on subsequent reboots,
within a few seconds after complete boot, everything will freeze and
eventually display on the serial consol
A patch has been submitted to linux-pci, and I've confirmed this fix
works: https://lkml.org/lkml/2018/5/22/817
--
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/1771467
Title:
Reboot/shutd
I tracked it down to https://patchwork.kernel.org/patch/10027157/ just
before 4.15-rc1. This appears to affect all DL360/DL380 Gen9 I've
encountered so far. Opened
https://bugzilla.kernel.org/show_bug.cgi?id=199779 and currently working
with Sinan Kaya to disagnose.
** Tags added: kernel-bug-exi
Public bug reported:
Verified on multiple DL360 Gen9 servers with up to date firmware. Just
before reboot or shutdown, there is the following panic:
[ 289.093083] {1}[Hardware Error]: Hardware error from APEI Generic Hardware
Error Source: 1
[ 289.093085] {1}[Hardware Error]: event severity:
I'm not even remotely sure about things here, so some raw notes:
* Current bisect effort ("oh man, this will take forever"):
# bad: [69973b830859bc6529a7a0468ba0d80ee5117826] Linux 4.9
# good: [c8d2bc9bc39ebea8437fd974fdbc21847bb897a3] Linux 4.8
git bisect start 'v4.9' 'v4.8'
# good: [a5af7e1fc69
4.8.0 works, 4.9.0 panics. I'll see about bisecting.
--
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/1761626
Title:
[regression] bionic 4.15.0-13-generic panics on qemu ppc64el
Status i
I can test earlier mainlines, but keep in mind that ppc64el is very slow
on my home qemu setup (note "only" "very slow"; ppc64 is "amazingly
slow", presumably due to endian swapping). Does Kernel have a POWER8
playground machine, if it comes to bisect compiling?
--
You received this bug notifica
Same result with 4.16.0-041600-generic and 4.13.0-38-generic
--
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/1761626
Title:
[regression] bionic 4.15.0-13-generic panics on qemu ppc64el
S
Public bug reported:
When upgrading to bionic on a qemu ppc64el instance, the 4.15.0 kernel
panics before initrd. Going back to xenial 4.4.0 works correctly.
linux-image-4.15.0-13-generic:
Installed: 4.15.0-13.14
Candidate: 4.15.0-13.14
Version table:
*** 4.15.0-13.14 500
500 http
** Attachment added: "Kernel boot log for 4.15.0-13-generic"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+attachment/5103357/+files/1761626-4.15.0-13-generic.boot.log
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to lin
** Attachment added: "libvirt XML file for instance"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1761626/+attachment/5103368/+files/1761626-libvirt.xml
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://b
This is one of the major contributing factors to LP: #1437913.
I have rebased 2013.02.13-1ubuntu1 on top of Debian 2014.11.18-1, please
see:
https://launchpad.net/~fo0bar/+archive/ubuntu/ppa/+build/7325504
Could I get a sponsor upload? Thank you.
--
You received this bug notification because
The problem is still being diagnosed on kernel bugzilla, but for the
moment, "iw reg set US" seems to be a workaround.
--
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/1437913
Title:
Wifi
** Bug watch added: Linux Kernel Bug Tracker #95901
http://bugzilla.kernel.org/show_bug.cgi?id=95901
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=95901
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of K
http://marc.info/?l=linux-wireless&m=142778129512570&w=2
--
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/1437913
Title:
Wifi unstable on vivid with Intel 7265 (Thinkpad X250)
Status in l
ASUS RT-AC87R (retail version of the RT-AC87U, same hardware), firmware
3.0.0.4.378_4608-g7e6c1e5 (latest), in WAP-only mode.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribe
No change with 4.0.0-04rc6.201503291935.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
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/1437913
Title:
Wifi unst
BIOS updated to 1.07, no change in behavior.
N10ET30W (1.07 )
03/05/2015
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bu
Public bug reported:
After upgrading from utopic to vivid beta, wifi on the Intel 7265 on my
Thinkpad X250 has become unstable (linux-image 3.19.0-10.10, linux-
firmware 1.143). I'm seeing two primary problems:
* On 5GHz 802.11ac, I'll get DEAUTH_LEAVING almost exactly every minute,
followed b
Tested linux-
image-3.16.0-031600rc7-generic_3.16.0-031600rc7.201407271635_amd64.deb
for a week, was not able to replicate.
** Tags added: kernel-fixed-upstream-3.16-rc7
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a
Public bug reported:
e1000e device on a trusty router/server/etc, up for a few weeks, stopped
responding and went into a "Detected Hardware Unit Hang" loop. At the
time, the interface was under moderate load, about 60mbps inbound.
[1871400.121801] e1000e :00:19.0 eth1: Detected Hardware Unit
I can confirm that 29c7787075c92ca8af353acd5301481e6f37082f applies
cleanly again the latest trusty tree (3.13.0-27.50), and does indeed fix
the vsftpd problem without apparent side effects.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
linux-image-3.13.0-24-generic_3.13.0-24.46~hvcdcc_armhf.deb verified as
working, both directly and via u-boot, thank you.
And thanks for including the DTB in the package now. I was using
vexpress-v2p-ca9.dtb, but IIRC I compiled it from vanilla sometime last
year.
--
You received this bug notif
FWIW, I was not able to compile the armhf package from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-trusty/:
CC [M] drivers/gpu/drm/msm/msm_drv.o
CC [M] drivers/gpu/drm/msm/msm_fb.o
CC [M] drivers/gpu/drm/msm/msm_gem.o
CC [M] drivers/gpu/drm/msm/msm_gem_prime.o
CC [M] drivers
The only option on https://wiki.ubuntu.com/DebuggingKernelBoot of
relevance to booting an ARM kernel in QEMU is the "debug" flag, which
doesn't change anything. The u-boot output is in the original report;
when booting through u-boot, it CPU spins after "Starting kernel ...".
When booting the kern
Looks like the lp helper script got confused; logs were already attached
from apport-bug. Overriding.
BTW, I removed u-boot from the situation and tried booting
3.13.0-23-generic directly from qemu-system-arm, same result. I have
not yet been able to get 3.13.0-23-generic to boot.
** Summary ch
Public bug reported:
Upon d-r-u of a qemu ARM guest from saucy to trusty, the kernel no
longer boots:
===
U-Boot 2013.10 (Nov 23 2013 - 04:30:10)
DRAM: 1 GiB
WARNING: Caches not enabled
Flash: 256 MiB
MMC: MMC: 0
In:serial
Out: serial
Err: serial
Net: smc911x-0
Hit any key to stop a
46 matches
Mail list logo
