from:"Frédéric"

apport information

** Attachment added: "ProcMisc.txt"
   
https://bugs.launchpad.net/bugs/2015994/+attachment/5663275/+files/ProcMisc.txt

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

Title:
  23.04 installer display broken with fbdev on ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  latest cloud image ( Daily Build [20230405] : 
https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img 
) , especially kernel 6.2.0-19-generic used, has the same issue as the
  one I encountered on Debian : 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 .
  qemu vga output with fbdev gets stuck at kernel boot time while serial 
console looks ok till login prompt .

  I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu-
  server/daily-live/current/lunar-live-server-ppc64el.iso soon.

  I open this bug to monitor the upstream fix Cyril Brulebois proposed
  and hopefully get it into Ubuntu asap.

  Thanks,
  F.
  --- 
  ProblemType: Bug
  .var.log.platform:
   
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 12 12:49 seq
   crw-rw 1 root audio 116, 33 Apr 12 12:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: ppc64le
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230405
  CloudSubPlatform: config-disk (/dev/sr0)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci-vt:
   -[:00]-+-00.0  Device 1234:
  +-01.0  NEC Corporation uPD720200 USB 3.0 Host Controller
  \-02.0  Red Hat, Inc. Virtio network device
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
   XDG_RUNTIME_DIR=
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic 
root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk
  ProcLoadAvg: 0.06 0.05 0.02 1/109 938
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 597 08:01:73471 0 EOF
   2: FLOCK  ADVISORY  WRITE 585 00:18:949 0 EOF
   3: POSIX  ADVISORY  WRITE 311 00:18:436 0 EOF
  ProcSwaps: Filename   TypeSize
UsedPriority
  ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) 
(powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU 
Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-19-generic N/A
   linux-backports-modules-6.2.0-19-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-19-generic ppc64le
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_dscr: DSCR is 0
  cpu_freq:
   Tool Computed frequencies
   min  :   2.293 GHz (cpu 0)
   max  :   2.293 GHz (cpu 0)
   avg  :   2.293 GHz
  cpu_runmode: run-mode=0
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

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

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/2015994/+attachment/5663274/+files/ProcInterrupts.txt

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

Title:
  23.04 installer display broken with fbdev on ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  latest cloud image ( Daily Build [20230405] : 
https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img 
) , especially kernel 6.2.0-19-generic used, has the same issue as the
  one I encountered on Debian : 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 .
  qemu vga output with fbdev gets stuck at kernel boot time while serial 
console looks ok till login prompt .

  I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu-
  server/daily-live/current/lunar-live-server-ppc64el.iso soon.

  I open this bug to monitor the upstream fix Cyril Brulebois proposed
  and hopefully get it into Ubuntu asap.

  Thanks,
  F.
  --- 
  ProblemType: Bug
  .var.log.platform:
   
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 12 12:49 seq
   crw-rw 1 root audio 116, 33 Apr 12 12:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: ppc64le
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230405
  CloudSubPlatform: config-disk (/dev/sr0)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci-vt:
   -[:00]-+-00.0  Device 1234:
  +-01.0  NEC Corporation uPD720200 USB 3.0 Host Controller
  \-02.0  Red Hat, Inc. Virtio network device
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
   XDG_RUNTIME_DIR=
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic 
root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk
  ProcLoadAvg: 0.06 0.05 0.02 1/109 938
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 597 08:01:73471 0 EOF
   2: FLOCK  ADVISORY  WRITE 585 00:18:949 0 EOF
   3: POSIX  ADVISORY  WRITE 311 00:18:436 0 EOF
  ProcSwaps: Filename   TypeSize
UsedPriority
  ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) 
(powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU 
Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-19-generic N/A
   linux-backports-modules-6.2.0-19-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-19-generic ppc64le
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_dscr: DSCR is 0
  cpu_freq:
   Tool Computed frequencies
   min  :   2.293 GHz (cpu 0)
   max  :   2.293 GHz (cpu 0)
   avg  :   2.293 GHz
  cpu_runmode: run-mode=0
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

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

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/2015994/+attachment/5663278/+files/WifiSyslog.txt

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

Title:
  23.04 installer display broken with fbdev on ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  latest cloud image ( Daily Build [20230405] : 
https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img 
) , especially kernel 6.2.0-19-generic used, has the same issue as the
  one I encountered on Debian : 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 .
  qemu vga output with fbdev gets stuck at kernel boot time while serial 
console looks ok till login prompt .

  I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu-
  server/daily-live/current/lunar-live-server-ppc64el.iso soon.

  I open this bug to monitor the upstream fix Cyril Brulebois proposed
  and hopefully get it into Ubuntu asap.

  Thanks,
  F.
  --- 
  ProblemType: Bug
  .var.log.platform:
   
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 12 12:49 seq
   crw-rw 1 root audio 116, 33 Apr 12 12:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: ppc64le
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230405
  CloudSubPlatform: config-disk (/dev/sr0)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci-vt:
   -[:00]-+-00.0  Device 1234:
  +-01.0  NEC Corporation uPD720200 USB 3.0 Host Controller
  \-02.0  Red Hat, Inc. Virtio network device
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
   XDG_RUNTIME_DIR=
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic 
root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk
  ProcLoadAvg: 0.06 0.05 0.02 1/109 938
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 597 08:01:73471 0 EOF
   2: FLOCK  ADVISORY  WRITE 585 00:18:949 0 EOF
   3: POSIX  ADVISORY  WRITE 311 00:18:436 0 EOF
  ProcSwaps: Filename   TypeSize
UsedPriority
  ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) 
(powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU 
Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-19-generic N/A
   linux-backports-modules-6.2.0-19-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-19-generic ppc64le
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_dscr: DSCR is 0
  cpu_freq:
   Tool Computed frequencies
   min  :   2.293 GHz (cpu 0)
   max  :   2.293 GHz (cpu 0)
   avg  :   2.293 GHz
  cpu_runmode: run-mode=0
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

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

apport information

** Attachment added: "nvram.gz"
   https://bugs.launchpad.net/bugs/2015994/+attachment/5663279/+files/nvram.gz

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

Title:
  23.04 installer display broken with fbdev on ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  latest cloud image ( Daily Build [20230405] : 
https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img 
) , especially kernel 6.2.0-19-generic used, has the same issue as the
  one I encountered on Debian : 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 .
  qemu vga output with fbdev gets stuck at kernel boot time while serial 
console looks ok till login prompt .

  I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu-
  server/daily-live/current/lunar-live-server-ppc64el.iso soon.

  I open this bug to monitor the upstream fix Cyril Brulebois proposed
  and hopefully get it into Ubuntu asap.

  Thanks,
  F.
  --- 
  ProblemType: Bug
  .var.log.platform:
   
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 12 12:49 seq
   crw-rw 1 root audio 116, 33 Apr 12 12:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: ppc64le
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230405
  CloudSubPlatform: config-disk (/dev/sr0)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci-vt:
   -[:00]-+-00.0  Device 1234:
  +-01.0  NEC Corporation uPD720200 USB 3.0 Host Controller
  \-02.0  Red Hat, Inc. Virtio network device
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
   XDG_RUNTIME_DIR=
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic 
root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk
  ProcLoadAvg: 0.06 0.05 0.02 1/109 938
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 597 08:01:73471 0 EOF
   2: FLOCK  ADVISORY  WRITE 585 00:18:949 0 EOF
   3: POSIX  ADVISORY  WRITE 311 00:18:436 0 EOF
  ProcSwaps: Filename   TypeSize
UsedPriority
  ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) 
(powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU 
Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-19-generic N/A
   linux-backports-modules-6.2.0-19-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-19-generic ppc64le
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_dscr: DSCR is 0
  cpu_freq:
   Tool Computed frequencies
   min  :   2.293 GHz (cpu 0)
   max  :   2.293 GHz (cpu 0)
   avg  :   2.293 GHz
  cpu_runmode: run-mode=0
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

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

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/2015994/+attachment/5663276/+files/ProcModules.txt

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

Title:
  23.04 installer display broken with fbdev on ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  latest cloud image ( Daily Build [20230405] : 
https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img 
) , especially kernel 6.2.0-19-generic used, has the same issue as the
  one I encountered on Debian : 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 .
  qemu vga output with fbdev gets stuck at kernel boot time while serial 
console looks ok till login prompt .

  I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu-
  server/daily-live/current/lunar-live-server-ppc64el.iso soon.

  I open this bug to monitor the upstream fix Cyril Brulebois proposed
  and hopefully get it into Ubuntu asap.

  Thanks,
  F.
  --- 
  ProblemType: Bug
  .var.log.platform:
   
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 12 12:49 seq
   crw-rw 1 root audio 116, 33 Apr 12 12:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: ppc64le
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230405
  CloudSubPlatform: config-disk (/dev/sr0)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci-vt:
   -[:00]-+-00.0  Device 1234:
  +-01.0  NEC Corporation uPD720200 USB 3.0 Host Controller
  \-02.0  Red Hat, Inc. Virtio network device
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
   XDG_RUNTIME_DIR=
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic 
root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk
  ProcLoadAvg: 0.06 0.05 0.02 1/109 938
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 597 08:01:73471 0 EOF
   2: FLOCK  ADVISORY  WRITE 585 00:18:949 0 EOF
   3: POSIX  ADVISORY  WRITE 311 00:18:436 0 EOF
  ProcSwaps: Filename   TypeSize
UsedPriority
  ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) 
(powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU 
Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-19-generic N/A
   linux-backports-modules-6.2.0-19-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-19-generic ppc64le
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_dscr: DSCR is 0
  cpu_freq:
   Tool Computed frequencies
   min  :   2.293 GHz (cpu 0)
   max  :   2.293 GHz (cpu 0)
   avg  :   2.293 GHz
  cpu_runmode: run-mode=0
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

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

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/2015994/+attachment/5663277/+files/UdevDb.txt

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

Title:
  23.04 installer display broken with fbdev on ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  latest cloud image ( Daily Build [20230405] : 
https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img 
) , especially kernel 6.2.0-19-generic used, has the same issue as the
  one I encountered on Debian : 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 .
  qemu vga output with fbdev gets stuck at kernel boot time while serial 
console looks ok till login prompt .

  I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu-
  server/daily-live/current/lunar-live-server-ppc64el.iso soon.

  I open this bug to monitor the upstream fix Cyril Brulebois proposed
  and hopefully get it into Ubuntu asap.

  Thanks,
  F.
  --- 
  ProblemType: Bug
  .var.log.platform:
   
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 12 12:49 seq
   crw-rw 1 root audio 116, 33 Apr 12 12:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: ppc64le
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230405
  CloudSubPlatform: config-disk (/dev/sr0)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci-vt:
   -[:00]-+-00.0  Device 1234:
  +-01.0  NEC Corporation uPD720200 USB 3.0 Host Controller
  \-02.0  Red Hat, Inc. Virtio network device
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
   XDG_RUNTIME_DIR=
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic 
root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk
  ProcLoadAvg: 0.06 0.05 0.02 1/109 938
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 597 08:01:73471 0 EOF
   2: FLOCK  ADVISORY  WRITE 585 00:18:949 0 EOF
   3: POSIX  ADVISORY  WRITE 311 00:18:436 0 EOF
  ProcSwaps: Filename   TypeSize
UsedPriority
  ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) 
(powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU 
Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-19-generic N/A
   linux-backports-modules-6.2.0-19-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-19-generic ppc64le
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_dscr: DSCR is 0
  cpu_freq:
   Tool Computed frequencies
   min  :   2.293 GHz (cpu 0)
   max  :   2.293 GHz (cpu 0)
   avg  :   2.293 GHz
  cpu_runmode: run-mode=0
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

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

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/2015994/+attachment/5663272/+files/ProcCpuinfo.txt

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

Title:
  23.04 installer display broken with fbdev on ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  latest cloud image ( Daily Build [20230405] : 
https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img 
) , especially kernel 6.2.0-19-generic used, has the same issue as the
  one I encountered on Debian : 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 .
  qemu vga output with fbdev gets stuck at kernel boot time while serial 
console looks ok till login prompt .

  I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu-
  server/daily-live/current/lunar-live-server-ppc64el.iso soon.

  I open this bug to monitor the upstream fix Cyril Brulebois proposed
  and hopefully get it into Ubuntu asap.

  Thanks,
  F.
  --- 
  ProblemType: Bug
  .var.log.platform:
   
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 12 12:49 seq
   crw-rw 1 root audio 116, 33 Apr 12 12:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: ppc64le
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230405
  CloudSubPlatform: config-disk (/dev/sr0)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci-vt:
   -[:00]-+-00.0  Device 1234:
  +-01.0  NEC Corporation uPD720200 USB 3.0 Host Controller
  \-02.0  Red Hat, Inc. Virtio network device
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
   XDG_RUNTIME_DIR=
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic 
root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk
  ProcLoadAvg: 0.06 0.05 0.02 1/109 938
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 597 08:01:73471 0 EOF
   2: FLOCK  ADVISORY  WRITE 585 00:18:949 0 EOF
   3: POSIX  ADVISORY  WRITE 311 00:18:436 0 EOF
  ProcSwaps: Filename   TypeSize
UsedPriority
  ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) 
(powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU 
Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-19-generic N/A
   linux-backports-modules-6.2.0-19-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-19-generic ppc64le
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_dscr: DSCR is 0
  cpu_freq:
   Tool Computed frequencies
   min  :   2.293 GHz (cpu 0)
   max  :   2.293 GHz (cpu 0)
   avg  :   2.293 GHz
  cpu_runmode: run-mode=0
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

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

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/2015994/+attachment/5663271/+files/Lsusb-v.txt

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

Title:
  23.04 installer display broken with fbdev on ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  latest cloud image ( Daily Build [20230405] : 
https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img 
) , especially kernel 6.2.0-19-generic used, has the same issue as the
  one I encountered on Debian : 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 .
  qemu vga output with fbdev gets stuck at kernel boot time while serial 
console looks ok till login prompt .

  I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu-
  server/daily-live/current/lunar-live-server-ppc64el.iso soon.

  I open this bug to monitor the upstream fix Cyril Brulebois proposed
  and hopefully get it into Ubuntu asap.

  Thanks,
  F.
  --- 
  ProblemType: Bug
  .var.log.platform:
   
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 12 12:49 seq
   crw-rw 1 root audio 116, 33 Apr 12 12:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: ppc64le
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230405
  CloudSubPlatform: config-disk (/dev/sr0)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci-vt:
   -[:00]-+-00.0  Device 1234:
  +-01.0  NEC Corporation uPD720200 USB 3.0 Host Controller
  \-02.0  Red Hat, Inc. Virtio network device
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
   XDG_RUNTIME_DIR=
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic 
root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk
  ProcLoadAvg: 0.06 0.05 0.02 1/109 938
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 597 08:01:73471 0 EOF
   2: FLOCK  ADVISORY  WRITE 585 00:18:949 0 EOF
   3: POSIX  ADVISORY  WRITE 311 00:18:436 0 EOF
  ProcSwaps: Filename   TypeSize
UsedPriority
  ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) 
(powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU 
Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-19-generic N/A
   linux-backports-modules-6.2.0-19-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-19-generic ppc64le
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_dscr: DSCR is 0
  cpu_freq:
   Tool Computed frequencies
   min  :   2.293 GHz (cpu 0)
   max  :   2.293 GHz (cpu 0)
   avg  :   2.293 GHz
  cpu_runmode: run-mode=0
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

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

apport information

** Attachment added: "DeviceTree.tar.gz"
   
https://bugs.launchpad.net/bugs/2015994/+attachment/5663269/+files/DeviceTree.tar.gz

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

Title:
  23.04 installer display broken with fbdev on ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  latest cloud image ( Daily Build [20230405] : 
https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img 
) , especially kernel 6.2.0-19-generic used, has the same issue as the
  one I encountered on Debian : 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 .
  qemu vga output with fbdev gets stuck at kernel boot time while serial 
console looks ok till login prompt .

  I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu-
  server/daily-live/current/lunar-live-server-ppc64el.iso soon.

  I open this bug to monitor the upstream fix Cyril Brulebois proposed
  and hopefully get it into Ubuntu asap.

  Thanks,
  F.
  --- 
  ProblemType: Bug
  .var.log.platform:
   
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 12 12:49 seq
   crw-rw 1 root audio 116, 33 Apr 12 12:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: ppc64le
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230405
  CloudSubPlatform: config-disk (/dev/sr0)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci-vt:
   -[:00]-+-00.0  Device 1234:
  +-01.0  NEC Corporation uPD720200 USB 3.0 Host Controller
  \-02.0  Red Hat, Inc. Virtio network device
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
   XDG_RUNTIME_DIR=
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic 
root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk
  ProcLoadAvg: 0.06 0.05 0.02 1/109 938
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 597 08:01:73471 0 EOF
   2: FLOCK  ADVISORY  WRITE 585 00:18:949 0 EOF
   3: POSIX  ADVISORY  WRITE 311 00:18:436 0 EOF
  ProcSwaps: Filename   TypeSize
UsedPriority
  ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) 
(powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU 
Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-19-generic N/A
   linux-backports-modules-6.2.0-19-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-19-generic ppc64le
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_dscr: DSCR is 0
  cpu_freq:
   Tool Computed frequencies
   min  :   2.293 GHz (cpu 0)
   max  :   2.293 GHz (cpu 0)
   avg  :   2.293 GHz
  cpu_runmode: run-mode=0
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

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

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2015994/+attachment/5663273/+files/ProcCpuinfoMinimal.txt

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

Title:
  23.04 installer display broken with fbdev on ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  latest cloud image ( Daily Build [20230405] : 
https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img 
) , especially kernel 6.2.0-19-generic used, has the same issue as the
  one I encountered on Debian : 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 .
  qemu vga output with fbdev gets stuck at kernel boot time while serial 
console looks ok till login prompt .

  I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu-
  server/daily-live/current/lunar-live-server-ppc64el.iso soon.

  I open this bug to monitor the upstream fix Cyril Brulebois proposed
  and hopefully get it into Ubuntu asap.

  Thanks,
  F.
  --- 
  ProblemType: Bug
  .var.log.platform:
   
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 12 12:49 seq
   crw-rw 1 root audio 116, 33 Apr 12 12:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: ppc64le
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230405
  CloudSubPlatform: config-disk (/dev/sr0)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci-vt:
   -[:00]-+-00.0  Device 1234:
  +-01.0  NEC Corporation uPD720200 USB 3.0 Host Controller
  \-02.0  Red Hat, Inc. Virtio network device
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
   XDG_RUNTIME_DIR=
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic 
root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk
  ProcLoadAvg: 0.06 0.05 0.02 1/109 938
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 597 08:01:73471 0 EOF
   2: FLOCK  ADVISORY  WRITE 585 00:18:949 0 EOF
   3: POSIX  ADVISORY  WRITE 311 00:18:436 0 EOF
  ProcSwaps: Filename   TypeSize
UsedPriority
  ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) 
(powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU 
Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-19-generic N/A
   linux-backports-modules-6.2.0-19-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-19-generic ppc64le
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_dscr: DSCR is 0
  cpu_freq:
   Tool Computed frequencies
   min  :   2.293 GHz (cpu 0)
   max  :   2.293 GHz (cpu 0)
   avg  :   2.293 GHz
  cpu_runmode: run-mode=0
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

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

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/2015994/+attachment/5663270/+files/Lspci.txt

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

Title:
  23.04 installer display broken with fbdev on ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  latest cloud image ( Daily Build [20230405] : 
https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img 
) , especially kernel 6.2.0-19-generic used, has the same issue as the
  one I encountered on Debian : 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 .
  qemu vga output with fbdev gets stuck at kernel boot time while serial 
console looks ok till login prompt .

  I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu-
  server/daily-live/current/lunar-live-server-ppc64el.iso soon.

  I open this bug to monitor the upstream fix Cyril Brulebois proposed
  and hopefully get it into Ubuntu asap.

  Thanks,
  F.
  --- 
  ProblemType: Bug
  .var.log.platform:
   
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Apr 12 12:49 seq
   crw-rw 1 root audio 116, 33 Apr 12 12:49 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: ppc64el
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: ppc64le
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial: 20230405
  CloudSubPlatform: config-disk (/dev/sr0)
  DistroRelease: Ubuntu 23.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci-vt:
   -[:00]-+-00.0  Device 1234:
  +-01.0  NEC Corporation uPD720200 USB 3.0 Host Controller
  \-02.0  Red Hat, Inc. Virtio network device
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
   |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=vt220
   XDG_RUNTIME_DIR=
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic 
root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk
  ProcLoadAvg: 0.06 0.05 0.02 1/109 938
  ProcLocks:
   1: FLOCK  ADVISORY  WRITE 597 08:01:73471 0 EOF
   2: FLOCK  ADVISORY  WRITE 585 00:18:949 0 EOF
   3: POSIX  ADVISORY  WRITE 311 00:18:436 0 EOF
  ProcSwaps: Filename   TypeSize
UsedPriority
  ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) 
(powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU 
Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023
  ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-19-generic N/A
   linux-backports-modules-6.2.0-19-generic  N/A
   linux-firmwareN/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags: cloud-image lunar
  Uname: Linux 6.2.0-19-generic ppc64le
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  acpidump:
   
  cpu_cores: Number of cores present = 1
  cpu_coreson: Number of cores online = 1
  cpu_dscr: DSCR is 0
  cpu_freq:
   Tool Computed frequencies
   min  :   2.293 GHz (cpu 0)
   max  :   2.293 GHz (cpu 0)
   avg  :   2.293 GHz
  cpu_runmode: run-mode=0
  cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+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 2015994] Re: 23.04 installer display broken with fbdev on ppc64el

apport information

** Tags added: apport-collected cloud-image lunar

** Description changed:

  Hi,
  
  latest cloud image ( Daily Build [20230405] : 
https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img 
) , especially kernel 6.2.0-19-generic used, has the same issue as the
  one I encountered on Debian : 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 .
  qemu vga output with fbdev gets stuck at kernel boot time while serial 
console looks ok till login prompt .
  
  I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu-
  server/daily-live/current/lunar-live-server-ppc64el.iso soon.
  
  I open this bug to monitor the upstream fix Cyril Brulebois proposed and
  hopefully get it into Ubuntu asap.
  
  Thanks,
  F.
+ --- 
+ ProblemType: Bug
+ .var.log.platform:
+  
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Apr 12 12:49 seq
+  crw-rw 1 root audio 116, 33 Apr 12 12:49 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
+ ApportVersion: 2.26.0-0ubuntu2
+ Architecture: ppc64el
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: N/A
+ CasperMD5CheckResult: unknown
+ CloudArchitecture: ppc64le
+ CloudBuildName: server
+ CloudID: nocloud
+ CloudName: unknown
+ CloudPlatform: nocloud
+ CloudSerial: 20230405
+ CloudSubPlatform: config-disk (/dev/sr0)
+ DistroRelease: Ubuntu 23.04
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
+ Lspci-vt:
+  -[:00]-+-00.0  Device 1234:
+ +-01.0  NEC Corporation uPD720200 USB 3.0 Host Controller
+ \-02.0  Red Hat, Inc. Virtio network device
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 003: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Mouse
+  Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Keyboard
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ Lsusb-t:
+  /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 5000M
+  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 480M
+  |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
+  |__ Port 2: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  LANG=C.UTF-8
+  PATH=(custom, no user)
+  SHELL=/bin/bash
+  TERM=vt220
+  XDG_RUNTIME_DIR=
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinux-6.2.0-19-generic 
root=LABEL=cloudimg-rootfs ro console=hvc0 earlyprintk
+ ProcLoadAvg: 0.06 0.05 0.02 1/109 938
+ ProcLocks:
+  1: FLOCK  ADVISORY  WRITE 597 08:01:73471 0 EOF
+  2: FLOCK  ADVISORY  WRITE 585 00:18:949 0 EOF
+  3: POSIX  ADVISORY  WRITE 311 00:18:436 0 EOF
+ ProcSwaps: Filename   TypeSize
UsedPriority
+ ProcVersion: Linux version 6.2.0-19-generic (buildd@bos02-ppc64el-009) 
(powerpc64le-linux-gnu-gcc-12 (Ubuntu 12.2.0-17ubuntu1) 12.2.0, GNU ld (GNU 
Binutils for Ubuntu) 2.40) #19-Ubuntu SMP Sat Mar 25 10:13:41 UTC 2023
+ ProcVersionSignature: Ubuntu 6.2.0-19.19-generic 6.2.6
+ RelatedPackageVersions:
+  linux-restricted-modules-6.2.0-19-generic N/A
+  linux-backports-modules-6.2.0-19-generic  N/A
+  linux-firmwareN/A
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
+ Tags: cloud-image lunar
+ Uname: Linux 6.2.0-19-generic ppc64le
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ acpidump:
+  
+ cpu_cores: Number of cores present = 1
+ cpu_coreson: Number of cores online = 1
+ cpu_dscr: DSCR is 0
+ cpu_freq:
+  Tool Computed frequencies
+  min  :   2.293 GHz (cpu 0)
+  max  :   2.293 GHz (cpu 0)
+  avg  :   2.293 GHz
+ cpu_runmode: run-mode=0
+ cpu_smt: Error: command ['ppc64_cpu', '--smt'] failed with exit code 255: 
Machine is not SMT capable

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/2015994/+attachment/5663268/+files/CurrentDmesg.txt

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

Title:
  23.04 installer display broken with fbdev on ppc64el

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  latest cloud image ( Daily Build [20230405] : 
https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img 
) , especially kernel 6.2.0-19-generic used, has the same issue as the
  one I encountered on Debian : 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 .
  qemu vga output with fbdev gets stuck at kernel boot time while serial 
console looks ok till login prompt .

  I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu-

[Kernel-packages] [Bug 2015994] Re: 23.04 installer display broken with fbdev on ppc64el

Functional serial output (sorry for the OpenQA artifacts)

** Attachment added: "Serial output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+attachment/5663235/+files/23.04_20230405_qemu_serial_ppc64el.txt

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

Title:
  23.04 installer display broken with fbdev on ppc64el

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  latest cloud image ( Daily Build [20230405] : 
https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img 
) , especially kernel 6.2.0-19-generic used, has the same issue as the
  one I encountered on Debian : 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 .
  qemu vga output with fbdev gets stuck at kernel boot time while serial 
console looks ok till login prompt .

  I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu-
  server/daily-live/current/lunar-live-server-ppc64el.iso soon.

  I open this bug to monitor the upstream fix Cyril Brulebois proposed
  and hopefully get it into Ubuntu asap.

  Thanks,
  F.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+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 2015994] [NEW] 23.04 installer display broken with fbdev on ppc64el

