[Kernel-packages] [Bug 1840945] [NEW] Concatenated lz4 initrds don't work

[Alkis Georgopoulos]

Public bug reported:

Concatenating multiple initrds works fine with gzipped initrds.
(microcode+gzip+gzip) => the kernel properly decompresses that

With lz4, it can't decompress anything after the first lz4:
(microcode+lz4+whatever) => it doesn't decompress whatever.

To reproduce:
Get vmlinuz and initrd.img from an eoan daily build and put them in a directory.
Create an lz4 (or gzip or uncompressed cpio, it doesn't matter):
# date > date.txt
# echo date.txt | cpio -oH newc | lz4 > date.img
Concatenate them:
# cat initrd.img.original date.img > initrd.img
Boot them:
# kvm -m 512 -kernel vmlinuz -initrd initrd.img -append rdinit=/bin/sh

Then inside kvm:
# ls /date.txt

The additional file doesn't exist.

`dmesg | grep -i initramfs` reports:
Trying to unpack rootfs image as initramfs...
Initramfs unpacking failed: Decoding failed

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Description changed:

  Concatenating multiple initrds works fine with gzipped initrds.
  (microcode+gzip+gzip) => the kernel properly decompresses that
  
  With lz4, it can't decompress anything after the first lz4:
  (microcode+lz4+whatever) => it doesn't decompress whatever.
  
  To reproduce:
  Get vmlinuz and initrd.img from an eoan daily build and put them in a 
directory.
  Create an lz4 (or gzip or uncompressed cpio, it doesn't matter):
+ # date > date.txt
  # echo date.txt | cpio -oH newc | lz4 > date.img
  Concatenate them:
  # cat initrd.img.original date.img > initrd.img
  Boot them:
  # kvm -m 512 -kernel vmlinuz -initrd initrd.img -append rdinit=/bin/sh
  
  Then inside kvm:
  # ls /date.txt
  
  The additional file doesn't exist.

** Description changed:

  Concatenating multiple initrds works fine with gzipped initrds.
  (microcode+gzip+gzip) => the kernel properly decompresses that
  
  With lz4, it can't decompress anything after the first lz4:
  (microcode+lz4+whatever) => it doesn't decompress whatever.
  
  To reproduce:
  Get vmlinuz and initrd.img from an eoan daily build and put them in a 
directory.
  Create an lz4 (or gzip or uncompressed cpio, it doesn't matter):
  # date > date.txt
  # echo date.txt | cpio -oH newc | lz4 > date.img
  Concatenate them:
  # cat initrd.img.original date.img > initrd.img
  Boot them:
  # kvm -m 512 -kernel vmlinuz -initrd initrd.img -append rdinit=/bin/sh
  
  Then inside kvm:
  # ls /date.txt
  
  The additional file doesn't exist.
+ 
+ `dmesg` reports:
+ Trying to unpack rootfs image as initramfs...
+ Initramfs unpacking failed: write error

** Description changed:

  Concatenating multiple initrds works fine with gzipped initrds.
  (microcode+gzip+gzip) => the kernel properly decompresses that
  
  With lz4, it can't decompress anything after the first lz4:
  (microcode+lz4+whatever) => it doesn't decompress whatever.
  
  To reproduce:
  Get vmlinuz and initrd.img from an eoan daily build and put them in a 
directory.
  Create an lz4 (or gzip or uncompressed cpio, it doesn't matter):
  # date > date.txt
  # echo date.txt | cpio -oH newc | lz4 > date.img
  Concatenate them:
  # cat initrd.img.original date.img > initrd.img
  Boot them:
  # kvm -m 512 -kernel vmlinuz -initrd initrd.img -append rdinit=/bin/sh
  
  Then inside kvm:
  # ls /date.txt
  
  The additional file doesn't exist.
  
- `dmesg` reports:
+ `dmesg | grep -i initramfs` reports:
  Trying to unpack rootfs image as initramfs...
- Initramfs unpacking failed: write error
+ Initramfs unpacking failed: Decoding failed

-- 
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/1840945

Title:
  Concatenated lz4 initrds don't work

Status in linux package in Ubuntu:
  New

Bug description:
  Concatenating multiple initrds works fine with gzipped initrds.
  (microcode+gzip+gzip) => the kernel properly decompresses that

  With lz4, it can't decompress anything after the first lz4:
  (microcode+lz4+whatever) => it doesn't decompress whatever.

  To reproduce:
  Get vmlinuz and initrd.img from an eoan daily build and put them in a 
directory.
  Create an lz4 (or gzip or uncompressed cpio, it doesn't matter):
  # date > date.txt
  # echo date.txt | cpio -oH newc | lz4 > date.img
  Concatenate them:
  # cat initrd.img.original date.img > initrd.img
  Boot them:
  # kvm -m 512 -kernel vmlinuz -initrd initrd.img -append rdinit=/bin/sh

  Then inside kvm:
  # ls /date.txt

  The additional file doesn't exist.

  `dmesg | grep -i initramfs` reports:
  Trying to unpack rootfs image as initramfs...
  Initramfs unpacking failed: Decoding failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840945/+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 1840945] Re: Concatenated lz4 initrds don't work

[Alkis Georgopoulos]

This is about loading the kernel/initrd, so running apport-collect on
the host won't provide any useful info, and running it inside the
initramfs isn't possible.

** 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/1840945

Title:
  Concatenated lz4 initrds don't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Concatenating multiple initrds works fine with gzipped initrds.
  (microcode+gzip+gzip) => the kernel properly decompresses that

  With lz4, it can't decompress anything after the first lz4:
  (microcode+lz4+whatever) => it doesn't decompress whatever.

  To reproduce:
  Get vmlinuz and initrd.img from an eoan daily build and put them in a 
directory.
  Create an lz4 (or gzip or uncompressed cpio, it doesn't matter):
  # date > date.txt
  # echo date.txt | cpio -oH newc | lz4 > date.img
  Concatenate them:
  # cat initrd.img.original date.img > initrd.img
  Boot them:
  # kvm -m 512 -kernel vmlinuz -initrd initrd.img -append rdinit=/bin/sh

  Then inside kvm:
  # ls /date.txt

  The additional file doesn't exist.

  `dmesg | grep -i initramfs` reports:
  Trying to unpack rootfs image as initramfs...
  Initramfs unpacking failed: Decoding failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840945/+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 1840945] Re: Concatenated lz4 initrds don't work

[Alkis Georgopoulos]

I tried all the COMPRESS= methods available in /etc/initramfs-
tools/initramfs.conf in both eoan and bionic.

For each one, I ran:
date > date.txt
echo date.txt | cpio -oH newc > date.img
update-initramfs -u
cat initrd.lz4 date.img > initrd.img
kvm -m 512 -kernel vmlinuz -initrd initrd.img -append rdinit=/bin/sh

The results show that:
xz works in both eoan and bionic,
gzip and bzip2 regressed in eoan,
lzma, lzop and lz4 never worked.

=== EOAN ===
Linux kernel x86 boot executable bzImage, version 5.2.0-10-generic 
(buildd@lgw01-amd64-046) #11-Ubuntu SMP Tue Jul 30 19:19:46 UTC 2019, 
RO-rootFS, swap_dev 0x8, Normal VGA

SIZE FILENAME  WORKS?
 9016056 vmlinuz
43335408 initrd.xz yes
43339869 initrd.lzma   no date.txt
63081861 initrd.bzip2  no date.txt
68362761 initrd.lzop   no date.txt
68364423 initrd.gzip   no date.txt
77600825 initrd.lz4kernel panic


=== BIONIC ===
Linux kernel x86 boot executable bzImage, version 4.15.0-58-generic 
(buildd@lcy01-amd64-013) #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019, RO-rootFS, 
swap_dev 0x7, Normal VGA

SIZE FILENAME  WORKS?
 8302232 vmlinuz
39946592 initrd.xz yes
39942761 initrd.lzma   no date.txt
56997316 initrd.bzip2  yes
61043794 initrd.lzop   no date.txt
61046528 initrd.gzip   yes

-- 
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/1840945

Title:
  Concatenated lz4 initrds don't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Concatenating multiple initrds works fine with gzipped initrds.
  (microcode+gzip+gzip) => the kernel properly decompresses that

  With lz4, it can't decompress anything after the first lz4:
  (microcode+lz4+whatever) => it doesn't decompress whatever.

  To reproduce:
  Get vmlinuz and initrd.img from an eoan daily build and put them in a 
directory.
  Create an lz4 (or gzip or uncompressed cpio, it doesn't matter):
  # date > date.txt
  # echo date.txt | cpio -oH newc | lz4 > date.img
  Concatenate them:
  # cat initrd.img.original date.img > initrd.img
  Boot them:
  # kvm -m 512 -kernel vmlinuz -initrd initrd.img -append rdinit=/bin/sh

  Then inside kvm:
  # ls /date.txt

  The additional file doesn't exist.

  `dmesg | grep -i initramfs` reports:
  Trying to unpack rootfs image as initramfs...
  Initramfs unpacking failed: Decoding failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840945/+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 1840945] Re: Concatenated lz4 initrds don't work

[Alkis Georgopoulos]

@xnox, thank you, in #3 I was testing date.img as a plain cpio without 
compression,
while with your updated lz4/xz commands, it appears that when date.img matches 
the compression of initrd.img, then it works fine.

So the problem only happens when mixed compressions are used.

Btw, the reason I was trying that, is that in the new version of the
"ltsp" netbooting package, we send all the netbooting code as an
additional initrd.

So if we can't use mixed compressions, we'll need to provide a different
initrd for each image/chroot/vm/live-cd that the ltsp sysadmin will want
to netboot.

If the plans to default to lz4 initramfs are cancelled, then ltsp will
work anywhere with a single initrd, from jessie and 16.04 to buster and
hopefully 20.04. :)

Otherwise... where should we hunt the bug? In the kernel decompression
code, or in mkinitramfs?

-- 
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/1840945

Title:
  Concatenated lz4 initrds don't work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Concatenating multiple initrds works fine with gzipped initrds.
  (microcode+gzip+gzip) => the kernel properly decompresses that

  With lz4, it can't decompress anything after the first lz4:
  (microcode+lz4+whatever) => it doesn't decompress whatever.

  To reproduce:
  Get vmlinuz and initrd.img from an eoan daily build and put them in a 
directory.
  Create an lz4 (or gzip or uncompressed cpio, it doesn't matter):
  # date > date.txt
  # echo date.txt | cpio -oH newc | lz4 > date.img
  Concatenate them:
  # cat initrd.img.original date.img > initrd.img
  Boot them:
  # kvm -m 512 -kernel vmlinuz -initrd initrd.img -append rdinit=/bin/sh

  Then inside kvm:
  # ls /date.txt

  The additional file doesn't exist.

  `dmesg | grep -i initramfs` reports:
  Trying to unpack rootfs image as initramfs...
  Initramfs unpacking failed: Decoding failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840945/+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 1840945] Re: Mixed compression initrds partially work

[Alkis Georgopoulos]

** Summary changed:

- Concatenated lz4 initrds don't work
+ Mixed compression initrds partially work

-- 
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/1840945

Title:
  Mixed compression initrds partially work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Updated description:

  The kernel supports loading multiple initrds, like: [cpio microcode,
  gzip initrd.img].

  Appending yet another initrd after that only works for selected
  compressions, not all of them. I'm not sure if this is a bug or a
  feature request.

  So for example, this works: [cpio microcode, xz initrd.img, gzip extra.img]
  And this doesn't: [cpio microcode, lz4 initrd.img, gzip extra.img]

  To reproduce:
  Get vmlinuz and initrd.img from an eoan daily build and put them in a 
directory.
  Create a compressed extra.img:
  # date > date.txt
  # echo date.txt | cpio -oH newc | gzip > extra.img
  Concatenate them:
  # cat initrd.img.original extra.img > initrd.img
  Boot them:
  # kvm -m 512 -kernel vmlinuz -initrd initrd.img -append rdinit=/bin/sh

  Then inside kvm:
  # ls /date.txt

  The date.txt file doesn't exist when initrd.img is lz4, while it
  appears if it's xz.

  `dmesg | grep -i initramfs` reports:
  Trying to unpack rootfs image as initramfs...
  Initramfs unpacking failed: Decoding failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840945/+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 1840945] Re: Mixed compression initrds partially work

[Alkis Georgopoulos]

** Description changed:

- Concatenating multiple initrds works fine with gzipped initrds.
- (microcode+gzip+gzip) => the kernel properly decompresses that
+ Updated description:
  
- With lz4, it can't decompress anything after the first lz4:
- (microcode+lz4+whatever) => it doesn't decompress whatever.
+ The kernel supports loading multiple initrds, like: [cpio microcode,
+ gzip initrd.img].
+ 
+ Appending yet another initrd after that only works for selected
+ compressions, not all of them. I'm not sure if this is a bug or a
+ feature request.
+ 
+ So for example, this works: [cpio microcode, xz initrd.img, gzip extra.img]
+ And this doesn't: [cpio microcode, lz4 initrd.img, gzip extra.img]
  
  To reproduce:
  Get vmlinuz and initrd.img from an eoan daily build and put them in a 
directory.
- Create an lz4 (or gzip or uncompressed cpio, it doesn't matter):
+ Create a compressed extra.img:
  # date > date.txt
- # echo date.txt | cpio -oH newc | lz4 > date.img
+ # echo date.txt | cpio -oH newc | gzip > extra.img
  Concatenate them:
- # cat initrd.img.original date.img > initrd.img
+ # cat initrd.img.original extra.img > initrd.img
  Boot them:
  # kvm -m 512 -kernel vmlinuz -initrd initrd.img -append rdinit=/bin/sh
  
  Then inside kvm:
  # ls /date.txt
  
- The additional file doesn't exist.
+ The date.txt file doesn't exist when initrd.img is lz4, while it appears
+ if it's xz.
  
  `dmesg | grep -i initramfs` reports:
  Trying to unpack rootfs image as initramfs...
  Initramfs unpacking failed: Decoding failed

-- 
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/1840945

Title:
  Mixed compression initrds partially work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Updated description:

  The kernel supports loading multiple initrds, like: [cpio microcode,
  gzip initrd.img].

  Appending yet another initrd after that only works for selected
  compressions, not all of them. I'm not sure if this is a bug or a
  feature request.

  So for example, this works: [cpio microcode, xz initrd.img, gzip extra.img]
  And this doesn't: [cpio microcode, lz4 initrd.img, gzip extra.img]

  To reproduce:
  Get vmlinuz and initrd.img from an eoan daily build and put them in a 
directory.
  Create a compressed extra.img:
  # date > date.txt
  # echo date.txt | cpio -oH newc | gzip > extra.img
  Concatenate them:
  # cat initrd.img.original extra.img > initrd.img
  Boot them:
  # kvm -m 512 -kernel vmlinuz -initrd initrd.img -append rdinit=/bin/sh

  Then inside kvm:
  # ls /date.txt

  The date.txt file doesn't exist when initrd.img is lz4, while it
  appears if it's xz.

  `dmesg | grep -i initramfs` reports:
  Trying to unpack rootfs image as initramfs...
  Initramfs unpacking failed: Decoding failed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840945/+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 1411330] Re: vmlinuz permissions

[Alkis Georgopoulos]

This affects the ltsp.org project too;
tftp can't access this file and we don't want to run tftpd as root for better 
security,
so we end up copying vmlinuz to a dedicated tftp folder just for the Ubuntu use 
case.

-- 
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/1411330

Title:
  vmlinuz permissions

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use NFS root-boot for our department systems.  Every time I upgrade,
  if it includes a linux-image-generic and I don't notice, I get lots of
  calls that the users cannot boot.  The vmlinuz image is chmod 600, but
  for NFS root-boot needs to be 644.  This is a very annoying (but not
  urgent) bug.

  Please fix so that new kernels are installed chmod 644 (as all other
  distros do).

  Thanx,

  David A. Bandel

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-generic 3.13.0.44.51
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dab11  1997 F pulseaudio
   /dev/snd/controlC0:  dab11  1997 F pulseaudio
  CurrentDesktop: LXDE
  Date: Thu Jan 15 11:24:22 2015
  HibernationDevice: RESUME=UUID=dd6857ae-02e4-4a78-befd-e7d5dad46af5
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 003: ID 0557:2219 ATEN International Co., Ltd 
   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 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision T1600
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: boot=nfs initrd=ubuntu-trusty/initrd.img init=/sbin/init 
root=/dev/nfs nfsroot=128.42.128.39:/srv/tftp/ubuntu-trusty,rw ip=dhcp sec=sys 
ifnames=0 BOOT_IMAGE=ubuntu-trusty/vmlinuz
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-44-generic N/A
   linux-backports-modules-3.13.0-44-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 02/21/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 06NWYK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd02/21/2012:svnDellInc.:pnPrecisionT1600:pvr01:rvnDellInc.:rn06NWYK:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: Precision T1600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411330/+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 759725] Re: The kernel is no longer readable by non-root users

[Alkis Georgopoulos]

This forces us to run tftpd as root, to serve $CHROOT/boot to netboot clients,
so it's actually LESS secure than it was before the change.

Applying the stat workaround isn't always easy; sometimes $CHROOT/boot
comes from a read-only loopback image.

Also note that initrd.img, which may actually contain private
information, is world-readable.

-- 
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/759725

Title:
  The kernel is no longer readable by non-root users

Status in linux package in Ubuntu:
  Won't Fix

Bug description:
  The mode of the latest kernel has changed so it is no longer readable
  by non-root users:

  -rw-r--r-- 1 root root 4336016 2010-10-17 01:37 
/boot/vmlinuz-2.6.35-22-generic
  -rw-r--r-- 1 root root 4336912 2010-11-24 12:46 
/boot/vmlinuz-2.6.35-23-generic
  -rw-r--r-- 1 root root 4523072 2011-03-08 18:47 /boot/vmlinuz-2.6.38-6-generic
  -rw--- 1 root root 4523936 2011-04-11 05:24 /boot/vmlinuz-2.6.38-8-generic

  This prevents people from using this kernel to boot qemu
  virtual machines as non-root.

  Please change the mode back to make the kernel readable.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: linux-image-2.6.38-8-generic 2.6.38-8.42
  Regression: Yes
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic x86_64
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access /dev/snd/: No such file or directory
  AplayDevices: aplay: device_list:240: no soundcards found...
  Architecture: amd64
  ArecordDevices: arecord: device_list:240: no soundcards found...
  CRDA: Error: [Errno 2] No such file or directory
  Date: Wed Apr 13 13:05:01 2011
  HibernationDevice: RESUME=UUID=112bf9c4-620e-441f-abb3-aeac6aa15294
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Red Hat KVM
  PciMultimedia:
   
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic 
root=UUID=1efa0b67-17df-484e-980c-8544fa2149fe ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-2.6.35-22-generic N/A
   linux-backports-modules-2.6.35-22-generic  N/A
   linux-firmware 1.50
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/01/2007
  dmi.bios.vendor: Seabios
  dmi.bios.version: 0.5.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: Red Hat
  dmi.modalias: 
dmi:bvnSeabios:bvr0.5.1:bd01/01/2007:svnRedHat:pnKVM:pvrRHEL6.0.0PC:cvnRedHat:ct1:cvr:
  dmi.product.name: KVM
  dmi.product.version: RHEL 6.0.0 PC
  dmi.sys.vendor: Red Hat

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/759725/+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 1411330] Re: vmlinuz permissions

