[DE] Problems with kernel 6.11.7-1 or is it only me?

[Geier0815]

After upgrading to linux-image-6.11.7-1-siduction-amd64 my system won't boot. I can see a "clean" for filesystemcheck on boot and then a message appears that say something about "couldn t find input interrupt endpoint" and the system stop.

With 6.11.6-1-siduction-amd64 no problems. Is this only me?

[edlin]

Zumindest ist es kein generelles Problem. Bei mir bootet der neue Kernel problemlos und ohne jegliches Gemecker.
Vielleicht kannst du uns etwas mehr Input (Fehlermeldung, logs, Hardware) liefern.

Klick mich

[dibl]

Code: [Select]

don@hibiscus:~$ uname -a
Linux hibiscus 6.11.7-1-siduction-amd64 #1 SMP PREEMPT_DYNAMIC siduction 6.11-7 (2024-11-08) x86_64 GNU/Linux
Booting and running OK here, including Nvidia graphics and qemu/KVM, 2 systems updated so far.

[michaa7]

After upgrading to linux-image-6.11.7-1-siduction-amd64 my system won't boot. I can see a "clean" for filesystemcheck on boot and then a message appears that say something about "couldn t find input interrupt endpoint" and the system stop.

With 6.11.6-1-siduction-amd64 no problems. Is this only me?

I have it very similar:

Boot stops at "Clean" for the system partition with the cursor jumping to the down right corner and there blinking.

I then stop booting by pressing the on-off switch for more then 4 seconds and try it again which then works.

[Penyelam]

Here also everything OK.

Code: [Select]

System:
  Host: tuxedo Kernel: 6.11.7-1-siduction-amd64 arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 5.27.11 Distro: siduction 2023.1.1 giants - kde -
    (202408281924)


[hendrikL]

Here also no™ problems with that kernel!

Code: [Select]

inxi -SG
System:
  Host: hhl-2 Kernel: 6.11.7-1-siduction-amd64 arch: x86_64 bits: 64
  Desktop: KDE Plasma v: 6.2.2 Distro: siduction 22.1.2 Masters_of_War -
    kde - (202303151559)
Graphics:
  Device-1: Intel 3rd Gen Core processor Graphics driver: i915 v: kernel
  Device-2: Chicony USB2.0 HD UVC WebCam driver: uvcvideo type: USB
  Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4
    compositor: kwin_wayland driver: X: loaded: modesetting unloaded: fbdev,vesa
    dri: crocus gpu: i915 resolution: 1366x768
  API: EGL v: 1.5 drivers: crocus,swrast
    platforms: gbm,wayland,x11,surfaceless,device
  API: OpenGL v: 4.5 compat-v: 4.2 vendor: intel mesa v: 24.2.6-1
    renderer: Mesa Intel HD Graphics 4000 (IVB GT2)
  API: Vulkan v: 1.3.296 drivers: N/A surfaces: xcb,xlib,wayland


[sedonix]

I only use the experimental kernels and the identical problem as described by the OP & michaa7 showed up awhile back and still persists. I was hoping it would go away on subsequent kernels.

$ inxi
CPU: quad core Intel Core i5-6400 (-MCP-) speed/min/max: 800/800/3300 MHz
Kernel: 6.12-rc7-siduction-amd64 x86_64 Up: 5h 30m Mem: 1.09/7.67 GiB (14.2%)
Storage: 2.27 TiB (48.8% used) Procs: 184 Shell: Bash inxi: 3.3.36

[hendrikL]

It would be helpful to post the graphic card 'inxi -G' and error messages you can find (take a look to dmesg, journalctl). Are you using wayland or xserver ...

Edit:
PS.: The CPU is also interesting, 'inxi -C' or do you have a special command in the boot parameters 'cat /proc/cmdline'
 

[Geier0815]

It seems to be a problem with my Logitech M500S mouse. If the mouse is disconnected or switched to an other computer by KVM the system boots fine. If I connect the mouse after the system is up, it works like a charm. On the other computer with debian stable are no issues.

[ro_sid]

Problems of "your type" have been reported in the web for years. Most of them with USB devices, some with graphic cards. As far as I can tell, all vanished with one of the following kernels.
For Siduction, we have a 6.11.8 kernel (since yesterday?). Thus you can ditch the 6.11.7 kernel and hopefully the newer one already works as expected.
If not, please report it. It may be worth to study the "old/historic" problems for preliminary solutions, then.
Best of luck.

[Geier0815]

Sorry, no luck with the new 6.11.8, maybe with another of the next ones. For me it's no problem to switch with the KVM for 10 seconds or so during boot, so don't rack your brains

[michaa7]

Here this problem persists even with siduction and with pure Debian 6.11.9 kernel.

But the hang can be stopped by waiting some seconds and simply press the enter key. boot then will go on ...

[DeepDayze]

Here this problem persists even with siduction and with pure Debian 6.11.9 kernel.

But the hang can be stopped by waiting some seconds and simply press the enter key. boot then will go on ...

Great tip and I'll try that if kernel hangs again at boot right after the "Linux clean..." message.

[Geier0815]

I will give it a try also