Public bug reported:

Hi,

latest cloud image ( Daily Build [20230405] :
https://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-ppc64el.img
) , especially kernel 6.2.0-19-generic used, has the same issue as the
one I encountered on Debian :
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1033058 .
qemu vga output with fbdev gets stuck at kernel boot time while serial console
looks ok till login prompt .

I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu-
server/daily-live/current/lunar-live-server-ppc64el.iso soon.

I open this bug to monitor the upstream fix Cyril Brulebois proposed and
hopefully get it into Ubuntu asap.

Thanks,
F.

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

** Attachment added: "vga output"

https://bugs.launchpad.net/bugs/2015994/+attachment/5663234/+files/23.04_20230405_qemu_ppc64el.png

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

Title:
23.04 installer display broken with fbdev on ppc64el

Status in linux package in Ubuntu:
Incomplete

Bug description:
Hi,

I guess it's going to propagate to http://cdimage.ubuntu.com/ubuntu-
server/daily-live/current/lunar-live-server-ppc64el.iso soon.

I open this bug to monitor the upstream fix Cyril Brulebois proposed
and hopefully get it into Ubuntu asap.

Thanks,
F.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2015994/+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 1903969] Re: failed to boot to GUI: i915 0000:00:02.0: [drm] ERROR Link Training Unsuccessful

2022-09-14 Thread Frédéric Grosshans

I seem to have the same problem in Jammy with the kernel
5.15.0-47-generic and with the latest firmware updates. The only
difference is dmesg speak of pipe B instead of pipe A:

[  509.965244] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
[  509.990694] i915 :00:02.0: [drm] *ERROR* CPU pipe B FIFO underrun
[  510.270856] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
[ ] 

Is that actually the same bug, or should I open a new one ?

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

Title:
  failed to boot to GUI: i915 :00:02.0: [drm] *ERROR* Link Training
  Unsuccessful

Status in HWE Next:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-5.10 package in Ubuntu:
  Invalid
Status in linux-oem-5.6 package in Ubuntu:
  Invalid
Status in linux source package in Focal:
  Invalid
Status in linux-oem-5.10 source package in Focal:
  Fix Released
Status in linux-oem-5.6 source package in Focal:
  Won't Fix
Status in linux source package in Groovy:
  Won't Fix
Status in linux-oem-5.10 source package in Groovy:
  Invalid
Status in linux-oem-5.6 source package in Groovy:
  Invalid
Status in linux source package in Hirsute:
  Fix Released
Status in linux-oem-5.10 source package in Hirsute:
  Invalid
Status in linux-oem-5.6 source package in Hirsute:
  Invalid

Bug description:
  [SRU Justification]

  [Impact]

  On platforms supported DP tunneling over USB 3.2 or so, a Retimer is
  required on the host side to cover insertion loss. On such platforms the
  rtimer firmware maybe configured to use LTTPR (Link Training Tunable PHY
  Repeater) non-transparent mode only, which is only supported in drm-tip
  currently. Without LTTPR support, link training may fail with following
  error messages depending on the data path configuration:

    i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful
    i915 :00:02.0: [drm] *ERROR* CPU pipe A FIFO underrun

  [Fix]

  Patchset https://www.spinics.net/lists/intel-gfx/msg248700.html
  ("drm/i915: Add support for LTTPR non-transparent link training mode")
  is required to fix this issue. It has been landed to drm-tip and will
  only be merged to mainline in v5.11.

  Patchset https://patchwork.freedesktop.org/series/76993/ ("Plumb crtc
  state to link training code") is included for link training functions
  prototype changes.

  [Test Case]

  On Dell OptiPlex and WD19 docking station, use following steps to verify:
  1. disconnect WD19 from OptiPlex, disconnect OptiPlex's power
  2. attach OptiPlex's power cord
  3. attach WD19's power cord
  4. attach DP to WD19
  5. attach WD19 to OptiPlex
  6. boot up and check if boot to GUI directly
  7. `dmesg` and check if aforementioned DRM link training error appears

  [Where problems could occur]

  The second patchset pulled for dependency doesn't have too much
  effective changes but refactoring some translation functions, so very
  unlikely to have regressions.

  For the major part, LTTPR support, when LTTPR is either not detected or
  not supported, it will fall back to use transparent mode as it was.
  Otherwise, DP Standard recommends to use LTTPR non-transparent mode for
  link training, so this should be the right way to have best hardware
  support.

  == original bug description ==

  [Summary]
  When the monitor ONLY is connected to the WD19 (DP port) and WD19 is 
connected to the type c port than boot the machine, the monitor shows no video 
output after loaded i915.

  [Reproduce Steps]
  1. connect power cable of WD19
  2. connect DP cable from monitor to WD19
  3. connect power cable to target system.
  4. connect type c cable from WD19 to target system
  5. boot up

  [Results]
  Expected: video output as there is only one monitor connected.
  Actual: No video output.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.6.0-1033-oem 5.6.0-1033.35
  ProcVersionSignature: Ubuntu 5.6.0-1033.35-oem 5.6.19
  Uname: Linux 5.6.0-1033-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.11
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Nov 12 05:11:11 2020
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-metapod+X40
  InstallationDate: Installed on 2020-11-03 (9 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  SourcePackage: linux-signed-oem-5.6
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1903969/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe :

[Kernel-packages] [Bug 1888326] [NEW] Bluetooth device not found QCA9565

2020-07-20 Thread Frédéric Annequin

Public bug reported:

Hello,
I run Ubuntu 20.04 LTS on my Acer Aspire E5-573G and Ubuntu can't found my 
bluetooth device.

I have a QCNFA335 (QCA9565) which can normally support both wifi and
bluetooth

I can use both wifi and bluetooth on windows 10.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: bluez 5.53-0ubuntu3
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul 20 20:24:58 2020
InstallationDate: Installed on 2020-07-17 (3 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
InterestingModules: bnep btusb bluetooth
MachineType: Acer Aspire E5-573G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=eec36b7b-bbf9-463c-80a6-6ec698a4d655 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/16/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.37
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: ZORO_BH
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: BDW
dmi.product.name: Aspire E5-573G
dmi.product.sku: Aspire E5-573G_098A_1_37
dmi.product.version: V3.72
dmi.sys.vendor: Acer
hciconfig:

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


** Tags: amd64 apport-bug focal

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

Title:
  Bluetooth device not found QCA9565

Status in bluez package in Ubuntu:
  New

Bug description:
  Hello,
  I run Ubuntu 20.04 LTS on my Acer Aspire E5-573G and Ubuntu can't found my 
bluetooth device.

  I have a QCNFA335 (QCA9565) which can normally support both wifi and
  bluetooth

  I can use both wifi and bluetooth on windows 10.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: bluez 5.53-0ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul 20 20:24:58 2020
  InstallationDate: Installed on 2020-07-17 (3 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  InterestingModules: bnep btusb bluetooth
  MachineType: Acer Aspire E5-573G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic 
root=UUID=eec36b7b-bbf9-463c-80a6-6ec698a4d655 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/16/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.37
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.37:bd02/16/2016:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: Aspire E5-573G
  dmi.product.sku: Aspire E5-573G_098A_1_37
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1888326/+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 1837726] Re: Installation fails on eoan/PowerVM : missing /dev/nvram

2019-09-26 Thread Frédéric Bonnard

Thanks Thadeu, good to know the problem has been identified !
I'll be happy to test the fix.

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

Title:
  Installation fails on eoan/PowerVM : missing /dev/nvram

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Hi,
  since eoan and kernel 5.2, the installation fails when installing grub at the 
end.
  Actually /dev/nvram does not exist.
  nvram support was previously built in the kernel and is now built as a module,
  and the module is not shipped within the iso or in udebs.
  This is probably due to commit d7d73492dc5f2 in Ubuntu's linux git tree :

  ---
  commit d7d73492dc5f2ccc5c76b042341370838af148e4
  Author: Seth Forshee 
  Date:   Wed Jun 5 10:47:33 2019 -0500

  UBUNTU: [Config] update annotations following config review
  ...
  -CONFIG_NVRAMpolicy<{'amd64': 'm', 
'i386': 'm'}>
  +CONFIG_NVRAMpolicy<{'amd64': 'm', 
'i386': 'm', 'ppc64el': 'm'}>
  ...
  ---

  F.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837726/+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 1837726] Re: Installation fails on eoan/PowerVM : missing /dev/nvram

2019-09-23 Thread Frédéric Bonnard

The fix is in 5.3.0-12.13 but trying current 
http://ports.ubuntu.com/ubuntu-ports/dists/eoan-proposed/main/installer-ppc64el/current/images/netboot/mini.iso
 (2019-09-21 81M, 3ed00b52f4335c589f4e1b070107c1af  mini.iso)
the kernel of the installer just panics without much details...

Preparing to boot Linux version 5.3.0-12-generic (buildd@bos02-ppc64el-011) 
(gcc version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)) #13-Ubuntu SMP Tue Sep 17 
12:34:04 UTC 2019 (Ubuntu 5.3.0-12.13-generic 5.3.0)
Detected machine type: 0101command line: 
BOOT_IMAGE=/install/vmlinux tasks=standard pkgsel/language-pack-patterns= 
pkgsel/install-language-support=false --- quiet
Max number of cores passed to firmware: 2048 (NR_CPUS = 2048)
Calling ibm,client-architecture-support... donememory layout at init:
  memory_limit :  (16 MB aligned)
  alloc_bottom : 0708  alloc_top: 3000
  alloc_top_hi : 0001
  rmo_top  : 3000  ram_top  : 0001
instantiating rtas at 0x2fff... done
prom_hold_cpus: skipped
copying OF device tree...
Building dt strings...
Building dt structure...
Device tree strings 0x0709 -> 0x07090a8d
Device tree struct  0x070a -> 0x070b
Quiescing Open Firmware ...
Booting Linux via __start() @ 0x0200 ...
Linux ppc64le
#13-Ubuntu SMP T[0.914674] vio vio: uevent: failed to send synthetic uevent
Failed to write 'add' to '/sys/devices/vio/uevent': No such device
[0.917725] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0100
[0.917815] CPU: 0 PID: 1 Comm: init Not tainted 5.3.0-12-generic #13-Ubuntu
[0.917885] Call Trace:
[0.917913] [c000fa4bfc00] [c0e72108] dump_stack+0xac/0xf4 
(unreliable)
[0.917996] [c000fa4bfc40] [c0126a2c] panic+0x16c/0x400
[0.918119] [c000fa4bfce0] [c012eb70] do_exit+0xca0/0xd40
[0.918206] [c000fa4bfdc0] [c012ece0] do_group_exit+0x60/0x120
[0.918308] [c000fa4bfe00] [c012edc4] sys_exit_group+0x24/0x40
[0.918377] [c000fa4bfe20] [c000b388] system_call+0x5c/0x70

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

Title:
  Installation fails on eoan/PowerVM : missing /dev/nvram

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Hi,
  since eoan and kernel 5.2, the installation fails when installing grub at the 
end.
  Actually /dev/nvram does not exist.
  nvram support was previously built in the kernel and is now built as a module,
  and the module is not shipped within the iso or in udebs.
  This is probably due to commit d7d73492dc5f2 in Ubuntu's linux git tree :

  ---
  commit d7d73492dc5f2ccc5c76b042341370838af148e4
  Author: Seth Forshee 
  Date:   Wed Jun 5 10:47:33 2019 -0500

  UBUNTU: [Config] update annotations following config review
  ...
  -CONFIG_NVRAMpolicy<{'amd64': 'm', 
'i386': 'm'}>
  +CONFIG_NVRAMpolicy<{'amd64': 'm', 
'i386': 'm', 'ppc64el': 'm'}>
  ...
  ---

  F.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837726/+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 1837726] Re: Installation fails on eoan/PowerVM : missing /dev/nvram

2019-09-10 Thread Frédéric Bonnard

Thanks Seth, I'll test this as soon as it's released.

F.

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

Title:
  Installation fails on eoan/PowerVM : missing /dev/nvram

Status in linux package in Ubuntu:
  Fix Committed

Bug description:
  Hi,
  since eoan and kernel 5.2, the installation fails when installing grub at the 
end.
  Actually /dev/nvram does not exist.
  nvram support was previously built in the kernel and is now built as a module,
  and the module is not shipped within the iso or in udebs.
  This is probably due to commit d7d73492dc5f2 in Ubuntu's linux git tree :

  ---
  commit d7d73492dc5f2ccc5c76b042341370838af148e4
  Author: Seth Forshee 
  Date:   Wed Jun 5 10:47:33 2019 -0500

  UBUNTU: [Config] update annotations following config review
  ...
  -CONFIG_NVRAMpolicy<{'amd64': 'm', 
'i386': 'm'}>
  +CONFIG_NVRAMpolicy<{'amd64': 'm', 
'i386': 'm', 'ppc64el': 'm'}>
  ...
  ---

  F.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837726/+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 1837726] Re: Installation fails on eoan/PowerVM : missing /dev/nvram

2019-07-24 Thread Frédéric Bonnard

apport-collect is not available from the installation iso shell

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

Title:
  Installation fails on eoan/PowerVM : missing /dev/nvram

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,
  since eoan and kernel 5.2, the installation fails when installing grub at the 