[Alkis Georgopoulos]

*** This bug is a duplicate of bug 759725 ***
https://bugs.launchpad.net/bugs/759725

** This bug has been marked a duplicate of bug 759725
   The kernel is no longer readable by non-root users

-- 
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/1411330

Title:
  vmlinuz permissions

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I use NFS root-boot for our department systems.  Every time I upgrade,
  if it includes a linux-image-generic and I don't notice, I get lots of
  calls that the users cannot boot.  The vmlinuz image is chmod 600, but
  for NFS root-boot needs to be 644.  This is a very annoying (but not
  urgent) bug.

  Please fix so that new kernels are installed chmod 644 (as all other
  distros do).

  Thanx,

  David A. Bandel

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-generic 3.13.0.44.51
  ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
  Uname: Linux 3.13.0-44-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dab11  1997 F pulseaudio
   /dev/snd/controlC0:  dab11  1997 F pulseaudio
  CurrentDesktop: LXDE
  Date: Thu Jan 15 11:24:22 2015
  HibernationDevice: RESUME=UUID=dd6857ae-02e4-4a78-befd-e7d5dad46af5
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  Lsusb:
   Bus 002 Device 003: ID 0557:2219 ATEN International Co., Ltd 
   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 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision T1600
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: boot=nfs initrd=ubuntu-trusty/initrd.img init=/sbin/init 
root=/dev/nfs nfsroot=128.42.128.39:/srv/tftp/ubuntu-trusty,rw ip=dhcp sec=sys 
ifnames=0 BOOT_IMAGE=ubuntu-trusty/vmlinuz
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-44-generic N/A
   linux-backports-modules-3.13.0-44-generic  N/A
   linux-firmware 1.127.11
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 02/21/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 06NWYK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd02/21/2012:svnDellInc.:pnPrecisionT1600:pvr01:rvnDellInc.:rn06NWYK:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: Precision T1600
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1411330/+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 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

