date:20191122

[Kernel-packages] [Bug 1852303] Re: xenial/linux-fips: 4.4.0-1026.31 -proposed tracker

2019-11-22 Thread Ubuntu Kernel Bot

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1852306
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 22. November 2019 19:02 UTC
  reason:
-   promote-signing-to-proposed: Pending -- ready for review
+   promote-signing-to-proposed: Stalled -- ready for review
  variant: debs

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

Title:
  xenial/linux-fips: 4.4.0-1026.31 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Invalid
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Released
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  Confirmed
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  Invalid
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow security-signoff series:
  Invalid
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  Invalid

Bug description:
  This bug will contain status and test results related to a kernel
  source (or snap) as stated in the title.

  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow

  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1852306
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
  phase: Ready for Promote to Proposed
  phase-changed: Friday, 22. November 2019 19:02 UTC
  reason:
promote-signing-to-proposed: Stalled -- ready for review
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852303/+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 1848790] Re: USB not working under arm64 on Pi4 with 4G ram

2019-11-22 Thread Hui Wang

Please ignore the #36, the boot.scr in the http://cdimage.ubuntu.com
/ubuntu-server/eoan/daily-preinstalled/20191122/ has some problem.

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

Title:
  USB not working under arm64 on Pi4 with 4G ram

Status in linux-raspi2 package in Ubuntu:
  Confirmed
Status in linux-raspi2 source package in Eoan:
  Fix Released

Bug description:
  Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard
  which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10
  armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the
  keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the
  keyboard worked successfully.

  Output of lsusb under arm64 on a Pi 3:

  ubuntu@ubuntu:~$ lsusb
  Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
  Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
  Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of lsusb under armhf on a Pi 4 (same keyboard attached):

  ubuntu@ubuntu:~$ lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard
  Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Output of lsusb under arm64 on the same Pi 4 (same keyboard attached):

  ubuntu@ubuntu:~$ lsusb
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  The fact even the VIA Labs hub doesn't show up (which is built in)
  suggests the kernel is (for some reason) unable to enumerate anything
  against the USB hubs.

  
  == Temporary Workaround ==

  As noted by various people below, the following line can be added to
  the "usercfg.txt" file on the boot partition:

  total_mem=3072

  This will limit the available RAM to 3Gb, but otherwise things should
  operate normally. Note that this bug does not affect Pi 4Bs with less
  than 4Gb of RAM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+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 1852035] Re: Cannot use full resolution (2560x1440) of Dell U2715H

2019-11-22 Thread Hui Wang

Could you tell us the detailed steps to install the desktop on the rpi4
board? Since we only released the server version, there is no desktop in
the server version.

And the detailed steps to reproduce this issue.


Then we will setup the same environment to debug this issue.

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

Title:
  Cannot use full resolution (2560x1440) of Dell U2715H

Status in linux-raspi2 package in Ubuntu:
  Confirmed

Bug description:
  While using Ubuntu 19.10 with either MATE or GNOME, I can use only
  1920x1080 resolution instead of the full 2560x1440.  If extra pixels
  are configured, they fall off the right side or bottom of the display
  and are not visible.  Reproduced on Raspberry Pi 4  with 3GB max
  workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: User Name 5.3.0-1008.9-raspi2 5.3.1
  Uname: Linux 5.3.0-1008-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 10 18:18:23 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 cma=64M cma=256M 
video=HDMI-A-1:1920x1080@60 smsc95xx.macaddr=DC:A6:32:38:DF:15 
vc_mem.mem_base=0x3ec0 vc_mem.mem_size=0x4000  net.ifnames=0 
dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=LABEL=writable 
rootfstype=ext4 elevator=deadline rootwait
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1852035/+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 1849721] Re: Raydium Touchscreen on ThinkPad L390 does not work

2019-11-22 Thread Kai-Heng Feng

Can you please try this kernel:
https://people.canonical.com/~khfeng/lp1849721-4/

Which included this commit:
commit 0c8432236dea20a95f68fa17989ea3f8af0186a5
Author: Aaron Ma 
Date:   Thu Nov 14 03:12:47 2019 +0800

HID: i2c-hid: fix no irq after reset on raydium 3118

On some ThinkPad L390 some raydium 3118 touchscreen devices
doesn't response any data after reset, but some does.

Add this ID to no irq quirk,
then don't wait for any response alike on these touchscreens.
All kinds of raydium 3118 devices work fine.

BugLink: https://bugs.launchpad.net/bugs/1849721

Signed-off-by: Aaron Ma 
Signed-off-by: Jiri Kosina 

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

Title:
  Raydium Touchscreen on ThinkPad L390 does not work

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I have bought new Lenovo ThinkPad L390 with touchscreen and it works fine on 
Windows, but not on Ubuntu.
  I've tried Ubuntu LTS 18.4, 19.4 and 19.10. I've tried installing Ubuntu and 
