[Kernel-packages] [Bug 1625440] Re: i2c_designware 808622C1:06: punit semaphore timed out, resetting

2016-11-22 Thread Marc Neiger
Still there in Kernel 4.8.9

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

Title:
  i2c_designware 808622C1:06: punit semaphore timed out, resetting

Status in linux package in Ubuntu:
  Triaged

Bug description:
  kernel crash on boot rendering sdio wifi and bluetooth from operating
  on Nexbox T9 (Intel x5-z8300), works fine under Windows 10. It happens
  on both 16.04 and 16.10 with kernel 4.4.0 and on kernel 4.8.0-rc4 on
  Fedora 25 alpha. The acpi errors don't show up in the 4.8.0 kernel
  dmesg.

  Ubuntu 16.10 output.

  [   34.656025] i2c_designware 808622C1:06: I2C bus managed by PUNIT
  [   34.756942] i2c_designware 808622C1:06: punit semaphore timed out, 
resetting
  [   34.757068] i2c_designware 808622C1:06: PUNIT SEM: 2
  [   34.757134] [ cut here ]
  [   34.757148] WARNING: CPU: 1 PID: 1137 at 
/build/linux-rTsl6N/linux-4.4.0/drivers/i2c/busses/i2c-designware-baytrail.c:112
 baytrail_i2c_acquire+0x139/0x1e0 [i2c_designware_platform]()
  [   34.757152] Modules linked in: mei_txe(+) mei snd_rawmidi lpc_ich(+) 
processor_thermal_device(+) intel_soc_dts_iosf snd_seq hci_uart snd_seq_device 
8250_fintek snd_timer intel_hid btbcm btqca dw_dmac btintel sparse_keymap 
dw_dmac_core 
  bluetooth snd pwm_lpss_platform spi_pxa2xx_platform 
i2c_designware_platform(+) rfkill_gpio i2c_designware_core pwm_lpss soundcore 
int3403_thermal int340x_thermal_zone 8250_dw int3400_thermal soc_button_array 
acpi_thermal_rel mac_hid acpi_
  pad parport_pc ppdev lp parport ip_tables x_tables autofs4 overlay nls_utf8 
isofs nls_iso8859_1 dm_mirror dm_region_hash dm_log uas usb_storage 
hid_logitech_hidpp hid_logitech_dj usbhid mmc_block i915 i2c_algo_bit 
drm_kms_helper syscopyar
  ea sysfillrect sysimgblt fb_sys_fops drm video fjes i2c_hid hid sdhci_acpi 
sdhci pinctrl_cherryview

  [   34.757245] CPU: 1 PID: 1137 Comm: systemd-udevd Not tainted 
4.4.0-9136-generic #55-Ubuntu
  [   34.757248] Hardware name: N/A CherryTrail/Type2 - Board Product Name, 
BIOS YT11.6W4x64.D003 05/17/2016
  [   34.757254]  0286 be581321 8800b8803a00 
813f13e3
  [   34.757260]   c0325708 8800b8803a38 
810810f2
  [   34.757266]  8801384f9018 ff92 fffefce0 
88013b08c810
  [   34.757272] Call Trace:
  [   34.757285]  [] dump_stack+0x63/0x90
  [   34.757293]  [] warn_slowpath_common+0x82/0xc0
  [   34.757298]  [] warn_slowpath_null+0x1a/0x20
  [   34.757305]  [] baytrail_i2c_acquire+0x139/0x1e0 
[i2c_designware_platform]
  [   34.757313]  [] i2c_dw_init+0x27/0x350 
[i2c_designware_core]
  [   34.757319]  [] i2c_dw_probe+0x52/0x180 
[i2c_designware_core]
  [   34.757325]  [] dw_i2c_plat_probe+0x1d4/0x410 
[i2c_designware_platform]
  [   34.757334]  [] platform_drv_probe+0x3b/0xa0
  [   34.757339]  [] driver_probe_device+0x222/0x4a0
  [   34.757344]  [] __driver_attach+0x84/0x90
  [   34.757349]  [] ? driver_probe_device+0x4a0/0x4a0
  [   34.757354]  [] bus_for_each_dev+0x6c/0xc0
  [   34.757359]  [] driver_attach+0x1e/0x20
  [   34.757364]  [] bus_add_driver+0x1eb/0x280
  [   34.757368]  [] ? 0xc032e000
  [   34.757373]  [] driver_register+0x60/0xe0
  [   34.757378]  [] __platform_driver_register+0x36/0x40
  [   34.757384]  [] dw_i2c_init_driver+0x17/0x1000 