end.
  Actually /dev/nvram does not exist.
  nvram support was previously built in the kernel and is now built as a module,
  and the module is not shipped within the iso or in udebs.
  This is probably due to commit d7d73492dc5f2 in Ubuntu's linux git tree :

  ---
  commit d7d73492dc5f2ccc5c76b042341370838af148e4
  Author: Seth Forshee 
  Date:   Wed Jun 5 10:47:33 2019 -0500

  UBUNTU: [Config] update annotations following config review
  ...
  -CONFIG_NVRAMpolicy<{'amd64': 'm', 
'i386': 'm'}>
  +CONFIG_NVRAMpolicy<{'amd64': 'm', 
'i386': 'm', 'ppc64el': 'm'}>
  ...
  ---

  F.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837726/+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 1837726] [NEW] Installation fails on eoan/PowerVM : missing /dev/nvram

2019-07-24 Thread Frédéric Bonnard

Public bug reported:

Hi,
since eoan and kernel 5.2, the installation fails when installing grub at the 
end.
Actually /dev/nvram does not exist.
nvram support was previously built in the kernel and is now built as a module,
and the module is not shipped within the iso or in udebs.
This is probably due to commit d7d73492dc5f2 in Ubuntu's linux git tree :

---
commit d7d73492dc5f2ccc5c76b042341370838af148e4
Author: Seth Forshee 
Date:   Wed Jun 5 10:47:33 2019 -0500

UBUNTU: [Config] update annotations following config review
...
-CONFIG_NVRAMpolicy<{'amd64': 'm', 'i386': 
'm'}>
+CONFIG_NVRAMpolicy<{'amd64': 'm', 'i386': 
'm', 'ppc64el': 'm'}>
...
---

F.

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

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

Title:
  Installation fails on eoan/PowerVM : missing /dev/nvram

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Hi,
  since eoan and kernel 5.2, the installation fails when installing grub at the 
end.
  Actually /dev/nvram does not exist.
  nvram support was previously built in the kernel and is now built as a module,
  and the module is not shipped within the iso or in udebs.
  This is probably due to commit d7d73492dc5f2 in Ubuntu's linux git tree :

  ---
  commit d7d73492dc5f2ccc5c76b042341370838af148e4
  Author: Seth Forshee 
  Date:   Wed Jun 5 10:47:33 2019 -0500

  UBUNTU: [Config] update annotations following config review
  ...
  -CONFIG_NVRAMpolicy<{'amd64': 'm', 
'i386': 'm'}>
  +CONFIG_NVRAMpolicy<{'amd64': 'm', 
'i386': 'm', 'ppc64el': 'm'}>
  ...
  ---

  F.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837726/+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 1709889] Re: Ubuntu 18.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.

2018-10-19 Thread Frédéric Bonnard

Hi all,

bug #1785081 was not mirrored completely for some reason and I'm working
on fixing this : it's just about the bug happening on 18.04 specifically
kernel 4.15.0-26. Sorry for the lag.

Also, on ppc64el, RHEL 7.5 with a 4.14 kernel uses deadline, so I guess it's 
not a completely unsafe path.
I'm not pushing for anything, I just noticed that.

F.

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

Title:
  Ubuntu 18.04: Bug in cfq scheduler, I/Os do not get submitted to
  adapter for a very long time.

Status in Linux:
  Unknown
Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  New
Status in linux source package in Zesty:
  Won't Fix
Status in linux source package in Bionic:
  Triaged

Bug description:
  ---Problem Description---
  When running stress test, sometimes seeing IO hung in dmesg or seeing "Host 
adapter abort request" error.

  ---Steps to Reproduce---
   There are two ways to re-create the issues:
  (1)running HTX, you will see IO timeout backtrace in dmesg in several hours
  (2)running some IO test, then reboot system, repeat this two steps, it takes 
long time to re-create the issue.

  ---uname output---
  4.10.0-11-generic - still valid up to latest kernel in Bionic

  The bulk of the effort for this issue is currently being worked in
  MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.

  Ran an interesting test: Ran HTX until I started getting the "stall"
  messages on the console, then shutdown HTX and examined the I/O
  counters for the tested disks in sysfs:

  root@bostonp15:~# for i in 
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
 do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
  0:2:2:0 0x5eba3d 0x5eba3d
  0:2:3:0 0x773cc9 0x773cc9
  0:2:4:0 0x782c61 0x782c61
  0:2:5:0 0x5ca134 0x5ca134
  root@bostonp15:~#

  So, none of the disks showed any evidence of having lost an I/O. I
  then restarted HTX and aside from having to manually restart one of
  the disks, see no problems with the testing. It appears that what was
  "hung" was purely in userland.

  This does not absolve the kernel or aacraid driver from blame, but it
  shows that the OS "believes" that it completed the I/O and thus
  removed it from the queue. What we don't know is whether the OS truly
  notified HTX about the completion, or if HTX (or userland libraries)
  just failed to process the notification.

  Tests are running again, will see what happens next.

  Update from JIRA:

  I have run some more experiments. Not sure what it tells us, but
  here's what I've seen.

  First test, ran until I got kernel messages about stalled tasks, then
  shutdown HTX. After HTX was down, I checked the above mentioned
  counters and found that on each disk iorequest_cnt matched iodone_cnt.
  The disks were usable and I could restart HTX. This suggests that the
  problem is not in the PM8069 firmware, and makes the case for the
  aacraid driver having a bug somewhat weaker. However, this merely says
  that the driver "completed" the I/O as far as the kernel is concerned,
  not that a completion rippled back to the application.

  I restarted HTX and have run until errors. This time, I am leaving HTX
  running and observing. Two of the disks reached the HTX error
  threshold and the testers stopped (those 2 disks are now idle).
  Another disks saw errors but then stopped and appears to be running
  fine now. The last disk has not seen any errors (yet). On the two idle
  (errored-out) disks I see  iorequest_cnt matches iodone_cnt. I am able
  to "terminate and restart" the two idle disks and HTX appears to be
  testing them again "normally". Note that no reboot was required,
  further supporting the evidence that, as far as the kernel is
  concerned, there is nothing wrong with the disks and their I/O paths.

  So, I don't believe this completely eliminates aacraid from the
  picture, especially given we don't see this behavior on other
  systems/drivers. But, it probably moves the focus of the investigation
  away form the adapter firmware.

  Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
  Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
  1.2.1[50792]-custom.

  Good new/bad news... While doing an initial evaluation of the LSI-3008
  SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
  So, it appears to have nothing specific to do with the PM8069 or
  aacraid driver.

  Some notes on reproduce this. I have been using the github release of
  HTX, built using the following steps:

  1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev 
(others may be required)
  2. git clone https://github.com/open-power/HTX
  3. cd HTX
  4. make
  5. make deb

  Then install the resulting "htxubuntu.deb" package.

  Note, HTX will not test disks that have

[Kernel-packages] [Bug 1709889] Re: Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to adapter for a very long time.

2018-08-02 Thread Frédéric Bonnard

Dimitri, we've synced the other bug 1785081 that is probably the same
issue as this one.

F.

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

Title:
  Ubuntu 17.04: Bug in cfq scheduler, I/Os do not get submitted to
  adapter for a very long time.

Status in Linux:
  Unknown
Status in The Ubuntu-power-systems project:
  New
Status in linux package in Ubuntu:
  New
Status in linux source package in Zesty:
  Won't Fix

Bug description:
  ---Problem Description---
  When running stress test, sometimes seeing IO hung in dmesg or seeing "Host 
adapter abort request" error.

  ---Steps to Reproduce---
   There are two ways to re-create the issues:
  (1)running HTX, you will see IO timeout backtrace in dmesg in several hours
  (2)running some IO test, then reboot system, repeat this two steps, it takes 
long time to re-create the issue.
   
  ---uname output---
  4.10.0-11-generic

  The bulk of the effort for this issue is currently being worked in
  MicroSemi's JIRA https://jira.pmcs.com/browse/ESDIBMOP-133.

  Ran an interesting test: Ran HTX until I started getting the "stall"
  messages on the console, then shutdown HTX and examined the I/O
  counters for the tested disks in sysfs:

  root@bostonp15:~# for i in 
/sys/devices/pci0003:00/0003:00:00.0/0003:01:00.0/host0/target0:2:[2345]/0:2:[2345]:0;
 do echo ${i##*/} $(<${i}/iorequest_cnt) $(<${i}/iodone_cnt); done
  0:2:2:0 0x5eba3d 0x5eba3d
  0:2:3:0 0x773cc9 0x773cc9
  0:2:4:0 0x782c61 0x782c61
  0:2:5:0 0x5ca134 0x5ca134
  root@bostonp15:~#

  So, none of the disks showed any evidence of having lost an I/O. I
  then restarted HTX and aside from having to manually restart one of
  the disks, see no problems with the testing. It appears that what was
  "hung" was purely in userland.

  This does not absolve the kernel or aacraid driver from blame, but it
  shows that the OS "believes" that it completed the I/O and thus
  removed it from the queue. What we don't know is whether the OS truly
  notified HTX about the completion, or if HTX (or userland libraries)
  just failed to process the notification.

  Tests are running again, will see what happens next.

  Update from JIRA:

  I have run some more experiments. Not sure what it tells us, but
  here's what I've seen.

  First test, ran until I got kernel messages about stalled tasks, then
  shutdown HTX. After HTX was down, I checked the above mentioned
  counters and found that on each disk iorequest_cnt matched iodone_cnt.
  The disks were usable and I could restart HTX. This suggests that the
  problem is not in the PM8069 firmware, and makes the case for the
  aacraid driver having a bug somewhat weaker. However, this merely says
  that the driver "completed" the I/O as far as the kernel is concerned,
  not that a completion rippled back to the application.

  I restarted HTX and have run until errors. This time, I am leaving HTX
  running and observing. Two of the disks reached the HTX error
  threshold and the testers stopped (those 2 disks are now idle).
  Another disks saw errors but then stopped and appears to be running
  fine now. The last disk has not seen any errors (yet). On the two idle
  (errored-out) disks I see  iorequest_cnt matches iodone_cnt. I am able
  to "terminate and restart" the two idle disks and HTX appears to be
  testing them again "normally". Note that no reboot was required,
  further supporting the evidence that, as far as the kernel is
  concerned, there is nothing wrong with the disks and their I/O paths.

  So, I don't believe this completely eliminates aacraid from the
  picture, especially given we don't see this behavior on other
  systems/drivers. But, it probably moves the focus of the investigation
  away form the adapter firmware.

  Tried build upstream 4.11 kernel on Ubuntu. This still gets the hangs.
  Both Ubuntu 4.10 and upstream 4.11 have aacraid driver
  1.2.1[50792]-custom.

  Good new/bad news... While doing an initial evaluation of the LSI-3008
  SAS HBA on Boston and Ubuntu 17.04, I am hitting this same problem.
  So, it appears to have nothing specific to do with the PM8069 or
  aacraid driver.

  Some notes on reproduce this. I have been using the github release of
  HTX, built using the following steps:

  1. apt install make gcc g++ git libncurses5-dev libcxl-dev libdapl-dev 
(others may be required)
  2. git clone https://github.com/open-power/HTX
  3. cd HTX
  4. make
  5. make deb

  Then install the resulting "htxubuntu.deb" package.

  Note, HTX will not test disks that have a filesystem or OS installed,
  so there must be at least two disks made available to HTX by clearing
  any previous data. A partition table is optional, in my testing I have
  none.

  Also, it may be desirable to run HTX somewhere other than the console,
  leaving the console free to watch for messages.

  To run:

  A. su - htx (this may take some

[Kernel-packages] [Bug 1737536] Re: Webcams not working on a Dell Latitude 5285 laptop

2018-04-06 Thread Frédéric Parrenin

A detailed answer to this problem is provided here: 
https://www.spinics.net/lists/linux-media/msg131388.html 
In summary, these "complex" webcams need drivers both in kernel space and user 
space, and it will take some time before they are supported under linux.
If ubuntu devs can help to speed up the development of these drivers, this 
would be appreciated!

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

Title:
  Webcams not working on a Dell Latitude 5285 laptop

Status in linux package in Ubuntu:
  Triaged

Bug description:
  I installed ubuntu 17.10 on a Dell latitude 5285 detachable laptop.
  Unfortunately, the webcams (both rear and front) do not work.
  There is no /dev/video* file.
  I tried upgrading the kernel to version 4.14 and 4.15rc3, but the problem is 
still there.
  Below are my lsusb and lspci outputs.

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 02)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
  00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 02)
  00:05.0 Multimedia controller: Intel Corporation Skylake Imaging Unit (rev 01)
  00:13.0 Non-VGA unclassified device: Intel Corporation Device 9d35 (rev 21)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:14.3 Multimedia controller: Intel Corporation Device 9d32 (rev 01)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #1 (rev 21)
  00:15.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #2 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#5 (rev f1)
  00:1c.7 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#8 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#9 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  01:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 
0116
  02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)

  $ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 8087:0a2b Intel Corp.
  Bus 001 Device 004: ID 044e:1218 Alps Electric Co., Ltd
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737536/+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 1739498] Re: Ubuntu 17.10 crashes on vmalloc.c

2018-02-05 Thread Frédéric Bonnard

Hi Manoj, the patches that fixed this issue are the 3 listed above in my
comment :
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739498/comments/6

F.

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

Title:
  Ubuntu 17.10 crashes on vmalloc.c

Status in The Ubuntu-power-systems project:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  == Comment: #0 - Breno Leitao - 2017-12-19 09:48:10 ==
  When running Ubuntu 17.10 on POWER9, I got the following error:

  [409038.118908] WARNING: CPU: 47 PID: 294 at 