[Alkis Georgopoulos]

Exactly. I did the "verification-done-bionic" step for 18.2.2 in comment
#12 above; and unfortunately I don't have an affected school nearby,
where I could test 18.2.8 in cosmic, and installing cosmic in a remote
school would be hard.

Thanks a lot Timo!

-- 
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/1815172

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]
  Several schools reported black screens after normally updating their Ubuntu 
boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

  This is caused by mesa assuming that soft-pinning on GEN8+ is working
  since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So
  a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT
  sizes/pin flags, but that's left for future.

  [Test case]
  install fixed mesa or kernel, check that the regression is fixed

  [Regression potential]
  mesa: shouldn't be any, it just reverts the change to always soft-pin
  (TODO kernel: adds commits from upstream stable, which have been well tested 
upstream by now)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[Alkis Georgopoulos]

** No longer affects: epoptes (Ubuntu)

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718227

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Fix Released
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  Invalid
Status in ethtool package in Ubuntu:
  Triaged
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  Won't Fix
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  Fix Released
Status in openvpn package in Ubuntu:
  New
Status in openvswitch package in Ubuntu:
  Triaged
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+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 183303] Re: Can't create new wireless network using mac80211 based drivers

[Alkis Georgopoulos]

** No longer affects: ltsp (Ubuntu)

-- 
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/183303

Title:
  Can't create new wireless network using mac80211 based drivers

Status in NetworkManager:
  Unknown
Status in linux package in Ubuntu:
  Won't Fix
Status in network-manager package in Ubuntu:
  Invalid
Status in wpasupplicant package in Ubuntu:
  Fix Released
Status in network-manager package in Debian:
  Fix Released

Bug description:
  I am trying to create a new wireless network (particularly, with no
  encryption) with the gnome applet. However, I just get the message
  "Trying to connect to wireless network  «(null)»". Then, after a
  couple of minutes or so, it gets back to the cabled connection and no
  wireless connection is created.

  I am using Gutsy, network-manager 0.6.5-0ubuntu16.7.10.0 and network-
  manager-gnome 0.6.5-0ubuntu11~7.10.0.

  Updated description: The original reporter used ipw2200, but for that driver 
a bug has already been reported for this isse: Bug #75358. 
  This bug now addresses users with mac20811-based drivers, since the majority 
of the commenters have such cards/drivers.

  The bug has persisted in Gutsy, Hardy, Intrepid and even Jaunty RC...

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/183303/+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 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

[Alkis Georgopoulos]

Hi Timo,

if I remember correctly, there were some schools that were affected by this 
issue, but I wasn't able to reproduce it in the office due to lack of similar 
hardware.
Unfortunately it's not easy to check which were those schools; but I can keep 
an eye on this issue, in case I hear about black screens in the near future

-- 
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/1815172

Title:
  [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Fix Committed
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  Won't Fix
Status in mesa source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  Several schools reported black screens after normally updating their Ubuntu 
boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

  This is caused by mesa assuming that soft-pinning on GEN8+ is working
  since kernel 4.5, but in fact this issue wasn't fixed until 4.19.3. So
  a proper fix would be to backport commits from 4.19.3/4.20 to fix GTT
  sizes/pin flags, but that's left for future.

  [Test case]
  install fixed mesa or kernel, check that the regression is fixed

  [Regression potential]
  mesa: shouldn't be any, it just reverts the change to always soft-pin
  (TODO kernel: adds commits from upstream stable, which have been well tested 
upstream by now)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+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 1815172] Re: Black screen on skylake after 18.0 => 18.2 update