[i2c_designware_platform]
  [   34.757390]  [] do_one_initcall+0xb3/0x200
  [   34.757397]  [] ? kmem_cache_alloc_trace+0x183/0x1f0
  [   34.757404]  [] do_init_module+0x5f/0x1cf
  [   34.757412]  [] load_module+0x1667/0x1c00
  [   34.757417]  [] ? __symbol_put+0x60/0x60
  [   34.757424]  [] ? kernel_read+0x50/0x80
  [   34.757429]  [] SYSC_finit_module+0xb4/0xe0
  [   34.757435]  [] SyS_finit_module+0xe/0x10
  [   34.757441]  [] entry_SYSCALL_64_fastpath+0x16/0x71
  [   34.757446] ---[ end trace e446adf67caf8c0d ]---
  [   34.757451] i2c_designware 808622C1:06: couldn't acquire bus ownership
  [   34.757582] i2c_designware: probe of 808622C1:06 failed with error -110
  --- 
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperVersion: 1.378
  DistroRelease: Ubuntu 16.10
  IwConfig:
   lono wireless extensions.
   
   enxc44eac810358  no wireless extensions.
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160919)
  MachineType: N/A CherryTrail
  Package: linux (not installed)
  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=/casper/vmlinuz.efi 
file=/cdrom/preseed/hostname.seed boot=casper quiet splash ---
  ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running 

[Kernel-packages] [Bug 998310] Re: .Xmodmap file makes xorg temporarily reach high cpu usage (90%-100%) after resume or when coming back from tty to X session

2019-01-08 Thread Marc Neiger
still here on 
Mint 19.1 xfce 
kernel 4.18.0-13-generic

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

Title:
  .Xmodmap file makes xorg temporarily reach high cpu usage (90%-100%)
  after resume or when coming back from tty to X session

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Each time when I resume my laptop, my computer nearly freezes for
  about 5 minutes and Xorg is using 90-100% cpu. This issue disappears
  and then everything is back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Fri May 11 22:57:03 2012
  EcryptfsInUse: Yes
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
  ProcEnviron:
   LANGUAGE=ca_ES
   TERM=xterm
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to precise on 2012-03-25 (47 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/998310/+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 998310] Re: .Xmodmap file makes xorg temporarily reach high cpu usage (90%-100%) after resume or when coming back from tty to X session

2019-08-17 Thread Marc Neiger
Still here on 
Mint 19.2 xfce 
Kernel Linux resh-lakish 5.0.0-25-generic

However the attached script seems to be a crude workaround/

** Attachment added: "xfce-onunlock.sh"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/998310/+attachment/5283024/+files/xfce-onunlock.sh

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

Title:
  .Xmodmap file makes xorg temporarily reach high cpu usage (90%-100%)
  after resume or when coming back from tty to X session

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Each time when I resume my laptop, my computer nearly freezes for
  about 5 minutes and Xorg is using 90-100% cpu. This issue disappears
  and then everything is back to normal.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: xorg 1:7.6+12ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.38-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Fri May 11 22:57:03 2012
  EcryptfsInUse: Yes
  InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427)
  ProcEnviron:
   LANGUAGE=ca_ES
   TERM=xterm
   LANG=ca_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: Upgraded to precise on 2012-03-25 (47 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/998310/+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 1966066] Re: audio from external sound card is distorted

2022-03-28 Thread Marc Neiger
I the same problem with several machines using Jabra Speak 710.
5.13.0-35 works perfectly on all though, while 5.13.0-37 produces distorted 
sound.

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

Title:
  audio from external sound card is distorted

Status in linux-signed-hwe-5.13 package in Ubuntu:
  Confirmed

Bug description:
  The sound card is a Focusrite Scarlett 2i2.

  The sound is distorted everywhere.

  Sound via HDMI works.

  Seen others having the same problem:
  (Edit because of previously wrong link here) 
https://askubuntu.com/questions/1398614/upgrading-to-5-13-0-37-generic-breaks-audio-with-external-audio-card

  ubuntu release: Ubuntu 20.04.4 LTS
  package name involved in bug: linux-image-5.13.0-37-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-37-generic 5.13.0-37.42~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-35.40~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 23 12:56:02 2022
  InstallationDate: Installed on 2020-12-18 (459 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  SourcePackage: linux-signed-hwe-5.13
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe-5.13/+bug/1966066/+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 1995150] Re: kernel NULL pointer dereference after monitor wake

2023-11-17 Thread Marc Neiger
I've also been meeting this bug since kernel serie 6.2 (and 6.1 I think).
However I only have one monitor, but I use a HDMI switch. 
It happens on every boot and the monitor is already awaken when reaching linux 
boot. The crash happens a few seconds after the graphical target is reached 
(whether logged in or not) and everything on screen freezes. the rest (network) 
of the machine seems to be still working but is unusable.

Syslog is attached

GPU is identified as 
09:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] 
Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev cf) (prog-if 00 [VGA 
controller])
Subsystem: PC Partner Limited / Sapphire Technology Radeon RX 470/480
Flags: bus master, fast devsel, latency 0, IRQ 45
Memory at d000 (64-bit, prefetchable) [size=256M]
Memory at cfe0 (64-bit, prefetchable) [size=2M]
I/O ports at d000 [size=256]
Memory at fbd8 (32-bit, non-prefetchable) [size=256K]
Expansion ROM at 000c [disabled] [size=128K]
Capabilities: 
Kernel driver in use: amdgpu
Kernel modules: amdgpu


** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995150/+attachment/5720404/+files/crash

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

Title:
  kernel NULL pointer dereference after monitor wake

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I ran into a bug shortly after upgrading from 22.04 to 22.10. I have 2
  monitors connected to a Radeon R9 FURY / NANO Series via DP cables.
  When returning to the PC after a screen lock (when both monitors had
  entered a power saving mode), the second monitor did not wake up. I
  see the following warning and `kernel NULL pointer dereference` in the
  systemd journal:

  Oct 28 12:24:11 desktop kernel: [ cut here ]
  Oct 28 12:24:11 desktop kernel: WARNING: CPU: 12 PID: 91 at 
drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dce110/dce110_clk_mgr.c:140 
dce110_fill_display_configs+0x83/0x2e0 [amdgpu]
  Oct 28 12:24:11 desktop kernel: Modules linked in: xt_multiport tls 
nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter nvme_fabrics 
rfcomm snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack 
ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat n>
  Oct 28 12:24:11 desktop kernel:  gigabyte_wmi rapl drm_kms_helper fb_sys_fops 
snd_timer syscopyarea iwlwifi(O) ccp sysfillrect snd sysimgblt k10temp 
soundcore cfg80211(O) iwlwifi_compat(O) mac_hid msr parport_pc ppdev lp parport 
drm ramoops pstore_blk reed_solomon pstore_zone efi_>
  Oct 28 12:24:11 desktop kernel: CPU: 12 PID: 91 Comm: kworker/12:0H Tainted: 
G   O  5.19.0-23.24-justin-stock-generic #stock
  Oct 28 12:24:11 desktop kernel: Hardware name: Gigabyte Technology Co., Ltd. 
X570 AORUS PRO WIFI/X570 AORUS PRO WIFI, BIOS F21 07/31/2020
  Oct 28 12:24:11 desktop kernel: Workqueue: events_highpri dm_irq_work_func 
[amdgpu]
  Oct 28 12:24:11 desktop kernel: RIP: 
0010:dce110_fill_display_configs+0x83/0x2e0 [amdgpu]
  Oct 28 12:24:11 desktop kernel: Code: 89 dd 31 db 4c 63 f3 49 83 fe 05 0f 87 
80 01 00 00 4d 39 65 00 0f 84 29 01 00 00 83 c3 01 49 81 c5 10 08 00 00 83 fb 
06 75 da <0f> 0b 31 db 45 0f b6 ac 24 c8 03 00 00 41 80 fd 01 0f 87 fd 55 19
  Oct 28 12:24:11 desktop kernel: RSP: 0018:b291404dfa90 EFLAGS: 00010246
  Oct 28 12:24:11 desktop kernel: RAX: 0110 RBX: 0006 
RCX: 
  Oct 28 12:24:11 desktop kernel: RDX:  RSI: 908acdcd2980 
RDI: 908acdcc
  Oct 28 12:24:11 desktop kernel: RBP: b291404dfae0 R08: 908acdcc 
R09: 
  Oct 28 12:24:11 desktop kernel: R10: 908acdcd2980 R11: 908acdcc01f0 
R12: 908aa3478000
  Oct 28 12:24:11 desktop kernel: R13: 908acdcc3250 R14: 0005 
R15: 
  Oct 28 12:24:11 desktop kernel: FS:  () 
GS:90911ed0() knlGS:
  Oct 28 12:24:11 desktop kernel: CS:  0010 DS:  ES:  CR0: 
80050033
  Oct 28 12:24:11 desktop kernel: CR2: 7f36aced3098 CR3: 0001a3e6c000 
CR4: 00350ee0
  Oct 28 12:24:11 desktop kernel: Call Trace:
  Oct 28 12:24:11 desktop kernel:  
  Oct 28 12:24:11 desktop kernel:  ? dce_get_required_clocks_state+0x25/0x140 
[amdgpu]
  Oct 28 12:24:11 desktop kernel:  dce_update_clocks+0xdb/0x170 [amdgpu]
  Oct 28 12:24:11 desktop kernel:  dce100_prepare_bandwidth+0x3e/0x50 [amdgpu]
  Oct 28 12:24:11 desktop kernel:  commit_planes_for_stream+0xd54/0x1060 
[amdgpu]
  Oct 28 12:24:11 desktop kernel:  ? 
dc_resource_state_copy_construct+0x167/0x2b0 [amdgpu]
  Oct 28 12:24:11 desktop kernel:  dc_commit_updates_for_stream+0x1e8/0x5b0 
[amdgpu]
  Oct 28 12:24:11 desktop kernel: