[Kernel-packages] [Bug 1874453] Re: ubuntu/focal64 very slow to boot and reboots once

2020-05-22 Thread Reinier Schoof 
It's still very slow. When I don't attach a serial device like you gave
an example for to the virtualbox, it still has that 90s pause between
mentioned 'printk' lines during booting and booting is slow in general.

When I do attach the serial device, it still panics the first time, but
the whole thing is so fast that vagrant doesn't notice or times out. So
that setup is now workable. Still doesn't explain why it behaves so
strange without a serial device.

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

Title:
  ubuntu/focal64 very slow to boot and reboots once

Status in cloud-images:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Using `ubuntu/focal64` version `20200423.0.0`, the boot process is
  extremely slow and the box always reboots once before completing a
  successful boot.  With default settings, this causes a timeout in
  Vagrant waiting for SSH to be available.  Setting a long enough
  timeout it does eventually boot successfully.  For comparison,
  `ubuntu/bionic64` boots successfully in roughly 10 seconds on my
  machine.

  This appears to be the big hang-up:

  Apr 23 14:00:12 ubuntu-focal kernel: [0.219784] printk: console [tty1] 
enabled
  Apr 23 14:00:12 ubuntu-focal kernel: [   76.448371] printk: console [ttyS0] 
enabled

  I have a hard time telling where exactly it reboots because my
  /var/log/syslog only ends up with the second boot.  I can watch it in
  Virtualbox though and it suddenly reboots, then the second boot
  process runs to completion.  The long delay shown above happens both
  times making the total time to a successful boot very long.  Here is
  the head of my /var/log/syslog:

  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Remount Root and Kernel 
File Systems.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Uncomplicated firewall.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting FUSE Control File System...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounting Kernel Configuration File 
System...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Rebuild 
Hardware Database being skipped.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Flush Journal to Persistent 
Storage...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Condition check resulted in Platform 
Persistent Storage Archival being skipped.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Load/Save Random Seed...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Apply Kernel Variables...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create System Users...
  Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting 
net/ipv4/conf/all/promote_secondaries (explicit setting exists).
  Apr 23 14:00:12 ubuntu-focal systemd-sysctl[434]: Not setting 
net/ipv4/conf/default/promote_secondaries (explicit setting exists).
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished udev Coldplug all Devices.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted FUSE Control File System.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Mounted Kernel Configuration File 
System.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Flush Journal to Persistent 
Storage.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Load/Save Random Seed.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Apply Kernel Variables.
  Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating group 
systemd-coredump with gid 999.
  Apr 23 14:00:12 ubuntu-focal systemd-sysusers[435]: Creating user 
systemd-coredump (systemd Core Dumper) with uid 999 and gid 999.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Wait for Complete 
Device Initialization...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create System Users.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting Create Static Device Nodes 
in /dev...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Finished Create Static Device Nodes 
in /dev.
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Starting udev Kernel Device 
Manager...
  Apr 23 14:00:12 ubuntu-focal systemd[1]: Started udev Kernel Device Manager.
  Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Linux version 
5.4.0-26-generic (buildd@lcy01-amd64-029) (gcc version 9.3.0 (Ubuntu 
9.3.0-10ubuntu2)) #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 (
  Ubuntu 5.4.0-26.30-generic 5.4.30)
  Apr 23 14:00:12 ubuntu-focal kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=PARTUUID=fac6339f-01 ro 
console=tty1 console=ttyS0

  
  Subsequent boots are also slow but don't seem to have the extra reboot.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 May  7 16:02 seq
   crw-rw 1 root audio 116, 33 May  7 16:02 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No su

[Kernel-packages] [Bug 1776616] Re: Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-Off"

2018-08-07 Thread Schoof 
hardware: IBM thinkpad T41p
xubuntu version 18.04 LTS 32bit

Moin,
got same problem with my elderly machine since installing with 4.15.0.20. 
Actual kernel 4.15.0-30-generic. Thought, it could depend on old BIOS (AHCI) 
with my pentium M. It appears with reboot - normal shutdown normally works. 
Don't remember problems with xubuntu 16/17 versions.

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

Title:
  Ubuntu 18.04 getting stuck at "Starting Reboot" and "Starting Power-
  Off"

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  Incomplete

Bug description:
  Hardware: HPE ProLiant DL360 gen9
  Ubuntu Version: 18.04

  Problem: When rebooting the server, everything goes well (shutting
  down services, unmounting etc) until the last step where it reads
  "Starting Reboot". At this point the system is getting stuck and
  nothing else can can be done than holding the power button in for a
  long enough time to turn it off. At the same time as the system get
  stuck, a red error light is lightening up on the server. This light is
  green until it reaches this "Starting Reboot" stage. The same happens
  if the server is shutdown, with the difference that the last message
  is "Starting Power-Off" instead of "Starting Reboot".

  The server is installed with a new clean 18.04 installation. This
  server was rebooting/shutting down without a problem with all releases
  between 16.04 and 17.10.

  This problem is serious as it prevents remote reboot.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Jun 13 11:16 seq
   crw-rw 1 root audio 116, 33 Jun 13 11:16 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=none
  MachineType: HP ProLiant DL360 Gen9
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 mgadrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic 
root=ZFS=rpool/ROOT/ubuntu ro
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 05/21/2018
  dmi.bios.vendor: HP
  dmi.bios.version: P89
  dmi.board.name: ProLiant DL360 Gen9
  dmi.board.vendor: HP
  dmi.chassis.type: 23
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrP89:bd05/21/2018:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr:
  dmi.product.family: ProLiant
  dmi.product.name: ProLiant DL360 Gen9
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776616/+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 1724639] Re: Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

2017-11-01 Thread Schoof 
"GRUB_GFXPAYLOAD_LINUX=text" works with ideapad S10-2 (Atom with Intel
Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics
Controller rev 03) after kicking out noplymouth für quiet splash.

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

Title:
  Bug in Kernel 4.13 : Intel Mobile Graphics 945 shows 80 % black screen

Status in linux package in Ubuntu:
  Confirmed
Status in openSUSE:
  Unknown

Bug description:
  Installed O.S. on Samsung NC10. Display worked O.K. in text mode so
  the install went smoothly. When the system is rebooted, however,
  switching to graphics mode results in the below described screen
  corruption:-

  Left  Hand Side 80% of screen black with a blue of white pixels and some blue 
lines at the top
  Right Hand Side 20% of screen OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-16-generic 4.13.0-16.19
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.13.0-16-generic.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: ALC272 Analog [ALC272 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian 918 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf034 irq 25'
 Mixer name : 'Realtek ALC272'
 Components : 'HDA:10ec0272,144dca00,0011'
 Controls  : 25
 Simple ctrls  : 12
  CurrentDesktop: LXDE
  Date: Wed Oct 18 18:30:15 2017
  HibernationDevice: RESUME=UUID=c54e130e-6625-4d96-ba75-4efaa6a9da75
  InstallationDate: Installed on 2017-10-18 (0 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. NC10
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=d74a58ab-e96e-4531-a2eb-13f0d1610658 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-16-generic N/A
   linux-backports-modules-4.13.0-16-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2009
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 07CA.M002.20090414.KTW
  dmi.board.name: NC10
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr07CA.M002.20090414.KTW:bd04/14/2009:svnSAMSUNGELECTRONICSCO.,LTD.:pnNC10:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNC10:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: NC10
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1724639/+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