[Alkis Georgopoulos]

I verify that the bionic-proposed package addresses the issue.

Tested in:
# lspci -nn -k | grep -A 2 VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 630 
[8086:5912] (rev 04)
Subsystem: Gigabyte Technology Co., Ltd HD Graphics 630 [1458:d000]
Kernel driver in use: i915


** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic

-- 
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/1815172

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+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 1815172]

[Alkis Georgopoulos]

I just tried with 4.18.0-14-generic, the same issue happens there as
well.

And, another school reported the issue on HD Graphics 630:

root@pc02:~# lspci -nn -k | grep -A 2 VGA 00:02.0 VGA compatible
controller [0300]: Intel Corporation HD Graphics 630 [8086:5912] (rev
04) Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
Kernel driver in use: i915

-- 
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/1815172

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+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 1815172]

[Alkis Georgopoulos]

I don't know the software stacks involved:

If I understood it correctly,
mesa 18.3.3 doesn't work with older kernels while 18.0 did work,
and so I'll do a bisection to see which kernel commit fixes the issue,
and then distro kernel maintainers may cherrypick it for older kernels.

If there's no need for mesa to work with older kernels without the
cherrypicked commit, then I guess yes, this issue should be closed, in
which case please close it for me or tell me to close it.

Thanks again!

-- 
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/1815172

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+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 1815172]

[Alkis Georgopoulos]

Hello Sergii,

I tried with 4.20.7 and it appears to work fine! Thanks!

Output of the commands:

# uname -a
Linux srv-6gym-chalk 4.20.7-042007-generic #201902061234 SMP Wed Feb 6 17:49:39 
UTC 2019 i686 i686 i686 GNU/Linux

# file /usr/bin/glxinfo
/usr/bin/glxinfo: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), 
dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 3.2.0, 
BuildID[sha1]=6cef7eab38835376734bdc80c5ab1ee786a6157a, stripped

# glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel Open Source Technology Center (0x8086)
Device: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) x86/MMX/SSE2 
(0x1912)   
Version: 18.3.3
Accelerated: yes
Video memory: 1536MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.5
Max compat profile version: 3.0
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel Open Source Technology Center
OpenGL renderer string: Mesa DRI Intel(R) HD Graphics 530 (Skylake GT2) 
x86/MMX/SSE2
OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.3.3
OpenGL core profile shading language version string: 4.50
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 3.0 Mesa 18.3.3
OpenGL shading language version string: 1.30
OpenGL context flags: (none)

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.3.3
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

-- 
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/1815172

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+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 1815172]

[Alkis Georgopoulos]

I tried a small kernel bisection using the ubuntu kernel binaries,
4.19.2-041902=fails,
4.19.3-041903=works

-- 
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/1815172

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+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 1815172]

[Alkis Georgopoulos]

Just correcting a wrong comment (#2) I made:
> It happens on both 32bit and 64bit installations.

I asked the school that reported the issue on 64bit to check again, and
they said they have a 32bit installation after all.

So the problem has only been reported in 32bit installations; I don't
know if it happened on 64bit. And btw everything is fixed now, thanks
again to all. :)

-- 
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/1815172

Title:
  Black screen on skylake after 18.0 => 18.2 update

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New
Status in linux source package in Bionic:
  New
Status in mesa source package in Bionic:
  Fix Committed
Status in linux source package in Cosmic:
  New
Status in mesa source package in Cosmic:
  Fix Committed

Bug description:
  Several schools reported black screens after normally updating their
  Ubuntu boxes from 18.0.5-0ubuntu0~18.04.1 to 18.2.2-0ubuntu1~18.04.1.

  Downgrading mesa fixes the problem.

  lspci: 00:02.0 VGA compatible controller [0300]: Intel Corporation HD
  Graphics 530 [8086:1912] (rev 06) Subsystem: ASUSTeK Computer
  Inc. HD Graphics 530 [1043:8694]Kernel modules: i915

  Unfortunately I can't find a lot of useful information, here are some bits:
   * systemctl --failed says "gpu-manager" and "lightdm" have failed
   * Xorg.log is clean: https://termbin.com/6l2b
   * dmesg too: https://termbin.com/ip4e
   * It happens on lightdm/MATE, I don't know about Ubuntu GNOME.
   * If one runs `xinit` from ssh, it fails with:
  i965: Failed to submit batchbuffer: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815172/+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 1650337] Re: unknown filesystem efivarfs

[Alkis Georgopoulos]

** Package changed: linux-lts-xenial (Ubuntu) => linux-signed (Ubuntu)

** Changed in: linux-signed (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux-signed (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed in Ubuntu.
https://bugs.launchpad.net/bugs/1650337

Title:
  unknown filesystem efivarfs

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  Please add file system efivarfs to 32-bit Linux kernel, so on EFI machine 
following command could be executed:
  sudo mount -t efivarfs efivarfs /sys/firmware/efi/efivars

  See also: bug 1648278

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1650337/+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 696435] Re: wait-for-root fails to detect nbd root

[Alkis Georgopoulos]

I'm the bug reporter, and I have a problem in doing the verification.

a) The initial testcase that I reported happens in both 4.4 unpatched
and 4.10. I.e. the bug that I reported is not yet fixed.

b) Some Ubuntu developer wrote a new testcase as part of doing the SRU.
I cannot reproduce that testcase neither in 4.4 unpatched nor in 4.10,
i.e. `udevadm monitor` does show add/change events for nbd devices for
me in both kernels. I.e. that sounds like a different bug that I never
saw.

So I'm not sure how I can help here...

-- 
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/696435

Title:
  wait-for-root fails to detect nbd root

Status in linux package in Ubuntu:
  Fix Released
Status in nbd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in systemd source package in Xenial:
  Confirmed

Bug description:
  [Impact]
  Kernel does not generate any events when ndb-client connects /dev/nbd0 
devices, therefore it is impossible to monitor/react to the state of /dev/nbd0.

  [Fix]
  Generate change uevent when size of /dev/nbd0 changes

  [Testcase]
  * Start udevadm monitor
  * modprobe nbd
  * use ndb-client to connect something to /dev/nbd0
  * observe that there are change udev events generated on /dev/nbd0 itself

  [Regression Potential]
  There is no change to existing uevents, or their ordering.
  There is now an addition change event which will cause systemd to mark ndb 
devices as ready and trigger appropriate actions

  [Original Bug Report]

  When using an nbd root, wait-for-root blocks for 30 seconds before
  booting continues successfully.

  Using Ubuntu Natty, related packages versions:
  nbd-client 1:2.9.16-6ubuntu1
  initramfs-tools 0.98.1ubuntu9

  The wait-for-root call from /usr/share/initramfs-tools/scripts/local:
   while [ -z "${FSTYPE}" ]; do
    FSTYPE=$(wait-for-root "${ROOT}" ${ROOTDELAY:-30})

    # Run failure hooks, hoping one of them can fix up the system
    # and we can restart the wait loop.  If they all fail, abort
    # and move on to the panic handler and shell.
    if [ -z "${FSTYPE}" ] && ! try_failure_hooks; then
     break
    fi
   done

  I replaced wait-for-root with a sh script that did `set >&2`, here are the 
relevant environment variables at the time wait-for-root was called:
  ROOT='/dev/nbd0'
  ROOTDELAY=''
  ROOTFLAGS=''
  ROOTFSTYPE=''
  nbdroot='192.168.0.1,2011'

  It's probably worth noting that "nbd0: unknown partition table" was
  displayed asynchronously 1-2 seconds after wait-for-root was invoked
  and while it was still waiting. But I tried adding a "sleep 5" as the
  last line of local-top/nbd, so that the nbd message was displayed a
  lot before wait-for-root was called, and it didn't make a difference.
  So I don't think a race condition is involved in this problem.

  Temporarily I'm passing rootdelay=1 in the kernel command line to work
  around the problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/696435/+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 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

[Alkis Georgopoulos]

For the maintainers of the affected packages to be able to help in this issue,
addressing the main question already stated above would be most helpful:

To support netplan, do we have to implement netlink events listeners ourselves?
I'm not sure all maintainers are willing to do that.
Or is there another package that provides this functionality that we could rely 
on?
E.g. NetworkManager does have a dispatcher.d directory that we can use, but 
does Ubuntu ship something similar (networkd-dispatcher?) in systems that don't 
use NetworkManager?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718227

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  Invalid
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  Triaged
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  Won't Fix
Status in ifmetric package in Ubuntu:
  Won't Fix
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  Invalid
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  Won't Fix
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  Won't Fix
Status in vzctl package in Ubuntu:
  Triaged
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug 1713803: replacement of resolvconf with systemd needs integration 
   * bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for 
dhclient needs integration

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: netplan (not installed)
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Sep 19 10:53:08 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (789 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: plan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kerne

[Kernel-packages] [Bug 1745118] Re: Unable to boot with i386 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel on Xenial / Artful

[Alkis Georgopoulos]

I had bisected this issue and I had reported upstream on 19 Jan:
https://bugzilla.kernel.org/show_bug.cgi?id=198529.

I verify that the patch/test kernel by wgrant works fine here.
Thanks a lot!

** Bug watch added: Linux Kernel Bug Tracker #198529
   https://bugzilla.kernel.org/show_bug.cgi?id=198529

-- 
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/1745118

Title:
  Unable to boot with i386 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel on
  Xenial / Artful

Status in Linux Mint:
  New
Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Some SRU testing node cannot boot with the latest 32bit 4.13 linux-hwe
  kernel.

  Take node "fozzie"(Dell PowerEdge R320) for example, it works with
  4.13.0-21.24~16.04.1 but not 4.13.0-25 / 4.13.0-26 / 4.13.0-31 kernel
  on Xenial.

  From the BMC console, I can see the grub menu on boot and after that
  it will drop into a boot loop.

  This can be reproduced on Artful 4.13 as well.

  Note that this kernel works for some of the node in our test pool
  (Intel SDP - Denlow)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-21-generic 4.13.0-21.24~16.04.1
  ProcVersionSignature: User Name 4.13.0-21.24~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-21-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Wed Jan 24 08:49:57 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-hwe-edge
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jan 24 09:17 seq
   crw-rw 1 root audio 116, 33 Jan 24 09:17 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 16.04
  IwConfig: Error: [Errno 2] No such file or directory
  MachineType: Dell Inc. PowerEdge R320
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-21-generic 
root=UUID=0845f9a0-ab8c-4dfa-8385-af21f2f2b9ad ro
  ProcVersionSignature: User Name 4.13.0-21.24~16.04.1-generic 4.13.13
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-21-generic N/A
   linux-backports-modules-4.13.0-21-generic  N/A
   linux-firmware 1.157.14
  RfKill: Error: [Errno 2] No such file or directory
  Tags:  xenial uec-images
  Uname: Linux 4.13.0-21-generic i686
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video
  _MarkForUpload: True
  dmi.bios.date: 05/11/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 0DY523
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd05/11/2012:svnDellInc.:pnPowerEdgeR320:pvr:rvnDellInc.:rn0DY523:rvrA03:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R320
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linuxmint/+bug/1745118/+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 1259861] Re: 5-10 second delay in kernel boot

[Alkis Georgopoulos]

@rhansen, your bug might be a different one, since ip=dhcp is processed
by the initramfs, while I'm talking about the kernel, before the
initramfs gets to run.

The bug is still there in Xenial.
I noticed that it doesn't happen in all hardware; I've seen it in *some* real 
clients and under VirtualBox, while I haven't been able to reproduce it under 
KVM.

Example from Xenial:
$ grep 'model name' /proc/cpuinfo 
model name  : Intel(R) Core(TM) i5-4590 CPU @ 3.30GHz

$ dmesg
...
[1.224044] usb 3-4: ep 0x81 - rounding interval to 64 microframes, ep desc 
says 80 microframes
[1.677095] tsc: Refined TSC clocksource calibration: 3292.375 MHz
[1.677134] clocksource: tsc: mask: 0x max_cycles: 
0x2f75298baf3, max_idle_ns: 440795322961 ns
[2.677286] clocksource: Switched to clocksource tsc
[   12.784911] PM: Hibernation image not present or could not be loaded.
[   12.785223] Freeing unused kernel memory: 936K (c1b6d000 - c1c57000)
[   12.785350] Write protecting the kernel text: 7816k
[   12.785450] Write protecting the kernel read-only data: 3120k
[   12.785502] NX-protecting the kernel data: 6520k
[   12.797220] random: systemd-udevd urandom read with 0 bits of entropy 
available
...

I also tried with "nohibernate", it's not related to hibernation.

** Tags removed: kernel-fixed-upstream
** Tags added: xenial

-- 
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/1259861

Title:
  5-10 second delay in kernel boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
  Excerpt from dmesg:
  [3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots 
or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1259861] Re: 5-10 second delay in kernel boot

[Alkis Georgopoulos]

@rhansen, sorry, it turns out you were right!

ip= is what's causing my kernel delay. I even tried without an initramfs
to verify it, and it caused 10 seconds of delay before the kernel panic
because of the missing initramfs.

I'll try to gather more info about it.

-- 
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/1259861

Title:
  5-10 second delay in kernel boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
  Excerpt from dmesg:
  [3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots 
or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1259861] Re: 5-10 second delay in kernel boot

[Alkis Georgopoulos]

The problem is not there in Ubuntu 12.04.2 (kernel 3.5.0-54)
and it is there in Ubuntu 12.04.3 (kernel 3.8.0-44).

My test case is to boot with ip=dhcp break=top. When the problem doesn't
exist, I get an initramfs prompt in 2 seconds, when it exists I get it
in 12 seconds, and that shows up in dmesg as well.

Comparing those configs from 
https://wiki.ubuntu.com/Kernel/Configs/QuantalToRaring, I got:
3.5: # CONFIG_IP_PNP is not set
3.8: CONFIG_IP_PNP=y CONFIG_IP_PNP_DHCP=y

Is it possible to revert those?
Can we find out why they were enabled?
If they're only needed on some arches (e.g. ARM), maybe they could only be 
enabled there?

@rhansen, writing an alias e.g. initramfs_ip=* won't help, e.g. IPAPPEND 3 in 
pxelinux puts ip=* in the cmdline, I don't think it'll ever be patched to put 
initramfs_ip=* there...
I think we should either get the configuration change reverted,
or fix ipconfig.c so that it aborts if no NICs/modules are detected.

-- 
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/1259861

Title:
  5-10 second delay in kernel boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
  Excerpt from dmesg:
  [3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots 
or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1259861] Re: 5-10 second delay in kernel boot

[Alkis Georgopoulos]

I think the upstream commit that set CONFIG_IP_PNP=y is this:
https://github.com/torvalds/linux/commit/c1b362e3b4d331a63915b268a33207311a439d60#diff-364c3610ebc6899c22148ba10636c71c

Ubuntu and openSUSE now have CONFIG_IP_PNP=y and experience the issue.
Debian and Fedora do not have CONFIG_IP_PNP set and do not experience the issue.

To reproduce in different distros, set `ip=dhcp init=/bin/sh` and see if
getting a prompt takes longer than 10+ seconds or not.

-- 
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/1259861

Title:
  5-10 second delay in kernel boot

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
  Excerpt from dmesg:
  [3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots 
or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1259861] Re: 5-10 second delay in kernel boot with kernel command line ip=

[Alkis Georgopoulos]

> TJ (tj) wrote 9 hours ago:#26
> Originally introduced into the Ubuntu 13.10 (Saucy) configuration with commit 
> 301b4bb
> UBUNTU: rebase to v3.10-rc4

TJ, that doesn't match my tests as mentioned in comment #21,
i.e. that I see the issue since kernel 3.8, and that
https://wiki.ubuntu.com/Kernel/Configs/QuantalToRaring says the change was done 
in Raring.

A `grep IP_PNP /boot/config*` in a 3.8 kernel does verify that the
change was done before 3.10 (or backported in 3.8? dunno).

-- 
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/1259861

Title:
  5-10 second delay in kernel boot with kernel command line ip=

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Wily:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
  Excerpt from dmesg:
  [3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots 
or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1259861] Re: 5-10 second delay in kernel boot with kernel command line ip=

[Alkis Georgopoulos]

$ for d in karmic lucid maverick natty oneiric precise quantal raring saucy 
trusty utopic vivid wily xenial; do
echo "$d: $(wget -q 
http://kernel.ubuntu.com/~kernel-ppa/configs/$d/i386-config.flavour.generic -O 
- | grep -w CONFIG_IP_PNP)"
done

karmic: 
lucid: 
maverick: 
natty: # CONFIG_IP_PNP is not set
oneiric: # CONFIG_IP_PNP is not set
precise: # CONFIG_IP_PNP is not set
quantal: # CONFIG_IP_PNP is not set
raring: CONFIG_IP_PNP=y
saucy: CONFIG_IP_PNP=y
trusty: CONFIG_IP_PNP=y
utopic: CONFIG_IP_PNP=y
vivid: CONFIG_IP_PNP=y
wily: CONFIG_IP_PNP=y
xenial:

-- 
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/1259861

Title:
  5-10 second delay in kernel boot with kernel command line ip=

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Wily:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
  Excerpt from dmesg:
  [3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots 
or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1259861] Re: 5-10 second delay in kernel boot with kernel command line ip=

[Alkis Georgopoulos]

apw uploaded a test kernel without CONFIG_IP_PNP in 
http://people.canonical.com/~apw/lp1259861-xenial/.
I tested it with "ip=dhcp break=top" and it didn't have the 10 sec delay.

Thanks a lot Andy!

-- 
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/1259861

Title:
  5-10 second delay in kernel boot with kernel command line ip=

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Trusty:
  Confirmed
Status in linux source package in Wily:
  Confirmed
Status in linux source package in Xenial:
  Fix Committed

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
  Excerpt from dmesg:
  [3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots 
or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1259861] Re: 5-10 second delay in kernel boot

[Alkis Georgopoulos]

Yes it's still happening on 3.13.0-29-generic.

[3.912539] random: nonblocking pool is initialized
[   19.999335] Adding 3957756k swap on /dev/sda7.  Priority:-1 extents:1 
across:3957756k FS


** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

** Tags removed: kernel-request-3.13.0-24.46 needs-kernel-logs
** Tags added: bot-stop-nagging

-- 
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/1259861

Title:
  5-10 second delay in kernel boot

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
  Excerpt from dmesg:
  [3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots 
or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1259861] Re: 5-10 second delay in kernel boot

[Alkis Georgopoulos]

@penalvch: as I mention in comment #6, the "kernel-fixed-upstream" tag
is not appropriate because this was never an upstream bug, so nothing
was fixed upstream. It's an ubuntu-specific bug, so upstream is not
related at all to this bug and shouldn't appear in any tags.

The "needs-kernel-logs" tag also isn't appropriate because it's useless
information, anyone willing to work on this can just check the logs on
his own pc.

Karma points are nice, but they shouldn't be a goal... If you really
want to help, do so by triaging bugs, not by tagging them...

-- 
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/1259861

Title:
  5-10 second delay in kernel boot

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
  Excerpt from dmesg:
  [3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots 
or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1259861] Re: 5-10 second delay in kernel boot

[Alkis Georgopoulos]

I think anyone can just run `dmesg` and verify that the bug exists in all 
recent Ubuntu kernels and in none of the vanilla or Debian kernels.
I don't know why the logs are important here.
I don't think there's any point in closing bugs just to lower the bug count 
(which means nothing if the bugs are still there), instead of running a single 
command to verify them.

** Changed in: linux (Ubuntu)
   Status: Expired => Confirmed

** Tags removed: needs-kernel-logs

-- 
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/1259861

Title:
  5-10 second delay in kernel boot

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
  Excerpt from dmesg:
  [3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots 
or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1259861] Re: 5-10 second delay in kernel boot

[Alkis Georgopoulos]

@penlalvch: I was asked in #ubuntu-kernel to file this bug report so
that they can assign someone to work on it.

If you keep adding "it needs this and that" tags, then this bug report
appears to be incomplete, and no developer will start working on it
until I satisfy/remove the tags.

But as I keep saying,
1) needs-apport-collect => why? it happens anywhere, so I could run 
apport-collect in a KVM VM, but why would anyone want that? It's just useless 
information.
2) needs-upstream-testing => as I said, the problem doesn't happen in any 
Debian or Vanilla kernels.
OK if you really need a specific version there, here it is:
$ uname -a
Linux alkis 3.13.0-9.29-031400rc3-generic #201402181344 SMP Tue Feb 18 19:02:54 
UTC 2014 i686 i686 i686 GNU/Linux
...but again that version number is useless because it doesn't happen in _any_ 
vanilla kernels.

** Tags removed: needs-apport-collect needs-upstream-testing
** Tags added: tested-upstream-its-ok-there-its-an-ubuntu-specific-bug

-- 
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/1259861

Title:
  5-10 second delay in kernel boot

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
  Excerpt from dmesg:
  [3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots 
or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 345374] Re: Silicon Integrated Systems [SiS] 191 Gigabit Ethernet

[Alkis Georgopoulos]

** Changed in: linux (Ubuntu)
   Status: Expired => 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/345374

Title:
  Silicon Integrated Systems [SiS] 191 Gigabit Ethernet

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi, I got an issue, ethernet doesn't work on ASUS X71SL-7S134C laptop
  with Intrepid and Jaunty

  eth0 exist but is unusable, no dhcp and if I try to with static IP
  nothing send or recieve. I'm 100% sure of my network, another laptop
  on the same rj45 link get dhcp without any problem.

  I try on kernel 2.6.28-11-generic

  eth0 Link encap:Ethernet HWaddr 00:24:8c:1c:9c:d8
UP BROADCAST MULTICAST MTU:1500 Metric:1
Packets reçus:0 erreurs:0 :0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 lg file transmission:1000
Octets reçus:0 (0.0 B) Octets transmis:0 (0.0 B)
Interruption:19 Adresse de base:0xdead

  $lspci -nn |grep Ethe
  00:04.0 Ethernet controller [0200]: Silicon Integrated Systems [SiS] 191 
Gigabit Ethernet Adapter [1039:0191] (rev 02)

  $ lsb_release -rd
  Description:  Ubuntu jaunty (development branch)
  Release:  9.04

  I attach lspci -vnn and dmesg, if something miss just ask ;)

  thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/345374/+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 1259861] [NEW] 5-10 second delay in kernel boot

[Alkis Georgopoulos]

Public bug reported:

In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
Excerpt from dmesg:
[3.740100] Switched to clocksource tsc
[   14.208118] PM: Hibernation image not present or could not be loaded.
[   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

The exact messages above don't matter, they are different on different boots or 
on different machines.
It even happens with e.g. 
$ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

My current kernel is
Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: trusty

-- 
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/1259861

Title:
  5-10 second delay in kernel boot

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
  Excerpt from dmesg:
  [3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots 
or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1259861] Re: 5-10 second delay in kernel boot

[Alkis Georgopoulos]

...ignoring the bot and changing the state back to New, as the exact
kernel version doesn't matter...

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1259861

Title:
  5-10 second delay in kernel boot

Status in “linux” package in Ubuntu:
  New

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
  Excerpt from dmesg:
  [3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots 
or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1259861] Re: 5-10 second delay in kernel boot

[Alkis Georgopoulos]

Changing to confirmed to satisfy the bot. :)

** 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/1259861

Title:
  5-10 second delay in kernel boot

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
  Excerpt from dmesg:
  [3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots 
or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 1259861] Re: 5-10 second delay in kernel boot

[Alkis Georgopoulos]

I just tested with linux-
image-3.13.0-031300rc3-generic_3.13.0-031300rc3.201312061335_i386.deb,
it doesn't happen there.

I don't think I should put the 'kernel-fixed-upstream' tag as the
problem might be in some Ubuntu-specific kernel patch or configuration
option that's been around for a couple of years.

Do you want me to test with the vanilla 3.12 too? The delay probably
won't exist there either...

** 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/1259861

Title:
  5-10 second delay in kernel boot

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  In Trusty I see a big delay while the kernel boots that I did not see back in 
Precise.
  Some people have been experiencing this in Saucy too, so I don't know exactly 
when it started happening.
  Excerpt from dmesg:
  [3.740100] Switched to clocksource tsc
  [   14.208118] PM: Hibernation image not present or could not be loaded.
  [   14.208885] Freeing unused kernel memory: 864K (c19ac000 - c1a84000)

  The exact messages above don't matter, they are different on different boots 
or on different machines.
  It even happens with e.g. 
  $ sudo kvm -m 768 -cdrom trusty-desktop-i386.iso

  My current kernel is
  Linux server 3.12.0-7-generic #15-Ubuntu SMP Sun Dec 8 23:42:09 UTC 2013 i686 
i686 i686 GNU/Linux
  ...but the exact version, maybe from 3.8 to 3.12+, shouldn't matter, just run 
`dmesg` yourself and check if there's a big delay there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1259861/+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 338328] Re: Acer Aspire 5920G - some Fn keys not working

[Alkis Georgopoulos]

That laptop has died 3 years ago, feel free to let the bug report
expire.

I'll be reporting all other kernel-related bugs upstream from now on
since those that I've reported in launchpad only get the occasional "can
we close it now?" feedback every few years. It's understandable, and
sorry I just didn't know where's the right place to report the bugs back
then. Thank you for your time!

-- 
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/338328

Title:
  Acer Aspire 5920G - some Fn keys not working

Status in “hal-info” package in Ubuntu:
  Fix Released
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: hal-info

  Continuing from bugs #327707 and #281951.
  Reporting the keys that do not work correctly with the latest patch 
(https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/327707/comments/15).

  Martin thanks for your interest in solving this.

  
  Please replace
  e04e:brightnessup 
  e06f:brightnessdown 
  with
  e04e:reserved 

  e06f:reserved 

  because the brightness is already changed in the hardware - so sending the 
keystrokes is changing the brightness again, reducing the available brighness 
levels from 10 to only 5.
  Another sideeffect of this is that while watching an e.g. youtube movie, the 
brightness keys cancel fullscreen (but not if they're declared as "reserved").

  
  Please add
  e00a:media 


  
  Also, with the new .fdi, my browser key send an "XF86HomePage" which didn't 
start the browser. So please add
  e032:www 
  which does start the browser (with the default gnome shortcuts).

  
  I don't have these keys, but I don't mind if they're declared because they 
don't collide with any of my keys:
  e054:bluetooth 
  e057:bluetooth 
  e058:bluetooth 
  (ok, removed with last patch)e059:brightnessup 
  e06e:brightnessup 
  e071:f22 
  (ok, removed with last patch)e072:f22 
  e073:prog2 

  e075:presentation 
  e078:fn 
  e079:f23 

  
  Kind regards,
  Alkis Georgopoulos
  --- 
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alkisg 1270 F pulseaudio
   /dev/snd/pcmC0D0p:   alkisg 1270 F...m pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf350 irq 22'
 Mixer name : 'Realtek ALC1200'
 Components : 'HDA:10ec0888,10250121,00100101 
HDA:14f12c06,10250121,0010'
 Controls  : 24
 Simple ctrls  : 14
  DistroRelease: Ubuntu 10.04
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100202)
  MachineType: Acer, inc. Aspire 5920G
  NonfreeKernelModules: nvidia
  Package: linux (not installed)
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-16-generic-pae 
root=UUID=ef8419f4-e069-4ec3-af61-70bc1fc78bb4 ro quiet splash
  ProcEnviron:
   PATH=(custom, user)
   LANG=el_GR.utf8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 2.6.32-16.25-generic-pae
  Regression: No
  RelatedPackageVersions: linux-firmware 1.32
  Reproducible: Yes
  Tags: lucid needs-upstream-testing
  TestedUpstream: No
  Uname: Linux 2.6.32-16-generic-pae i686
  UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev 
plugdev sambashare sudo tape vboxusers video
  dmi.bios.date: 01/29/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v1.3808
  dmi.board.name: Chapala
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrv1.3808:bd01/29/2008:svnAcer,inc.:pnAspire5920G:pvrNotApplicable:rvnAcer,Inc.:rnChapala:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: Aspire 5920G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/338328/+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 1262287] [NEW] SSH sockets on overlayfs report connection refused

[Alkis Georgopoulos]

Public bug reported:

Reusing a master ssh socket that is created on an overlayfs mount
reports connection refused, while on real filesystems or on tmpfs it
works fine.

Steps to reproduce (/var is ext4, /tmp is tmpfs.):
# mkdir -p /var/overlayfs-socket
# cd /var/overlayfs-socket
# mkdir root rofs /tmp/cow
# mount -t overlayfs -o "upperdir=/tmp/cow,lowerdir=rofs" overlayfs root
# ssh -NMS root/socket alkisg@localhost
alkisg@localhost's password: []

And on another tab of the same terminal:
# ssh -S root/socket alkisg@localhost ls
Control socket connect(root/socket): Connection refused
alkisg@localhost's password: 

The problem is in the last line, on real filesystems or on tmpfs it
doesn't ask for a password, it reuses the existing socket.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.12.0-7-generic 3.12.0-7.15
ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
Uname: Linux 3.12.0-7-generic i686
ApportVersion: 2.12.7-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  alkisg 3511 F pulseaudio
 /dev/snd/controlC0:  alkisg 3511 F pulseaudio
CurrentDesktop: GNOME
Date: Wed Dec 18 18:57:18 2013
HibernationDevice: RESUME=UUID=5eff7bf1-95b5-4fc1-9c71-0950810c717e
InstallationDate: Installed on 2013-10-31 (48 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20131021.1)
MachineType: System manufacturer System Product Name
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic 
root=UUID=e1f06e01-d2dc-45e5-b446-54e1e4a5dc2c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.12.0-7-generic N/A
 linux-backports-modules-3.12.0-7-generic  N/A
 linux-firmware1.117
RfKill:
 
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/04/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0415
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5KPL-AM EPU
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0415:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AMEPU:rvrx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug i386 trusty

-- 
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/1262287

Title:
  SSH sockets on overlayfs report connection refused

Status in “linux” package in Ubuntu:
  New

Bug description:
  Reusing a master ssh socket that is created on an overlayfs mount
  reports connection refused, while on real filesystems or on tmpfs it
  works fine.

  Steps to reproduce (/var is ext4, /tmp is tmpfs.):
  # mkdir -p /var/overlayfs-socket
  # cd /var/overlayfs-socket
  # mkdir root rofs /tmp/cow
  # mount -t overlayfs -o "upperdir=/tmp/cow,lowerdir=rofs" overlayfs root
  # ssh -NMS root/socket alkisg@localhost
  alkisg@localhost's password: []

  And on another tab of the same terminal:
  # ssh -S root/socket alkisg@localhost ls
  Control socket connect(root/socket): Connection refused
  alkisg@localhost's password: 

  The problem is in the last line, on real filesystems or on tmpfs it
  doesn't ask for a password, it reuses the existing socket.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-7-generic 3.12.0-7.15
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic i686
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alkisg 3511 F pulseaudio
   /dev/snd/controlC0:  alkisg 3511 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Dec 18 18:57:18 2013
  HibernationDevice: RESUME=UUID=5eff7bf1-95b5-4fc1-9c71-0950810c717e
  InstallationDate: Installed on 2013-10-31 (48 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20131021.1)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic 
root=UUID=e1f06e01-d2dc-45e5-b446-54e1e4a5dc2c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-7-generic N/A
   linux-backports-modules-3.12.0-7-generic  N/A
   linux-firmware1.117
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.vers

[Kernel-packages] [Bug 1262287] Re: SSH sockets on overlayfs report connection refused

[Alkis Georgopoulos]

AFAIK, overlayfs is not mainlined yet.

The problem I reported exists in the Ubuntu patched kernels of at least
Precise, Raring and Trusty though.

** 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/1262287

Title:
  SSH sockets on overlayfs report connection refused

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Reusing a master ssh socket that is created on an overlayfs mount
  reports connection refused, while on real filesystems or on tmpfs it
  works fine.

  Steps to reproduce (/var is ext4, /tmp is tmpfs.):
  # mkdir -p /var/overlayfs-socket
  # cd /var/overlayfs-socket
  # mkdir root rofs /tmp/cow
  # mount -t overlayfs -o "upperdir=/tmp/cow,lowerdir=rofs" overlayfs root
  # ssh -NMS root/socket alkisg@localhost
  alkisg@localhost's password: []

  And on another tab of the same terminal:
  # ssh -S root/socket alkisg@localhost ls
  Control socket connect(root/socket): Connection refused
  alkisg@localhost's password: 

  The problem is in the last line, on real filesystems or on tmpfs it
  doesn't ask for a password, it reuses the existing socket.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.12.0-7-generic 3.12.0-7.15
  ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4
  Uname: Linux 3.12.0-7-generic i686
  ApportVersion: 2.12.7-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  alkisg 3511 F pulseaudio
   /dev/snd/controlC0:  alkisg 3511 F pulseaudio
  CurrentDesktop: GNOME
  Date: Wed Dec 18 18:57:18 2013
  HibernationDevice: RESUME=UUID=5eff7bf1-95b5-4fc1-9c71-0950810c717e
  InstallationDate: Installed on 2013-10-31 (48 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20131021.1)
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.12.0-7-generic 
root=UUID=e1f06e01-d2dc-45e5-b446-54e1e4a5dc2c ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.12.0-7-generic N/A
   linux-backports-modules-3.12.0-7-generic  N/A
   linux-firmware1.117
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0415
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P5KPL-AM EPU
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: x.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0415:bd02/04/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KPL-AMEPU:rvrx.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1262287/+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 853244] Re: 8086:0046 Acer Aspire 5742Z brightness keys not working

[Alkis Georgopoulos]

Hi Christopher, as mentioned in my other kernel related bug reports I
just didn't know that launchpad wasn't the appropriate place to report
kernel bugs. So for some of my bug reports I provided feedback for 3-4
years and the only result I got was the occasional "can we close it
now?" answer.

I'll be reporting them upstream from now on, except for any ubuntu-specific 
ones, so feel free to close this one too.
Thanks, and wishes for a happy new year to you.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/853244

Title:
  8086:0046 Acer Aspire 5742Z brightness keys not working

Status in The Linux Kernel:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  In 2.6.32 (Lucid) there's an
  /sys/devices/virtual/backlight/acpi_video0 interface for Aspire 5742Z,
  and brightness hotkeys do modify the values of the files in that dir,
  but the actual laptop brightness isn't changed.

  In 3.0.0-9 (Oneiric beta 1) there's no /sys/devices/virtual/backlight
  interface at all.

  If I boot with acpi=off, the brightness keys correctly modify
  brightness, but of course I lose all other ACPI functionality.

  I tried some of the other acpi-related kernel parameters 
(acpi_backlight=vendor etc) mentioned in
   * https://wiki.ubuntu.com/Kernel/Debugging/Backlight
   * https://wiki.ubuntu.com/DebuggingACPI
   * www.kernel.org/doc/Documentation/kernel-parameters.txt
   * http://www.lesswatts.org/projects/acpi/debug.php
  to no avail, brightness only works with acpi=off or acpi=ht.

  I tried the fwts tool for ACPI testing, and it produced some errors,
  I'm attaching the output. I also tried playing with acpiexec, but
  calling the _BCM method didn't change the brightness either.

  WORKAROUND: echo 123 > /sys/class/backlight/intel_backlight/brightness

  WORKAROUND: If I boot with `acpi_osi=Linux` in the kernel command
  line, I can change the brightness, but the brightness window doesn't
  pop up.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-24-generic 3.2.0-24.37
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0: alkisg 1705 F xfce4-volumed
    alkisg 1736 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xb440 irq 44'
     Mixer name : 'Intel IbexPeak HDMI'
     Components : 'HDA:10ec0272,10250487,0011 
HDA:80862804,80860101,0010'
     Controls : 27
     Simple ctrls : 13
  Date: Fri May 18 07:51:58 2012
  HibernationDevice: RESUME=UUID=52f7a35f-fad8-4c9d-baf1-3d3087278f3c
  InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120201.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 003: ID 064e:c21c Suyin Corp.
  MachineType: Acer Aspire 5742Z
  ProcEnviron:
   LANGUAGE=el:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic 
root=UUID=9ba52df4-ec9e-4e1c-bbd7-322f50437f94 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic N/A
   linux-backports-modules-3.2.0-24-generic N/A
   linux-firmware 1.79
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5742Z
  dmi.board.vendor: Acer
  dmi.board.version: V1.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.24
  dmi.modalias: 
dmi:bvnAcer:bvrV1.24:bd08/10/2011:svnAcer:pnAspire5742Z:pvrV1.24:rvnAcer:rnAspire5742Z:rvrV1.24:cvnAcer:ct10:cvrV1.24:
  dmi.product.name: Aspire 5742Z
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/853244/+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 853244] Re: Acer Aspire 5742Z brightness keys not working

[Alkis Georgopoulos]

Hi! No, updating the BIOS didn't change anything at all.

$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
V1.30
08/13/2012

I tried both with the raring kernel (3.8.0-33-generic ) on my Precise system,
and with a Trusty daily live CD, with the same results as usual.

Summary:
 * The brightness keys make the brightness window pop up, but the brightness 
isn't changed at all.
 * Comment #22 from ag200spr does apply to me. So it is possible to change the 
brightness by e.g.
   # echo 123 > /sys/class/backlight/intel_backlight/brightness
 * If I boot with `acpi_osi=Linux` in the kernel command line, I can change the 
brightness,
   but the brightness window doesn't pop up.

So fixing the problem should be easy, if some upstream developer was
actually interested in this.

Thanks,
Alkis

** Changed in: linux (Ubuntu)
   Status: Incomplete => Triaged

-- 
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/853244

Title:
  Acer Aspire 5742Z brightness keys not working

Status in The Linux Kernel:
  New
Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  In 2.6.32 (Lucid) there's an
  /sys/devices/virtual/backlight/acpi_video0 interface for Aspire 5742Z,
  and brightness hotkeys do modify the values of the files in that dir,
  but the actual laptop brightness isn't changed.

  In 3.0.0-9 (Oneiric beta 1) there's no /sys/devices/virtual/backlight
  interface at all.

  If I boot with acpi=off, the brightness keys correctly modify
  brightness, but of course I lose all other ACPI functionality.

  I tried some of the other acpi-related kernel parameters 
(acpi_backlight=vendor etc) mentioned in
   * https://wiki.ubuntu.com/Kernel/Debugging/Backlight
   * https://wiki.ubuntu.com/DebuggingACPI
   * www.kernel.org/doc/Documentation/kernel-parameters.txt
   * http://www.lesswatts.org/projects/acpi/debug.php
  to no avail, brightness only works with acpi=off or acpi=ht.

  I tried the fwts tool for ACPI testing, and it produced some errors, I'm 
attaching the output.
  I also tried playing with acpiexec, but calling the _BCM method didn't change 
the brightness either.

  `ubuntu-bug linux` doesn't work from the oneiric beta live CD, I'll
  manually attach lspci etc as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-24-generic 3.2.0-24.37
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0: alkisg 1705 F xfce4-volumed
alkisg 1736 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xb440 irq 44'
 Mixer name : 'Intel IbexPeak HDMI'
 Components : 'HDA:10ec0272,10250487,0011 
HDA:80862804,80860101,0010'
 Controls : 27
 Simple ctrls : 13
  Date: Fri May 18 07:51:58 2012
  HibernationDevice: RESUME=UUID=52f7a35f-fad8-4c9d-baf1-3d3087278f3c
  InstallationMedia: Xubuntu 12.04 "Precise Pangolin" - Alpha amd64 (20120201.1)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 003: ID 064e:c21c Suyin Corp.
  MachineType: Acer Aspire 5742Z
  ProcEnviron:
   LANGUAGE=el:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=el_GR.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic 
root=UUID=9ba52df4-ec9e-4e1c-bbd7-322f50437f94 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic N/A
   linux-backports-modules-3.2.0-24-generic N/A
   linux-firmware 1.79
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V1.24
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Aspire 5742Z
  dmi.board.vendor: Acer
  dmi.board.version: V1.24
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.24
  dmi.modalias: 
dmi:bvnAcer:bvrV1.24:bd08/10/2011:svnAcer:pnAspire5742Z:pvrV1.24:rvnAcer:rnAspire5742Z:rvrV1.24:cvnAcer:ct10:cvrV1.24:
  dmi.product.name: Aspire 5742Z
  dmi.product.version: V1.24
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/853244/+subscriptions

-- 
Mailing list: https://launchpad.net/~ke