/build/linux-LIHoWc/linux-4.13.0/mm/vmalloc.c:2527 pcpu_get_vm_areas+0x62c/0x660
  [409038.118909] Modules linked in: xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
iptable_filter kvm_hv kvm at24 ofpart ipmi_powernv ipmi_devintf ipmi_msghandler 
cmdlinepart powernv_flash uio_pdrv_genirq uio mtd vmx_crypto ibmpowernv 
crct10dif_vpmsum opal_prd binfmt_misc ip_tables x_tables autofs4 crc32c_vpmsum 
ast i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops 
ttm drm tg3 ahci libahci
  [409038.118933] CPU: 47 PID: 294 Comm: kworker/47:0 Tainted: GW   
4.13.0-12-generic #13-Ubuntu
  [409038.118934] Workqueue: events pcpu_balance_workfn
  [409038.118936] task: c03fe3cdcc00 task.stack: c03fe3be
  [409038.118937] NIP: c032c1fc LR: c02f5fd4 CTR: 

  [409038.118937] REGS: c03fe3be3810 TRAP: 0700   Tainted: GW   
 (4.13.0-12-generic)
  [409038.118938] MSR: 9282b033 
  [409038.118944]   CR: 24024828  XER: 2004
  [409038.118944] CFAR: c032bdb8 SOFTE: 1
  GPR00: 2df0 c03fe3be3a90 c15e3000 
c000203fff6b6880
  GPR04: c000203fff223608 0008 c000203fff6b6888 

  GPR08: 2df0 0800 0160 
c000203fff6b6888
  GPR12: 0002 cfaded80 c0f6c050 
c03fe3be3bc0
  GPR16: 0010  c189daf8 
c000203fff223608
  GPR20: 2f50 c000203fff2235f8 c000203fff223600 

  GPR24:  c000203fff6b6888 0001 
2f50
  GPR28: 0002 000f d800 
d000
  [409038.118963] NIP [c032c1fc] pcpu_get_vm_areas+0x62c/0x660
  [409038.118964] LR [c02f5fd4] pcpu_create_chunk+0xb4/0x1b0
  [409038.118965] Call Trace:
  [409038.118966] [c03fe3be3a90] [c03fe3be3ad0] 0xc03fe3be3ad0 
(unreliable)
  [409038.118968] [c03fe3be3b60] [c02f5fd4] 
pcpu_create_chunk+0xb4/0x1b0
  [409038.118970] [c03fe3be3ba0] [c02f7890] 
pcpu_balance_workfn+0x600/0x960
  [409038.118972] [c03fe3be3ca0] [c01205d8] 
process_one_work+0x298/0x5a0
  [409038.118975] [c03fe3be3d30] [c0120968] worker_thread+0x88/0x620
  [409038.118977] [c03fe3be3dc0] [c012980c] kthread+0x1ac/0x1c0
  [409038.118979] [c03fe3be3e30] [c000b4e8] 
ret_from_kernel_thread+0x5c/0x74
  [409038.118980] Instruction dump:
  [409038.118981] eae3 4191fad0 7ed3b378 e9210030 7efbbb78 7c791b78 
3b40 e953

   
  ---uname output---
  4.13.0-12-generic

  == Comment: #3 - ANEESH K. K V  - 2017-12-20 05:59:13 ==
  https://lkml.kernel.org/r/1501583364-14909-1-git-send-email-...@ellerman.id.au

  The above may be related?

  Related discussions
  https://lkml.kernel.org/r/20170724134240.gl25...@dhcp22.suse.cz

  -aneesh

  == Comment: #4 - Breno Leitao - 2017-12-20 09:48:07 ==
  I just tested with kernel 4.15.0-041500rc4 and I didn't see a problem so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1739498/+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 1737536] Re: Webcams not working on a Dell Latitude 5285 laptop

2017-12-11 Thread Frédéric Parrenin

After some research, it seems the webcams depend on a new intel driver which 
will be released in kernel 4.16:
https://www.mail-archive.com/linux-media@vger.kernel.org/msg122619.html

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

Title:
  Webcams not working on a Dell Latitude 5285 laptop

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed ubuntu 17.10 on a Dell latitude 5285 detachable laptop.
  Unfortunately, the webcams (both rear and front) do not work.
  There is no /dev/video* file.
  I tried upgrading the kernel to version 4.14 and 4.15rc3, but the problem is 
still there.
  Below are my lsusb and lspci outputs.

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 02)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
  00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 02)
  00:05.0 Multimedia controller: Intel Corporation Skylake Imaging Unit (rev 01)
  00:13.0 Non-VGA unclassified device: Intel Corporation Device 9d35 (rev 21)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:14.3 Multimedia controller: Intel Corporation Device 9d32 (rev 01)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #1 (rev 21)
  00:15.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #2 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#5 (rev f1)
  00:1c.7 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#8 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#9 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  01:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 
0116
  02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
  03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)

  $ lsusb
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 8087:0a2b Intel Corp.
  Bus 001 Device 004: ID 044e:1218 Alps Electric Co., Ltd
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1737536/+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 1737536] [NEW] Webcams not working on a Dell Latitude 5285 laptop

2017-12-11 Thread Frédéric Parrenin

Public bug reported:

I installed ubuntu 17.10 on a Dell latitude 5285 detachable laptop.
Unfortunately, the webcams (both rear and front) do not work.
There is no /dev/video* file.
I tried upgrading the kernel to version 4.14 and 4.15rc3, but the problem is 
still there.
Below are my lsusb and lspci outputs.

$ lspci
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 02)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 02)
00:05.0 Multimedia controller: Intel Corporation Skylake Imaging Unit (rev 01)
00:13.0 Non-VGA unclassified device: Intel Corporation Device 9d35 (rev 21)
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
00:14.3 Multimedia controller: Intel Corporation Device 9d32 (rev 01)
00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial 
IO I2C Controller #0 (rev 21)
00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial 
IO I2C Controller #1 (rev 21)
00:15.2 Signal processing controller: Intel Corporation Sunrise Point-LP Serial 
IO I2C Controller #2 (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI 
#1 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 
(rev f1)
00:1c.7 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #8 
(rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 
(rev f1)
00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
01:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 0116
02:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
03:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 8087:0a2b Intel Corp.
Bus 001 Device 004: ID 044e:1218 Alps Electric Co., Ltd
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

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

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

Title:
  Webcams not working on a Dell Latitude 5285 laptop

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I installed ubuntu 17.10 on a Dell latitude 5285 detachable laptop.
  Unfortunately, the webcams (both rear and front) do not work.
  There is no /dev/video* file.
  I tried upgrading the kernel to version 4.14 and 4.15rc3, but the problem is 
still there.
  Below are my lsusb and lspci outputs.

  $ lspci
  00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 02)
  00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
  00:04.0 Signal processing controller: Intel Corporation Skylake Processor 
Thermal Subsystem (rev 02)
  00:05.0 Multimedia controller: Intel Corporation Skylake Imaging Unit (rev 01)
  00:13.0 Non-VGA unclassified device: Intel Corporation Device 9d35 (rev 21)
  00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
  00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
  00:14.3 Multimedia controller: Intel Corporation Device 9d32 (rev 01)
  00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #0 (rev 21)
  00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #1 (rev 21)
  00:15.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Serial IO I2C Controller #2 (rev 21)
  00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME 
HECI #1 (rev 21)
  00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#5 (rev f1)
  00:1c.7 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#8 (rev f1)
  00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port 
#9 (rev f1)
  00:1f.0 ISA bridge: Intel Corporation Device 9d4e (rev 21)
  00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
  00:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
  00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
  01:00.0 Non-Volatile memory controller: Toshiba America Info Systems Device 
0116
  02:00.0 Network controller:

[Kernel-packages] [Bug 1666421] Re: kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

2017-03-14 Thread Frédéric Danis

Freeze still occurs after installed linux-image-4.4.0-67-generic and 
linux-image-extra-4.4.0-67-generic from proposed.
Are they correct packages to test?

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

Title:
  kernel 4.4.0-63 with USB WLAN RTL8192CU freezes desktop

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Yakkety:
  Fix Committed

Bug description:
  booting PC with USB WLAN stick RTL8192CU attached on kernel 4.4.0-63-generic:
  Grub works, entering full disk encryption passphrase works, but when the 
desktop comes up mouse and keyboard (via USB) are dead and the desktop also.

  booting the PC without the stick attached works fine, but as soon as
  it is attached (see syslog) mouse, keyboard and the desktop itself are
  dead (checked by opening terminal and "watch date" - freezes, with
  desktop still visible).

  problem is resolved by booting former kernel 4.4.0-59-generic.

  syslog upon attaching stick 
---
  Feb 21 07:17:02 orin kernel: [  188.998338] usb 8-2: new high-speed USB 
device number 2 using xhci_hcd
  Feb 21 07:17:02 orin kernel: [  189.129674] usb 8-2: New USB device found, 
idVendor=0bda, idProduct=8178
  Feb 21 07:17:02 orin kernel: [  189.129682] usb 8-2: New USB device strings: 
Mfr=1, Product=2, SerialNumber=3
  Feb 21 07:17:02 orin kernel: [  189.129687] usb 8-2: Product: USB WLAN
  Feb 21 07:17:02 orin kernel: [  189.129691] usb 8-2: Manufacturer: Realtek
  Feb 21 07:17:02 orin kernel: [  189.129694] usb 8-2: SerialNumber: 
00e04c01
  Feb 21 07:17:02 orin mtp-probe: checking bus 8, device 2: 
"/sys/devices/pci:00/:00:10.1/usb8/8-2"
  Feb 21 07:17:02 orin mtp-probe: bus: 8, device: 2 was not an MTP device
  Feb 21 07:17:02 orin dbus[1112]: [system] Activating via systemd: service 
name='org.freedesktop.UDisks2' unit='udisks2.service'
  Feb 21 07:17:02 orin systemd[1]: Starting Disk Manager...
  Feb 21 07:17:02 orin udisksd[2447]: udisks daemon version 2.1.7 starting
  Feb 21 07:17:02 orin dbus[1112]: [system] Successfully activated service 
'org.freedesktop.UDisks2'
  Feb 21 07:17:02 orin systemd[1]: Started Disk Manager.
  Feb 21 07:17:02 orin udisksd[2447]: Acquired the name org.freedesktop.UDisks2 
on the system message bus
  Feb 21 07:17:02 orin org.gtk.vfs.AfcVolumeMonitor[1918]: Volume monitor alive
  Feb 21 07:17:03 orin kernel: [  190.200286] cfg80211: World regulatory domain 
updated:
  Feb 21 07:17:03 orin kernel: [  190.200294] cfg80211:  DFS Master region: 
unset
  Feb 21 07:17:03 orin kernel: [  190.200297] cfg80211:   (start_freq - 
end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
  Feb 21 07:17:03 orin kernel: [  190.200303] cfg80211:   (2402000 KHz - 
2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200308] cfg80211:   (2457000 KHz - 
2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200312] cfg80211:   (2474000 KHz - 
2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200317] cfg80211:   (517 KHz - 
525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200321] cfg80211:   (525 KHz - 
533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200325] cfg80211:   (549 KHz - 
573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s)
  Feb 21 07:17:03 orin kernel: [  190.200329] cfg80211:   (5735000 KHz - 
5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.200333] cfg80211:   (5724 KHz - 
6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A)
  Feb 21 07:17:03 orin kernel: [  190.223081] rtl8192cu: Chip version 0x11
  Feb 21 07:17:03 orin kernel: [  190.625235] rtl8192cu: MAC address: 
14:cc:20:10:43:98
  Feb 21 07:17:03 orin kernel: [  190.625241] rtl8192cu: Board Type 0
  Feb 21 07:17:03 orin kernel: [  190.626355] rtl_usb: rx_max_size 15360, 
rx_urb_num 8, in_ep 1
  Feb 21 07:17:03 orin kernel: [  190.626408] rtl8192cu: Loading firmware 
rtlwifi/rtl8192cufw_TMSC.bin
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7698] (wlan0): 
using nl80211 for WiFi device control
  Feb 21 07:17:03 orin kernel: [  190.636625] ieee80211 phy0: Selected rate 
control algorithm 'rtl_rc'
  Feb 21 07:17:03 orin kernel: [  190.637211] usbcore: registered new interface 
driver rtl8192cu
  Feb 21 07:17:03 orin systemd[1]: Starting Load/Save RF Kill Switch Status...
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7780] device 
(wlan0): driver supports Access Point (AP) mode
  Feb 21 07:17:03 orin NetworkManager[1181]:   [1487657823.7798] manager: 
(wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/4)
  Feb 21

[Kernel-packages] [Bug 1584042] Re: Hyper-V NIC cannot pass IPv6 UDP packets by default until protocol offload is disabled

2016-09-22 Thread Frédéric Druilhet

This is probably a bug in the Linux HyperV Card driver. 
Maybe it's MS job to correct this. I don't know who has responsibility on this 
package. 
But, I confirm it is not a bug in the guest hyperV system or windows. I have 
ipv6 windows servers (multiple versions) and they all work correctly with Ipv6. 
Even my HyperV Servers are on ipv6 and work fine.
On the other hand, if the bug is on Linux, but more widely that only on Hyperv 
Card driver, we would have heard about it way faster ;)
At last, changing a settings with ethtool resolves the problem is pointing the 
investigation starting point I guess.

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

