[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension

[Kai-Heng Feng]

rtimai, is it possible for you to file a new bug?

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

Title:
  r8169 ethernet card don't work after returning from suspension

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

Bug description:
  ===SRU Justification===
  [Impact]
  Ethernet r8169 stops working after system resumed from suspend.

  [Test]
  User confirmed these patches fix the issue. r8169 continues to work
  after resume from suspend.

  [Regression Potential]
  Medium. The fix is limited to one device, all patches are in mainline.
  The WOL default change might cause regression for users that depend on
  BIOS settings. We can advice them to use userspace tool (systemd,
  ethtool, etc.) instead.

  ===Original Bug Report===
  I have noticed that the network stopped working on my desktop after I've 
suspended the system and woke it up. On dmesg there are messages like:

  [  150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready
  [  150.944101] do_IRQ: 3.37 No irq handler for vector
  [  150.944105] r8169 :01:00.0 enp1s0: link down
  [  150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready

  When using Xenial (from a different install), this problem is not
  happening. This is happening on Bionic.

  There are only two ways to restore connectivity:
  1) Reboot the system;
  2) Remove the r8169 module and reinsert it with modprobe.

  The motherboard is a AsRock H55M-LE and the Ethernet controller is:

  01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
  RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-firmware 1.172
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Fri Mar  2 00:21:57 2018
  Dependencies:

  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  PackageArchitecture: all
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-10-generic.
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  usuario1153 F pulseaudio
   /dev/snd/controlC1:  usuario1153 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26'
     Mixer name : 'VIA VT1818S'
     Components : 'HDA:11060440,18492818,0010'
     Controls  : 40
     Simple ctrls  : 17
  Card1.Amixer.info:
   Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27'
     Mixer name : 'ATI R6xx HDMI'
     Components : 'HDA:1002aa01,00aa0100,00100200'
     Controls  : 7
     Simple ctrls  : 1
  Card1.Amixer.values:
   Simple mixer control 'IEC958',0
     Capabilities: pswitch pswitch-joined
     Playback channels: Mono
     Mono: Playback [on]
  CurrentDesktop: LXDE
  Dependencies:

  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f
  InstallationDate: Installed on 2018-02-26 (3 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: linux-firmware 1.172
  PackageArchitecture: all
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz 
root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-10-generic N/A
   linux-backports-modules-4.15.0-10-generic  N/A
   linux-firmware 1.172
  RfKill:

  Tags:  bionic
  Uname: Linux 4.15.0-10-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/20/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: H55M-LE
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/20/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH55M-LE:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By 

[Kernel-packages] [Bug 1760545] Re: [18.04] GLK hang after a while

[Kai-Heng Feng]

** Description changed:

  SRU Justification
  
- Impact: i915 lacks information about the glk_dmc_ver1_04.bin firmware
- file in modinfo, so it is not included in the initrd along with the i915
- driver. Thus the firmware does not get loaded. Loading the firmware is
- said to prevent a hang.
+ [Impact] 
+ i915 lacks information about the glk_dmc_ver1_04.bin firmware file in
+ modinfo, so it is not included in the initrd along with the i915 driver.
+ Thus the firmware does not get loaded. Loading the firmware is said to
+ prevent a hang.
  
- Fix: Add a MODULE_FIRMWARE statement for the firmware.
+ In addition to that, this also causes GLK's HDMI audio codec stops
+ working after S3.
+ 
+ [Fix]
+ Add a MODULE_FIRMWARE statement for the firmware.
+ 
+ This information is required to let initramfs-tools includes the
+ firmware.
  
- Test Case: Without the firmware there will be a "Direct firmware load
- for i915/glk_dmc_ver1_04.bin failed with error -2" line in dmesg. With
- the firmware there is no such message.
+ [Test Case]
+ Without the firmware there will be a "Direct firmware load for
+ i915/glk_dmc_ver1_04.bin failed with error -2" line in dmesg. With the
+ firmware there is no such message.
  
- Regression Potential: Minimal. Will only be loaded by i915 for specific
- hardware, and loading the firmware is known to fix a hang.
+ I can confirm the GLK HDMI audio issue is gone when firmware is loaded.
+ 
+ [Regression Potential]
+ Minimal. Will only be loaded by i915 for specific hardware, and loading
+ the firmware is known to fix a hang.
  
  ---
  
  Description:
  
  Platform information:
  Label: GLK02SDP
  Processor: Silver N5000
  Bios: GELKRVPA.X64.0083.B30.1801162142
  OS: Ubuntu 18.04
  Kernel: 4.15.0-10-generic
  
  Details:
  Power on, and enter into the system;
  After a period, sometimes about 20 minutes, sometimes 1 hour, the machine 
will hang.
  We can only power it off manually, then power on to enter into OS again.

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

Title:
  [18.04] GLK hang after a while

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  SRU Justification

  [Impact] 
  i915 lacks information about the glk_dmc_ver1_04.bin firmware file in
  modinfo, so it is not included in the initrd along with the i915 driver.
  Thus the firmware does not get loaded. Loading the firmware is said to
  prevent a hang.

  In addition to that, this also causes GLK's HDMI audio codec stops
  working after S3.
  
  [Fix]
  Add a MODULE_FIRMWARE statement for the firmware.
  
  This information is required to let initramfs-tools includes the
  firmware.

  [Test Case]
  Without the firmware there will be a "Direct firmware load for
  i915/glk_dmc_ver1_04.bin failed with error -2" line in dmesg. With the
  firmware there is no such message.

  I can confirm the GLK HDMI audio issue is gone when firmware is
  loaded.

  [Regression Potential]
  Minimal. Will only be loaded by i915 for specific hardware, and loading
  the firmware is known to fix a hang.

  ---

  Description:

  Platform information:
  Label: GLK02SDP
  Processor: Silver N5000
  Bios: GELKRVPA.X64.0083.B30.1801162142
  OS: Ubuntu 18.04
  Kernel: 4.15.0-10-generic

  Details:
  Power on, and enter into the system;
  After a period, sometimes about 20 minutes, sometimes 1 hour, the machine 
will hang.
  We can only power it off manually, then power on to enter into OS again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760545/+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 1782427] Re: package wireless-regdb 2018.05.09-0ubuntu1~16.04.1 failed to install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: wireless-regdb (Ubuntu)
   Status: New => Confirmed

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

Title:
  package wireless-regdb 2018.05.09-0ubuntu1~16.04.1 failed to
  install/upgrade: trying to overwrite
  '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also in package
  crda 3.18-1build1

Status in wireless-regdb package in Ubuntu:
  Confirmed

Bug description:
  Every time I start system, this error appears

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: wireless-regdb 2018.05.09-0ubuntu1~16.04.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Jul 13 22:41:15 2018
  Dependencies:
   
  DuplicateSignature:
   package:wireless-regdb:2018.05.09-0ubuntu1~16.04.1
   Unpacking wireless-regdb (2018.05.09-0ubuntu1~16.04.1) over 
(2016.06.10-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-Sc51aa/5-wireless-regdb_2018.05.09-0ubuntu1~16.04.1_all.deb
 (--unpack):
trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', which is also 
in package crda 3.18-1build1
  ErrorMessage: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', 
which is also in package crda 3.18-1build1
  InstallationDate: Installed on 2018-04-27 (82 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: wireless-regdb
  Title: package wireless-regdb 2018.05.09-0ubuntu1~16.04.1 failed to 
install/upgrade: trying to overwrite '/lib/crda/pubkeys/sforshee.key.pub.pem', 
which is also in package crda 3.18-1build1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wireless-regdb/+bug/1782427/+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 1785363] Re: Error in Booting

[Daniel van Vugt]

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Expired => New

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

Title:
  Error in Booting

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  When i change my default graphics driver as Nvidia then it's not start
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Aug  4 09:59:11 2018
  DistUpgraded: 2018-06-18 22:25:36,929 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-23-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:397d]
   NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GF119M [GeForce GT 520M] [17aa:397d]
  MachineType: LENOVO HuronRiver Platform
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=976f64eb-604f-4770-b36c-2efb3dae6ef1 ro quiet splash 
acpi_backlight=none vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-06-18 (46 days ago)
  dmi.bios.date: 10/21/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 45CN38WW
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Emerald Lake
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnLENOVO:bvr45CN38WW:bd10/21/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: HuronRiver Platform
  dmi.product.version: Ideapad Z570
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Mon Jun 18 23:25:54 2018
  xserver.configfile: default
  xserver.errors: Failed to initialize GLX extension (Compatible NVIDIA X 
driver not found)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16560 
   vendor LEN
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1785363/+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 1793997] Re: iwlwifi 0000:04:00.0: Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a

[Yura Pakhuchiy]

Joseph do you need any more information? Any ideas to try?

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

Title:
  iwlwifi :04:00.0: Queue 10 is active on fifo 2 and stuck for 1
  ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  Every few days iwlwifi decides to stop working. Only recourse is
  restart.

  From syslog:

  Sep 24 11:42:10 bonobo kernel: [109525.538612] iwlwifi :04:00.0: iwlwifi 
transaction failed, dumping registers
  Sep 24 11:42:10 bonobo kernel: [109525.538622] iwlwifi :04:00.0: iwlwifi 
device config registers:
  Sep 24 11:42:10 bonobo kernel: [109525.538669] iwlwifi :04:00.0: 
: 08b18086 0010 028000bb  0004   

  Sep 24 11:42:10 bonobo kernel: [109525.538674] iwlwifi :04:00.0: 
0020:    40708086  00c8  
0100
  Sep 24 11:42:10 bonobo kernel: [109525.538677] iwlwifi :04:00.0: iwlwifi 
device memory mapped registers:
  Sep 24 11:42:10 bonobo kernel: [109525.538709] iwlwifi :04:00.0: 
:        

  Sep 24 11:42:10 bonobo kernel: [109525.538713] iwlwifi :04:00.0: 
0020:        

  Sep 24 11:42:10 bonobo kernel: [109525.538719] iwlwifi :04:00.0: iwlwifi 
device AER capability structure:
  Sep 24 11:42:10 bonobo kernel: [109525.538746] iwlwifi :04:00.0: 
: 14010001 0010  00462031 3141 2000 0014 
4001
  Sep 24 11:42:10 bonobo kernel: [109525.538749] iwlwifi :04:00.0: 
0020: 000f ec100460 
  Sep 24 11:42:10 bonobo kernel: [109525.538752] iwlwifi :04:00.0: iwlwifi 
parent port (:00:1c.3) config registers:
  Sep 24 11:42:10 bonobo kernel: [109525.538775] iwlwifi :00:1c.3: 
: 8c168086 0017 060400d5 00810010   00040400 
20f0
  Sep 24 11:42:10 bonobo kernel: [109525.538779] iwlwifi :00:1c.3: 
0020: ec10ec10 0001fff1    0040  
00100405
  Sep 24 11:42:10 bonobo kernel: [109525.538784] [ cut here 
]
  Sep 24 11:42:10 bonobo kernel: [109525.538785] Timeout waiting for hardware 
access (CSR_GP_CNTRL 0x)
  Sep 24 11:42:10 bonobo kernel: [109525.538842] WARNING: CPU: 5 PID: 0 at 
/build/linux-SlLHxe/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1973
 iwl_trans_pcie_grab_nic_access+0xea/0xf0 [iwlwifi]
  Sep 24 11:42:10 bonobo kernel: [109525.538843] Modules linked in: 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache rfcomm ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_comment vmnet(OE) pci_stub 
vmw_vsock_vmci_transport vsock xfrm_user vboxpci(OE) vmw_vmci xfrm4_tunnel 
tunnel4 vboxnetadp(OE) ipcomp xfrm_ipcomp vmmon(OE) vboxnetflt(OE) esp4 
vboxdrv(OE) ah4 af_key xfrm_algo ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
devlink iptable_filter cmac bnep ec_sys binfmt_misc zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) algif_skcipher af_alg dm_crypt 
intel_rapl x86_pkg_temp_thermal
  Sep 24 11:42:10 bonobo kernel: [109525.538898]  intel_powerclamp coretemp 
kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_hda_codec_hdmi arc4 
intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm 
btusb btrtl snd_seq_midi btbcm snd_seq_midi_event btintel uvcvideo 
intel_rapl_perf bluetooth serio_raw snd_rawmidi videobuf2_vmalloc iwlmvm 
mxm_wmi mac80211 rtsx_pci_ms videobuf2_memops ecdh_generic input_leds iwlwifi 
snd_seq videobuf2_v4l2 memstick videobuf2_core cfg80211 snd_seq_device videodev 
snd_timer media joydev snd mei_me soundcore nvidia_uvm(POE) mei mac_hid 
ie31200_edac shpchp lpc_ich wmi_bmof sch_fq_codel parport_pc ppdev sunrpc lp 
parport ip_tables
  Sep 24 11:42:10 bonobo kernel: [109525.538952]  x_tables autofs4 btrfs xor 
zstd_compress raid6_pq dm_mirror dm_region_hash dm_log hid_generic usbhid hid 
nvidia_drm(POE) nvidia_modeset(POE) rtsx_pci_sdmmc nvidia(POE) drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm rtsx_pci psmouse ahci r8169 
libahci ipmi_devintf mii ipmi_msghandler video wmi
  Sep 24 11:42:10 bonobo kernel: [109525.538982] CPU: 5 PID: 0 Comm: swapper/5 
Tainted: P   OE4.15.0-34-generic #37-Ubuntu
  Sep 24 11:42:10 bonobo kernel: [109525.538983] Hardware name: 

[Kernel-packages] [Bug 1794922] Re: lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci 0000:00:a.7: dma_direct_map_sg: overflow 0x000000016e3f3000+2048 of device mask ffffffff" repeats

[Walter Lapchynski]

Maybe installing in a virtual machine might be good idea?

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

Title:
  lubuntu 18.10 x86 (32bit) image fails to load "ehci-pci :00:a.7:
  dma_direct_map_sg: overflow 0x00016e3f3000+2048 of device mask
  " repeats

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

Bug description:
  -- Background --
  Testing the x86 (32bit) ISO image on various machines.

  After zsync download, the thumb-drive is tested ("check disk for
  defects") & passes; and worked fine on two systems today (dell d610 &
  hp dx6120), however

  -- Issue --

  dell 755 (desktop) & hp dc7700 (small form factor) it just sits at
  lubuntu plymouth screen.

  switching to messages, it's just the following repeating

  // on dell 755
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x00016e3f3000+2048 
of device mask "

  // on hp dc7700
  "ehci-pci :00:1a.7: dma_direct_map_sg: overflow 0x000162317000+2048 
of device mask "

  NOTE:  I can't copy/paste from systems, as it never completes boot; I
  left it >30mins (on 755) & it just kept repeating message. I've
  manually typed it; so typo's could have been made.

  A discussion on #lubuntu-devel provided a possible cause (Thank you
  Walter!) -

  ---
   guiverc: lyorian: 
http://debian.2.n7.nabble.com/Bug-908924-dma-direct-map-sg-overflow-on-USB-access-after-upgrade-to-kernel-4-18-td4387757.html
   seems like it's a usb issue of some kind with 4.18
  ---

  This fits because whilst I do my testing mostly on d610 & t43 (no
  issues today), I'd tested Lubuntu 18.10 before on the dell 755 with no
  issues.  My last test was also long enough ago to be on 4.17 kernel.

  I'll add `lshw` files for the two failed systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794922/+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 1793111] Re: [Asus UX331UAL] Touchpad events become slow and laggy

[Kai-Heng Feng]

Not really.
So I think what I am working on and what you've been seeing are two different 
bugs.

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

Title:
  [Asus UX331UAL] Touchpad events become slow and laggy

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  My laptop's touchpad starts fast and smooth:

  ELAN1200:00 04F3:309C Touchpad: Latest   142Hz, Average   141Hz
  ELAN1200:00 04F3:309C Touchpad: Latest   142Hz, Average   141Hz
  ELAN1200:00 04F3:309C Touchpad: Latest   142Hz, Average   141Hz

  But after holding one finger down (click) and moving a second finger,
  the stream of events from the kernel slows way down:

  ELAN1200:00 04F3:309C Touchpad: Latest35Hz, Average47Hz
  ELAN1200:00 04F3:309C Touchpad: Latest47Hz, Average47Hz
  ELAN1200:00 04F3:309C Touchpad: Latest47Hz, Average47Hz
  ELAN1200:00 04F3:309C Touchpad: Latest27Hz, Average46Hz

  which is very noticeable on screen. Those measurements are from:
  https://gitlab.com/iankelling/evhz but the problem was very obvious on
  the desktop before that.

  After a while, seemingly randomly, the touchpad will eventually return
  to the full speed :/

  Possibly related, but maybe not since it's at different times, the
  kernel says:

  [ 8191.785882] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report 
(16/65535)
  [ 8256.953046] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report 
(16/65535)
  [ 8261.013145] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report 
(16/65535)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dan1886 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 18 11:56:14 2018
  InstallationDate: Installed on 2018-09-11 (6 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 8087:0a2b Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook 13 UX331UAL
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX331UAL.305
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX331UAL
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX331UAL.305:bd03/02/2018:svnASUSTeKCOMPUTERINC.:pnZenBook13UX331UAL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX331UAL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook 13 UX331UAL
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793111/+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 1793997] Re: iwlwifi 0000:04:00.0: Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a

[Yura Pakhuchiy]

In my case crash can happen on freshly booted system as well. And it is
more likely to happen when I'm using Wi-Fi actively, although it
sometimes happens even if I barely use Wi-Fi (eg. I'm connected via
ethernet cable and Wi-Fi at the same time and routing is configured to
use the cable).

@berend have you tried replacing the card?

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

Title:
  iwlwifi :04:00.0: Queue 10 is active on fifo 2 and stuck for 1
  ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  Every few days iwlwifi decides to stop working. Only recourse is
  restart.

  From syslog:

  Sep 24 11:42:10 bonobo kernel: [109525.538612] iwlwifi :04:00.0: iwlwifi 
transaction failed, dumping registers
  Sep 24 11:42:10 bonobo kernel: [109525.538622] iwlwifi :04:00.0: iwlwifi 
device config registers:
  Sep 24 11:42:10 bonobo kernel: [109525.538669] iwlwifi :04:00.0: 
: 08b18086 0010 028000bb  0004   

  Sep 24 11:42:10 bonobo kernel: [109525.538674] iwlwifi :04:00.0: 
0020:    40708086  00c8  
0100
  Sep 24 11:42:10 bonobo kernel: [109525.538677] iwlwifi :04:00.0: iwlwifi 
