Re: [Bug 1896482] Re: acpi event detection crashes (fwd)
Hi Alex, just to make sure that I reinstalled one of the kernels that was supposed to be good (perhaps by accident I reinstalled a bad one), could you direct me to a good kernel on your ftp site? best, Jim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896482 Title: acpi event detection crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1896482] Re: acpi event detection crashes (fwd)
Hi Alex, unfortunately that bug has come back. It just took longer to manifest itself after booting. It also affects recognition of the power state and the brightness buttons, which I hadn't noticed before. --Jim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896482 Title: acpi event detection crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1898389] Re: browser frequently crashing with trap int3
My workaround is to close chromium frequently (closing its x-window rather than normal exit from the browser) and restart it, in order to save all my open tabs. This seems to release the excess memory and CPU that is being hogged by this atrocious piece of software. On Tue, 26 Jan 2021, Fevrin wrote: > Just to note, the kernel trap int3 issue persists for me, even in the > latest Chromium release for Ubuntu 20.04.1, Version 88.0.4324.96 > (Official Build) snap (64-bit). > > Here's my kernel info: > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Linux cweeks-XPS-13-9380 5.4.0-59-generic #65-Ubuntu SMP Thu Dec 10 12:01:51 > UTC 2020 x86_64 x86_64 x86_64 GNU/Linux > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > I'm seeing errors like the following: > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > Jan 26 13:25:14 XPS-13-9380 kernel: traps: chrome[2013993] trap int3 > ip:562b6998b3de sp:7ffe6c8b6a30 error:0 in chrome[562b64e8d000+7548000] > Jan 26 13:13:26 XPS-13-9380 chromium_chromium.desktop[1642720]: > [1642720:1642720:0126/131326.176240:ERROR:fallback_task_provider.cc(118)] > Every renderer should have at least one task provided by a primary task > provider. If a fallback task is shown, it is a bug. Please file a new bug and > tag it as a dependency of crbug.com/739782. > Jan 26 13:13:26 XPS-13-9380 chromium_chromium.desktop[1642720]: > [1642720:1642720:0126/131326.178190:ERROR:fallback_task_provider.cc(118)] > Every renderer should have at least one task provided by a primary task > provider. If a fallback task is shown, it is a bug. Please file a new bug and > tag it as a dependency of crbug.com/739782. > Jan 26 13:13:26 XPS-13-9380 chromium_chromium.desktop[1642720]: > [1642720:1642720:0126/131326.179527:ERROR:fallback_task_provider.cc(118)] > Every renderer should have at least one task provided by a primary task > provider. If a fallback task is shown, it is a bug. Please file a new bug and > tag it as a dependency of crbug.com/739782. > Jan 26 13:13:26 XPS-13-9380 chromium_chromium.desktop[1642720]: > [1642720:1642720:0126/131326.180881:ERROR:fallback_task_provider.cc(118)] > Every renderer should have at least one task provided by a primary task > provider. If a fallback task is shown, it is a bug. Please file a new bug and > tag it as a dependency of crbug.com/739782. > =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1898389 > > Title: > browser frequently crashing with trap int3 > > Status in chromium-browser package in Ubuntu: > Expired > > Bug description: > I used to be able to have many tabs open with Chromium without > problems. Lately it crashes or gives "aw snap" errors (see kernel > messages below) if I start to keep more than 25 or so open. > > Description:Ubuntu 16.04.7 LTS > Release:16.04 > > chromium-browser: >Installed: 85.0.4183.83-0ubuntu0.16.04.2 >Candidate: 85.0.4183.121-0ubuntu0.16.04.1 >Version table: > 85.0.4183.121-0ubuntu0.16.04.1 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe > amd64 Packages > 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 > Packages > *** 85.0.4183.83-0ubuntu0.16.04.2 100 > 100 /var/lib/dpkg/status > 49.0.2623.108-0ubuntu1.1233 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 > Packages > 18.0.1025.151~r130497-0ubuntu1 500 > 500 http://mirrors.kernel.org/ubuntu precise/universe amd64 Packages > > > dmesg: > > [510927.956240] traps: chromium-browse[20348] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [510927.961473] traps: chromium-browse[20984] trap int3 ip:5584761d6817 > sp:7ffdfc31ca70 error:0 > [510927.963650] traps: chromium-browse[20981] trap int3 ip:562e91183f52 > sp:7ffd8fc04770 error:0 > [510927.964791] traps: chromium-browse[20076] trap int3 ip:5584761d6817 > sp:7ffdfc31b2c0 error:0 > [510990.558454] traps: chromium-browse[21122] trap int3 ip:5584758743be > sp:7ffdfc31bd40 error:0 > [510995.156958] traps: chromium-browse[21137] trap int3 ip:558476229df7 > sp:7ffdfc31cab0 error:0 > [510995.183512] traps: chromium-browse[16340] trap int3 ip:5584761d6817 > sp:7ffdfc31b300 error:0 > [515143.367254] traps: chromium-browse[22618] trap int3 ip:5584761d6817 > sp:7ffdfc31c640 error:0 > [515148.805562] traps: chromium-browse[23018] trap int3 ip:5584758743be > sp:7ffdfc31a6a0 error:0 > [519367.266074] traps: chromium-browse[24576] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [519367.269766] traps: Compositor[24496] trap int3 ip:558473072b38 > sp:7fe1dcaf95e0 error:0 > [519367.329864] traps: chromium-browse[24588] trap invalid opcode > ip:558478cb1962
Re: [Bug 1896482] Re: acpi event detection crashes (fwd)
Hi Alex, I see that I am currently running 5.4.0-48-generic, which I think is the same version that you originally sent me. But livepatch alters the running kernel without changing its version number, doesn't it? That's what makes me still wonder if it is the culprit. thanks--Jim On Tue, 3 Nov 2020, Jim Cline wrote: > > > > -- Forwarded message -- > Date: Mon, 02 Nov 2020 23:24:48 - > From: Alex Hung <1896...@bugs.launchpad.net> > To: gxgilt...@gmail.com > Subject: [Bug 1896482] Re: acpi event detection crashes > > @jim, > > You can check your kernel version by "uname -r". > > I also built a rebased one: > https://people.canonical.com/~alexhung/LP1896482/Ubuntu-5.4.0-52.57/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1896482 Title: acpi event detection crashes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896482/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1898389] Re: browser frequently crashing with trap int3
the new version of Chromium seems to be a disaster when I try to go to full screen in YouTube. It scatters parts of the screen amongst my various virtual desktops and creates a huge mess, forcing me to kill chromium from the command line. On Fri, 30 Oct 2020, Olivier Tilloy wrote: > Thanks for the report Gerald, and sorry for the lack of a timely response. > Is this still happening with the latest update available for Ubuntu 16.04 > (version 86.0.4240.75-0ubuntu0.16.04.1)? > > ** Changed in: chromium-browser (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1898389 > > Title: > browser frequently crashing with trap int3 > > Status in chromium-browser package in Ubuntu: > Incomplete > > Bug description: > I used to be able to have many tabs open with Chromium without > problems. Lately it crashes or gives "aw snap" errors (see kernel > messages below) if I start to keep more than 25 or so open. > > Description:Ubuntu 16.04.7 LTS > Release:16.04 > > chromium-browser: >Installed: 85.0.4183.83-0ubuntu0.16.04.2 >Candidate: 85.0.4183.121-0ubuntu0.16.04.1 >Version table: > 85.0.4183.121-0ubuntu0.16.04.1 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe > amd64 Packages > 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 > Packages > *** 85.0.4183.83-0ubuntu0.16.04.2 100 > 100 /var/lib/dpkg/status > 49.0.2623.108-0ubuntu1.1233 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 > Packages > 18.0.1025.151~r130497-0ubuntu1 500 > 500 http://mirrors.kernel.org/ubuntu precise/universe amd64 Packages > > > dmesg: > > [510927.956240] traps: chromium-browse[20348] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [510927.961473] traps: chromium-browse[20984] trap int3 ip:5584761d6817 > sp:7ffdfc31ca70 error:0 > [510927.963650] traps: chromium-browse[20981] trap int3 ip:562e91183f52 > sp:7ffd8fc04770 error:0 > [510927.964791] traps: chromium-browse[20076] trap int3 ip:5584761d6817 > sp:7ffdfc31b2c0 error:0 > [510990.558454] traps: chromium-browse[21122] trap int3 ip:5584758743be > sp:7ffdfc31bd40 error:0 > [510995.156958] traps: chromium-browse[21137] trap int3 ip:558476229df7 > sp:7ffdfc31cab0 error:0 > [510995.183512] traps: chromium-browse[16340] trap int3 ip:5584761d6817 > sp:7ffdfc31b300 error:0 > [515143.367254] traps: chromium-browse[22618] trap int3 ip:5584761d6817 > sp:7ffdfc31c640 error:0 > [515148.805562] traps: chromium-browse[23018] trap int3 ip:5584758743be > sp:7ffdfc31a6a0 error:0 > [519367.266074] traps: chromium-browse[24576] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [519367.269766] traps: Compositor[24496] trap int3 ip:558473072b38 > sp:7fe1dcaf95e0 error:0 > [519367.329864] traps: chromium-browse[24588] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31cb68 error:0 in > chromium-browser[558471f1c000+a1c4000] > [519367.357674] traps: chromium-browse[24558] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31b6a8 error:0 in > chromium-browser[558471f1c000+a1c4000] > [519367.454722] traps: chromium-browse[24483] trap int3 ip:5584761d6817 > sp:7ffdfc316260 error:0 > [519372.392415] traps: chromium-browse[24372] trap int3 ip:558475879bc2 > sp:7ffdfc31abd0 error:0 > [519372.493260] traps: chromium-browse[24606] trap int3 ip:5584758743be > sp:7ffdfc31bbb0 error:0 > [519429.551779] traps: chromium-browse[24895] trap int3 ip:558476229df7 > sp:7ffdfc31d020 error:0 > [519429.585427] traps: chromium-browse[24884] trap int3 ip:5584761d6817 > sp:7ffdfc3165c0 error:0 > [519429.588811] traps: chromium-browse[24697] trap int3 ip:5584761d6817 > sp:7ffdfc3164c0 error:0 > [519429.646931] traps: chromium-browse[24742] trap int3 ip:5584761d6817 > sp:7ffdfc31c5b0 error:0 > [519429.841404] traps: chromium-browse[24906] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31cb68 error:0 in > chromium-browser[558471f1c000+a1c4000 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898389/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898389 Title: browser frequently crashing with trap int3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1898389] Re: browser frequently crashing with trap int3
thanks, I will try with the updated version and keep you posted On Fri, 30 Oct 2020, Olivier Tilloy wrote: > Thanks for the report Gerald, and sorry for the lack of a timely response. > Is this still happening with the latest update available for Ubuntu 16.04 > (version 86.0.4240.75-0ubuntu0.16.04.1)? > > ** Changed in: chromium-browser (Ubuntu) > Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1898389 > > Title: > browser frequently crashing with trap int3 > > Status in chromium-browser package in Ubuntu: > Incomplete > > Bug description: > I used to be able to have many tabs open with Chromium without > problems. Lately it crashes or gives "aw snap" errors (see kernel > messages below) if I start to keep more than 25 or so open. > > Description:Ubuntu 16.04.7 LTS > Release:16.04 > > chromium-browser: >Installed: 85.0.4183.83-0ubuntu0.16.04.2 >Candidate: 85.0.4183.121-0ubuntu0.16.04.1 >Version table: > 85.0.4183.121-0ubuntu0.16.04.1 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe > amd64 Packages > 500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 > Packages > *** 85.0.4183.83-0ubuntu0.16.04.2 100 > 100 /var/lib/dpkg/status > 49.0.2623.108-0ubuntu1.1233 500 > 500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 > Packages > 18.0.1025.151~r130497-0ubuntu1 500 > 500 http://mirrors.kernel.org/ubuntu precise/universe amd64 Packages > > > dmesg: > > [510927.956240] traps: chromium-browse[20348] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [510927.961473] traps: chromium-browse[20984] trap int3 ip:5584761d6817 > sp:7ffdfc31ca70 error:0 > [510927.963650] traps: chromium-browse[20981] trap int3 ip:562e91183f52 > sp:7ffd8fc04770 error:0 > [510927.964791] traps: chromium-browse[20076] trap int3 ip:5584761d6817 > sp:7ffdfc31b2c0 error:0 > [510990.558454] traps: chromium-browse[21122] trap int3 ip:5584758743be > sp:7ffdfc31bd40 error:0 > [510995.156958] traps: chromium-browse[21137] trap int3 ip:558476229df7 > sp:7ffdfc31cab0 error:0 > [510995.183512] traps: chromium-browse[16340] trap int3 ip:5584761d6817 > sp:7ffdfc31b300 error:0 > [515143.367254] traps: chromium-browse[22618] trap int3 ip:5584761d6817 > sp:7ffdfc31c640 error:0 > [515148.805562] traps: chromium-browse[23018] trap int3 ip:5584758743be > sp:7ffdfc31a6a0 error:0 > [519367.266074] traps: chromium-browse[24576] trap int3 ip:5584758743be > sp:7ffdfc31ca40 error:0 > [519367.269766] traps: Compositor[24496] trap int3 ip:558473072b38 > sp:7fe1dcaf95e0 error:0 > [519367.329864] traps: chromium-browse[24588] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31cb68 error:0 in > chromium-browser[558471f1c000+a1c4000] > [519367.357674] traps: chromium-browse[24558] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31b6a8 error:0 in > chromium-browser[558471f1c000+a1c4000] > [519367.454722] traps: chromium-browse[24483] trap int3 ip:5584761d6817 > sp:7ffdfc316260 error:0 > [519372.392415] traps: chromium-browse[24372] trap int3 ip:558475879bc2 > sp:7ffdfc31abd0 error:0 > [519372.493260] traps: chromium-browse[24606] trap int3 ip:5584758743be > sp:7ffdfc31bbb0 error:0 > [519429.551779] traps: chromium-browse[24895] trap int3 ip:558476229df7 > sp:7ffdfc31d020 error:0 > [519429.585427] traps: chromium-browse[24884] trap int3 ip:5584761d6817 > sp:7ffdfc3165c0 error:0 > [519429.588811] traps: chromium-browse[24697] trap int3 ip:5584761d6817 > sp:7ffdfc3164c0 error:0 > [519429.646931] traps: chromium-browse[24742] trap int3 ip:5584761d6817 > sp:7ffdfc31c5b0 error:0 > [519429.841404] traps: chromium-browse[24906] trap invalid opcode > ip:558478cb1962 sp:7ffdfc31cb68 error:0 in > chromium-browser[558471f1c000+a1c4000 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898389/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1898389 Title: browser frequently crashing with trap int3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1898389/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1896482] Re: acpi event detection crashes
Hi Alex, my problem came back. Is it possible that livepatch has replaced my working kernel with the broken one again? --Jim On Thu, 24 Sep 2020, Alex Hung wrote: > A test kernel with target patches ready for SRU is available @ > https://people.canonical.com/~alexhung/LP1896482/fixes/ > > The patch in #23 requires three precedent patches. See SRU.log file for > more details. > > Note it is rebased Ubuntu-5.4.0-48.52 now. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > In Progress > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661] >
Re: [Bug 1896482] Re: acpi event detection crashes
last one you sent with the commit? It is working. On Fri, 25 Sep 2020, Alex Hung wrote: > @jcline-physics, > > can you give kernel in #24 a try? > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > In Progress > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661] > acpi_ec_transaction+0x16c/0x3c0 > Sep 20 11:35:33 laxmi kernel: [232492.303663] > acpi_ec_space_handler+0xd4/0x280 > Sep 20 11:35:33 laxmi kernel: [232492.303666] > acpi_ev_address_space_dispatch+0x2f7/0x39f > Sep 20 11:35:33 laxmi kernel: [232492.303668] ? ec_transaction+0x70/0x70 > Sep 20
Re: [Bug 1896482] Re: acpi event detection crashes
thanks a lot Alex On Thu, 24 Sep 2020, Alex Hung wrote: > A test kernel with target patches ready for SRU is available @ > https://people.canonical.com/~alexhung/LP1896482/fixes/ > > The patch in #23 requires three precedent patches. See SRU.log file for > more details. > > Note it is rebased Ubuntu-5.4.0-48.52 now. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > In Progress > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661] > acpi_ec_transaction+0x16c/0x3c0 > Sep 20 11:35:33 laxmi kernel: [232492.303663] > acpi_ec_space_handler+0xd4/0x280 > Sep 20
Re: [Bug 1896482] Re: acpi event detection crashes
that one seems to be fine. On Thu, 24 Sep 2020, Alex Hung wrote: > Next one: > https://people.canonical.com/~alexhung/LP1896482/937d1d5d752513b8/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > In Progress > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661] > acpi_ec_transaction+0x16c/0x3c0 > Sep 20 11:35:33 laxmi kernel: [232492.303663] > acpi_ec_space_handler+0xd4/0x280 > Sep 20 11:35:33 laxmi kernel: [232492.303666] > acpi_ev_address_space_dispatch+0x2f7/0x39f > Sep 20 11:35:33 laxmi kernel: [232492.303668] ? ec_transaction+0x70/0x70 > Sep 20
Re: [Bug 1896482] Re: acpi event detection crashes
that one also seems to be good. On Wed, 23 Sep 2020, Alex Hung wrote: > Next one is @ > https://people.canonical.com/~alexhung/LP1896482/c271d18b523bb58e/ > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > In Progress > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661] > acpi_ec_transaction+0x16c/0x3c0 > Sep 20 11:35:33 laxmi kernel: [232492.303663] > acpi_ec_space_handler+0xd4/0x280 > Sep 20 11:35:33 laxmi kernel: [232492.303666] > acpi_ev_address_space_dispatch+0x2f7/0x39f > Sep 20 11:35:33 laxmi kernel: [232492.303668] ? ec_transaction+0x70/0x70 >
Re: [Bug 1896482] Re: acpi event detection crashes
this one seems to be good On Wed, 23 Sep 2020, Alex Hung wrote: > @jcline-physics, > > Thanks for testing. The next is available @ > https://people.canonical.com/~alexhung/LP1896482/31be3e3551d09f20/ > > ** Changed in: linux (Ubuntu) > Status: Confirmed => In Progress > > ** Changed in: linux (Ubuntu) > Assignee: (unassigned) => Alex Hung (alexhung) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > In Progress > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661] > acpi_ec_transaction+0x16c/0x3c0 > Sep 20 11:35:33 laxmi kernel: [232492.303663] >
Re: [Bug 1896482] Re: acpi event detection crashes
okay, so that kernel has the problem again. On Wed, 23 Sep 2020, Alex Hung wrote: > Thanks mfo for helping out how to disable secure boot and install kernel > > I uploaded a test kernel @ > https://people.canonical.com/~alexhung/LP1896482/0a8c35897f60b202/ > > There are 17 patches so it requires 4 times to identify the fixing > kernel patch. The included patches are listed in ec_bisect1.log in the > above link. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661] > acpi_ec_transaction+0x16c/0x3c0 > Sep
Re: [Bug 1896482] Re: acpi event detection crashes
ok, that's not such a big problem. I'll keep all the versions' deb packages in separate directories so I can easily switch back to one of them if needed. On Wed, 23 Sep 2020, Mauricio Faria de Oliveira wrote: > Hi Jim, > > You can install on top of the previous ones without removing them first. > > The versioning of the test packages used the same 5.4.0-47 number, > so unfortunately they will keep overwriting themselves (including > the original/non-test 5.4.0-47 kernel.) > > I'd think this is why you only see two entries in grub boot list > (e.g., since your installation is recent there may be one other > kernel installed, and 5.4.0-47 which is being overwritten.) > > Maybe Alex can change that to a fake non-published version number > in the next steps, so that all test versions are kept installed/ > listed in grub config. > > cheers, > Mauricio > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2:
Re: [Bug 1896482] Re: acpi event detection crashes
Hi, if I install this on top of the previous one using dpkg -i * will that be sufficient? Or do I have to remove the previous packages first? It seems like my grub configuration is somehow set to keeping only two kernels in the boot list. It would be nice if it would keep them all so I don't have to keep reinstalling kernels to retest them. On Wed, 23 Sep 2020, Alex Hung wrote: > Thanks mfo for helping out how to disable secure boot and install kernel > > I uploaded a test kernel @ > https://people.canonical.com/~alexhung/LP1896482/0a8c35897f60b202/ > > There are 17 patches so it requires 4 times to identify the fixing > kernel patch. The included patches are listed in ec_bisect1.log in the > above link. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi
Re: [Bug 1896482] Re: acpi event detection crashes
ok, I can do that On Tue, 22 Sep 2020, Mauricio Faria de Oliveira wrote: > Hey Jim, > > That's very good news! > > I believe Alex should send you more test kernels, > with different sets of patches included/removed, > so to bisect/identify which specific patch(es) > resolve the problem. > > If you could help with testing that as well, > that would be great, so a smaller patch(set) > can be put into the Ubuntu stable release(s). > > cheers, > Mauricio > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661]
Re: [Bug 1896482] Re: acpi event detection crashes
Looks like it is working! At any rate the old kernel started having the problem much sooner while this one is still fine. Thanks very much for your help with this! > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661] > acpi_ec_transaction+0x16c/0x3c0 > Sep 20 11:35:33 laxmi kernel: [232492.303663] > acpi_ec_space_handler+0xd4/0x280 > Sep 20 11:35:33 laxmi kernel: [232492.303666] > acpi_ev_address_space_dispatch+0x2f7/0x39f > Sep 20 11:35:33 laxmi kernel: [232492.303668] ?
Re: [Bug 1896482] Re: acpi event detection crashes
thanks, I fixed that and will start testing On Tue, 22 Sep 2020, Mauricio Faria de Oliveira wrote: > It looks like you have secure boot enabled. > Unfortunately test kernels are unsigned and thus require it to be disabled in > your BIOS/EFI menu. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657] queue_work_on+0x3b/0x50 > Sep 20 11:35:33 laxmi kernel: [232492.303659] > advance_transaction+0x2b9/0x620 > Sep 20 11:35:33 laxmi kernel: [232492.303661] > acpi_ec_transaction+0x16c/0x3c0 > Sep 20 11:35:33 laxmi kernel: [232492.303663] > acpi_ec_space_handler+0xd4/0x280 > Sep 20 11:35:33 laxmi kernel: [232492.303666] >
Re: [Bug 1896482] Re: acpi event detection crashes
Hi Maricio, I did as you suggested, but cannot boot, error:/boot/vmlinuz-5.4.0-47-generic has invalid signature loading initial ramdisk error: you need to load the kernel first --Jim On Tue, 22 Sep 2020, Mauricio Faria de Oliveira wrote: > Hi Jim, > > This is a conflict between the (un)signed kernel packages; but it's easy > to solve: > > Please remove the linux-image-5.4.0-47-generic package and try > installing again; e.g., > > $ sudo apt purge linux-image-5.4.0-47-generic # confirm to remove the running > kernel if asked. > $ sudo dpkg -i *.deb # from alex hung > > cheers, > Mauricio > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd > Sep 20 11:35:33 laxmi kernel: [232492.303638] RSP: 0018:b16bc0ebb8f8 > EFLAGS: 00010087 > Sep 20 11:35:33 laxmi kernel: [232492.303640] RAX: 9a2477432600 RBX: > 0002 RCX: 0004 > Sep 20 11:35:33 laxmi kernel: [232492.303641] RDX: 9a2475af4a90 RSI: > 9a2475b03200 RDI: 9a2430215f00 > Sep 20 11:35:33 laxmi kernel: [232492.303642] RBP: b16bc0ebb938 R08: > R09: 0007 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R10: 9a24755ad678 R11: > R12: 9a2475af4a00 > Sep 20 11:35:33 laxmi kernel: [232492.303643] R13: 9a2475b03200 R14: > 2000 R15: 9a2475af4a90 > Sep 20 11:35:33 laxmi kernel: [232492.303645] FS: () > GS:9a247740() knlGS: > Sep 20 11:35:33 laxmi kernel: [232492.303646] CS: 0010 DS: ES: > CR0: 80050033 > Sep 20 11:35:33 laxmi kernel: [232492.303647] CR2: 00c42098b000 CR3: > 00018520a003 CR4: 003606f0 > Sep 20 11:35:33 laxmi kernel: [232492.303648] Call Trace: > Sep 20 11:35:33 laxmi kernel: [232492.303654] ? > acpi_os_release_lock+0xe/0x10 > Sep 20 11:35:33 laxmi kernel: [232492.303657]
Re: [Bug 1896482] Re: acpi event detection crashes (fwd)
Hi Alex, thanks for that. I got this error message while installing, dpkg: regarding linux-image-unsigned-5.4.0-47-generic_5.4.0-47.51_amd64.deb contntaining linux-image-unsigned-5.4.0-47-generic: linux-image-unsigned-5.4.0-47-generic conflicts with linux-image-5.4.0-47-genereric linux-image-5.4.0-47-generic (version 5.4.0-47.51) is present and installed. dpkg: error processing archive linux-image-unsigned-5.4.0-47-generic_5.4.0-47.5151_amd64.deb (--install): conflicting packages - not installing linux-image-unsigned-5.4.0-47-generic The others, linux-headers-5.4.0-47_5.4.0-47.51_all.deb linux-headers-5.4.0-47-generic_5.4.0-47.51_amd64.deb linux-modules-5.4.0-47-generic_5.4.0-47.51_amd64.deb linux-modules-extra-5.4.0-47-generic_5.4.0-47.51_amd64.deb seem to have installed properly. Should I go ahead and reboot? regards, Jim On Tue, 22 Sep 2020, Jim Cline wrote: > > > > -- Forwarded message -- > Date: Mon, 21 Sep 2020 21:19:04 - > From: Alex Hung <1896...@bugs.launchpad.net> > To: gxgilt...@gmail.com > Subject: [Bug 1896482] Re: acpi event detection crashes > > The warning messages occurred between "ACPI: EC: interrupt blocked" and > "ACPI: EC: interrupt unblocked". Let's try to apply all (17) mainline > patches to ACPI EC to Ubuntu-5.4.0-47.51. > > If this solves the problems we can then bi-select to identify which > patches are the solution and then backport to 5.4 kernel. > > The test kernel is available @ > https://people.canonical.com/~alexhung/LP1896482/ and the applied > patches are listed in ec_patches.log > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1896482 > > Title: > acpi event detection crashes > > Status in linux package in Ubuntu: > Confirmed > > Bug description: > Right after booting, acpi lid open/close is detected as it should be > by the kernel, but some time later it crashes, so I have to manually > suspend the system. The traceback is here: > > Sep 20 11:35:33 laxmi kernel: [232492.303557] [ cut here > ] > Sep 20 11:35:33 laxmi kernel: [232492.303564] WARNING: CPU: 0 PID: 8302 at > kernel/workqueue.c:1416 __queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303565] Modules linked in: ccm rfcomm > cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_soc_skl_hda_dsp > snd_hda_codec_hdmi snd_soc_hdac_hdmi snd_hda_codec_realtek snd_soc_dmic > snd_hda_codec_generic snd_sof_pci mei_hdcp x86_pkg_temp_thermal > intel_powerclamp intel_rapl_msr coretemp snd_sof_intel_hda_common > snd_soc_hdac_hda snd_sof_intel_hda kvm_intel snd_sof_intel_byt > snd_sof_intel_ipc kvm snd_sof snd_sof_xtensa_dsp snd_hda_ext_core > snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress ac97_bus > snd_pcm_dmaengine joydev crct10dif_pclmul ghash_clmulni_intel snd_hda_intel > aesni_intel snd_intel_dspcfg crypto_simd iwlmvm cryptd snd_hda_codec > glue_helper rapl mac80211 snd_hda_core snd_seq_midi snd_hwdep > snd_seq_midi_event libarc4 intel_cstate uvcvideo snd_rawmidi i915 snd_pcm > videobuf2_vmalloc input_leds thinkpad_acpi btusb videobuf2_memops serio_raw > btrtl videobuf2_v4l2 snd_seq btbcm btintel nvram videobuf2_common iwlwif! > i processor_thermal_device bluetooth videodev > Sep 20 11:35:33 laxmi kernel: [232492.303600] drm_kms_helper mc wmi_bmof > i2c_algo_bit intel_rapl_common fb_sys_fops ucsi_acpi intel_wmi_thunderbolt > ecdh_generic ledtrig_audio typec_ucsi mei_me syscopyarea hid_multitouch > snd_seq_device sysfillrect cfg80211 ecc sysimgblt mei intel_soc_dts_iosf > typec snd_timer snd soundcore int3403_thermal int340x_thermal_zone acpi_pad > intel_hid int3400_thermal acpi_thermal_rel sparse_keymap mac_hid sch_fq_codel > parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic > crc32_pclmul nvme psmouse e1000e i2c_i801 thunderbolt intel_lpss_pci > intel_lpss nvme_core idma64 virt_dma i2c_hid hid wmi video pinctrl_cannonlake > pinctrl_intel > Sep 20 11:35:33 laxmi kernel: [232492.303628] CPU: 0 PID: 8302 Comm: > kworker/0:0 Not tainted 5.4.0-47-generic #51-Ubuntu > Sep 20 11:35:33 laxmi kernel: [232492.303629] Hardware name: LENOVO > 20U9001NUS/20U9001NUS, BIOS N2WET19W (1.09 ) 07/01/2020 > Sep 20 11:35:33 laxmi kernel: [232492.303632] Workqueue: kec_query > acpi_ec_event_processor > Sep 20 11:35:33 laxmi kernel: [232492.303635] RIP: > 0010:__queue_work+0x337/0x3f0 > Sep 20 11:35:33 laxmi kernel: [232492.303637] Code: ff 49 8b 9d a0 00 00 00 > e9 aa fd ff ff 65 8b 05 e7 59 15 6d a9 00 01 1f 00 75 0f 65 48 8b 3c 25 c0 6b > 01 00 f6 47 24 20 75 25 <0f> 0b 48 83 c4 18 5b 41 5c 41 5d 41 5e 41 5f 5d c3 > 0f 0b e9 fd fd >
Re: [Bug 1895217] Re: gnome control center mouse settings don't work in other window manager
yes I know that. I'm talking about gnome-control-center not saving the settings. On Fri, 11 Sep 2020, Daniel van Vugt wrote: > Anything you want run automatically on login, try putting it in a script > called: > > ~/.xsession > > or > > ~/.xinitrc > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1895217 > > Title: > gnome control center mouse settings don't work in other window manager > > Status in gnome-control-center package in Ubuntu: > Invalid > > Bug description: > I would like to use gnome control center from Fvwm window manager. > But the mouse speed does not respond at all to what I set unless I am > running it from the default ubuntu window manager. I tried running > gnome control center using different XDG environment variables as > suggested by some posts, but this had no effect. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1895217/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895217 Title: gnome control center mouse settings don't work in other window manager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1895217/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1540084] Re: xfig crashes when moving a point of an arc
This bug probably affects zillions of people, now 7 have reported it. The fix exists, can someone please apply it? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1540084 Title: xfig crashes when moving a point of an arc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xfig/+bug/1540084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598993] Re: xrandr scaling corrupts external monitor output
I recently reproduced the same problem without using scaling, by connecting to a different external monitor. Now the problem exists in every video mode. Perhaps a problem of compatibility with Sky Lake integrated graphics in Thinkpad X260 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598993 Title: xrandr scaling corrupts external monitor output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1598993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1034928] Re: Fontconfig warning: Having multiple values in isn't supported and may not works as expected
This bug is easy to fix. For example, it will be caused by a section like this: zh-cn zh-sg The correct syntax would be zh-cn zh-sg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1034928 Title: Fontconfig warning: Having multiple values in isn't supported and may not works as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/culmus/+bug/1034928/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1065606] Re: Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 96: Having multiple values in isn't supported and may not works as expected
Here is the corrected version of 65-droid-sans-fonts.conf. At least I think it's correct, it gets rid of the error messages. Can some developer please correct it in the distribution? ** Attachment added: "65-droid-sans-fonts.conf" https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1065606/+attachment/4762999/+files/65-droid-sans-fonts.conf -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1065606 Title: Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 96: Having multiple values in isn't supported and may not works as expected To manage notifications about this bug go to: https://bugs.launchpad.net/update-manager/+bug/1065606/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598993] Re: xrandr scaling corrupts external monitor output
For any who are affected by this, here is a work-around. I was able to add a screen resolution that was detected for my internal monitor, but not for the external one, using xrandr --addmode. It gets the width of the screen right, but truncates the bottom. However panning makes the bottom accessible, so this is not a serious limitation. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598993 Title: xrandr scaling corrupts external monitor output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1598993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1598993] [NEW] xrandr scaling corrupts external monitor output
Public bug reported: after doing xrandr --output HDMI2 --scale wxh, using any values except 1x1, the screen becomes increasingly distorted when typing in an editor window. The problem first appears as images of the previous cursor position being left behind, but as typing continues, lines below that being edited become increasingly garbled. The distortion can be removed temporarily by dragging the window to a different position. But of course it comes back as soon as editing resumes. The problem appears also in typing in an xterm window, as the image of the cursor gets left behind while typing the space bar. This makes the scale option completely useless for my usual purposes, and forces me to live with a screen resolution that doesn't properly fill the external monitor. The problem did not exist in xrandr 1.3.3 on my old system. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1598993 Title: xrandr scaling corrupts external monitor output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1598993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319] Re: xrandr --scale restricts area in which mouse moves
I have the same bug in a recent build from xenial. I tried downgrading xorg to precise, no difference, mouse still hits the wall when output to internal monitor is turned off. If both monitors are turned on, the problem does not occur. But I like to conserve my laptop screen when I am connected to an external monitor. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1597984] Re: horizontal scrolling with middle trackpoint button broken
Sorry, I withdraw this bug. The solution is to turn off Evdev Wheel Emulation. But maybe some other confused person can benefit from this. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597984 Title: horizontal scrolling with middle trackpoint button broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1597984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1597984] [NEW] horizontal scrolling with middle trackpoint button broken
Public bug reported: Horizontal scrolling with the middle trackpoint button on Thinkpad X260 does not work as expected. I noticed the problem in nedit, where holding the middle button while dragging the cursor over the text to be copied is a fast way of copying text. But the cursor does not move, so this feature does not work. In chromium, scrolling works with the cursor in place, but this is not the same functionality as with a real mouse, which is what is supposed to be emulated. This all worked perfectly in Ubuntu 10.10 (what I have been using until now). The difference between scrolling with the middle button of a real mouse and the broken emulation is that with a real mouse, xev sees a ButtonPress event (button 2) followed by MotionNotify events, followed by a ButtonRelease event, whereas with the trackpoint it sees a series of ButtonPress and ButtonRelease events (buttons 4,5,6,7) with no MotionNotify events. Completely different behavior from what an application is expecting. Since this worked in a previous release, is there some work-around? ** Affects: xserver-xorg-input-evdev (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1597984 Title: horizontal scrolling with middle trackpoint button broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/1597984/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 881046]
I have this bug when I use xrandr to resize the output to the VGA monitor, and then turn off the LVD using xrandr --output LVDS1 --off. The mouse becomes confined to the left side of the monitor as soon I turn off the LVD. I have version 2:1.11.4-0ubuntu10.13 of xorg-server, where this problem is supposed to be fixed for the LVD, but evidently it is not fixed for the VGA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881046 Title: Panning in a virtual monitor is not possible after upgrade to Ubuntu 11.10 To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/881046/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 883319]
I have this bug when I use xrandr to resize the output to the VGA monitor, and then turn off the LVD using xrandr --output LVDS1 --off. The mouse becomes confined to the left side of the monitor as soon I turn off the LVD. I have version 2:1.11.4-0ubuntu10.13 of xorg-server, where this problem is supposed to be fixed for the LVD, but evidently it is not fixed for the VGA. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/883319 Title: xrandr --scale restricts area in which mouse moves To manage notifications about this bug go to: https://bugs.launchpad.net/xorg-server/+bug/883319/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 785362] Re: can't paste high-bit characters from font tool
It's a bug, since it used to work, e.g. when I used Debian instead of Ubuntu. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/785362 Title: can't paste high-bit characters from font tool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grace/+bug/785362/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 785362] Re: can't paste high-bit characters from font tool
It's definitely a grace bug, since I compiled grace-5.1.0 and the bug is not there. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/785362 Title: can't paste high-bit characters from font tool -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 785362] Re: can't paste high-bit characters from font tool
The only work-around I've found is to edit the grace file in a text editor to insert the desired special characters. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/785362 Title: can't paste high-bit characters from font tool -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 785362] Re: can't paste high-bit characters from font tool
I just rebuilt the latest stable grace from the source (grace-5.1.22) and I get the same error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/785362 Title: can't paste high-bit characters from font tool -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 785362] [NEW] can't paste high-bit characters from font tool
Public bug reported:
Binary package hint: grace
Font tool from the Window menu is supposed to help one find the syntax for
special characters. For example, it reports that
\f{Symbol}£ is the way to input the less than or equal sign from the symbol
font. However when I try to copy and paste this
into a text box, only the low-bit characters \f{Symbol} get pasted. The
high-bit one does not. I have to paste it into a terminal
window, say, recopy it, and paste again in grace. Maybe it's a motif or
lesstif problem, but I have only noticed it in grace so far.
** Affects: grace (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/785362
Title:
can't paste high-bit characters from font tool
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 785362] Re: can't paste high-bit characters from font tool
In fact, sometimes I can't even paste into grace using the method described above. For example it converts ò into ò which appears as junk in the graph. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/785362 Title: can't paste high-bit characters from font tool -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 619841] Re: [REGRESSION] e1000e doesnt work on 2.6.35.
I am suffering from this bug as well. It should be marked as important -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/619841 Title: [REGRESSION] e1000e doesnt work on 2.6.35. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 619841] Re: [REGRESSION] e1000e doesnt work on 2.6.35.
Brad, I am running Maverick, but I realized it's not the same bug. I get an IP address, but my problem is that the connection keeps disappearing at random but frequent intervals. I would be willing to test a new kernel. Can I just add an appropriate apt-source to install an alpha kernel with synaptic? If not some hints about installing kernels would be helpful. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/619841 Title: [REGRESSION] e1000e doesnt work on 2.6.35. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 689007] Re: Cannot connect to some unsecured public wifi networks
This is not really satisfactory. When I recently installed Ubuntu on my new laptop, only version 10.10 is listed as the current version. That's still the case. So I have to go hunting for an alpha version that might break other things in order to solve this problem? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/689007 Title: Cannot connect to some unsecured public wifi networks -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 689007] Re: Cannot connect to some unsecured public wifi networks
Has anyone tried a less radical solution like upgrading just the wpa_supplicant package? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/689007 Title: Cannot connect to some unsecured public wifi networks -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