Title:
  Hyper-V NIC cannot pass IPv6 UDP packets by default until protocol
  offload is disabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:

  Hi,

  On a client server, I can't get a response from a name server in ipv6+udp. On 
the same server, it works fine in tcp.
  If I log on my name server, I can get a response from himself but, as a 
client, it can't get a response from another name server.

  here are the steps to reproduce : 
  - Create a new server using Ubuntu server 16.04. Set it to use ipv4 and use 
your preferred name server. Select absolutely nothing as functionality. 
  - check some nslookup and apt-get stuff to verify network is OK
  - add ipv6 to the interface and refer to an IPV6 nameserver. I have 3 and 
thats why I noticed the problem >> All 3 ipv6 nameservers are filling the 3 
places in resolv.conf.
  - if you don't have 3 ipv6 nameservers, just add one and comment the line 
with the ipv4 name server.
  - verify your resolv.conf. Should only content ipv6 reference.
  - Now, you can't nslookup anymore... 
  - add some tests : "dig @ipv4server google.com" works but "dig @ipv6server 
google.com" don't

  
  Here a more tests : 

  
  Nameserver1 : Nameserver1.MyDomain :  XXX.YYY.ZZZ.250 / ::::250
  ClientStandAloneServer.MyDomain   :   
XXX.YYY.ZZZ.209 / ::::209

  With IPV4

  
  # dig @XXX.YYY.ZZZ.226 www.google.fr

  /var/log/named/queries.log on Nameserver1:
  20-May-2016 12:25:02.834 queries: info: client XXX.YYY.ZZZ.209#35116 
(www.google.fr): query: www.google.fr IN A +E (XXX.YYY.ZZZ.226)

  Tcp Dump on Nameserver1:
  12:25:02.834092 IP StandAloneServer.MyDomain.35116 > 
Nameserver1.MyDomain.domain: 62949+ [1au] A? www.google.fr. (42)
  12:25:02.834395 IP Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35116: 62949 1/4/5 A 216.58.210.195 (204)

  Tcp Dump on Client
  12:25:02.668200 IP StandAloneServer.MyDomain.35116 > 
Nameserver1.MyDomain.domain: 62949+ [1au] A? www.google.fr. (42)
  12:25:02.669573 IP Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35116: 62949 1/4/5 A 216.58.210.195 (204)

  
  RESULT:

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @XXX.YYY.ZZZ.226 www.google.fr
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49591
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 5
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;www.google.fr.   IN  A
  ;; ANSWER SECTION:
  www.google.fr.300 IN  A   216.58.210.195
  ;; AUTHORITY SECTION:
  google.fr.171625  IN  NS  ns1.google.com.
  [TRUNCATED]



  WITH IPV6
  # dig @::::226 www.google.fr 

  NOTE  : I only asked once, it created 3 queries with 5 secs
  d’intervalle environ

  /var/log/named/queries.log on Nameserver1:
  20-May-2016 12:32:34.902 queries: info: client ::::209#35362 
(www.google.fr): query: www.google.fr IN A +E (::::226)
  20-May-2016 12:32:39.902 queries: info: client ::::209#35362 
(www.google.fr): query: www.google.fr IN A +E (::::226)
  20-May-2016 12:32:44.902 queries: info: client ::::209#35362 
(www.google.fr): query: www.google.fr IN A +E (::::226)

  Tcp Dump on Nameserver1:
  12:32:34.902598 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:34.902994 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)
  …
  12:32:39.902644 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:39.902975 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)
  …
  12:32:39.902644 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:39.902975 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)

  
  Tcp Dump on Client12:32:34.725312 IP6 StandAloneServer.MyDomain.35362 >

[Kernel-packages] [Bug 1359689] Re: cryptsetup password prompt not shown

2016-08-08 Thread Frédéric

Since few months, after updates, no problem

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

Title:
  cryptsetup password prompt not shown

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Triaged
Status in plymouth package in Debian:
  Fix Released

Bug description:
  Currently in utopic the following happens when booting an encrypted
  setup:

  Press enter in grub, after a while screen freezes (or turns completely
  black) and stays like that. When I press the down key, I can see the
  password prompt. When I press the up key again, I get to the graphical
  password prompt.

  This is demonstrated in the following screencast:
  https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing

  Maybe this is related to the version of plymouth utopic currently uses, a 
similar debian bug report seems to be resolved with a newer version 0.9.0-6, 
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752.
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821)
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821)
  MachineType: Dell Inc. Precision M4600
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/10/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4600
  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/1359689/+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 1584042] Re: Hyper-V NIC cannot pass IPv6 UDP packets by default until protocol offload is disabled

Spotted, sorry :)

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

Title:
  Hyper-V NIC cannot pass IPv6 UDP packets by default until protocol
  offload is disabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:

  Hi,

  On a client server, I can't get a response from a name server in ipv6+udp. On 
the same server, it works fine in tcp.
  If I log on my name server, I can get a response from himself but, as a 
client, it can't get a response from another name server.

  here are the steps to reproduce : 
  - Create a new server using Ubuntu server 16.04. Set it to use ipv4 and use 
your preferred name server. Select absolutely nothing as functionality. 
  - check some nslookup and apt-get stuff to verify network is OK
  - add ipv6 to the interface and refer to an IPV6 nameserver. I have 3 and 
thats why I noticed the problem >> All 3 ipv6 nameservers are filling the 3 
places in resolv.conf.
  - if you don't have 3 ipv6 nameservers, just add one and comment the line 
with the ipv4 name server.
  - verify your resolv.conf. Should only content ipv6 reference.
  - Now, you can't nslookup anymore... 
  - add some tests : "dig @ipv4server google.com" works but "dig @ipv6server 
google.com" don't

  
  Here a more tests : 

  
  Nameserver1 : Nameserver1.MyDomain :  XXX.YYY.ZZZ.250 / ::::250
  ClientStandAloneServer.MyDomain   :   
XXX.YYY.ZZZ.209 / ::::209

  With IPV4

  
  # dig @XXX.YYY.ZZZ.226 www.google.fr

  /var/log/named/queries.log on Nameserver1:
  20-May-2016 12:25:02.834 queries: info: client XXX.YYY.ZZZ.209#35116 
(www.google.fr): query: www.google.fr IN A +E (XXX.YYY.ZZZ.226)

  Tcp Dump on Nameserver1:
  12:25:02.834092 IP StandAloneServer.MyDomain.35116 > 
Nameserver1.MyDomain.domain: 62949+ [1au] A? www.google.fr. (42)
  12:25:02.834395 IP Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35116: 62949 1/4/5 A 216.58.210.195 (204)

  Tcp Dump on Client
  12:25:02.668200 IP StandAloneServer.MyDomain.35116 > 
Nameserver1.MyDomain.domain: 62949+ [1au] A? www.google.fr. (42)
  12:25:02.669573 IP Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35116: 62949 1/4/5 A 216.58.210.195 (204)

  
  RESULT:

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @XXX.YYY.ZZZ.226 www.google.fr
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49591
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 5
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;www.google.fr.   IN  A
  ;; ANSWER SECTION:
  www.google.fr.300 IN  A   216.58.210.195
  ;; AUTHORITY SECTION:
  google.fr.171625  IN  NS  ns1.google.com.
  [TRUNCATED]



  WITH IPV6
  # dig @::::226 www.google.fr 

  NOTE  : I only asked once, it created 3 queries with 5 secs
  d’intervalle environ

  /var/log/named/queries.log on Nameserver1:
  20-May-2016 12:32:34.902 queries: info: client ::::209#35362 
(www.google.fr): query: www.google.fr IN A +E (::::226)
  20-May-2016 12:32:39.902 queries: info: client ::::209#35362 
(www.google.fr): query: www.google.fr IN A +E (::::226)
  20-May-2016 12:32:44.902 queries: info: client ::::209#35362 
(www.google.fr): query: www.google.fr IN A +E (::::226)

  Tcp Dump on Nameserver1:
  12:32:34.902598 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:34.902994 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)
  …
  12:32:39.902644 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:39.902975 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)
  …
  12:32:39.902644 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:39.902975 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)

  
  Tcp Dump on Client12:32:34.725312 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:34.726036 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)
  …
  12:32:39.725199 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:39.726045 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)
  …
  12:32:44.725288 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:44.725944 IP6

[Kernel-packages] [Bug 1584042] Re: Hyper-V NIC cannot pass IPv6 UDP packets by default until protocol offload is disabled

On "client" and "server":
Setting up linux-headers-4.6.0-040600 (4.6.0-040600.201605151930) ...
Setting up linux-headers-4.6.0-040600-generic (4.6.0-040600.201605151930) ...
Setting up linux-image-4.6.0-040600-generic (4.6.0-040600.201605151930) ...

root@Server:/# uname -a
Linux Server 4.6.0-040600-generic #201605151930 SMP Sun May 15 23:32:59 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

root@Client:/# uname -a
Linux Client 4.6.0-040600-generic #201605151930 SMP Sun May 15 23:32:59 UTC 
2016 x86_64 x86_64 x86_64 GNU/Linux

root@Client:/# ethtool --show-offload  eth0
Features for eth0:
rx-checksumming: on
tx-checksumming: on
tx-checksum-ipv4: off [fixed]
tx-checksum-ip-generic: on
tx-checksum-ipv6: off [fixed]
tx-checksum-fcoe-crc: off [fixed]
tx-checksum-sctp: off [fixed]

root@Client:/# ethtool --offload  eth0  rx off  tx off
Actual changes:
rx-checksumming: off
tx-checksumming: off

root@Server:/# ethtool --offload  eth0  rx off  tx off
Actual changes:
rx-checksumming: off
tx-checksumming: off

oot@Client:/# dig @2001:660:660c:120::2000 testubuntu NS

; <<>> DiG 9.10.3-P4-Ubuntu <<>> @2001:660:660c:120::2000 testubuntu NS
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2664
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 2

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;testubuntu.IN  NS

;; ANSWER SECTION:
testubuntu. 172800  IN  NS  server.testubuntu.



--
Bug still present upstream !!
Confirmed 
tag: kernel-bug-exists-upstream

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

Title:
  Hyper-V NIC cannot pass IPv6 UDP packets by default until protocol
  offload is disabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:

  Hi,

  On a client server, I can't get a response from a name server in ipv6+udp. On 
the same server, it works fine in tcp.
  If I log on my name server, I can get a response from himself but, as a 
client, it can't get a response from another name server.

  here are the steps to reproduce : 
  - Create a new server using Ubuntu server 16.04. Set it to use ipv4 and use 
your preferred name server. Select absolutely nothing as functionality. 
  - check some nslookup and apt-get stuff to verify network is OK
  - add ipv6 to the interface and refer to an IPV6 nameserver. I have 3 and 
thats why I noticed the problem >> All 3 ipv6 nameservers are filling the 3 
places in resolv.conf.
  - if you don't have 3 ipv6 nameservers, just add one and comment the line 
with the ipv4 name server.
  - verify your resolv.conf. Should only content ipv6 reference.
  - Now, you can't nslookup anymore... 
  - add some tests : "dig @ipv4server google.com" works but "dig @ipv6server 
google.com" don't

  
  Here a more tests : 

  
  Nameserver1 : Nameserver1.MyDomain :  XXX.YYY.ZZZ.250 / ::::250
  ClientStandAloneServer.MyDomain   :   
XXX.YYY.ZZZ.209 / ::::209

  With IPV4

  
  # dig @XXX.YYY.ZZZ.226 www.google.fr

  /var/log/named/queries.log on Nameserver1:
  20-May-2016 12:25:02.834 queries: info: client XXX.YYY.ZZZ.209#35116 
(www.google.fr): query: www.google.fr IN A +E (XXX.YYY.ZZZ.226)

  Tcp Dump on Nameserver1:
  12:25:02.834092 IP StandAloneServer.MyDomain.35116 > 
Nameserver1.MyDomain.domain: 62949+ [1au] A? www.google.fr. (42)
  12:25:02.834395 IP Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35116: 62949 1/4/5 A 216.58.210.195 (204)

  Tcp Dump on Client
  12:25:02.668200 IP StandAloneServer.MyDomain.35116 > 
Nameserver1.MyDomain.domain: 62949+ [1au] A? www.google.fr. (42)
  12:25:02.669573 IP Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35116: 62949 1/4/5 A 216.58.210.195 (204)

  
  RESULT:

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @XXX.YYY.ZZZ.226 www.google.fr
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49591
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 5
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;www.google.fr.   IN  A
  ;; ANSWER SECTION:
  www.google.fr.300 IN  A   216.58.210.195
  ;; AUTHORITY SECTION:
  google.fr.171625  IN  NS  ns1.google.com.
  [TRUNCATED]



  WITH IPV6
  # dig @::::226 www.google.fr 

  NOTE  : I only asked once, it created 3 queries with 5 secs
  d’intervalle environ

  /var/log/named/queries.log on Nameserver1:
  20-May-2016 12:32:34.902 queries: info: client ::::209#35362 
(www.google.fr): query: www.google.fr IN A +E (::::226)
  20-May-2016 12:32:39.902 queries: info:

[Kernel-packages] [Bug 1584042] Re: Hyper-V NIC cannot pass IPv6 UDP packets by default until protocol offload is disabled

Sorry, on my previous post, I forgot to copy paste this fail before setting 
offload off:
Also, I didn't find where to add the tag kernel-bug-exists-upstream ??