running Live USB image, and also other distributions (Manjaro i3, Kubuntu).
  There is an Ubuntu certification with the same touchscreen using Ubuntu 18.4: 
https://certification.ubuntu.com/hardware/201812-26720

  Other info:
  - `xinput` is showing touchscreen: "Raydium Touchscreen id=10 [slave pointer 
(2)]"
  - if I list device props using `xinput list-props 10`, I see device: `Device 
Node (277): "/dev/input/event9"`
  - `cat /dev/input/event9` does not produce anything
  - `xinput --test-xi2 --root` does not produce any touchscreen events, even 
though events from other devices are successfully shown

  Also, attached `ubuntu-bug` report.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1821 F pulseaudio
  CasperVersion: 1.427
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 24 18:32:07 2019
  LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20NRCTO1WW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed quiet splash ---
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-18-generic N/A
   linux-backports-modules-5.3.0-18-generic  N/A
   linux-firmware1.183
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/12/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R10ET39W (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NRCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR10ET39W(1.24):bd08/12/2019:svnLENOVO:pn20NRCTO1WW:pvrThinkPadL390:rvnLENOVO:rn20NRCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L390
  dmi.product.name: 20NRCTO1WW
  dmi.product.sku: LENOVO_MT_20NR_BU_Think_FM_ThinkPad L390
  dmi.product.version: ThinkPad L390
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1849721/+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 1853005] Re: Wifi drops out at large bandwidth usage

2019-11-22 Thread thedoctar

** Summary changed:

- Wifi randomly drops out
+ Wifi drops out at large bandwidth usage

** Description changed:

System: Linux Dell-XPS-13-9360 4.15.0-70-generic #79-Ubuntu SMP Tue Nov
12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

- Problem: Wifi randomly drops out. For example, I had trouble downloading
- a folder from a ssh server at uni. During the download, the wifi
- stopped. In the log of journalctl --follow, I found many records of the
- kernel complaining about an unknown pci event, which I think is related
- to the wifi dropping out. The output of journalctl --follow during the
- wifi drop outs is attached as the file log.txt. I deleted all entries
- from Nautilus and plank.desktop.
+ Problem: Wifi drops out with large bandwidth usage. For example, I had
+ trouble downloading a folder from a ssh server at uni. During the
+ download, the wifi stopped. In the log of journalctl --follow, I found
+ many records of the kernel complaining about an unknown pci event, which
+ I think is related to the wifi dropping out. The output of journalctl
+ --follow during the wifi drop outs is attached as the file log.txt. I
+ deleted all entries from Nautilus and plank.desktop.

Additional notes: simply turning the wifi on and off again re-
establishes the connection, but obviously irritating if I need to
download lots of files from a ssh server. Furthermore, my iPad has
internet connection after my Linux laptop wifi drops out, so the problem
is not the router/ISP.

- Update: limiting the download speed allowed me to download from the ssh
- server. scp -r -l 100 user@address:~/Documents/Textbooks ./
+ Limiting the download speed allowed me to download from the ssh server.
+ scp -r -l 100 user@address:~/Documents/Textbooks ./

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-70-generic 4.15.0-70.79
ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
Uname: Linux 4.15.0-70-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: albert 2011 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 18 14:31:06 2019
HibernationDevice: RESUME=UUID=9f8b6855-caac-4e96-91bd-b366050fd722
InstallationDate: Installed on 2017-02-26 (995 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64
(20170215.2)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp.
Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc.
Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. XPS 13 9360
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-70-generic
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
linux-restricted-modules-4.15.0-70-generic N/A
linux-backports-modules-4.15.0-70-generic N/A
linux-firmware 1.173.12
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-10-06 (407 days ago)
dmi.bios.date: 05/26/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.12.0
dmi.board.name: 0T3FTF
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.12.0:bd05/26/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0T3FTF:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 9360
dmi.sys.vendor: Dell Inc.

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

Title:
Wifi drops out at large bandwidth usage

Status in linux package in Ubuntu:
Confirmed

Bug description:
System: Linux Dell-XPS-13-9360 4.15.0-70-generic #79-Ubuntu SMP Tue
Nov 12 10:36:11 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Problem: Wifi drops out with large bandwidth usage. For example, I had
trouble downloading a folder from a ssh server at uni. During the
download, the wifi stopped. In the log of journalctl --follow, I found
many records of the kernel complaining about an unknown pci event,
which I think is related to the wifi dropping out. The output of
journalctl --follow during the wifi drop outs is attached as the file
log.txt. I deleted all entries from Nautilus and plank.desktop.

1 2 >

1 - 100 of 145 matches

Mail list logo