device memory mapped registers:
  Sep 24 11:42:10 bonobo kernel: [109525.538709] iwlwifi :04:00.0: 
:        

  Sep 24 11:42:10 bonobo kernel: [109525.538713] iwlwifi :04:00.0: 
0020:        

  Sep 24 11:42:10 bonobo kernel: [109525.538719] iwlwifi :04:00.0: iwlwifi 
device AER capability structure:
  Sep 24 11:42:10 bonobo kernel: [109525.538746] iwlwifi :04:00.0: 
: 14010001 0010  00462031 3141 2000 0014 
4001
  Sep 24 11:42:10 bonobo kernel: [109525.538749] iwlwifi :04:00.0: 
0020: 000f ec100460 
  Sep 24 11:42:10 bonobo kernel: [109525.538752] iwlwifi :04:00.0: iwlwifi 
parent port (:00:1c.3) config registers:
  Sep 24 11:42:10 bonobo kernel: [109525.538775] iwlwifi :00:1c.3: 
: 8c168086 0017 060400d5 00810010   00040400 
20f0
  Sep 24 11:42:10 bonobo kernel: [109525.538779] iwlwifi :00:1c.3: 
0020: ec10ec10 0001fff1    0040  
00100405
  Sep 24 11:42:10 bonobo kernel: [109525.538784] [ cut here 
]
  Sep 24 11:42:10 bonobo kernel: [109525.538785] Timeout waiting for hardware 
access (CSR_GP_CNTRL 0x)
  Sep 24 11:42:10 bonobo kernel: [109525.538842] WARNING: CPU: 5 PID: 0 at 
/build/linux-SlLHxe/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1973
 iwl_trans_pcie_grab_nic_access+0xea/0xf0 [iwlwifi]
  Sep 24 11:42:10 bonobo kernel: [109525.538843] Modules linked in: 
rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace fscache rfcomm ip6table_nat 
nf_conntrack_ipv6 nf_defrag_ipv6 nf_nat_ipv6 xt_comment vmnet(OE) pci_stub 
vmw_vsock_vmci_transport vsock xfrm_user vboxpci(OE) vmw_vmci xfrm4_tunnel 
tunnel4 vboxnetadp(OE) ipcomp xfrm_ipcomp vmmon(OE) vboxnetflt(OE) esp4 
vboxdrv(OE) ah4 af_key xfrm_algo ccm xt_CHECKSUM iptable_mangle ipt_MASQUERADE 
nf_nat_masquerade_ipv4 iptable_nat nf_nat_ipv4 nf_nat nf_conntrack_ipv4 
nf_defrag_ipv4 xt_conntrack nf_conntrack libcrc32c ipt_REJECT nf_reject_ipv4 
xt_tcpudp bridge stp llc ebtable_filter ebtables ip6table_filter ip6_tables 
devlink iptable_filter cmac bnep ec_sys binfmt_misc zfs(PO) zunicode(PO) 
zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) algif_skcipher af_alg dm_crypt 
intel_rapl x86_pkg_temp_thermal
  Sep 24 11:42:10 bonobo kernel: [109525.538898]  intel_powerclamp coretemp 
kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc 
aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_hda_codec_hdmi arc4 
intel_cstate snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel 
snd_hda_codec snd_usb_audio snd_hda_core snd_usbmidi_lib snd_hwdep snd_pcm 
btusb btrtl snd_seq_midi btbcm snd_seq_midi_event btintel uvcvideo 
intel_rapl_perf bluetooth serio_raw snd_rawmidi videobuf2_vmalloc iwlmvm 
mxm_wmi mac80211 rtsx_pci_ms videobuf2_memops ecdh_generic input_leds iwlwifi 
snd_seq videobuf2_v4l2 memstick videobuf2_core cfg80211 snd_seq_device videodev 
snd_timer media joydev snd mei_me soundcore nvidia_uvm(POE) mei mac_hid 
ie31200_edac shpchp lpc_ich wmi_bmof sch_fq_codel parport_pc ppdev sunrpc lp 
parport ip_tables
  Sep 24 11:42:10 bonobo kernel: [109525.538952]  x_tables autofs4 btrfs xor 
zstd_compress raid6_pq dm_mirror dm_region_hash dm_log hid_generic usbhid hid 
nvidia_drm(POE) nvidia_modeset(POE) rtsx_pci_sdmmc nvidia(POE) drm_kms_helper 
syscopyarea sysfillrect sysimgblt fb_sys_fops drm 

[Kernel-packages] [Bug 1795292] Re: ELAN469D touch pad not working

[Patrick Van Oosterwijck]

Upstream kernel 4.19.0-rc7 doesn't help either.
Anyone working on this?

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

Title:
  ELAN469D touch pad not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I installed Bionic Beaver and now upgraded to Cosmic Cuttlefish on
  this Lenovo Ideapad 330S-15ARR laptop.  The touch pad doesn't work in
  either.

  Some possibly relevant info from dmesg:
  i2c_hid i2c-ELAN469D:00: i2c-ELAN469D:00 supply vdd not found, using dummy 
regulator
  i2c_designware AMDI0010:01: controller timed out

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-7-generic 4.18.0-7.8
  ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
  Uname: Linux 4.18.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xorbit 2086 F pulseaudio
   /dev/snd/pcmC1D0p:   xorbit 2086 F...m pulseaudio
   /dev/snd/controlC0:  xorbit 2086 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Sep 30 23:14:26 2018
  InstallationDate: Installed on 2018-09-20 (10 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 81FB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-7-generic 
root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic processor.max_cstate=1 
rcu_nocbs=0-7 pcie_aspm=off pci=noaer quiet splash vt.handoff=1 
elan_i2c.dyndbg=+p
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-7-generic N/A
   linux-backports-modules-4.18.0-7-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (0 days ago)
  dmi.bios.date: 06/08/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WCN22WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330S-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WCN22WW:bd06/08/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:
  dmi.product.family: ideapad 330S-15ARR
  dmi.product.name: 81FB
  dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR
  dmi.product.version: Lenovo ideapad 330S-15ARR
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-09-20 (13 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Tags:  cosmic
  Uname: Linux 4.19.0-041900rc6-generic x86_64
  UnreportableReason: The running kernel is not an Ubuntu kernel
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (2 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795292/+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 1796355] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1796355

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  USB-C ValueLine network adapter fails to connect

Status in linux package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  The adapter I'm trying to use using is a 'Valueline' USB-C adapter,
  with no external identifying information. lsusb lists it as

  Bus 004 Device 022: ID 0bda:8153 Realtek Semiconductor Corp.

  It works fine on a Windows 10 system (same hardware platform), where
  it's identified as a 10/100/1000 Realtek adapter.

  When I connect it to my system (Asus Zenbook UX490UA) internal lights
  go on, but no connection is produced.  The network icon (upper right)
  is shown briefly, then disappears, the is show, then disappears.
  After some time it seems to give up.

  Kernel logs show repeated occurrences of:

  Oct  5 17:02:22 athasus kernel: [  317.843590] usb 4-2: new SuperSpeed USB 
device number 121 using xhci_hcd
  Oct  5 17:02:22 athasus kernel: [  317.863719] usb 4-2: New USB device found, 
idVendor=0bda, idProduct=8153
  Oct  5 17:02:22 athasus kernel: [  317.863728] usb 4-2: New USB device 
strings: Mfr=1, Product=2, SerialNumber=6
  Oct  5 17:02:22 athasus kernel: [  317.863735] usb 4-2: Product: USB 
10/100/1000 LAN
  Oct  5 17:02:22 athasus kernel: [  317.863741] usb 4-2: Manufacturer: Realtek
  Oct  5 17:02:22 athasus kernel: [  317.863745] usb 4-2: SerialNumber: 
0100
  Oct  5 17:02:22 athasus kernel: [  318.000268] usb 4-2: reset SuperSpeed USB 
device number 121 using xhci_hcd
  Oct  5 17:02:22 athasus kernel: [  318.057875] r8152 4-2:1.0 eth0: v1.09.9
  Oct  5 17:02:22 athasus kernel: [  318.138042] r8152 4-2:1.0 enxa0cec809bf58: 
renamed from eth0
  Oct  5 17:02:22 athasus kernel: [  318.170397] IPv6: ADDRCONF(NETDEV_UP): 
enxa0cec809bf58: link is not ready
  Oct  5 17:02:22 athasus kernel: [  318.176359] IPv6: ADDRCONF(NETDEV_UP): 
enxa0cec809bf58: link is not ready
  Oct  5 17:02:22 athasus kernel: [  318.354745] r8152 4-2:1.0 enxa0cec809bf58: 
Stop submitting intr, status -71
  Oct  5 17:02:22 athasus kernel: [  318.543737] usb 4-2: USB disconnect, 
device number 121

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  5 17:35:17 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-10-03 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 172.16.4.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   172.16.4.0/24 dev wlp2s0 proto kernel scope link src 172.16.4.102 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   TIMESTAMP-REAL 
   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH  
   SLAVE 
   ATH   79577e92-4b01-46c4-bbff-2088aaf0750a  wifi  1538753528  fre  5 okt 
2018 17:32:08  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  ATH  
   79577e92-4b01-46c4-bbff-2088aaf0750a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW 

[Kernel-packages] [Bug 1796580] Re: Touchscreen breaks after suspend on Acer Aspire Switch 11

[Timo Aaltonen]

you could try installing newer mainline kernels to see if they help

http://kernel.ubuntu.com/~kernel-ppa/mainline/

** Package changed: xinput (Ubuntu) => linux (Ubuntu)

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

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

Title:
  Touchscreen breaks after suspend on Acer Aspire Switch 11

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I'm not entirely sure this bug belongs in package xinput, but I'm
  following the lead of
  https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1275416, which
  describes the same symptoms (but on other hardware, so likely a
  different underlying problem).

  On this notebook, the touchscreen works well out of the box. But as
  soon as I suspend (by pressing the power button or closing the lid)
  and resume again, the touch screen no longer works. Kernel and Xorg
  logs show no indication of any problem, xinput still lists the
  touchscreen, but it just no longer works.

  The touchscreen can be made to work again by reloading the
  hid_multitouch module (that works by unloading and reloading after a
  resume, or by unloading the module before suspend and reloading it
  after resume).

  I tried updating the bios from v1.03 to the latest v1.04 (no changelog
  available), but that did not change the problem.

  I'm attaching a dmesg.txt in addition to the stuff ubuntu-bug
  collected. In this dmesg log, I've shown a full boot, a suspend
  (breaking the touchscreen), a module reload (fixing the touchscreen),
  then a module unload, suspend and module reload, after which the
  touchscreen also works (I've added annotations to the log to indicate
  what happens when). The log also shows some USB-related errors after
  suspend, but that seems to be about the bluetooth adapter (looking at
  the usb ids), so I think these are unrelated.

  The touchscreen in question seems to be connected through I2c,
  according to dmesg:

  [4.561527] input: SYNA7508:00 06CB:77B2 Pen as 
/devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input8
  [4.561741] input: SYNA7508:00 06CB:77B2 as 
/devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input9
  [4.561917] hid-multitouch 0018:06CB:77B2.0002: input,hidraw1: I2C HID 
v1.00 Mouse [SYNA7508:00 06CB:77B2] on i2c-SYNA7508:00

  I realize that this is not enough information to diagnose and fix the
  problem, but I'd gladly receive some suggestions on debug strategies
  to dig into this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xinput 1.6.2-1build1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 19:40:05 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:0a1e] (rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Device [1025:0930]
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Acer Aspire SW5-171P
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=4893a2e6-84af-4d45-8e31-773e622c36c6 ro quiet splash vt.handoff=1
  SourcePackage: xinput
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/7/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Longchamp_S
  dmi.board.vendor: Acer
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd11/7/2014:svnAcer:pnAspireSW5-171P:pvrV1.04:rvnAcer:rnLongchamp_S:rvrV1.04:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.family: Haswell-Y System
  dmi.product.name: Aspire SW5-171P
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  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

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

-- 
Mailing list: 

[Kernel-packages] [Bug 1796580] [NEW] Touchscreen breaks after suspend on Acer Aspire Switch 11

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I'm not entirely sure this bug belongs in package xinput, but I'm
following the lead of
https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1275416, which
describes the same symptoms (but on other hardware, so likely a
different underlying problem).

On this notebook, the touchscreen works well out of the box. But as soon
as I suspend (by pressing the power button or closing the lid) and
resume again, the touch screen no longer works. Kernel and Xorg logs
show no indication of any problem, xinput still lists the touchscreen,
but it just no longer works.

The touchscreen can be made to work again by reloading the
hid_multitouch module (that works by unloading and reloading after a
resume, or by unloading the module before suspend and reloading it after
resume).

I tried updating the bios from v1.03 to the latest v1.04 (no changelog
available), but that did not change the problem.

I'm attaching a dmesg.txt in addition to the stuff ubuntu-bug collected.
In this dmesg log, I've shown a full boot, a suspend (breaking the
touchscreen), a module reload (fixing the touchscreen), then a module
unload, suspend and module reload, after which the touchscreen also
works (I've added annotations to the log to indicate what happens when).
The log also shows some USB-related errors after suspend, but that seems
to be about the bluetooth adapter (looking at the usb ids), so I think
these are unrelated.

The touchscreen in question seems to be connected through I2c, according
to dmesg:

[4.561527] input: SYNA7508:00 06CB:77B2 Pen as 
/devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input8
[4.561741] input: SYNA7508:00 06CB:77B2 as 
/devices/pci:00/INT33C3:00/i2c-1/i2c-SYNA7508:00/0018:06CB:77B2.0002/input/input9
[4.561917] hid-multitouch 0018:06CB:77B2.0002: input,hidraw1: I2C HID v1.00 
Mouse [SYNA7508:00 06CB:77B2] on i2c-SYNA7508:00

I realize that this is not enough information to diagnose and fix the
problem, but I'd gladly receive some suggestions on debug strategies to
dig into this issue.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xinput 1.6.2-1build1
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct  7 19:40:05 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Device [8086:0a1e] (rev 0b) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:0930]
InstallationDate: Installed on 2018-10-06 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Acer Aspire SW5-171P
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=UUID=4893a2e6-84af-4d45-8e31-773e622c36c6 ro quiet splash vt.handoff=1
SourcePackage: xinput
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/7/2014
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Longchamp_S
dmi.board.vendor: Acer
dmi.board.version: V1.04
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd11/7/2014:svnAcer:pnAspireSW5-171P:pvrV1.04:rvnAcer:rnLongchamp_S:rvrV1.04:cvnAcer:ct10:cvrChassisVersion:
dmi.product.family: Haswell-Y System
dmi.product.name: Aspire SW5-171P
dmi.product.version: V1.04
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
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

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


** Tags: amd64 apport-bug bionic ubuntu
-- 
Touchscreen breaks after suspend on Acer Aspire Switch 11
https://bugs.launchpad.net/bugs/1796580
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

-- 
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 1796355] Re: USB-C ValueLine network adapter fails to connect

[Kai-Heng Feng]

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

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

Title:
  USB-C ValueLine network adapter fails to connect

Status in linux package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  The adapter I'm trying to use using is a 'Valueline' USB-C adapter,
  with no external identifying information. lsusb lists it as

  Bus 004 Device 022: ID 0bda:8153 Realtek Semiconductor Corp.

  It works fine on a Windows 10 system (same hardware platform), where
  it's identified as a 10/100/1000 Realtek adapter.

  When I connect it to my system (Asus Zenbook UX490UA) internal lights
  go on, but no connection is produced.  The network icon (upper right)
  is shown briefly, then disappears, the is show, then disappears.
  After some time it seems to give up.

  Kernel logs show repeated occurrences of:

  Oct  5 17:02:22 athasus kernel: [  317.843590] usb 4-2: new SuperSpeed USB 
device number 121 using xhci_hcd
  Oct  5 17:02:22 athasus kernel: [  317.863719] usb 4-2: New USB device found, 
idVendor=0bda, idProduct=8153
  Oct  5 17:02:22 athasus kernel: [  317.863728] usb 4-2: New USB device 
strings: Mfr=1, Product=2, SerialNumber=6
  Oct  5 17:02:22 athasus kernel: [  317.863735] usb 4-2: Product: USB 
10/100/1000 LAN
  Oct  5 17:02:22 athasus kernel: [  317.863741] usb 4-2: Manufacturer: Realtek
  Oct  5 17:02:22 athasus kernel: [  317.863745] usb 4-2: SerialNumber: 
0100
  Oct  5 17:02:22 athasus kernel: [  318.000268] usb 4-2: reset SuperSpeed USB 
device number 121 using xhci_hcd
  Oct  5 17:02:22 athasus kernel: [  318.057875] r8152 4-2:1.0 eth0: v1.09.9
  Oct  5 17:02:22 athasus kernel: [  318.138042] r8152 4-2:1.0 enxa0cec809bf58: 
renamed from eth0
  Oct  5 17:02:22 athasus kernel: [  318.170397] IPv6: ADDRCONF(NETDEV_UP): 
enxa0cec809bf58: link is not ready
  Oct  5 17:02:22 athasus kernel: [  318.176359] IPv6: ADDRCONF(NETDEV_UP): 
enxa0cec809bf58: link is not ready
  Oct  5 17:02:22 athasus kernel: [  318.354745] r8152 4-2:1.0 enxa0cec809bf58: 
Stop submitting intr, status -71
  Oct  5 17:02:22 athasus kernel: [  318.543737] usb 4-2: USB disconnect, 
device number 121

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  5 17:35:17 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-10-03 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 172.16.4.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   172.16.4.0/24 dev wlp2s0 proto kernel scope link src 172.16.4.102 metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID  TYPE  TIMESTAMP   TIMESTAMP-REAL 
   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
ACTIVE  DEVICE  STATE  ACTIVE-PATH  
   SLAVE 
   ATH   79577e92-4b01-46c4-bbff-2088aaf0750a  wifi  1538753528  fre  5 okt 
2018 17:32:08  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp2s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  ATH  
   79577e92-4b01-46c4-bbff-2088aaf0750a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796355/+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 1785363] Re: Error in Booting

[Launchpad Bug Tracker]

[Expired for nvidia-graphics-drivers-390 (Ubuntu) because there has been
no activity for 60 days.]

** Changed in: nvidia-graphics-drivers-390 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Error in Booting

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Expired