root@Client:/# dig @2001:660:660c:120::2000 testubuntu NS

; <<>> DiG 9.10.3-P4-Ubuntu <<>> @2001:660:660c:120::2000 testubuntu NS
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

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

Title:
  Hyper-V NIC cannot pass IPv6 UDP packets by default until protocol
  offload is disabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:

  Hi,

  On a client server, I can't get a response from a name server in ipv6+udp. On 
the same server, it works fine in tcp.
  If I log on my name server, I can get a response from himself but, as a 
client, it can't get a response from another name server.

  here are the steps to reproduce : 
  - Create a new server using Ubuntu server 16.04. Set it to use ipv4 and use 
your preferred name server. Select absolutely nothing as functionality. 
  - check some nslookup and apt-get stuff to verify network is OK
  - add ipv6 to the interface and refer to an IPV6 nameserver. I have 3 and 
thats why I noticed the problem >> All 3 ipv6 nameservers are filling the 3 
places in resolv.conf.
  - if you don't have 3 ipv6 nameservers, just add one and comment the line 
with the ipv4 name server.
  - verify your resolv.conf. Should only content ipv6 reference.
  - Now, you can't nslookup anymore... 
  - add some tests : "dig @ipv4server google.com" works but "dig @ipv6server 
google.com" don't

  
  Here a more tests : 

  
  Nameserver1 : Nameserver1.MyDomain :  XXX.YYY.ZZZ.250 / ::::250
  ClientStandAloneServer.MyDomain   :   
XXX.YYY.ZZZ.209 / ::::209

  With IPV4

  
  # dig @XXX.YYY.ZZZ.226 www.google.fr

  /var/log/named/queries.log on Nameserver1:
  20-May-2016 12:25:02.834 queries: info: client XXX.YYY.ZZZ.209#35116 
(www.google.fr): query: www.google.fr IN A +E (XXX.YYY.ZZZ.226)

  Tcp Dump on Nameserver1:
  12:25:02.834092 IP StandAloneServer.MyDomain.35116 > 
Nameserver1.MyDomain.domain: 62949+ [1au] A? www.google.fr. (42)
  12:25:02.834395 IP Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35116: 62949 1/4/5 A 216.58.210.195 (204)

  Tcp Dump on Client
  12:25:02.668200 IP StandAloneServer.MyDomain.35116 > 
Nameserver1.MyDomain.domain: 62949+ [1au] A? www.google.fr. (42)
  12:25:02.669573 IP Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35116: 62949 1/4/5 A 216.58.210.195 (204)

  
  RESULT:

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @XXX.YYY.ZZZ.226 www.google.fr
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49591
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 5
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;www.google.fr.   IN  A
  ;; ANSWER SECTION:
  www.google.fr.300 IN  A   216.58.210.195
  ;; AUTHORITY SECTION:
  google.fr.171625  IN  NS  ns1.google.com.
  [TRUNCATED]



  WITH IPV6
  # dig @::::226 www.google.fr 

  NOTE  : I only asked once, it created 3 queries with 5 secs
  d’intervalle environ

  /var/log/named/queries.log on Nameserver1:
  20-May-2016 12:32:34.902 queries: info: client ::::209#35362 
(www.google.fr): query: www.google.fr IN A +E (::::226)
  20-May-2016 12:32:39.902 queries: info: client ::::209#35362 
(www.google.fr): query: www.google.fr IN A +E (::::226)
  20-May-2016 12:32:44.902 queries: info: client ::::209#35362 
(www.google.fr): query: www.google.fr IN A +E (::::226)

  Tcp Dump on Nameserver1:
  12:32:34.902598 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:34.902994 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)
  …
  12:32:39.902644 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:39.902975 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)
  …
  12:32:39.902644 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:39.902975 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)

  
  Tcp Dump on Client12:32:34.725312 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:34.726036 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)
  …
  12:32:39.725199 IP6

[Kernel-packages] [Bug 1584042] Re: Hyper-V NIC cannot pass IPv6 UDP packets by default until protocol offload is disabled

This issue could exist since a long time. Having only 3 servers, each 
nameserver, did hide the problem (as each could resolve)
In my numerous tests, I made a virtual machine using an old Ubuntu server 15.04 
and the problem was present. But,in the meanwhile, my bind server was having 
troubles (rx/tx activated). So I don't know if its due to 15.04 or the 
production bind server

I'll try to test on the upstream build as soon as possible. I'll tell
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/1584042

Title:
  Hyper-V NIC cannot pass IPv6 UDP packets by default until protocol
  offload is disabled

Status in linux package in Ubuntu:
  Confirmed

Bug description:

  Hi,

  On a client server, I can't get a response from a name server in ipv6+udp. On 
the same server, it works fine in tcp.
  If I log on my name server, I can get a response from himself but, as a 
client, it can't get a response from another name server.

  here are the steps to reproduce : 
  - Create a new server using Ubuntu server 16.04. Set it to use ipv4 and use 
your preferred name server. Select absolutely nothing as functionality. 
  - check some nslookup and apt-get stuff to verify network is OK
  - add ipv6 to the interface and refer to an IPV6 nameserver. I have 3 and 
thats why I noticed the problem >> All 3 ipv6 nameservers are filling the 3 
places in resolv.conf.
  - if you don't have 3 ipv6 nameservers, just add one and comment the line 
with the ipv4 name server.
  - verify your resolv.conf. Should only content ipv6 reference.
  - Now, you can't nslookup anymore... 
  - add some tests : "dig @ipv4server google.com" works but "dig @ipv6server 
google.com" don't

  
  Here a more tests : 

  
  Nameserver1 : Nameserver1.MyDomain :  XXX.YYY.ZZZ.250 / ::::250
  ClientStandAloneServer.MyDomain   :   
XXX.YYY.ZZZ.209 / ::::209

  With IPV4

  
  # dig @XXX.YYY.ZZZ.226 www.google.fr

  /var/log/named/queries.log on Nameserver1:
  20-May-2016 12:25:02.834 queries: info: client XXX.YYY.ZZZ.209#35116 
(www.google.fr): query: www.google.fr IN A +E (XXX.YYY.ZZZ.226)

  Tcp Dump on Nameserver1:
  12:25:02.834092 IP StandAloneServer.MyDomain.35116 > 
Nameserver1.MyDomain.domain: 62949+ [1au] A? www.google.fr. (42)
  12:25:02.834395 IP Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35116: 62949 1/4/5 A 216.58.210.195 (204)

  Tcp Dump on Client
  12:25:02.668200 IP StandAloneServer.MyDomain.35116 > 
Nameserver1.MyDomain.domain: 62949+ [1au] A? www.google.fr. (42)
  12:25:02.669573 IP Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35116: 62949 1/4/5 A 216.58.210.195 (204)

  
  RESULT:

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @XXX.YYY.ZZZ.226 www.google.fr
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49591
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 5
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;www.google.fr.   IN  A
  ;; ANSWER SECTION:
  www.google.fr.300 IN  A   216.58.210.195
  ;; AUTHORITY SECTION:
  google.fr.171625  IN  NS  ns1.google.com.
  [TRUNCATED]



  WITH IPV6
  # dig @::::226 www.google.fr 

  NOTE  : I only asked once, it created 3 queries with 5 secs
  d’intervalle environ

  /var/log/named/queries.log on Nameserver1:
  20-May-2016 12:32:34.902 queries: info: client ::::209#35362 
(www.google.fr): query: www.google.fr IN A +E (::::226)
  20-May-2016 12:32:39.902 queries: info: client ::::209#35362 
(www.google.fr): query: www.google.fr IN A +E (::::226)
  20-May-2016 12:32:44.902 queries: info: client ::::209#35362 
(www.google.fr): query: www.google.fr IN A +E (::::226)

  Tcp Dump on Nameserver1:
  12:32:34.902598 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:34.902994 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)
  …
  12:32:39.902644 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:39.902975 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)
  …
  12:32:39.902644 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:39.902975 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)

  
  Tcp Dump on Client12:32:34.725312 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:34.726036 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362:

[Kernel-packages] [Bug 1584042] Re: Hyper-V NIC cannot pass IPv6 UDP packets by default until protocol offload is disabled

root@Client:/home/ssi# uname -a
Linux Client 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux

root@Client:/home/ssi# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 16.04 LTS
Release:16.04
Codename:   denial

root@Client:/home/ssi# lsblk -o NAME,SIZE
NAME   SIZE
fd0  4K
sda 15G
├─sda1 487M
├─sda2   1K
└─sda514.5G
  ├─Client--vg-root   13.5G
  └─Client--vg-swap_11G
sr0   1024M

root@Client:/home/ssi# lspci
00:00.0 Host bridge: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX Host bridge 
(AGP disabled) (rev 03)
00:07.0 ISA bridge: Intel Corporation 82371AB/EB/MB PIIX4 ISA (rev 01)
00:07.1 IDE interface: Intel Corporation 82371AB/EB/MB PIIX4 IDE (rev 01)
00:07.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 02)
00:08.0 VGA compatible controller: Microsoft Corporation Hyper-V virtual VGA


root@Client:/home/ssi# lshw -sanitize
computer  
description: Computer
width: 64 bits
capabilities: smbios-2.3 vsyscall32
  *-core
   description: Motherboard
   physical id: 0
 *-memory
  description: System memory
  physical id: 0
  size: 983MiB
 *-cpu
  product: Intel(R) Xeon(R) CPU   E5507  @ 2.27GHz
  vendor: Intel Corp.
  physical id: 1
  bus info: cpu@0
  width: 64 bits
  capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 
apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx 
x86-64 constant_tsc rep_good nopl pni ssse3 cx16 sse4_1 sse4_2 popcnt 
hypervisor lahf_lm
 *-pci
  description: Host bridge
  product: 440BX/ZX/DX - 82443BX/ZX/DX Host bridge (AGP disabled)
  vendor: Intel Corporation
  physical id: 100
  bus info: pci@:00:00.0
  version: 03
  width: 32 bits
  clock: 33MHz
*-isa
 description: ISA bridge
 product: 82371AB/EB/MB PIIX4 ISA
 vendor: Intel Corporation
 physical id: 7
 bus info: pci@:00:07.0
 version: 01
 width: 32 bits
 clock: 33MHz
 capabilities: isa bus_master
 configuration: latency=0
*-ide
 description: IDE interface
 product: 82371AB/EB/MB PIIX4 IDE
 vendor: Intel Corporation
 physical id: 7.1
 bus info: pci@:00:07.1
 version: 01
 width: 32 bits
 clock: 33MHz
 capabilities: ide bus_master
 configuration: driver=ata_piix latency=0
 resources: irq:0 ioport:1f0(size=8) ioport:3f6 ioport:170(size=8) 
ioport:376 ioport:ffa0(size=16)
*-bridge UNCLAIMED
 description: Bridge
 product: 82371AB/EB/MB PIIX4 ACPI
 vendor: Intel Corporation
 physical id: 7.3
 bus info: pci@:00:07.3
 version: 02
 width: 32 bits
 clock: 33MHz
 capabilities: bridge
 configuration: latency=0
*-display
 description: VGA compatible controller
 product: Hyper-V virtual VGA
 vendor: Microsoft Corporation
 physical id: 8
 bus info: pci@:00:08.0
 version: 00
 width: 32 bits
 clock: 33MHz
 capabilities: vga_controller bus_master rom
 configuration: driver=hyperv_fb latency=0
 resources: irq:11 memory:f800-fbff
 *-scsi:0
  physical id: 2
  logical name: scsi1
  capabilities: emulated
*-cdrom
 description: DVD reader
 physical id: 0.0.0
 bus info: scsi@1:0.0.0
 logical name: /dev/cdrom
 logical name: /dev/dvd
 logical name: /dev/sr0
 capabilities: audio dvd
 configuration: status=nodisc
 *-scsi:1
  physical id: 3
  logical name: scsi2
*-disk
 description: SCSI Disk
 physical id: 0.0.0
 bus info: scsi@2:0.0.0
 logical name: /dev/sda
 size: 15GiB (16GB)
 capabilities: partitioned partitioned:dos
 configuration: logicalsectorsize=512 sectorsize=4096 
signature=053b3857
   *-volume:0
description: Linux filesystem partition
vendor: Linux
physical id: 1
bus info: scsi@2:0.0.0,1
logical name: /dev/sda1
logical name: /boot
version: 1.0
serial: [REMOVED]
size: 487MiB
capacity: 487MiB
capabilities: primary bootable

[Kernel-packages] [Bug 1584042] Re: Hyper-V NIC cannot pass IPv6 UDP packets by default until protocol offload is disabled

Hi ! I'sorry but I can't apport-collect;
Due to ipv4 adress lack and network isolation, my servers are setup ipv6 only 
and launchpad.net only resolves in ipv4

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

Title:
  Hyper-V NIC cannot pass IPv6 UDP packets by default until protocol
  offload is disabled

Status in linux package in Ubuntu:
  Incomplete

Bug description:

  Hi,

  On a client server, I can't get a response from a name server in ipv6+udp. On 
the same server, it works fine in tcp.
  If I log on my name server, I can get a response from himself but, as a 
client, it can't get a response from another name server.

  here are the steps to reproduce : 
  - Create a new server using Ubuntu server 16.04. Set it to use ipv4 and use 
your preferred name server. Select absolutely nothing as functionality. 
  - check some nslookup and apt-get stuff to verify network is OK
  - add ipv6 to the interface and refer to an IPV6 nameserver. I have 3 and 
thats why I noticed the problem >> All 3 ipv6 nameservers are filling the 3 
places in resolv.conf.
  - if you don't have 3 ipv6 nameservers, just add one and comment the line 
with the ipv4 name server.
  - verify your resolv.conf. Should only content ipv6 reference.
  - Now, you can't nslookup anymore... 
  - add some tests : "dig @ipv4server google.com" works but "dig @ipv6server 
google.com" don't

  
  Here a more tests : 

  
  Nameserver1 : Nameserver1.MyDomain :  XXX.YYY.ZZZ.250 / ::::250
  ClientStandAloneServer.MyDomain   :   
XXX.YYY.ZZZ.209 / ::::209

  With IPV4

  
  # dig @XXX.YYY.ZZZ.226 www.google.fr

  /var/log/named/queries.log on Nameserver1:
  20-May-2016 12:25:02.834 queries: info: client XXX.YYY.ZZZ.209#35116 
(www.google.fr): query: www.google.fr IN A +E (XXX.YYY.ZZZ.226)

  Tcp Dump on Nameserver1:
  12:25:02.834092 IP StandAloneServer.MyDomain.35116 > 
Nameserver1.MyDomain.domain: 62949+ [1au] A? www.google.fr. (42)
  12:25:02.834395 IP Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35116: 62949 1/4/5 A 216.58.210.195 (204)

  Tcp Dump on Client
  12:25:02.668200 IP StandAloneServer.MyDomain.35116 > 
Nameserver1.MyDomain.domain: 62949+ [1au] A? www.google.fr. (42)
  12:25:02.669573 IP Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35116: 62949 1/4/5 A 216.58.210.195 (204)

  
  RESULT:

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @XXX.YYY.ZZZ.226 www.google.fr
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 49591
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 5
  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;www.google.fr.   IN  A
  ;; ANSWER SECTION:
  www.google.fr.300 IN  A   216.58.210.195
  ;; AUTHORITY SECTION:
  google.fr.171625  IN  NS  ns1.google.com.
  [TRUNCATED]



  WITH IPV6
  # dig @::::226 www.google.fr 

  NOTE  : I only asked once, it created 3 queries with 5 secs
  d’intervalle environ

  /var/log/named/queries.log on Nameserver1:
  20-May-2016 12:32:34.902 queries: info: client ::::209#35362 
(www.google.fr): query: www.google.fr IN A +E (::::226)
  20-May-2016 12:32:39.902 queries: info: client ::::209#35362 
(www.google.fr): query: www.google.fr IN A +E (::::226)
  20-May-2016 12:32:44.902 queries: info: client ::::209#35362 
(www.google.fr): query: www.google.fr IN A +E (::::226)

  Tcp Dump on Nameserver1:
  12:32:34.902598 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:34.902994 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)
  …
  12:32:39.902644 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:39.902975 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)
  …
  12:32:39.902644 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:39.902975 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)

  
  Tcp Dump on Client12:32:34.725312 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:34.726036 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)
  …
  12:32:39.725199 IP6 StandAloneServer.MyDomain.35362 > 
Nameserver1.MyDomain.domain: 23393+ [1au] A? www.google.fr. (42)
  12:32:39.726045 IP6 Nameserver1.MyDomain.domain > 
StandAloneServer.MyDomain.35362: 23393 1/4/5 A 216.58.210.195 (204)
  …

[Kernel-packages] [Bug 1448566] Re: Ubuntu 15.04 - Macbook Pro Early 2015 (12, 1) Bluetooth disabled

2016-05-03 Thread Jean-Frédéric

Posting this in case it would help someone else: I had the same issue
with 15.10 (with kernel 4.2). I upgraded today to 16.04 (with kernel
4.4.0) and the buletooth is working like a charm.

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

Title:
  Ubuntu 15.04 - Macbook Pro Early 2015 (12,1) Bluetooth disabled

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of 15.04 on a Macbook Pro 12,1.

  I get no Bluetooth icon in the status bar, and in System Settings >
  Bluetooth, everything is greyed out (i.e., can't turn it on).

  
  $lsusb; dmesg | grep -i bluetooth; dmesg | grep -i firmware; rfkill list all; 
lsmod | grep bluetooth; hciconfig -a; uname -a

  Bus 002 Device 002: ID 05ac:8406 Apple, Inc.
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 05ac:0273 Apple, Inc.
  Bus 001 Device 004: ID 05ac:8290 Apple, Inc.
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  [ 32.369395] usb 1-3: Product: Bluetooth USB Host Controller
  [ 32.435743] input: Broadcom Corp. Bluetooth USB Host Controller as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/0003:05AC:8290.0006/input/input7
  [ 32.490662] hid-generic 0003:05AC:8290.0006: input,hidraw5: USB HID v1.11 
Keyboard [Broadcom Corp. Bluetooth USB Host Controller] on 
usb-:00:14.0-3/input0
  [ 32.490750] input: Broadcom Corp. Bluetooth USB Host Controller as 
/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.1/0003:05AC:8290.0007/input/input8
  [ 32.490995] hid-generic 0003:05AC:8290.0007: input,hidraw6: USB HID v1.11 
Mouse [Broadcom Corp. Bluetooth USB Host Controller] on 
usb-:00:14.0-3/input1
  [ 34.866186] Bluetooth: Core ver 2.20
  [ 34.866205] Bluetooth: HCI device and connection manager initialized
  [ 34.866751] Bluetooth: HCI socket layer initialized
  [ 34.866754] Bluetooth: L2CAP socket layer initialized
  [ 34.866759] Bluetooth: SCO socket layer initialized
  [ 0.158493] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
  [ 0.168342] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain  [bus 
00-9b] only partially covers this bridge
  [ 35.003383] brcmfmac :03:00.0: Direct firmware load for 
brcm/brcmfmac43602-pcie.txt failed with error -2
  [ 35.290656] brcmf_c_preinit_dcmds: Firmware version = wl0: Mar 13 2015 
08:11:08 version 7.35.177.36 (r540934) FWID 01-e4dc15b
  0: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no
  bluetooth 491520 1 btusb
  Linux hxn-laptop-linux 3.19.0-15-generic #15-Ubuntu SMP Thu Apr 16 23:32:37 
UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1448566/+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 1359689] Re: cryptsetup password prompt not shown

2016-04-24 Thread Frédéric

I confirm the problem since I upgraded to Lubuntu 16.04.

Does anyone have a solution to remove cryptsetup without reinstall all
the system ?

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

Title:
  cryptsetup password prompt not shown

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Utopic:
  Won't Fix
Status in linux source package in Vivid:
  Triaged
Status in plymouth package in Debian:
  Fix Released

Bug description:
  Currently in utopic the following happens when booting an encrypted
  setup:

  Press enter in grub, after a while screen freezes (or turns completely
  black) and stays like that. When I press the down key, I can see the
  password prompt. When I press the up key again, I get to the graphical
  password prompt.

  This is demonstrated in the following screencast:
  https://drive.google.com/file/d/0B7EMvd1LJKgZREJocHBueEhpa2s/edit?usp=sharing

  Maybe this is related to the version of plymouth utopic currently uses, a 
similar debian bug report seems to be resolved with a newer version 0.9.0-6, 
see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752752.
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821)
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  --- 
  ApportVersion: 2.14.6-0ubuntu2
  Architecture: amd64
  DefaultPlymouth: /lib/plymouth/themes/ubuntu-logo/ubuntu-logo.plymouth
  DistroRelease: Ubuntu 14.10
  InstallationDate: Installed on 2014-08-21 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140821)
  MachineType: Dell Inc. Precision M4600
  Package: plymouth 0.9.0-0ubuntu3
  PackageArchitecture: amd64
  ProcCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.16.0-9-generic 
root=/dev/mapper/VG--Ubuntu-LV--Ubuntu--ROOT ro rootflags=subvol=@ 
cryptopts=target=Ubuntu,source=/dev/disk/by-uuid/6fc200da-aa04-4e73-b6a7-a2326f0b6204,lvm=VG-Ubuntu
 quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.16.0-9.14-generic 3.16.1
  Tags:  utopic
  TextPlymouth: /lib/plymouth/themes/ubuntu-text/ubuntu-text.plymouth
  Uname: Linux 3.16.0-9-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/10/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd03/10/2013:svnDellInc.:pnPrecisionM4600:pvr01:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4600
  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/1359689/+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 1503647] Re: System hangs with kernel 3.19.0-31

2015-10-15 Thread Frédéric Besnard

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

same problem for me, on my vivid system. The henrix's patch fixed it.
Thanx.

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

Title:
  System hangs with kernel 3.19.0-31

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After installing kernel 3.19.0-31, the system freezes at login. I got
  following error during install, I don't know if that is the reason for
  the freeze.

  sudo dpkg-reconfigure linux-headers-3.19.0-31 linux-
  headers-3.19.0-31-generic

  Examining /etc/kernel/header_postinst.d.
  run-parts: executing /etc/kernel/header_postinst.d/dkms 3.19.0-31-generic 
/boot/vmlinuz-3.19.0-31-generic
  ERROR: Cannot create report: [Errno 17] File exists: 
'/var/crash/i915-3.15-3.13-dkms.0.crash'
  Error! Bad return status for module build on kernel: 3.19.0-31-generic 
(x86_64)
  Consult /var/lib/dkms/i915-3.15-3.13/0.01/build/make.log for more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-headers-3.19.0-31-generic 3.19.0-31.35
  ProcVersionSignature: Ubuntu 3.19.0-30.34-generic 3.19.8-ckt6
  Uname: Linux 3.19.0-30-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  simon  2192 F pulseaudio
   /dev/snd/controlC1:  simon  2192 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Oct  7 12:18:47 2015
  HibernationDevice: RESUME=UUID=c929a208-30d1-4e36-9943-d68352b90a26
  InstallationDate: Installed on 2014-07-28 (435 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Notebook W65_67SZ
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic 
root=UUID=da3171d0-cb60-47b3-8584-e10466a6c8a9 ro quiet splash acpi_osi=Linux 
acpi_backlight=vendor vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-30-generic N/A
   linux-backports-modules-3.19.0-30-generic  N/A
   linux-firmware 1.143.4
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/26/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03.05
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SZ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03.05:bd02/26/2014:svnNotebook:pnW65_67SZ:pvrNotApplicable:rvnNotebook:rnW65_67SZ:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SZ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1503647/+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 1467542] [NEW] Add new userspace package 'opal-prd'

Public bug reported:

This is a bug to track the inclusion of opal-prd package in Ubuntu. The
plan is to add it initially for 15.10 and later backport it to 14.04
archive.

opal-prd is a daemon that listens for hardware diagnostic events (by
listening on the /dev/opal-prd device), and executes firmware-
providedexecutable code to handle these events.

For now, the code lives inside https://github.com/open-
power/skiboot/tree/master/external/opal-prd.

** Affects: ubuntu
 Importance: Undecided
 Status: New

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

Title:
  Add new userspace package 'opal-prd'

Status in Ubuntu:
  New

Bug description:
  This is a bug to track the inclusion of opal-prd package in Ubuntu.
  The plan is to add it initially for 15.10 and later backport it to
  14.04 archive.

  opal-prd is a daemon that listens for hardware diagnostic events (by
  listening on the /dev/opal-prd device), and executes firmware-
  providedexecutable code to handle these events.

  For now, the code lives inside https://github.com/open-
  power/skiboot/tree/master/external/opal-prd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1467542/+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 1467542] Re: Add new userspace package 'opal-prd'

Here is a packaging for opal-prd based on what Jeremy Kerr did with some 
improvements.
As I understand, we need opal-prd kernel headers which is tracked in 
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1439562 .
For the time being, Jeremy provided me a -linux-libc-dev .deb for 14.10 so I 
tested everything on 14.10 so far.
Here are the files attached. debian/changelog should be changed otherwise there 
should be no lintian, just a pedantic one for 
debian-watch-may-check-gpg-signature .

** Attachment added: skiboot_5.0.3-1.dsc
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1467542/+attachment/4418568/+files/skiboot_5.0.3-1.dsc

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

Title:
  Add new userspace package 'opal-prd'

Status in Ubuntu:
  New

Bug description:
  This is a bug to track the inclusion of opal-prd package in Ubuntu.
  The plan is to add it initially for 15.10 and later backport it to
  14.04 archive.

  opal-prd is a daemon that listens for hardware diagnostic events (by
  listening on the /dev/opal-prd device), and executes firmware-
  providedexecutable code to handle these events.

  For now, the code lives inside https://github.com/open-
  power/skiboot/tree/master/external/opal-prd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1467542/+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 1467542] Re: Add new userspace package 'opal-prd'

** Attachment added: skiboot_5.0.3-1.debian.tar.xz
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1467542/+attachment/4418570/+files/skiboot_5.0.3-1.debian.tar.xz

** Package changed: linux (Ubuntu) = 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/1467542

Title:
  Add new userspace package 'opal-prd'

Status in Ubuntu:
  New

Bug description:
  This is a bug to track the inclusion of opal-prd package in Ubuntu.
  The plan is to add it initially for 15.10 and later backport it to
  14.04 archive.

  opal-prd is a daemon that listens for hardware diagnostic events (by
  listening on the /dev/opal-prd device), and executes firmware-
  providedexecutable code to handle these events.

  For now, the code lives inside https://github.com/open-
  power/skiboot/tree/master/external/opal-prd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1467542/+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 1467542] Re: Add new userspace package 'opal-prd'