[Kernel-packages] [Bug 491852] Re: KMS - RADEON - DRM - BUG: unable to handle kernel NULL pointer dereference

[Bug Watch Updater]

Launchpad has imported 5 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=24340.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-10-05T23:09:17+00:00 octoploid wrote:

Created attachment 30104
Kernel log

I've got this BUG twice in the last couple of days.
I'm running the latest git kernel (rc3), xf86-video-ati, mesa
and libdrm. 
This happens in KMS mode in the middle of the night. After
the BUG happens the machine kept running and it is only in the
morning, when I exit the screensaver, that the machine hangs.

Oct 06 04:51:26 [kernel] BUG: unable to handle kernel NULL pointer dereference 
at 0168
Oct 06 04:51:26 [kernel] IP: [] 
radeon_object_list_unreserve+0x13/0x34
Oct 06 04:51:26 [kernel] PGD 11e64c067 PUD 11d3f4067 PMD 0 
Oct 06 04:51:26 [kernel] CPU 1 
Oct 06 04:51:26 [kernel] Pid: 1899, comm: X Not tainted 
2.6.32-rc3-00049-g19d031e #6 System Product Name
Oct 06 04:51:26 [kernel] RIP: 0010:[]  [] 
radeon_object_list_unreserve+0x13/0x34
Oct 06 04:51:26 [kernel] RSP: 0018:88011e7a1c68  EFLAGS: 00010206
Oct 06 04:51:26 [kernel] RAX: 88011fa94930 RBX: 88011f2a8d78 RCX: 

Oct 06 04:51:26 [kernel] RDX: 88011d977850 RSI: 0286 RDI: 

Oct 06 04:51:26 [kernel] RBP: 88011e7a1c78 R08:  R09: 
880028292180
Oct 06 04:51:26 [kernel] R10: 00173396cc90 R11: 88011f962f00 R12: 
88011e7a1d18
Oct 06 04:51:26 [kernel] R13: 88011f2a8000 R14:  R15: 
811f9ef1
Oct 06 04:51:26 [kernel] FS:  7f24d1ad96f0() GS:88002828() 
knlGS:
Oct 06 04:51:26 [kernel] CS:  0010 DS:  ES:  CR0: 80050033
Oct 06 04:51:26 [kernel] CR2: 0168 CR3: 00011c872000 CR4: 
06e0
Oct 06 04:51:26 [kernel] DR0:  DR1:  DR2: 

Oct 06 04:51:26 [kernel] DR3:  DR6: 0ff0 DR7: 
0400
Oct 06 04:51:26 [kernel] Process X (pid: 1899, threadinfo 88011e7a, 
task 88011f9dc1d0)
Oct 06 04:51:26 [kernel]  88011e7a1cd8 88011f2a8dd8 88011e7a1c88 
811ee136
Oct 06 04:51:26 [kernel] <0> 88011e7a1cb8 811f99a6 88011e7a1cd8 
88011e7a1cd8
Oct 06 04:51:26 [kernel] <0> 88011f2a8dd8 88011f2a8000 88011e7a1d68 
811fa06b
Oct 06 04:51:26 [kernel]  [] radeon_object_list_clean+0x9/0xb
Oct 06 04:51:26 [kernel]  [] radeon_cs_parser_fini+0x24/0xf9
Oct 06 04:51:26 [kernel]  [] radeon_cs_ioctl+0x17a/0x193
Oct 06 04:51:26 [kernel]  [] drm_ioctl+0x223/0x2c9
Oct 06 04:51:26 [kernel]  [] ? do_sync_read+0xe3/0x120
Oct 06 04:51:26 [kernel]  [] vfs_ioctl+0x6a/0x82
Oct 06 04:51:26 [kernel]  [] do_vfs_ioctl+0x473/0x4b9
Oct 06 04:51:26 [kernel]  [] sys_ioctl+0x42/0x65
Oct 06 04:51:26 [kernel]  [] system_call_fastpath+0x16/0x1b
Oct 06 04:51:26 [kernel] RIP  [] 
radeon_object_list_unreserve+0x13/0x34
Oct 06 04:51:26 [kernel]  RSP 
Oct 06 04:51:26 [kernel] ---[ end trace fa4572652ee9a268 ]---
Oct 06 04:51:26 [kernel] Unpin not necessary for 88011d976800 !
Oct 06 04:51:26 [kernel] [drm:drm_release] *ERROR* Device busy: 1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/491852/comments/0


On 2009-10-05T23:10:15+00:00 octoploid wrote:

Created attachment 30105
Kernel config

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/491852/comments/1


On 2010-02-28T09:05:06+00:00 Mpupat wrote:

I have had my machine completely freezing with the same sort of message
showing up in the logs. Attached is an example of it.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/491852/comments/19


On 2010-02-28T09:06:52+00:00 Mpupat wrote:

Created attachment 33644
Log for when a similar issue happened

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/491852/comments/20


On 2019-11-19T08:08:08+00:00 Martin-peres-n wrote:

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/drm/amd/issues/73.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/491852/comments/21


** Changed in: linux
   Status: Confirmed => Unknown

** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #73
   

[Kernel-packages] [Bug 943263]

[Martin-peres-n]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/drm/amd/issues/231.

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

Title:
  PC display will not turn on with Llano APUs connected to the VGA port

Status in Linux:
  Unknown
Status in linux package in Ubuntu:
  Fix Released

Bug description:
  The PC has a Llano A6-3650 APU with a display connected to the VGA
  port, but the display turns off when plymouth should appear, thus
  making installation from liveCD/USB impossible. Ubuntu starts up, as I
  can hear the login sound, but nothing is visible.

  Filed separately, as requested in bug #825777, as this one is about a PC, and 
the other one is about laptops.
  ---
  Ubuntu Bug Squad volunteer triager
  http://wiki.ubuntu.com/BugSquad

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: linux-image-3.0.0-16-generic-pae 3.0.0-16.28
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic-pae 3.0.17
  Uname: Linux 3.0.0-16-generic-pae i686
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 1.23-0ubuntu4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  evfool 1592 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Generic'/'HD-Audio Generic at 0xfe01c000 irq 52'
 Mixer name : 'ATI R6xx HDMI'
 Components : 'HDA:1002aa01,00aa0100,00100200'
 Controls  : 4
 Simple ctrls  : 1
  Card0.Amixer.values:
   Simple mixer control 'IEC958',0
 Capabilities: pswitch pswitch-joined penum
 Playback channels: Mono
 Mono: Playback [on]
  Card1.Amixer.info:
   Card hw:1 'Generic_1'/'HD-Audio Generic at 0xfe02 irq 16'
 Mixer name : 'Realtek ALC889'
 Components : 'HDA:10ec0889,1458a132,0014'
 Controls  : 37
 Simple ctrls  : 22
  CheckboxSubmission: 589b7562703a9b18f8c7bdabc7186c59
  CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2
  Date: Wed Feb 29 15:48:11 2012
  HibernationDevice: RESUME=UUID=1b7f7f1a-53b1-4d7a-95df-6862c754e92e
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  IwConfig:
   lono wireless extensions.
   
   eth0  no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. GA-A75M-UD2H
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic-pae 
root=UUID=9cafb3fa-9832-4949-bf09-039fbc4a9df6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.0.0-16-generic-pae N/A
   linux-backports-modules-3.0.0-16-generic-pae  N/A
   linux-firmware1.60
  RfKill:
   
  SourcePackage: linux
  UpgradeStatus: Upgraded to oneiric on 2011-11-21 (100 days ago)
  WifiSyslog:
   
  dmi.bios.date: 11/03/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F5
  dmi.board.name: GA-A75M-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd11/03/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-A75M-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/943263/+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 1826691] Re: fwupd hangs after 19.04 upgrade from 18.10

[Bug Watch Updater]

Launchpad has imported 2 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=110604.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-05-04T04:26:59+00:00 Jason Pritchard wrote:

Created attachment 144154
Test file: read-dpcd.c

While working with the Ubuntu maintainers of fwupd, they've determined
that I have an issue with the AMD driver on Ubuntu's 5.0 kernel in
19.04. In the sample program that they provided (see read-dpcd.c
attached) the call to aux_read(fd, REG_RC_CAP, buf, 1) hangs on my
machine. They recommended I post the issue here.

Machine is a Dell 7730 with AMD WX4150 graphics.

See the original bug report here:
https://bugs.launchpad.net/ubuntu/+source/fwupd/+bug/1826691


Not sure if it's related, but here are dmesg warnings from the other ticket.

Apr 23 19:29:14 texas kernel: [ 133.673290] [drm] REG_WAIT timeout 10us * 160 
tries - submit_channel_request line:246
Apr 23 19:29:14 texas kernel: [ 133.673348] WARNING: CPU: 6 PID: 2467 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/dc_helper.c:249 
generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
Apr 23 19:29:14 texas kernel: [ 133.673349] Modules linked in: thunderbolt 
rfcomm xt_owner ip6table_filter ip6_tables ipt_MASQUERADE iptable_nat 
nf_nat_ipv4 nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bridge 
xt_CHECKSUM xt_tcpudp stp llc iptable_filter iptable_mangle bpfilter ccm 
snd_hda_codec_realtek snd_hda_codec_generic pci_stub vboxpci(OE) vboxnetadp(OE) 
vboxnetflt(OE) cmac vboxdrv(OE) bnep binfmt_misc dell_rbtn nls_iso8859_1 joydev 
arc4 snd_soc_skl snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc 
snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi 
snd_soc_core snd_compress ac97_bus intel_rapl snd_pcm_dmaengine 
x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel 
snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep crct10dif_pclmul i915 
snd_pcm crc32_pclmul iwlmvm uvcvideo amdgpu snd_seq_midi ghash_clmulni_intel 
snd_seq_midi_event mac80211 videobuf2_vmalloc kvmgt videobuf2_memops vfio_mdev 
videobuf2_v4l2 snd_rawmidi dell_laptop mdev videobuf2_common
Apr 23 19:29:14 texas kernel: [ 133.673362] ledtrig_audio vfio_iommu_type1 
videodev dell_smm_hwmon vfio snd_seq dell_wmi media kvm chash btusb 
snd_seq_device amd_iommu_v2 btrtl snd_timer btbcm dell_smbios gpu_sched 
irqbypass btintel dcdbas ttm aesni_intel iwlwifi bluetooth drm_kms_helper 
aes_x86_64 crypto_simd cryptd glue_helper rtsx_pci_ms input_leds snd drm 
ecdh_generic intel_cstate mei_me ucsi_acpi cfg80211 serio_raw 
dell_wmi_descriptor intel_wmi_thunderbolt wmi_bmof memstick i2c_algo_bit mei 
fb_sys_fops intel_rapl_perf idma64 syscopyarea hid_multitouch 
processor_thermal_device soundcore sysfillrect virt_dma typec_ucsi sysimgblt 
intel_soc_dts_iosf intel_pch_thermal typec int3403_thermal int340x_thermal_zone 
dell_smo8800 acpi_pad intel_hid int3400_thermal mac_hid acpi_thermal_rel 
sparse_keymap sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables 
autofs4 hid_generic rtsx_pci_sdmmc nvme e1000e i2c_i801 intel_lpss_pci rtsx_pci 
nvme_core intel_lpss i2c_hid wmi hid video pinctrl_cannonlake pinctrl_intel
Apr 23 19:29:14 texas kernel: [ 133.673381] CPU: 6 PID: 2467 Comm: fwupd 
Tainted: G OE 5.0.0-13-generic #14-Ubuntu
Apr 23 19:29:14 texas kernel: [ 133.673382] Hardware name: Dell Inc. Precision 
7730/05W5TJ, BIOS 1.7.0 02/19/2019
Apr 23 19:29:14 texas kernel: [ 133.673417] RIP: 
0010:generic_reg_wait.cold.3+0x25/0x2c [amdgpu]
Apr 23 19:29:14 texas kernel: [ 133.673418] Code: e9 37 7e fe ff 44 8b 45 20 48 
8b 4d 18 48 c7 c7 40 34 17 c1 8b 55 10 8b 75 d4 e8 3b ce 82 e1 41 83 7d 20 01 
0f 84 0c c3 fe ff <0f> 0b e9 05 c3 fe ff 55 48 89 e5 e8 5d de ec ff 48 c7 c7 00 
a0 18
Apr 23 19:29:14 texas kernel: [ 133.673419] RSP: 0018:bbaa0612fbb0 EFLAGS: 
00010297
Apr 23 19:29:14 texas kernel: [ 133.673420] RAX: 0049 RBX: 
00a1 RCX: 
Apr 23 19:29:14 texas kernel: [ 133.673420] RDX:  RSI: 
94843c196448 RDI: 94843c196448
Apr 23 19:29:14 texas kernel: [ 133.673420] RBP: bbaa0612fbf8 R08: 
0001 R09: 04fa
Apr 23 19:29:14 texas kernel: [ 133.673421] R10: 0004 R11: 
 R12: 5c04
Apr 23 19:29:14 texas kernel: [ 133.673421] R13: 948431de5840 R14: 
 R15: 948431de5840
Apr 23 19:29:14 texas kernel: [ 133.673422] FS: 7ff849b11b40() 
GS:94843c18() knlGS:
Apr 23 19:29:14 texas kernel: [ 133.673422] CS: 0010 DS:  ES:  CR0: 
80050033
Apr 23 19:29:14 texas kernel: [ 133.673423] CR2: 7ff83400f6d8 CR3: 
000847680006 CR4: 003606e0
Apr 23 19:29:14 texas kernel: 

[Kernel-packages] [Bug 1852268] Re: bionic/linux-aws-fips: 4.15.0-2005.5 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/prepare-package
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-lrm
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: Fix Committed => Fix Released

** 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 --
  kernel-stable-master-bug: 1852270
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
- phase: Packaging
- phase-changed: Tuesday, 19. November 2019 10:20 UTC
+ phase: Holding before Promote to Proposed
+ phase-changed: Tuesday, 19. November 2019 16:50 UTC
  reason:
-   prepare-package: Stalled -- package tag not yet published
-   prepare-package-lrm: Stalled -- package tag not yet published
-   prepare-package-meta: Stalled -- package tag not yet published
-   prepare-package-signed: Stalled -- package tag not yet published
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
  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/1852268

Title:
  bionic/linux-aws-fips: 4.15.0-2005.5 -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-lrm 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:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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 Bionic:
  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 --
  kernel-stable-master-bug: 1852270
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Holding before Promote to Proposed
  phase-changed: Tuesday, 19. November 2019 16:50 UTC
  reason:
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852268/+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 1852287] Re: xenial/linux-deeplens: 4.15.0-1013.13 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

** 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 --
  kernel-stable-master-bug: 1852288
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
- phase: Ready for Packaging
- phase-changed: Monday, 18. November 2019 15:51 UTC
+ phase: Packaging
+ phase-changed: Tuesday, 19. November 2019 16:50 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
  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/1852287

Title:
  xenial/linux-deeplens: 4.15.0-1013.13 -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:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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:
  Invalid
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 --
  kernel-stable-master-bug: 1852288
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Packaging
  phase-changed: Tuesday, 19. November 2019 16:50 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852287/+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 1839097] Re: [ 54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0

[Bug Watch Updater]

Launchpad has imported 4 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=111333.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-08-08T15:41:26+00:00 Mike wrote:

I see redline in dmesg:
[   54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen 
encoder in use 0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  Uname: Linux 5.2.0-050200-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  6 10:54:51 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] 
[1002:9495] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP 
[1002:0028]
  InstallationDate: Installed on 2018-12-22 (226 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.2.0-050200-generic 
root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro text 
resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/21/2007
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: L1.71
  dmi.board.name: ConRoe865PE
  dmi.board.version: 3.00
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00:
  dmi.product.name: ConRoe865PE
  dmi.product.version: 3.00
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839097/comments/10


On 2019-08-08T16:39:33+00:00 Alexdeucher wrote:

Are you actually seeing any problems or is it just the message you are
concerned about?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839097/comments/12


On 2019-08-08T19:43:34+00:00 Mike wrote:

Created attachment 144986
attachment-30209-0.html

bugzilla-dae...@freedesktop.org pisze:
>
> *Comment # 1  
> on bug 111333  
> from Alex Deucher  *
> Are you actually seeing any problems or is it just the message you are
> concerned about?
> 
> You are receiving this mail because:
>
>   * You reported the bug.
>
The only one redline message in log is concerning.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839097/comments/13


On 2019-11-19T09:35:32+00:00 Martin-peres-n wrote:

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/drm/amd/issues/868.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839097/comments/14


** Changed in: linux
   Importance: Unknown => Medium

** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #868
   https://gitlab.freedesktop.org/drm/amd/issues/868

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

Title:
  [   54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR*
  chosen encoder in use 0

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

Bug description:
  Purged Open source PPA and problem persists:
  [   54.401642] [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen 
encoder in use 0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  

[Kernel-packages] [Bug 1852268] Re: bionic/linux-aws-fips: 4.15.0-2005.5 -proposed tracker

[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 --
  kernel-stable-master-bug: 1852270
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Packaging
  phase-changed: Tuesday, 19. November 2019 10:20 UTC
  reason:
prepare-package: Stalled -- package tag not yet published
prepare-package-lrm: Stalled -- package tag not yet published
prepare-package-meta: Stalled -- package tag not yet published
prepare-package-signed: Stalled -- package tag not yet published
-   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
  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/1852268

Title:
  bionic/linux-aws-fips: 4.15.0-2005.5 -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 Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Committed
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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 Bionic:
  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 --
  kernel-stable-master-bug: 1852270
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Packaging
  phase-changed: Tuesday, 19. November 2019 10:20 UTC
  reason:
prepare-package: Stalled -- package tag not yet published
prepare-package-lrm: Stalled -- package tag not yet published
prepare-package-meta: Stalled -- package tag not yet published
prepare-package-signed: Stalled -- package tag not yet published
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,meta:depwait,signed:depwait
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852268/+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 1852287] Re: xenial/linux-deeplens: 4.15.0-1013.13 -proposed tracker

[Manoj Iyer]

** Summary changed:

- xenial/linux-deeplens:  -proposed tracker
+ xenial/linux-deeplens: 4.15.0-1013.13 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer 
(manjo)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Manoj Iyer 
(manjo)

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

Title:
  xenial/linux-deeplens: 4.15.0-1013.13 -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:
  New
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Invalid
Status in Kernel SRU Workflow security-signoff series:
  New
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 --
  kernel-stable-master-bug: 1852288
  packages:
main: linux-deeplens
meta: linux-meta-deeplens
  phase: Ready for Packaging
  phase-changed: Monday, 18. November 2019 15:51 UTC
  reason:
prepare-package: Pending -- version not specified
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852287/+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 1852335] Re: Xenial update: 4.4.201 upstream stable release

[Connor Kuehl]

The following patches were NOT applied from this upstream stable update
in favor of their UBUNTU SAUCE equivalents:

* drm/i915/gtt: Add read only pages to gen8_pte_encode
* drm/i915/gtt: Read-only pages for insert_entries on bdw+
* drm/i915/gtt: Disable read-only support under GVT
* drm/i915: Rename gen7 cmdparser tables
* drm/i915: Disable Secure Batches for gen6+
* drm/i915: Remove Master tables from cmdparser
* drm/i915: Add support for mandatory cmdparsing
* drm/i915: Support ro ppgtt mapped cmdparser shadow buffers
* drm/i915: Allow parsing of unsized batches
* drm/i915: Add gen9 BCS cmdparsing
* drm/i915/cmdparser: Add support for backward jumps
* drm/i915/cmdparser: Ignore Length operands during command matching
* drm/i915: Lower RM timeout to avoid DSI hard hangs
* drm/i915/gen8+: Add RC6 CTX corruption WA
* drm/i915/cmdparser: Fix jump whitelist clearing

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

Title:
  Xenial update: 4.4.201 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

  * CDC-NCM: handle incomplete transfer of MTU
  * net: fix data-race in neigh_event_send()
  * NFC: fdp: fix incorrect free object
  * NFC: st21nfca: fix double free
  * qede: fix NULL pointer deref in __qede_remove()
  * nfc: netlink: fix double device reference drop
  * ALSA: bebob: fix to detect configured source of sampling clock for 
Focusrite Saffire Pro i/o series
  * ALSA: hda/ca0132 - Fix possible workqueue stall
  * mm, vmstat: hide /proc/pagetypeinfo from normal users
  * dump_stack: avoid the livelock of the dump_lock
  * perf tools: Fix time sorting
  * drm/radeon: fix si_enable_smc_cac() failed issue
  * ceph: fix use-after-free in __ceph_remove_cap()
  * iio: imu: adis16480: make sure provided frequency is positive
  * netfilter: nf_tables: Align nft_expr private data to 64-bit
  * netfilter: ipset: Fix an error code in ip_set_sockfn_get()
  * can: usb_8dev: fix use-after-free on disconnect
  * can: c_can: c_can_poll(): only read status register after status IRQ
  * can: peak_usb: fix a potential out-of-sync while decoding packets
  * can: gs_usb: gs_can_open(): prevent memory leak
  * can: peak_usb: fix slab info leak
  * drivers: usb: usbip: Add missing break statement to switch
  * configfs: fix a deadlock in configfs_symlink()
  * PCI: tegra: Enable Relaxed Ordering only for Tegra20 & Tegra30
  * scsi: qla2xxx: fixup incorrect usage of host_byte
  * scsi: lpfc: Honor module parameter lpfc_use_adisc
  * ipvs: move old_secure_tcp into struct netns_ipvs
  * bonding: fix unexpected IFF_BONDING bit unset
  * usb: fsl: Check memory resource before releasing it
  * usb: gadget: udc: atmel: Fix interrupt storm in FIFO mode.
  * usb: gadget: composite: Fix possible double free memory bug
  * usb: gadget: configfs: fix concurrent issue between composite APIs
  * perf/x86/amd/ibs: Fix reading of the IBS OpData register and thus precise 
RIP validity
  * USB: Skip endpoints with 0 maxpacket length
  * scsi: qla2xxx: stop timer in shutdown path
  * net: hisilicon: Fix "Trying to free already-free IRQ"
  * NFSv4: Don't allow a cached open with a revoked delegation
  * igb: Fix constant media auto sense switching when no cable is connected
  * e1000: fix memory leaks
  * can: flexcan: disable completely the ECC mechanism
  * mm/filemap.c: don't initiate writeback if mapping has no dirty pages
  * cgroup,writeback: don't switch wbs immediately on dead wbs if the memcg is 
dead
  * net: prevent load/store tearing on sk->sk_stamp
  * Linux 4.4.201
  * UBUNTU: upstream stable to v4.4.201

     4.4.201 upstream stable release
     from git://git.kernel.org/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852335/+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 1852335] Re: Xenial update: 4.4.201 upstream stable release

[Connor Kuehl]

** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ * CDC-NCM: handle incomplete transfer of MTU
+ * net: fix data-race in neigh_event_send()
+ * NFC: fdp: fix incorrect free object
+ * NFC: st21nfca: fix double free
+ * qede: fix NULL pointer deref in __qede_remove()
+ * nfc: netlink: fix double device reference drop
+ * ALSA: bebob: fix to detect configured source of sampling clock for 
Focusrite Saffire Pro i/o series
+ * ALSA: hda/ca0132 - Fix possible workqueue stall
+ * mm, vmstat: hide /proc/pagetypeinfo from normal users
+ * dump_stack: avoid the livelock of the dump_lock
+ * perf tools: Fix time sorting
+ * drm/radeon: fix si_enable_smc_cac() failed issue
+ * ceph: fix use-after-free in __ceph_remove_cap()
+ * iio: imu: adis16480: make sure provided frequency is positive
+ * netfilter: nf_tables: Align nft_expr private data to 64-bit
+ * netfilter: ipset: Fix an error code in ip_set_sockfn_get()
+ * can: usb_8dev: fix use-after-free on disconnect
+ * can: c_can: c_can_poll(): only read status register after status IRQ
+ * can: peak_usb: fix a potential out-of-sync while decoding packets
+ * can: gs_usb: gs_can_open(): prevent memory leak
+ * can: peak_usb: fix slab info leak
+ * drivers: usb: usbip: Add missing break statement to switch
+ * configfs: fix a deadlock in configfs_symlink()
+ * PCI: tegra: Enable Relaxed Ordering only for Tegra20 & Tegra30
+ * scsi: qla2xxx: fixup incorrect usage of host_byte
+ * scsi: lpfc: Honor module parameter lpfc_use_adisc
+ * ipvs: move old_secure_tcp into struct netns_ipvs
+ * bonding: fix unexpected IFF_BONDING bit unset
+ * usb: fsl: Check memory resource before releasing it
+ * usb: gadget: udc: atmel: Fix interrupt storm in FIFO mode.
+ * usb: gadget: composite: Fix possible double free memory bug
+ * usb: gadget: configfs: fix concurrent issue between composite APIs
+ * perf/x86/amd/ibs: Fix reading of the IBS OpData register and thus precise 
RIP validity
+ * USB: Skip endpoints with 0 maxpacket length
+ * scsi: qla2xxx: stop timer in shutdown path
+ * net: hisilicon: Fix "Trying to free already-free IRQ"
+ * NFSv4: Don't allow a cached open with a revoked delegation
+ * igb: Fix constant media auto sense switching when no cable is connected
+ * e1000: fix memory leaks
+ * can: flexcan: disable completely the ECC mechanism
+ * mm/filemap.c: don't initiate writeback if mapping has no dirty pages
+ * cgroup,writeback: don't switch wbs immediately on dead wbs if the memcg is 
dead
+ * net: prevent load/store tearing on sk->sk_stamp
+ * Linux 4.4.201
+ * UBUNTU: upstream stable to v4.4.201
  
-4.4.201 upstream stable release
-from git://git.kernel.org/
+    4.4.201 upstream stable release
+    from git://git.kernel.org/

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

Title:
  Xenial update: 4.4.201 upstream stable release

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Xenial:
  In Progress

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

  * CDC-NCM: handle incomplete transfer of MTU
  * net: fix data-race in neigh_event_send()
  * NFC: fdp: fix incorrect free object
  * NFC: st21nfca: fix double free
  * qede: fix NULL pointer deref in __qede_remove()
  * nfc: netlink: fix double device reference drop
  * ALSA: bebob: fix to detect configured source of sampling clock for 
Focusrite Saffire Pro i/o series
  * ALSA: hda/ca0132 - Fix possible workqueue stall
  * mm, vmstat: hide /proc/pagetypeinfo from normal users
  * dump_stack: avoid the livelock of the dump_lock
  * perf 

[Kernel-packages] [Bug 1852282] Re: xenial/linux-azure: 4.15.0-1064.69 -proposed tracker

[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 --
  kernel-stable-master-bug: 1852289
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Ready for Packaging
- phase-changed: Thursday, 14. November 2019 09:12 UTC
+ phase: Packaging
+ phase-changed: Tuesday, 19. November 2019 16:08 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  trackers:
trusty/linux-azure: bug 1852281
xenial/linux-azure-edge: bug 1852280
xenial/linux-azure/azure-kernel: bug 1852279
  variant: debs

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

Title:
  xenial/linux-azure: 4.15.0-1064.69 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
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:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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 --
  kernel-stable-master-bug: 1852289
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Packaging
  phase-changed: Tuesday, 19. November 2019 16:08 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  trackers:
trusty/linux-azure: bug 1852281
xenial/linux-azure-edge: bug 1852280
xenial/linux-azure/azure-kernel: bug 1852279
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852282/+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 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

[Pavel]

Guys, try to set sleep state from Linux to Windows in BIOS settings. It
seems worked for me.

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

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

  Terminology in case we use different terms:
  touchpad - just the rectangular touch-sensitive surface below the keyboard 
(xinput lists it as Synaptics TM3288-011)
  trackpoint - the red thingy built into the keyboard + 3 physical buttons 
below the keyboard (trackpoint and buttons are integrated together; listed in 
xinput as TPPS/2 Elan TrackPoint)

  On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
  enables proper S3 deep sleep state - users no longer have to patch
  DSDT tables to get it. It can be enabled in the BIOS settings. In X1
  carbon 6th generation models that have NFC, when laptop wakes from
  suspend by opening the lid, in most cases both touchpad and trackpoint
  stop working completely. They are also no longer listed when running
  xinput command. Sometimes just one of them stops working, usually the
  trackpoint. In some rare cases it is possible to bring them back by
  using these commands:

  echo -n none > /sys/devices/platform/i8042/serio1/drvctl
  echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
  rmmod psmouse
  modprobe psmouse

  These worked properly when waking up from S2Idle sleep state (had
  these in a script that runs after waking the machine from suspend),
  but with S3 deep sleep these rarely work and the only way to bring
  back touchpad and/or trackpoint is turning off the machine and turning
  it on (restart does not help).

  I could not find any pattern that would show when the input devices
  stop working or start working again using the commands mentioned
  above. It's completely random from my perspective.

  This is happening on the standard issue 4.15.0-33-generic kernel that
  shipped with my Ubuntu 18.04 (with updates), as well as with newer
  mainline kernels, such as the newest point versions of 4.17, 4.18 and
  4.19 RC2.

  This happens regardless of whether "blacklist i2c_i801" is commented
  out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
  whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
  Presence of TLP does not make it better, nor worse.

  It appears that non-NFC models are not affected. I know at least one
  Arch Linux user who has the exact same model, but without this issue.
  I'm using synaptics driver (no libinput installed), he uses libinput
  and doesn't have synaptics, if that information is of any use.
  Libinput does not seem to help.

  This forum thread also has more details from users who updated their
  BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
  Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
  Suspend-to/td-p/3998182/page/27

  Another related thread:
  https://bbs.archlinux.org/viewtopic.php?id=236367

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maciej 2651 F...m pulseaudio
   /dev/snd/controlC0:  maciej 2651 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Sep  8 13:45:43 2018
  HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET55W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KH006KPB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
 

[Kernel-packages] [Bug 1852282] Re: xenial/linux-azure: 4.15.0-1064.69 -proposed tracker

[Kleber Sacilotto de Souza]

** Summary changed:

- xenial/linux-azure:  -proposed tracker
+ xenial/linux-azure: 4.15.0-1064.69 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber 
Sacilotto de Souza (kleber-souza)

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

Title:
  xenial/linux-azure: 4.15.0-1064.69 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow certification-testing series:
  Invalid
Status in Kernel SRU Workflow prepare-package series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-security series:
  New
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:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in Kernel SRU Workflow verification-testing series:
  New
Status in linux-azure package in Ubuntu:
  Invalid
Status in linux-azure source package in Xenial:
  Confirmed

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 --
  kernel-stable-master-bug: 1852289
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
  phase: Ready for Packaging
  phase-changed: Thursday, 14. November 2019 09:12 UTC
  reason:
prepare-package: Pending -- version not specified
  trackers:
trusty/linux-azure: bug 1852281
xenial/linux-azure-edge: bug 1852280
xenial/linux-azure/azure-kernel: bug 1852279
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852282/+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

Re: [Kernel-packages] [Bug 1853130] Re: zfs-dkms-0.7.5-1ubuntu15 fail build kernel-hwe kernel 5.0.0-36-generic

[alberto fiaschi]

Ok, thanks.


*«L'immaginazione è più importante della conoscenza.» - Albert
Einstein.*


*Alberto M.Fiaschi*


*http://it.linkedin.com/pub/alberto-fiaschi
 *


Il giorno mar 19 nov 2019 alle ore 14:50 Colin Ian King <
1853...@bugs.launchpad.net> ha scritto:

> No problem at all. I'll close this bug if that's OK.
>
> ** Changed in: zfs-linux (Ubuntu)
>Status: Triaged => Won't Fix
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1853130
>
> Title:
>   zfs-dkms-0.7.5-1ubuntu15 fail build kernel-hwe kernel 5.0.0-36-generic
>
> Status in zfs-linux package in Ubuntu:
>   Won't Fix
>
> Bug description:
>   zfs-dkms- Fail build  with kernel 5.0.0-36-generic
>   cripts/Makefile.build:284: recipe for target
> '/var/lib/dkms/spl/0.7.5/build/module/spl/spl-condvar.o' failed
>make[5]: *** [/var/lib/dkms/spl/0.7.5/build/module/spl/spl-condvar.o]
> Error 1
>make[5]: *** Waiting for unfinished jobs
>In file included from
> /var/lib/dkms/spl/0.7.5/build/include/sys/kstat.h:31:0,
> from
> /var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.c:28:
>/var/lib/dkms/spl/0.7.5/build/include/sys/time.h: In function
> ‘gethrestime’:
>/var/lib/dkms/spl/0.7.5/build/include/sys/time.h:63:9: error: implicit
> declaration of function ‘current_kernel_time’; did you mean ‘current_time’?
> [-Werror=implicit-function-declaration]
>  *now = current_kernel_time();
> ^~~
> current_time
>/var/lib/dkms/spl/0.7.5/build/include/sys/time.h:63:7: error:
> incompatible types when assigning to type ‘timestruc_t {aka struct
> timespec}’ from type ‘int’
>  *now = current_kernel_time();
>   ^
>/var/lib/dkms/spl/0.7.5/build/include/sys/time.h: In function
> ‘gethrestime_sec’:
>/var/lib/dkms/spl/0.7.5/build/include/sys/time.h:70:5: error:
> incompatible types when assigning to type ‘struct timespec’ from type ‘int’
>  ts = current_kernel_time();
> ^
>  CC [M]  /var/lib/dkms/spl/0.7.5/build/module/splat/splat-linux.o
>cc1: some warnings being treated as errors
>scripts/Makefile.build:284: recipe for target
> '/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.o' failed
>make[5]: *** [/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.o]
> Error 1
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1853130/+subscriptions
>

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

Title:
  zfs-dkms-0.7.5-1ubuntu15 fail build kernel-hwe kernel 5.0.0-36-generic

Status in zfs-linux package in Ubuntu:
  Won't Fix

Bug description:
  zfs-dkms- Fail build  with kernel 5.0.0-36-generic 
  cripts/Makefile.build:284: recipe for target 
'/var/lib/dkms/spl/0.7.5/build/module/spl/spl-condvar.o' failed
   make[5]: *** [/var/lib/dkms/spl/0.7.5/build/module/spl/spl-condvar.o] Error 1
   make[5]: *** Waiting for unfinished jobs
   In file included from /var/lib/dkms/spl/0.7.5/build/include/sys/kstat.h:31:0,
from 
/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.c:28:
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h: In function ‘gethrestime’:
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h:63:9: error: implicit 
declaration of function ‘current_kernel_time’; did you mean ‘current_time’? 
[-Werror=implicit-function-declaration]
 *now = current_kernel_time();
^~~
current_time
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h:63:7: error: incompatible 
types when assigning to type ‘timestruc_t {aka struct timespec}’ from type ‘int’
 *now = current_kernel_time();
  ^
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h: In function 
‘gethrestime_sec’:
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h:70:5: error: incompatible 
types when assigning to type ‘struct timespec’ from type ‘int’
 ts = current_kernel_time();
^
 CC [M]  /var/lib/dkms/spl/0.7.5/build/module/splat/splat-linux.o
   cc1: some warnings being treated as errors
   scripts/Makefile.build:284: recipe for target 
'/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.o' failed
   make[5]: *** [/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.o] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1853130/+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 1852268] Re: bionic/linux-aws-fips: 4.15.0-2005.5 -proposed tracker

[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 --
  kernel-stable-master-bug: 1852270
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Packaging
  phase-changed: Tuesday, 19. November 2019 10:20 UTC
  reason:
-   prepare-package: Pending -- package not yet uploaded
-   prepare-package-lrm: Pending -- package not yet uploaded
-   prepare-package-meta: Pending -- package not yet uploaded
-   prepare-package-signed: Pending -- package not yet uploaded
+   prepare-package: Stalled -- package tag not yet published
+   prepare-package-lrm: Stalled -- package tag not yet published
+   prepare-package-meta: Stalled -- package tag not yet published
+   prepare-package-signed: Stalled -- package tag not yet published
+   promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
  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/1852268

Title:
  bionic/linux-aws-fips: 4.15.0-2005.5 -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 Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Committed
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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 Bionic:
  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 --
  kernel-stable-master-bug: 1852270
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Packaging
  phase-changed: Tuesday, 19. November 2019 10:20 UTC
  reason:
prepare-package: Stalled -- package tag not yet published
prepare-package-lrm: Stalled -- package tag not yet published
prepare-package-meta: Stalled -- package tag not yet published
prepare-package-signed: Stalled -- package tag not yet published
promote-to-proposed: Ongoing -- builds not complete in ppa 
lrm:depwait,main:building,meta:depwait,signed:depwait
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852268/+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 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140

[Hui Wang]

** Changed in: linux (Ubuntu)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: linux (Ubuntu)
   Importance: Undecided => High

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

Title:
  [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no
  longer works on Dell Venue 11 Pro 7140

Status in Linux:
  Confirmed
Status in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello!

  I noticed that since Linux 5.2rc2 audio playback no longer works on
  Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that
  happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel
  binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel-
  ppa/mainline/v5.2-rc2/

  To verify this assumption I tested two builds of Linux 5.3.1.
  1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from 
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/

  Audio playback doesn't work, dmesg:
  [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link 
System PCM: -517
  [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.480344] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14
  [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 
header 0x8700
  [   13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 
still running
  [   13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 
still running
  [   19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- 
ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff
  [   19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 
faile

  2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT.

  Audio playback works, dmesg:
  [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for 
intel/IntcPP01.bin failed with error -2
  [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image 
intel/IntcPP01.bin not available(-2)
  [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox 
readback FW info: type 01, - version: 00.00, build 77, source commit id: 
876ac6906f31a43b6772b23c7c983ce9dcb18a19
  [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops 
i915_audio_component_bind_ops [i915])
  [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System 
Pin mapping ok
  [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload0 Pin mapping ok
  [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Offload1 Pin mapping ok
  [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> 
Loopback Pin mapping ok
  [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> 
snd-soc-dummy-dai mapping ok
  [4.929629] input: broadwell-rt286 Headset as 
/devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  irina   818 F pulseaudio
   /dev/snd/controlC0:  irina   818 F pulseaudio
  CurrentDesktop: GNOME
  Date: Fri Oct  4 01:22:54 2019
  InstallationDate: Installed on 2019-02-12 (233 days 

[Kernel-packages] [Bug 1852268] Re: bionic/linux-aws-fips: 4.15.0-2005.5 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/prepare-package
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-lrm
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: In Progress => Fix Committed

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: In Progress => Fix Committed

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

Title:
  bionic/linux-aws-fips: 4.15.0-2005.5 -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 Committed
Status in Kernel SRU Workflow prepare-package-lrm series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Committed
Status in Kernel SRU Workflow prepare-package-signed series:
  Fix Committed
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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 Bionic:
  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 --
  kernel-stable-master-bug: 1852270
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Packaging
  phase-changed: Tuesday, 19. November 2019 10:20 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852268/+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 1349252] Re: crypt(3) lacks Blowfish support

[Thommie Rother]

Has there been any progress on this more than five year old topic?
The glibc of the long time supported 18.04.3 LTS still has no support for 
BLF-CRYPT. I saw that from debian-side blowfish is still not supported but some 
distros add it by themselves. Why not 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/1349252

Title:
  crypt(3) lacks Blowfish support

Status in glibc package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Invalid

Bug description:
  crypt(3) bundled with Ubuntu's GNU C Library supports MD5, DES, SHA256
  and SHA512 hashing methods, but lacks support for Blowfish (aka
  bcrypt).

  There is a patch available from Openwall:
  http://www.openwall.com/crypt/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1349252/+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 1852253] Re: disco/linux: 5.0.0-37.40 -proposed tracker

[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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 14. November 2019 18:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
-   bionic/linux-oem-osp1: bug 1852251, bug 1853116
+   bionic/linux-oem-osp1: bug 1853116
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
unknown/unknown: bug 1852245
  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/1852253

Title:
  disco/linux: 5.0.0-37.40 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Confirmed

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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 14. November 2019 18:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1853116
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
unknown/unknown: bug 1852245
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+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 1852723] Re: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2

[Ike Panhc]

For more information,

1) 628859e8621cb is part of large patchset landed in 4.16 kernel and 4.14.151 
stable release
2) 4.14.151 mainline build kernel is ok to bring up SMP CPUs (See #5, kernel 
oops on SMP initial)
3) 4.16 mainline build kernel is ok to bring up SMP CPUs

So, we can not report 4.14.151 and 4.16 has this issue. I am going to
check anything missing between 4.14 and 4.15

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

Title:
  [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  [Impact]
  4.15.0-71-generic can not boot on several arm64 machine e.g. ThunderX2, 
Kunpeng 920 and CN88xx.

  [Test Case]
  Boot kernel with earlycon. See if kernel oops while booting.

  [Regression Risk]
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852723/+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 1853130] Re: zfs-dkms-0.7.5-1ubuntu15 fail build kernel-hwe kernel 5.0.0-36-generic

[Colin Ian King]

No problem at all. I'll close this bug if that's OK.

** Changed in: zfs-linux (Ubuntu)
   Status: Triaged => Won't Fix

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

Title:
  zfs-dkms-0.7.5-1ubuntu15 fail build kernel-hwe kernel 5.0.0-36-generic

Status in zfs-linux package in Ubuntu:
  Won't Fix

Bug description:
  zfs-dkms- Fail build  with kernel 5.0.0-36-generic 
  cripts/Makefile.build:284: recipe for target 
'/var/lib/dkms/spl/0.7.5/build/module/spl/spl-condvar.o' failed
   make[5]: *** [/var/lib/dkms/spl/0.7.5/build/module/spl/spl-condvar.o] Error 1
   make[5]: *** Waiting for unfinished jobs
   In file included from /var/lib/dkms/spl/0.7.5/build/include/sys/kstat.h:31:0,
from 
/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.c:28:
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h: In function ‘gethrestime’:
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h:63:9: error: implicit 
declaration of function ‘current_kernel_time’; did you mean ‘current_time’? 
[-Werror=implicit-function-declaration]
 *now = current_kernel_time();
^~~
current_time
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h:63:7: error: incompatible 
types when assigning to type ‘timestruc_t {aka struct timespec}’ from type ‘int’
 *now = current_kernel_time();
  ^
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h: In function 
‘gethrestime_sec’:
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h:70:5: error: incompatible 
types when assigning to type ‘struct timespec’ from type ‘int’
 ts = current_kernel_time();
^
 CC [M]  /var/lib/dkms/spl/0.7.5/build/module/splat/splat-linux.o
   cc1: some warnings being treated as errors
   scripts/Makefile.build:284: recipe for target 
'/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.o' failed
   make[5]: *** [/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.o] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1853130/+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 1847256] Re: Support Raspberry Pi 4

[Juerg Haefliger]

** Summary changed:

- Support Raspberry PI 4
+ Support Raspberry Pi 4

** Description changed:

- Add support for the Raspberry PI 4 to Bionic 4.15.
+ Add support for the Raspberry Pi 4 to Bionic 4.15.

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

Title:
  Support Raspberry Pi 4

Status in linux-raspi2 package in Ubuntu:
  New
Status in linux-raspi2 source package in Bionic:
  Confirmed

Bug description:
  Add support for the Raspberry Pi 4 to Bionic 4.15.

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

Re: [Kernel-packages] [Bug 1853130] Re: zfs-dkms-0.7.5-1ubuntu15 fail build kernel-hwe kernel 5.0.0-36-generic

[alberto fiaschi]

sorry for the mistake
thanks


*«L'immaginazione è più importante della conoscenza.» - Albert
Einstein.*


*Alberto M.Fiaschi*


*http://it.linkedin.com/pub/alberto-fiaschi
 *


Il giorno mar 19 nov 2019 alle ore 13:30 Colin Ian King <
1853...@bugs.launchpad.net> ha scritto:

> The hwe (and bionic) kernels come with zfs and spl modules already
> provided, so there is no need for zfs-dkms and spl-dkms, e.g.
>
> cking@bionic-amd64:~$ uname -a
> Linux bionic-amd64 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12
> 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
> cking@bionic-amd64:~$ lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description:Ubuntu 18.04.3 LTS
> Release:18.04
> Codename:   bionic
> cking@bionic-amd64:~$ dpkg -l | grep zfs-dkms
> cking@bionic-amd64:~$ dmesg | grep ZFS
> [   16.209504] ZFS: Loaded module v0.7.12-1ubuntu5, ZFS pool version 5000,
> ZFS filesystem version 5
> cking@bionic-amd64:~$ lsmod | grep zfs
> zfs  3035136  8
> zunicode  331776  1 zfs
> zavl   16384  1 zfs
> icp   258048  1 zfs
> zcommon65536  1 zfs
> znvpair77824  2 zfs,zcommon
> spl   102400  4 zfs,icp,znvpair,zcommon
>
> so just remove zfs-dkms and you can still use zfs on the HWE 5.0.x
> kernel on Bionic.
>
> ** Changed in: zfs-linux (Ubuntu)
>Importance: Undecided => Wishlist
>
> ** Changed in: zfs-linux (Ubuntu)
>  Assignee: (unassigned) => Colin Ian King (colin-king)
>
> ** Changed in: zfs-linux (Ubuntu)
>Status: New => Triaged
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1853130
>
> Title:
>   zfs-dkms-0.7.5-1ubuntu15 fail build kernel-hwe kernel 5.0.0-36-generic
>
> Status in zfs-linux package in Ubuntu:
>   Triaged
>
> Bug description:
>   zfs-dkms- Fail build  with kernel 5.0.0-36-generic
>   cripts/Makefile.build:284: recipe for target
> '/var/lib/dkms/spl/0.7.5/build/module/spl/spl-condvar.o' failed
>make[5]: *** [/var/lib/dkms/spl/0.7.5/build/module/spl/spl-condvar.o]
> Error 1
>make[5]: *** Waiting for unfinished jobs
>In file included from
> /var/lib/dkms/spl/0.7.5/build/include/sys/kstat.h:31:0,
> from
> /var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.c:28:
>/var/lib/dkms/spl/0.7.5/build/include/sys/time.h: In function
> ‘gethrestime’:
>/var/lib/dkms/spl/0.7.5/build/include/sys/time.h:63:9: error: implicit
> declaration of function ‘current_kernel_time’; did you mean ‘current_time’?
> [-Werror=implicit-function-declaration]
>  *now = current_kernel_time();
> ^~~
> current_time
>/var/lib/dkms/spl/0.7.5/build/include/sys/time.h:63:7: error:
> incompatible types when assigning to type ‘timestruc_t {aka struct
> timespec}’ from type ‘int’
>  *now = current_kernel_time();
>   ^
>/var/lib/dkms/spl/0.7.5/build/include/sys/time.h: In function
> ‘gethrestime_sec’:
>/var/lib/dkms/spl/0.7.5/build/include/sys/time.h:70:5: error:
> incompatible types when assigning to type ‘struct timespec’ from type ‘int’
>  ts = current_kernel_time();
> ^
>  CC [M]  /var/lib/dkms/spl/0.7.5/build/module/splat/splat-linux.o
>cc1: some warnings being treated as errors
>scripts/Makefile.build:284: recipe for target
> '/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.o' failed
>make[5]: *** [/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.o]
> Error 1
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1853130/+subscriptions
>

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

Title:
  zfs-dkms-0.7.5-1ubuntu15 fail build kernel-hwe kernel 5.0.0-36-generic

Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  zfs-dkms- Fail build  with kernel 5.0.0-36-generic 
  cripts/Makefile.build:284: recipe for target 
'/var/lib/dkms/spl/0.7.5/build/module/spl/spl-condvar.o' failed
   make[5]: *** [/var/lib/dkms/spl/0.7.5/build/module/spl/spl-condvar.o] Error 1
   make[5]: *** Waiting for unfinished jobs
   In file included from /var/lib/dkms/spl/0.7.5/build/include/sys/kstat.h:31:0,
from 
/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.c:28:
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h: In function ‘gethrestime’:
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h:63:9: error: implicit 
declaration of function ‘current_kernel_time’; did you mean ‘current_time’? 
[-Werror=implicit-function-declaration]
 *now = current_kernel_time();
^~~
current_time
   

[Kernel-packages] [Bug 1848978] Re: CML: perf enabling for core

[You-Sheng Yang]

There are still something already committed to mainline but missed on
the list. I have to include also IceLake support for CometLake backports
to D/OEM-OSP1-B, but `perf list` doesn't give PC8-10 for IceLake
platforms. However, by installing v5.4-generic kernel from
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable,
they're back.

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

Title:
  CML: perf enabling for core

Status in intel:
  Fix Committed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in linux-oem-osp1 source package in Bionic:
  In Progress
Status in linux source package in Disco:
  New
Status in linux-oem-osp1 source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  New
Status in linux-oem-osp1 source package in Eoan:
  Confirmed
Status in linux source package in Focal:
  Confirmed
Status in linux-oem-osp1 source package in Focal:
  Confirmed

Bug description:
  Description:

  CML perf enabling for core

  v5.4-rc3
  1ffa6c04dae39776a3c222bdf88051e394386c01 
9066288b2aab1804dc1eebec6ff88474363b89cb 
9674b1cc0f94c34f76e58c102623a866836f269e

  
  Target Kernel: 5.4
  Target Release: 20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1848978/+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 1852723] Re: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2

[Ike Panhc]

** Description changed:

- Tested on bionic GA 4.15.0-70-generic 4.15.0-71-generic
- and also HWE 5.0.0-37-generic 5.3.0-23-generic
+ [Impact]
+ 4.15.0-71-generic can not boot on several arm64 machine e.g. ThunderX2, 
Kunpeng 920 and CN88xx.
  
- Only 4.15.0-71-generic can not boot on Cavium ThunderX2
+ [Test Case]
+ Boot kernel with earlycon. See if kernel oops while booting.
  
- On console nothing after EFI messages.
- 
- Loading Linux 4.15.0-71-generic ...
- Loading initial ramdisk ...
- EFI stub: Booting Linux Kernel...
- EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
- EFI stub: Using DTB from configuration table
- EFI stub: Exiting boot services and installing virtual address map...
+ [Regression Risk]
+ TBD

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

Title:
  [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  [Impact]
  4.15.0-71-generic can not boot on several arm64 machine e.g. ThunderX2, 
Kunpeng 920 and CN88xx.

  [Test Case]
  Boot kernel with earlycon. See if kernel oops while booting.

  [Regression Risk]
  TBD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852723/+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 1853130] Re: zfs-dkms-0.7.5-1ubuntu15 fail build kernel-hwe kernel 5.0.0-36-generic

[Colin Ian King]

The hwe (and bionic) kernels come with zfs and spl modules already
provided, so there is no need for zfs-dkms and spl-dkms, e.g.

cking@bionic-amd64:~$ uname -a
Linux bionic-amd64 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
cking@bionic-amd64:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename:   bionic
cking@bionic-amd64:~$ dpkg -l | grep zfs-dkms
cking@bionic-amd64:~$ dmesg | grep ZFS
[   16.209504] ZFS: Loaded module v0.7.12-1ubuntu5, ZFS pool version 5000, ZFS 
filesystem version 5
cking@bionic-amd64:~$ lsmod | grep zfs
zfs  3035136  8
zunicode  331776  1 zfs
zavl   16384  1 zfs
icp   258048  1 zfs
zcommon65536  1 zfs
znvpair77824  2 zfs,zcommon
spl   102400  4 zfs,icp,znvpair,zcommon

so just remove zfs-dkms and you can still use zfs on the HWE 5.0.x
kernel on Bionic.

** Changed in: zfs-linux (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: zfs-linux (Ubuntu)
 Assignee: (unassigned) => Colin Ian King (colin-king)

** Changed in: zfs-linux (Ubuntu)
   Status: New => Triaged

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

Title:
  zfs-dkms-0.7.5-1ubuntu15 fail build kernel-hwe kernel 5.0.0-36-generic

Status in zfs-linux package in Ubuntu:
  Triaged

Bug description:
  zfs-dkms- Fail build  with kernel 5.0.0-36-generic 
  cripts/Makefile.build:284: recipe for target 
'/var/lib/dkms/spl/0.7.5/build/module/spl/spl-condvar.o' failed
   make[5]: *** [/var/lib/dkms/spl/0.7.5/build/module/spl/spl-condvar.o] Error 1
   make[5]: *** Waiting for unfinished jobs
   In file included from /var/lib/dkms/spl/0.7.5/build/include/sys/kstat.h:31:0,
from 
/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.c:28:
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h: In function ‘gethrestime’:
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h:63:9: error: implicit 
declaration of function ‘current_kernel_time’; did you mean ‘current_time’? 
[-Werror=implicit-function-declaration]
 *now = current_kernel_time();
^~~
current_time
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h:63:7: error: incompatible 
types when assigning to type ‘timestruc_t {aka struct timespec}’ from type ‘int’
 *now = current_kernel_time();
  ^
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h: In function 
‘gethrestime_sec’:
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h:70:5: error: incompatible 
types when assigning to type ‘struct timespec’ from type ‘int’
 ts = current_kernel_time();
^
 CC [M]  /var/lib/dkms/spl/0.7.5/build/module/splat/splat-linux.o
   cc1: some warnings being treated as errors
   scripts/Makefile.build:284: recipe for target 
'/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.o' failed
   make[5]: *** [/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.o] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1853130/+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 1846016] Re: Intel Wireless AC 3168 on Eoan complaints FW error in SYNC CMD GEO_TX_POWER_LIMIT

[brett hassall]

verified eoan 5.3.0-24.26 against my original bug (1846264) as well

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

Title:
  Intel Wireless AC 3168 on Eoan complaints FW error in SYNC CMD
  GEO_TX_POWER_LIMIT

Status in Linux:
  Fix Released
Status in linux package in Ubuntu:
  In Progress
Status in linux-oem package in Ubuntu:
  Confirmed
Status in linux-oem-osp1 package in Ubuntu:
  Confirmed
Status in linux source package in Bionic:
  Fix Committed
Status in linux-oem source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in linux source package in Disco:
  Fix Committed
Status in linux-oem source package in Disco:
  Confirmed
Status in linux-oem-osp1 source package in Disco:
  Confirmed
Status in linux source package in Eoan:
  Fix Committed
Status in linux-oem source package in Eoan:
  Confirmed
Status in linux-oem-osp1 source package in Eoan:
  Confirmed

Bug description:
  I have ubuntu 19.10 Eoan Ermine development version. Cannot boot since
  yesterday.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: linux-firmware 1.182
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  Date: Mon Sep 30 20:57:08 2019
  Dependencies:

  InstallationDate: Installed on 2019-07-23 (68 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (2 days ago)

  --
  Also found on Ubuntu-certified HP EliteDesk 800 G3 DM.

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1846016/+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 1853130] [NEW] zfs-dkms-0.7.5-1ubuntu15 fail build kernel-hwe kernel 5.0.0-36-generic

[alberto fiaschi]

Public bug reported:

zfs-dkms- Fail build  with kernel 5.0.0-36-generic 
cripts/Makefile.build:284: recipe for target 
'/var/lib/dkms/spl/0.7.5/build/module/spl/spl-condvar.o' failed
 make[5]: *** [/var/lib/dkms/spl/0.7.5/build/module/spl/spl-condvar.o] Error 1
 make[5]: *** Waiting for unfinished jobs
 In file included from /var/lib/dkms/spl/0.7.5/build/include/sys/kstat.h:31:0,
  from /var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.c:28:
 /var/lib/dkms/spl/0.7.5/build/include/sys/time.h: In function ‘gethrestime’:
 /var/lib/dkms/spl/0.7.5/build/include/sys/time.h:63:9: error: implicit 
declaration of function ‘current_kernel_time’; did you mean ‘current_time’? 
[-Werror=implicit-function-declaration]
   *now = current_kernel_time();
  ^~~
  current_time
 /var/lib/dkms/spl/0.7.5/build/include/sys/time.h:63:7: error: incompatible 
types when assigning to type ‘timestruc_t {aka struct timespec}’ from type ‘int’
   *now = current_kernel_time();
^
 /var/lib/dkms/spl/0.7.5/build/include/sys/time.h: In function 
‘gethrestime_sec’:
 /var/lib/dkms/spl/0.7.5/build/include/sys/time.h:70:5: error: incompatible 
types when assigning to type ‘struct timespec’ from type ‘int’
   ts = current_kernel_time();
  ^
   CC [M]  /var/lib/dkms/spl/0.7.5/build/module/splat/splat-linux.o
 cc1: some warnings being treated as errors
 scripts/Makefile.build:284: recipe for target 
'/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.o' failed
 make[5]: *** [/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.o] Error 1

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

** Attachment added: "spl-dkms.0.crash"
   
https://bugs.launchpad.net/bugs/1853130/+attachment/5306466/+files/spl-dkms.0.crash

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

Title:
  zfs-dkms-0.7.5-1ubuntu15 fail build kernel-hwe kernel 5.0.0-36-generic

Status in zfs-linux package in Ubuntu:
  New

Bug description:
  zfs-dkms- Fail build  with kernel 5.0.0-36-generic 
  cripts/Makefile.build:284: recipe for target 
'/var/lib/dkms/spl/0.7.5/build/module/spl/spl-condvar.o' failed
   make[5]: *** [/var/lib/dkms/spl/0.7.5/build/module/spl/spl-condvar.o] Error 1
   make[5]: *** Waiting for unfinished jobs
   In file included from /var/lib/dkms/spl/0.7.5/build/include/sys/kstat.h:31:0,
from 
/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.c:28:
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h: In function ‘gethrestime’:
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h:63:9: error: implicit 
declaration of function ‘current_kernel_time’; did you mean ‘current_time’? 
[-Werror=implicit-function-declaration]
 *now = current_kernel_time();
^~~
current_time
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h:63:7: error: incompatible 
types when assigning to type ‘timestruc_t {aka struct timespec}’ from type ‘int’
 *now = current_kernel_time();
  ^
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h: In function 
‘gethrestime_sec’:
   /var/lib/dkms/spl/0.7.5/build/include/sys/time.h:70:5: error: incompatible 
types when assigning to type ‘struct timespec’ from type ‘int’
 ts = current_kernel_time();
^
 CC [M]  /var/lib/dkms/spl/0.7.5/build/module/splat/splat-linux.o
   cc1: some warnings being treated as errors
   scripts/Makefile.build:284: recipe for target 
'/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.o' failed
   make[5]: *** [/var/lib/dkms/spl/0.7.5/build/module/spl/spl-kstat.o] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1853130/+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 1852586] Re: Boot hangs after "Loading initial ramdisk ..."

[Stefan Bader]

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Eoan)
   Importance: Undecided => High

** Changed in: linux (Ubuntu Eoan)
   Status: New => 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/1852586

Title:
  Boot hangs after "Loading initial ramdisk ..."

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Confirmed

Bug description:
  Kernel 5.3.0.-23-generic and
  Kernel 5.3.0.-22-generic 

  don't boot, I get the "Loading initial ramdisk ..." on purple background, 
nothing happens, Notebook need to get shutoff to resume
  Kernels:
  5.3.0-19 and
  5.3.0-18 
  do work

  It's a Lenovo L580 Running Ubuntu 19.10

  
  output of version signature:
  Ubuntu 5.3.0-19.20-generic 5.3.1

  output of lscpi:
  00:00.0 Host bridge [0600]: Intel Corporation Device [8086:3e34] (rev 0c)
Subsystem: Lenovo Device [17aa:5075]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 
(Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:5075]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
 AtomicOpsCtl: ReqEn-
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 14
PASIDCtl: Enable- Exec- Priv-
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] Page Request Interface (PRI)
PRICtl: Enable- Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 8000, Page Request Allocation: 

Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0c)
Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor 
Thermal Subsystem [17aa:5075]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / 
E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [8086:1911]
Subsystem: Lenovo Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core 
Processor Gaussian Mixture Model [17aa:5075]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- 
SERR- 
Kernel driver in use: xhci_hcd

  00:14.2 RAM memory [0500]: Intel Corporation Cannon Point-LP Shared SRAM 
[8086:9def] (rev 30)
Subsystem: Lenovo Cannon Point-LP Shared SRAM [17aa:5075]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci

  00:15.2 Serial bus controller [0c80]: Intel 

[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

[Jeroen Roumen]

@thorstenr-42: Also have a nfc model so still facing the same dead touchpad 
issues.
I've never built a custom kernel before, just loaded a kernel module for a wifi 
nic that didn't have drivers in the kernel. How do you go about building and 
running this?

Also I'm wondering what would be necessary, or what I can do, to finally
get these patches 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/1791427

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

Status in linux package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 18.04.1

  Terminology in case we use different terms:
  touchpad - just the rectangular touch-sensitive surface below the keyboard 
(xinput lists it as Synaptics TM3288-011)
  trackpoint - the red thingy built into the keyboard + 3 physical buttons 
below the keyboard (trackpoint and buttons are integrated together; listed in 
xinput as TPPS/2 Elan TrackPoint)

  On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which
  enables proper S3 deep sleep state - users no longer have to patch
  DSDT tables to get it. It can be enabled in the BIOS settings. In X1
  carbon 6th generation models that have NFC, when laptop wakes from
  suspend by opening the lid, in most cases both touchpad and trackpoint
  stop working completely. They are also no longer listed when running
  xinput command. Sometimes just one of them stops working, usually the
  trackpoint. In some rare cases it is possible to bring them back by
  using these commands:

  echo -n none > /sys/devices/platform/i8042/serio1/drvctl
  echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl
  rmmod psmouse
  modprobe psmouse

  These worked properly when waking up from S2Idle sleep state (had
  these in a script that runs after waking the machine from suspend),
  but with S3 deep sleep these rarely work and the only way to bring
  back touchpad and/or trackpoint is turning off the machine and turning
  it on (restart does not help).

  I could not find any pattern that would show when the input devices
  stop working or start working again using the commands mentioned
  above. It's completely random from my perspective.

  This is happening on the standard issue 4.15.0-33-generic kernel that
  shipped with my Ubuntu 18.04 (with updates), as well as with newer
  mainline kernels, such as the newest point versions of 4.17, 4.18 and
  4.19 RC2.

  This happens regardless of whether "blacklist i2c_i801" is commented
  out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of
  whether "psmouse.synaptics_intertouch=1" is passed as grub parameter.
  Presence of TLP does not make it better, nor worse.

  It appears that non-NFC models are not affected. I know at least one
  Arch Linux user who has the exact same model, but without this issue.
  I'm using synaptics driver (no libinput installed), he uses libinput
  and doesn't have synaptics, if that information is of any use.
  Libinput does not seem to help.

  This forum thread also has more details from users who updated their
  BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux-
  Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka-
  Suspend-to/td-p/3998182/page/27

  Another related thread:
  https://bbs.archlinux.org/viewtopic.php?id=236367

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-33-generic 4.15.0-33.36
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   maciej 2651 F...m pulseaudio
   /dev/snd/controlC0:  maciej 2651 F pulseaudio
  CurrentDesktop: i3
  Date: Sat Sep  8 13:45:43 2018
  HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e
  InstallationDate: Installed on 2018-07-21 (49 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:56b2 IMC Networks 
   Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless 
optical mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20KH006KPB
  ProcFB:
   0 EFI VGA
   1 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-33-generic N/A
   linux-backports-modules-4.15.0-33-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 

[Kernel-packages] [Bug 1852521] Re: Unable to boot "Gave up waiting for root device" for kernel version 5.3.0-19 & 5.3.0-22

[Stefan Bader]

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: New

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

** Changed in: linux (Ubuntu Eoan)
   Importance: Undecided => High

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

Title:
  Unable to boot "Gave up waiting for root device" for kernel version
  5.3.0-19 & 5.3.0-22

Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Eoan:
  Confirmed

Bug description:
  Ubuntu cannot boot if using kernel version 5.3.0-19 & 5.3.0-22.

  However, kernel version 5.3.0-18 works fine.

  The root disk is encrypted. When booting with 5.3.0-18, a passsphrase
  input field is displayed during boot. However, such an input field
  does not appear in 5.3.0-19 & 5.3.0-22, which eventually leads to time
  out and the boot failed.


  Additional information: When I execute `sudo update-initramfs -c -k
  5.3.0-22-generic`

  It shows the following:

  
  > update-initramfs: Generating /boot/initrd.img-5.3.0-22-generic
  > cryptsetup: WARNING: Skipping root target nvme0n1p5_crypt: uses a key file

  
  I feel that the message about the root partition (nvme0n1p5_crypt) using a 
key file might suggest something wrong? Because actually I didn't use a key 
file for the root partition, instead only a passphrase is used.


  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
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  shaform2068 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 13 21:41:07 2019
  InstallationDate: Installed on 2019-11-09 (5 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: LENOVO 20LD0017US
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-18-generic 
root=UUID=6709141d-5e30-44ef-a676-c3bb559cd47c ro 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.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/29/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N25ET50W (1.36 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20LD0017US
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 31
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN25ET50W(1.36):bd07/29/2019:svnLENOVO:pn20LD0017US:pvrThinkPadX1Yoga3rd:rvnLENOVO:rn20LD0017US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone:
  dmi.product.family: ThinkPad X1 Yoga 3rd
  dmi.product.name: 20LD0017US
  dmi.product.sku: LENOVO_MT_20LD_BU_Think_FM_ThinkPad X1 Yoga 3rd
  dmi.product.version: ThinkPad X1 Yoga 3rd
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852521/+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 1852723] Re: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2

[Stefan Bader]

Just to reason lowering the priority: I consider critical those issues
which cause loss of data. Not being able to boot is "just" loss of
functionality and so high.

** Changed in: linux (Ubuntu Bionic)
   Importance: Critical => High

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

Title:
  [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Tested on bionic GA 4.15.0-70-generic 4.15.0-71-generic
  and also HWE 5.0.0-37-generic 5.3.0-23-generic

  Only 4.15.0-71-generic can not boot on Cavium ThunderX2

  On console nothing after EFI messages.

  Loading Linux 4.15.0-71-generic ...
  Loading initial ramdisk ...
  EFI stub: Booting Linux Kernel...
  EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
  EFI stub: Using DTB from configuration table
  EFI stub: Exiting boot services and installing virtual address map...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852723/+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 1852976] Re: zram01 / zram02 / zram03 in kernel_misc from ubuntu_ltp failed on D-Oracle

[Po-Hsu Lin]

https://kernel.ubuntu.com/git/ubuntu/autotest-client-
tests.git/commit/?id=135585f1ad75dcea0e5bab344a7c60fffbb15dfb

** Changed in: ubuntu-kernel-tests
   Status: In Progress => Fix Released

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

** Changed in: linux-signed-oracle (Ubuntu Disco)
   Status: New => Invalid

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

Title:
  zram01 / zram02 / zram03 in kernel_misc from ubuntu_ltp failed on
  D-Oracle

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-signed-oracle package in Ubuntu:
  Invalid
Status in linux-signed-oracle source package in Disco:
  Invalid

Bug description:
  It looks like the failures in zram01 are causing zram02 and zram03 to
  fail as well.

  Seems that this is broken since commit 7cfac804 (zram: Rewrite shell
  tests into new API)

   tag=zram01 stime=1573887406 dur=300 exit=signaled stat=9 core=no cu=23757 
cs=7590
   startup='Sat Nov 16 06:56:46 2019'
   zram01 1 TINFO: timeout per run is 0h 5m 0s
   zram01 1 TINFO: create '4' zram device(s)
   zram01 1 TPASS: test succeeded
   zram01 1 TCONF: The device attribute max_comp_streams was introduced in 
kernel 3.15 and deprecated in 4.7
   zram01 2 TINFO: test that we can set compression algorithm
   zram01 2 TINFO: supported algs: [lzo] lz4 lz4hc 842 zstd
   zram01 2 TINFO: /sys/block/zram0/comp_algorithm = 'lzo' (1/4)
   zram01 2 TINFO: /sys/block/zram1/comp_algorithm = 'lzo' (2/4)
   zram01 2 TINFO: /sys/block/zram2/comp_algorithm = 'lzo' (3/4)
   zram01 2 TINFO: /sys/block/zram3/comp_algorithm = 'lzo' (4/4)
   zram01 2 TPASS: test succeeded
   zram01 3 TINFO: set disk size to zram device(s)
   zram01 3 TINFO: /sys/block/zram0/disksize = '26214400' (1/4)
   zram01 3 TINFO: /sys/block/zram1/disksize = '26214400' (2/4)
   zram01 3 TINFO: /sys/block/zram2/disksize = '26214400' (3/4)
   zram01 3 TINFO: /sys/block/zram3/disksize = '402653184' (4/4)
   zram01 3 TPASS: test succeeded
   zram01 4 TINFO: set memory limit to zram device(s)
   zram01 4 TINFO: /sys/block/zram0/mem_limit = '25M' (1/4)
   zram01 4 TINFO: /sys/block/zram1/mem_limit = '25M' (2/4)
   zram01 4 TINFO: /sys/block/zram2/mem_limit = '25M' (3/4)
   zram01 4 TINFO: /sys/block/zram3/mem_limit = '384M' (4/4)
   zram01 4 TPASS: test succeeded
   zram01 5 TINFO: make ext3 filesystem on /dev/zram0
   zram01 5 TINFO: make ext4 filesystem on /dev/zram1
   zram01 5 TINFO: make xfs filesystem on /dev/zram2
   zram01 5 TINFO: make btrfs filesystem on /dev/zram3
   zram01 5 TPASS: zram_makefs succeeded
   zram01 6 TINFO: mount /dev/zram0
   zram01 6 TINFO: mount /dev/zram1
   zram01 6 TINFO: mount /dev/zram2
   zram01 6 TINFO: mount /dev/zram3
   zram01 6 TPASS: mount of zram device(s) succeeded
   zram01 7 TINFO: filling zram0 (it can take long time)
   zram01 7 TPASS: zram0 was filled with '20628' KB
   zram01 7 TPASS: compression ratio: 732.90:1
   zram01 7 TINFO: filling zram1 (it can take long time)
   zram01 7 TPASS: zram1 was filled with '20140' KB
   zram01 7 TPASS: compression ratio: 5151.97:1
   zram01 7 TINFO: filling zram2 (it can take long time)
   zram01 7 TPASS: zram2 was filled with '17756' KB
   zram01 7 TPASS: compression ratio: 285.26:1
   zram01 7 TINFO: filling zram3 (it can take long time)
   zram01 1 TBROK: test killed, timeout! If you are running on slow machine, 
try exporting LTP_TIMEOUT_MUL > 1

   tag=zram02 stime=1573887712 dur=0 exit=exited stat=1 core=no cu=2 cs=0
   startup='Sat Nov 16 07:01:52 2019'
   zram02 1 TINFO: timeout per run is 0h 5m 0s
   zram02 1 TINFO: create '1' zram device(s)
   zram02 1 TFAIL: unexpected num of devices: 4
   /opt/ltp/testcases/bin/zram02.sh: 27: echo: echo: I/O error
   zram02 1 TINFO: AppArmor enabled, this may affect test results
   zram02 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root)
   zram02 1 TINFO: loaded AppArmor profiles: none

   Summary:
   passed 0
   failed 1
   skipped 0
   warnings 0

   tag=zram03 stime=1573887718 dur=0 exit=exited stat=2 core=no cu=0 cs=0
   startup='Sat Nov 16 07:01:58 2019'
   zram03 0 TINFO : create a zram device with 536870912 bytes in size.
   zram03 1 TBROK : safe_file_ops.c:301: Failed to close FILE 
'/sys/block/zram0/disksize' at zram03.c:87: errno=EBUSY(16): Device or resource 
busy
   zram03 2 TBROK : safe_file_ops.c:301: Remaining cases broken

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1005-oracle 5.0.0-1005.9
  ProcVersionSignature: User Name 5.0.0-1005.9-oracle 5.0.21
  Uname: Linux 5.0.0-1005-oracle x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Mon Nov 18 07:50:37 2019
  SourcePackage: linux-signed-oracle
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1852976] Re: zram01 / zram02 / zram03 in kernel_misc from ubuntu_ltp failed on D-Oracle

[Po-Hsu Lin]

Tested on Oracle (Disco) / AWS (Eoan)

LTP_TIMEOUT_MUL=3 works, I will apply the patch for this.

** Changed in: ubuntu-kernel-tests
   Status: New => In Progress

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

Title:
  zram01 / zram02 / zram03 in kernel_misc from ubuntu_ltp failed on
  D-Oracle

Status in ubuntu-kernel-tests:
  Fix Released
Status in linux-signed-oracle package in Ubuntu:
  Invalid
Status in linux-signed-oracle source package in Disco:
  Invalid

Bug description:
  It looks like the failures in zram01 are causing zram02 and zram03 to
  fail as well.

  Seems that this is broken since commit 7cfac804 (zram: Rewrite shell
  tests into new API)

   tag=zram01 stime=1573887406 dur=300 exit=signaled stat=9 core=no cu=23757 
cs=7590
   startup='Sat Nov 16 06:56:46 2019'
   zram01 1 TINFO: timeout per run is 0h 5m 0s
   zram01 1 TINFO: create '4' zram device(s)
   zram01 1 TPASS: test succeeded
   zram01 1 TCONF: The device attribute max_comp_streams was introduced in 
kernel 3.15 and deprecated in 4.7
   zram01 2 TINFO: test that we can set compression algorithm
   zram01 2 TINFO: supported algs: [lzo] lz4 lz4hc 842 zstd
   zram01 2 TINFO: /sys/block/zram0/comp_algorithm = 'lzo' (1/4)
   zram01 2 TINFO: /sys/block/zram1/comp_algorithm = 'lzo' (2/4)
   zram01 2 TINFO: /sys/block/zram2/comp_algorithm = 'lzo' (3/4)
   zram01 2 TINFO: /sys/block/zram3/comp_algorithm = 'lzo' (4/4)
   zram01 2 TPASS: test succeeded
   zram01 3 TINFO: set disk size to zram device(s)
   zram01 3 TINFO: /sys/block/zram0/disksize = '26214400' (1/4)
   zram01 3 TINFO: /sys/block/zram1/disksize = '26214400' (2/4)
   zram01 3 TINFO: /sys/block/zram2/disksize = '26214400' (3/4)
   zram01 3 TINFO: /sys/block/zram3/disksize = '402653184' (4/4)
   zram01 3 TPASS: test succeeded
   zram01 4 TINFO: set memory limit to zram device(s)
   zram01 4 TINFO: /sys/block/zram0/mem_limit = '25M' (1/4)
   zram01 4 TINFO: /sys/block/zram1/mem_limit = '25M' (2/4)
   zram01 4 TINFO: /sys/block/zram2/mem_limit = '25M' (3/4)
   zram01 4 TINFO: /sys/block/zram3/mem_limit = '384M' (4/4)
   zram01 4 TPASS: test succeeded
   zram01 5 TINFO: make ext3 filesystem on /dev/zram0
   zram01 5 TINFO: make ext4 filesystem on /dev/zram1
   zram01 5 TINFO: make xfs filesystem on /dev/zram2
   zram01 5 TINFO: make btrfs filesystem on /dev/zram3
   zram01 5 TPASS: zram_makefs succeeded
   zram01 6 TINFO: mount /dev/zram0
   zram01 6 TINFO: mount /dev/zram1
   zram01 6 TINFO: mount /dev/zram2
   zram01 6 TINFO: mount /dev/zram3
   zram01 6 TPASS: mount of zram device(s) succeeded
   zram01 7 TINFO: filling zram0 (it can take long time)
   zram01 7 TPASS: zram0 was filled with '20628' KB
   zram01 7 TPASS: compression ratio: 732.90:1
   zram01 7 TINFO: filling zram1 (it can take long time)
   zram01 7 TPASS: zram1 was filled with '20140' KB
   zram01 7 TPASS: compression ratio: 5151.97:1
   zram01 7 TINFO: filling zram2 (it can take long time)
   zram01 7 TPASS: zram2 was filled with '17756' KB
   zram01 7 TPASS: compression ratio: 285.26:1
   zram01 7 TINFO: filling zram3 (it can take long time)
   zram01 1 TBROK: test killed, timeout! If you are running on slow machine, 
try exporting LTP_TIMEOUT_MUL > 1

   tag=zram02 stime=1573887712 dur=0 exit=exited stat=1 core=no cu=2 cs=0
   startup='Sat Nov 16 07:01:52 2019'
   zram02 1 TINFO: timeout per run is 0h 5m 0s
   zram02 1 TINFO: create '1' zram device(s)
   zram02 1 TFAIL: unexpected num of devices: 4
   /opt/ltp/testcases/bin/zram02.sh: 27: echo: echo: I/O error
   zram02 1 TINFO: AppArmor enabled, this may affect test results
   zram02 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root)
   zram02 1 TINFO: loaded AppArmor profiles: none

   Summary:
   passed 0
   failed 1
   skipped 0
   warnings 0

   tag=zram03 stime=1573887718 dur=0 exit=exited stat=2 core=no cu=0 cs=0
   startup='Sat Nov 16 07:01:58 2019'
   zram03 0 TINFO : create a zram device with 536870912 bytes in size.
   zram03 1 TBROK : safe_file_ops.c:301: Failed to close FILE 
'/sys/block/zram0/disksize' at zram03.c:87: errno=EBUSY(16): Device or resource 
busy
   zram03 2 TBROK : safe_file_ops.c:301: Remaining cases broken

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1005-oracle 5.0.0-1005.9
  ProcVersionSignature: User Name 5.0.0-1005.9-oracle 5.0.21
  Uname: Linux 5.0.0-1005-oracle x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Mon Nov 18 07:50:37 2019
  SourcePackage: linux-signed-oracle
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1852976/+subscriptions

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

[Kernel-packages] [Bug 1845810] Re: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor

[Robie Basak]

I was still running your good test kernel:

(actual kernel package appeared autoremoved) 4.15.0-66-generic
#75~lp1845810 noise level low

Upgrading to bionic-updates:

4.15.0-70.79 4.15.0-70-generic #79-Ubuntu noise level high (as expected,
bug not yet fixed)

Upgrading to bionic-proposed:

4.15.0-71.80 4.15.0-71-generic #80-Ubuntu noise level low (bug appears
fixed)

I also checked general audio playback on the bionic-proposed kernel
(4.15.0-71.80 4.15.0-71-generic #80-Ubuntu) and that also seems fine.

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

Title:
  [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise
  floor

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise
  in my headphones has increased to unreasonable levels. In linux-
  image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise
  was present but at a bearable level, which I had always assumed was a
  hardware design issue. Now, with the increased noise floor, the
  headphone socket is essentially unusable.

  This is a regression in a stable release (Bionic). The problem
  consistently reproduces as follows:

  OK: linux-image-4.15.0-58-generic 4.15.0-58.64
  BAD: linux-image-4.15.0-60-generic4.15.0-60.67
  BAD: linux-image-4.15.0-62-generic4.15.0-62.69
  BAD: linux-image-4.15.0-64-generic4.15.0-64.73

  Steps to reproduce:

  Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually
  reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything
  is on defaults.

  1. Boot with no headphones connected
  2. Log in
  3. Plug the headphones in

  Expected: normal noise level
  Actual: very high noise level. Playback does work correctly but the SnR is 
terrible.

  The "Select Audio Device" prompt appears, but the noise problem is
  present before I make a selection. If I select Headphones or Headset
  (I'm using a headset) then the noise remains after a brief (~0.5s)
  interruption. If I select Microphone then the noise goes, but then the
  audio comes through the speakers and not the headset as required.

  I have tried messing with alsamixer but haven't found anything to
  explain or reduce the noise. Switching to a previous kernel fixes the
  problem immediately with no settings change required.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18
  Uname: Linux 4.15.0-64-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robie  2126 F pulseaudio
robie  3648 F alsamixer
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 23:51:05 2019
  InstallationDate: Installed on 2017-05-11 (870 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] Background 
noise or low volume
  UpgradeStatus: Upgraded to bionic on 2018-07-28 (427 days ago)
  dmi.bios.date: 03/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.11.0
  dmi.board.name: 00GCYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robie  2329 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc
  InstallationDate: Installed on 2017-05-11 (871 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-64-generic 

[Kernel-packages] [Bug 1845810] Re: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor

[Robie Basak]

@kaihengfeng Thank you for your help in resolving this!

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

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

Title:
  [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise
  floor

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise
  in my headphones has increased to unreasonable levels. In linux-
  image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise
  was present but at a bearable level, which I had always assumed was a
  hardware design issue. Now, with the increased noise floor, the
  headphone socket is essentially unusable.

  This is a regression in a stable release (Bionic). The problem
  consistently reproduces as follows:

  OK: linux-image-4.15.0-58-generic 4.15.0-58.64
  BAD: linux-image-4.15.0-60-generic4.15.0-60.67
  BAD: linux-image-4.15.0-62-generic4.15.0-62.69
  BAD: linux-image-4.15.0-64-generic4.15.0-64.73

  Steps to reproduce:

  Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually
  reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything
  is on defaults.

  1. Boot with no headphones connected
  2. Log in
  3. Plug the headphones in

  Expected: normal noise level
  Actual: very high noise level. Playback does work correctly but the SnR is 
terrible.

  The "Select Audio Device" prompt appears, but the noise problem is
  present before I make a selection. If I select Headphones or Headset
  (I'm using a headset) then the noise remains after a brief (~0.5s)
  interruption. If I select Microphone then the noise goes, but then the
  audio comes through the speakers and not the headset as required.

  I have tried messing with alsamixer but haven't found anything to
  explain or reduce the noise. Switching to a previous kernel fixes the
  problem immediately with no settings change required.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18
  Uname: Linux 4.15.0-64-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robie  2126 F pulseaudio
robie  3648 F alsamixer
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 23:51:05 2019
  InstallationDate: Installed on 2017-05-11 (870 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] Background 
noise or low volume
  UpgradeStatus: Upgraded to bionic on 2018-07-28 (427 days ago)
  dmi.bios.date: 03/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.11.0
  dmi.board.name: 00GCYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robie  2329 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc
  InstallationDate: Installed on 2017-05-11 (871 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-64-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-64-generic N/A
   linux-backports-modules-4.15.0-64-generic  N/A
   linux-firmware 1.173.9
  Tags:  bionic
  Uname: Linux 4.15.0-64-generic x86_64
  

[Kernel-packages] [Bug 1852978] Re: Asus USB-AC51 is not recognized by default on 4.15

[Po-Hsu Lin]

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

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

Title:
  Asus USB-AC51 is not recognized by default on 4.15

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Ubuntu 18.04 with kernel 4.15.0-70-generic all up to date to latest @
  18/11/2019

  Asus USB-AC51 wifi dongle does not get recognized by default on kernel
  4.15

  Installing the HWE kernel for 18.04 fixed this

  Bus 001 Device 003: ID 0b05:17d1 ASUSTek Computer, Inc. AC51
  802.11a/b/g/n/ac Wireless Adapter [Mediatek MT7610/Ralink RT2870]

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-5.0.0-36-generic 5.0.0-36.39~18.04.1
  ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 18 09:51:28 2019
  InstallationDate: Installed on 2018-09-25 (419 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: linux-signed-hwe
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  johan  2297 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-09-25 (419 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IwConfig:
   eno1  no wireless extensions.
   
   lono wireless extensions.
  MachineType: Hewlett-Packard HP Pavilion g7 Notebook PC
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic 
root=UUID=5b035efe-03db-41c4-b44b-a415de3a0d59 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18
  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
  RfKill:
   
  Tags:  bionic
  Uname: Linux 4.15.0-70-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1842
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong7NotebookPC:pvr08831138591620100:rvnHewlett-Packard:rn1842:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g7 Notebook PC
  dmi.product.version: 08831138591620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852978/+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 1852976] Re: zram01 / zram02 / zram03 in kernel_misc from ubuntu_ltp failed on D-Oracle

[Po-Hsu Lin]

** Changed in: ubuntu-kernel-tests
 Assignee: (unassigned) => Po-Hsu Lin (cypressyew)

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

Title:
  zram01 / zram02 / zram03 in kernel_misc from ubuntu_ltp failed on
  D-Oracle

Status in ubuntu-kernel-tests:
  In Progress
Status in linux-signed-oracle package in Ubuntu:
  New
Status in linux-signed-oracle source package in Disco:
  New

Bug description:
  It looks like the failures in zram01 are causing zram02 and zram03 to
  fail as well.

  Seems that this is broken since commit 7cfac804 (zram: Rewrite shell
  tests into new API)

   tag=zram01 stime=1573887406 dur=300 exit=signaled stat=9 core=no cu=23757 
cs=7590
   startup='Sat Nov 16 06:56:46 2019'
   zram01 1 TINFO: timeout per run is 0h 5m 0s
   zram01 1 TINFO: create '4' zram device(s)
   zram01 1 TPASS: test succeeded
   zram01 1 TCONF: The device attribute max_comp_streams was introduced in 
kernel 3.15 and deprecated in 4.7
   zram01 2 TINFO: test that we can set compression algorithm
   zram01 2 TINFO: supported algs: [lzo] lz4 lz4hc 842 zstd
   zram01 2 TINFO: /sys/block/zram0/comp_algorithm = 'lzo' (1/4)
   zram01 2 TINFO: /sys/block/zram1/comp_algorithm = 'lzo' (2/4)
   zram01 2 TINFO: /sys/block/zram2/comp_algorithm = 'lzo' (3/4)
   zram01 2 TINFO: /sys/block/zram3/comp_algorithm = 'lzo' (4/4)
   zram01 2 TPASS: test succeeded
   zram01 3 TINFO: set disk size to zram device(s)
   zram01 3 TINFO: /sys/block/zram0/disksize = '26214400' (1/4)
   zram01 3 TINFO: /sys/block/zram1/disksize = '26214400' (2/4)
   zram01 3 TINFO: /sys/block/zram2/disksize = '26214400' (3/4)
   zram01 3 TINFO: /sys/block/zram3/disksize = '402653184' (4/4)
   zram01 3 TPASS: test succeeded
   zram01 4 TINFO: set memory limit to zram device(s)
   zram01 4 TINFO: /sys/block/zram0/mem_limit = '25M' (1/4)
   zram01 4 TINFO: /sys/block/zram1/mem_limit = '25M' (2/4)
   zram01 4 TINFO: /sys/block/zram2/mem_limit = '25M' (3/4)
   zram01 4 TINFO: /sys/block/zram3/mem_limit = '384M' (4/4)
   zram01 4 TPASS: test succeeded
   zram01 5 TINFO: make ext3 filesystem on /dev/zram0
   zram01 5 TINFO: make ext4 filesystem on /dev/zram1
   zram01 5 TINFO: make xfs filesystem on /dev/zram2
   zram01 5 TINFO: make btrfs filesystem on /dev/zram3
   zram01 5 TPASS: zram_makefs succeeded
   zram01 6 TINFO: mount /dev/zram0
   zram01 6 TINFO: mount /dev/zram1
   zram01 6 TINFO: mount /dev/zram2
   zram01 6 TINFO: mount /dev/zram3
   zram01 6 TPASS: mount of zram device(s) succeeded
   zram01 7 TINFO: filling zram0 (it can take long time)
   zram01 7 TPASS: zram0 was filled with '20628' KB
   zram01 7 TPASS: compression ratio: 732.90:1
   zram01 7 TINFO: filling zram1 (it can take long time)
   zram01 7 TPASS: zram1 was filled with '20140' KB
   zram01 7 TPASS: compression ratio: 5151.97:1
   zram01 7 TINFO: filling zram2 (it can take long time)
   zram01 7 TPASS: zram2 was filled with '17756' KB
   zram01 7 TPASS: compression ratio: 285.26:1
   zram01 7 TINFO: filling zram3 (it can take long time)
   zram01 1 TBROK: test killed, timeout! If you are running on slow machine, 
try exporting LTP_TIMEOUT_MUL > 1

   tag=zram02 stime=1573887712 dur=0 exit=exited stat=1 core=no cu=2 cs=0
   startup='Sat Nov 16 07:01:52 2019'
   zram02 1 TINFO: timeout per run is 0h 5m 0s
   zram02 1 TINFO: create '1' zram device(s)
   zram02 1 TFAIL: unexpected num of devices: 4
   /opt/ltp/testcases/bin/zram02.sh: 27: echo: echo: I/O error
   zram02 1 TINFO: AppArmor enabled, this may affect test results
   zram02 1 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires 
super/root)
   zram02 1 TINFO: loaded AppArmor profiles: none

   Summary:
   passed 0
   failed 1
   skipped 0
   warnings 0

   tag=zram03 stime=1573887718 dur=0 exit=exited stat=2 core=no cu=0 cs=0
   startup='Sat Nov 16 07:01:58 2019'
   zram03 0 TINFO : create a zram device with 536870912 bytes in size.
   zram03 1 TBROK : safe_file_ops.c:301: Failed to close FILE 
'/sys/block/zram0/disksize' at zram03.c:87: errno=EBUSY(16): Device or resource 
busy
   zram03 2 TBROK : safe_file_ops.c:301: Remaining cases broken

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-1005-oracle 5.0.0-1005.9
  ProcVersionSignature: User Name 5.0.0-1005.9-oracle 5.0.21
  Uname: Linux 5.0.0-1005-oracle x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  Date: Mon Nov 18 07:50:37 2019
  SourcePackage: linux-signed-oracle
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1852976/+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 1825222] Re: CONFIG_ARCH_ROCKCHIP is not set in ubuntu 18.04 aarch64, arm64

[Po-Hsu Lin]

Hi Paweł,

I think it's better to open another bug for that. Please feel free to
subscribe me to that one.

Another question is that do you need CONFIG_CRYPTO_DEV_ROCKCHIP to be set to 
'm'?
If not I will set it to 'n' just like armhf.

Also, as Eoan is available now, can you help us to verify if this kernel works 
for you:
https://people.canonical.com/~phlin/kernel/lp-1825222-rockchip-arm64/E/

The .deb in w-RK818 is the kernel with ROCKCHIP support + RK818 id patch.
/boot/config-5.3.0-24-generic:CONFIG_ARCH_ROCKCHIP=y
/boot/config-5.3.0-24-generic:CONFIG_PCIE_ROCKCHIP=y
/boot/config-5.3.0-24-generic:CONFIG_PCIE_ROCKCHIP_HOST=m
/boot/config-5.3.0-24-generic:CONFIG_PCIE_ROCKCHIP_EP=y
/boot/config-5.3.0-24-generic:CONFIG_EMAC_ROCKCHIP=m
/boot/config-5.3.0-24-generic:CONFIG_DWMAC_ROCKCHIP=m
/boot/config-5.3.0-24-generic:CONFIG_ROCKCHIP_PHY=m
/boot/config-5.3.0-24-generic:CONFIG_SPI_ROCKCHIP=m
/boot/config-5.3.0-24-generic:CONFIG_PINCTRL_ROCKCHIP=y
/boot/config-5.3.0-24-generic:CONFIG_ROCKCHIP_IODOMAIN=m
/boot/config-5.3.0-24-generic:CONFIG_ROCKCHIP_THERMAL=m
/boot/config-5.3.0-24-generic:CONFIG_VIDEO_ROCKCHIP_RGA=m
/boot/config-5.3.0-24-generic:CONFIG_DRM_ROCKCHIP=m
/boot/config-5.3.0-24-generic:CONFIG_ROCKCHIP_ANALOGIX_DP=y
/boot/config-5.3.0-24-generic:CONFIG_ROCKCHIP_CDN_DP=y
/boot/config-5.3.0-24-generic:CONFIG_ROCKCHIP_DW_HDMI=y
/boot/config-5.3.0-24-generic:CONFIG_ROCKCHIP_DW_MIPI_DSI=y
/boot/config-5.3.0-24-generic:CONFIG_ROCKCHIP_INNO_HDMI=y
/boot/config-5.3.0-24-generic:CONFIG_ROCKCHIP_LVDS=y
/boot/config-5.3.0-24-generic:CONFIG_ROCKCHIP_RGB=y
/boot/config-5.3.0-24-generic:CONFIG_ROCKCHIP_RK3066_HDMI=y
/boot/config-5.3.0-24-generic:CONFIG_SND_SOC_ROCKCHIP=m
/boot/config-5.3.0-24-generic:CONFIG_SND_SOC_ROCKCHIP_I2S=m
/boot/config-5.3.0-24-generic:CONFIG_SND_SOC_ROCKCHIP_PDM=m
/boot/config-5.3.0-24-generic:CONFIG_SND_SOC_ROCKCHIP_SPDIF=m
/boot/config-5.3.0-24-generic:CONFIG_SND_SOC_ROCKCHIP_MAX98090=m
/boot/config-5.3.0-24-generic:CONFIG_SND_SOC_ROCKCHIP_RT5645=m
/boot/config-5.3.0-24-generic:CONFIG_MMC_DW_ROCKCHIP=m
/boot/config-5.3.0-24-generic:CONFIG_ROCKCHIP_TIMER=y
/boot/config-5.3.0-24-generic:CONFIG_ROCKCHIP_MBOX=y
/boot/config-5.3.0-24-generic:CONFIG_ROCKCHIP_IOMMU=y
/boot/config-5.3.0-24-generic:CONFIG_ROCKCHIP_GRF=y
/boot/config-5.3.0-24-generic:CONFIG_ROCKCHIP_PM_DOMAINS=y
/boot/config-5.3.0-24-generic:CONFIG_DEVFREQ_EVENT_ROCKCHIP_DFI=m
/boot/config-5.3.0-24-generic:CONFIG_ROCKCHIP_SARADC=m
/boot/config-5.3.0-24-generic:CONFIG_PWM_ROCKCHIP=m
/boot/config-5.3.0-24-generic:CONFIG_PHY_ROCKCHIP_DP=m
/boot/config-5.3.0-24-generic:CONFIG_PHY_ROCKCHIP_EMMC=m
/boot/config-5.3.0-24-generic:CONFIG_PHY_ROCKCHIP_INNO_HDMI=m
/boot/config-5.3.0-24-generic:CONFIG_PHY_ROCKCHIP_INNO_USB2=m
/boot/config-5.3.0-24-generic:CONFIG_PHY_ROCKCHIP_PCIE=m
/boot/config-5.3.0-24-generic:CONFIG_PHY_ROCKCHIP_TYPEC=m
/boot/config-5.3.0-24-generic:CONFIG_PHY_ROCKCHIP_USB=m
/boot/config-5.3.0-24-generic:CONFIG_ROCKCHIP_EFUSE=m
/boot/config-5.3.0-24-generic:CONFIG_CRYPTO_DEV_ROCKCHIP=m


Thanks

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

Title:
  CONFIG_ARCH_ROCKCHIP is not set in ubuntu 18.04 aarch64,arm64

Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Bionic:
  New
Status in linux source package in Disco:
  New
Status in linux source package in Eoan:
  Incomplete

Bug description:
  Would it be possible to enable rockchip support in Ubuntu 18.04 kernel
  for arch aarch64(arm64)?

  Related kernel config options:

  CONFIG_ARCH_ROCKCHIP
  CONFIG_PCIE_ROCKCHIP
  CONFIG_PCIE_ROCKCHIP_HOST
  CONFIG_EMAC_ROCKCHIP
  CONFIG_DWMAC_ROCKCHIP
  CONFIG_ROCKCHIP_PHY
  CONFIG_SPI_ROCKCHIP
  CONFIG_PINCTRL_ROCKCHIP
  CONFIG_ROCKCHIP_IODOMAIN
  CONFIG_ROCKCHIP_THERMAL
  CONFIG_VIDEO_ROCKCHIP_RGA
  CONFIG_DRM_ROCKCHIP
  CONFIG_ROCKCHIP_ANALOGIX_DP
  CONFIG_ROCKCHIP_CDN_DP
  CONFIG_ROCKCHIP_DW_HDMI
  CONFIG_ROCKCHIP_DW_MIPI_DSI
  CONFIG_ROCKCHIP_INNO_HDMI
  CONFIG_ROCKCHIP_LVDS
  CONFIG_ROCKCHIP_RGB
  CONFIG_SND_SOC_ROCKCHIP
  CONFIG_SND_SOC_ROCKCHIP_I2S
  CONFIG_SND_SOC_ROCKCHIP_PDM
  CONFIG_SND_SOC_ROCKCHIP_SPDIF
  CONFIG_SND_SOC_ROCKCHIP_MAX98090
  CONFIG_SND_SOC_ROCKCHIP_RT5645
  CONFIG_MMC_DW_ROCKCHIP
  CONFIG_ROCKCHIP_TIMER
  CONFIG_ROCKCHIP_MBOX
  CONFIG_ROCKCHIP_IOMMU
  CONFIG_ROCKCHIP_GRF
  CONFIG_ROCKCHIP_PM_DOMAINS
  CONFIG_DEVFREQ_EVENT_ROCKCHIP_DFI
  CONFIG_ROCKCHIP_SARADC
  CONFIG_PWM_ROCKCHIP
  CONFIG_PHY_ROCKCHIP_DP
  CONFIG_PHY_ROCKCHIP_EMMC
  CONFIG_PHY_ROCKCHIP_INNO_HDMI
  CONFIG_PHY_ROCKCHIP_INNO_USB2
  CONFIG_PHY_ROCKCHIP_PCIE
  CONFIG_PHY_ROCKCHIP_TYPEC
  CONFIG_PHY_ROCKCHIP_USB
  CONFIG_ROCKCHIP_EFUSE
  CONFIG_CRYPTO_DEV_ROCKCHIP

  Cheers,
  Paweł Jarosz

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

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

[Kernel-packages] [Bug 1852268] Re: bionic/linux-aws-fips: 4.15.0-2005.5 -proposed tracker

[Ubuntu Kernel Bot]

** Changed in: kernel-sru-workflow/promote-to-security
   Status: New => Invalid

** Changed in: kernel-sru-workflow/security-signoff
   Status: New => Invalid

** 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 --
  kernel-stable-master-bug: 1852270
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
- phase: Ready for Packaging
- phase-changed: Monday, 18. November 2019 07:37 UTC
+ phase: Packaging
+ phase-changed: Tuesday, 19. November 2019 10:20 UTC
  reason:
-   prepare-package: Pending -- version not specified
+   prepare-package: Pending -- package not yet uploaded
+   prepare-package-lrm: Pending -- package not yet uploaded
+   prepare-package-meta: Pending -- package not yet uploaded
+   prepare-package-signed: Pending -- package not yet uploaded
  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/1852268

Title:
  bionic/linux-aws-fips: 4.15.0-2005.5 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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 Bionic:
  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 --
  kernel-stable-master-bug: 1852270
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Packaging
  phase-changed: Tuesday, 19. November 2019 10:20 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852268/+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 1550779] Re: [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun

[vinibali]

Hi Timo,

I wanted to try the AMD64 version at: 
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/2019-11-14/.
But only unsigned kernels are shipped and I couldn't switch from UEFI or boot 
unsigned kernels, because it's a corporate machine.
Do you have any ideas?

Regards

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

Title:
  [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A
  FIFO underrun

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Upgraded linux-image-extra-4.2.0-30-generic I see graphic glitches,
  looks like the graphic buffer gets screwed up

  - funny repetition's patterns  (back in time glitches)
  - black screen (<1sec)
  - graphic errors  

  I can influence the severity of the issue with switching windows and
  using certain programs, e.g. Google Maps in chrome causes this issue
  reproducibly

  dmesg  | grep i915
  [2.726864] [drm] Initialized i915 1.6.0 20150522 for :00:02.0 on 
minor 0
  [2.792005] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit 
banging on pin 5
  [3.471092] i915 :00:02.0: fb0: inteldrmfb frame buffer device
  [3.471093] i915 :00:02.0: registered panic notifier
  [9.573129] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU 
pipe A FIFO underrun
  [9.574847] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [9.574895] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  linux-image-extra-4.2.0-27-generic works find

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-30.36-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-30-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sat Feb 27 20:26:07 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.14, 4.2.0-27-generic, x86_64: installed
   virtualbox, 5.0.14, 4.2.0-30-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:21da]
  InstallationDate: Installed on 2016-02-11 (15 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  MachineType: LENOVO 42912XG
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.2.0-30-generic 
root=UUID=cb34d7bb-9316-49b3-aa94-4e2a3512168f ro rootflags=subvol=@ noprompt 
quiet
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8DET69WW (1.39 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 42912XG
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8DET69WW(1.39):bd07/18/2013:svnLENOVO:pn42912XG:pvrThinkPadX220:rvnLENOVO:rn42912XG:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 42912XG
  dmi.product.version: ThinkPad X220
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Sat Feb 27 20:25:23 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12359 
   vendor SEC
  xserver.version: 2:1.17.2-1ubuntu9.1

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1730864] Re: Shutdown crashing when connected to AC adapter

[Bug Watch Updater]

Launchpad has imported 16 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=103783.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-11-16T17:54:35+00:00 Renê Barbosa wrote:

Created attachment 135524
dmesg

Hello there,

I'm using Ubuntu 17.10 (fully updated) and my system is crashing at
shutdown. It's freezing until I force a reboot/shutdown using Magic
SysRq.

The error is:

Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294280] [drm:atom_op_jump 
[amdgpu]] *ERROR* atombios stuck in loop for more than 5secs aborting
Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294336] 
[drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck 
executing 75A8 (len 272, WS 0, PS 4) @ 0x75F1
Nov 6 22:16:49 rene-Inspiron-5447 kernel: [ 248.294384] 
[drm:amdgpu_atom_execute_table_locked [amdgpu]] *ERROR* atombios stuck 
executing 640C (len 68, WS 0, PS 8) @ 0x6430]

This behavior is only happening when my laptop is charging. When running
on battery I got a clean shutdown/reboot.

Already tried to run the latest kernel package from
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.14 and the problem is
exactly the same.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: linux-image-4.13.0-16-generic 4.13.0-16.19 [modified: 
boot/vmlinuz-4.13.0-16-generic]
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: rene 1249 F pulseaudio
 /dev/snd/controlC0: rene 1249 F pulseaudio
CurrentDesktop: GNOME
Date: Wed Nov 8 01:00:51 2017
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=0f3b9237-1086-430d-be15-043b9ca00fd2
InstallationDate: Installed on 2017-11-06 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: Dell Inc. Inspiron 5447
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=UUID=1237aa76-9a2f-4a06-8552-526f124914ff ro quiet splash 
acpi_backlight=intel_backlight
RelatedPackageVersions:
 linux-restricted-modules-4.13.0-16-generic N/A
 linux-backports-modules-4.13.0-16-generic N/A
 linux-firmware 1.169
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/25/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0MHP6R
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A10
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd08/25/2016:svnDellInc.:pnInspiron5447:pvrA10:rvnDellInc.:rn0MHP6R:rvrA00:cvnDellInc.:ct8:cvrA10:
dmi.product.family: 00
dmi.product.name: Inspiron 5447
dmi.product.version: A10
dmi.sys.vendor: Dell Inc.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730864/comments/7


On 2017-11-16T17:55:13+00:00 Renê Barbosa wrote:

Created attachment 135525
lspci

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730864/comments/8


On 2017-11-16T17:55:34+00:00 Renê Barbosa wrote:

Created attachment 135526
modules

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730864/comments/9


On 2017-11-16T18:00:00+00:00 Alexdeucher wrote:

(In reply to Rene Barbosa from comment #0)
> Created attachment 135524 [details]
> dmesg

Looks like you attached the wrong file.  Please attach your full dmesg
output.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730864/comments/11


On 2017-11-16T18:10:09+00:00 Renê Barbosa wrote:

Created attachment 135527
dmesg

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730864/comments/12


On 2017-11-16T18:10:51+00:00 Renê Barbosa wrote:

Err. Sorry about that.
I've uploaded the correct file now.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730864/comments/13


On 2017-11-16T19:36:45+00:00 Renê Barbosa wrote:

An interesting information: It's only with open source amdgpu driver.
With amdgpu-pro it's not happening but this driver isn't compatible with
Ubuntu 17.10.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1730864/comments/14


On 2017-11-18T20:54:52+00:00 Vadym Krevs wrote:

I've got a similar issue on a 

[Kernel-packages] [Bug 1852268] Re: bionic/linux-aws-fips: 4.15.0-2005.5 -proposed tracker

[Andrea Righi]

** Summary changed:

- bionic/linux-aws-fips:  -proposed tracker
+ bionic/linux-aws-fips: 4.15.0-2005.5 -proposed tracker

** Changed in: kernel-sru-workflow/prepare-package
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/prepare-package
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi 
(arighi)

** Changed in: kernel-sru-workflow/prepare-package-lrm
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-lrm
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi 
(arighi)

** Changed in: kernel-sru-workflow/prepare-package-meta
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-meta
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi 
(arighi)

** Changed in: kernel-sru-workflow/prepare-package-signed
   Status: New => In Progress

** Changed in: kernel-sru-workflow/prepare-package-signed
 Assignee: Canonical Kernel Team (canonical-kernel-team) => Andrea Righi 
(arighi)

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

Title:
  bionic/linux-aws-fips: 4.15.0-2005.5 -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:
  In Progress
Status in Kernel SRU Workflow prepare-package-lrm series:
  In Progress
Status in Kernel SRU Workflow prepare-package-meta series:
  In Progress
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-signing-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
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 Bionic:
  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 --
  kernel-stable-master-bug: 1852270
  packages:
lrm: linux-restricted-modules-aws-fips
main: linux-aws-fips
meta: linux-meta-aws-fips
signed: linux-signed-aws-fips
  phase: Packaging
  phase-changed: Tuesday, 19. November 2019 10:20 UTC
  reason:
prepare-package: Pending -- package not yet uploaded
prepare-package-lrm: Pending -- package not yet uploaded
prepare-package-meta: Pending -- package not yet uploaded
prepare-package-signed: Pending -- package not yet uploaded
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852268/+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 1780590] Re: Add support for Realtek 8723DE wireless adapter

[Yuan-Chen Cheng]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Tags added: oem-priority

** Changed in: oem-priority
   Importance: Undecided => Critical

** Changed in: oem-priority
   Status: New => Confirmed

** Changed in: oem-priority
 Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn)

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

Title:
  Add support for Realtek 8723DE wireless adapter

Status in OEM Priority Project:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Won't Fix
Status in linux-firmware source package in Disco:
  Fix Released
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Won't Fix
Status in linux-firmware source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Confirmed
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-osp1 source package in Focal:
  Won't Fix

Bug description:
  === SRU Justification ===
  [Impact]
  There's no in-kernel support for Realtek 8723DE, so users need to use
  out-of-tree DKMS which is not from Ubuntu archive. This has security
  implication and should be avoided. Also this provides pretty bad user
  experience.

  [Fix]
  Add support to Realtek 8723DE.
  All commits are cherry-picked from Realtek maintained repo:
  https://github.com/rtlwifi-linux/rtw88_8723de

  [Test]
  With the patch series applied, 8723DE can scan and connect to APs
  succesfully. Also did some S3 smoke test, it continues to work.

  [Regression Potential]
  Low. The device in question was never supported, and if there's any
  regression, we can count on Realtek Wireless team, thy are now pretty
  responsive on upstream mailing list.

  === Original Bug Report ===
  recently I just installed ubuntu 18.04 lts in dual bot next to windows 10. 
Everything in the installation was fine until the moment to start session. The 
problem is that the wireless network card does not detect me and when entering 
the configuration I simply get an error message saying that no wireless adapter 
was found. I have already followed all the tutorials I found on the web. and 
update the driver of a github repository, and install how much program they 
told me to install and I still can not connect via wifi.

  I just do not know what to do. I have a laptop hp 14-bs004 came with
  windows 10 installed. The information on the network card is as
  follows:

   Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec: 
d723]
  Subsystem: Hewlett-Packard Company Device [103c: 8319]
  Control: I / O + Mem + BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
  Status: Cap + 66MHz- UDF- FastB2B- ParErr- DEVSEL = fast> TAbort-  SERR- 
  Kernel modules: wl

  already install the most recent kernel, already intale driver driver
  realtek rtl8723be according to the instructions of the git repository.
  and nothing has worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  7 22:57:40 2018
  InstallationDate: Installed on 2018-07-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1780590/+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 1319589] Re: [drm:rv770_dpm_set_power_state] *ERROR* rv770_set_sw_state failed

[Bug Watch Updater]

** Changed in: dri
   Status: Confirmed => Unknown

** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #463
   https://gitlab.freedesktop.org/drm/amd/issues/463

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

Title:
  [drm:rv770_dpm_set_power_state] *ERROR* rv770_set_sw_state failed

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

Bug description:
  Hello,
  On Ubuntu 14.04 LTS, when the computer starts (before the splash screen 
appears), I see this error in the console:

  [drm:rv770_dpm_set_power_state] *ERROR* rv770_set_sw_state failed

  I don't know what does exactly this bug, but I supposed that it's not
  normal.

  
  OS: Linux
  Type: amd64
  Distribution: Ubuntu 14.04 LTS
  GPU: ATI Mobility Radeon HD 4570
  → 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV710/M92 [Mobility Radeon HD 4530/4570/545v]

  Kernel: 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014
  x86_64 x86_64 x86_64 GNU/Linux

  I use the free driver for Linux, ATI doesn't support this GPU with
  proprietary drivers today... but without this little bug, the free
  drivers are very good :)

  
  Message appears at [   17.026313]
  (See dmesg file)

  Thank you.
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  valentin   4277 F pulseaudio
   /dev/snd/controlC0:  valentin   4277 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=2fe681c2-5497-453b-bc19-4401ca76baaf
  InstallationDate: Installed on 2014-05-06 (8 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  MachineType: Acer Aspire 5542
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=20964cff-7885-4482-8618-d60d52c7d229 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.2
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/18/2010
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.09
  dmi.board.name: JV50TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.09:bd01/18/2010:svnAcer:pnAspire5542:pvr0100:rvnAcer:rnJV50TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 5542
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1319589/+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 1852586] Re: Boot hangs after "Loading initial ramdisk ..."

[Eugen]

Hi,

here is the output of 
sudo update-initramfs -u -k 5.3.0-23-generic

update-initramfs: Generating /boot/initrd.img-5.3.0-23-generic
I: The initramfs will attempt to resume from /dev/dm-2
I: (/dev/mapper/vgubuntu-swap_1)
I: Set the RESUME variable to override this.

(for 24 it's the same)

also 5.3.0-24 from eoan-proposed doesn't work either

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

Title:
  Boot hangs after "Loading initial ramdisk ..."

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Kernel 5.3.0.-23-generic and
  Kernel 5.3.0.-22-generic 

  don't boot, I get the "Loading initial ramdisk ..." on purple background, 
nothing happens, Notebook need to get shutoff to resume
  Kernels:
  5.3.0-19 and
  5.3.0-18 
  do work

  It's a Lenovo L580 Running Ubuntu 19.10

  
  output of version signature:
  Ubuntu 5.3.0-19.20-generic 5.3.1

  output of lscpi:
  00:00.0 Host bridge [0600]: Intel Corporation Device [8086:3e34] (rev 0c)
Subsystem: Lenovo Device [17aa:5075]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: skl_uncore

  00:02.0 VGA compatible controller [0300]: Intel Corporation UHD Graphics 620 
(Whiskey Lake) [8086:3ea0] (rev 02) (prog-if 00 [VGA controller])
Subsystem: Lenovo UHD Graphics 620 (Whiskey Lake) [17aa:5075]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Capabilities: [70] Express (v2) Root Complex Integrated Endpoint, MSI 00
DevCap: MaxPayload 128 bytes, PhantFunc 0
ExtTag- RBE+
DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
RlxdOrd- ExtTag- PhantFunc- AuxPwr- NoSnoop-
MaxPayload 128 bytes, MaxReadReq 128 bytes
DevSta: CorrErr- NonFatalErr- FatalErr- UnsupReq- AuxPwr- 
TransPend-
DevCap2: Completion Timeout: Not Supported, TimeoutDis-, LTR-, 
OBFF Not Supported
 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis-, LTR-, 
OBFF Disabled
 AtomicOpsCtl: ReqEn-
Capabilities: [ac] MSI: Enable+ Count=1/1 Maskable- 64bit-
Address: fee00018  Data: 
Capabilities: [d0] Power Management version 2
Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA 
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [100 v1] Process Address Space ID (PASID)
PASIDCap: Exec- Priv-, Max PASID Width: 14
PASIDCtl: Enable- Exec- Priv-
Capabilities: [200 v1] Address Translation Service (ATS)
ATSCap: Invalidate Queue Depth: 00
ATSCtl: Enable-, Smallest Translation Unit: 00
Capabilities: [300 v1] Page Request Interface (PRI)
PRICtl: Enable- Reset-
PRISta: RF- UPRGI- Stopped+
Page Request Capacity: 8000, Page Request Allocation: 

Kernel driver in use: i915
Kernel modules: i915

  00:04.0 Signal processing controller [1180]: Intel Corporation Xeon E3-1200 
v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem [8086:1903] (rev 0c)
Subsystem: Lenovo Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor 
Thermal Subsystem [17aa:5075]
Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device

  00:08.0 System peripheral [0880]: Intel Corporation Xeon E3-1200 v5/v6 / 
E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model [8086:1911]
Subsystem: Lenovo Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core 
Processor Gaussian Mixture Model [17aa:5075]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- TAbort- 
SERR- 
Kernel driver in use: xhci_hcd

  00:14.2 RAM memory [0500]: Intel Corporation Cannon Point-LP Shared SRAM 
[8086:9def] (rev 30)
Subsystem: Lenovo Cannon Point-LP Shared SRAM [17aa:5075]
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- TAbort- SERR- 
Kernel driver in use: intel-lpss

[Kernel-packages] [Bug 1319589]

[Martin-peres-n]

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/drm/amd/issues/463.

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

Title:
  [drm:rv770_dpm_set_power_state] *ERROR* rv770_set_sw_state failed

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

Bug description:
  Hello,
  On Ubuntu 14.04 LTS, when the computer starts (before the splash screen 
appears), I see this error in the console:

  [drm:rv770_dpm_set_power_state] *ERROR* rv770_set_sw_state failed

  I don't know what does exactly this bug, but I supposed that it's not
  normal.

  
  OS: Linux
  Type: amd64
  Distribution: Ubuntu 14.04 LTS
  GPU: ATI Mobility Radeon HD 4570
  → 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
RV710/M92 [Mobility Radeon HD 4530/4570/545v]

  Kernel: 3.13.0-24-generic #47-Ubuntu SMP Fri May 2 23:30:00 UTC 2014
  x86_64 x86_64 x86_64 GNU/Linux

  I use the free driver for Linux, ATI doesn't support this GPU with
  proprietary drivers today... but without this little bug, the free
  drivers are very good :)

  
  Message appears at [   17.026313]
  (See dmesg file)

  Thank you.
  --- 
  ApportVersion: 2.14.1-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  valentin   4277 F pulseaudio
   /dev/snd/controlC0:  valentin   4277 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=2fe681c2-5497-453b-bc19-4401ca76baaf
  InstallationDate: Installed on 2014-05-06 (8 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326)
  MachineType: Acer Aspire 5542
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=20964cff-7885-4482-8618-d60d52c7d229 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.2
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/18/2010
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.09
  dmi.board.name: JV50TR
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.09:bd01/18/2010:svnAcer:pnAspire5542:pvr0100:rvnAcer:rnJV50TR:rvrRev:cvnAcer:ct10:cvrNone:
  dmi.product.name: Aspire 5542
  dmi.product.version: 0100
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/dri/+bug/1319589/+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 1852253] Re: disco/linux: 5.0.0-37.40 -proposed tracker

[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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 14. November 2019 18:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
-   bionic/linux-oem-osp1: bug 1852251
+   bionic/linux-oem-osp1: bug 1852251, bug 1853116
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
unknown/unknown: bug 1852245
  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/1852253

Title:
  disco/linux: 5.0.0-37.40 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  In Progress
Status in Kernel SRU Workflow certification-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-lrm 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-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-security series:
  New
Status in Kernel SRU Workflow promote-to-updates series:
  New
Status in Kernel SRU Workflow regression-testing series:
  In Progress
Status in Kernel SRU Workflow security-signoff series:
  In Progress
Status in Kernel SRU Workflow verification-testing series:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Disco:
  Confirmed

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
  bugs-spammed: true
  packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
  phase: Testing
  phase-changed: Thursday, 14. November 2019 18:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-bluefield: bug 1852252
bionic/linux-hwe: bug 1852250
bionic/linux-oem-osp1: bug 1852251, bug 1853116
disco/linux-aws: bug 1852236
disco/linux-azure: bug 1852239
disco/linux-gcp: bug 1852244
disco/linux-kvm: bug 1852245
disco/linux-oracle: bug 1852248
disco/linux-raspi2: bug 1852233
disco/linux-snapdragon: bug 1852249
unknown/unknown: bug 1852245
  variant: debs

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852253/+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 1780590] Re: Add support for Realtek 8723DE wireless adapter

[Timo Aaltonen]

** Changed in: linux-oem-osp1 (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Add support for Realtek 8723DE wireless adapter

Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  New
Status in linux source package in Bionic:
  Won't Fix
Status in linux-firmware source package in Bionic:
  Fix Released
Status in linux-oem-osp1 source package in Bionic:
  Fix Committed
Status in linux source package in Disco:
  Won't Fix
Status in linux-firmware source package in Disco:
  Fix Released
Status in linux-oem-osp1 source package in Disco:
  Won't Fix
Status in linux source package in Eoan:
  Won't Fix
Status in linux-firmware source package in Eoan:
  Fix Released
Status in linux-oem-osp1 source package in Eoan:
  Won't Fix
Status in linux source package in Focal:
  Confirmed
Status in linux-firmware source package in Focal:
  Fix Released
Status in linux-oem-osp1 source package in Focal:
  Won't Fix

Bug description:
  === SRU Justification ===
  [Impact]
  There's no in-kernel support for Realtek 8723DE, so users need to use
  out-of-tree DKMS which is not from Ubuntu archive. This has security
  implication and should be avoided. Also this provides pretty bad user
  experience.

  [Fix]
  Add support to Realtek 8723DE.
  All commits are cherry-picked from Realtek maintained repo:
  https://github.com/rtlwifi-linux/rtw88_8723de

  [Test]
  With the patch series applied, 8723DE can scan and connect to APs
  succesfully. Also did some S3 smoke test, it continues to work.

  [Regression Potential]
  Low. The device in question was never supported, and if there's any
  regression, we can count on Realtek Wireless team, thy are now pretty
  responsive on upstream mailing list.

  === Original Bug Report ===
  recently I just installed ubuntu 18.04 lts in dual bot next to windows 10. 
Everything in the installation was fine until the moment to start session. The 
problem is that the wireless network card does not detect me and when entering 
the configuration I simply get an error message saying that no wireless adapter 
was found. I have already followed all the tutorials I found on the web. and 
update the driver of a github repository, and install how much program they 
told me to install and I still can not connect via wifi.

  I just do not know what to do. I have a laptop hp 14-bs004 came with
  windows 10 installed. The information on the network card is as
  follows:

   Network controller [0280]: Realtek Semiconductor Co., Ltd. Device [10ec: 
d723]
  Subsystem: Hewlett-Packard Company Device [103c: 8319]
  Control: I / O + Mem + BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
  Status: Cap + 66MHz- UDF- FastB2B- ParErr- DEVSEL = fast> TAbort-  SERR- 
  Kernel modules: wl

  already install the most recent kernel, already intale driver driver
  realtek rtl8723be according to the instructions of the git repository.
  and nothing has worked.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bcmwl-kernel-source 6.30.223.271+bdcom-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  7 22:57:40 2018
  InstallationDate: Installed on 2018-07-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  SourcePackage: bcmwl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780590/+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 1853113] [NEW] 'Convert to RGB working space' dialogue mixed language

[Ian]

Public bug reported:

GIMP 2.10.8, UK English system

1. Open an image with a different working space, and the 'Convert to RGB
working space' dialogue pops up.

2. One check box ('Nicht wieder fragen') and one button ('Behalten') are
labelled in German.

See attached screenshot.

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

** Attachment added: "Screenshot at 2019-11-19 08-48-14.png"
   
https://bugs.launchpad.net/bugs/1853113/+attachment/5306442/+files/Screenshot%20at%202019-11-19%2008-48-14.png

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

Title:
  'Convert to RGB working space' dialogue mixed language

Status in gimp package in Ubuntu:
  New

Bug description:
  GIMP 2.10.8, UK English system

  1. Open an image with a different working space, and the 'Convert to
  RGB working space' dialogue pops up.

  2. One check box ('Nicht wieder fragen') and one button ('Behalten')
  are labelled in German.

  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1853113/+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 1853113] Re: 'Convert to RGB working space' dialogue mixed language

[Ian]

Originally assigned to wrong package, sorry - I thought I had selected
the right one, but hadn't pressed enough buttons!

** Package changed: nvidia-graphics-drivers-435 (Ubuntu) => gimp
(Ubuntu)

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

Title:
  'Convert to RGB working space' dialogue mixed language

Status in gimp package in Ubuntu:
  New

Bug description:
  GIMP 2.10.8, UK English system

  1. Open an image with a different working space, and the 'Convert to
  RGB working space' dialogue pops up.

  2. One check box ('Nicht wieder fragen') and one button ('Behalten')
  are labelled in German.

  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1853113/+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 1853050] Re: Wifi fails to connect (RTL8822BE, linux 5.3.0 w/ rtwpci)

[yk4ever]

@kainengfeng: yes, 5.4-rc8 works (at the cost of not building the nvidia
module).

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

Title:
  Wifi fails to connect (RTL8822BE, linux 5.3.0 w/ rtwpci)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Wifi just fails to connect to an access point after upgrading from
  Ubuntu 19.04 to 19.10.

  Some outputs:
  uname -a
  Linux mothership 5.3.0-23-generic #25-Ubuntu SMP Tue Nov 12 09:22:33 UTC 2019 
x86_64 x86_64 x86_64 GNU/Linux

   lspci -nnk | grep 0280 -A3
  03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 
802.11a/b/g/n/ac WiFi adapter [10ec:b822]
Subsystem: AzureWave RTL8822BE 802.11a/b/g/n/ac WiFi adapter [1a3b:2950]
Kernel driver in use: rtw_pci
Kernel modules: rtwpci

  The typical failure looks like this in journalctl:

  Nov 18 23:04:13 mothership kernel: wlp3s0: send auth to d4:60:e3:15:4d:71 
(try 3/3)
  Nov 18 23:04:13 mothership kernel: [ cut here ]
  Nov 18 23:04:13 mothership kernel: purge skb(s) not reported by firmware
  Nov 18 23:04:13 mothership kernel: WARNING: CPU: 5 PID: 0 at 
drivers/net/wireless/realtek/rtw88/tx.c:156 rtw_tx_report_purge_timer+0x25/0x60 
[rtw88]
  Nov 18 23:04:13 mothership kernel: Modules linked in: nf_conntrack_netlink 
xt_owner xt_conntrack xt_MASQUERADE nfnetlink xfrm_user xfrm_algo iptable_nat 
nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c xt_addrtype 
bpfilter aufs overlay binfmt_misc nvidia_uvm(O
  Nov 18 23:04:13 mothership kernel:  spi_pxa2xx_platform videobuf2_memops 
asus_wmi videobuf2_v4l2 i915 mxm_wmi wmi_bmof sparse_keymap serio_raw 
videobuf2_common cfg80211 dw_dmac soundcore dw_dmac_core videodev input_leds 
drm_kms_helper joydev ipmi_devintf libarc4 mc ipmi_
  Nov 18 23:04:13 mothership kernel: CPU: 5 PID: 0 Comm: swapper/5 Tainted: P   
 W  OE 5.3.0-23-generic #25-Ubuntu
  Nov 18 23:04:13 mothership kernel: Hardware name: ASUSTeK COMPUTER INC. 
X705UDR/X705UDR, BIOS X705UDR.300 08/29/2017
  Nov 18 23:04:13 mothership kernel: RIP: 
0010:rtw_tx_report_purge_timer+0x25/0x60 [rtw88]
  Nov 18 23:04:13 mothership kernel: Code: 00 00 00 00 00 0f 1f 44 00 00 8b 47 
f0 85 c0 75 01 c3 55 48 89 e5 41 55 41 54 53 48 89 fb 48 c7 c7 f0 cd b3 c0 e8 
f6 fa 7b f6 <0f> 0b 4c 8d 6b d8 4c 89 ef e8 dd 3f 1c f7 48 8d 7b e0 49 89 c4 e8
  Nov 18 23:04:13 mothership kernel: RSP: 0018:a25b4020ce48 EFLAGS: 00010286
  Nov 18 23:04:13 mothership kernel: RAX:  RBX: 
913317bed848 RCX: 0006
  Nov 18 23:04:13 mothership kernel: RDX: 0007 RSI: 
0082 RDI: 91331eb57440
  Nov 18 23:04:13 mothership kernel: RBP: a25b4020ce60 R08: 
1754 R09: 0004
  Nov 18 23:04:13 mothership kernel: R10:  R11: 
0001 R12: 91331eb5b600
  Nov 18 23:04:13 mothership kernel: R13: 913317bed848 R14: 
c0adb7d0 R15: 913317bed848
  Nov 18 23:04:13 mothership kernel: FS:  () 
GS:91331eb4() knlGS:
  Nov 18 23:04:13 mothership kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Nov 18 23:04:13 mothership kernel: CR2: 7fb4eee0b000 CR3: 
0003818bc005 CR4: 003606e0
  Nov 18 23:04:13 mothership kernel: Call Trace:
  Nov 18 23:04:13 mothership kernel:  
  Nov 18 23:04:13 mothership kernel:  call_timer_fn+0x32/0x130
  Nov 18 23:04:13 mothership kernel:  __run_timers.part.0+0x177/0x270
  Nov 18 23:04:13 mothership kernel:  ? enqueue_hrtimer+0x3d/0x90
  Nov 18 23:04:13 mothership kernel:  ? recalibrate_cpu_khz+0x10/0x10
  Nov 18 23:04:13 mothership kernel:  ? ktime_get+0x42/0xa0
  Nov 18 23:04:13 mothership kernel:  run_timer_softirq+0x2a/0x50
  Nov 18 23:04:13 mothership kernel:  __do_softirq+0xe1/0x2d6
  Nov 18 23:04:13 mothership kernel:  ? hrtimer_interrupt+0x13b/0x220
  Nov 18 23:04:13 mothership kernel:  irq_exit+0xae/0xb0
  Nov 18 23:04:13 mothership kernel:  smp_apic_timer_interrupt+0x7b/0x140
  Nov 18 23:04:13 mothership kernel:  apic_timer_interrupt+0xf/0x20
  Nov 18 23:04:13 mothership kernel:  
  Nov 18 23:04:13 mothership kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x420
  Nov 18 23:04:13 mothership kernel: Code: ff e8 5f 73 83 ff 80 7d c7 00 74 17 
9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 3d 03 00 00 31 ff e8 c2 ce 89 ff fb 66 0f 
1f 44 00 00 <45> 85 ed 0f 89 d1 01 00 00 41 c7 44 24 10 00 00 00 00 48 83 c4 18
  Nov 18 23:04:13 mothership kernel: RSP: 0018:a25b400f3e38 EFLAGS: 
0246 ORIG_RAX: ff13
  Nov 18 23:04:13 mothership kernel: RAX: 91331eb6a740 RBX: 
b895a740 RCX: 001f
  Nov 18 23:04:13 mothership kernel: RDX:  RSI: 
4041ceb5 RDI: 
  Nov 18 23:04:13 mothership kernel: RBP: a25b400f3e78 R08: 
01076596b017 R09: 1d6b
  Nov 18 

[Kernel-packages] [Bug 1609750] Re: Audio not working on Acer Chromebook R11

[Timo Jyrinki]

I've updated my cyan (Acer Chromebook R11) to kernel 5.4rc7 from
Ubuntu's mainline PPA, but the audio is still not working (no audio
device visible according to pulseaudio).

Are you aware of something else that still needs upstreaming beside the
mentioned
https://github.com/torvalds/linux/commit/d5e120422db8808e1c8b1507900ca393a877c58f
?

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

Title:
  Audio not working on Acer Chromebook R11

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Audio is not working at all on Acer Chromebook R11 (codename CYAN).
  It's a Intel Braswell platform. snd_hda_intel messages seem normal,
  but Pulseaudio does not detect sound hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-1.1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  Date: Thu Aug  4 14:12:03 2016
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  --- 
  ApportVersion: 2.20.3-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08
  InstallationDate: Installed on 2016-07-22 (13 days ago)
  InstallationMedia:
   
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: GOOGLE Cyan
  Package: linux-image-4.4.0-33-generic 4.4.0-33.52
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic 
root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-33-generic N/A
   linux-backports-modules-4.4.0-33-generic  N/A
   linux-firmware1.159
  Tags:  yakkety
  Uname: Linux 4.4.0-33-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/20/2016
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Cyan
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel/+bug/1609750/+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 1852723] Re: [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2

[Ike Panhc]

Test kernel with commit 628859e8 reverted is at

  https://kernel.ubuntu.com/~ikepanhc/lp1852723/

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

Title:
  [Regression] Bionic kernel 4.15.0-71.80 can not boot on ThunderX2

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Confirmed

Bug description:
  Tested on bionic GA 4.15.0-70-generic 4.15.0-71-generic
  and also HWE 5.0.0-37-generic 5.3.0-23-generic

  Only 4.15.0-71-generic can not boot on Cavium ThunderX2

  On console nothing after EFI messages.

  Loading Linux 4.15.0-71-generic ...
  Loading initial ramdisk ...
  EFI stub: Booting Linux Kernel...
  EFI stub: EFI_RNG_PROTOCOL unavailable, no randomness supplied
  EFI stub: Using DTB from configuration table
  EFI stub: Exiting boot services and installing virtual address map...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852723/+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 1853075] Re: 19.10 Boots into a black screen

[Kai-Heng Feng]

$ sudo apt install linux-generic

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

Title:
  19.10 Boots into a black screen

Status in linux package in Ubuntu:
  Invalid

Bug description:
  After upgrading to 19.10 and rebooting. My machine goes into a frozen
  black screen. The default kernel after the update (5.3.0-23-generic)
  does not succeed in booting. If I select the older kernel,
  5.0.0-36-generic, grub does go through and succeeds booting up.

  System is a Dell XPS 15 9550 with Ubuntu Dual Boot. GRUB version
  2.04-1ubuntu12. The Windows partition does work properly, and I am
  able to boot into it. Please advice on how to proceed with a fix, or
  if an update pushed to grub will fix this issue.

  Thanks.
  ---
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  pipemon2417 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 19.10
  HibernationDevice: RESUME=UUID=c26ef9c3-b999-4441-b750-cf80d00fc68e
  InstallationDate: Installed on 2017-11-02 (746 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Touchscreen
   Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications
   Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9550
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-36-generic 
root=UUID=6b1a4315-6bdf-471f-90b5-6fb32c3bfc2b ro quiet splash
  ProcVersionSignature: Ubuntu 5.0.0-36.39-generic 5.0.21
  RelatedPackageVersions:
   linux-restricted-modules-5.0.0-36-generic N/A
   linux-backports-modules-5.0.0-36-generic  N/A
   linux-firmware1.183.2
  Tags:  eoan
  Uname: Linux 5.0.0-36-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-18 (0 days ago)
  UserGroups: adm audio cdrom dialout dip kvm lpadmin plugdev pulse sambashare 
sudo video
  _MarkForUpload: True
  dmi.bios.date: 07/30/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.11.2
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.11.2:bd07/30/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9550
  dmi.product.sku: 06E4
  dmi.sys.vendor: Dell Inc.

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