Bug description:
  When i change my default graphics driver as Nvidia then it's not start
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sat Aug  4 09:59:11 2018
  DistUpgraded: 2018-06-18 22:25:36,929 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-23-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-29-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-29-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:397d]
   NVIDIA Corporation GF119M [GeForce GT 520M] [10de:1050] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GF119M [GeForce GT 520M] [17aa:397d]
  MachineType: LENOVO HuronRiver Platform
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-29-generic 
root=UUID=976f64eb-604f-4770-b36c-2efb3dae6ef1 ro quiet splash 
acpi_backlight=none vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-06-18 (46 days ago)
  dmi.bios.date: 10/21/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 45CN38WW
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Emerald Lake
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnLENOVO:bvr45CN38WW:bd10/21/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
  dmi.product.family: HuronRiver System
  dmi.product.name: HuronRiver Platform
  dmi.product.version: Ideapad Z570
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  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
  xserver.bootTime: Mon Jun 18 23:25:54 2018
  xserver.configfile: default
  xserver.errors: Failed to initialize GLX extension (Compatible NVIDIA X 
driver not found)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16560 
   vendor LEN
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1785363/+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 1796553] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

** Changed in: linux (Ubuntu)
   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/1796553

Title:
  BT mouse getting reset during operation

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  
  (note: It's unclear to me if that's a kernel regression or an issue with 
bluez)

  
  I've been using this particular combination of Bluetooth mouse ("TECKNET 
BM306") & laptop ("Dell Latitude E7240") for over a year now.

  It used to work with 18.04 and 17.10, but with 18.10 I'm encountering
  a strange disconnect behaviour:

  1) Mouse is working ok
  2) Mouse suddenly stops
  3) Disabling and enabling bluetooth on the laptop makes the mouse work again.

  when this happens, dmesg reports:

  [57812.977570] usb 1-1.3: reset full-speed USB device number 18 using
  ehci-pci

  Disabling bluetooth and enabling it again results in:

  [57833.455866] usb 1-1.3: USB disconnect, device number 18
  [57833.455948] Bluetooth: hci0: turning off Intel device LED failed (-19)
  [57836.905656] usb 1-1.3: new full-speed USB device number 19 using ehci-pci
  [57837.016248] usb 1-1.3: New USB device found, idVendor=8087, 
idProduct=07dc, bcdDevice= 0.01
  [57837.016253] usb 1-1.3: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
  [57837.030092] Bluetooth: hci0: read Intel version: 370710018002030d00
  [57837.030169] Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
  [57837.251206] Bluetooth: hci0: Intel firmware patch completed and activated
  [57841.724368] hid-generic 0005:0A5C:0001.001F: unknown main item tag 0x0
  [57841.724587] input: TECKNET BM306 Mouse as 
/devices/pci:00/:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:256/0005:0A5C:0001.001F/input/input78
  [57841.724873] hid-generic 0005:0A5C:0001.001F: input,hidraw0: BLUETOOTH HID 
v1.29 Mouse [TECKNET BM306] on fc:f8:ae:45:3c:05

  $ bluetoothctl --version
  bluetoothctl: 5.50

  $ hciconfig -a
  hci0: Type: Primary  Bus: USB
BD Address: FC:F8:AE:45:3C:05  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN 
RX bytes:52465 acl:3355 sco:0 events:222 errors:0
TX bytes:28384 acl:13 sco:0 commands:170 errors:0
Features: 0xff 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH HOLD SNIFF 
Link mode: SLAVE ACCEPT 
Name: 'ChromeLinux_AA14'
Class: 0x0c010c
Service Classes: Rendering, Capturing
Device Class: Computer, Laptop
HCI Version: 4.0 (0x6)  Revision: 0x500
LMP Version: 4.0 (0x6)  Subversion: 0x500
Manufacturer: Intel Corp. (2)

  $ bluetoothctl
  Agent registered
  [TECKNET BM306]# show
  Controller FC:F8:AE:45:3C:05 (public)
Name: humbaba
Alias: ChromeLinux_AA14
Class: 0x000c010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: no
  [TECKNET BM306]# devices
  Device 20:9B:A5:68:AE:67 SoundBuds Flow
  Device DC:2C:26:01:24:23 TECKNET BM306
  Device 88:71:E5:0E:6B:99 Echo-HPT
  Device 00:0B:E4:A0:A2:14 Nokia BH-103
  Device A8:96:75:8B:4F:49 Moto G5S Plus
  Device 00:02:5B:20:75:3C Trust SPK-02
  Device 88:75:98:F2:5C:9E NS9+
  Device 00:E0:4C:D5:E0:F5 SoundCore mini
  [TECKNET BM306]# info DC:2C:26:01:24:23
  Device DC:2C:26:01:24:23 (public)
Name: TECKNET BM306
Alias: TECKNET BM306
Class: 0x0580
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
Modalias: usb:v0A5Cp0001d0129

  
  $ rfkill list
  2: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
  3: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
  4: dell-wwan: Wireless WAN
Soft blocked: yes
  

[Kernel-packages] [Bug 1796608] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module failed to build [error: implicit declaration of function ‘init_timer’; did you mean ‘init_timer

[Daniel van Vugt]

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

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1757008, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Summary changed:

- bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module failed 
to build
+ bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module failed 
to build [error: implicit declaration of function ‘init_timer’; did you mean 
‘init_timers’?]

** This bug has been marked a duplicate of bug 1757008
   Broadcom wireless drivers failed to build [error: implicit declaration of 
function ‘init_timer’]

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

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module
  failed to build [error: implicit declaration of function ‘init_timer’;
  did you mean ‘init_timers’?]

Status in bcmwl package in Ubuntu:
  New

Bug description:
  package will not load

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-29-generic
  Date: Sun Oct  7 21:26:55 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu8:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:2358:2:
 error: implicit declaration of function ‘init_timer’; did you mean 
‘init_timers’? [-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2018-10-05 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu8
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1796608/+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 1788807] Re: Bluetooth device not detected after resume from suspend [Qualcomm Atheros QCA9565]

[Daniel van Vugt]

Please:

1. Reboot so as to start a fresh kernel log.

2. Reproduce the bug (suspend and resume).

3. Run:  dmesg > dmesg.txt

4. Attach the file 'dmesg.txt' to this bug.

** Changed in: bluez (Ubuntu)
   Status: New => Incomplete

** Changed in: gnome-bluetooth (Ubuntu)
   Status: New => Incomplete

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

Title:
  Bluetooth device not detected after resume from suspend [Qualcomm
  Atheros QCA9565]

Status in bluez package in Ubuntu:
  Incomplete
Status in gnome-bluetooth package in Ubuntu:
  Incomplete

Bug description:
  When I suspend my laptop, it often happens that the bluetooth stops
  working. From gnome settings it is shown like if I had no bluetooth
  device at all.

  $ lspci -nnk | grep -iA3 net; lsusb; rfkill list; uname -r; dmesg | egrep -i 
'blue|firm'
  03:00.0 Network controller [0280]: Qualcomm Atheros QCA9565 / AR9565 Wireless 
Network Adapter [168c:0036] (rev 01)
Subsystem: AzureWave QCA9565 / AR9565 Wireless Network Adapter 
[1a3b:2130]
Kernel driver in use: ath9k
Kernel modules: ath9k
  04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI 
Express Card Reader [10ec:5287] (rev 01)
  --
  04:00.1 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 12)
Subsystem: ASUSTeK Computer Inc. RTL8111/8168/8411 PCI Express Gigabit 
Ethernet Controller [1043:200f]
Kernel driver in use: r8169
Kernel modules: r8169
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0bda:57b4 Realtek Semiconductor Corp. 
  Bus 001 Device 006: ID 13d3:3408 IMC Networks 
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  4.15.0-32-generic
  [0.024000] Spectre V2 : Enabling Restricted Speculation for firmware calls
  [0.048030] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
  [2.758768] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS
  [   35.407491] Bluetooth: Core ver 2.22
  [   35.407504] Bluetooth: HCI device and connection manager initialized
  [   35.407506] Bluetooth: HCI socket layer initialized
  [   35.407507] Bluetooth: L2CAP socket layer initialized
  [   35.407510] Bluetooth: SCO socket layer initialized
  [   53.501780] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   53.501780] Bluetooth: BNEP filters: protocol multicast
  [   53.501783] Bluetooth: BNEP socket layer initialized
  [   87.220137] Bluetooth: RFCOMM TTY layer initialized
  [   87.220143] Bluetooth: RFCOMM socket layer initialized
  [   87.220149] Bluetooth: RFCOMM ver 1.11
  [ 1675.503865] usb 1-5: device firmware changed
  [ 1681.095543] Bluetooth: Can't get version to change to load ram patch err
  [ 1681.095546] Bluetooth: Loading patch file failed
  [ 4105.994687] audit: type=1107 audit(1534926184.213:339): pid=1258 uid=105 
auid=4294967295 ses=4294967295 msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/" 
interface="org.freedesktop.DBus.ObjectManager" member="GetManagedObjects" 
mask="send" name="org.bluez" pid=10248 
label="snap.signal-desktop.signal-desktop" peer_pid=1314 peer_label="unconfined"


  Trying to use bluetooth from bluetoothctl
  $ bluetoothctl
  Agent registered
  [bluetooth]# scan on
  No default controller available

  
  Trying to restart the bluetooth service doesn't produce any effect:
  $ sudo service bluetooth restart

  
  Getting bluetooth service status:
  $ sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Fri 2018-08-24 11:23:17 EEST; 1min 35s ago
   Docs: man:bluetoothd(8)
   Main PID: 24999 (bluetoothd)
 Status: "Running"
  Tasks: 1 (limit: 4915)
 CGroup: /system.slice/bluetooth.service
 └─24999 /usr/lib/bluetooth/bluetoothd

  elo 24 11:23:17 fabio-X550JK systemd[1]: Stopping Bluetooth service...
  elo 24 11:23:17 fabio-X550JK systemd[1]: Stopped Bluetooth service.
  elo 24 11:23:17 fabio-X550JK systemd[1]: Starting Bluetooth service...
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth daemon 5.48
  elo 24 11:23:17 fabio-X550JK systemd[1]: Started Bluetooth service.
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Starting SDP server
  elo 24 11:23:17 fabio-X550JK bluetoothd[24999]: Bluetooth management 
interface 1
  lines 1-17/17 (END)

  
  Reloading the driver:
  $ sudo modprobe -r btusb; sudo modprobe btusb;
  $ sudo service bluetooth restart

  
  None of these attempts could solve the issue.


  What happens?
  Bluetooth is working, I suspend my laptop, I resume my laptop -> Bluetooth 
controller is no longer recognised and 

[Kernel-packages] [Bug 1796553] Re: BT mouse getting reset during operation

[Daniel van Vugt]

Also, according to your kernel log (CurrentDmesg.txt) the message
happens along with a bunch of other messages relating to the system
suspending/resuming. Maybe it is trying to suspend and just failed to do
so?...

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

Title:
  BT mouse getting reset during operation

Status in linux package in Ubuntu:
  New

Bug description:
  
  (note: It's unclear to me if that's a kernel regression or an issue with 
bluez)

  
  I've been using this particular combination of Bluetooth mouse ("TECKNET 
BM306") & laptop ("Dell Latitude E7240") for over a year now.

  It used to work with 18.04 and 17.10, but with 18.10 I'm encountering
  a strange disconnect behaviour:

  1) Mouse is working ok
  2) Mouse suddenly stops
  3) Disabling and enabling bluetooth on the laptop makes the mouse work again.

  when this happens, dmesg reports:

  [57812.977570] usb 1-1.3: reset full-speed USB device number 18 using
  ehci-pci

  Disabling bluetooth and enabling it again results in:

  [57833.455866] usb 1-1.3: USB disconnect, device number 18
  [57833.455948] Bluetooth: hci0: turning off Intel device LED failed (-19)
  [57836.905656] usb 1-1.3: new full-speed USB device number 19 using ehci-pci
  [57837.016248] usb 1-1.3: New USB device found, idVendor=8087, 
idProduct=07dc, bcdDevice= 0.01
  [57837.016253] usb 1-1.3: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
  [57837.030092] Bluetooth: hci0: read Intel version: 370710018002030d00
  [57837.030169] Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
  [57837.251206] Bluetooth: hci0: Intel firmware patch completed and activated
  [57841.724368] hid-generic 0005:0A5C:0001.001F: unknown main item tag 0x0
  [57841.724587] input: TECKNET BM306 Mouse as 
/devices/pci:00/:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:256/0005:0A5C:0001.001F/input/input78
  [57841.724873] hid-generic 0005:0A5C:0001.001F: input,hidraw0: BLUETOOTH HID 
v1.29 Mouse [TECKNET BM306] on fc:f8:ae:45:3c:05

  $ bluetoothctl --version
  bluetoothctl: 5.50

  $ hciconfig -a
  hci0: Type: Primary  Bus: USB
BD Address: FC:F8:AE:45:3C:05  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN 
RX bytes:52465 acl:3355 sco:0 events:222 errors:0
TX bytes:28384 acl:13 sco:0 commands:170 errors:0
Features: 0xff 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH HOLD SNIFF 
Link mode: SLAVE ACCEPT 
Name: 'ChromeLinux_AA14'
Class: 0x0c010c
Service Classes: Rendering, Capturing
Device Class: Computer, Laptop
HCI Version: 4.0 (0x6)  Revision: 0x500
LMP Version: 4.0 (0x6)  Subversion: 0x500
Manufacturer: Intel Corp. (2)

  $ bluetoothctl
  Agent registered
  [TECKNET BM306]# show
  Controller FC:F8:AE:45:3C:05 (public)
Name: humbaba
Alias: ChromeLinux_AA14
Class: 0x000c010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: no
  [TECKNET BM306]# devices
  Device 20:9B:A5:68:AE:67 SoundBuds Flow
  Device DC:2C:26:01:24:23 TECKNET BM306
  Device 88:71:E5:0E:6B:99 Echo-HPT
  Device 00:0B:E4:A0:A2:14 Nokia BH-103
  Device A8:96:75:8B:4F:49 Moto G5S Plus
  Device 00:02:5B:20:75:3C Trust SPK-02
  Device 88:75:98:F2:5C:9E NS9+
  Device 00:E0:4C:D5:E0:F5 SoundCore mini
  [TECKNET BM306]# info DC:2C:26:01:24:23
  Device DC:2C:26:01:24:23 (public)
Name: TECKNET BM306
Alias: TECKNET BM306
Class: 0x0580
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
Modalias: usb:v0A5Cp0001d0129

  
  $ rfkill list
  2: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
  3: dell-bluetooth: 

[Kernel-packages] [Bug 1796553] Re: BT mouse getting reset during operation

[Daniel van Vugt]

It sounds more like a kernel issue (or hardware) if your Bluetooth
dongle is getting reset:

[57812.977570] usb 1-1.3: reset full-speed USB device number 18 using
ehci-pci

so reassigning to the kernel.

Also, if your Bluetooth adapter is an external one then please try a
different USB port.

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

** No longer affects: bluez (Ubuntu)

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

Title:
  BT mouse getting reset during operation

Status in linux package in Ubuntu:
  New

Bug description:
  
  (note: It's unclear to me if that's a kernel regression or an issue with 
bluez)

  
  I've been using this particular combination of Bluetooth mouse ("TECKNET 
BM306") & laptop ("Dell Latitude E7240") for over a year now.

  It used to work with 18.04 and 17.10, but with 18.10 I'm encountering
  a strange disconnect behaviour:

  1) Mouse is working ok
  2) Mouse suddenly stops
  3) Disabling and enabling bluetooth on the laptop makes the mouse work again.

  when this happens, dmesg reports:

  [57812.977570] usb 1-1.3: reset full-speed USB device number 18 using
  ehci-pci

  Disabling bluetooth and enabling it again results in:

  [57833.455866] usb 1-1.3: USB disconnect, device number 18
  [57833.455948] Bluetooth: hci0: turning off Intel device LED failed (-19)
  [57836.905656] usb 1-1.3: new full-speed USB device number 19 using ehci-pci
  [57837.016248] usb 1-1.3: New USB device found, idVendor=8087, 
idProduct=07dc, bcdDevice= 0.01
  [57837.016253] usb 1-1.3: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
  [57837.030092] Bluetooth: hci0: read Intel version: 370710018002030d00
  [57837.030169] Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
  [57837.251206] Bluetooth: hci0: Intel firmware patch completed and activated
  [57841.724368] hid-generic 0005:0A5C:0001.001F: unknown main item tag 0x0
  [57841.724587] input: TECKNET BM306 Mouse as 
/devices/pci:00/:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:256/0005:0A5C:0001.001F/input/input78
  [57841.724873] hid-generic 0005:0A5C:0001.001F: input,hidraw0: BLUETOOTH HID 
v1.29 Mouse [TECKNET BM306] on fc:f8:ae:45:3c:05

  $ bluetoothctl --version
  bluetoothctl: 5.50

  $ hciconfig -a
  hci0: Type: Primary  Bus: USB
BD Address: FC:F8:AE:45:3C:05  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN 
RX bytes:52465 acl:3355 sco:0 events:222 errors:0
TX bytes:28384 acl:13 sco:0 commands:170 errors:0
Features: 0xff 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH HOLD SNIFF 
Link mode: SLAVE ACCEPT 
Name: 'ChromeLinux_AA14'
Class: 0x0c010c
Service Classes: Rendering, Capturing
Device Class: Computer, Laptop
HCI Version: 4.0 (0x6)  Revision: 0x500
LMP Version: 4.0 (0x6)  Subversion: 0x500
Manufacturer: Intel Corp. (2)

  $ bluetoothctl
  Agent registered
  [TECKNET BM306]# show
  Controller FC:F8:AE:45:3C:05 (public)
Name: humbaba
Alias: ChromeLinux_AA14
Class: 0x000c010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: no
  [TECKNET BM306]# devices
  Device 20:9B:A5:68:AE:67 SoundBuds Flow
  Device DC:2C:26:01:24:23 TECKNET BM306
  Device 88:71:E5:0E:6B:99 Echo-HPT
  Device 00:0B:E4:A0:A2:14 Nokia BH-103
  Device A8:96:75:8B:4F:49 Moto G5S Plus
  Device 00:02:5B:20:75:3C Trust SPK-02
  Device 88:75:98:F2:5C:9E NS9+
  Device 00:E0:4C:D5:E0:F5 SoundCore mini
  [TECKNET BM306]# info DC:2C:26:01:24:23
  Device DC:2C:26:01:24:23 (public)
Name: TECKNET BM306
Alias: TECKNET BM306
Class: 0x0580
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
UUID: PnP Information   

[Kernel-packages] [Bug 1728385] Re: Reduce/hide excessive logging when Bluetooth is intentionally disabled: "Failed to set mode: Blocked through rfkill (0x12)"

