November 2022 - openSUSE Kernel Bugs - openSUSE Mailing Lists

[Bug 1205660] Fix non-working Realtek USB ethernet after system resume
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205660 https://bugzilla.suse.com/show_bug.cgi?id=1205660#c12 --- Comment #12 from Takashi Iwai <tiwai(a)suse.com> --- So the network worked even with r8153_ecm blacklisted, and the suspend/resume problem persists even after the blacklist? If so, another test would be to pass usbcore.autosuspend=-1 boot option while keeping the blacklist. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205740] New: btrfs fails to act on fs if the fs is read-only
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205740 Bug ID: 1205740 Summary: btrfs fails to act on fs if the fs is read-only Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: william.brown(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Transactional server mounts in read only mode on /. This causes all btrfs management commands to fail. # btrfs balance start -f -sconvert=dup -mconvert=dup -dconvert=single / ERROR: error during balancing '/': Read-only file system There may be more info in syslog - try dmesg | tail However if you (on the same filesystem/pool) do this to /home, it works since that's mounted rw. This is an extremely surprising and unintuitive behaviour. -- You are receiving this mail because: You are the assignee for the bug.

1 1

[Bug 1205751] RPI4: black screen on boot
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205751 https://bugzilla.suse.com/show_bug.cgi?id=1205751#c5 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE --- Comment #5 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Ivan Ivanov from comment #4) > I would say duplicate of bsc#1205259. Indeed! *** This bug has been marked as a duplicate of bug 1205259 *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205259] WIth kernel 6.0.7-1 on raspberry pi400 nothing displayed on HDMI ports
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205259 https://bugzilla.suse.com/show_bug.cgi?id=1205259#c10 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrian.schroeter(a)suse.com --- Comment #10 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- *** Bug 1205751 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205751] RPI4: black screen on boot
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205751 https://bugzilla.suse.com/show_bug.cgi?id=1205751#c4 --- Comment #4 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- I would say duplicate of bsc#1205259. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205751] RPI4: black screen on boot
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205751 https://bugzilla.suse.com/show_bug.cgi?id=1205751#c3 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(guillaume.gardet@ | |arm.com) | --- Comment #3 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- (In reply to Ivan Ivanov from comment #2) > Exact kernel version, please? It fails with 6.0.8-1-default. According to the user report on the mailing list it worked with 6.0.3 -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205751] RPI4: black screen on boot
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205751 https://bugzilla.suse.com/show_bug.cgi?id=1205751#c2 Ivan Ivanov <ivan.ivanov(a)suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(guillaume.gardet@ | |arm.com) --- Comment #2 from Ivan Ivanov <ivan.ivanov(a)suse.com> --- Exact kernel version, please? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205751] RPI4: black screen on boot
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205751 https://bugzilla.suse.com/show_bug.cgi?id=1205751#c1 Guillaume GARDET <guillaume.gardet(a)arm.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CONFIRMED Component|Basesystem |Kernel Assignee|screening-team-bugs(a)suse.de |kernel-bugs(a)opensuse.org --- Comment #1 from Guillaume GARDET <guillaume.gardet(a)arm.com> --- This has been reported on the mailing list as well: https://lists.opensuse.org/archives/list/arm@lists.opensuse.org/thread/X526… I can reproduce locally with latest JeOS image for Raspberry Pi: HDMI output goes down once drm/vc4 driver takes over. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c54 --- Comment #54 from Takashi Iwai <tiwai(a)suse.com> --- I meant not the "section" but just the all output from dmesg. That is, simply run dmesg > dmesg.out and attach the dmesg.out file to Bugzilla. For debugging such hardware issues, you need to see the full picture, not only the focused on. Especially a case like this is involved with different layers (the input device is enabled via ACPI, then transport via designware i2c bus over kernel i2c layer, kernel HID layer, kernel HID touchpad driver, then kernel input driver, finally comes to user-space, then interpreted by libinput, and reaches to the desktop environment at last -- maybe there are something middle I forgot, too). -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c53 --- Comment #53 from Paul Soto <pst73de(a)yahoo.com> --- how full is full? I pasted you the section that gets logged after resume from STR. there is nothing else related to the touchpad driver -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205741] New: btrfs splitting a raid1 mirror is "not a trivial process".
by bugzilla_noreply＠suse.com 25 Nov '22

25 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205741 Bug ID: 1205741 Summary: btrfs splitting a raid1 mirror is "not a trivial process". Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: william.brown(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- In zfs if I have a pool of two disks in a raid 1 mirror and want to "split" that to remove a single device (say I'm replacing it, and can't add all three at once)., all I have to do is: zpool remove pool device. In btrfs you can't simply break a raid1 mirror and you have to go through a very confusing and tedious process. First, you need to find which devid you need to remove: # btrfs filesystem show Label: none uuid: cfa4961a-bb45-4941-ae70-948bb27fdd9b Total devices 2 FS bytes used 101.68GiB devid 1 size 256.00GiB used 103.03GiB path /dev/nvme0n1p2 devid 2 size 256.00GiB used 103.03GiB path /dev/nvme1n1p2 Then you have to rebalance to raid0 (jbod?). It's unclear where stripes of data are moved and rebalanced here. The rebalance command is not trivial either, required a bit of knowledge about what is a data,system and metadata chunk. # btrfs balance start -f -sconvert=dup -mconvert=dup -dconvert=single / So at this point I can only assume my raid 1 is now a raid 0 and data is striped over two devices (reducing redundancy). Then I can finally split this with: # btrfs device remove 2 /home Beside being very confusing, this process does open up the possibility of surprise dataloss due to the raid 1 -> raid 0 conversion in the middle, as well as generally being very time consuming. Breaking mirrors to remove a drive and replace a new one in should be a routine and easy task but it's not so here. I think the user experience here should be improved so that I can "break" a raid 1 mirror, keep it as "raid 1" in the btrfs metadata and just remove a single device into a degraded mode before replacing in the new one. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1203748] New: Laptop very slow in battery mode (Lenovo Thinkpad T470)
by bugzilla_noreply＠suse.com 24 Nov '22

24 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1203748 Bug ID: 1203748 Summary: Laptop very slow in battery mode (Lenovo Thinkpad T470) Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.4 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: sndirsch(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- For some reason my laptop gets very slow in battery only mode. I notice this when watching videos. It makes it rather unusable when not connecting it to power. It looks like it goes into some deep powersave mode. I would like to avoid this even if this would half the running time in battery mode. Which information do you need? -- You are receiving this mail because: You are the assignee for the bug.

1 26

[Bug 1137748] suspend to RAM no longer working after upgrade to Leap 15.1
by bugzilla_noreply＠suse.com 24 Nov '22

24 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1137748 http://bugzilla.opensuse.org/show_bug.cgi?id=1137748#c140 --- Comment #140 from Takashi Iwai <tiwai(a)suse.com> --- Mainly because the problem happens only on certain (likely old) machines under some situations. And partly because debugging the suspend/resume problem is *VERY* difficult to do remotely; the suspend/resume can't leave much logs unless you set up specially. At least you can try the latest upstream kernel from OBS Kernel:stable:Backport, and check whether the problem persists. If yes, the issue should be reported rather to the upstream and handled there. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 24 Nov '22

24 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c52 --- Comment #52 from Takashi Iwai <tiwai(a)suse.com> --- Again: * Please don't paste too long texts on the form but use attachments * Please give the full dmesg output instead of snippet -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 24 Nov '22

24 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c51 --- Comment #51 from Paul Soto <pst73de(a)yahoo.com> --- 2022-10-26T00:40:43.770672-04:00 t16 kernel: [ 8234.507064][ T5334] PM: hibernation: hibernation entry 2022-10-26T00:40:57.849014-04:00 t16 kernel: [ 8234.586000][ T5334] Filesystems sync: 0.011 seconds 2022-10-26T00:40:57.849145-04:00 t16 kernel: [ 8234.586006][ T5334] Freezing user space processes ... (elapsed 12.299 seconds) done. 2022-10-26T00:40:57.849150-04:00 t16 kernel: [ 8246.885774][ T5334] OOM killer disabled. 2022-10-26T00:40:57.849152-04:00 t16 kernel: [ 8246.886134][ T5334] PM: hibernation: Marking nosave pages: [mem 0x00000000-0x00000fff] 2022-10-26T00:40:57.849153-04:00 t16 kernel: [ 8246.886144][ T5334] PM: hibernation: Marking nosave pages: [mem 0x0009f000-0x000fffff] 2022-10-26T00:40:57.849155-04:00 t16 kernel: [ 8246.886152][ T5334] PM: hibernation: Marking nosave pages: [mem 0x88906000-0x8894dfff] 2022-10-26T00:40:57.849160-04:00 t16 kernel: [ 8246.886158][ T5334] PM: hibernation: Marking nosave pages: [mem 0x89252000-0x89252fff] 2022-10-26T00:40:57.849162-04:00 t16 kernel: [ 8246.886181][ T5334] PM: hibernation: Marking nosave pages: [mem 0x8db6f000-0x937fefff] 2022-10-26T00:40:57.849199-04:00 t16 kernel: [ 8246.887174][ T5334] PM: hibernation: Marking nosave pages: [mem 0x93800000-0xffffffff] 2022-10-26T00:40:57.849200-04:00 t16 kernel: [ 8246.891016][ T5334] PM: hibernation: Basic memory bitmaps created 2022-10-26T00:40:57.849201-04:00 t16 kernel: [ 8246.891754][ T5334] PM: hibernation: Preallocating image memory 2022-10-26T00:40:57.849202-04:00 t16 kernel: [ 8247.113079][ T5334] PM: hibernation: Allocated 881810 pages for snapshot 2022-10-26T00:40:57.849203-04:00 t16 kernel: [ 8247.113080][ T5334] PM: hibernation: Allocated 3527240 kbytes in 0.22 seconds (16032.90 MB/s) 2022-10-26T00:40:57.849204-04:00 t16 kernel: [ 8247.113082][ T5334] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. 2022-10-26T00:40:57.849206-04:00 t16 kernel: [ 8247.114516][ T5334] printk: Suspending console(s) (use no_console_suspend to debug) 2022-10-26T00:40:57.849207-04:00 t16 kernel: [ 8247.121125][ T1043] i2c_hid_acpi i2c-ELAN0683:00: i2c_hid_get_input: incomplete report (14/259) 2022-10-26T00:40:57.849208-04:00 t16 kernel: [ 8247.123101][ T1043] i2c_hid_acpi i2c-ELAN0683:00: i2c_hid_get_input: incomplete report (14/1) 2022-10-26T00:40:57.849209-04:00 t16 kernel: [ 8247.393948][ T4740] xhci_hcd 0000:00:14.0: PM: pci_pm_freeze(): hcd_pci_suspend+0x0/0x30 [usbcore] returns -16 2022-10-26T00:40:57.849211-04:00 t16 kernel: [ 8247.394025][ T4740] xhci_hcd 0000:00:14.0: PM: dpm_run_callback(): pci_pm_freeze+0x0/0xd0 returns -16 2022-10-26T00:40:57.849212-04:00 t16 kernel: [ 8247.394041][ T4740] xhci_hcd 0000:00:14.0: PM: failed to freeze async: error -16 2022-10-26T00:40:57.849213-04:00 t16 kernel: [ 8247.850542][ T5705] nvme nvme0: 7/0/0 default/read/poll queues 2022-10-26T00:40:57.849214-04:00 t16 kernel: [ 8247.852188][ T4761] i915 0000:00:02.0: [drm] GuC firmware i915/adlp_guc_70.1.1.bin version 70.1 2022-10-26T00:40:57.849215-04:00 t16 kernel: [ 8247.852190][ T4761] i915 0000:00:02.0: [drm] HuC firmware i915/tgl_huc_7.9.3.bin version 7.9 2022-10-26T00:40:57.849216-04:00 t16 kernel: [ 8247.867776][ T4761] i915 0000:00:02.0: [drm] HuC authenticated 2022-10-26T00:40:57.849218-04:00 t16 kernel: [ 8247.867976][ T4761] i915 0000:00:02.0: [drm] GuC submission enabled 2022-10-26T00:40:57.849219-04:00 t16 kernel: [ 8247.867976][ T4761] i915 0000:00:02.0: [drm] GuC SLPC enabled 2022-10-26T00:40:57.849220-04:00 t16 kernel: [ 8247.868565][ T4761] i915 0000:00:02.0: [drm] GuC RC: enabled 2022-10-26T00:40:57.849221-04:00 t16 kernel: [ 8248.587458][ T5334] PM: hibernation: Basic memory bitmaps freed 2022-10-26T00:40:57.849222-04:00 t16 kernel: [ 8248.587465][ T5334] OOM killer enabled. 2022-10-26T00:40:57.849223-04:00 t16 kernel: [ 8248.587467][ T5334] Restarting tasks ... 2022-10-26T00:40:57.849225-04:00 t16 kernel: [ 8248.587767][ T5692] mei_hdcp 0000:00:16.0-b638ab7e-94e2-4ea2-a552-d1c54b627f04: bound 0000:00:02.0 (ops i915_hdcp_component_ops [i915]) 2022-10-26T00:40:57.850670-04:00 t16 kernel: [ 8248.589439][ T5334] done. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1137748] suspend to RAM no longer working after upgrade to Leap 15.1
by bugzilla_noreply＠suse.com 23 Nov '22

23 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1137748 http://bugzilla.opensuse.org/show_bug.cgi?id=1137748#c139 christian mathieu <cma63(a)free.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|Normal |Major --- Comment #139 from christian mathieu <cma63(a)free.fr> --- Hello. Why is this old bug not fixed ? OpenSUSE is the only distribution affected ! I prefer OpenSUSE, but I can't install it! Kind regards -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205649] New: SEGV when mounting / during boot
by bugzilla_noreply＠suse.com 23 Nov '22

23 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205649 Bug ID: 1205649 Summary: SEGV when mounting / during boot Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Critical Priority: P5 - None Component: Kernel Assignee: kernel-bugs(a)opensuse.org Reporter: thomas.leroy(a)suse.com QA Contact: qa-bugs(a)suse.de Found By: --- Blocker: --- Created attachment 863042 --> https://bugzilla.suse.com/attachment.cgi?id=863042&action=edit Kernel BUG I receive a kernel BUG during boot when trying to mount the root partition. Unfortunately I can't copy/paste the journalctl output because it's the laptop's host kernel, but I linked a picture of the kernel BUG information. I'm running Tumbleweed with a 6.0.8-1-vanilla kernel on x86_64. Additionally, I tried to mount the decrypted disk in a live usb, and mount also segfaulted. -- You are receiving this mail because: You are the assignee for the bug.

1 2

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 23 Nov '22

23 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c50 --- Comment #50 from Takashi Iwai <tiwai(a)suse.com> --- Please give the full dmesg output instead of snippet. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c49 --- Comment #49 from Paul Soto <pst73de(a)yahoo.com> --- what appeared in kernel log after the touchpad switched into crazy mode after wake up from STR: 2022-11-10T16:48:25.834049-05:00 t16 kernel: [ 8262.080731][ T1015] i2c_hid_acpi i2c-ELAN0683:00: i2c_hid_get_input: incomplete report (14/255) 2022-11-10T16:48:25.834050-05:00 t16 kernel: [ 8262.082980][ T1015] i2c_hid_acpi i2c-ELAN0683:00: i2c_hid_get_input: incomplete report (14/65280) 2022-11-11T14:45:25.960183-05:00 t16 kernel: [ 8391.816413][ T1015] i2c_hid_acpi i2c-ELAN0683:00: i2c_hid_get_input: incomplete report (14/255) 2022-11-11T14:45:25.960184-05:00 t16 kernel: [ 8391.817710][ T1015] i2c_hid_acpi i2c-ELAN0683:00: i2c_hid_get_input: incomplete report (14/259) 2022-11-11T14:45:25.960207-05:00 t16 kernel: [ 8391.818875][ T1015] i2c_hid_acpi i2c-ELAN0683:00: i2c_hid_get_input: incomplete report (14/65281) apparently from drivers/hid/i2c-hid/i2c-hid-core.c -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c48 --- Comment #48 from Takashi Iwai <tiwai(a)suse.com> --- Also give the dmesg output, too. The hwinfo and dmesg outputs are required to figure out exactly which device is on your machine and what are probed, also whether any relevant info / error is seen from the kernel. To deal with a hardware issue like this, you always need to know the detailed hardware information as much as possible before going further. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205410] Thinkpad T16 touchpad does not work correctly after resume
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

http://bugzilla.opensuse.org/show_bug.cgi?id=1205410 http://bugzilla.opensuse.org/show_bug.cgi?id=1205410#c47 --- Comment #47 from Paul Soto <pst73de(a)yahoo.com> --- Created attachment 863047 --> http://bugzilla.opensuse.org/attachment.cgi?id=863047&action=edit hwinfo doubt hwinfo will help you -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205576 https://bugzilla.suse.com/show_bug.cgi?id=1205576#c10 --- Comment #10 from Takashi Iwai <tiwai(a)suse.com> --- Ah right, I forgot one more step. I thought it were done automatically, but apparently not. Run as root: make modules_install *before* running "make install". This will install modules. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205576 https://bugzilla.suse.com/show_bug.cgi?id=1205576#c9 --- Comment #9 from Philippe Cond� <conde.philippe(a)skynet.be> --- hello, I followed your instructions but the build kernel gives a infinite loop start -> reboot. I see this remark with sudo make install "philippe@hpprol2:~/kernel_clone/linux> sudo make install [sudo] Mot de passe de philippe�: INSTALL /boot renamed '/boot/config-6.0.7-test07' -> '/boot/config-6.0.7-test07.old' Certificate must have Code Signing extended key usage defined for Secure Boot. You may need to create an initial ramdisk now. " but mkinitrd doesn't take kernel 6.0.7-test07 in account I see in /boot that the config-6.0.7.test07 is not linked to a lib/module directory lrwxrwxrwx 1 root root 41 Nov 7 14:07 config-6.0.7-1-default -> ../usr/lib/modules/6.0.7-1-default/config -rw-r--r-- 1 philippe users 171587 Nov 22 12:33 config-6.0.7-test07 -rw-r--r-- 1 philippe users 171587 Nov 22 12:33 config-6.0.7-test07.old lrwxrwxrwx 1 root root 41 Nov 14 14:07 config-6.0.8-1-default -> ../usr/lib/modules/6.0.8-1-default/config lrwxrwxrwx 1 root root 50 Nov 22 08:30 config-6.0.9-2.g699b9c2-default -> ../usr/lib/modules/6.0.9-2.g699b9c2-default/config drwxr-xr-x 6 root root 4096 Nov 22 14:12 grub2 lrwxrwxrwx 1 root root 31 Nov 22 08:30 initrd -> initrd-6.0.9-2.g699b9c2-default -rw------- 1 root root 20359727 Nov 22 13:50 initrd-6.0.7-1-default -rw------- 1 root root 20361111 Nov 22 13:50 initrd-6.0.8-1-default -rw------- 1 root root 20343116 Nov 22 13:50 initrd-6.0.9-2.g699b9c2-default any advice? -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205576 https://bugzilla.suse.com/show_bug.cgi?id=1205576#c8 --- Comment #8 from Takashi Iwai <tiwai(a)suse.com> --- In this case, it might be better to run git bisect on linux-stable git tree, supposing it's an upstream problem. Clone the linux-stable.git from either github.com or git.kernel.org. https://github.com/gregkh/linux or git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git Then checkout v6.0.7, copy the kernel config from the running kernel: % git checkout v6.0.7 % zcat /proc/config.gz > .config Edit .config file to change CONFIG_LOCALVERSION, set it to a unique prefix (e.g. "-test"). The next step is to reduce the needed config to match with the currently used modules (which will reduce the compile time a lot): % make localmodconfig You'll need a few more packages like kernel-install-tools, etc. Then make, and install it % make -j8 % sudo make install Confirm that it's working. Then checkout v6.0.8, build, install, and retest. Confirm that the problem appears. Once after confirming the bug reproduction, go for bisection. % git bisect start % git bisect good v6.0.7 % git bisect bad v6.0.8 Again, build, install and retest. If the kernel is good, give "git bisect good". If it's buggy, "git bisect bad". Then git will lead to another commit to test. It's repeated until you find the first buggy commit. As a hint: it might be better to change the kernel suffix at each time not to conflict with the previous kernels (e.g. name it "bisect1" or such). And, be careful to choose the kernel to boot at GRUB. It's crucial to know exactly which kernel / commit you're testing. -- You are receiving this mail because: You are the assignee for the bug.

1 0

[Bug 1205576] General protection fault With kernel 6.0.8. and game pysolfc
by bugzilla_noreply＠suse.com 22 Nov '22

22 Nov '22

https://bugzilla.suse.com/show_bug.cgi?id=1205576 https://bugzilla.suse.com/show_bug.cgi?id=1205576#c7 --- Comment #7 from Philippe Cond� <conde.philippe(a)skynet.be> --- Hello, I have the kernel sources installed and I think all development tools needed. Can I follow this guide? https://github.com/openSUSE/kernel-source/blob/master/doc/README.SUSE I never did a run git bisect so I need some instructions about this Regards Philippe -- You are receiving this mail because: You are the assignee for the bug.

1 0