[Kernel-packages] [Bug 1614953] Re: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40
Getting it all the time: [Apr13 04:28] kino6_0: hw csum failure [ +0.003777] CPU: 18 PID: 0 Comm: swapper/18 Tainted: P OE 4.15.0-58-generic #64-Ubuntu [ +0.03] Hardware name: GIGABYTE G291-281-00/MG51-G21-00, BIOS R06 11/19/2019 [ +0.01] Call Trace: [ +0.03] [ +0.10] dump_stack+0x63/0x8b [ +0.08] netdev_rx_csum_fault+0x38/0x40 [ +0.03] __skb_checksum_complete+0xbc/0xd0 [ +0.05] nf_ip_checksum+0xc3/0xf0 [ +0.17] tcp_error+0x162/0x1c0 [nf_conntrack] [ +0.07] ? kfree_skbmem+0x5f/0x70 [ +0.04] ? consume_skb+0x34/0x90 [ +0.11] nf_conntrack_in+0x14f/0x500 [nf_conntrack] [ +0.09] ? csum_partial_ext+0x9/0x10 [ +0.04] ? __skb_checksum+0x6b/0x300 [ +0.06] ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4] [ +0.05] nf_hook_slow+0x48/0xc0 [ +0.04] ? skb_send_sock+0x50/0x50 [ +0.05] ip_rcv+0x2fa/0x360 [ +0.03] ? inet_del_offload+0x40/0x40 [ +0.04] __netif_receive_skb_core+0x432/0xb40 [ +0.04] ? tcp4_gro_receive+0x137/0x1a0 [ +0.03] __netif_receive_skb+0x18/0x60 [ +0.03] ? __netif_receive_skb+0x18/0x60 [ +0.04] netif_receive_skb_internal+0x45/0xe0 [ +0.03] napi_gro_receive+0xc5/0xf0 [ +0.34] mlx5e_handle_rx_cqe_mpwrq+0x465/0x860 [mlx5_core] [ +0.29] mlx5e_poll_rx_cq+0xd1/0x8b0 [mlx5_core] [ +0.25] mlx5e_napi_poll+0x9d/0x290 [mlx5_core] [ +0.04] net_rx_action+0x140/0x3a0 [ +0.06] __do_softirq+0xe4/0x2d4 [ +0.06] irq_exit+0xc5/0xd0 [ +0.04] do_IRQ+0x8a/0xe0 [ +0.03] common_interrupt+0x8c/0x8c [ +0.02] [ +0.05] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0 [ +0.05] RSP: 0018:a278002b3e68 EFLAGS: 0246 ORIG_RAX: ffdd [ +0.04] RAX: 970ebeea2840 RBX: 0008672cdbad1064 RCX: 001f [ +0.02] RDX: 0008672cdbad1064 RSI: f3a434de6285 RDI: [ +0.02] RBP: a278002b3ea8 R08: 0004 R09: 00022080 [ +0.02] R10: a278002b3e38 R11: 00137021632d21b0 R12: c277ff683298 [ +0.01] R13: 0003 R14: aa172e78 R15: [ +0.05] ? cpuidle_enter_state+0x97/0x2f0 [ +0.03] cpuidle_enter+0x17/0x20 [ +0.05] call_cpuidle+0x23/0x40 [ +0.04] do_idle+0x18c/0x1f0 [ +0.05] cpu_startup_entry+0x73/0x80 [ +0.04] start_secondary+0x1ab/0x200 [ +0.05] secondary_startup_64+0xa5/0xb0 -- 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/1614953 Title: hw csum failure when IPv6 interfaces configured in netdev_rx_csum_fault+0x38/0x40 Status in linux package in Ubuntu: Expired Status in linux source package in Xenial: Expired Status in linux source package in Yakkety: Expired Bug description: Since I started using IPv6 I noticed the following kernel error: Thu Aug 18 15:05:01 2016] : hw csum failure [Thu Aug 18 15:05:01 2016] CPU: 5 PID: 11086 Comm: Chrome_IOThread Tainted: P OE 4.4.0-34-generic #53-Ubuntu [Thu Aug 18 15:05:01 2016] Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./Z77-D3H, BIOS F22 11/14/2013 [Thu Aug 18 15:05:01 2016] 0286 c05989f2 8807573dfcd0 813f11b3 [Thu Aug 18 15:05:01 2016] 0008 8807573dfce8 8171f6e8 [Thu Aug 18 15:05:01 2016] 0074 8807573dfd30 8171639b fe091360 [Thu Aug 18 15:05:01 2016] Call Trace: [Thu Aug 18 15:05:01 2016] [] dump_stack+0x63/0x90 [Thu Aug 18 15:05:01 2016] [] netdev_rx_csum_fault+0x38/0x40 [Thu Aug 18 15:05:01 2016] [] skb_copy_and_csum_datagram_msg+0xeb/0x100 [Thu Aug 18 15:05:01 2016] [] udpv6_recvmsg+0x233/0x670 [Thu Aug 18 15:05:01 2016] [] inet_recvmsg+0x7e/0xb0 [Thu Aug 18 15:05:01 2016] [] sock_recvmsg+0x3b/0x50 [Thu Aug 18 15:05:01 2016] [] SYSC_recvfrom+0xe1/0x160 [Thu Aug 18 15:05:01 2016] [] ? wake_up_q+0x70/0x70 [Thu Aug 18 15:05:01 2016] [] SyS_recvfrom+0xe/0x10 [Thu Aug 18 15:05:01 2016] [] entry_SYSCALL_64_fastpath+0x16/0x71 It repeats periodically: $ dmesg -T | grep 'hw csum failure' | wc -l 201 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-34-generic 4.4.0-34.53 ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Aug 19 13:47:54 2016 HibernationDevice: RESUME=UUID=066c8903-7f5e-43d5-b48f-76d33c4558f2 InstallationDate: Installed on 2016-04-24 (116 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. ProcFB: 0 EFI VGA ProcKernelCmdLine: BO
[Kernel-packages] [Bug 1840854] Re: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs
Hi Jeff, hmm, didn't get notified by launchpad about your answer :(((. Anyway, tried another machine with 4.15.0-91-generic and indeed, it seems to be fixed. Now the problem is, that our GPU machines are running 4.15.0-58-generic and cannot be upgraded because all the nvidia stuff is very picky and we do not have the time to upgrade the cluster to a new kernel version. Therefore the question: is this just a driver problem? Copying over the kmod from a 4.15.0-91 isn't probably a problem, I guess. Or rebuilding the kmod for 4.15.0-58 may work out of the box 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/1840854 Title: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1840854 [Impact] On machines equipped with Mellanox NIC's, in this particular case, Mellanox 5 series NICs using the mlx5_core driver, after installing 4.15.0-56 or later there is the following kernel splat: bond0: hw csum failure CPU: 63 PID: 2473 Comm: in:imklog Tainted: P OE 4.15.0-58-generic #64~16.04.1-Ubuntu Call Trace: dump_stack+0x63/0x8b netdev_rx_csum_fault+0x38/0x40 __skb_checksum_complete+0xc0/0xd0 nf_ip_checksum+0xca/0xf0 tcp_error+0xe0/0x1a0 [nf_conntrack] ? tcp_v4_rcv+0x7c6/0xa70 nf_conntrack_in+0xde/0x520 [nf_conntrack] ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4] nf_hook_slow+0x48/0xd0 ? skb_send_sock+0x50/0x50 ip_rcv+0x30f/0x370 ? inet_del_offload+0x40/0x40 __netif_receive_skb_core+0x879/0xba0 ? tcp4_gro_receive+0x117/0x1b0 __netif_receive_skb+0x18/0x60 ? __netif_receive_skb+0x18/0x60 netif_receive_skb_internal+0x45/0xf0 napi_gro_receive+0xd0/0xf0 mlx5e_handle_rx_cqe_mpwrq+0x4a1/0x8a0 [mlx5_core] mlx5e_poll_rx_cq+0xc3/0x880 [mlx5_core] mlx5e_napi_poll+0x9b/0x280 [mlx5_core] net_rx_action+0x265/0x3b0 __do_softirq+0xf5/0x2a8 irq_exit+0xca/0xd0 do_IRQ+0x57/0xe0 common_interrupt+0x8c/0x8c In 4.15.0-56, a commit was added from upstream -stable that introduced an optimisation for checksumming packets which have had zero bytes padded to the end of the packet. commit 88078d98d1bb085d72af8437707279e203524fa5 Author: Eric Dumazet Date: Wed Apr 18 11:43:15 2018 -0700 subject: net: pskb_trim_rcsum() and CHECKSUM_COMPLETE are friends You can read it here: https://github.com/torvalds/linux/commit/88078d98d1bb085d72af8437707279e203524fa5 It was discussed in this bugzilla link: https://bugzilla.kernel.org/show_bug.cgi?id=201849 This commit causes problems with a number of NIC devices, including Mellanox. This is best described by the maintainer, Dimitris Michailidis: > > > MLNX devices have an issue with packets that are padded past the end of > > > the L3 payload with bytes that aren't all 0s. They use a mode of checksum > > > reporting which should be including the padding bytes but MLNX devices > > > leave those out. When the padding bytes aren't all 0 this omission causes > > > a checksum error. This device behavior has existed for a long time but it > > > has begun causing errors only this year. Before a padded packet had its > HW > > > checksum ignored so it wasn't material what HW had reported. More > recently > > > padded packet checksums started using the HW value and now it is > > > noticeable when that value isn't right. Now, some routers stick additional information in the zero padding section on occasion, which will change the hardware checksum. Since the hardware checksum was ignored until 4.15.0-56 with 88078d98d1bb085d72af8437707279e203524fa5, this wasn't an issue. But with the optimisation, we start running into trouble since the hardware checksums no longer match what the kernel is expecting. [Fix] This was fixed for Mellanox 4 and 5 series drivers recently. Mellanox 4: 74abc07dee613086f9c0ded9e263ddc959a6de04 https://github.com/torvalds/linux/commit/74abc07dee613086f9c0ded9e263ddc959a6de04 Mellanox 5: e8c8b53ccaff568fef4c13a6ccaf08bf241aa01a https://github.com/torvalds/linux/commit/e8c8b53ccaff568fef4c13a6ccaf08bf241aa01a This customer hit the issue with mlx5_core driver, so the fix is: commit e8c8b53ccaff568fef4c13a6ccaf08bf241aa01a Author: Cong Wang Date: Mon Dec 3 22:14:04 2018 -0800 subject: net/mlx5e: Force CHECKSUM_UNNECESSARY for short ethernet frames This is actually present in 4.15.0-59, which is currently sitting in -proposed. The commits are a part of 4.9.156, 4.14.99, 4.19.21 upstream -stable releases, and have been pulled into bionic as a part of LP #1837664 [Testcase] Simply try and bring an interface up on a machine with Mellanox series 5 NICs. When a packet comes through which is smaller th
[Kernel-packages] [Bug 1743529] Re: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered.
kdump package is crap, because it is using a different image (initrd) than update-initramfs creates, so /boot/initrd.img-* != /var/lib/kdump/initrd.img-* . Yes, they may have the same name, but not the same content. What a hugh bullshit! So no wonder, why one has to waste several hours to find out, why /etc/systemd/network/* get not honored. Crap, crap, crap! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kexec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1743529 Title: Merge kexec-tools 2.0.16-1 from Debian: System hung with Kernel panic -not syncing: Out of memory message when crash is triggered. Status in The Ubuntu-power-systems project: Fix Released Status in kexec-tools package in Ubuntu: Fix Released Status in kexec-tools source package in Xenial: Fix Released Status in kexec-tools source package in Artful: Fix Released Status in kexec-tools source package in Bionic: Fix Released Bug description: [Impact] Latest kexec-tools is needed to load/kexec recent kernels. For older releases, like xenial, it's needed to support linux-hwe kernels. [Regression Potential] It might fail to load the GA kernels, like a 4.4 kernel on xenial. [Test case] Different kernels on different architectures have been tested. == Comment: #0 - INDIRA P. JOGA Problem Description: === System hung with kernel panic Kernel panic - not syncing: Out of memory message when crash is triggered Steps to re-create: == > Installed ubuntu1804 daily build on Witherspoon test system root@whip:~# uname -a Linux whip 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux root@whip:~# uname -r 4.13.0-17-generic > root@whip:~# free -h totalusedfree shared buff/cache available Mem: 507G2.0G504G 19M728M 503G Swap: 2.0G 0B2.0G > Edited the grub /etc/default/grub.d/kexec-tools.cfg file and set the crash kernel parameter=4096M > Updated grub using update-grub command and reboot system. cat root@whip:~# cat /proc/cmdline root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet crashkernel=4096M > kdump status before triggering crash root@whip:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.13.0-17-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-4.13.0-17-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="root=UUID=46c6aa02-8215-44cc-b3fc-0bc79c3c8815 ro splash quiet irqpoll noirqdistrib nr_cpus=1 nousb systemd.unit=kdump-tools.service ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@whip:~# kdump-config status current state : ready to kdump > Enabled sysrq root@whip:~# sysctl -w kernel.sysrq=1 kernel.sysrq = 1 > Triggered crash and it hangs with kernel panic- OOM message as below root@whip:~# echo c > /proc/sysrq-trigger [ 85.731415] sysrq: SysRq : Trigger a crash [ 85.731472] Unable to handle kernel paging request for data at address 0x [ 85.731584] Faulting instruction address: 0xc078f588 [ 85.731670] Oops: Kernel access of bad area, sig: 11 [#1] [ 85.731744] SMP NR_CPUS=2048 [ 85.731745] NUMA [ 85.731790] PowerNV [ 85.731853] Modules linked in: rpcsec_gss_krb5 nfsv4 nfs fscache sctp_diag sctp dccp_diag dccp tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag binfmt_misc vmx_crypto crct10dif_vpmsum ofpart cmdlinepart idt_89hpesx powernv_flash ipmi_powernv opal_prd ibmpowernv mtd ipmi_devintf ipmi_msghandler at24 uio_pdrv_genirq uio dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua nfsd auth_rpcgss sch_fq_codel nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs xor raid6_pq nouveau bnx2x ast i2c_algo_bit ttm drm_kms_helper mdio libcrc32c crc32c_vpmsum mlx5_core syscopyarea sysfillrect sysimgblt fb_sys_fops tg3 drm ahci mlxfw libahci nvme devlink nvme_core [ 85.732704] CPU: 10 PID: 4316 Comm: bash Not tainted 4.13.0-17-generic #20-Ubuntu [ 85.732764] task: c03fcb141700 task.stack: c03fc2374000 [ 85.732858] NIP: c078f588 LR: c07904b8 CTR: c078f560 [ 85.732977] REGS: c03fc23779f0 TRAP: 0300 Not tainted (4.13.0-17-generic) [ 85.733066] MSR: 90009033 [ 85.733075] CR: 2842 XER: 2004 [ 85.733201] CFAR: c07904b4 DAR: DSISR: 4200 SOFTE: 1 [ 85.733201] GPR00: c07904b8 c03fc2377c70 c15f6000 0063 [ 85.733201] GPR04: c03feedfade8 c0
[Kernel-packages] [Bug 1800861] [NEW] DBI.pm is buggy and out of date
Public bug reported:
/usr/lib/x86_64-linux-gnu/perl5/5.22/DBI.pm (xenial with latest updates) is
buggy.
To test, simply run:
---schnipp---
#!/usr/bin/perl
require DBI;
my $dbfile = "/tmp/notifications_sqlite.dat";
my $dbh = DBI->connect("dbi:SQLite:dbname=$dbfile",'','');
my $qu_attr = "SELECT * FROM notifications_attr WHERE keyref = '21';";
my $notifhr = $dbh->selectall_arrayref($qu, { Slice => {} });
---schnapp---
It seems, that this bug got already fixed upstream ~ 2 years ago with
DBI version 1.635 (however, most recent version is 1.542).
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
--
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/1800861
Title:
DBI.pm is buggy and out of date
Status in linux package in Ubuntu:
Incomplete
Bug description:
/usr/lib/x86_64-linux-gnu/perl5/5.22/DBI.pm (xenial with latest updates) is
buggy.
To test, simply run:
---schnipp---
#!/usr/bin/perl
require DBI;
my $dbfile = "/tmp/notifications_sqlite.dat";
my $dbh = DBI->connect("dbi:SQLite:dbname=$dbfile",'','');
my $qu_attr = "SELECT * FROM notifications_attr WHERE keyref = '21';";
my $notifhr = $dbh->selectall_arrayref($qu, { Slice => {} });
---schnapp---
It seems, that this bug got already fixed upstream ~ 2 years ago with
DBI version 1.635 (however, most recent version is 1.542).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1800861/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800861] Re: DBI.pm is buggy and out of date
** Package changed: linux (Ubuntu) => libdbi-perl (Ubuntu)
** Changed in: libdbi-perl (Ubuntu)
Status: Incomplete => In Progress
--
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/1800861
Title:
DBI.pm is buggy and out of date
Status in libdbi-perl package in Ubuntu:
In Progress
Bug description:
/usr/lib/x86_64-linux-gnu/perl5/5.22/DBI.pm (xenial with latest updates) is
buggy.
To test, simply run:
---schnipp---
#!/usr/bin/perl
require DBI;
my $dbfile = "/tmp/notifications_sqlite.dat";
my $dbh = DBI->connect("dbi:SQLite:dbname=$dbfile",'','');
my $qu_attr = "SELECT * FROM notifications_attr WHERE keyref = '21';";
my $notifhr = $dbh->selectall_arrayref($qu, { Slice => {} });
---schnapp---
It seems, that this bug got already fixed upstream ~ 2 years ago with
DBI version 1.635 (however, most recent version is 1.542).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdbi-perl/+bug/1800861/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1527727] Re: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/...
Just encountered the same problem with xenial: grub-probe: error: failed to get canonical path of `/dev/HDD0p2' See also http://savannah.gnu.org/bugs/?50896 IMHO "zpool status -P $pool" should be used, everything else is a kludge, which will fail sooner or later. ** Bug watch added: GNU Savannah Bug Tracker #50896 http://savannah.gnu.org/bugs/?50896 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1527727 Title: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/... Status in grub: Unknown Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in grub2 source package in Xenial: In Progress Status in grub2-signed source package in Xenial: In Progress Status in zfs-linux source package in Xenial: Confirmed Bug description: [Impact] Installs over ZFS where a ZFS disk is expected to be used as a root device. [Test case] - Run update-grub on a system with a ZFS root filesystem. [Regression Potential] Installs relying on the current broken behavior to avoid listing other operating systems in grub menu may find that new entries are added. --- update-grub runs /usr/sbin/grub-probe Without libzfslinux support compiled in, /usr/sbin/grub-probe runs ["zpool", "status", poolname] to find out ZFS info. zpool responds with device names as used at (I think!) pool creation time. Often, this is /dev/disk/by-id/... names, without the path. grub-probe then parses the output, and takes the names of devices, and if they do not start with a "/", it prepends "/dev/". It then tests the existence of the path name of the device. it fails. grub-probe then returns something like /usr/sbin/grub-probe: error: failed to get canonical path of `/dev /ata-ST31000333AS_-part1'. The actual path is of course /dev/disk/by- id/ST31000333AS_-part1 It can prepend smarter than "/dev" or it can understand ZFS natively, to fix the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1527727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1527727] Re: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/...
Done - see 1687664. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1527727 Title: grub-probe for zfs assumes all devices prefix with /dev, ignoring /dev/disk/... Status in grub: Unknown Status in grub2 package in Ubuntu: Fix Released Status in grub2-signed package in Ubuntu: Fix Released Status in zfs-linux package in Ubuntu: Fix Released Status in grub2 source package in Xenial: In Progress Status in grub2-signed source package in Xenial: In Progress Status in zfs-linux source package in Xenial: Confirmed Bug description: [Impact] Installs over ZFS where a ZFS disk is expected to be used as a root device. [Test case] - Run update-grub on a system with a ZFS root filesystem. [Regression Potential] Installs relying on the current broken behavior to avoid listing other operating systems in grub menu may find that new entries are added. --- update-grub runs /usr/sbin/grub-probe Without libzfslinux support compiled in, /usr/sbin/grub-probe runs ["zpool", "status", poolname] to find out ZFS info. zpool responds with device names as used at (I think!) pool creation time. Often, this is /dev/disk/by-id/... names, without the path. grub-probe then parses the output, and takes the names of devices, and if they do not start with a "/", it prepends "/dev/". It then tests the existence of the path name of the device. it fails. grub-probe then returns something like /usr/sbin/grub-probe: error: failed to get canonical path of `/dev /ata-ST31000333AS_-part1'. The actual path is of course /dev/disk/by- id/ST31000333AS_-part1 It can prepend smarter than "/dev" or it can understand ZFS natively, to fix the problem. To manage notifications about this bug go to: https://bugs.launchpad.net/grub/+bug/1527727/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688162] [NEW] dmidecode should print diagnostic messages to stderr
Public bug reported: Ubuntu version of dmidecode breaks several scripts because it prints diagnostics messages to stdout instead of stderr. E.g.: sudo /bin/ksh93 # /usr/sbin/dmidecode -s baseboard-manufacturer 2>/dev/null Supermicro Invalid entry length (16). Fixed up to 11. The original version (https://git.savannah.nongnu.org/git/dmidecode.git) however, works as expected: # /tmp/dmidecode -s baseboard-manufacturer 2>/dev/null Supermicro $ /usr/bin/lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial ** Affects: dmidecode (Ubuntu) Importance: Undecided Status: New ** Tags: dmidecode ** Package changed: qemu (Ubuntu) => dmidecode (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dmidecode in Ubuntu. https://bugs.launchpad.net/bugs/1688162 Title: dmidecode should print diagnostic messages to stderr Status in dmidecode package in Ubuntu: New Bug description: Ubuntu version of dmidecode breaks several scripts because it prints diagnostics messages to stdout instead of stderr. E.g.: sudo /bin/ksh93 # /usr/sbin/dmidecode -s baseboard-manufacturer 2>/dev/null Supermicro Invalid entry length (16). Fixed up to 11. The original version (https://git.savannah.nongnu.org/git/dmidecode.git) however, works as expected: # /tmp/dmidecode -s baseboard-manufacturer 2>/dev/null Supermicro $ /usr/bin/lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1688162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688162] Re: dmidecode should print diagnostic messages to stderr
Hi Christian, Yepp, the patch looks good. Would be nice to get this integrated (or to sync dmidecode with the current GNU version). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dmidecode in Ubuntu. https://bugs.launchpad.net/bugs/1688162 Title: dmidecode should print diagnostic messages to stderr Status in dmidecode package in Ubuntu: Triaged Bug description: Ubuntu version of dmidecode breaks several scripts because it prints diagnostics messages to stdout instead of stderr. E.g.: sudo /bin/ksh93 # /usr/sbin/dmidecode -s baseboard-manufacturer 2>/dev/null Supermicro Invalid entry length (16). Fixed up to 11. The original version (https://git.savannah.nongnu.org/git/dmidecode.git) however, works as expected: # /tmp/dmidecode -s baseboard-manufacturer 2>/dev/null Supermicro $ /usr/bin/lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.2 LTS Release: 16.04 Codename: xenial To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1688162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688424] [NEW] grub-mkrelpath returns invalid zfs dataset -> initramfs: mount /root fails
Public bug reported:
If zfs is used for boot, boot will fail because of bogus information returned by
/usr/bin/grub-mkrelpath. E.g. if the zfs dataset for / is rpool/ROOT/linux:
# /usr/bin/grub-mkrelpath /
/ROOT/linux@
This leads to a bogus /boot/grub/grub.cfg because /etc/grub.d/10_linux
generates a boot entry like this:
linux /ROOT/linux@/boot/vmlinuz-4.4.0-77-generic root=ZFS=/ROOT/linux ro
crashkernel=384M-2G:64M,2G-:128M bootdegraded=true debug=y console=ttyS1,115200
crashkernel=384M-:128M
This in turn causes that initramfs to fail on boot:
...
+ wait_for_udev
+ command -v udevadm
+ udevadm settle
+ modprobe zfs zfs_autoimport_disable=1
+ ZFS_BOOTFS=/ROOT/linux
+ echo /ROOT/linux
+ sed -e s,/.*,,
+ ZFS_RPOOL=
+ delay=0
+ [ 0 -gt 0 ]
+ unset delay
+ zpool import -N
[ 10.922149] SPL: The /etc/hostid file is not found.
[ 10.927031] SPL: using hostid 0x
+ ZFS_STDERR=cannot import '': no such pool available
+ ZFS_ERROR=1
+ [ 1 -ne 0 ]
+ panic Command: zpool import -N
Message: cannot import '': no such pool available
Error: 1
Manually import the root pool at the command prompt and then exit.
Hint: Try: zpool import -f -R / -N
Wrong hint BTW, but at least a hint: "zpool import; zpool import
${poolID}|rpool" fixes it.
Anyway, when continuing after an 'exit' it fails with:
...
+ zpool status -L
+ [ n != y ]
+ log_begin_msg Setting mountpoint=/ on ZFS filesystem /ROOT/linux
+ _log_msg Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ...
+ [ n = y ]
+ printf Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ...
Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ... + zfs set
mountpoint=/ /ROOT/linux
+ ZFS_STDERR=cannot open '/ROOT/linux': invalid dataset name
+ [ n != y ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ [ n != y ]
+ log_begin_msg Mounting ZFS filesystem /ROOT/linux
+ _log_msg Begin: Mounting ZFS filesystem /ROOT/linux ...
+ [ n = y ]
+ printf Begin: Mounting ZFS filesystem /ROOT/linux ...
Begin: Mounting ZFS filesystem /ROOT/linux ... + mount -t zfs -o zfsutil
/ROOT/linux /root
+ ZFS_STDERR=filesystem 'ROOT/linux' cannot be mounted, unable to open the
dataset
mount: mounting /ROOT/linux on /root failed: No such file or directory
+ ZFS_ERROR=1
+ [ n != y ]
+ log_end_msg
+ _log_msg done.\n
+ [ n = y ]
+ printf done.\n
done.
+ [ 1 -ne 0 ]
+ panic Command: mount -t zfs -o zfsutil /ROOT/linux /root
Message: filesystem 'ROOT/linux' cannot be mounted, unable to open the dataset
mount: mounting /ROOT/linux on /root failed: No such file or directory
Error: 1
Manually mount the root filesystem on /root and then exit.
A 'mount -t zfs -o zfsutil rpool/ROOT/linux /root' fixis it and after an 'exit'
the system finally starts.
** Affects: grub2 (Ubuntu)
Importance: Undecided
Status: New
** Package changed: dmidecode (Ubuntu) => grub2 (Ubuntu)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1688424
Title:
grub-mkrelpath returns invalid zfs dataset -> initramfs: mount /root
fails
Status in grub2 package in Ubuntu:
New
Bug description:
If zfs is used for boot, boot will fail because of bogus information returned
by
/usr/bin/grub-mkrelpath. E.g. if the zfs dataset for / is rpool/ROOT/linux:
# /usr/bin/grub-mkrelpath /
/ROOT/linux@
This leads to a bogus /boot/grub/grub.cfg because /etc/grub.d/10_linux
generates a boot entry like this:
linux /ROOT/linux@/boot/vmlinuz-4.4.0-77-generic root=ZFS=/ROOT/linux ro
crashkernel=384M-2G:64M,2G-:128M bootdegraded=true debug=y console=ttyS1,115200
crashkernel=384M-:128M
This in turn causes that initramfs to fail on boot:
...
+ wait_for_udev
+ command -v udevadm
+ udevadm settle
+ modprobe zfs zfs_autoimport_disable=1
+ ZFS_BOOTFS=/ROOT/linux
+ echo /ROOT/linux
+ sed -e s,/.*,,
+ ZFS_RPOOL=
+ delay=0
+ [ 0 -gt 0 ]
+ unset delay
+ zpool import -N
[ 10.922149] SPL: The /etc/hostid file is not found.
[ 10.927031] SPL: using hostid 0x
+ ZFS_STDERR=cannot import '': no such pool available
+ ZFS_ERROR=1
+ [ 1 -ne 0 ]
+ panic Command: zpool import -N
Message: cannot import '': no such pool available
Error: 1
Manually import the root pool at the command prompt and then exit.
Hint: Try: zpool import -f -R / -N
Wrong hint BTW, but at least a hint: "zpool import; zpool import
${poolID}|rpool" fixes it.
Anyway, when continuing after an 'exit' it fails with:
...
+ zpool status -L
+ [ n != y ]
+ log_begin_msg Setting mountpoint=/ on ZFS filesystem /ROOT/linux
+ _log_msg Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ...
+ [ n = y ]
+ printf Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ...
Begin: Setting mountpoint=/ on ZFS filesystem /ROOT/linux ... + zfs set
mountpoint=/ /ROOT/linux
+ ZFS_STDERR=cannot open '/ROOT/linux': i
[Kernel-packages] [Bug 1687791] Re: Install of kdump-tools fails
~ # sed -i.orig -e '/^set/ a\set -x' /target/var/lib/dpkg/info/kdump-tools.postinst ~ # tail -f /var/log/syslog May 5 12:11:29 in-target: linux-crashdump depends on kdump-tools; however: May 5 12:11:29 in-target: Package kdump-tools is not configured yet. May 5 12:11:29 in-target: May 5 12:11:29 in-target: dpkg: error processing package linux-crashdump (--configure): May 5 12:11:29 in-target: dependency problems - leaving unconfigured May 5 12:11:29 in-target: Errors were encountered while processing: May 5 12:11:29 in-target: kdump-tools May 5 12:11:29 in-target: linux-crashdump May 5 12:11:29 main-menu[422]: WARNING **: Configuring 'pkgsel' failed with error code 100 May 5 12:11:29 main-menu[422]: WARNING **: Menu item 'pkgsel' failed. May 5 12:13:15 main-menu[422]: INFO: Modifying debconf priority limit from 'critical' to 'high' May 5 12:13:15 debconf: Setting debconf/priority to high May 5 12:13:15 main-menu[422]: INFO: Falling back to the package description for brltty-udeb May 5 12:13:20 main-menu[422]: INFO: Falling back to the package description for brltty-udeb May 5 12:13:20 main-menu[422]: INFO: Menu item 'pkgsel' selected May 5 12:13:21 in-target: Reading package lists... May 5 12:13:21 in-target: May 5 12:13:21 in-target: Building dependency tree... May 5 12:13:21 in-target: May 5 12:13:21 in-target: Reading state information... May 5 12:13:21 in-target: May 5 12:13:21 in-target: tasksel is already the newest version (3.34ubuntu3). May 5 12:13:21 in-target: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. May 5 12:13:21 in-target: 2 not fully installed or removed. May 5 12:13:21 in-target: After this operation, 0 B of additional disk space will be used. May 5 12:13:21 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ...^M May 5 12:13:21 in-target: + uname -r^M May 5 12:13:21 in-target: + /etc/kernel/postinst.d/kdump-tools 4.4.0-62-generic^M May 5 12:13:21 in-target: dpkg: error processing package kdump-tools (--configure):^M May 5 12:13:21 in-target: subprocess installed post-installation script returned error exit status 1^M May 5 12:13:21 in-target: No apport report written because the error message indicates its a followup error from a previous failure. May 5 12:13:21 in-target: dpkg: dependency problems prevent configuration of linux-crashdump:^M May 5 12:13:21 in-target: linux-crashdump depends on kdump-tools; however:^M May 5 12:13:21 in-target: Package kdump-tools is not configured yet.^M May 5 12:13:21 in-target: ^M May 5 12:13:21 in-target: dpkg: error processing package linux-crashdump (--configure):^M May 5 12:13:21 in-target: dependency problems - leaving unconfigured^M May 5 12:13:21 in-target: Errors were encountered while processing:^M May 5 12:13:21 in-target: kdump-tools^M May 5 12:13:21 in-target: linux-crashdump^M May 5 12:13:22 in-target: E: Sub-process /usr/bin/dpkg returned an error code (1) May 5 12:13:22 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ... May 5 12:13:22 in-target: + uname -r May 5 12:13:22 in-target: + /etc/kernel/postinst.d/kdump-tools 4.4.0-62-generic May 5 12:13:22 in-target: dpkg: error processing package kdump-tools (--configure): May 5 12:13:22 in-target: subprocess installed post-installation script returned error exit status 1 May 5 12:13:22 in-target: dpkg: dependency problems prevent configuration of linux-crashdump: May 5 12:13:22 in-target: linux-crashdump depends on kdump-tools; however: May 5 12:13:22 in-target: Package kdump-tools is not configured yet. May 5 12:13:22 in-target: May 5 12:13:22 in-target: dpkg: error processing package linux-crashdump (--configure): May 5 12:13:22 in-target: dependency problems - leaving unconfigured May 5 12:13:22 in-target: Errors were encountered while processing: May 5 12:13:22 in-target: kdump-tools May 5 12:13:22 in-target: linux-crashdump May 5 12:13:24 pkgsel: checking for (security) updates to the base system May 5 12:13:25 in-target: Reading package lists... May 5 12:13:25 in-target: May 5 12:13:25 in-target: Building dependency tree... May 5 12:13:25 in-target: May 5 12:13:25 in-target: Reading state information... May 5 12:13:25 in-target: May 5 12:13:25 in-target: Calculating upgrade... May 5 12:13:25 in-target: May 5 12:13:25 in-target: 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. May 5 12:13:25 in-target: 2 not fully installed or removed. May 5 12:13:25 in-target: After this operation, 0 B of additional disk space will be used. May 5 12:13:25 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ...^M May 5 12:13:25 in-target: + uname -r^M May 5 12:13:25 in-target: + /etc/kernel/postinst.d/kdump-tools 4.4.0-62-generic^M May 5 12:13:25 in-target: dpkg: error processing package kdump-tools (--configure):^M May 5 12:13:25 in-target: subprocess installed post-installation script returned error exit status 1^M May 5 12:13:2
[Kernel-packages] [Bug 1687791] Re: Install of kdump-tools fails
Seems, that this package gets included via preseed: tasksel tasksel/first multiselect minimal d-i pkgsel/include string grub2 linux-crashdump openssh-server tcsh ksh gawk vim sysstat lxc debootstrap libcap-ng-utils acpid at bc ethtool libxslt1.1 lxc-templates patch uidmap xz-utils acl iptables ulogd2 ntp nfs-common autofs ldap-utils gdisk zfsutils-linux zfs-initramfs dmidecode Anyway, IMHO it doesn't matter what kind of install - it should not fail to install. BTW: The image used is http://archive.ubuntu.com/ubuntu/dists/xenial/main/installer- amd64/current/images/netboot/netboot.tar.gz I've already added the 'set -x' as shown above. The 1st line of the output shows, how it has been done (because there is no vi[m] available in the install environment), and the remaining lines show the output after resuming the install (I guess, the installer redirects everything to /var/log/syslog, otherwise I wonder, where else the output gets captured.). Anyway, I can see two lines prefixed with a '+', so I guess, that 'set -x' does what it should, but there is simply not more than this. IIUC, it does not hurt, if it fails - can be done later/on demand as well. So why not append a '|| true' or remove it completely from postinstall ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1687791 Title: Install of kdump-tools fails Status in makedumpfile package in Ubuntu: New Bug description: When installing Ubuntu xenial via netimage, installation fails because of an error, when configuring the kdump-tools. /var/log/syslog says: ... May 2 22:15:17 in-target: Setting up grub2 (2.02~beta2-36ubuntu3.9) ...^M May 2 22:15:17 in-target: Setting up lxc-common (2.0.7-0ubuntu1~16.04.2) ...^M May 2 22:15:17 in-target: Running in chroot, ignoring request.^M May 2 22:15:17 in-target: invoke-rc.d: policy-rc.d denied execution of reload.^M May 2 22:15:17 in-target: Setting up grub-gfxpayload-lists (0.7) ...^M May 2 22:15:17 in-target: Processing triggers for libc-bin (2.23-0ubuntu7) ...^M May 2 22:15:17 in-target: Processing triggers for systemd (229-4ubuntu17) ...^M May 2 22:15:17 in-target: Processing triggers for ureadahead (0.100.0-19) ...^M May 2 22:15:17 in-target: Processing triggers for dbus (1.10.6-1ubuntu3.3) ...^M May 2 22:15:17 in-target: Errors were encountered while processing:^M May 2 22:15:17 in-target: kdump-tools^M May 2 22:15:17 in-target: linux-crashdump^M May 2 22:15:18 in-target: E: Sub-process /usr/bin/dpkg returned an error code (1) May 2 22:15:18 in-target: Setting up kdump-tools (1:1.5.9-5ubuntu0.4) ... May 2 22:15:18 in-target: dpkg: error processing package kdump-tools (--configure): May 2 22:15:18 in-target: subprocess installed post-installation script returned error exit status 1 May 2 22:15:18 in-target: dpkg: dependency problems prevent configuration of linux-crashdump: May 2 22:15:18 in-target: linux-crashdump depends on kdump-tools; however: May 2 22:15:18 in-target: Package kdump-tools is not configured yet. May 2 22:15:18 in-target: May 2 22:15:18 in-target: dpkg: error processing package linux-crashdump (--configure): May 2 22:15:18 in-target: dependency problems - leaving unconfigured May 2 22:15:18 in-target: Errors were encountered while processing: May 2 22:15:18 in-target: kdump-tools May 2 22:15:18 in-target: linux-crashdump May 2 22:15:18 main-menu[616]: WARNING **: Configuring 'pkgsel' failed with error code 100 May 2 22:15:18 main-menu[616]: WARNING **: Menu item 'pkgsel' failed. After this the 'Select and install software' dialog pops up and says, that 'Installation step failed'. If one presses '', one gets bombed back into the 'Ubuntu installer main menu'. Now you get into a loop, when choosing the 'Select and install software' item from the menu. Installer image is 'Linux foo 4.4.0-62-generic #83-Ubuntu SMP Wed Jan 18 14:10:15 UTC 2017 x86_64 GNU/Linux'. The only workaround found so far is: cp -p /target/var/lib/dpkg/info/kdump-tools.postinst \ /target/var/lib/dpkg/info/kdump-tools.postinst.suck printf '#!/bin/sh\nexit 0\n' \ >/target/var/lib/dpkg/info/kdump-tools.postinst To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1687791/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688890] [NEW] initramfs-zfs should support misc /dev dirs
Public bug reported: Right now 'zfs-initramfs', i.e. /usr/share/initramfs-tools/scripts/zfs does not support any other directory than /dev for "zpool import ...". Therefore even if a pool gets created from a different directory like /dev, say /dev/disk/by-id or /dev/chassis/SYS on next reboot /dev will be used and thus zpool status will show the /dev/sd* etc. on successful import. Beside that now a user does not see the original names used in "zpool create ..." the unstable names like "/dev/sd*" are shown, which is explicitly NOT recommended. The following patch introduces the "pseudo" kernel param named "zdirs" - a comma separated list of dev dirs to scan on import - which gets used by /usr/share/initramfs-tools/scripts/zfs to honor it. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New ** Package changed: grub2 (Ubuntu) => zfs-linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1688890 Title: initramfs-zfs should support misc /dev dirs Status in zfs-linux package in Ubuntu: New Bug description: Right now 'zfs-initramfs', i.e. /usr/share/initramfs-tools/scripts/zfs does not support any other directory than /dev for "zpool import ...". Therefore even if a pool gets created from a different directory like /dev, say /dev/disk/by-id or /dev/chassis/SYS on next reboot /dev will be used and thus zpool status will show the /dev/sd* etc. on successful import. Beside that now a user does not see the original names used in "zpool create ..." the unstable names like "/dev/sd*" are shown, which is explicitly NOT recommended. The following patch introduces the "pseudo" kernel param named "zdirs" - a comma separated list of dev dirs to scan on import - which gets used by /usr/share/initramfs-tools/scripts/zfs to honor it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1688890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1688890] Re: initramfs-zfs should support misc /dev dirs
** Patch added: "honor misc /dev dirs" https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1688890/+attachment/4872753/+files/initramfs-zfs.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1688890 Title: initramfs-zfs should support misc /dev dirs Status in zfs-linux package in Ubuntu: New Bug description: Right now 'zfs-initramfs', i.e. /usr/share/initramfs-tools/scripts/zfs does not support any other directory than /dev for "zpool import ...". Therefore even if a pool gets created from a different directory like /dev, say /dev/disk/by-id or /dev/chassis/SYS on next reboot /dev will be used and thus zpool status will show the /dev/sd* etc. on successful import. Beside that now a user does not see the original names used in "zpool create ..." the unstable names like "/dev/sd*" are shown, which is explicitly NOT recommended. The following patch introduces the "pseudo" kernel param named "zdirs" - a comma separated list of dev dirs to scan on import - which gets used by /usr/share/initramfs-tools/scripts/zfs to honor it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1688890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1685528] Re: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail
It should not restrict import to hardcoded /dev and /dev/disk/by-id - see https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1688890 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1685528 Title: ZFS initramfs mounts dataset explicitly set not to be mounted, causing boot process to fail Status in zfs-linux package in Ubuntu: New Bug description: Per https://github.com/zfsonlinux/pkg-zfs/issues/221: the initramfs zfs script might overrule canmount and mountpoint options for a dataset, causing other mount operations and with them the boot process to fail. Experienced this with Ubuntu Zesty. Xenial seems to ship with a different zfs script for the initrd. Work around when it happens: unmount the dataset that should not be mounted, and exit the initramfs rescue prompt to resume booting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1685528/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905160] [NEW] zfs-initramfs: zfs import rpool fails - too early
Public bug reported:
/usr/share/initramfs-tools/scripts/zfs::import_pool() tries to import
the root pool (in my case named rpool) before the related devices are
available, i.e. scsi scan has been finished.
I use the following Q&D workaround to fix it:
--- /usr/share/initramfs-tools/scripts/zfs.orig 2020-08-18 11:10:41.0
+0200
+++ /usr/share/initramfs-tools/scripts/zfs 2020-11-22 09:03:10.17698 +0100
@@ -217,12 +217,21 @@
import_pool()
{
local pool="$1"
- local dirs dir
+ local dirs dir T=30
# Verify that the pool isn't already imported
# Make as sure as we can to not require '-f' to import.
"${ZPOOL}" get name,guid -o value -H 2>/dev/null | grep -Fxq "$pool" &&
return 0
+ # Make sure, that at least rpool devices are available. Otherwise
+ # zfs import may fail for "no" reason.
+ while [ ! -e /dev/chassis/SYS/DOM0p2 ]; do
+ sleep 1
+ let T-=1
+ [ $T -lt 0 ] && break
+ done
+ /bin/udevadm settle
+
# For backwards compatibility, make sure that ZPOOL_IMPORT_PATH is set
# to something we can use later with the real import(s). We want to
# make sure we find all by* dirs, BUT by-vdev should be first (if it
###
/dev/chassis/SYS/DOM0p2 is one dev of the rpool 3-way mirror [the others
are /dev/chassis/SYS/DOM1p2 and /dev/nvme0n1p2]. DOM* are SM SuperDOMs
sitting on */ata[56]/* bus, but get handled s scsi devices as well.
Unfortunately things like 'udevadm settle' or 'udevadm settle --exit-if-
exists=/dev/chassis/SYS/DOM0p2' or 'udevadm trigger --verbose
--type=devices --subsystem-match=scsi_disk' did not fix the problem. Not
sure whether there is a way to say, wait until scsi subsystem [scan] has
been finished.
To get a better idea I'll attach 2 files: xxxlong-fail.out shows the
debug output when booting the vanilla focal, xxxlong-patched.out shows
the debug output with the patch above applied.
BTW: Because it takes Ubuntu ~ 29 min to boot when the 2nd pool with 44
disks is ZoL formatted, I disabled the OPROM usage of related SAS-HBA in
the UEFI-BIOS (so that the disks cannot be seen) which brings it back to
~ 1:45 min until the kernel actually starts. I guess, therefore Linux
needs a little bit more time to initialize it and that's why 'zfs import
...' starts too early. However, a system boot time of 30+ min is
unacceptable and thus letting the BIOS initialize the HBA is not an
option. I guess that's a linux efi bootloader problem: Solaris did not
have any problems on this machine, even with HBA-OPROM enabled ...
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "debug output when import fails"
https://bugs.launchpad.net/bugs/1905160/+attachment/5436798/+files/xxxlong-fail.out
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1905160
Title:
zfs-initramfs: zfs import rpool fails - too early
Status in zfs-linux package in Ubuntu:
New
Bug description:
/usr/share/initramfs-tools/scripts/zfs::import_pool() tries to import
the root pool (in my case named rpool) before the related devices are
available, i.e. scsi scan has been finished.
I use the following Q&D workaround to fix it:
--- /usr/share/initramfs-tools/scripts/zfs.orig 2020-08-18 11:10:41.0
+0200
+++ /usr/share/initramfs-tools/scripts/zfs 2020-11-22 09:03:10.17698
+0100
@@ -217,12 +217,21 @@
import_pool()
{
local pool="$1"
- local dirs dir
+ local dirs dir T=30
# Verify that the pool isn't already imported
# Make as sure as we can to not require '-f' to import.
"${ZPOOL}" get name,guid -o value -H 2>/dev/null | grep -Fxq "$pool" &&
return 0
+ # Make sure, that at least rpool devices are available. Otherwise
+ # zfs import may fail for "no" reason.
+ while [ ! -e /dev/chassis/SYS/DOM0p2 ]; do
+ sleep 1
+ let T-=1
+ [ $T -lt 0 ] && break
+ done
+ /bin/udevadm settle
+
# For backwards compatibility, make sure that ZPOOL_IMPORT_PATH is set
# to something we can use later with the real import(s). We want to
# make sure we find all by* dirs, BUT by-vdev should be first (if it
###
/dev/chassis/SYS/DOM0p2 is one dev of the rpool 3-way mirror [the
others are /dev/chassis/SYS/DOM1p2 and /dev/nvme0n1p2]. DOM* are SM
SuperDOMs sitting on */ata[56]/* bus, but get handled s scsi devices
as well. Unfortunately things like 'udevadm settle' or 'udevadm settle
--exit-if-exists=/dev/chassis/SYS/DOM0p2' or 'udevadm trigger
--verbose --type=devices --subsystem-match=scsi_disk' did not fix the
problem. Not sure whether there is a way to say, wait until scsi
subsystem [scan] has been finished.
To get a better idea I'll attach 2 files: xxxlong-fail.out shows the
debug output when booting the vanilla focal, xxxlong-patched.out shows
the debug output with the patch a
[Kernel-packages] [Bug 1905160] Re: zfs-initramfs: zfs import rpool fails - too early
** Attachment added: "debug output with Q&D fix"
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1905160/+attachment/5436799/+files/xxxlong-patched.out
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1905160
Title:
zfs-initramfs: zfs import rpool fails - too early
Status in zfs-linux package in Ubuntu:
New
Bug description:
/usr/share/initramfs-tools/scripts/zfs::import_pool() tries to import
the root pool (in my case named rpool) before the related devices are
available, i.e. scsi scan has been finished.
I use the following Q&D workaround to fix it:
--- /usr/share/initramfs-tools/scripts/zfs.orig 2020-08-18 11:10:41.0
+0200
+++ /usr/share/initramfs-tools/scripts/zfs 2020-11-22 09:03:10.17698
+0100
@@ -217,12 +217,21 @@
import_pool()
{
local pool="$1"
- local dirs dir
+ local dirs dir T=30
# Verify that the pool isn't already imported
# Make as sure as we can to not require '-f' to import.
"${ZPOOL}" get name,guid -o value -H 2>/dev/null | grep -Fxq "$pool" &&
return 0
+ # Make sure, that at least rpool devices are available. Otherwise
+ # zfs import may fail for "no" reason.
+ while [ ! -e /dev/chassis/SYS/DOM0p2 ]; do
+ sleep 1
+ let T-=1
+ [ $T -lt 0 ] && break
+ done
+ /bin/udevadm settle
+
# For backwards compatibility, make sure that ZPOOL_IMPORT_PATH is set
# to something we can use later with the real import(s). We want to
# make sure we find all by* dirs, BUT by-vdev should be first (if it
###
/dev/chassis/SYS/DOM0p2 is one dev of the rpool 3-way mirror [the
others are /dev/chassis/SYS/DOM1p2 and /dev/nvme0n1p2]. DOM* are SM
SuperDOMs sitting on */ata[56]/* bus, but get handled s scsi devices
as well. Unfortunately things like 'udevadm settle' or 'udevadm settle
--exit-if-exists=/dev/chassis/SYS/DOM0p2' or 'udevadm trigger
--verbose --type=devices --subsystem-match=scsi_disk' did not fix the
problem. Not sure whether there is a way to say, wait until scsi
subsystem [scan] has been finished.
To get a better idea I'll attach 2 files: xxxlong-fail.out shows the
debug output when booting the vanilla focal, xxxlong-patched.out shows
the debug output with the patch above applied.
BTW: Because it takes Ubuntu ~ 29 min to boot when the 2nd pool with
44 disks is ZoL formatted, I disabled the OPROM usage of related SAS-
HBA in the UEFI-BIOS (so that the disks cannot be seen) which brings
it back to ~ 1:45 min until the kernel actually starts. I guess,
therefore Linux needs a little bit more time to initialize it and
that's why 'zfs import ...' starts too early. However, a system boot
time of 30+ min is unacceptable and thus letting the BIOS initialize
the HBA is not an option. I guess that's a linux efi bootloader
problem: Solaris did not have any problems on this machine, even with
HBA-OPROM enabled ...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1905160/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905160] Re: zfs-initramfs: zfs import rpool fails - too early
There is no apport* installed on the machine.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1905160
Title:
zfs-initramfs: zfs import rpool fails - too early
Status in zfs-linux package in Ubuntu:
New
Bug description:
/usr/share/initramfs-tools/scripts/zfs::import_pool() tries to import
the root pool (in my case named rpool) before the related devices are
available, i.e. scsi scan has been finished.
I use the following Q&D workaround to fix it:
--- /usr/share/initramfs-tools/scripts/zfs.orig 2020-08-18 11:10:41.0
+0200
+++ /usr/share/initramfs-tools/scripts/zfs 2020-11-22 09:03:10.17698
+0100
@@ -217,12 +217,21 @@
import_pool()
{
local pool="$1"
- local dirs dir
+ local dirs dir T=30
# Verify that the pool isn't already imported
# Make as sure as we can to not require '-f' to import.
"${ZPOOL}" get name,guid -o value -H 2>/dev/null | grep -Fxq "$pool" &&
return 0
+ # Make sure, that at least rpool devices are available. Otherwise
+ # zfs import may fail for "no" reason.
+ while [ ! -e /dev/chassis/SYS/DOM0p2 ]; do
+ sleep 1
+ let T-=1
+ [ $T -lt 0 ] && break
+ done
+ /bin/udevadm settle
+
# For backwards compatibility, make sure that ZPOOL_IMPORT_PATH is set
# to something we can use later with the real import(s). We want to
# make sure we find all by* dirs, BUT by-vdev should be first (if it
###
/dev/chassis/SYS/DOM0p2 is one dev of the rpool 3-way mirror [the
others are /dev/chassis/SYS/DOM1p2 and /dev/nvme0n1p2]. DOM* are SM
SuperDOMs sitting on */ata[56]/* bus, but get handled s scsi devices
as well. Unfortunately things like 'udevadm settle' or 'udevadm settle
--exit-if-exists=/dev/chassis/SYS/DOM0p2' or 'udevadm trigger
--verbose --type=devices --subsystem-match=scsi_disk' did not fix the
problem. Not sure whether there is a way to say, wait until scsi
subsystem [scan] has been finished.
To get a better idea I'll attach 2 files: xxxlong-fail.out shows the
debug output when booting the vanilla focal, xxxlong-patched.out shows
the debug output with the patch above applied.
BTW: Because it takes Ubuntu ~ 29 min to boot when the 2nd pool with
44 disks is ZoL formatted, I disabled the OPROM usage of related SAS-
HBA in the UEFI-BIOS (so that the disks cannot be seen) which brings
it back to ~ 1:45 min until the kernel actually starts. I guess,
therefore Linux needs a little bit more time to initialize it and
that's why 'zfs import ...' starts too early. However, a system boot
time of 30+ min is unacceptable and thus letting the BIOS initialize
the HBA is not an option. I guess that's a linux efi bootloader
problem: Solaris did not have any problems on this machine, even with
HBA-OPROM enabled ...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1905160/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1711407] Re: unregister_netdevice: waiting for lo to become free
Since xenial we have this very annoying behavior (unregister_netdevice: waiting for lo to become free. Usage count = 1) as well, which in turn makes a container reboot taking several minutes instead of seconds e.g. on vivid (lxc-ls -f also hangs for that time). E.g.: [ +10.244888] unregister_netdevice: waiting for lo to become free. Usage count = 1 [Oct 2 17:16] INFO: task lxc-autostart:5321 blocked for more than 120 seconds. [ +0.007147] Tainted: P OE 4.4.0-96-generic #119-Ubuntu [ +0.006796] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ +0.007913] lxc-autostart D 883fb99fbcb8 0 5321 1 0x [ +0.07] 883fb99fbcb8 883ff2a3aa00 881fed2fe200 [ +0.04] 883fb99fc000 81ef79a4 881fed2fe200 [ +0.04] 81ef79a8 883fb99fbcd0 8183f165 81ef79a0 [ +0.04] Call Trace: [ +0.14] [] schedule+0x35/0x80 [ +0.05] [] schedule_preempt_disabled+0xe/0x10 [ +0.16] [] __mutex_lock_slowpath+0xb9/0x130 [ +0.14] [] mutex_lock+0x1f/0x30 [ +0.09] [] copy_net_ns+0x6e/0x120 [ +0.09] [] create_new_namespaces+0x11b/0x1d0 [ +0.03] [] copy_namespaces+0x6d/0xa0 [ +0.07] [] copy_process+0x8e2/0x1b30 [ +0.11] [] _do_fork+0x80/0x360 [ +0.15] [] ? exit_to_usermode_loop+0xa6/0xd0 [ +0.04] [] SyS_clone+0x19/0x20 [ +0.09] [] entry_SYSCALL_64_fastpath+0x16/0x71 [ +4.882232] unregister_netdevice: waiting for lo to become free. Usage count = 1 ... -- 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/1711407 Title: unregister_netdevice: waiting for lo to become free Status in linux package in Ubuntu: Confirmed Bug description: This is a "continuation" of bug 1403152, as that bug has been marked "fix released" and recent reports of failure may (or may not) be a new bug. Any further reports of the problem should please be reported here instead of that bug. -- [Impact] When shutting down and starting containers the container network namespace may experience a dst reference counting leak which results in this message repeated in the logs: unregister_netdevice: waiting for lo to become free. Usage count = 1 This can cause issues when trying to create net network namespace and thus block a user from creating new containers. [Test Case] See comment 16, reproducer provided at https://github.com/fho/docker- samba-loop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687664] Re: grub-probe zfs bug: failed to get canonical path
BTW: Just encountered, that netinstall fails, when it tries to install grub, because /sys seems not to be mounted to /target/sys: # zpool status The ZFS modules are not loaded. Try running '/sbin/modprobe zfs' as root to load them. After a mount --rbind /sys /target/sys : # zpool status pool: rpool state: ONLINE scan: none requested config: NAMESTATE READ WRITE CKSUM rpool ONLINE 0 0 0 HDD0p2ONLINE 0 0 0 errors: No known data errors -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1687664 Title: grub-probe zfs bug: failed to get canonical path Status in grub2 package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: grub-probe / fails with grub-probe: error: failed to get canonical path of `/dev/HDD0p2'. This is simply because grub makes the wrong assumption, that "zpool status $pool" lists the vdevs in use only with the '/dev/' prefix stripped off. It probably assumes something like /dev/sda etc., which is discouraged to use. Instead, grub should use "zpool status -P $pool" to get the full device path. This would probably result into a symlink, e.g. /dev /disk-by-id/$bla . If this is not sufficient, grub should use realpath() to get the final blockdev entry like /dev/sda1 . The current setup I use is: 433 0 drwxr-xr-x 4 root root 80 Apr 28 20:22 /dev/chassis/SYS 434 0 drwxr-xr-x 2 root root 200 Apr 28 23:06 /dev/chassis/SYS/HDD0 435 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0 -> ../../../sda 417 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p1 -> ../../../sda1 442 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p2 -> ../../../sda2 423 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p9 -> ../../../sda9 436 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD0/disk -> ../../../sda 418 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p1 -> ../../../sda1 443 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p2 -> ../../../sda2 424 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p9 -> ../../../sda9 437 0 drwxr-xr-x 2 root root 80 Apr 28 20:22 /dev/chassis/SYS/HDD1 438 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD1/HDD1 -> ../../../sdb 439 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD1/disk -> ../../../sdb with 'zpool create ... rpool /dev/chassis/SYS/HDD0/HDD0p2' PS: The full version is 2.02~beta2-36ubuntu3.9 and ZoL 0.6.5.6-0ubuntu15 (Ubuntu xenial 16.04). For simulation one may setup a VirtualBox VM, with Storage == Controller SAS (Type: LsiLogic SAS, Port Count: 8), and e.g. one VDI attached to it (/dev/sda) and e.g. netboot an install image. When it comes to the 'partitioning disks' dialog, start a shell and fetch/install ksh93 (i.e. ksh-udeb). Than the script http://iks.cs.ovgu.de/~elkner/tmp/ubuntu/bayLinks.sh can be used, to create the required dev symlinks (e.g. bayLinks.sh -mru). For convenience http://iks.cs.ovgu.de/~elkner/tmp/ubuntu/ubuntu-part.sh can be used to create the script for [re-]partitioning the drive[s] and setup zfs related stuff (whereby the 'zpool create' and consecutive stuff will fail because of the bug). E.g. /tmp/ubuntu-part.sh /dev/chassis/SYS/HDD0/HDD0 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1687664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687664] Re: grub-probe zfs bug: failed to get canonical path
BUG or not? At least I get mixed feelings, when I see, that the log device gets passed to grub-probe! E.g.: + zpool status rpool pool: rpool state: ONLINE scan: resilvered 547M in 0h0m with 0 errors on Thu May 18 03:49:08 2017 config: NAME STATE READ WRITE CKSUM rpoolONLINE 0 0 0 mirror-0 ONLINE 0 0 0 HDD0p2 ONLINE 0 0 0 HDD12p2 ONLINE 0 0 0 logs HDD2p3 ONLINE 0 0 0 spares HDD1p2 AVAIL errors: No known data errors + zpool status -P rpool pool: rpool state: ONLINE scan: resilvered 547M in 0h0m with 0 errors on Thu May 18 03:49:08 2017 config: NAME STATE READ WRITE CKSUM rpool ONLINE 0 0 0 mirror-0ONLINE 0 0 0 /dev/chassis/SYS/HDD0p2 ONLINE 0 0 0 /dev/chassis/SYS/HDD12p2 ONLINE 0 0 0 logs /dev/chassis/SYS/HDD2p3 ONLINE 0 0 0 spares /dev/chassis/SYS/HDD1p2 AVAIL errors: No known data errors and than on update-grub I see: ... prepare_grub_to_access_device /dev/sda2 /dev/sdf2 /dev/sdb3 + old_ifs= + IFS= + /usr/sbin/grub-probe --device /dev/sda2 /dev/sdf2 /dev/sdb3 --target=partmap /usr/sbin/grub-probe: error: cannot find a GRUB drive for /dev/sda2. Check your device.map. ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1687664 Title: grub-probe zfs bug: failed to get canonical path Status in grub2 package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: grub-probe / fails with grub-probe: error: failed to get canonical path of `/dev/HDD0p2'. This is simply because grub makes the wrong assumption, that "zpool status $pool" lists the vdevs in use only with the '/dev/' prefix stripped off. It probably assumes something like /dev/sda etc., which is discouraged to use. Instead, grub should use "zpool status -P $pool" to get the full device path. This would probably result into a symlink, e.g. /dev /disk-by-id/$bla . If this is not sufficient, grub should use realpath() to get the final blockdev entry like /dev/sda1 . The current setup I use is: 433 0 drwxr-xr-x 4 root root 80 Apr 28 20:22 /dev/chassis/SYS 434 0 drwxr-xr-x 2 root root 200 Apr 28 23:06 /dev/chassis/SYS/HDD0 435 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0 -> ../../../sda 417 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p1 -> ../../../sda1 442 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p2 -> ../../../sda2 423 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p9 -> ../../../sda9 436 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD0/disk -> ../../../sda 418 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p1 -> ../../../sda1 443 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p2 -> ../../../sda2 424 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p9 -> ../../../sda9 437 0 drwxr-xr-x 2 root root 80 Apr 28 20:22 /dev/chassis/SYS/HDD1 438 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD1/HDD1 -> ../../../sdb 439 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD1/disk -> ../../../sdb with 'zpool create ... rpool /dev/chassis/SYS/HDD0/HDD0p2' PS: The full version is 2.02~beta2-36ubuntu3.9 and ZoL 0.6.5.6-0ubuntu15 (Ubuntu xenial 16.04). For simulation one may setup a VirtualBox VM, with Storage == Controller SAS (Type: LsiLogic SAS, Port Count: 8), and e.g. one VDI attached to it (/dev/sda) and e.g. netboot an install image. When it comes to the 'partitioning disks' dialog, start a shell and fetch/install ksh93 (i.e. ksh-udeb). Than the script http://iks.cs.ovgu.de/~elkner/tmp/ubuntu/bayLinks.sh can be used, to create the required dev symlinks (e.g. bayLinks.sh -mru). For convenience http://iks.cs.ovgu.de/~elkner/tmp/ubuntu/ubuntu-part.sh can be used to create the script for [re-]partitioning the drive[s] and setup zfs related stuff (whereby the 'zpool create' and consecutive stuff will fail because of the bug). E.g. /tmp/ubuntu-part.sh /dev/chassis/SYS/HDD0/HDD0 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1687664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687664] Re: grub-probe zfs bug: failed to get canonical path
Wondering, whether there is an official repository, where one may look into the source of the shipped version of the package. I found https://launchpad.net/ubuntu/+source/grub2/2.02~beta2-36ubuntu3.9, but even the grub2_2.02~beta2.orig.tar.xz is != to what is tagged as grub-2.02-beta2 in the official repo (https://git.savannah.gnu.org/git/grub.git) ... g ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1687664 Title: grub-probe zfs bug: failed to get canonical path Status in grub2 package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: grub-probe / fails with grub-probe: error: failed to get canonical path of `/dev/HDD0p2'. This is simply because grub makes the wrong assumption, that "zpool status $pool" lists the vdevs in use only with the '/dev/' prefix stripped off. It probably assumes something like /dev/sda etc., which is discouraged to use. Instead, grub should use "zpool status -P $pool" to get the full device path. This would probably result into a symlink, e.g. /dev /disk-by-id/$bla . If this is not sufficient, grub should use realpath() to get the final blockdev entry like /dev/sda1 . The current setup I use is: 433 0 drwxr-xr-x 4 root root 80 Apr 28 20:22 /dev/chassis/SYS 434 0 drwxr-xr-x 2 root root 200 Apr 28 23:06 /dev/chassis/SYS/HDD0 435 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0 -> ../../../sda 417 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p1 -> ../../../sda1 442 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p2 -> ../../../sda2 423 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p9 -> ../../../sda9 436 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD0/disk -> ../../../sda 418 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p1 -> ../../../sda1 443 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p2 -> ../../../sda2 424 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p9 -> ../../../sda9 437 0 drwxr-xr-x 2 root root 80 Apr 28 20:22 /dev/chassis/SYS/HDD1 438 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD1/HDD1 -> ../../../sdb 439 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD1/disk -> ../../../sdb with 'zpool create ... rpool /dev/chassis/SYS/HDD0/HDD0p2' PS: The full version is 2.02~beta2-36ubuntu3.9 and ZoL 0.6.5.6-0ubuntu15 (Ubuntu xenial 16.04). For simulation one may setup a VirtualBox VM, with Storage == Controller SAS (Type: LsiLogic SAS, Port Count: 8), and e.g. one VDI attached to it (/dev/sda) and e.g. netboot an install image. When it comes to the 'partitioning disks' dialog, start a shell and fetch/install ksh93 (i.e. ksh-udeb). Than the script http://iks.cs.ovgu.de/~elkner/tmp/ubuntu/bayLinks.sh can be used, to create the required dev symlinks (e.g. bayLinks.sh -mru). For convenience http://iks.cs.ovgu.de/~elkner/tmp/ubuntu/ubuntu-part.sh can be used to create the script for [re-]partitioning the drive[s] and setup zfs related stuff (whereby the 'zpool create' and consecutive stuff will fail because of the bug). E.g. /tmp/ubuntu-part.sh /dev/chassis/SYS/HDD0/HDD0 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1687664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1687664] Re: grub-probe zfs bug: failed to get canonical path
*** This bug is a duplicate of bug 1527727 *** https://bugs.launchpad.net/bugs/1527727 No ETAs, when the backport is available for the LTS release? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1687664 Title: grub-probe zfs bug: failed to get canonical path Status in grub2 package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: grub-probe / fails with grub-probe: error: failed to get canonical path of `/dev/HDD0p2'. This is simply because grub makes the wrong assumption, that "zpool status $pool" lists the vdevs in use only with the '/dev/' prefix stripped off. It probably assumes something like /dev/sda etc., which is discouraged to use. Instead, grub should use "zpool status -P $pool" to get the full device path. This would probably result into a symlink, e.g. /dev /disk-by-id/$bla . If this is not sufficient, grub should use realpath() to get the final blockdev entry like /dev/sda1 . The current setup I use is: 433 0 drwxr-xr-x 4 root root 80 Apr 28 20:22 /dev/chassis/SYS 434 0 drwxr-xr-x 2 root root 200 Apr 28 23:06 /dev/chassis/SYS/HDD0 435 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0 -> ../../../sda 417 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p1 -> ../../../sda1 442 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p2 -> ../../../sda2 423 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/HDD0p9 -> ../../../sda9 436 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD0/disk -> ../../../sda 418 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p1 -> ../../../sda1 443 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p2 -> ../../../sda2 424 0 lrwxrwxrwx 1 root root 13 Apr 28 23:16 /dev/chassis/SYS/HDD0/p9 -> ../../../sda9 437 0 drwxr-xr-x 2 root root 80 Apr 28 20:22 /dev/chassis/SYS/HDD1 438 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD1/HDD1 -> ../../../sdb 439 0 lrwxrwxrwx 1 root root 12 Apr 28 23:16 /dev/chassis/SYS/HDD1/disk -> ../../../sdb with 'zpool create ... rpool /dev/chassis/SYS/HDD0/HDD0p2' PS: The full version is 2.02~beta2-36ubuntu3.9 and ZoL 0.6.5.6-0ubuntu15 (Ubuntu xenial 16.04). For simulation one may setup a VirtualBox VM, with Storage == Controller SAS (Type: LsiLogic SAS, Port Count: 8), and e.g. one VDI attached to it (/dev/sda) and e.g. netboot an install image. When it comes to the 'partitioning disks' dialog, start a shell and fetch/install ksh93 (i.e. ksh-udeb). Than the script http://iks.cs.ovgu.de/~elkner/tmp/ubuntu/bayLinks.sh can be used, to create the required dev symlinks (e.g. bayLinks.sh -mru). For convenience http://iks.cs.ovgu.de/~elkner/tmp/ubuntu/ubuntu-part.sh can be used to create the script for [re-]partitioning the drive[s] and setup zfs related stuff (whereby the 'zpool create' and consecutive stuff will fail because of the bug). E.g. /tmp/ubuntu-part.sh /dev/chassis/SYS/HDD0/HDD0 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1687664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1694090] [NEW] ZoL: wrong import order prevents boot
Public bug reported: I've the following zfs: # zfs list -r rpool/VARSHARE NAME USED AVAIL REFER MOUNTPOINT rpool/VARSHARE 114K 165G30K /var/share rpool/VARSHARE/lxc84K 165G19K /var/share/lxc rpool/VARSHARE/lxc/xenial 65K 165G19K /var/share/lxc/xenial rpool/VARSHARE/lxc/xenial/pkg 19K 165G19K /var/share/lxc/xenial/pkg rpool/VARSHARE/lxc/xenial/rootfs-amd6427K 165G27K /var/share/lxc/xenial/rootfs-amd64 On boot, we see Starting Mount ZFS filesystems... [FAILED] Failed to start Mount ZFS filesystems. See 'systemctl status zfs-mount.service' for details. Welcome to emergPress Enter for maintenance (or press Control-D to continue): # df -h /var/share rpool/VARSHARE/lxc165G 0 165G 0% /var/share/lxc rpool/VARSHARE/lxc/xenial 165G 0 165G 0% /var/share/lxc/xenial rpool/VARSHARE/lxc/xenial/pkg 165G 0 165G 0% /var/share/lxc/xenial/pkg rpool/VARSHARE/lxc/xenial/rootfs-amd64165G 0 165G 0% /var/share/lxc/xenial/rootfs-amd64 Obviously rpool/VARSHARE - the parent of rpool/VARSHARE/lxc - was not mounted, even so canmount property is for all set to on, rpool/VARSHARE's mountpoint to /var/share and rpool/VARSHARE/lxc children inherit their mountpoint. # systemctl status zfs-mount.service ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2017-05-28 04:51:46 CEST; 13min ago Process: 6935 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 6935 (code=exited, status=1/FAILURE) May 28 04:51:45 ares systemd[1]: Starting Mount ZFS filesystems... May 28 04:51:45 ares zfs[6935]: cannot mount '/var/share': directory is not empty May 28 04:51:46 ares systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE May 28 04:51:46 ares systemd[1]: Failed to start Mount ZFS filesystems. May 28 04:51:46 ares systemd[1]: zfs-mount.service: Unit entered failed state. May 28 04:51:46 ares systemd[1]: zfs-mount.service: Failed with result 'exit-code'. So 'zfs mount ...' seems to be severely buggy. ** Affects: zfs-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1694090 Title: ZoL: wrong import order prevents boot Status in zfs-linux package in Ubuntu: New Bug description: I've the following zfs: # zfs list -r rpool/VARSHARE NAME USED AVAIL REFER MOUNTPOINT rpool/VARSHARE 114K 165G30K /var/share rpool/VARSHARE/lxc84K 165G19K /var/share/lxc rpool/VARSHARE/lxc/xenial 65K 165G19K /var/share/lxc/xenial rpool/VARSHARE/lxc/xenial/pkg 19K 165G19K /var/share/lxc/xenial/pkg rpool/VARSHARE/lxc/xenial/rootfs-amd6427K 165G27K /var/share/lxc/xenial/rootfs-amd64 On boot, we see Starting Mount ZFS filesystems... [FAILED] Failed to start Mount ZFS filesystems. See 'systemctl status zfs-mount.service' for details. Welcome to emergPress Enter for maintenance (or press Control-D to continue): # df -h /var/share rpool/VARSHARE/lxc165G 0 165G 0% /var/share/lxc rpool/VARSHARE/lxc/xenial 165G 0 165G 0% /var/share/lxc/xenial rpool/VARSHARE/lxc/xenial/pkg 165G 0 165G 0% /var/share/lxc/xenial/pkg rpool/VARSHARE/lxc/xenial/rootfs-amd64165G 0 165G 0% /var/share/lxc/xenial/rootfs-amd64 Obviously rpool/VARSHARE - the parent of rpool/VARSHARE/lxc - was not mounted, even so canmount property is for all set to on, rpool/VARSHARE's mountpoint to /var/share and rpool/VARSHARE/lxc children inherit their mountpoint. # systemctl status zfs-mount.service ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2017-05-28 04:51:46 CEST; 13min ago Process: 6935 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 6935 (code=exited, status=1/FAILURE) May 28 04:51:45 ares systemd[1]: Starting Mount ZFS filesystems... May 28 04:51:45 ares zfs[6935]: cannot mount '/var/share': directory is not empty May 28 04:51:46 ares systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE May 28 04:51:46 ares systemd[1]: Failed to start Mount ZFS filesystems. May 28 04:51:46 ares systemd[1]: zfs-mount.service: Unit entered failed state. May 28 04:51:46 ares systemd[1]: zfs-mount.service: Failed
[Kernel-packages] [Bug 1694090] Re: ZoL: wrong import order prevents boot
Please read carefully before answering: As already said (and the given output clearly shows the problem beside being mentioned in the subject): zfs screwed up the mount order and mounted rpool/VARSHARE/lxc _before_ rpool/VARSHARE. And when /var/share/lxc gets mounted, obviously /var/share is not empty and thus zfs,mount shot itself into the feet ... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1694090 Title: ZoL: wrong import order prevents boot Status in zfs-linux package in Ubuntu: Incomplete Bug description: I've the following zfs: # zfs list -r rpool/VARSHARE NAME USED AVAIL REFER MOUNTPOINT rpool/VARSHARE 114K 165G30K /var/share rpool/VARSHARE/lxc84K 165G19K /var/share/lxc rpool/VARSHARE/lxc/xenial 65K 165G19K /var/share/lxc/xenial rpool/VARSHARE/lxc/xenial/pkg 19K 165G19K /var/share/lxc/xenial/pkg rpool/VARSHARE/lxc/xenial/rootfs-amd6427K 165G27K /var/share/lxc/xenial/rootfs-amd64 On boot, we see Starting Mount ZFS filesystems... [FAILED] Failed to start Mount ZFS filesystems. See 'systemctl status zfs-mount.service' for details. Welcome to emergPress Enter for maintenance (or press Control-D to continue): # df -h /var/share rpool/VARSHARE/lxc165G 0 165G 0% /var/share/lxc rpool/VARSHARE/lxc/xenial 165G 0 165G 0% /var/share/lxc/xenial rpool/VARSHARE/lxc/xenial/pkg 165G 0 165G 0% /var/share/lxc/xenial/pkg rpool/VARSHARE/lxc/xenial/rootfs-amd64165G 0 165G 0% /var/share/lxc/xenial/rootfs-amd64 Obviously rpool/VARSHARE - the parent of rpool/VARSHARE/lxc - was not mounted, even so canmount property is for all set to on, rpool/VARSHARE's mountpoint to /var/share and rpool/VARSHARE/lxc children inherit their mountpoint. # systemctl status zfs-mount.service ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; static; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2017-05-28 04:51:46 CEST; 13min ago Process: 6935 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 6935 (code=exited, status=1/FAILURE) May 28 04:51:45 ares systemd[1]: Starting Mount ZFS filesystems... May 28 04:51:45 ares zfs[6935]: cannot mount '/var/share': directory is not empty May 28 04:51:46 ares systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE May 28 04:51:46 ares systemd[1]: Failed to start Mount ZFS filesystems. May 28 04:51:46 ares systemd[1]: zfs-mount.service: Unit entered failed state. May 28 04:51:46 ares systemd[1]: zfs-mount.service: Failed with result 'exit-code'. So 'zfs mount ...' seems to be severely buggy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1694090/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1694090] Re: ZoL: wrong import order prevents boot
It might be also a result of the bogus mount.zfs, which requires POSIX
incorrect arguments but honors POSIXLY_CORRECT env var!
Had a similar zfs mount order problem with a rpool/local/home/{A,B,C}
tree (was created using -p option) ...
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1694090
Title:
ZoL: wrong import order prevents boot
Status in zfs-linux package in Ubuntu:
Incomplete
Bug description:
I've the following zfs:
# zfs list -r rpool/VARSHARE
NAME USED AVAIL REFER MOUNTPOINT
rpool/VARSHARE 114K 165G30K /var/share
rpool/VARSHARE/lxc84K 165G19K /var/share/lxc
rpool/VARSHARE/lxc/xenial 65K 165G19K
/var/share/lxc/xenial
rpool/VARSHARE/lxc/xenial/pkg 19K 165G19K
/var/share/lxc/xenial/pkg
rpool/VARSHARE/lxc/xenial/rootfs-amd6427K 165G27K
/var/share/lxc/xenial/rootfs-amd64
On boot, we see
Starting Mount ZFS filesystems...
[FAILED] Failed to start Mount ZFS filesystems.
See 'systemctl status zfs-mount.service' for details.
Welcome to emergPress Enter for maintenance
(or press Control-D to continue):
# df -h /var/share
rpool/VARSHARE/lxc165G 0 165G 0% /var/share/lxc
rpool/VARSHARE/lxc/xenial 165G 0 165G 0%
/var/share/lxc/xenial
rpool/VARSHARE/lxc/xenial/pkg 165G 0 165G 0%
/var/share/lxc/xenial/pkg
rpool/VARSHARE/lxc/xenial/rootfs-amd64165G 0 165G 0%
/var/share/lxc/xenial/rootfs-amd64
Obviously rpool/VARSHARE - the parent of rpool/VARSHARE/lxc - was not
mounted, even so canmount property is for all set to on, rpool/VARSHARE's
mountpoint to /var/share and rpool/VARSHARE/lxc children inherit their
mountpoint.
# systemctl status zfs-mount.service
● zfs-mount.service - Mount ZFS filesystems
Loaded: loaded (/lib/systemd/system/zfs-mount.service; static; vendor
preset: enabled)
Active: failed (Result: exit-code) since Sun 2017-05-28 04:51:46 CEST;
13min ago
Process: 6935 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE)
Main PID: 6935 (code=exited, status=1/FAILURE)
May 28 04:51:45 ares systemd[1]: Starting Mount ZFS filesystems...
May 28 04:51:45 ares zfs[6935]: cannot mount '/var/share': directory is not
empty
May 28 04:51:46 ares systemd[1]: zfs-mount.service: Main process exited,
code=exited, status=1/FAILURE
May 28 04:51:46 ares systemd[1]: Failed to start Mount ZFS filesystems.
May 28 04:51:46 ares systemd[1]: zfs-mount.service: Unit entered failed state.
May 28 04:51:46 ares systemd[1]: zfs-mount.service: Failed with result
'exit-code'.
So 'zfs mount ...' seems to be severely buggy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1694090/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1355010] Re: ernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
Haven't tried, but found a way to fix it myself. In general the problem is, that Ubuntu still uses a setup/environment, which looks like ~15 years ago - all the bogus klibc/busybox pain! I mean, I want to boot a workstation, not my dish washer! In detail one problem seems, that Ubuntu uses the buggy /bin/losetup, and not the working version provided as /sbin/losetup. Furthermore the /bin/run-init seems to be bogus. I replaced it with http://code.metager.de/source/raw/opensuse/mkinitrd/src/run-init.c and finally got nfs boot working. To get a clue, what we do exactly, have a look at: http://iws.cs.uni-magdeburg.de/~elkner/tmp/ubuntu/ The setupUbuntuPXE.sh (entry point) is used to fetch the ISO, setup PXE and mangle the initrd image on the PXE server. Note, that we currently force TORAM for nfs root, because without it Ubuntu stops working after a while (looks like, when the client becomes idle for a certain time, trouble starts - I guess, buggy squash/unionfs implementation ...). -- 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/1355010 Title: ernel panic - not syncing: Attempted to kill init! exitcode=0x0100 Status in “linux” package in Ubuntu: Incomplete Bug description: We are trying to provide Ubuntu desktop (ubuntu-14.04.1-desktop-amd64.iso) to our labs for studs, which just wanna give it a try. Unfortunately it doesn't work: If it tries to exec the final step (e.g. run-init /root /sbin/init textonly toram /root/dev/console 2>&1) it panics: [ 320.076015] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 320.076015] [ 320.085145] CPU: 25 PID: 1 Comm: run-init Not tainted 3.13.0-32-generic #57-Ubuntu [ 320.092709] Hardware name: WBS F224A-DE5/X9DRH-iF, BIOS 3.0b 04/28/2014 [ 320.099315] 883fce017380 881fd31cde78 8171bcb4 81a4e5e8 [ 320.106792] 881fd31cdef0 81714eb5 0010 881fd31cdf00 [ 320.114271] 881fd31cdea0 81f239e0 0100 883fd2d60398 [ 320.121750] Call Trace: [ 320.124215] [] dump_stack+0x45/0x56 [ 320.129360] [] panic+0xc8/0x1d7 [ 320.134158] [] do_exit+0xa41/0xa50 [ 320.139213] [] ? syscall_trace_enter+0x145/0x250 [ 320.145474] [] SyS_exit+0x17/0x20 [ 320.150442] [] tracesys+0xe1/0xe6 I've no clue, what the problem could be. Already tried to append kernel params 'selinux=0 apparmor=0 enforcig=0' but without success :( The /root fs seems to be properly populated (overlayfs). Any hints? --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 BootDmesg: (Nothing has been logged yet.) CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperVersion: 1.340 DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: WBS F224A-DE5 Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/vmlinuz root=/dev/nfs netboot=nfs nfsroot=141.44.24.61:/data/mnt/hostname-14.04.1-desktop-amd64 boot=casper locale=de_DE.UTF-8 pw=$6$7CPMoOcQ$n3dtobqEnQrvJwQUKI/CoowOFI9AyUyf9I1eGY0.WK0s.PeuYpnQcVcsxt/6gN8ksJ7U2wSgAr0yavpDv4CH.0 textonly console=ttyS1,115200 debug selinux=0 apparmor=0 enforcing=0 break=init toram initrd=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/initrd.lz BOOTIF=01-68-05-ca-0a-49-be ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Tags: trusty UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0b dmi.board.asset.tag: 0672042101108 dmi.board.name: X9DRH-iF dmi.board.vendor: Supermicro dmi.board.version: 1.02 dmi.chassis.asset.tag: 0672042071494 dmi.chassis.type: 23 dmi.chassis.vendor: Supermicro dmi.chassis.version: CSE-216BA-R920LPB dmi.modalia
[Kernel-packages] [Bug 1355010] [NEW] ernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
Public bug reported: We are trying to provide Ubuntu desktop (ubuntu-14.04.1-desktop-amd64.iso) to our labs for studs, which just wanna give it a try. Unfortunately it doesn't work: If it tries to exec the final step (e.g. run-init /root /sbin/init textonly toram /root/dev/console 2>&1) it panics: [ 320.076015] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 320.076015] [ 320.085145] CPU: 25 PID: 1 Comm: run-init Not tainted 3.13.0-32-generic #57-Ubuntu [ 320.092709] Hardware name: WBS F224A-DE5/X9DRH-iF, BIOS 3.0b 04/28/2014 [ 320.099315] 883fce017380 881fd31cde78 8171bcb4 81a4e5e8 [ 320.106792] 881fd31cdef0 81714eb5 0010 881fd31cdf00 [ 320.114271] 881fd31cdea0 81f239e0 0100 883fd2d60398 [ 320.121750] Call Trace: [ 320.124215] [] dump_stack+0x45/0x56 [ 320.129360] [] panic+0xc8/0x1d7 [ 320.134158] [] do_exit+0xa41/0xa50 [ 320.139213] [] ? syscall_trace_enter+0x145/0x250 [ 320.145474] [] SyS_exit+0x17/0x20 [ 320.150442] [] tracesys+0xe1/0xe6 I've no clue, what the problem could be. Already tried to append kernel params 'selinux=0 apparmor=0 enforcig=0' but without success :( The /root fs seems to be properly populated (overlayfs). Any hints? ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1355010 Title: ernel panic - not syncing: Attempted to kill init! exitcode=0x0100 Status in “linux” package in Ubuntu: New Bug description: We are trying to provide Ubuntu desktop (ubuntu-14.04.1-desktop-amd64.iso) to our labs for studs, which just wanna give it a try. Unfortunately it doesn't work: If it tries to exec the final step (e.g. run-init /root /sbin/init textonly toram /root/dev/console 2>&1) it panics: [ 320.076015] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 320.076015] [ 320.085145] CPU: 25 PID: 1 Comm: run-init Not tainted 3.13.0-32-generic #57-Ubuntu [ 320.092709] Hardware name: WBS F224A-DE5/X9DRH-iF, BIOS 3.0b 04/28/2014 [ 320.099315] 883fce017380 881fd31cde78 8171bcb4 81a4e5e8 [ 320.106792] 881fd31cdef0 81714eb5 0010 881fd31cdf00 [ 320.114271] 881fd31cdea0 81f239e0 0100 883fd2d60398 [ 320.121750] Call Trace: [ 320.124215] [] dump_stack+0x45/0x56 [ 320.129360] [] panic+0xc8/0x1d7 [ 320.134158] [] do_exit+0xa41/0xa50 [ 320.139213] [] ? syscall_trace_enter+0x145/0x250 [ 320.145474] [] SyS_exit+0x17/0x20 [ 320.150442] [] tracesys+0xe1/0xe6 I've no clue, what the problem could be. Already tried to append kernel params 'selinux=0 apparmor=0 enforcig=0' but without success :( The /root fs seems to be properly populated (overlayfs). Any hints? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1355010] Re: ernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
Since after the kernel panic the machine is frozen, there is no way to run any app or collect further information. ** 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/1355010 Title: ernel panic - not syncing: Attempted to kill init! exitcode=0x0100 Status in “linux” package in Ubuntu: Confirmed Bug description: We are trying to provide Ubuntu desktop (ubuntu-14.04.1-desktop-amd64.iso) to our labs for studs, which just wanna give it a try. Unfortunately it doesn't work: If it tries to exec the final step (e.g. run-init /root /sbin/init textonly toram /root/dev/console 2>&1) it panics: [ 320.076015] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 320.076015] [ 320.085145] CPU: 25 PID: 1 Comm: run-init Not tainted 3.13.0-32-generic #57-Ubuntu [ 320.092709] Hardware name: WBS F224A-DE5/X9DRH-iF, BIOS 3.0b 04/28/2014 [ 320.099315] 883fce017380 881fd31cde78 8171bcb4 81a4e5e8 [ 320.106792] 881fd31cdef0 81714eb5 0010 881fd31cdf00 [ 320.114271] 881fd31cdea0 81f239e0 0100 883fd2d60398 [ 320.121750] Call Trace: [ 320.124215] [] dump_stack+0x45/0x56 [ 320.129360] [] panic+0xc8/0x1d7 [ 320.134158] [] do_exit+0xa41/0xa50 [ 320.139213] [] ? syscall_trace_enter+0x145/0x250 [ 320.145474] [] SyS_exit+0x17/0x20 [ 320.150442] [] tracesys+0xe1/0xe6 I've no clue, what the problem could be. Already tried to append kernel params 'selinux=0 apparmor=0 enforcig=0' but without success :( The /root fs seems to be properly populated (overlayfs). Any hints? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1355010] Re: ernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
apport information ** Tags added: apport-collected ** Description changed: We are trying to provide Ubuntu desktop (ubuntu-14.04.1-desktop-amd64.iso) to our labs for studs, which just wanna give it a try. Unfortunately it doesn't work: If it tries to exec the final step (e.g. run-init /root /sbin/init textonly toram /root/dev/console 2>&1) it panics: [ 320.076015] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 320.076015] [ 320.085145] CPU: 25 PID: 1 Comm: run-init Not tainted 3.13.0-32-generic #57-Ubuntu [ 320.092709] Hardware name: WBS F224A-DE5/X9DRH-iF, BIOS 3.0b 04/28/2014 [ 320.099315] 883fce017380 881fd31cde78 8171bcb4 81a4e5e8 [ 320.106792] 881fd31cdef0 81714eb5 0010 881fd31cdf00 [ 320.114271] 881fd31cdea0 81f239e0 0100 883fd2d60398 [ 320.121750] Call Trace: [ 320.124215] [] dump_stack+0x45/0x56 [ 320.129360] [] panic+0xc8/0x1d7 [ 320.134158] [] do_exit+0xa41/0xa50 [ 320.139213] [] ? syscall_trace_enter+0x145/0x250 [ 320.145474] [] SyS_exit+0x17/0x20 [ 320.150442] [] tracesys+0xe1/0xe6 I've no clue, what the problem could be. Already tried to append kernel params 'selinux=0 apparmor=0 enforcig=0' but without success :( The /root fs seems to be properly populated (overlayfs). Any hints? + --- + ApportVersion: 2.14.1-0ubuntu3.2 + Architecture: amd64 + BootDmesg: (Nothing has been logged yet.) + CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. + CasperVersion: 1.340 + DistroRelease: Ubuntu 14.04 + LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) + Lsusb: + Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub + Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon + Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: WBS F224A-DE5 + Package: linux (not installed) + ProcEnviron: + TERM=linux + PATH=(custom, no user) + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/vmlinuz root=/dev/nfs netboot=nfs nfsroot=141.44.24.61:/data/mnt/hostname-14.04.1-desktop-amd64 boot=casper locale=de_DE.UTF-8 pw=$6$7CPMoOcQ$n3dtobqEnQrvJwQUKI/CoowOFI9AyUyf9I1eGY0.WK0s.PeuYpnQcVcsxt/6gN8ksJ7U2wSgAr0yavpDv4CH.0 textonly console=ttyS1,115200 debug selinux=0 apparmor=0 enforcing=0 break=init toram initrd=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/initrd.lz BOOTIF=01-68-05-ca-0a-49-be + ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 + PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. + RelatedPackageVersions: + linux-restricted-modules-3.13.0-32-generic N/A + linux-backports-modules-3.13.0-32-generic N/A + linux-firmware 1.127.5 + RfKill: + + Tags: trusty + UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' + Uname: Linux 3.13.0-32-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: + + WifiSyslog: + + _MarkForUpload: True + dmi.bios.date: 04/28/2014 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 3.0b + dmi.board.asset.tag: 0672042101108 + dmi.board.name: X9DRH-iF + dmi.board.vendor: Supermicro + dmi.board.version: 1.02 + dmi.chassis.asset.tag: 0672042071494 + dmi.chassis.type: 23 + dmi.chassis.vendor: Supermicro + dmi.chassis.version: CSE-216BA-R920LPB + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnWBS:pnF224A-DE5:pvr3.0:rvnSupermicro:rnX9DRH-iF:rvr1.02:cvnSupermicro:ct23:cvrCSE-216BA-R920LPB: + dmi.product.name: F224A-DE5 + dmi.product.version: 3.0 + dmi.sys.vendor: WBS ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1355010/+attachment/4174536/+files/AlsaInfo.txt -- 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/1355010 Title: ernel panic - not syncing: Attempted to kill init! exitcode=0x0100 Status in “linux” package in Ubuntu: Confirmed Bug description: We are trying to provide Ubuntu desktop (ubuntu-14.04.1-desktop-amd64.iso) to our labs for studs, which just wanna give it a try. Unfortunately it doesn't work: If it tries to exec the final step (e.g. run-init /root /sbin/init textonly toram /root/dev/console 2>&1) it panics: [ 320.076015] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 320.076015] [ 320.085145] CPU: 25 PID: 1 Comm: run-init Not tainted 3.13.0-32-generic #57-Ubuntu [ 320.092709] Hardware name: WBS F224A-DE5/X9DRH-iF, BIOS 3.0b 04/28/2014 [
[Kernel-packages] [Bug 1355010] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1355010/+attachment/4174538/+files/AudioDevicesInUse.txt -- 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/1355010 Title: ernel panic - not syncing: Attempted to kill init! exitcode=0x0100 Status in “linux” package in Ubuntu: Confirmed Bug description: We are trying to provide Ubuntu desktop (ubuntu-14.04.1-desktop-amd64.iso) to our labs for studs, which just wanna give it a try. Unfortunately it doesn't work: If it tries to exec the final step (e.g. run-init /root /sbin/init textonly toram /root/dev/console 2>&1) it panics: [ 320.076015] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 320.076015] [ 320.085145] CPU: 25 PID: 1 Comm: run-init Not tainted 3.13.0-32-generic #57-Ubuntu [ 320.092709] Hardware name: WBS F224A-DE5/X9DRH-iF, BIOS 3.0b 04/28/2014 [ 320.099315] 883fce017380 881fd31cde78 8171bcb4 81a4e5e8 [ 320.106792] 881fd31cdef0 81714eb5 0010 881fd31cdf00 [ 320.114271] 881fd31cdea0 81f239e0 0100 883fd2d60398 [ 320.121750] Call Trace: [ 320.124215] [] dump_stack+0x45/0x56 [ 320.129360] [] panic+0xc8/0x1d7 [ 320.134158] [] do_exit+0xa41/0xa50 [ 320.139213] [] ? syscall_trace_enter+0x145/0x250 [ 320.145474] [] SyS_exit+0x17/0x20 [ 320.150442] [] tracesys+0xe1/0xe6 I've no clue, what the problem could be. Already tried to append kernel params 'selinux=0 apparmor=0 enforcig=0' but without success :( The /root fs seems to be properly populated (overlayfs). Any hints? --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 BootDmesg: (Nothing has been logged yet.) CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperVersion: 1.340 DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: WBS F224A-DE5 Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/vmlinuz root=/dev/nfs netboot=nfs nfsroot=141.44.24.61:/data/mnt/hostname-14.04.1-desktop-amd64 boot=casper locale=de_DE.UTF-8 pw=$6$7CPMoOcQ$n3dtobqEnQrvJwQUKI/CoowOFI9AyUyf9I1eGY0.WK0s.PeuYpnQcVcsxt/6gN8ksJ7U2wSgAr0yavpDv4CH.0 textonly console=ttyS1,115200 debug selinux=0 apparmor=0 enforcing=0 break=init toram initrd=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/initrd.lz BOOTIF=01-68-05-ca-0a-49-be ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Tags: trusty UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0b dmi.board.asset.tag: 0672042101108 dmi.board.name: X9DRH-iF dmi.board.vendor: Supermicro dmi.board.version: 1.02 dmi.chassis.asset.tag: 0672042071494 dmi.chassis.type: 23 dmi.chassis.vendor: Supermicro dmi.chassis.version: CSE-216BA-R920LPB dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnWBS:pnF224A-DE5:pvr3.0:rvnSupermicro:rnX9DRH-iF:rvr1.02:cvnSupermicro:ct23:cvrCSE-216BA-R920LPB: dmi.product.name: F224A-DE5 dmi.product.version: 3.0 dmi.sys.vendor: WBS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1355010] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1355010/+attachment/4174544/+files/ProcInterrupts.txt -- 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/1355010 Title: ernel panic - not syncing: Attempted to kill init! exitcode=0x0100 Status in “linux” package in Ubuntu: Confirmed Bug description: We are trying to provide Ubuntu desktop (ubuntu-14.04.1-desktop-amd64.iso) to our labs for studs, which just wanna give it a try. Unfortunately it doesn't work: If it tries to exec the final step (e.g. run-init /root /sbin/init textonly toram /root/dev/console 2>&1) it panics: [ 320.076015] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 320.076015] [ 320.085145] CPU: 25 PID: 1 Comm: run-init Not tainted 3.13.0-32-generic #57-Ubuntu [ 320.092709] Hardware name: WBS F224A-DE5/X9DRH-iF, BIOS 3.0b 04/28/2014 [ 320.099315] 883fce017380 881fd31cde78 8171bcb4 81a4e5e8 [ 320.106792] 881fd31cdef0 81714eb5 0010 881fd31cdf00 [ 320.114271] 881fd31cdea0 81f239e0 0100 883fd2d60398 [ 320.121750] Call Trace: [ 320.124215] [] dump_stack+0x45/0x56 [ 320.129360] [] panic+0xc8/0x1d7 [ 320.134158] [] do_exit+0xa41/0xa50 [ 320.139213] [] ? syscall_trace_enter+0x145/0x250 [ 320.145474] [] SyS_exit+0x17/0x20 [ 320.150442] [] tracesys+0xe1/0xe6 I've no clue, what the problem could be. Already tried to append kernel params 'selinux=0 apparmor=0 enforcig=0' but without success :( The /root fs seems to be properly populated (overlayfs). Any hints? --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 BootDmesg: (Nothing has been logged yet.) CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperVersion: 1.340 DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: WBS F224A-DE5 Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/vmlinuz root=/dev/nfs netboot=nfs nfsroot=141.44.24.61:/data/mnt/hostname-14.04.1-desktop-amd64 boot=casper locale=de_DE.UTF-8 pw=$6$7CPMoOcQ$n3dtobqEnQrvJwQUKI/CoowOFI9AyUyf9I1eGY0.WK0s.PeuYpnQcVcsxt/6gN8ksJ7U2wSgAr0yavpDv4CH.0 textonly console=ttyS1,115200 debug selinux=0 apparmor=0 enforcing=0 break=init toram initrd=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/initrd.lz BOOTIF=01-68-05-ca-0a-49-be ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Tags: trusty UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0b dmi.board.asset.tag: 0672042101108 dmi.board.name: X9DRH-iF dmi.board.vendor: Supermicro dmi.board.version: 1.02 dmi.chassis.asset.tag: 0672042071494 dmi.chassis.type: 23 dmi.chassis.vendor: Supermicro dmi.chassis.version: CSE-216BA-R920LPB dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnWBS:pnF224A-DE5:pvr3.0:rvnSupermicro:rnX9DRH-iF:rvr1.02:cvnSupermicro:ct23:cvrCSE-216BA-R920LPB: dmi.product.name: F224A-DE5 dmi.product.version: 3.0 dmi.sys.vendor: WBS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1355010] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1355010/+attachment/4174541/+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.launchpad.net/bugs/1355010 Title: ernel panic - not syncing: Attempted to kill init! exitcode=0x0100 Status in “linux” package in Ubuntu: Confirmed Bug description: We are trying to provide Ubuntu desktop (ubuntu-14.04.1-desktop-amd64.iso) to our labs for studs, which just wanna give it a try. Unfortunately it doesn't work: If it tries to exec the final step (e.g. run-init /root /sbin/init textonly toram /root/dev/console 2>&1) it panics: [ 320.076015] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 320.076015] [ 320.085145] CPU: 25 PID: 1 Comm: run-init Not tainted 3.13.0-32-generic #57-Ubuntu [ 320.092709] Hardware name: WBS F224A-DE5/X9DRH-iF, BIOS 3.0b 04/28/2014 [ 320.099315] 883fce017380 881fd31cde78 8171bcb4 81a4e5e8 [ 320.106792] 881fd31cdef0 81714eb5 0010 881fd31cdf00 [ 320.114271] 881fd31cdea0 81f239e0 0100 883fd2d60398 [ 320.121750] Call Trace: [ 320.124215] [] dump_stack+0x45/0x56 [ 320.129360] [] panic+0xc8/0x1d7 [ 320.134158] [] do_exit+0xa41/0xa50 [ 320.139213] [] ? syscall_trace_enter+0x145/0x250 [ 320.145474] [] SyS_exit+0x17/0x20 [ 320.150442] [] tracesys+0xe1/0xe6 I've no clue, what the problem could be. Already tried to append kernel params 'selinux=0 apparmor=0 enforcig=0' but without success :( The /root fs seems to be properly populated (overlayfs). Any hints? --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 BootDmesg: (Nothing has been logged yet.) CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperVersion: 1.340 DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: WBS F224A-DE5 Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/vmlinuz root=/dev/nfs netboot=nfs nfsroot=141.44.24.61:/data/mnt/hostname-14.04.1-desktop-amd64 boot=casper locale=de_DE.UTF-8 pw=$6$7CPMoOcQ$n3dtobqEnQrvJwQUKI/CoowOFI9AyUyf9I1eGY0.WK0s.PeuYpnQcVcsxt/6gN8ksJ7U2wSgAr0yavpDv4CH.0 textonly console=ttyS1,115200 debug selinux=0 apparmor=0 enforcing=0 break=init toram initrd=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/initrd.lz BOOTIF=01-68-05-ca-0a-49-be ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Tags: trusty UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0b dmi.board.asset.tag: 0672042101108 dmi.board.name: X9DRH-iF dmi.board.vendor: Supermicro dmi.board.version: 1.02 dmi.chassis.asset.tag: 0672042071494 dmi.chassis.type: 23 dmi.chassis.vendor: Supermicro dmi.chassis.version: CSE-216BA-R920LPB dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnWBS:pnF224A-DE5:pvr3.0:rvnSupermicro:rnX9DRH-iF:rvr1.02:cvnSupermicro:ct23:cvrCSE-216BA-R920LPB: dmi.product.name: F224A-DE5 dmi.product.version: 3.0 dmi.sys.vendor: WBS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1355010] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1355010/+attachment/4174540/+files/IwConfig.txt -- 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/1355010 Title: ernel panic - not syncing: Attempted to kill init! exitcode=0x0100 Status in “linux” package in Ubuntu: Confirmed Bug description: We are trying to provide Ubuntu desktop (ubuntu-14.04.1-desktop-amd64.iso) to our labs for studs, which just wanna give it a try. Unfortunately it doesn't work: If it tries to exec the final step (e.g. run-init /root /sbin/init textonly toram /root/dev/console 2>&1) it panics: [ 320.076015] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 320.076015] [ 320.085145] CPU: 25 PID: 1 Comm: run-init Not tainted 3.13.0-32-generic #57-Ubuntu [ 320.092709] Hardware name: WBS F224A-DE5/X9DRH-iF, BIOS 3.0b 04/28/2014 [ 320.099315] 883fce017380 881fd31cde78 8171bcb4 81a4e5e8 [ 320.106792] 881fd31cdef0 81714eb5 0010 881fd31cdf00 [ 320.114271] 881fd31cdea0 81f239e0 0100 883fd2d60398 [ 320.121750] Call Trace: [ 320.124215] [] dump_stack+0x45/0x56 [ 320.129360] [] panic+0xc8/0x1d7 [ 320.134158] [] do_exit+0xa41/0xa50 [ 320.139213] [] ? syscall_trace_enter+0x145/0x250 [ 320.145474] [] SyS_exit+0x17/0x20 [ 320.150442] [] tracesys+0xe1/0xe6 I've no clue, what the problem could be. Already tried to append kernel params 'selinux=0 apparmor=0 enforcig=0' but without success :( The /root fs seems to be properly populated (overlayfs). Any hints? --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 BootDmesg: (Nothing has been logged yet.) CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperVersion: 1.340 DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: WBS F224A-DE5 Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/vmlinuz root=/dev/nfs netboot=nfs nfsroot=141.44.24.61:/data/mnt/hostname-14.04.1-desktop-amd64 boot=casper locale=de_DE.UTF-8 pw=$6$7CPMoOcQ$n3dtobqEnQrvJwQUKI/CoowOFI9AyUyf9I1eGY0.WK0s.PeuYpnQcVcsxt/6gN8ksJ7U2wSgAr0yavpDv4CH.0 textonly console=ttyS1,115200 debug selinux=0 apparmor=0 enforcing=0 break=init toram initrd=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/initrd.lz BOOTIF=01-68-05-ca-0a-49-be ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Tags: trusty UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0b dmi.board.asset.tag: 0672042101108 dmi.board.name: X9DRH-iF dmi.board.vendor: Supermicro dmi.board.version: 1.02 dmi.chassis.asset.tag: 0672042071494 dmi.chassis.type: 23 dmi.chassis.vendor: Supermicro dmi.chassis.version: CSE-216BA-R920LPB dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnWBS:pnF224A-DE5:pvr3.0:rvnSupermicro:rnX9DRH-iF:rvr1.02:cvnSupermicro:ct23:cvrCSE-216BA-R920LPB: dmi.product.name: F224A-DE5 dmi.product.version: 3.0 dmi.sys.vendor: WBS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1355010] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1355010/+attachment/4174545/+files/ProcModules.txt -- 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/1355010 Title: ernel panic - not syncing: Attempted to kill init! exitcode=0x0100 Status in “linux” package in Ubuntu: Confirmed Bug description: We are trying to provide Ubuntu desktop (ubuntu-14.04.1-desktop-amd64.iso) to our labs for studs, which just wanna give it a try. Unfortunately it doesn't work: If it tries to exec the final step (e.g. run-init /root /sbin/init textonly toram /root/dev/console 2>&1) it panics: [ 320.076015] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 320.076015] [ 320.085145] CPU: 25 PID: 1 Comm: run-init Not tainted 3.13.0-32-generic #57-Ubuntu [ 320.092709] Hardware name: WBS F224A-DE5/X9DRH-iF, BIOS 3.0b 04/28/2014 [ 320.099315] 883fce017380 881fd31cde78 8171bcb4 81a4e5e8 [ 320.106792] 881fd31cdef0 81714eb5 0010 881fd31cdf00 [ 320.114271] 881fd31cdea0 81f239e0 0100 883fd2d60398 [ 320.121750] Call Trace: [ 320.124215] [] dump_stack+0x45/0x56 [ 320.129360] [] panic+0xc8/0x1d7 [ 320.134158] [] do_exit+0xa41/0xa50 [ 320.139213] [] ? syscall_trace_enter+0x145/0x250 [ 320.145474] [] SyS_exit+0x17/0x20 [ 320.150442] [] tracesys+0xe1/0xe6 I've no clue, what the problem could be. Already tried to append kernel params 'selinux=0 apparmor=0 enforcig=0' but without success :( The /root fs seems to be properly populated (overlayfs). Any hints? --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 BootDmesg: (Nothing has been logged yet.) CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperVersion: 1.340 DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: WBS F224A-DE5 Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/vmlinuz root=/dev/nfs netboot=nfs nfsroot=141.44.24.61:/data/mnt/hostname-14.04.1-desktop-amd64 boot=casper locale=de_DE.UTF-8 pw=$6$7CPMoOcQ$n3dtobqEnQrvJwQUKI/CoowOFI9AyUyf9I1eGY0.WK0s.PeuYpnQcVcsxt/6gN8ksJ7U2wSgAr0yavpDv4CH.0 textonly console=ttyS1,115200 debug selinux=0 apparmor=0 enforcing=0 break=init toram initrd=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/initrd.lz BOOTIF=01-68-05-ca-0a-49-be ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Tags: trusty UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0b dmi.board.asset.tag: 0672042101108 dmi.board.name: X9DRH-iF dmi.board.vendor: Supermicro dmi.board.version: 1.02 dmi.chassis.asset.tag: 0672042071494 dmi.chassis.type: 23 dmi.chassis.vendor: Supermicro dmi.chassis.version: CSE-216BA-R920LPB dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnWBS:pnF224A-DE5:pvr3.0:rvnSupermicro:rnX9DRH-iF:rvr1.02:cvnSupermicro:ct23:cvrCSE-216BA-R920LPB: dmi.product.name: F224A-DE5 dmi.product.version: 3.0 dmi.sys.vendor: WBS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1355010] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1355010/+attachment/4174542/+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.launchpad.net/bugs/1355010 Title: ernel panic - not syncing: Attempted to kill init! exitcode=0x0100 Status in “linux” package in Ubuntu: Confirmed Bug description: We are trying to provide Ubuntu desktop (ubuntu-14.04.1-desktop-amd64.iso) to our labs for studs, which just wanna give it a try. Unfortunately it doesn't work: If it tries to exec the final step (e.g. run-init /root /sbin/init textonly toram /root/dev/console 2>&1) it panics: [ 320.076015] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 320.076015] [ 320.085145] CPU: 25 PID: 1 Comm: run-init Not tainted 3.13.0-32-generic #57-Ubuntu [ 320.092709] Hardware name: WBS F224A-DE5/X9DRH-iF, BIOS 3.0b 04/28/2014 [ 320.099315] 883fce017380 881fd31cde78 8171bcb4 81a4e5e8 [ 320.106792] 881fd31cdef0 81714eb5 0010 881fd31cdf00 [ 320.114271] 881fd31cdea0 81f239e0 0100 883fd2d60398 [ 320.121750] Call Trace: [ 320.124215] [] dump_stack+0x45/0x56 [ 320.129360] [] panic+0xc8/0x1d7 [ 320.134158] [] do_exit+0xa41/0xa50 [ 320.139213] [] ? syscall_trace_enter+0x145/0x250 [ 320.145474] [] SyS_exit+0x17/0x20 [ 320.150442] [] tracesys+0xe1/0xe6 I've no clue, what the problem could be. Already tried to append kernel params 'selinux=0 apparmor=0 enforcig=0' but without success :( The /root fs seems to be properly populated (overlayfs). Any hints? --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 BootDmesg: (Nothing has been logged yet.) CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperVersion: 1.340 DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: WBS F224A-DE5 Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/vmlinuz root=/dev/nfs netboot=nfs nfsroot=141.44.24.61:/data/mnt/hostname-14.04.1-desktop-amd64 boot=casper locale=de_DE.UTF-8 pw=$6$7CPMoOcQ$n3dtobqEnQrvJwQUKI/CoowOFI9AyUyf9I1eGY0.WK0s.PeuYpnQcVcsxt/6gN8ksJ7U2wSgAr0yavpDv4CH.0 textonly console=ttyS1,115200 debug selinux=0 apparmor=0 enforcing=0 break=init toram initrd=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/initrd.lz BOOTIF=01-68-05-ca-0a-49-be ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Tags: trusty UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0b dmi.board.asset.tag: 0672042101108 dmi.board.name: X9DRH-iF dmi.board.vendor: Supermicro dmi.board.version: 1.02 dmi.chassis.asset.tag: 0672042071494 dmi.chassis.type: 23 dmi.chassis.vendor: Supermicro dmi.chassis.version: CSE-216BA-R920LPB dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnWBS:pnF224A-DE5:pvr3.0:rvnSupermicro:rnX9DRH-iF:rvr1.02:cvnSupermicro:ct23:cvrCSE-216BA-R920LPB: dmi.product.name: F224A-DE5 dmi.product.version: 3.0 dmi.sys.vendor: WBS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1355010] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1355010/+attachment/4174546/+files/UdevDb.txt -- 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/1355010 Title: ernel panic - not syncing: Attempted to kill init! exitcode=0x0100 Status in “linux” package in Ubuntu: Confirmed Bug description: We are trying to provide Ubuntu desktop (ubuntu-14.04.1-desktop-amd64.iso) to our labs for studs, which just wanna give it a try. Unfortunately it doesn't work: If it tries to exec the final step (e.g. run-init /root /sbin/init textonly toram /root/dev/console 2>&1) it panics: [ 320.076015] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 320.076015] [ 320.085145] CPU: 25 PID: 1 Comm: run-init Not tainted 3.13.0-32-generic #57-Ubuntu [ 320.092709] Hardware name: WBS F224A-DE5/X9DRH-iF, BIOS 3.0b 04/28/2014 [ 320.099315] 883fce017380 881fd31cde78 8171bcb4 81a4e5e8 [ 320.106792] 881fd31cdef0 81714eb5 0010 881fd31cdf00 [ 320.114271] 881fd31cdea0 81f239e0 0100 883fd2d60398 [ 320.121750] Call Trace: [ 320.124215] [] dump_stack+0x45/0x56 [ 320.129360] [] panic+0xc8/0x1d7 [ 320.134158] [] do_exit+0xa41/0xa50 [ 320.139213] [] ? syscall_trace_enter+0x145/0x250 [ 320.145474] [] SyS_exit+0x17/0x20 [ 320.150442] [] tracesys+0xe1/0xe6 I've no clue, what the problem could be. Already tried to append kernel params 'selinux=0 apparmor=0 enforcig=0' but without success :( The /root fs seems to be properly populated (overlayfs). Any hints? --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 BootDmesg: (Nothing has been logged yet.) CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperVersion: 1.340 DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: WBS F224A-DE5 Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/vmlinuz root=/dev/nfs netboot=nfs nfsroot=141.44.24.61:/data/mnt/hostname-14.04.1-desktop-amd64 boot=casper locale=de_DE.UTF-8 pw=$6$7CPMoOcQ$n3dtobqEnQrvJwQUKI/CoowOFI9AyUyf9I1eGY0.WK0s.PeuYpnQcVcsxt/6gN8ksJ7U2wSgAr0yavpDv4CH.0 textonly console=ttyS1,115200 debug selinux=0 apparmor=0 enforcing=0 break=init toram initrd=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/initrd.lz BOOTIF=01-68-05-ca-0a-49-be ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Tags: trusty UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0b dmi.board.asset.tag: 0672042101108 dmi.board.name: X9DRH-iF dmi.board.vendor: Supermicro dmi.board.version: 1.02 dmi.chassis.asset.tag: 0672042071494 dmi.chassis.type: 23 dmi.chassis.vendor: Supermicro dmi.chassis.version: CSE-216BA-R920LPB dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnWBS:pnF224A-DE5:pvr3.0:rvnSupermicro:rnX9DRH-iF:rvr1.02:cvnSupermicro:ct23:cvrCSE-216BA-R920LPB: dmi.product.name: F224A-DE5 dmi.product.version: 3.0 dmi.sys.vendor: WBS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1355010] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1355010/+attachment/4174543/+files/ProcCpuinfo.txt -- 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/1355010 Title: ernel panic - not syncing: Attempted to kill init! exitcode=0x0100 Status in “linux” package in Ubuntu: Confirmed Bug description: We are trying to provide Ubuntu desktop (ubuntu-14.04.1-desktop-amd64.iso) to our labs for studs, which just wanna give it a try. Unfortunately it doesn't work: If it tries to exec the final step (e.g. run-init /root /sbin/init textonly toram /root/dev/console 2>&1) it panics: [ 320.076015] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 320.076015] [ 320.085145] CPU: 25 PID: 1 Comm: run-init Not tainted 3.13.0-32-generic #57-Ubuntu [ 320.092709] Hardware name: WBS F224A-DE5/X9DRH-iF, BIOS 3.0b 04/28/2014 [ 320.099315] 883fce017380 881fd31cde78 8171bcb4 81a4e5e8 [ 320.106792] 881fd31cdef0 81714eb5 0010 881fd31cdf00 [ 320.114271] 881fd31cdea0 81f239e0 0100 883fd2d60398 [ 320.121750] Call Trace: [ 320.124215] [] dump_stack+0x45/0x56 [ 320.129360] [] panic+0xc8/0x1d7 [ 320.134158] [] do_exit+0xa41/0xa50 [ 320.139213] [] ? syscall_trace_enter+0x145/0x250 [ 320.145474] [] SyS_exit+0x17/0x20 [ 320.150442] [] tracesys+0xe1/0xe6 I've no clue, what the problem could be. Already tried to append kernel params 'selinux=0 apparmor=0 enforcig=0' but without success :( The /root fs seems to be properly populated (overlayfs). Any hints? --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 BootDmesg: (Nothing has been logged yet.) CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperVersion: 1.340 DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: WBS F224A-DE5 Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/vmlinuz root=/dev/nfs netboot=nfs nfsroot=141.44.24.61:/data/mnt/hostname-14.04.1-desktop-amd64 boot=casper locale=de_DE.UTF-8 pw=$6$7CPMoOcQ$n3dtobqEnQrvJwQUKI/CoowOFI9AyUyf9I1eGY0.WK0s.PeuYpnQcVcsxt/6gN8ksJ7U2wSgAr0yavpDv4CH.0 textonly console=ttyS1,115200 debug selinux=0 apparmor=0 enforcing=0 break=init toram initrd=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/initrd.lz BOOTIF=01-68-05-ca-0a-49-be ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Tags: trusty UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0b dmi.board.asset.tag: 0672042101108 dmi.board.name: X9DRH-iF dmi.board.vendor: Supermicro dmi.board.version: 1.02 dmi.chassis.asset.tag: 0672042071494 dmi.chassis.type: 23 dmi.chassis.vendor: Supermicro dmi.chassis.version: CSE-216BA-R920LPB dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnWBS:pnF224A-DE5:pvr3.0:rvnSupermicro:rnX9DRH-iF:rvr1.02:cvnSupermicro:ct23:cvrCSE-216BA-R920LPB: dmi.product.name: F224A-DE5 dmi.product.version: 3.0 dmi.sys.vendor: WBS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1355010] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1355010/+attachment/4174539/+files/CurrentDmesg.txt -- 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/1355010 Title: ernel panic - not syncing: Attempted to kill init! exitcode=0x0100 Status in “linux” package in Ubuntu: Confirmed Bug description: We are trying to provide Ubuntu desktop (ubuntu-14.04.1-desktop-amd64.iso) to our labs for studs, which just wanna give it a try. Unfortunately it doesn't work: If it tries to exec the final step (e.g. run-init /root /sbin/init textonly toram /root/dev/console 2>&1) it panics: [ 320.076015] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 320.076015] [ 320.085145] CPU: 25 PID: 1 Comm: run-init Not tainted 3.13.0-32-generic #57-Ubuntu [ 320.092709] Hardware name: WBS F224A-DE5/X9DRH-iF, BIOS 3.0b 04/28/2014 [ 320.099315] 883fce017380 881fd31cde78 8171bcb4 81a4e5e8 [ 320.106792] 881fd31cdef0 81714eb5 0010 881fd31cdf00 [ 320.114271] 881fd31cdea0 81f239e0 0100 883fd2d60398 [ 320.121750] Call Trace: [ 320.124215] [] dump_stack+0x45/0x56 [ 320.129360] [] panic+0xc8/0x1d7 [ 320.134158] [] do_exit+0xa41/0xa50 [ 320.139213] [] ? syscall_trace_enter+0x145/0x250 [ 320.145474] [] SyS_exit+0x17/0x20 [ 320.150442] [] tracesys+0xe1/0xe6 I've no clue, what the problem could be. Already tried to append kernel params 'selinux=0 apparmor=0 enforcig=0' but without success :( The /root fs seems to be properly populated (overlayfs). Any hints? --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 BootDmesg: (Nothing has been logged yet.) CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperVersion: 1.340 DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: WBS F224A-DE5 Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/vmlinuz root=/dev/nfs netboot=nfs nfsroot=141.44.24.61:/data/mnt/hostname-14.04.1-desktop-amd64 boot=casper locale=de_DE.UTF-8 pw=$6$7CPMoOcQ$n3dtobqEnQrvJwQUKI/CoowOFI9AyUyf9I1eGY0.WK0s.PeuYpnQcVcsxt/6gN8ksJ7U2wSgAr0yavpDv4CH.0 textonly console=ttyS1,115200 debug selinux=0 apparmor=0 enforcing=0 break=init toram initrd=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/initrd.lz BOOTIF=01-68-05-ca-0a-49-be ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Tags: trusty UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0b dmi.board.asset.tag: 0672042101108 dmi.board.name: X9DRH-iF dmi.board.vendor: Supermicro dmi.board.version: 1.02 dmi.chassis.asset.tag: 0672042071494 dmi.chassis.type: 23 dmi.chassis.vendor: Supermicro dmi.chassis.version: CSE-216BA-R920LPB dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnWBS:pnF224A-DE5:pvr3.0:rvnSupermicro:rnX9DRH-iF:rvr1.02:cvnSupermicro:ct23:cvrCSE-216BA-R920LPB: dmi.product.name: F224A-DE5 dmi.product.version: 3.0 dmi.sys.vendor: WBS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1355010] Re: ernel panic - not syncing: Attempted to kill init! exitcode=0x00000100
To get the info above, I added break=init and did manually: chroot /root /bin/bash # created /etc/resolv.conf apt-get install python-apport apport-collect 1355010 -- 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/1355010 Title: ernel panic - not syncing: Attempted to kill init! exitcode=0x0100 Status in “linux” package in Ubuntu: Confirmed Bug description: We are trying to provide Ubuntu desktop (ubuntu-14.04.1-desktop-amd64.iso) to our labs for studs, which just wanna give it a try. Unfortunately it doesn't work: If it tries to exec the final step (e.g. run-init /root /sbin/init textonly toram /root/dev/console 2>&1) it panics: [ 320.076015] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0100 [ 320.076015] [ 320.085145] CPU: 25 PID: 1 Comm: run-init Not tainted 3.13.0-32-generic #57-Ubuntu [ 320.092709] Hardware name: WBS F224A-DE5/X9DRH-iF, BIOS 3.0b 04/28/2014 [ 320.099315] 883fce017380 881fd31cde78 8171bcb4 81a4e5e8 [ 320.106792] 881fd31cdef0 81714eb5 0010 881fd31cdf00 [ 320.114271] 881fd31cdea0 81f239e0 0100 883fd2d60398 [ 320.121750] Call Trace: [ 320.124215] [] dump_stack+0x45/0x56 [ 320.129360] [] panic+0xc8/0x1d7 [ 320.134158] [] do_exit+0xa41/0xa50 [ 320.139213] [] ? syscall_trace_enter+0x145/0x250 [ 320.145474] [] SyS_exit+0x17/0x20 [ 320.150442] [] tracesys+0xe1/0xe6 I've no clue, what the problem could be. Already tried to append kernel params 'selinux=0 apparmor=0 enforcig=0' but without success :( The /root fs seems to be properly populated (overlayfs). Any hints? --- ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 BootDmesg: (Nothing has been logged yet.) CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CasperVersion: 1.340 DistroRelease: Ubuntu 14.04 LiveMediaBuild: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 0557:2221 ATEN International Co., Ltd Winbond Hermon Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: WBS F224A-DE5 Package: linux (not installed) ProcEnviron: TERM=linux PATH=(custom, no user) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/vmlinuz root=/dev/nfs netboot=nfs nfsroot=141.44.24.61:/data/mnt/hostname-14.04.1-desktop-amd64 boot=casper locale=de_DE.UTF-8 pw=$6$7CPMoOcQ$n3dtobqEnQrvJwQUKI/CoowOFI9AyUyf9I1eGY0.WK0s.PeuYpnQcVcsxt/6gN8ksJ7U2wSgAr0yavpDv4CH.0 textonly console=ttyS1,115200 debug selinux=0 apparmor=0 enforcing=0 break=init toram initrd=http://141.44.24.61/boot/hostname-14.04.1-desktop-amd64/initrd.lz BOOTIF=01-68-05-ca-0a-49-be ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.13.0-32-generic N/A linux-backports-modules-3.13.0-32-generic N/A linux-firmware 1.127.5 RfKill: Tags: trusty UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' Uname: Linux 3.13.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: WifiSyslog: _MarkForUpload: True dmi.bios.date: 04/28/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.0b dmi.board.asset.tag: 0672042101108 dmi.board.name: X9DRH-iF dmi.board.vendor: Supermicro dmi.board.version: 1.02 dmi.chassis.asset.tag: 0672042071494 dmi.chassis.type: 23 dmi.chassis.vendor: Supermicro dmi.chassis.version: CSE-216BA-R920LPB dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.0b:bd04/28/2014:svnWBS:pnF224A-DE5:pvr3.0:rvnSupermicro:rnX9DRH-iF:rvr1.02:cvnSupermicro:ct23:cvrCSE-216BA-R920LPB: dmi.product.name: F224A-DE5 dmi.product.version: 3.0 dmi.sys.vendor: WBS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1355010/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1840854] Re: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs
We use 'Linux kino6 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux' (Ubuntu 18.04.3 LTS) and see all the time 'hw csum failure's: [ +28.297139] kino6_0: hw csum failure [ +0.003607] CPU: 12 PID: 0 Comm: swapper/12 Tainted: P O 4.15.0-58-generic #64-Ubuntu [ +0.03] Hardware name: GIGABYTE G291-281-00/MG51-G21-00, BIOS R06 11/19/2019 [ +0.01] Call Trace: [ +0.02] [ +0.11] dump_stack+0x63/0x8b [ +0.08] netdev_rx_csum_fault+0x38/0x40 [ +0.03] __skb_checksum_complete+0xbc/0xd0 [ +0.05] nf_ip_checksum+0xc3/0xf0 [ +0.18] tcp_error+0x162/0x1c0 [nf_conntrack] [ +0.06] ? ttwu_do_wakeup+0x1e/0x140 [ +0.11] nf_conntrack_in+0x14f/0x500 [nf_conntrack] [ +0.07] ? csum_partial_ext+0x9/0x10 [ +0.07] ? __skb_checksum+0x6b/0x300 [ +0.06] ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4] [ +0.05] nf_hook_slow+0x48/0xc0 [ +0.04] ? skb_send_sock+0x50/0x50 [ +0.05] ip_rcv+0x2fa/0x360 [ +0.03] ? inet_del_offload+0x40/0x40 [ +0.04] __netif_receive_skb_core+0x432/0xb40 [ +0.03] ? update_curr+0xf2/0x1d0 [ +0.04] ? tcp4_gro_receive+0x137/0x1a0 [ +0.03] __netif_receive_skb+0x18/0x60 [ +0.03] ? __netif_receive_skb+0x18/0x60 [ +0.03] netif_receive_skb_internal+0x45/0xe0 [ +0.04] napi_gro_receive+0xc5/0xf0 [ +0.36] mlx5e_handle_rx_cqe_mpwrq+0x465/0x860 [mlx5_core] [ +0.28] mlx5e_poll_rx_cq+0xd1/0x8b0 [mlx5_core] [ +0.25] mlx5e_napi_poll+0x9d/0x290 [mlx5_core] [ +0.04] net_rx_action+0x140/0x3a0 [ +0.05] __do_softirq+0xe4/0x2d4 [ +0.06] irq_exit+0xc5/0xd0 [ +0.03] do_IRQ+0x8a/0xe0 [ +0.03] common_interrupt+0x8c/0x8c [ +0.02] [ +0.05] RIP: 0010:cpuidle_enter_state+0xa7/0x2f0 [ +0.02] RSP: 0018:ad7a00283e68 EFLAGS: 0246 ORIG_RAX: ffdd [ +0.04] RAX: 89f13fd22840 RBX: 02273da74e91 RCX: 001f [ +0.02] RDX: 02273da74e91 RSI: feba65558937 RDI: [ +0.02] RBP: ad7a00283ea8 R08: 0004 R09: 00022080 [ +0.01] R10: ad7a00283e38 R11: 07e0dcda6658 R12: cd5a00503298 [ +0.02] R13: 0003 R14: b3f72e78 R15: [ +0.04] ? cpuidle_enter_state+0x97/0x2f0 [ +0.03] cpuidle_enter+0x17/0x20 [ +0.05] call_cpuidle+0x23/0x40 [ +0.04] do_idle+0x18c/0x1f0 [ +0.04] cpu_startup_entry+0x73/0x80 [ +0.05] start_secondary+0x1ab/0x200 [ +0.05] secondary_startup_64+0xa5/0xb0 -- 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/1840854 Title: mlx5_core reports hardware checksum error for padded packets on Mellanox NICs Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: BugLink: https://bugs.launchpad.net/bugs/1840854 [Impact] On machines equipped with Mellanox NIC's, in this particular case, Mellanox 5 series NICs using the mlx5_core driver, after installing 4.15.0-56 or later there is the following kernel splat: bond0: hw csum failure CPU: 63 PID: 2473 Comm: in:imklog Tainted: P OE 4.15.0-58-generic #64~16.04.1-Ubuntu Call Trace: dump_stack+0x63/0x8b netdev_rx_csum_fault+0x38/0x40 __skb_checksum_complete+0xc0/0xd0 nf_ip_checksum+0xca/0xf0 tcp_error+0xe0/0x1a0 [nf_conntrack] ? tcp_v4_rcv+0x7c6/0xa70 nf_conntrack_in+0xde/0x520 [nf_conntrack] ipv4_conntrack_in+0x1c/0x20 [nf_conntrack_ipv4] nf_hook_slow+0x48/0xd0 ? skb_send_sock+0x50/0x50 ip_rcv+0x30f/0x370 ? inet_del_offload+0x40/0x40 __netif_receive_skb_core+0x879/0xba0 ? tcp4_gro_receive+0x117/0x1b0 __netif_receive_skb+0x18/0x60 ? __netif_receive_skb+0x18/0x60 netif_receive_skb_internal+0x45/0xf0 napi_gro_receive+0xd0/0xf0 mlx5e_handle_rx_cqe_mpwrq+0x4a1/0x8a0 [mlx5_core] mlx5e_poll_rx_cq+0xc3/0x880 [mlx5_core] mlx5e_napi_poll+0x9b/0x280 [mlx5_core] net_rx_action+0x265/0x3b0 __do_softirq+0xf5/0x2a8 irq_exit+0xca/0xd0 do_IRQ+0x57/0xe0 common_interrupt+0x8c/0x8c In 4.15.0-56, a commit was added from upstream -stable that introduced an optimisation for checksumming packets which have had zero bytes padded to the end of the packet. commit 88078d98d1bb085d72af8437707279e203524fa5 Author: Eric Dumazet Date: Wed Apr 18 11:43:15 2018 -0700 subject: net: pskb_trim_rcsum() and CHECKSUM_COMPLETE are friends You can read it here: https://github.com/torvalds/linux/commit/88078d98d1bb085d72af8437707279e203524fa5 It was discussed in this bugzilla link: https://bugzilla.kernel.org/show_bug.cgi?id=201849 This commit causes problems with a number of NIC devices, including Mellanox. This is best described by the maintainer, Dimitris Michailidis: > > > MLNX devices have an issue with packets that
[Kernel-packages] [Bug 1926845] [NEW] Unable to store nvidia-settings
Public bug reported: Since focal a casual unprivileged user cannot save the current X Server Display Configuration, no matter which location is used. I.e. even for e.g. /tmp/xorg.conf or /home/$LOGNAME/xorg.conf the user gets asked for the root password. This really stupid '"AUTHENTICATING FOR com.ubuntu.screen-resolution- extra.root-display" "Authenticating as: root"' bug needs to be fixed. An unprivileged user should be able to store the config wherever he wants to, as long as he has write permission for the related file/directory. ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Package changed: nvidia-settings-updates (Ubuntu) => nvidia-settings (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1926845 Title: Unable to store nvidia-settings Status in nvidia-settings package in Ubuntu: New Bug description: Since focal a casual unprivileged user cannot save the current X Server Display Configuration, no matter which location is used. I.e. even for e.g. /tmp/xorg.conf or /home/$LOGNAME/xorg.conf the user gets asked for the root password. This really stupid '"AUTHENTICATING FOR com.ubuntu.screen-resolution- extra.root-display" "Authenticating as: root"' bug needs to be fixed. An unprivileged user should be able to store the config wherever he wants to, as long as he has write permission for the related file/directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1926845/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2088282] Re: kernel-nfs-server does not work at all
FWIW: Because on jammy (on my desktop) nfs-server works, I downloaded
and replaced/installed the related nfs-packages on noble
(libldap-2.5-0_2.5.18+dfsg-0ubuntu0.22.04.2_amd64.deb
libnfsidmap1_1%3a2.6.1-1ubuntu1.2_amd64.deb nfs-
common_1%3a2.6.1-1ubuntu1.2_amd64.deb nfs-kernel-
server_1%3a2.6.1-1ubuntu1.2_amd64.deb rpcbind_1.2.6-2build1_amd64.deb) -
but no luck. Same problem. So it really seems to be a kernel problem
(unless I missed something).
Also tried the 6.8.0-31 kernel (the oldest on I can get via Ubuntu
repos), but no luck either.
--
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/2088282
Title:
kernel-nfs-server does not work at all
Status in linux package in Ubuntu:
New
Bug description:
I'm trying to setup a NFSv4 server on Ubuntu LTS 24.04 but it does not
work at all. The client (no matter whether Ubuntu 22.04.4 LTS, or
Solaris 11.3.x, or ...) sends a V4 Null call, the server receives the
paket on the related interface and ACKs it, but in never sends an
answer.
The server setup has been made the same way we did with our focal
server (applied the /etc/default/*nfs* to /etc/nfs.conf). Same clients
used to test the noble nfs server work fine with the focal nfs server.
This and the paket captures suggests that this must be nfsd/kernel
problem.
The setup is basically:
1) zfs create -o mountpoint=/export -p pool1/${HOST}/export
2) zfs create pool1/${HOST}/export/iks/backup
3) zfs set
sharenfs=sec=sys,secure,sync,crossmnt,no_subtree_check,root_squash,rw=@141.44.21.94/31
pool1/${HOST}/export/iks/backup
4) adjust /etc/nfs.conf if needed (basically sed -ire '/^#*vers3=/
s/^.*/vers3=n/' -e 's/^#*vers(4[^=]*)=.*/vers\1=y/' -e '/^\[nfsd\]/
a\debug=all' /etc/nfs.conf )
5) optionally restart nfs-server: systemctl restart nfs-server
The only difference wrt. to the focal instance setup is, that on focal there
is no statd and no mountd running (NFSv4 does not need them AFAIK), but haven't
found a way on noble, how to disable them (and systemd nfs-server is not smart
enough to disable them). The /etc/default/nfs-common looks like this:
```
STATDOPTS=
NEED_GSSD=no
NEED_STATD=no
NEED_IDMAPD=yes
```
and /etc/default/nfs-kernel-server
```
RPCNFSDCOUNT=32
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids --no-nfs-version 2 --no-nfs-version 3"
NEED_SVCGSSD=""
RPCSVCGSSDOPTS=""
```
Not sure how to map the NEED_* to /etc/nfs.conf, but beside this and
thread count it should be the same as the attached /etc/nfs.conf.
So it should work but does not at all, even if I set sharenfs=off and use
/etc/exports with `/export/iks/backup
141.44.21.94/31(sync,wdelay,hide,crossmnt,no_subtree_check,mountpoint,sec=sys,rw,secure,root_squash,no_all_squash)`.
exportfs always shows:
```
/export/iks/backup
141.44.21.94/31
```
and thus should work.
Last but not least I found and tried
https://ppa.launchpadcontent.net/mehmetbasaran/linux-6.8.0-45.45-nfs-
patch/ubuntu but unfortunately it behaves like the linux-
image-6.8.0-48-generic - no answer to V4 NULL calls.
So are there any kernels in Ubuntu 24.04 (noble), where the nfsd actually
works?
And optionally: Is there a way to permanently turn off statd and mountd
daemons?
--
version.log: Ubuntu 6.8.0-46.2-generic-nfs 6.8.12
About Ubuntu: Ubuntu 22.04.4 LTS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2088282/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2088282] [NEW] kernel-nfs-server does not work at all
Public bug reported:
I'm trying to setup a NFSv4 server on Ubuntu LTS 24.04 but it does not
work at all. The client (no matter whether Ubuntu 22.04.4 LTS, or
Solaris 11.3.x, or ...) sends a V4 Null call, the server receives the
paket on the related interface and ACKs it, but in never sends an
answer.
The server setup has been made the same way we did with our focal server
(applied the /etc/default/*nfs* to /etc/nfs.conf). Same clients used to
test the noble nfs server work fine with the focal nfs server. This and
the paket captures suggests that this must be nfsd/kernel problem.
The setup is basically:
1) zfs create -o mountpoint=/export -p pool1/${HOST}/export
2) zfs create pool1/${HOST}/export/iks/backup
3) zfs set
sharenfs=sec=sys,secure,sync,crossmnt,no_subtree_check,root_squash,rw=@141.44.21.94/31
pool1/${HOST}/export/iks/backup
4) adjust /etc/nfs.conf if needed (basically sed -ire '/^#*vers3=/
s/^.*/vers3=n/' -e 's/^#*vers(4[^=]*)=.*/vers\1=y/' -e '/^\[nfsd\]/
a\debug=all' /etc/nfs.conf )
5) optionally restart nfs-server: systemctl restart nfs-server
The only difference wrt. to the focal instance setup is, that on focal there is
no statd and no mountd running (NFSv4 does not need them AFAIK), but haven't
found a way on noble, how to disable them (and systemd nfs-server is not smart
enough to disable them). The /etc/default/nfs-common looks like this:
```
STATDOPTS=
NEED_GSSD=no
NEED_STATD=no
NEED_IDMAPD=yes
```
and /etc/default/nfs-kernel-server
```
RPCNFSDCOUNT=32
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids --no-nfs-version 2 --no-nfs-version 3"
NEED_SVCGSSD=""
RPCSVCGSSDOPTS=""
```
Not sure how to map the NEED_* to /etc/nfs.conf, but beside this and
thread count it should be the same as the attached /etc/nfs.conf.
So it should work but does not at all, even if I set sharenfs=off and use
/etc/exports with `/export/iks/backup
141.44.21.94/31(sync,wdelay,hide,crossmnt,no_subtree_check,mountpoint,sec=sys,rw,secure,root_squash,no_all_squash)`.
exportfs always shows:
```
/export/iks/backup
141.44.21.94/31
```
and thus should work.
Last but not least I found and tried
https://ppa.launchpadcontent.net/mehmetbasaran/linux-6.8.0-45.45-nfs-
patch/ubuntu but unfortunately it behaves like the linux-
image-6.8.0-48-generic - no answer to V4 NULL calls.
So are there any kernels in Ubuntu 24.04 (noble), where the nfsd actually works?
And optionally: Is there a way to permanently turn off statd and mountd daemons?
--
version.log: Ubuntu 6.8.0-46.2-generic-nfs 6.8.12
About Ubuntu: Ubuntu 22.04.4 LTS
** Affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Attachment added: "nfs.conf"
https://bugs.launchpad.net/bugs/2088282/+attachment/5837467/+files/nfs.conf
--
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/2088282
Title:
kernel-nfs-server does not work at all
Status in linux package in Ubuntu:
New
Bug description:
I'm trying to setup a NFSv4 server on Ubuntu LTS 24.04 but it does not
work at all. The client (no matter whether Ubuntu 22.04.4 LTS, or
Solaris 11.3.x, or ...) sends a V4 Null call, the server receives the
paket on the related interface and ACKs it, but in never sends an
answer.
The server setup has been made the same way we did with our focal
server (applied the /etc/default/*nfs* to /etc/nfs.conf). Same clients
used to test the noble nfs server work fine with the focal nfs server.
This and the paket captures suggests that this must be nfsd/kernel
problem.
The setup is basically:
1) zfs create -o mountpoint=/export -p pool1/${HOST}/export
2) zfs create pool1/${HOST}/export/iks/backup
3) zfs set
sharenfs=sec=sys,secure,sync,crossmnt,no_subtree_check,root_squash,rw=@141.44.21.94/31
pool1/${HOST}/export/iks/backup
4) adjust /etc/nfs.conf if needed (basically sed -ire '/^#*vers3=/
s/^.*/vers3=n/' -e 's/^#*vers(4[^=]*)=.*/vers\1=y/' -e '/^\[nfsd\]/
a\debug=all' /etc/nfs.conf )
5) optionally restart nfs-server: systemctl restart nfs-server
The only difference wrt. to the focal instance setup is, that on focal there
is no statd and no mountd running (NFSv4 does not need them AFAIK), but haven't
found a way on noble, how to disable them (and systemd nfs-server is not smart
enough to disable them). The /etc/default/nfs-common looks like this:
```
STATDOPTS=
NEED_GSSD=no
NEED_STATD=no
NEED_IDMAPD=yes
```
and /etc/default/nfs-kernel-server
```
RPCNFSDCOUNT=32
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids --no-nfs-version 2 --no-nfs-version 3"
NEED_SVCGSSD=""
RPCSVCGSSDOPTS=""
```
Not sure how to map the NEED_* to /etc/nfs.conf, but beside this and
thread count it should be the same as the attached /etc/nfs.conf.
So it should work but does not at all, even if I set sharenfs=off and use
/etc/exports with `/export/iks/backup
141.44.21.94/31(sync,wdelay,hi
[Kernel-packages] [Bug 2088282] Re: kernel-nfs-server does not work at all
s/mountd/gssd/ ;-)
--
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/2088282
Title:
kernel-nfs-server does not work at all
Status in linux package in Ubuntu:
New
Bug description:
I'm trying to setup a NFSv4 server on Ubuntu LTS 24.04 but it does not
work at all. The client (no matter whether Ubuntu 22.04.4 LTS, or
Solaris 11.3.x, or ...) sends a V4 Null call, the server receives the
paket on the related interface and ACKs it, but in never sends an
answer.
The server setup has been made the same way we did with our focal
server (applied the /etc/default/*nfs* to /etc/nfs.conf). Same clients
used to test the noble nfs server work fine with the focal nfs server.
This and the paket captures suggests that this must be nfsd/kernel
problem.
The setup is basically:
1) zfs create -o mountpoint=/export -p pool1/${HOST}/export
2) zfs create pool1/${HOST}/export/iks/backup
3) zfs set
sharenfs=sec=sys,secure,sync,crossmnt,no_subtree_check,root_squash,rw=@141.44.21.94/31
pool1/${HOST}/export/iks/backup
4) adjust /etc/nfs.conf if needed (basically sed -ire '/^#*vers3=/
s/^.*/vers3=n/' -e 's/^#*vers(4[^=]*)=.*/vers\1=y/' -e '/^\[nfsd\]/
a\debug=all' /etc/nfs.conf )
5) optionally restart nfs-server: systemctl restart nfs-server
The only difference wrt. to the focal instance setup is, that on focal there
is no statd and no mountd running (NFSv4 does not need them AFAIK), but haven't
found a way on noble, how to disable them (and systemd nfs-server is not smart
enough to disable them). The /etc/default/nfs-common looks like this:
```
STATDOPTS=
NEED_GSSD=no
NEED_STATD=no
NEED_IDMAPD=yes
```
and /etc/default/nfs-kernel-server
```
RPCNFSDCOUNT=32
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids --no-nfs-version 2 --no-nfs-version 3"
NEED_SVCGSSD=""
RPCSVCGSSDOPTS=""
```
Not sure how to map the NEED_* to /etc/nfs.conf, but beside this and
thread count it should be the same as the attached /etc/nfs.conf.
So it should work but does not at all, even if I set sharenfs=off and use
/etc/exports with `/export/iks/backup
141.44.21.94/31(sync,wdelay,hide,crossmnt,no_subtree_check,mountpoint,sec=sys,rw,secure,root_squash,no_all_squash)`.
exportfs always shows:
```
/export/iks/backup
141.44.21.94/31
```
and thus should work.
Last but not least I found and tried
https://ppa.launchpadcontent.net/mehmetbasaran/linux-6.8.0-45.45-nfs-
patch/ubuntu but unfortunately it behaves like the linux-
image-6.8.0-48-generic - no answer to V4 NULL calls.
So are there any kernels in Ubuntu 24.04 (noble), where the nfsd actually
works?
And optionally: Is there a way to permanently turn off statd and mountd
daemons?
--
version.log: Ubuntu 6.8.0-46.2-generic-nfs 6.8.12
About Ubuntu: Ubuntu 22.04.4 LTS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2088282/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2088282] Re: kernel-nfs-server does not work at all
Wrong terminal for 'About Ubuntu'. It is of course 'Ubuntu 24.04.1 LTS'.
--
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/2088282
Title:
kernel-nfs-server does not work at all
Status in linux package in Ubuntu:
New
Bug description:
I'm trying to setup a NFSv4 server on Ubuntu LTS 24.04 but it does not
work at all. The client (no matter whether Ubuntu 22.04.4 LTS, or
Solaris 11.3.x, or ...) sends a V4 Null call, the server receives the
paket on the related interface and ACKs it, but in never sends an
answer.
The server setup has been made the same way we did with our focal
server (applied the /etc/default/*nfs* to /etc/nfs.conf). Same clients
used to test the noble nfs server work fine with the focal nfs server.
This and the paket captures suggests that this must be nfsd/kernel
problem.
The setup is basically:
1) zfs create -o mountpoint=/export -p pool1/${HOST}/export
2) zfs create pool1/${HOST}/export/iks/backup
3) zfs set
sharenfs=sec=sys,secure,sync,crossmnt,no_subtree_check,root_squash,rw=@141.44.21.94/31
pool1/${HOST}/export/iks/backup
4) adjust /etc/nfs.conf if needed (basically sed -ire '/^#*vers3=/
s/^.*/vers3=n/' -e 's/^#*vers(4[^=]*)=.*/vers\1=y/' -e '/^\[nfsd\]/
a\debug=all' /etc/nfs.conf )
5) optionally restart nfs-server: systemctl restart nfs-server
The only difference wrt. to the focal instance setup is, that on focal there
is no statd and no mountd running (NFSv4 does not need them AFAIK), but haven't
found a way on noble, how to disable them (and systemd nfs-server is not smart
enough to disable them). The /etc/default/nfs-common looks like this:
```
STATDOPTS=
NEED_GSSD=no
NEED_STATD=no
NEED_IDMAPD=yes
```
and /etc/default/nfs-kernel-server
```
RPCNFSDCOUNT=32
RPCNFSDPRIORITY=0
RPCMOUNTDOPTS="--manage-gids --no-nfs-version 2 --no-nfs-version 3"
NEED_SVCGSSD=""
RPCSVCGSSDOPTS=""
```
Not sure how to map the NEED_* to /etc/nfs.conf, but beside this and
thread count it should be the same as the attached /etc/nfs.conf.
So it should work but does not at all, even if I set sharenfs=off and use
/etc/exports with `/export/iks/backup
141.44.21.94/31(sync,wdelay,hide,crossmnt,no_subtree_check,mountpoint,sec=sys,rw,secure,root_squash,no_all_squash)`.
exportfs always shows:
```
/export/iks/backup
141.44.21.94/31
```
and thus should work.
Last but not least I found and tried
https://ppa.launchpadcontent.net/mehmetbasaran/linux-6.8.0-45.45-nfs-
patch/ubuntu but unfortunately it behaves like the linux-
image-6.8.0-48-generic - no answer to V4 NULL calls.
So are there any kernels in Ubuntu 24.04 (noble), where the nfsd actually
works?
And optionally: Is there a way to permanently turn off statd and mountd
daemons?
--
version.log: Ubuntu 6.8.0-46.2-generic-nfs 6.8.12
About Ubuntu: Ubuntu 22.04.4 LTS
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2088282/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