[Daniel van Vugt]

** Changed in: bluez (Ubuntu)
   Status: Expired => New

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

** Tags removed: artful
** Tags added: bionic

** Changed in: bluez (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Reduce/hide excessive logging when Bluetooth is intentionally
  disabled: "Failed to set mode: Blocked through rfkill (0x12)"

Status in bluez package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-24 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20GJ001HMH
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET26W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20GJ001HMH
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S2
  dmi.product.name: 20GJ001HMH
  dmi.product.version: ThinkPad S2
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:14933 acl:0 sco:0 events:2414 errors:0
TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1728385/+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 1793997] Re: iwlwifi 0000:04:00.0: Queue 10 is active on fifo 2 and stuck for 10000 ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a

[berend]

Another crash, without any temperature message.

What I forgot to mention is that a crash only happens after a sleep. I
don't think I have seen a crash after a fresh boot, only the next day
after the machine has slept at least once.

> dmesg | grep iwlwifi
[45654.419172] iwlwifi :04:00.0: iwlwifi transaction failed, dumping 
registers
[45654.419184] iwlwifi :04:00.0: iwlwifi device config registers:
[45654.419236] iwlwifi :04:00.0: : 08b18086 0010 028000bb 
 0004   
[45654.419243] iwlwifi :04:00.0: 0020:    
40708086  00c8  0100
[45654.419247] iwlwifi :04:00.0: iwlwifi device memory mapped registers:
[45654.419282] iwlwifi :04:00.0: :    
    
[45654.419288] iwlwifi :04:00.0: 0020:    
    
[45654.419296] iwlwifi :04:00.0: iwlwifi device AER capability structure:
[45654.419325] iwlwifi :04:00.0: : 14010001 0010  
00462031 31c1 2000 0014 4001
[45654.419329] iwlwifi :04:00.0: 0020: 000f ec100460 
[45654.419335] iwlwifi :04:00.0: iwlwifi parent port (:00:1c.3) config 
registers:
[45654.419361] iwlwifi :00:1c.3: : 8c168086 0017 060400d5 
00810010   00040400 20f0
[45654.419367] iwlwifi :00:1c.3: 0020: ec10ec10 0001fff1  
  0040  00100405
[45654.419450] WARNING: CPU: 4 PID: 0 at 
/build/linux-39dmni/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/trans.c:1973
 iwl_trans_pcie_grab_nic_access+0xea/0xf0 [iwlwifi]
[45654.419536]  intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp arc4 
snd_hda_codec_realtek snd_hda_codec_generic kvm_intel kvm irqbypass 
crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel uvcvideo 
snd_hda_intel videobuf2_vmalloc videobuf2_memops aes_x86_64 crypto_simd 
snd_hda_codec glue_helper cryptd videobuf2_v4l2 snd_hda_core snd_usb_audio 
intel_cstate videobuf2_core snd_usbmidi_lib snd_seq_midi intel_rapl_perf 
videodev btusb snd_hwdep snd_seq_midi_event media btrtl snd_pcm snd_rawmidi 
btbcm iwlmvm mac80211 btintel iwlwifi bluetooth snd_seq input_leds ecdh_generic 
rtsx_pci_ms joydev nvidia_uvm(POE) snd_seq_device memstick serio_raw snd_timer 
cfg80211 mxm_wmi snd wmi_bmof soundcore shpchp sch_fq_codel mei_me mei mac_hid 
lpc_ich ie31200_edac parport_pc ppdev sunrpc lp parport
[45654.419675] RIP: 0010:iwl_trans_pcie_grab_nic_access+0xea/0xf0 [iwlwifi]
[45654.419715]  iwl_read_prph+0x38/0x90 [iwlwifi]
[45654.419729]  iwl_trans_pcie_log_scd_error+0x125/0x1f0 [iwlwifi]
[45654.419742]  ? iwl_pcie_txq_build_tfd+0xe0/0xe0 [iwlwifi]
[45654.419753]  iwl_pcie_txq_stuck_timer+0x46/0x70 [iwlwifi]
[45654.472666] iwlwifi :04:00.0: Queue 10 is active on fifo 2 and stuck for 
1 ms. SW [31, 126] HW [90, 90] FH TRB=0x05a5a5a5a

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

Title:
  iwlwifi :04:00.0: Queue 10 is active on fifo 2 and stuck for 1
  ms. SW [247, 164] HW [90, 90] FH TRB=0x05a5a5a5a

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  Every few days iwlwifi decides to stop working. Only recourse is
  restart.

  From syslog:

  Sep 24 11:42:10 bonobo kernel: [109525.538612] iwlwifi :04:00.0: iwlwifi 
transaction failed, dumping registers
  Sep 24 11:42:10 bonobo kernel: [109525.538622] iwlwifi :04:00.0: iwlwifi 
device config registers:
  Sep 24 11:42:10 bonobo kernel: [109525.538669] iwlwifi :04:00.0: 
: 08b18086 0010 028000bb  0004   

  Sep 24 11:42:10 bonobo kernel: [109525.538674] iwlwifi :04:00.0: 
0020:    40708086  00c8  
0100
  Sep 24 11:42:10 bonobo kernel: [109525.538677] iwlwifi :04:00.0: iwlwifi 
device memory mapped registers:
  Sep 24 11:42:10 bonobo kernel: [109525.538709] iwlwifi :04:00.0: 
:        

  Sep 24 11:42:10 bonobo kernel: [109525.538713] iwlwifi :04:00.0: 
0020:        

  Sep 24 11:42:10 bonobo kernel: [109525.538719] iwlwifi :04:00.0: iwlwifi 
device AER capability structure:
  Sep 24 11:42:10 bonobo kernel: [109525.538746] iwlwifi :04:00.0: 
: 14010001 0010  00462031 3141 2000 0014 
4001
  Sep 24 11:42:10 bonobo kernel: [109525.538749] iwlwifi :04:00.0: 
0020: 000f ec100460 
  Sep 24 11:42:10 bonobo kernel: [109525.538752] iwlwifi :04:00.0: iwlwifi 
parent port (:00:1c.3) config registers:
  Sep 24 11:42:10 bonobo kernel: 

[Kernel-packages] [Bug 1796608] Re: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module failed to build

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  package will not load

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-29-generic
  Date: Sun Oct  7 21:26:55 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu8:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:2358:2:
 error: implicit declaration of function ‘init_timer’; did you mean 
‘init_timers’? [-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2018-10-05 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu8
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1796608/+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 1796550] Re: Separate keyboard brightness control keys (down/up) don't work

[Daniel van Vugt]

Now upstream in: https://gitlab.gnome.org/GNOME/gnome-settings-
daemon/issues/100

** Description changed:

- https://gitlab.gnome.org/GNOME/gnome-shell/issues/636
+ https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/100
  
  ---
  
  On laptops with two separate (down,up) keys to control the backlit
  keyboard, both keys seem to do nothing. The OSD for the backlit keyboard
  is displayed but no progress bar and no actual effect to the backlight.
  Almost as if the shell only understands laptops with a single key for
  controlling the keyboard backlight...
  
  Bug verified in cosmic on:
    * Asus UX331UAL
    * Apple Macbook Pro 12,1
    * Apple Macbook Air
  
  All of them have these keys and they all fail in the same way. However
  it is not a kernel bug. The kernel interface
  (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly.
  This seems to be a problem with Gnome Shell only.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 13:41:50 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (25 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

** Also affects: gnome-settings-daemon (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Separate keyboard brightness control keys (down/up) don't work

Status in gnome-settings-daemon package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/100

  ---

  On laptops with two separate (down,up) keys to control the backlit
  keyboard, both keys seem to do nothing. The OSD for the backlit
  keyboard is displayed but no progress bar and no actual effect to the
  backlight. Almost as if the shell only understands laptops with a
  single key for controlling the keyboard backlight...

  Bug verified in cosmic on:
    * Asus UX331UAL
    * Apple Macbook Pro 12,1
    * Apple Macbook Air

  All of them have these keys and they all fail in the same way. However
  it is not a kernel bug. The kernel interface
  (/sys/class/leds/*::kbd_backlight/*) works when I write to it
  directly. This seems to be a problem with Gnome Shell only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 13:41:50 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (25 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1796550/+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 1796608] [NEW] bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module failed to build

[Mark Dannunzio]

Public bug reported:

package will not load

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
DKMSKernelVersion: 4.15.0-29-generic
Date: Sun Oct  7 21:26:55 2018
DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu8:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:2358:2:
 error: implicit declaration of function ‘init_timer’; did you mean 
‘init_timers’? [-Werror=implicit-function-declaration]
InstallationDate: Installed on 2018-10-05 (2 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageVersion: 6.30.223.248+bdcom-0ubuntu8
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3
SourcePackage: bcmwl
Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module 
failed to build
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module
  failed to build

Status in bcmwl package in Ubuntu:
  New

Bug description:
  package will not load

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  DKMSKernelVersion: 4.15.0-29-generic
  Date: Sun Oct  7 21:26:55 2018
  DuplicateSignature: 
dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu8:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_linux.c:2358:2:
 error: implicit declaration of function ‘init_timer’; did you mean 
‘init_timers’? [-Werror=implicit-function-declaration]
  InstallationDate: Installed on 2018-10-05 (2 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageVersion: 6.30.223.248+bdcom-0ubuntu8
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: bcmwl
  Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module 
failed to build
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1796608/+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 1792660] Re: nvme name floated after boot with 4.15.0 kernel

[Guo Yaowen]

hi Guilherme,
I couldn't find a normal Linux-image package in 4.17 and 4.17-rac4, just a 
package with unsigned. Could you please tell me  if this package is available. 

  linux-headers-4.17.0-041700_4.17.0-041700.201806041953_all.deb
   linux-headers-4.17.0-041700-generic_4.17.0-041700.201806041953_amd64.deb
   linux-headers-4.17.0-041700-lowlatency_4.17.0-041700.201806041953_amd64.deb
   
//linux-image-unsigned-4.17.0-041700-generic_4.17.0-041700.201806041953_amd64.deb
   
//linux-image-unsigned-4.17.0-041700-lowlatency_4.17.0-041700.201806041953_amd64.deb
   linux-modules-4.17.0-041700-generic_4.17.0-041700.201806041953_amd64.deb
   linux-modules-4.17.0-041700-lowlatency_4.17.0-041700.201806041953_amd64.deb



By the way, can you tell me the relation between the kernel with RAC and the 
kernel without RAC? 

Thanks,
Guo Yaowen

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

Title:
  nvme name floated after boot with 4.15.0 kernel

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

Bug description:
  nvme device name such as /dev/nvme?n?p? would be floated that is
  symbol link to different real ssd device after reboot in 4.15.0 kernel
  for 16.04.5 HWE and 18.04 GA-kernel. This are not found on 16.04.5 GA-
  kernel ( 4.4.0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792660/+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 1795492] Re: linux-aws: 4.18.0-1001.2 -proposed tracker

[Brad Figg]

** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Description changed:

  This bug is for tracking the 4.18.0-1001.1 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
- kernel-phase-changed:Sunday, 07. October 2018 22:32 UTC
- kernel-phase:Uploaded
- 
  -- swm properties --
  phase: Uploaded
+ kernel-phase-changed:Sunday, 07. October 2018 23:32 UTC
+ kernel-phase:Promoted to proposed

** Description changed:

  This bug is for tracking the 4.18.0-1001.1 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
- phase: Uploaded
- kernel-phase-changed:Sunday, 07. October 2018 23:32 UTC
- kernel-phase:Promoted to proposed
+ phase: Promoted to proposed
+ proposed-announcement-sent: true
+ proposed-testing-requested: true

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

Title:
  linux-aws: 4.18.0-1001.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  Confirmed
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Released
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  Confirmed
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-aws source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the 4.18.0-1001.1 upload package. This bug
  will contain status and testing results related to that upload.

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

  -- swm properties --
  phase: Promoted to proposed
  proposed-announcement-sent: true
  proposed-testing-requested: true

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795492/+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 1795492] Re: linux-aws: 4.18.0-1001.2 -proposed tracker

[Brad Figg]

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

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

** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Fix Committed

** Tags added: block-proposed-cosmic

** Tags added: block-proposed

** Description changed:

  This bug is for tracking the 4.18.0-1001.1 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
+ 
+ kernel-phase-changed:Sunday, 07. October 2018 22:32 UTC
+ kernel-phase:Uploaded

** Description changed:

  This bug is for tracking the 4.18.0-1001.1 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  kernel-phase-changed:Sunday, 07. October 2018 22:32 UTC
  kernel-phase:Uploaded
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux-aws: 4.18.0-1001.2 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
  Fix Committed
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-aws package in Ubuntu:
  Confirmed
Status in linux-aws source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the 4.18.0-1001.1 upload package. This bug
  will contain status and testing results related to that upload.

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

  kernel-phase-changed:Sunday, 07. October 2018 22:32 UTC
  kernel-phase:Uploaded

  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795492/+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 1796346] Re: linux: 4.18.0-9.10 -proposed tracker

[Brad Figg]

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

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1796347 (linux-hwe-edge), bug 1796348 (linux-azure-edge)
  derivatives: bug 1796349 (linux-raspi2), bug 1796350 (linux-azure), bug 
1796351 (linux-gcp), bug 1796353 (linux-kvm)
+ kernel-phase:Uploaded
+ kernel-phase-changed:Sunday, 07. October 2018 22:02 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see:
  https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1796347 (linux-hwe-edge), bug 1796348 (linux-azure-edge)
  derivatives: bug 1796349 (linux-raspi2), bug 1796350 (linux-azure), bug 
1796351 (linux-gcp), bug 1796353 (linux-kvm)
  kernel-phase:Uploaded
  kernel-phase-changed:Sunday, 07. October 2018 22:02 UTC
+ 
+ -- swm properties --
+ phase: Uploaded

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

Title:
  linux: 4.18.0-9.10 -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
  Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
  In Progress
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

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

  backports: bug 1796347 (linux-hwe-edge), bug 1796348 (linux-azure-edge)
  derivatives: bug 1796349 (linux-raspi2), bug 1796350 (linux-azure), bug 
1796351 (linux-gcp), bug 1796353 (linux-kvm)
  kernel-phase:Uploaded
  kernel-phase-changed:Sunday, 07. October 2018 22:02 UTC

  -- swm properties --
  phase: Uploaded

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796346/+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 1796350] Re: linux-azure: -proposed tracker

[Brad Figg]

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
+ kernel-phase:Packaging
+ kernel-phase-changed:Sunday, 07. October 2018 22:03 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
- kernel-phase:Packaging
- kernel-phase-changed:Sunday, 07. October 2018 22:03 UTC
+ phase: Packaging

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

Title:
  linux-azure:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in Kernel SRU Workflow stakeholder-signoff series:
  New
Status in linux-azure package in Ubuntu:
  Confirmed
Status in linux-azure source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796350/+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 1796351] Re: linux-gcp: -proposed tracker

[Brad Figg]

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

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
+ kernel-phase:Packaging
+ kernel-phase-changed:Sunday, 07. October 2018 22:02 UTC

** Description changed:

  This bug is for tracking the  upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
- kernel-phase:Packaging
- kernel-phase-changed:Sunday, 07. October 2018 22:02 UTC
+ phase: Packaging

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

Title:
  linux-gcp:  -proposed tracker

Status in Kernel SRU Workflow:
  In Progress
Status in Kernel SRU Workflow automated-testing series:
  New
Status in Kernel SRU Workflow prepare-package series:
  Confirmed
Status in Kernel SRU Workflow prepare-package-meta series:
  New
Status in Kernel SRU Workflow prepare-package-signed series:
  New
Status in Kernel SRU Workflow promote-to-proposed series:
  New
Status in Kernel SRU Workflow promote-to-release series:
  New
Status in Kernel SRU Workflow regression-testing series:
  New
Status in linux-gcp package in Ubuntu:
  Confirmed
Status in linux-gcp source package in Cosmic:
  Confirmed

Bug description:
  This bug is for tracking the  upload package.
  This bug will contain status and testing results related to that
  upload.

  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  kernel-master-bug: 1796346
  phase: Packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796351/+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 1760545] Re: [18.04] GLK hang after a while

[Chris Allen]

What is the timeline for having this fix backported to the 4.15 kernel?

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

Title:
  [18.04] GLK hang after a while

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Bionic:
  In Progress

Bug description:
  SRU Justification

  Impact: i915 lacks information about the glk_dmc_ver1_04.bin firmware
  file in modinfo, so it is not included in the initrd along with the
  i915 driver. Thus the firmware does not get loaded. Loading the
  firmware is said to prevent a hang.

  Fix: Add a MODULE_FIRMWARE statement for the firmware.

  Test Case: Without the firmware there will be a "Direct firmware load
  for i915/glk_dmc_ver1_04.bin failed with error -2" line in dmesg. With
  the firmware there is no such message.

  Regression Potential: Minimal. Will only be loaded by i915 for
  specific hardware, and loading the firmware is known to fix a hang.

  ---

  Description:

  Platform information:
  Label: GLK02SDP
  Processor: Silver N5000
  Bios: GELKRVPA.X64.0083.B30.1801162142
  OS: Ubuntu 18.04
  Kernel: 4.15.0-10-generic

  Details:
  Power on, and enter into the system;
  After a period, sometimes about 20 minutes, sometimes 1 hour, the machine 
will hang.
  We can only power it off manually, then power on to enter into OS again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1760545/+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 1792044] Re: update ENA driver to latest mainline version

[p3lonjan1l]

** Changed in: linux (Ubuntu)
   Status: Fix Committed => 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/1792044

Title:
  update ENA driver to latest mainline version

Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Xenial:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  Update ENA driver to latest mainline version as of this commit:
  
https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=0e1f4c76be241377d282e34ebea6d16ff7829747

  For Bionic, the following commits:

  net: ena: fix incorrect usage of memory barriers
  net: ena: fix missing calls to READ_ONCE
  net: ena: fix missing lock during device destruction
  net: ena: fix potential double ena_destroy_device()
  net: ena: fix device destruction to gracefully free resources
  net: ena: fix driver when PAGE_SIZE == 64kB
  net: ena: fix surprise unplug NULL dereference kernel crash
  net: ena: Fix use of uninitialized DMA address bits field
  UBUNTU: SAUCE: ena: devm_kzalloc() -> devm_kcalloc()
  net: ena: Eliminate duplicate barriers on weakly-ordered archs
  net: ena: increase ena driver version to 1.5.0
  net: ena: add detection and recovery mechanism for handling missed/misrouted 
MSI-X

  For Xenial, the following commits:

  net: ena: fix incorrect usage of memory barriers
  net: ena: fix missing calls to READ_ONCE
  net: ena: fix missing lock during device destruction
  net: ena: fix potential double ena_destroy_device()
  net: ena: fix device destruction to gracefully free resources
  net: ena: fix driver when PAGE_SIZE == 64kB
  net: ena: fix surprise unplug NULL dereference kernel crash
  net: ena: Fix use of uninitialized DMA address bits field
  UBUNTU: SAUCE: ena: devm_kzalloc() -> devm_kcalloc()
  net: ena: Eliminate duplicate barriers on weakly-ordered archs
  net: ena: fix error handling in ena_down() sequence
  net: ena: increase ena driver version to 1.5.0
  net: ena: add detection and recovery mechanism for handling missed/misrouted 
MSI-X
  net: ena: fix race condition between device reset and link up setup
  net: ena: increase ena driver version to 1.3.0
  net: ena: add new admin define for future support of IPv6 RSS
  net: ena: add statistics for missed tx packets
  net: ena: add power management ops to the ENA driver
  net: ena: remove legacy suspend suspend/resume support
  net: ena: improve ENA driver boot time.
  net: ena: fix wrong max Tx/Rx queues on ethtool
  net: ena: fix rare kernel crash when bar memory remap fails
  net: ena: reduce the severity of some printouts
  net: ena: Remove redundant unlikely()

  *Note that some of these were already present in the linux-aws
  variants (the remainder will be picked up on their next rebase
  cycles).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792044/+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 1777238] Re: video lag

[Damiön la Bagh]

Another thing to note. The stutter (every 5 seconds a freeze frame) is
consistently reproduce-able on Gnome on Ubuntu 18.04 but when you switch
to Unity there is no stutter the video at all. So suspect that Gnome
could also be playing a part in this issue.

** Summary changed:

- video lag
+ video lag - Every 5 seconds a freeze frame when playing video of any source

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

Title:
  video lag - Every 5 seconds a freeze frame when playing video of any
  source

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The problem exists for months and I didn't find a good answer on it.
  It affects many softwares: Cheese, Super Tux Cart, VLC (when I rewind
  the video the sounds continues, but the video stops), youtube,
  Hangouts and every software where video is played.

  I experienced that there are 2 things that can break it:
   - if I move the mouse out and in on the affected window (it doesn't work in 
full screen)
   - if I open the system monitor, the problem also disappears

  other people also face with this problem:
  
https://unix.stackexchange.com/questions/447696/ubuntu-16-04-18-04-video-playback-lags-stutters
  
https://askubuntu.com/questions/1032035/ubuntu-18-04-budgie-desktop-video-lag-youtube-twitch-in-chrome
  
https://askubuntu.com/questions/1030074/my-video-player-in-ubuntu-18-04-lts-lags/1030194
  https://askubuntu.com/questions/1030155/youtube-video-lag-on-18-04

  Ubuntu 4.15.0-23.25-generic 4.15.18
  it was upgraded from 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cheese 3.28.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun 16 14:34:26 2018
  ExecutablePath: /usr/bin/cheese
  InstallationDate: Installed on 2016-08-04 (680 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5440
  RelatedPackageVersions:
   cheese3.28.0-1ubuntu1
   cheese-common 3.28.0-1ubuntu1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago)
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 009TY8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  vandor 3436 F pulseaudio
   /dev/snd/controlC1:  vandor 3436 F pulseaudio
   /dev/snd/controlC0:  vandor 3436 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=b5a3c617-9443-458f-92a3-63eea1f57d5c
  InstallationDate: Installed on 2016-08-04 (681 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Dell Inc. Latitude E5440
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=38affd30-88f0-4a36-b9ae-6b5c210844b4 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-02 (74 days ago)
  UserGroups: adm bumblebee cdrom dip docker libvirt libvirtd lpadmin mail 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/01/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 009TY8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/01/2014:svnDellInc.:pnLatitudeE5440:pvr01:rvnDellInc.:rn009TY8:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5440
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777238/+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 1796591] [NEW] package libnvidia-compute-390 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package

[George Triantafyllou]

Public bug reported:

install failed

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libnvidia-compute-390 (not installed)
ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
Uname: Linux 4.15.0-36-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
AptOrdering:
 libcuda1-340:amd64: Remove
 nvidia-opencl-icd-340:amd64: Remove
 libnvidia-compute-390:amd64: Install
 nvidia-utils-390:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sun Oct  7 22:12:51 2018
DpkgTerminalLog:
 Preparing to unpack .../libnvidia-compute-390_390.48-0ubuntu3_amd64.deb ...
 Unpacking libnvidia-compute-390:amd64 (390.48-0ubuntu3) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libnvidia-compute-390_390.48-0ubuntu3_amd64.deb 
(--unpack):
  trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is 
also in package nvidia-340 340.107-0ubuntu0.18.04.1
ErrorMessage: trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', 
which is also in package nvidia-340 340.107-0ubuntu0.18.04.1
InstallationDate: Installed on 2018-10-05 (1 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: nvidia-graphics-drivers-390
Title: package libnvidia-compute-390 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also 
in package nvidia-340 340.107-0ubuntu0.18.04.1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-390 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

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

Title:
  package libnvidia-compute-390 (not installed) failed to
  install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu
  /libnvidia-ml.so', which is also in package nvidia-340
  340.107-0ubuntu0.18.04.1

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  New

Bug description:
  install failed

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libnvidia-compute-390 (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  AptOrdering:
   libcuda1-340:amd64: Remove
   nvidia-opencl-icd-340:amd64: Remove
   libnvidia-compute-390:amd64: Install
   nvidia-utils-390:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sun Oct  7 22:12:51 2018
  DpkgTerminalLog:
   Preparing to unpack .../libnvidia-compute-390_390.48-0ubuntu3_amd64.deb ...
   Unpacking libnvidia-compute-390:amd64 (390.48-0ubuntu3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libnvidia-compute-390_390.48-0ubuntu3_amd64.deb 
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is 
also in package nvidia-340 340.107-0ubuntu0.18.04.1
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
nvidia-340 340.107-0ubuntu0.18.04.1
  InstallationDate: Installed on 2018-10-05 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: nvidia-graphics-drivers-390
  Title: package libnvidia-compute-390 (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libnvidia-ml.so', which is also in package 
nvidia-340 340.107-0ubuntu0.18.04.1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1796591/+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 1777364] Re: coping files to cifs mounted directory causes general protection fault

[Martin Barlow]

opened bug upstream https://bugzilla.samba.org/show_bug.cgi?id=13647

** Bug watch added: Samba Bugzilla #13647
   https://bugzilla.samba.org/show_bug.cgi?id=13647

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

Title:
  coping files to cifs mounted directory causes general protection fault

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  How to reproduce:

  Copy some large files from local filesystem to CIFS mounted
  filesystem. After some gigabytes, it syslog will show "general
  protection fault" and mounted file system will become unresponsive.

  How often does it occur:

  Every time, after a few minutes or so.

  Affected kernels:

  Bionic 4.15.0-23-generic and forward. I also tried 4.15.18-041518-generic and 
4.16.13-041613-generic from ubuntu archives an got similar GPF.
  4.13.0-43-generic from ubuntu 17.10 not affected.

  More information:

  I have kerberos authenticated, autofs mounted, cifs
  Mounted with:
  type cifs 
(rw,relatime,vers=default,sec=krb5,cache=strict,username=root,uid=1100,forceuid,gid=0,noforcegid,addr=192.168.50.2,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=1048576,wsize=1048576,echo_interval=60,actimeo=1)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-23-generic 4.15.0-23.25
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mbarlow2249 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Jun 17 23:14:02 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  HibernationDevice: RESUME=UUID=25088f17-7123-46c8-bda4-362bcd9f986e
  InstallationDate: Installed on 2017-11-26 (203 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia
   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
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=69170b9c-88cc-4e5b-83a8-c6a01d7b738b ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (51 days ago)
  WifiSyslog:

  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.6.2
  dmi.board.name: 06CC14
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.6.2:bd02/26/2018:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn06CC14:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1777364/+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 1796582] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

** Changed in: linux (Ubuntu)
   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/1796582

Title:
  Internal microphone not working on Lenovo Ideapad 330S-15ARR

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  The internal microphone on this troublesome laptop stopped working
  after upgrading from Bionic to Cosmic.  There is no signal from the
  microphone with kernel 4.18.0-7 or 4.18.0-8.

  This DOES work correctly with kernel 4.15.0-34 that is still present
  on Cosmic after the upgrade.

  I recommend Canonical gets this laptop for testing since a ton of
  stuff is troublesome on this Raven Ridge laptop.  Would be a good
  specimen to get support for this platform improved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xorbit 2295 F pulseaudio
   /dev/snd/controlC0:  xorbit 2295 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Oct  7 12:02:45 2018
  InstallationDate: Installed on 2018-09-20 (17 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 81FB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic rcu_nocbs=0-7 quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (6 days ago)
  dmi.bios.date: 09/05/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WCN26WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330S-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WCN26WW:bd09/05/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:
  dmi.product.family: ideapad 330S-15ARR
  dmi.product.name: 81FB
  dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR
  dmi.product.version: Lenovo ideapad 330S-15ARR
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796582/+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 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

[Richard Baka]

Another User (another-user), install newer kernel than ubuntu's default
and don't use noapic just ivrs parameters.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1776563/+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 1796582] [NEW] Internal microphone not working on Lenovo Ideapad 330S-15ARR

[Patrick Van Oosterwijck]

Public bug reported:

The internal microphone on this troublesome laptop stopped working after
upgrading from Bionic to Cosmic.  There is no signal from the microphone
with kernel 4.18.0-7 or 4.18.0-8.

This DOES work correctly with kernel 4.15.0-34 that is still present on
Cosmic after the upgrade.

I recommend Canonical gets this laptop for testing since a ton of stuff
is troublesome on this Raven Ridge laptop.  Would be a good specimen to
get support for this platform improved.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-8-generic 4.18.0-8.9
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  xorbit 2295 F pulseaudio
 /dev/snd/controlC0:  xorbit 2295 F pulseaudio
CurrentDesktop: GNOME
Date: Sun Oct  7 12:02:45 2018
InstallationDate: Installed on 2018-09-20 (17 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 81FB
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic rcu_nocbs=0-7 quiet 
splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-8-generic N/A
 linux-backports-modules-4.18.0-8-generic  N/A
 linux-firmware1.175
SourcePackage: linux
UpgradeStatus: Upgraded to cosmic on 2018-09-30 (6 days ago)
dmi.bios.date: 09/05/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: 7WCN26WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 330S-15ARR
dmi.modalias: 
dmi:bvnLENOVO:bvr7WCN26WW:bd09/05/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:
dmi.product.family: ideapad 330S-15ARR
dmi.product.name: 81FB
dmi.product.sku: LENOVO_MT_81FB_BU_idea_FM_ideapad 330S-15ARR
dmi.product.version: Lenovo ideapad 330S-15ARR
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug cosmic

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

Title:
  Internal microphone not working on Lenovo Ideapad 330S-15ARR

Status in linux package in Ubuntu:
  New

Bug description:
  The internal microphone on this troublesome laptop stopped working
  after upgrading from Bionic to Cosmic.  There is no signal from the
  microphone with kernel 4.18.0-7 or 4.18.0-8.

  This DOES work correctly with kernel 4.15.0-34 that is still present
  on Cosmic after the upgrade.

  I recommend Canonical gets this laptop for testing since a ton of
  stuff is troublesome on this Raven Ridge laptop.  Would be a good
  specimen to get support for this platform improved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  xorbit 2295 F pulseaudio
   /dev/snd/controlC0:  xorbit 2295 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun Oct  7 12:02:45 2018
  InstallationDate: Installed on 2018-09-20 (17 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 81FB
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=4d91f09e-6122-4dd4-81fc-482465f8f0e7 ro noapic rcu_nocbs=0-7 quiet 
splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (6 days ago)
  dmi.bios.date: 09/05/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7WCN26WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 330S-15ARR
  dmi.modalias: 
dmi:bvnLENOVO:bvr7WCN26WW:bd09/05/2018:svnLENOVO:pn81FB:pvrLenovoideapad330S-15ARR:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad330S-15ARR:
  

[Kernel-packages] [Bug 1796574] Lsusb.txt

[Andreas Lööw]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1796574/+attachment/5198338/+files/Lsusb.txt

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas2086 F pulseaudio
   /dev/snd/controlC0:  andreas2086 F pulseaudio
   /dev/snd/controlC1:  andreas2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3305
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Andreas Lööw]

apport information

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

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas2086 F pulseaudio
   /dev/snd/controlC0:  andreas2086 F pulseaudio
   /dev/snd/controlC1:  andreas2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3305
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Andreas Lööw]

apport information

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

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas2086 F pulseaudio
   /dev/snd/controlC0:  andreas2086 F pulseaudio
   /dev/snd/controlC1:  andreas2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3305
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Andreas Lööw]

apport information

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

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas2086 F pulseaudio
   /dev/snd/controlC0:  andreas2086 F pulseaudio
   /dev/snd/controlC1:  andreas2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3305
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Andreas Lööw]

apport information

** Attachment added: "PulseList.txt"
   
https://bugs.launchpad.net/bugs/1796574/+attachment/5198344/+files/PulseList.txt

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas2086 F pulseaudio
   /dev/snd/controlC0:  andreas2086 F pulseaudio
   /dev/snd/controlC1:  andreas2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3305
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Andreas Lööw]

apport information

** Attachment added: "RfKill.txt"
   https://bugs.launchpad.net/bugs/1796574/+attachment/5198345/+files/RfKill.txt

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas2086 F pulseaudio
   /dev/snd/controlC0:  andreas2086 F pulseaudio
   /dev/snd/controlC1:  andreas2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3305
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796574/+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 1796574] Re: Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

[Andreas Lööw]

I just upgraded the BIOS to the latest available and the problem seem to
be fixed. No more black screen. Case closed.

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas2086 F pulseaudio
   /dev/snd/controlC0:  andreas2086 F pulseaudio
   /dev/snd/controlC1:  andreas2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3305
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Andreas Lööw]

apport information

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

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas2086 F pulseaudio
   /dev/snd/controlC0:  andreas2086 F pulseaudio
   /dev/snd/controlC1:  andreas2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3305
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796574/+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 1796576] [NEW] rtl8723be cannot connect to wifi since Kernel version 4.15.0-33-generic

[Alessio "Spinus" Moscatello]

Public bug reported:

Starting from Kernel version linux-image-4.15.0-33-generic I cannot connect 
anymore to wifi network. The problem occurs also with 
linux-image-4.15.0-34-generic.
Kernel version linux-headers-4.15.0-32-generic is working fine.

My current configuration for rtl8723be is
/etc/modprobe.d/rtlbtcoex.conf:
options rtl8723be ant_sel=2 ips=0

I'm using these parameters with for rtl8723be module in order to get the
correct gain for Wifi antenna.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-modules-extra-4.15.0-34-generic 4.15.0-34.37
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  alessio1778 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct  7 19:16:55 2018
EcryptfsInUse: Yes
HibernationDevice: RESUME=UUID=9d050d63-7a5d-443b-9210-3f51da9bf26f
InstallationDate: Installed on 2017-02-20 (593 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:b008 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 1bcf:2c87 Sunplus Innovation Technology Inc. 
 Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Pavilion Notebook
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=6c5ccef4-fabc-435b-a40b-c3d11c52cbfe ro quiet splash pci=noaer 
vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-34-generic N/A
 linux-backports-modules-4.15.0-34-generic  N/A
 linux-firmware 1.173.1
SourcePackage: linux
UpgradeStatus: Upgraded to bionic on 2018-08-21 (46 days ago)
dmi.bios.date: 12/12/2016
dmi.bios.vendor: Insyde
dmi.bios.version: F.25
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 8216
dmi.board.vendor: HP
dmi.board.version: 83.14
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd12/12/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.14:cvnHP:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
dmi.product.name: HP Pavilion Notebook
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug 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/1796576

Title:
  rtl8723be cannot connect to wifi since Kernel version
  4.15.0-33-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Starting from Kernel version linux-image-4.15.0-33-generic I cannot connect 
anymore to wifi network. The problem occurs also with 
linux-image-4.15.0-34-generic.
  Kernel version linux-headers-4.15.0-32-generic is working fine.

  My current configuration for rtl8723be is
  /etc/modprobe.d/rtlbtcoex.conf:
  options rtl8723be ant_sel=2 ips=0

  I'm using these parameters with for rtl8723be module in order to get
  the correct gain for Wifi antenna.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-modules-extra-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alessio1778 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 19:16:55 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=9d050d63-7a5d-443b-9210-3f51da9bf26f
  InstallationDate: Installed on 2017-02-20 (593 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:b008 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 1bcf:2c87 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=6c5ccef4-fabc-435b-a40b-c3d11c52cbfe ro quiet splash pci=noaer 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware  

[Kernel-packages] [Bug 1796576] Re: rtl8723be cannot connect to wifi since Kernel version 4.15.0-33-generic

[Alessio "Spinus" Moscatello]

Attaching dmesg output

** Attachment added: "dmesg output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796576/+attachment/5198384/+files/dmesg.txt

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

Title:
  rtl8723be cannot connect to wifi since Kernel version
  4.15.0-33-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Starting from Kernel version linux-image-4.15.0-33-generic I cannot connect 
anymore to wifi network. The problem occurs also with 
linux-image-4.15.0-34-generic.
  Kernel version linux-headers-4.15.0-32-generic is working fine.

  My current configuration for rtl8723be is
  /etc/modprobe.d/rtlbtcoex.conf:
  options rtl8723be ant_sel=2 ips=0

  I'm using these parameters with for rtl8723be module in order to get
  the correct gain for Wifi antenna.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-modules-extra-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alessio1778 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 19:16:55 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=9d050d63-7a5d-443b-9210-3f51da9bf26f
  InstallationDate: Installed on 2017-02-20 (593 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:b008 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 1bcf:2c87 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=6c5ccef4-fabc-435b-a40b-c3d11c52cbfe ro quiet splash pci=noaer 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (46 days ago)
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd12/12/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.14:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

[Ubuntu Kernel Bot]

This change was made by a bot.

** Changed in: linux (Ubuntu)
   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/1796576

Title:
  rtl8723be cannot connect to wifi since Kernel version
  4.15.0-33-generic

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Starting from Kernel version linux-image-4.15.0-33-generic I cannot connect 
anymore to wifi network. The problem occurs also with 
linux-image-4.15.0-34-generic.
  Kernel version linux-headers-4.15.0-32-generic is working fine.

  My current configuration for rtl8723be is
  /etc/modprobe.d/rtlbtcoex.conf:
  options rtl8723be ant_sel=2 ips=0

  I'm using these parameters with for rtl8723be module in order to get
  the correct gain for Wifi antenna.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-modules-extra-4.15.0-34-generic 4.15.0-34.37
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  alessio1778 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 19:16:55 2018
  EcryptfsInUse: Yes
  HibernationDevice: RESUME=UUID=9d050d63-7a5d-443b-9210-3f51da9bf26f
  InstallationDate: Installed on 2017-02-20 (593 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:b008 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 1bcf:2c87 Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 046d:c52f Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic 
root=UUID=6c5ccef4-fabc-435b-a40b-c3d11c52cbfe ro quiet splash pci=noaer 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-34-generic N/A
   linux-backports-modules-4.15.0-34-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-08-21 (46 days ago)
  dmi.bios.date: 12/12/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.14
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd12/12/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.14:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

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

[Andreas Lööw]

apport information

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

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas2086 F pulseaudio
   /dev/snd/controlC0:  andreas2086 F pulseaudio
   /dev/snd/controlC1:  andreas2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3305
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Andreas Lööw]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1796574/+attachment/5198341/+files/ProcEnviron.txt

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas2086 F pulseaudio
   /dev/snd/controlC0:  andreas2086 F pulseaudio
   /dev/snd/controlC1:  andreas2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3305
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796574/+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 1796574] Re: Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

[Andreas Lööw]

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796574/+attachment/5198332/+files/lspci-vnvn.log

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas2086 F pulseaudio
   /dev/snd/controlC0:  andreas2086 F pulseaudio
   /dev/snd/controlC1:  andreas2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3305
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Andreas Lööw]

apport information

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

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas2086 F pulseaudio
   /dev/snd/controlC0:  andreas2086 F pulseaudio
   /dev/snd/controlC1:  andreas2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3305
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Andreas Lööw]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1796574/+attachment/5198334/+files/CRDA.txt

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas2086 F pulseaudio
   /dev/snd/controlC0:  andreas2086 F pulseaudio
   /dev/snd/controlC1:  andreas2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3305
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Andreas Lööw]

apport information

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

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas2086 F pulseaudio
   /dev/snd/controlC0:  andreas2086 F pulseaudio
   /dev/snd/controlC1:  andreas2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3305
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Andreas Lööw]

apport information

** Attachment added: "IwConfig.txt"
   
https://bugs.launchpad.net/bugs/1796574/+attachment/5198336/+files/IwConfig.txt

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas2086 F pulseaudio
   /dev/snd/controlC0:  andreas2086 F pulseaudio
   /dev/snd/controlC1:  andreas2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3305
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Andreas Lööw]

apport information

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

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas2086 F pulseaudio
   /dev/snd/controlC0:  andreas2086 F pulseaudio
   /dev/snd/controlC1:  andreas2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3305
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796574/+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 1796574] Re: Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

[Andreas Lööw]

[Q1]
Description:Ubuntu 18.04.1 LTS
Release:18.04

[Q2]
linux-image-4.15.0-36-generic:
  Installed: 4.15.0-36.39
  Candidate: 4.15.0-36.39

[Q3]
Ubuntu to boot into X and display GUI on monitor.

[Q4]
Hang on black screen.


** Tags added: apport-collected bionic

** Description changed:

  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.
  
  dmesg:
  
  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed
  
  And it looks like the DisplayPort is not initialized correctly.
  
  "Black screen" in this context means nothing works (no TTY:s).
  
  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.
  
  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].
  
  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  
  
  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.4
+ Architecture: amd64
+ AudioDevicesInUse:
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC2:  andreas2086 F pulseaudio
+  /dev/snd/controlC0:  andreas2086 F pulseaudio
+  /dev/snd/controlC1:  andreas2086 F pulseaudio
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
+ InstallationDate: Installed on 2018-10-06 (0 days ago)
+ InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
+ MachineType: System manufacturer System Product Name
+ Package: linux (not installed)
+ ProcFB: 0 radeondrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
+ RelatedPackageVersions:
+  linux-restricted-modules-4.15.0-36-generic N/A
+  linux-backports-modules-4.15.0-36-generic  N/A
+  linux-firmware 1.173.1
+ Tags:  bionic
+ Uname: Linux 4.15.0-36-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
+ _MarkForUpload: True
+ dmi.bios.date: 12/25/2012
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: 3305
+ dmi.board.asset.tag: To be filled by O.E.M.
+ dmi.board.name: P9X79 DELUXE
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: Rev 1.xx
+ dmi.chassis.asset.tag: Asset-1234567890
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: Chassis Manufacture
+ dmi.chassis.version: Chassis Version
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
+ dmi.product.family: To be filled by O.E.M.
+ dmi.product.name: System Product Name
+ dmi.product.version: System Version
+ dmi.sys.vendor: System manufacturer

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

 

[Kernel-packages] [Bug 1796574] AlsaInfo.txt

[Andreas Lööw]

apport information

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1796574/+attachment/5198333/+files/AlsaInfo.txt

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas2086 F pulseaudio
   /dev/snd/controlC0:  andreas2086 F pulseaudio
   /dev/snd/controlC1:  andreas2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3305
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796574/+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 1796574] Re: Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

[Andreas Lööw]

** Tags added: radeon

** Tags added: 4.15.0-36-generic amdgpu

** Attachment added: "version.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796574/+attachment/5198331/+files/version.log

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  andreas2086 F pulseaudio
   /dev/snd/controlC0:  andreas2086 F pulseaudio
   /dev/snd/controlC1:  andreas2086 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=fa1b42ae-604b-448d-a294-6578ef07f7fe
  InstallationDate: Installed on 2018-10-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: System manufacturer System Product Name
  Package: linux (not installed)
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic 
root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-36-generic N/A
   linux-backports-modules-4.15.0-36-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-36-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  _MarkForUpload: True
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3305
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P9X79 DELUXE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3305:bd12/25/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79DELUXE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1796574

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796574/+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 1795116] Re: large performance regression (~20-40%) in wifi with 4.15.0-33 and later

[arQon]

> on channel 8(+4), 4.19 typically performed on par with -32 and older.

apparently only because of some fluke. the router switched to 4(+8) some
time in the past couple of days, and the newer kernels are certainly
sucking hard on that too:

---

Linux brix 4.15.0-32-generic #35~16.04.1-Ubuntu SMP Fri Aug 10 21:54:34 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  Current Frequency:2.427 GHz (Channel 4)
  Link Quality=70/70  Signal level=-36 dBm  
Sun 07-Oct-18 03:30
429,840,384 100%9.00MB/s0:00:45 (xfr#1, to-chk=0/1)
sent 429,945,420 bytes  received 35 bytes  9,449,350.66 bytes/sec

---

Linux brix 4.15.0-36-generic #39~16.04.1-Ubuntu SMP Tue Sep 25 08:59:23 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  Current Frequency:2.427 GHz (Channel 4)
  Link Quality=64/70  Signal level=-46 dBm  
Sun 07-Oct-18 05:05
429,840,384 100%6.46MB/s0:01:03 (xfr#1, to-chk=0/1)
sent 429,945,420 bytes  received 35 bytes  6,665,821.01 bytes/sec

---

this is a major regression. is there any activity on it upstream?

i can't imagine it's ALL wifi, or people would be screaming for blood,
but it would be good to at least get it in front of larry finger (the
rtl driver author) as a starting point.

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

Title:
  large performance regression (~20-40%) in wifi with 4.15.0-33 and
  later

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  16.04 install using the HWE stack. after several weeks of uptime on
  -32, an update to -34 showed a major drop in wifi throughput,
  dependent solely on the kernel chosen:

  $  uname -a && ./wifibench.sh 
  Linux brix 4.15.0-32-generic #35~16.04.1-Ubuntu SMP Fri Aug 10 21:54:34 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  Tue 25-Sep-18 06:07
  PlatformSDK-SVR2003R2.iso
  429,840,384 100%8.41MB/s0:00:48 (xfr#1, to-chk=0/1)
  sent 429,945,420 bytes  received 35 bytes  8,685,766.77 bytes/sec

  $  uname -a && ./wifibench.sh 
  Linux brix 4.15.0-34-generic #37~16.04.1-Ubuntu SMP Tue Aug 28 10:44:06 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  Tue 25-Sep-18 06:14
  PlatformSDK-SVR2003R2.iso
  429,840,384 100%4.83MB/s0:01:24 (xfr#1, to-chk=0/1)
  sent 429,945,420 bytes  received 35 bytes  5,028,601.81 bytes/sec

  (the script is a simple rsync from a NAS. nothing in the NAS, or the
  router, or the physical positions of the devices or etc etc has
  changed, let alone in those 7 minutes).

  there is no interference, no other devices connected, etc.
  prior to the transfer, the link quality is 62-64 and the signal similarly 
weaker because of power saving, but once packets are in flight it looks perfect:

  $  iwconfig 
  wlan0 IEEE 802.11  ESSID:""
Mode:Managed  Frequency:2.452 GHz  Access Point:    
Bit Rate=150 Mb/s   Tx-Power=20 dBm   
Retry short limit:7   RTS thr=2347 B   Fragment thr:off
Power Management:on
Link Quality=70/70  Signal level=10 dBm  
Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
Tx excessive retries:0  Invalid misc:15   Missed beacon:0

  the client is a J1900-based (baytrail) machine with a RTL8723BE wifi module. 
average performance while on -32 was consistently 70-80 Mb/s, over a period of 
several weeks. with -33 and later, it's generally 50-65.
  (that machine has no access to launchpad. i'll try apport-cli over the 
weekend).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795116/+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 1796574] [NEW] Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

[Andreas Lööw]

Public bug reported:

[1]
Using the default "radeon" driver result in black screen on boot. Waiting until 
what looks like X finish initializing, putting the computer to sleep and awake 
it again almost always works as a workaround.

dmesg:

[5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 5 
tries
[5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

And it looks like the DisplayPort is not initialized correctly.

"Black screen" in this context means nothing works (no TTY:s).

[2]
Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

[3]
Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].


[xrandr]
DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
   2560x1440 59.95*+
   1280x720  59.86  

[lshw -c display]
  *-display 
   description: VGA compatible controller
   product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
   vendor: Advanced Micro Devices, Inc. [AMD/ATI]
   physical id: 0
   bus info: pci@:02:00.0
   version: 00
   width: 64 bits
   clock: 33MHz
   capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
   configuration: driver=radeon latency=0
   resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d

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


** Tags: 4.15.0-36-generic amdgpu radeon

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

Title:
  Black screen on boot with AMD Radeon HD 7970/8970 OEM / R9 280X

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  [1]
  Using the default "radeon" driver result in black screen on boot. Waiting 
until what looks like X finish initializing, putting the computer to sleep and 
awake it again almost always works as a workaround.

  dmesg:

  [5.165441] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed: 
5 tries
  [5.165453] [drm:radeon_dp_link_train [radeon]] *ERROR* channel eq failed

  And it looks like the DisplayPort is not initialized correctly.

  "Black screen" in this context means nothing works (no TTY:s).

  [2]
  Disabling si_support (GCN 1.0) in grub results in system always boot correct 
from a shutdown state but awake from sleep doesn't work.

  [3]
  Switching to the experimental (for GCN 1.0 cards) amdgpu driver result in the 
same behavior as in [2].

  
  [xrandr]
  DisplayPort-1 connected primary 2560x1440+0+0 (normal left inverted right x 
axis y axis) 597mm x 336mm
 2560x1440 59.95*+
 1280x720  59.86  

  [lshw -c display]
*-display 
 description: VGA compatible controller
 product: Tahiti XT [Radeon HD 7970/8970 OEM / R9 280X]
 vendor: Advanced Micro Devices, Inc. [AMD/ATI]
 physical id: 0
 bus info: pci@:02:00.0
 version: 00
 width: 64 bits
 clock: 33MHz
 capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
 configuration: driver=radeon latency=0
 resources: irq:57 memory:c000-cfff memory:fbe0-fbe3 
ioport:e000(size=256) memory:c-d

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796574/+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 1796573] Status changed to Confirmed

[Ubuntu Kernel Bot]

This change was made by a bot.

** Changed in: linux (Ubuntu)
   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/1796573

Title:
  Keyboard backlight not working on ubuntu 18.10, but works on 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) 18.10
  2) 
  3) keyboard backlight turns on
  4) nothing

  I have ASUS s14 s406ua laptop and I can't turn my keyboard backlight
  on...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nadavshabtai   2215 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 19:21:02 2018
  InstallationDate: Installed on 2018-09-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3500 IMC Networks 
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X406UAR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=35bafd0c-f18c-4cc0-9146-d0f9f77447ff ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-28 (9 days ago)
  dmi.bios.date: 04/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X406UAR.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X406UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX406UAR.309:bd04/24/2018:svnASUSTeKCOMPUTERINC.:pnX406UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX406UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X406UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796573/+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 1796573] [NEW] Keyboard backlight not working on ubuntu 18.10, but works on 18.04

[nadav shatbai]

Public bug reported:

1) 18.10
2) 
3) keyboard backlight turns on
4) nothing

I have ASUS s14 s406ua laptop and I can't turn my keyboard backlight
on...

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: linux-image-4.18.0-8-generic 4.18.0-8.9
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  nadavshabtai   2215 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct  7 19:21:02 2018
InstallationDate: Installed on 2018-09-28 (9 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 13d3:3500 IMC Networks 
 Bus 001 Device 002: ID 13d3:56a2 IMC Networks 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. X406UAR
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=35bafd0c-f18c-4cc0-9146-d0f9f77447ff ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-4.18.0-8-generic N/A
 linux-backports-modules-4.18.0-8-generic  N/A
 linux-firmware1.175
SourcePackage: linux
UpgradeStatus: Upgraded to cosmic on 2018-09-28 (9 days ago)
dmi.bios.date: 04/24/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X406UAR.309
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X406UAR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX406UAR.309:bd04/24/2018:svnASUSTeKCOMPUTERINC.:pnX406UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX406UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: VivoBook
dmi.product.name: X406UAR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug cosmic

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

Title:
  Keyboard backlight not working on ubuntu 18.10, but works on 18.04

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  1) 18.10
  2) 
  3) keyboard backlight turns on
  4) nothing

  I have ASUS s14 s406ua laptop and I can't turn my keyboard backlight
  on...

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-8-generic 4.18.0-8.9
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nadavshabtai   2215 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 19:21:02 2018
  InstallationDate: Installed on 2018-09-28 (9 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:3500 IMC Networks 
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X406UAR
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-8-generic 
root=UUID=35bafd0c-f18c-4cc0-9146-d0f9f77447ff ro quiet splash vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-8-generic N/A
   linux-backports-modules-4.18.0-8-generic  N/A
   linux-firmware1.175
  SourcePackage: linux
  UpgradeStatus: Upgraded to cosmic on 2018-09-28 (9 days ago)
  dmi.bios.date: 04/24/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X406UAR.309
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X406UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX406UAR.309:bd04/24/2018:svnASUSTeKCOMPUTERINC.:pnX406UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX406UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: VivoBook
  dmi.product.name: X406UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

[Another User]

Earlier I've got kernel panic (no working init found) with IOMMU disabled in 
BIOS and without additional kernel parameters. 
And one strange thing: with Ubuntu my touchpad works in advanced multitouch 
mode but in bios is set basic mode. With Fedora 28 it works in basic mode and 
do not work when set to advanced.
P.S: Sorry for my bad English

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1776563/+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 1722478] Re: Two-finger scrolling no longer works after resuming from suspend

[Robin]

Commenting out blacklist i2c_i801 did end with mouse not working at all
after wakeup but adding psmouse.synaptics_intertouch=0 to grub did solve
the issue. I got an L440. Ubuntu 18.04 4.19rc1

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

Title:
  Two-finger scrolling no longer works after resuming from suspend

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

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1722478/+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 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

[Another User]

I have same problem with ACER Aspire a315-41-R19S (ryzen 2200u without dGPU). 
I'm using Ubuntu 18.04.1 with noapic kernel parameter (Manjaro don't work 
without it too). With suggested ivrs_ioapic[4]... parameters GUI is very slow.
Fedora boots without any additional kernel parameters, but message about buggy 
firmware present in dmesg

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

Status in amd:
  New
Status in Linux:
  Incomplete
Status in linux package in Ubuntu:
  Triaged
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  CPU: Ryzen 5 2500U
  VGA: Radeon 535
  Notebook: Acer Aspire A315

  This is a brand new notebook on the market with Ryzen 5/Radeon. 
  The default kernel of Ubuntu(18.04) hangs at loading with message:

  tsc: Refined TSC clocksource calibration: 1996.250 MHz
  clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: 
(...) 
  Soft lockup

  Using pci=noacpi kernel parameter kernel loads without any problem but
  my notebook produces more heat than on Win10. If I know right Acer
  notebooks need ACPI to the correct power management.

  The same thing happens on mainline 4.17,4.18rc1-2.
  BIOS upgrade to the latest version: 1.08 hasn't helped

  This problem has been reported upstream:
  https://bugzilla.kernel.org/show_bug.cgi?id=200087

  The latest correctly working kernel was 4.13.* but the heat problem
  was present with this too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/amd/+bug/1776563/+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 1742892] Re: [Power 9] ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Unable to start the guest with more than 1 thread on ubuntu1804 KVM host machine.

[bugproxy]

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

Title:
  [Power 9] ISST-LTE:KVM:Ubuntu1804:BostonLC:boslcp3: Unable to start
  the guest with more than 1 thread on ubuntu1804 KVM host machine.

Status in The Ubuntu-power-systems project:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Fix Released

Bug description:
  == Comment: #0 - INDIRA P. JOGA  - 2018-01-07 
13:18:32 ==
  Problem Description:
  ===
  Not able to start the ubutnu1804 guest with more than 1 thread on ubuntu1804 
KVM host machine

  Steps to re-create:
  ==
  > Installed Ubuntu1804 on boslcp3 host.

  root@boslcp3:/home# uname -a
  Linux boslcp3 4.13.0-17-generic #20-Ubuntu SMP Mon Nov 6 10:03:08 UTC 2017 
ppc64le ppc64le ppc64le GNU/Linux
  root@boslcp3:/home# uname -r
  4.13.0-17-generic

  > Installed qemu-kvm libvirt-bin ubuntu-vm-builder bridge-utils
  packages

  root@boslcp3:/home# virsh version
  Compiled against library: libvirt 3.6.0
  Using library: libvirt 3.6.0
  Using API: QEMU 3.6.0
  Running hypervisor: QEMU 2.10.1

  > root@boslcp3:~# ppc64_cpu --smt
  SMT is off

  > Defined the guest boslcp3g1 from host machine

  root@boslcp3:/home# virsh list --all
   IdName   State
  
   - boslcp3g1  shut off

  Please cherry pick

  commit 45c940ba490df28cb87b993981a5f63df6bbb8db
  Author: Paul Mackerras 
  Date:   Fri Nov 18 17:43:30 2016 +1100

  KVM: PPC: Book3S HV: Treat POWER9 CPU threads as independent subcores


  > Started the guest and it fails with the error

  root@boslcp3:~# virsh start --console boslcp3g1
  error: Failed to start domain boslcp3g1
  error: internal error: process exited while connecting to monitor: 
2018-01-05T02:54:37.762120Z qemu-system-ppc64: -chardev pty,id=charserial0: 
char device redirected to /dev/pts/3 (label charserial0)
  2018-01-05T02:54:37.829236Z qemu-system-ppc64: Cannot support more than 1 
threads on PPC with KVM

  > Unable to start the guest with more than 1 Thread from Ubuntu1804
  KVM host machine.

  XML:
  
  root@boslcp3:/home# virsh dumpxml boslcp3g1
  
boslcp3g1
95374879-0ed3-4562-a00f-e47d9aaf285c
10485760
6291456
6291456

  

  

32

  /machine


  hvm
  
  
  


  
  


  power9
  
  


  


destroy
restart
coredump-restart

  /usr/bin/qemu-system-ppc64 
  




  
  




  
  




  
  

  
  

  
  


  
  


  
  




  
  


  
  


  
  

  
  

  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1742892/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[Unkraut]

Please add rollback instructions. I'm now stuck with a broken intel
driver.

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-prime source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[Unkraut]

I tested this on a Dell XPS 15 9570. 
When using the kernel is 4.18.12-041812-generic, boot options: 
acpi_rev_override=5 acpi_osi=Linux scsi_mod.use_blk_mq=1 and selecting nvidia I 
don't get any graphical login.I have to switch to intel via the recovery root 
console.

When selecting intel, power consumption is between 8 and 9 W which means nvidia 
GPU is off.
After standby the screen is corrupted.

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-prime source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1778011/+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 1685794] Re: Boot delayed for about 90 seconds until 'random: crng init done'

[gscscnd]

** Bug watch added: Debian Bug tracker #910504
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910504

** Also affects: broadcom-sta (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910504
   Importance: Unknown
   Status: Unknown

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

Title:
  Boot delayed for about 90 seconds until 'random: crng init done'

Status in linux package in Ubuntu:
  Confirmed
Status in broadcom-sta package in Debian:
  Unknown

Bug description:

  Shortened dmesg output, notice the unnaturally long delay before crng
  init finishes:

  [8.533630] Bluetooth: hci0: Intel Bluetooth firmware patch completed and 
activated
  [8.542239] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1b.0/sound/card1/input18
  [8.542313] input: HDA Intel PCH Line as 
/devices/pci:00/:00:1b.0/sound/card1/input19
  [8.542382] input: HDA Intel PCH Dock Line Out as 
/devices/pci:00/:00:1b.0/sound/card1/input20
  [8.542449] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1b.0/sound/card1/input21
  [8.544240] cdc_ether 2-6:2.0 usb0: register 'cdc_ether' at 
usb-:00:14.0-6, CDC Ethernet Device, 02:1e:10:1f:00:00
  [8.544271] usbcore: registered new interface driver cdc_ether
  [8.637660] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
  [8.654022] input: HP WMI hotkeys as /devices/virtual/input/input22
  [8.688226] cdc_ether 2-6:2.0 enp0s20u6c2: renamed from usb0
  [8.713288] iwlwifi :02:00.0 wlo1: renamed from wlan0
  [9.804308] input: ST LIS3LV02DL Accelerometer as 
/devices/platform/lis3lv02d/input/input23
  [   98.327857] random: crng init done
  [   98.330072] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   98.330073] Bluetooth: BNEP filters: protocol multicast
  [   98.330077] Bluetooth: BNEP socket layer initialized
  [   98.443281] kauditd_printk_skb: 90 callbacks suppressed
  [   98.492927] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
  [   98.681030] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
  [   98.685672] IPv6: ADDRCONF(NETDEV_UP): enp0s20u6c2: link is not ready
  [   98.685789] cdc_ether 2-6:2.0 enp0s20u6c2: kevent 12 may have been dropped
  [   98.688384] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
  [   98.690915] iwlwifi :02:00.0: L1 Enabled - LTR Enabled

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: 
boot/vmlinuz-4.10.0-19-generic]
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/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:Unity7
  Date: Mon Apr 24 14:58:33 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-18 (5 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=9fb9fc1d-15a4-4e98-a2ae-bf572e0900d5 ro quiet splash vt.handoff=7
  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.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.37
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: USH452L0B1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685794/+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 1796542] Re: Silent corruption in Linux kernel 4.15

[Vasil Kolev]

Thank you for looking at this bug report.

We have some additional information.

qemu/kvm with cache=none (common) and aio=threads (default) is required
to trigger the bug. aio=native (another common option) does not trigger
it in our testing.

We applied the following patches on top of Ubuntu-4.15.0-36.39.

commit 0aa69fd32a5f766e997ca8ab4723c5a1146efa8b - block: add a lower-level 
bio_add_page interface
commit b403ea2404889e1227812fa9657667a1deb9c694 - block: 
bio_iov_iter_get_pages: fix size of last iovec
commit 9362dd1109f87a9d0a798fbc890cb339c171ed35 - blkdev: 
__blkdev_direct_IO_simple: fix leak in error case
commit 17d51b10d7773e4618bcac64648f30f12d4078fb - block: 
bio_iov_iter_get_pages: pin more pages for multi-segment IOs

The first one introduces a helper function, and the next three are the
upstream patchset that fixes the issue.

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

Title:
  Silent corruption in Linux kernel 4.15

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  TLDR: commit 72ecad22d9f198aafee64218512e02ffa7818671 (in v4.10)
  introduced silent data corruption for O_DIRECT uses, it's fixed in
  17d51b10d7773e4618bcac64648f30f12d4078fb (in v4.18)

  A silent data corruption was introduced in v4.10-rc1 with commit
  72ecad22d9f198aafee64218512e02ffa7818671 and was fixed in v4.18-rc7
  with commit 17d51b10d7773e4618bcac64648f30f12d4078fb. It affects users
  of O_DIRECT, in our case a KVM virtual machine with drives which use
  qemu's "cache=none" option.

  This is the commit which fixes the issue:
  -
  commit 17d51b10d7773e4618bcac64648f30f12d4078fb
  Author: Martin Wilck 
  Date:   Wed Jul 25 23:15:09 2018 +0200

  block: bio_iov_iter_get_pages: pin more pages for multi-segment
  IOs

  bio_iov_iter_get_pages() currently only adds pages for the next non-zero
  segment from the iov_iter to the bio. That's suboptimal for callers,
  which typically try to pin as many pages as fit into the bio. This patch
  converts the current bio_iov_iter_get_pages() into a static helper, and
  introduces a new helper that allocates as many pages as

   1) fit into the bio,
   2) are present in the iov_iter,
   3) and can be pinned by MM.

  Error is returned only if zero pages could be pinned. Because of 3), a
  zero return value doesn't necessarily mean all pages have been pinned.
  Callers that have to pin every page in the iov_iter must still call this
  function in a loop (this is currently the case).

  This change matters most for __blkdev_direct_IO_simple(), which calls
  bio_iov_iter_get_pages() only once. If it obtains less pages than
  requested, it returns a "short write" or "short read", and
  __generic_file_write_iter() falls back to buffered writes, which may
  lead to data corruption.

  Fixes: 72ecad22d9f1 ("block: support a full bio worth of IO for 
simplified bdev direct-io")
  Reviewed-by: Christoph Hellwig 
  Signed-off-by: Martin Wilck 
  Signed-off-by: Jens Axboe 
  -

  Since there were a lot of components involved in the initial report to
  us (xfs, guest kernel, guest virtio drivers, qemu, host kernel,
  storage system), we had to isolate it. This is the commit which fixes
  the data corruption bug. We created a reliable reproduction and tested
  with the patch and without the patch. We also created a version of the
  kernel which prints when the data-corrupting path in the kernel is
  triggered.

  > 1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  # lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  > 2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  # apt-cache policy linux-image-4.15.0-36-generic
  linux-image-4.15.0-36-generic:
   Installed: 4.15.0-36.39
   Candidate: 4.15.0-36.39
   Version table:
  *** 4.15.0-36.39 500
500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status

  > 3) What you expected to happen

  We ran a fio random write workload over 8x 512MB files over XFS in guest OS, 
over qemu/kvm, over kernel 4.15.0-36.39-generic.
  qemu-system was configured with cache=none, which means Direct IO. This is a 
very common configuration.
  qemu-system was with aio=threads -- the default.

  We were expecting no data corruption.

  > 4) What happened instead

  The guest filesystem was corrupted.

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

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

[Kernel-packages] [Bug 1796542] Re: Silent corruption in Linux kernel 4.15

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Silent corruption in Linux kernel 4.15

Status in linux-signed package in Ubuntu:
  Confirmed

Bug description:
  TLDR: commit 72ecad22d9f198aafee64218512e02ffa7818671 (in v4.10)
  introduced silent data corruption for O_DIRECT uses, it's fixed in
  17d51b10d7773e4618bcac64648f30f12d4078fb (in v4.18)

  A silent data corruption was introduced in v4.10-rc1 with commit
  72ecad22d9f198aafee64218512e02ffa7818671 and was fixed in v4.18-rc7
  with commit 17d51b10d7773e4618bcac64648f30f12d4078fb. It affects users
  of O_DIRECT, in our case a KVM virtual machine with drives which use
  qemu's "cache=none" option.

  This is the commit which fixes the issue:
  -
  commit 17d51b10d7773e4618bcac64648f30f12d4078fb
  Author: Martin Wilck 
  Date:   Wed Jul 25 23:15:09 2018 +0200

  block: bio_iov_iter_get_pages: pin more pages for multi-segment
  IOs

  bio_iov_iter_get_pages() currently only adds pages for the next non-zero
  segment from the iov_iter to the bio. That's suboptimal for callers,
  which typically try to pin as many pages as fit into the bio. This patch
  converts the current bio_iov_iter_get_pages() into a static helper, and
  introduces a new helper that allocates as many pages as

   1) fit into the bio,
   2) are present in the iov_iter,
   3) and can be pinned by MM.

  Error is returned only if zero pages could be pinned. Because of 3), a
  zero return value doesn't necessarily mean all pages have been pinned.
  Callers that have to pin every page in the iov_iter must still call this
  function in a loop (this is currently the case).

  This change matters most for __blkdev_direct_IO_simple(), which calls
  bio_iov_iter_get_pages() only once. If it obtains less pages than
  requested, it returns a "short write" or "short read", and
  __generic_file_write_iter() falls back to buffered writes, which may
  lead to data corruption.

  Fixes: 72ecad22d9f1 ("block: support a full bio worth of IO for 
simplified bdev direct-io")
  Reviewed-by: Christoph Hellwig 
  Signed-off-by: Martin Wilck 
  Signed-off-by: Jens Axboe 
  -

  Since there were a lot of components involved in the initial report to
  us (xfs, guest kernel, guest virtio drivers, qemu, host kernel,
  storage system), we had to isolate it. This is the commit which fixes
  the data corruption bug. We created a reliable reproduction and tested
  with the patch and without the patch. We also created a version of the
  kernel which prints when the data-corrupting path in the kernel is
  triggered.

  > 1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  # lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  > 2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  # apt-cache policy linux-image-4.15.0-36-generic
  linux-image-4.15.0-36-generic:
   Installed: 4.15.0-36.39
   Candidate: 4.15.0-36.39
   Version table:
  *** 4.15.0-36.39 500
500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status

  > 3) What you expected to happen

  We ran a fio random write workload over 8x 512MB files over XFS in guest OS, 
over qemu/kvm, over kernel 4.15.0-36.39-generic.
  qemu-system was configured with cache=none, which means Direct IO. This is a 
very common configuration.
  qemu-system was with aio=threads -- the default.

  We were expecting no data corruption.

  > 4) What happened instead

  The guest filesystem was corrupted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1796542/+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 1685794] Re: Boot delayed for about 90 seconds until 'random: crng init done'

[gscscnd]

Debian stretch with backports (kernels 4.17 and 4.18) on a Dell Latitude
E6420 with a Dell Wireless 1530 (Broadcom BCM43228) card.

This problem (although the delay is of about three minutes) has started
occurring on every boot after installing broadcom-sta-dkms (drivers for
the above wireless card). Installing rng-tools (or uninstalling
broadcom-sta-dkms) fixes it.

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

Title:
  Boot delayed for about 90 seconds until 'random: crng init done'

Status in linux package in Ubuntu:
  Confirmed

Bug description:

  Shortened dmesg output, notice the unnaturally long delay before crng
  init finishes:

  [8.533630] Bluetooth: hci0: Intel Bluetooth firmware patch completed and 
activated
  [8.542239] input: HDA Intel PCH Mic as 
/devices/pci:00/:00:1b.0/sound/card1/input18
  [8.542313] input: HDA Intel PCH Line as 
/devices/pci:00/:00:1b.0/sound/card1/input19
  [8.542382] input: HDA Intel PCH Dock Line Out as 
/devices/pci:00/:00:1b.0/sound/card1/input20
  [8.542449] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1b.0/sound/card1/input21
  [8.544240] cdc_ether 2-6:2.0 usb0: register 'cdc_ether' at 
usb-:00:14.0-6, CDC Ethernet Device, 02:1e:10:1f:00:00
  [8.544271] usbcore: registered new interface driver cdc_ether
  [8.637660] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
  [8.654022] input: HP WMI hotkeys as /devices/virtual/input/input22
  [8.688226] cdc_ether 2-6:2.0 enp0s20u6c2: renamed from usb0
  [8.713288] iwlwifi :02:00.0 wlo1: renamed from wlan0
  [9.804308] input: ST LIS3LV02DL Accelerometer as 
/devices/platform/lis3lv02d/input/input23
  [   98.327857] random: crng init done
  [   98.330072] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   98.330073] Bluetooth: BNEP filters: protocol multicast
  [   98.330077] Bluetooth: BNEP socket layer initialized
  [   98.443281] kauditd_printk_skb: 90 callbacks suppressed
  [   98.492927] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
  [   98.681030] IPv6: ADDRCONF(NETDEV_UP): enp0s25: link is not ready
  [   98.685672] IPv6: ADDRCONF(NETDEV_UP): enp0s20u6c2: link is not ready
  [   98.685789] cdc_ether 2-6:2.0 enp0s20u6c2: kevent 12 may have been dropped
  [   98.688384] IPv6: ADDRCONF(NETDEV_UP): wlo1: link is not ready
  [   98.690915] iwlwifi :02:00.0: L1 Enabled - LTR Enabled

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: linux-image-4.10.0-19-generic 4.10.0-19.21 [modified: 
boot/vmlinuz-4.10.0-19-generic]
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC1D0', '/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', 
'/dev/snd/controlC1', '/dev/snd/hwC0D0', '/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:Unity7
  Date: Mon Apr 24 14:58:33 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-04-18 (5 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Hewlett-Packard HP EliteBook 840 G1
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic.efi.signed 
root=UUID=9fb9fc1d-15a4-4e98-a2ae-bf572e0900d5 ro quiet splash vt.handoff=7
  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.10.0-19-generic N/A
   linux-backports-modules-4.10.0-19-generic  N/A
   linux-firmware 1.164
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/23/2016
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L71 Ver. 01.37
  dmi.board.name: 198F
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 15.59
  dmi.chassis.asset.tag: USH452L0B1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL71Ver.01.37:bd05/23/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10203:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 840 G1
  dmi.product.version: A3009DD10203
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1685794/+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 1796553] [NEW] BT mouse getting reset during operation

[Ralf Hildebrandt]

Public bug reported:


(note: It's unclear to me if that's a kernel regression or an issue with bluez)


I've been using this particular combination of Bluetooth mouse ("TECKNET 
BM306") & laptop ("Dell Latitude E7240") for over a year now.

It used to work with 18.04 and 17.10, but with 18.10 I'm encountering a
strange disconnect behaviour:

1) Mouse is working ok
2) Mouse suddenly stops
3) Disabling and enabling bluetooth on the laptop makes the mouse work again.

when this happens, dmesg reports:

[57812.977570] usb 1-1.3: reset full-speed USB device number 18 using
ehci-pci

Disabling bluetooth and enabling it again results in:

[57833.455866] usb 1-1.3: USB disconnect, device number 18
[57833.455948] Bluetooth: hci0: turning off Intel device LED failed (-19)
[57836.905656] usb 1-1.3: new full-speed USB device number 19 using ehci-pci
[57837.016248] usb 1-1.3: New USB device found, idVendor=8087, idProduct=07dc, 
bcdDevice= 0.01
[57837.016253] usb 1-1.3: New USB device strings: Mfr=0, Product=0, 
SerialNumber=0
[57837.030092] Bluetooth: hci0: read Intel version: 370710018002030d00
[57837.030169] Bluetooth: hci0: Intel Bluetooth firmware file: 
intel/ibt-hw-37.7.10-fw-1.80.2.3.d.bseq
[57837.251206] Bluetooth: hci0: Intel firmware patch completed and activated
[57841.724368] hid-generic 0005:0A5C:0001.001F: unknown main item tag 0x0
[57841.724587] input: TECKNET BM306 Mouse as 
/devices/pci:00/:00:1d.0/usb1/1-1/1-1.3/1-1.3:1.0/bluetooth/hci0/hci0:256/0005:0A5C:0001.001F/input/input78
[57841.724873] hid-generic 0005:0A5C:0001.001F: input,hidraw0: BLUETOOTH HID 
v1.29 Mouse [TECKNET BM306] on fc:f8:ae:45:3c:05

$ bluetoothctl --version
bluetoothctl: 5.50

$ hciconfig -a
hci0:   Type: Primary  Bus: USB
BD Address: FC:F8:AE:45:3C:05  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN 
RX bytes:52465 acl:3355 sco:0 events:222 errors:0
TX bytes:28384 acl:13 sco:0 commands:170 errors:0
Features: 0xff 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
Link policy: RSWITCH HOLD SNIFF 
Link mode: SLAVE ACCEPT 
Name: 'ChromeLinux_AA14'
Class: 0x0c010c
Service Classes: Rendering, Capturing
Device Class: Computer, Laptop
HCI Version: 4.0 (0x6)  Revision: 0x500
LMP Version: 4.0 (0x6)  Subversion: 0x500
Manufacturer: Intel Corp. (2)

$ bluetoothctl
Agent registered
[TECKNET BM306]# show
Controller FC:F8:AE:45:3C:05 (public)
Name: humbaba
Alias: ChromeLinux_AA14
Class: 0x000c010c
Powered: yes
Discoverable: no
Pairable: yes
UUID: Headset AG(1112--1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Generic Access Profile(1800--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: Audio Source  (110a--1000-8000-00805f9b34fb)
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: Headset   (1108--1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d0532
Discovering: no
[TECKNET BM306]# devices
Device 20:9B:A5:68:AE:67 SoundBuds Flow
Device DC:2C:26:01:24:23 TECKNET BM306
Device 88:71:E5:0E:6B:99 Echo-HPT
Device 00:0B:E4:A0:A2:14 Nokia BH-103
Device A8:96:75:8B:4F:49 Moto G5S Plus
Device 00:02:5B:20:75:3C Trust SPK-02
Device 88:75:98:F2:5C:9E NS9+
Device 00:E0:4C:D5:E0:F5 SoundCore mini
[TECKNET BM306]# info DC:2C:26:01:24:23
Device DC:2C:26:01:24:23 (public)
Name: TECKNET BM306
Alias: TECKNET BM306
Class: 0x0580
Icon: input-mouse
Paired: yes
Trusted: yes
Blocked: no
Connected: yes
LegacyPairing: no
UUID: Service Discovery Serve.. (1000--1000-8000-00805f9b34fb)
UUID: Human Interface Device... (1124--1000-8000-00805f9b34fb)
UUID: PnP Information   (1200--1000-8000-00805f9b34fb)
Modalias: usb:v0A5Cp0001d0129


$ rfkill list
2: dell-wifi: Wireless LAN
Soft blocked: no
Hard blocked: no
3: dell-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
4: dell-wwan: Wireless WAN
Soft blocked: yes
Hard blocked: no
5: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
46: nfc0: NFC
Soft blocked: no
Hard blocked: no
48: hci0: Bluetooth
Soft blocked: no
Hard blocked: no

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: bluez 5.50-0ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-7.8-generic 4.18.5
Uname: Linux 4.18.0-7-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon 

[Kernel-packages] [Bug 1796550] Re: Separate keyboard brightness control keys (down/up) don't work

[Daniel van Vugt]

Upstream: https://gitlab.gnome.org/GNOME/gnome-shell/issues/636

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

Title:
  Separate keyboard brightness control keys (down/up) don't work

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/636

  ---

  On laptops with two separate (down,up) keys to control the backlit
  keyboard, both keys seem to do nothing. The OSD for the backlit
  keyboard is displayed but no progress bar and no actual effect to the
  backlight. Almost as if the shell only understands laptops with a
  single key for controlling the keyboard backlight...

  Bug verified in cosmic on:
    * Asus UX331UAL
    * Apple Macbook Pro 12,1
    * Apple Macbook Air

  All of them have these keys and they all fail in the same way. However
  it is not a kernel bug. The kernel interface
  (/sys/class/leds/*::kbd_backlight/*) works when I write to it
  directly. This seems to be a problem with Gnome Shell only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 13:41:50 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (25 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796550/+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 1796550] [NEW] Separate keyboard brightness control keys (down/up) don't work

[Daniel van Vugt]

Public bug reported:

https://gitlab.gnome.org/GNOME/gnome-shell/issues/636

---

On laptops with two separate (down,up) keys to control the backlit
keyboard, both keys seem to do nothing. The OSD for the backlit keyboard
is displayed but no progress bar and no actual effect to the backlight.
Almost as if the shell only understands laptops with a single key for
controlling the keyboard backlight...

Bug verified in cosmic on:
  * Asus UX331UAL
  * Apple Macbook Pro 12,1
  * Apple Macbook Air

All of them have these keys and they all fail in the same way. However
it is not a kernel bug. The kernel interface
(/sys/class/leds/*::kbd_backlight/*) works when I write to it directly.
This seems to be a problem with Gnome Shell only.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.30.0-3ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
Uname: Linux 4.18.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct  7 13:41:50 2018
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-11 (25 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-shell (Ubuntu)
 Importance: Medium
 Status: New

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


** Tags: amd64 apport-bug cosmic wayland-session

** Summary changed:

- Keyboard brightness controls don't work
+ Separate keyboard brightness control keys (down/up) don't work

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

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

** Description changed:

+ https://gitlab.gnome.org/GNOME/gnome-shell/issues/636
+ 
+ ---
+ 
  On laptops with two separate (down,up) keys to control the backlit
  keyboard, both keys seem to do nothing. The OSD for the backlit keyboard
  is displayed but no progress bar and no actual effect to the backlight.
  Almost as if the shell only understands laptops with a single key for
  controlling the keyboard backlight...
  
  Bug verified in cosmic on:
-   * Asus UX331UAL
-   * Apple Macbook Pro 12,1
-   * Apple Macbook Air
+   * Asus UX331UAL
+   * Apple Macbook Pro 12,1
+   * Apple Macbook Air
  
  All of them have these keys and they all fail in the same way. However
  it is not a kernel bug. The kernel interface
  (/sys/class/leds/*::kbd_backlight/*) works when I write to it directly.
  This seems to be a problem with Gnome Shell only.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 13:41:50 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (25 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Separate keyboard brightness control keys (down/up) don't work

Status in gnome-shell package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Invalid

Bug description:
  https://gitlab.gnome.org/GNOME/gnome-shell/issues/636

  ---

  On laptops with two separate (down,up) keys to control the backlit
  keyboard, both keys seem to do nothing. The OSD for the backlit
  keyboard is displayed but no progress bar and no actual effect to the
  backlight. Almost as if the shell only understands laptops with a
  single key for controlling the keyboard backlight...

  Bug verified in cosmic on:
    * Asus UX331UAL
    * Apple Macbook Pro 12,1
    * Apple Macbook Air

  All of them have these keys and they all fail in the same way. However
  it is not a kernel bug. The kernel interface
  (/sys/class/leds/*::kbd_backlight/*) works when I write to it
  directly. This seems to be a problem with Gnome Shell only.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-shell 3.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-8.9-generic 4.18.7
  Uname: Linux 4.18.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu11
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Oct  7 13:41:50 2018
  DisplayManager: gdm3
  InstallationDate: Installed on 2018-09-11 (25 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1796550/+subscriptions

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

[Kernel-packages] [Bug 1728385] Re: Reduce/hide excessive logging when Bluetooth is intentionally disabled: "Failed to set mode: Blocked through rfkill (0x12)"

[joshas]

Issue still exists in Ubuntu 18.04.1 LTS

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

Title:
  Reduce/hide excessive logging when Bluetooth is intentionally
  disabled: "Failed to set mode: Blocked through rfkill (0x12)"

Status in bluez package in Ubuntu:
  Expired

Bug description:
  Ubuntu 17.10, bluetooth disabled, get error in Logs:
  bluetoothd: Failed to set mode: Blocked through rfkill (0x12)
  --- 
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 17.10
  InstallationDate: Installed on 2017-10-24 (6 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20GJ001HMH
  Package: bluez 5.46-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Tags:  artful wayland-session
  Uname: Linux 4.13.0-16-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0CET26W (1.14 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20GJ001HMH
  dmi.board.vendor: LENOVO
  dmi.board.version: S
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0CET26W(1.14):bd06/13/2016:svnLENOVO:pn20GJ001HMH:pvrThinkPadS2:rvnLENOVO:rn20GJ001HMH:rvrS:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad S2
  dmi.product.name: 20GJ001HMH
  dmi.product.version: ThinkPad S2
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:B3:18:52:20:69  ACL MTU: 1021:4  SCO MTU: 96:6
DOWN 
RX bytes:14933 acl:0 sco:0 events:2414 errors:0
TX bytes:596764 acl:0 sco:0 commands:2412 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1728385/+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 1777279] Re: Resume from suspend to RAM fails with nvidia-graphics-drivers-390

[Gerhard Hagerer]

I  got a workaround for suspend working on Ubuntu 18.04 with a NVIDIA
GeForce GTX 1050 Mobile and proprietary nvidia drivers 390. I installed
pm-suspend via ```sudo apt-get install pm-utils```.  Then, I switch from
Gnome Shell to the terminal via Ctrl+Alt+f6. After  the login, I do
```sudo pm-suspend```. After waking up from standby, I  change back to
Gnome Shell via Ctrl+Alt+f1. Done!

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

Title:
  Resume from suspend to RAM fails with nvidia-graphics-drivers-390

Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Confirmed

Bug description:
  After suspending to RAM when resuming only black screen is visible with 
frozen mouse cursor. Can't switch to console and reset is required. When trying 
to suspend to RAM with pm-suspend command system doesn't suspend at all, you 
can find pm-suspend.log file attached. With default nouveau drivers system 
resumes fine however hangs forever on shutdown.
  My specs:
  AMD Ryzen 5 1600
  Kingston Predator DDR4 8GB
  Gigabyte GA-AB350N-Gaming WIFI
  MSI GeForce GTX 1060 AERO ITX
  SSD Crucial MX500 500GB

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-22-generic 4.15.0-22.24
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jaroslaw   1386 F pulseaudio
   /dev/snd/controlC1:  jaroslaw   1386 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Sat Jun 16 21:38:21 2018
  InstallationDate: Installed on 2018-05-16 (31 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. AB350N-Gaming WIFI
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=b5a92bcf-517e-4b97-ab26-84dbab8247c5 ro quiet splash resume=/dev/sda2 
resume_offset=19075072 vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-22-generic N/A
   linux-backports-modules-4.15.0-22-generic  N/A
   linux-firmware 1.173.1
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/17/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23d
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350N-Gaming WIFI-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23d:bd04/17/2018:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: AB350N-Gaming WIFI
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1777279/+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 1796542] [NEW] Silent corruption in Linux kernel 4.15

[Vasil Kolev]

Public bug reported:

TLDR: commit 72ecad22d9f198aafee64218512e02ffa7818671 (in v4.10)
introduced silent data corruption for O_DIRECT uses, it's fixed in
17d51b10d7773e4618bcac64648f30f12d4078fb (in v4.18)

A silent data corruption was introduced in v4.10-rc1 with commit
72ecad22d9f198aafee64218512e02ffa7818671 and was fixed in v4.18-rc7 with
commit 17d51b10d7773e4618bcac64648f30f12d4078fb. It affects users of
O_DIRECT, in our case a KVM virtual machine with drives which use qemu's
"cache=none" option.

This is the commit which fixes the issue:
-
commit 17d51b10d7773e4618bcac64648f30f12d4078fb
Author: Martin Wilck 
Date:   Wed Jul 25 23:15:09 2018 +0200

block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs

bio_iov_iter_get_pages() currently only adds pages for the next non-zero
segment from the iov_iter to the bio. That's suboptimal for callers,
which typically try to pin as many pages as fit into the bio. This patch
converts the current bio_iov_iter_get_pages() into a static helper, and
introduces a new helper that allocates as many pages as

 1) fit into the bio,
 2) are present in the iov_iter,
 3) and can be pinned by MM.

Error is returned only if zero pages could be pinned. Because of 3), a
zero return value doesn't necessarily mean all pages have been pinned.
Callers that have to pin every page in the iov_iter must still call this
function in a loop (this is currently the case).

This change matters most for __blkdev_direct_IO_simple(), which calls
bio_iov_iter_get_pages() only once. If it obtains less pages than
requested, it returns a "short write" or "short read", and
__generic_file_write_iter() falls back to buffered writes, which may
lead to data corruption.

Fixes: 72ecad22d9f1 ("block: support a full bio worth of IO for simplified 
bdev direct-io")
Reviewed-by: Christoph Hellwig 
Signed-off-by: Martin Wilck 
Signed-off-by: Jens Axboe 
-

Since there were a lot of components involved in the initial report to
us (xfs, guest kernel, guest virtio drivers, qemu, host kernel, storage
system), we had to isolate it. This is the commit which fixes the data
corruption bug. We created a reliable reproduction and tested with the
patch and without the patch. We also created a version of the kernel
which prints when the data-corrupting path in the kernel is triggered.

> 1) The release of Ubuntu you are using, via 'lsb_release -rd' or
System -> About Ubuntu

# lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04

> 2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center

# apt-cache policy linux-image-4.15.0-36-generic
linux-image-4.15.0-36-generic:
 Installed: 4.15.0-36.39
 Candidate: 4.15.0-36.39
 Version table:
*** 4.15.0-36.39 500
500 http://archive.ubuntu.com/ubuntu bionic-security/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
100 /var/lib/dpkg/status

> 3) What you expected to happen

We ran a fio random write workload over 8x 512MB files over XFS in guest OS, 
over qemu/kvm, over kernel 4.15.0-36.39-generic.
qemu-system was configured with cache=none, which means Direct IO. This is a 
very common configuration.
qemu-system was with aio=threads -- the default.

We were expecting no data corruption.

> 4) What happened instead

The guest filesystem was corrupted.

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

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

Title:
  Silent corruption in Linux kernel 4.15

Status in linux-signed package in Ubuntu:
  New

Bug description:
  TLDR: commit 72ecad22d9f198aafee64218512e02ffa7818671 (in v4.10)
  introduced silent data corruption for O_DIRECT uses, it's fixed in
  17d51b10d7773e4618bcac64648f30f12d4078fb (in v4.18)

  A silent data corruption was introduced in v4.10-rc1 with commit
  72ecad22d9f198aafee64218512e02ffa7818671 and was fixed in v4.18-rc7
  with commit 17d51b10d7773e4618bcac64648f30f12d4078fb. It affects users
  of O_DIRECT, in our case a KVM virtual machine with drives which use
  qemu's "cache=none" option.

  This is the commit which fixes the issue:
  -
  commit 17d51b10d7773e4618bcac64648f30f12d4078fb
  Author: Martin Wilck 
  Date:   Wed Jul 25 23:15:09 2018 +0200

  block: bio_iov_iter_get_pages: pin more pages for multi-segment
  IOs

  bio_iov_iter_get_pages() currently only adds pages for the next non-zero
  segment from the iov_iter to the bio. That's suboptimal for callers,
  which typically try to pin as many pages as fit into the bio. This patch
  converts the current bio_iov_iter_get_pages() into a static helper, and
  introduces a new helper 

[Kernel-packages] [Bug 1778011] Re: SRU: PRIME Power Saving mode draws too much power

[ubname]

I tested with i7 Broadwell and GTX 850M and I think it works. I'm
sending the log also.


** Attachment added: "i7broadweel_GTX850M_gpu-manager.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1778011/+attachment/5198239/+files/i7broadweel_GTX850M_gpu-manager.log

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

Title:
  SRU: PRIME Power Saving mode draws too much power

Status in HWE Next:
  New
Status in gdm3 package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in nvidia-prime package in Ubuntu:
  Fix Released
Status in nvidia-settings package in Ubuntu:
  Fix Released
Status in ubuntu-drivers-common package in Ubuntu:
  Fix Released
Status in gdm3 source package in Bionic:
  Fix Released
Status in nvidia-graphics-drivers-390 source package in Bionic:
  Fix Committed
Status in nvidia-prime source package in Bionic:
  Fix Committed
Status in nvidia-settings source package in Bionic:
  Fix Committed
Status in ubuntu-drivers-common source package in Bionic:
  Fix Committed

Bug description:
  SRU Request:

  [Impact]
  Relying on the nouveau driver and on the vga switcheroo (to get around a 
change in systemd LP: #1777099) caused increased power consumption, and slowed 
down the switching process.

  Furthermore, if the main X/Xwayland session was started by Gdm when
  the nvidia driver was loaded, the session will keep the nvidia module
  loaded, and prevent the system from switching off the dGPU. Also, the
  nouveau driver will be loaded, if nvidia is not, and this can cause
  problems to unsupported NVIDIA GPUs.

  The solution involves the following changes:

  1) Solving the problem in systemd (LP: #1777099)

  2) Adding code in gpu-manager and in nvidia-prime to unload the nvidia
  modules, and to allow the PCI device to sleep.

  3) Making a slight change to the current patch in Gdm, used to call
  the PRIME scripts before and after a Gdm session (so that gpu-manager
  gets actually called on log out)

  4) Adding code in gpu-manager to kill the main X/Xwayland session on
  log out, if the session is preventing us from unloading the nvidia
  driver. A new X/Xwayland session will be created after unload the
  module.

  5) Removing the systemd service that loads nouveau from the nvidia
  packages.

  [Test Case]
  1) Enable the -proposed repository, and install the new 
"ubuntu-drivers-common", nvidia drivers, nvidia-prime, and gdm3 *

  2) Make sure the nvidia packages are installed, and enable performance mode 
(if it is already enabled, call "sudo prime-select intel" first):
  sudo prime-select nvidia

  3) Restart your computer and attach your /var/log/gpu-manager.log. see
  if the system boots correctly. If unsure, please attach your /var/log
  /gpu-manager.log and /var/log/Xorg.0.log

  4) Select power saving mode:
  sudo prime-select intel

  5) Log out and log back in

  6) Check if the nvidia driver is still loaded:
  lsmod | grep nvidia

  [Regression Potential]
  Low, as hybrid graphics support does not work correctly, and the changes only 
affect this use case.

  _
  * Steps to test the updates:

  1) Enable the bionic-proposed repositories

  2) Create /etc/apt/preferences.d/proposed-updates with the following
  content:

  Package: *
  Pin: release a=bionic-proposed
  Pin-Priority: 400

  3) Update the list of packages:

  sudo apt-get update

  4) Install the packages from -proposed using the following command:

  sudo apt install nvidia-driver-390/bionic-proposed gdm3/bionic-
  proposed ubuntu-drivers-common/bionic-proposed nvidia-prime/bionic-
  proposed nvidia-settings/bionic-proposed libnvidia-gl-390/bionic-
  proposed libnvidia-compute-390/bionic-proposed libnvidia-decode-390
  /bionic-proposed libnvidia-encode-390/bionic-proposed libnvidia-
  ifr1-390/bionic-proposed libnvidia-fbc1-390/bionic-proposed

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