Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #84574 > unrolled thread

Bug#1087748: linux-image-6.12-rc6-amd64: xHCI host not responding to stop endpoint command

Back to article view | Back to linux.debian.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#1087748: linux-image-6.12-rc6-amd64: xHCI host not responding to stop endpoint command Uwe Kleine-König <ukleinek@debian.org> - 2024-11-18 10:10 +0100
    Bug#1087748: linux-image-6.12-rc6-amd64: xHCI host not responding to stop endpoint command Roger Lynn <Roger@rilynn.me.uk> - 2024-11-18 12:10 +0100
      Bug#1087748: linux-image-6.12-rc6-amd64: xHCI host not responding to stop endpoint command Roger Lynn <Roger@rilynn.me.uk> - 2024-11-18 13:10 +0100
        Bug#1087748: linux-image-6.12-rc6-amd64: xHCI host not responding to stop endpoint command Uwe Kleine-König <ukleinek@debian.org> - 2024-11-21 22:50 +0100
          Bug#1087748: linux-image-6.12-rc6-amd64: xHCI host not responding to stop endpoint command Salvatore Bonaccorso <carnil@debian.org> - 2025-05-04 23:30 +0200

#84574 — Bug#1087748: linux-image-6.12-rc6-amd64: xHCI host not responding to stop endpoint command

[Multipart message — attachments visible in raw view] — view raw

On Sun, Nov 17, 2024 at 11:31:02PM +0000, Roger Lynn wrote:
> 
> [...]
> 2024-11-17T22:39:11.330714+00:00 thruxton kernel: [   17.609131] CR2: 0000562eaf13dec0 CR3: 00000005a6622000 CR4: 0000000000f50ef0
> 2024-11-17T22:39:11.330715+00:00 thruxton kernel: [   17.609132] PKRU: 55555554
> 2024-11-17T22:39:11.330715+00:00 thruxton kernel: [   17.609132] Call Trace:
> 2024-11-17T22:39:11.330715+00:00 thruxton kernel: [   17.609134]  <TASK>
> 2024-11-17T22:39:11.330715+00:00 thruxton kernel: [   17.609136]  ? __die_body.cold+0x19/0x27
> 2024-11-17T22:39:11.330716+00:00 thruxton kernel: [   17.609138]  ? die+0x2e/0x50
> 2024-11-17T22:39:11.330716+00:00 thruxton kernel: [   17.609140]  ? do_trap+0xca/0x110
> 2024-11-17T22:39:11.330717+00:00 thruxton kernel: [   17.609142]  ? do_error_trap+0x6a/0x90
> 2024-11-17T22:39:11.330717+00:00 thruxton kernel: [   17.609143]  ? __list_del_entry_valid_or_report.cold+0x5c/0x6f
> 2024-11-17T22:39:11.330717+00:00 thruxton kernel: [   17.609145]  ? exc_invalid_op+0x50/0x70
> 2024-11-17T22:39:11.330718+00:00 thruxton kernel: [   17.609148]  ? __list_del_entry_valid_or_report.cold+0x5c/0x6f
> 2024-11-17T22:39:11.330718+00:00 thruxton kernel: [   17.609149]  ? asm_exc_invalid_op+0x1a/0x20
> 2024-11-17T22:39:11.330718+00:00 thruxton kernel: [   17.609153]  ? __list_del_entry_valid_or_report.cold+0x5c/0x6f
> 2024-11-17T22:39:11.330719+00:00 thruxton kernel: [   17.609154]  ? __list_del_entry_valid_or_report.cold+0x5c/0x6f
> 2024-11-17T22:39:11.330719+00:00 thruxton kernel: [   17.609156]  hci_unregister_dev+0x46/0x1f0 [bluetooth]
> 2024-11-17T22:39:11.330719+00:00 thruxton kernel: [   17.609169]  btusb_disconnect+0x67/0x170 [btusb]
> 2024-11-17T22:39:11.330719+00:00 thruxton kernel: [   17.609172]  usb_unbind_interface+0x90/0x290 [usbcore]
> 2024-11-17T22:39:11.330720+00:00 thruxton kernel: [   17.609182]  device_release_driver_internal+0x19c/0x200
> 2024-11-17T22:39:11.330720+00:00 thruxton kernel: [   17.609185]  bus_remove_device+0xc6/0x130
> 2024-11-17T22:39:11.330720+00:00 thruxton kernel: [   17.609186]  device_del+0x161/0x3e0
> 2024-11-17T22:39:11.330721+00:00 thruxton kernel: [   17.609188]  ? kobject_put+0xa0/0x1d0
> 2024-11-17T22:39:11.330721+00:00 thruxton kernel: [   17.609190]  usb_disable_device+0xf4/0x210 [usbcore]
> 2024-11-17T22:39:11.330721+00:00 thruxton kernel: [   17.609198]  usb_disconnect+0xe6/0x2e0 [usbcore]
> 2024-11-17T22:39:11.330722+00:00 thruxton kernel: [   17.609205]  hub_quiesce+0x5e/0xc0 [usbcore]
> 2024-11-17T22:39:11.330722+00:00 thruxton kernel: [   17.609211]  hub_event+0x5bf/0x19d0 [usbcore]
> 2024-11-17T22:39:11.330722+00:00 thruxton kernel: [   17.609217]  ? ilookup+0x78/0x150
> 2024-11-17T22:39:11.330722+00:00 thruxton kernel: [   17.609219]  ? psi_task_switch+0x6b/0x200
> 2024-11-17T22:39:11.330723+00:00 thruxton kernel: [   17.609221]  ? finish_task_switch.isra.0+0x97/0x2c0
> 2024-11-17T22:39:11.330723+00:00 thruxton kernel: [   17.609223]  ? kernfs_notify_workfn+0x36/0x220
> 2024-11-17T22:39:11.330723+00:00 thruxton kernel: [   17.609225]  process_one_work+0x174/0x330
> 2024-11-17T22:39:11.330724+00:00 thruxton kernel: [   17.609227]  worker_thread+0x252/0x390
> 2024-11-17T22:39:11.330724+00:00 thruxton kernel: [   17.609229]  ? __pfx_worker_thread+0x10/0x10
> 2024-11-17T22:39:11.330724+00:00 thruxton kernel: [   17.609231]  kthread+0xcf/0x100
> 2024-11-17T22:39:11.330725+00:00 thruxton kernel: [   17.609233]  ? __pfx_kthread+0x10/0x10
> 2024-11-17T22:39:11.330725+00:00 thruxton kernel: [   17.609235]  ret_from_fork+0x31/0x50
> 2024-11-17T22:39:11.330725+00:00 thruxton kernel: [   17.609236]  ? __pfx_kthread+0x10/0x10
> 2024-11-17T22:39:11.330725+00:00 thruxton kernel: [   17.609238]  ret_from_fork_asm+0x1a/0x30
> 2024-11-17T22:39:11.330726+00:00 thruxton kernel: [   17.609241]  </TASK>

I guess this is a duplicate of https://bugs.debian.org/1069301. There
are some reverts scheduled for 6.1.y, see https://bugs.debian.org/1069301#74

If you can provide test feedback that would be great.

Best regards
Uwe

[toc] | [next] | [standalone]

#84579

On 18/11/2024 09:05, Uwe Kleine-König wrote:
> I guess this is a duplicate of https://bugs.debian.org/1069301. There
> are some reverts scheduled for 6.1.y, see https://bugs.debian.org/1069301#74
> 
> If you can provide test feedback that would be great.

It does appear to be similar, but I see no indication in any of the discussion
of that bug affecting the latest 6.11 and 6.12 kernels, and there are not yet
any later kernels packaged in Debian for me to test. The 6.1 kernel in Debian
stable does not support my bluetooth interface and so does not show the bug.

Also I'm not clear as to whether this bug is causing the xHCI host controller to
stop responding or if it is a separate issue. I'll try with an updated kernel
when one becomes available with a fix for this bug and hope that the xHCI
problem also goes away.

Thanks,

Roger

[toc] | [prev] | [next] | [standalone]

#84582

On 18/11/2024 10:35, Roger Lynn wrote:
> On 18/11/2024 09:05, Uwe Kleine-König wrote:
>> I guess this is a duplicate of https://bugs.debian.org/1069301. There
>> are some reverts scheduled for 6.1.y, see https://bugs.debian.org/1069301#74
>> 
>> If you can provide test feedback that would be great.
> 
> It does appear to be similar, but I see no indication in any of the discussion
> of that bug affecting the latest 6.11 and 6.12 kernels, and there are not yet
> any later kernels packaged in Debian for me to test. The 6.1 kernel in Debian
> stable does not support my bluetooth interface and so does not show the bug.

It was assumed that #1069301 applied only to 6.1, as a result of a reports of it
not affecting 6.9-rc5[0], 6.10.11+bpo-amd64[1] and 6.6.13-1~bpo12+1[2].

[0] https://lore.kernel.org/all/ecee3a54-1a09-40fa-afdb-057ca02cb574@leemhuis.info/
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069301#62
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069301#67

[toc] | [prev] | [next] | [standalone]

#84623

[Multipart message — attachments visible in raw view] — view raw

On Mon, Nov 18, 2024 at 12:05:40PM +0000, Roger Lynn wrote:
> On 18/11/2024 10:35, Roger Lynn wrote:
> > On 18/11/2024 09:05, Uwe Kleine-König wrote:
> >> I guess this is a duplicate of https://bugs.debian.org/1069301. There
> >> are some reverts scheduled for 6.1.y, see https://bugs.debian.org/1069301#74
> >> 
> >> If you can provide test feedback that would be great.
> > 
> > It does appear to be similar, but I see no indication in any of the discussion
> > of that bug affecting the latest 6.11 and 6.12 kernels, and there are not yet
> > any later kernels packaged in Debian for me to test. The 6.1 kernel in Debian
> > stable does not support my bluetooth interface and so does not show the bug.
> 
> It was assumed that #1069301 applied only to 6.1, as a result of a reports of it
> not affecting 6.9-rc5[0], 6.10.11+bpo-amd64[1] and 6.6.13-1~bpo12+1[2].
> 
> [0] https://lore.kernel.org/all/ecee3a54-1a09-40fa-afdb-057ca02cb574@leemhuis.info/
> [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069301#62
> [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069301#67

Yes, you're entirely right, seems to be a different issue.

I took a quick look in the respective source code and checked if there
are commits upstream that might address this issue, but I didn't find
anything. I think the right thing to do is to report your issue
upstream. For someone knowing about the bluetooth stack, the list
poisoning might be actionable.

Do you want to do that, or should one of the Debian kernel team take
care? If you do, please keep 1087748@bugs.debian.org in Cc:.

Best regards
Uwe

[toc] | [prev] | [next] | [standalone]

#87360

Hi Roger,

On Thu, Nov 21, 2024 at 10:38:04PM +0100, Uwe Kleine-König wrote:
> On Mon, Nov 18, 2024 at 12:05:40PM +0000, Roger Lynn wrote:
> > On 18/11/2024 10:35, Roger Lynn wrote:
> > > On 18/11/2024 09:05, Uwe Kleine-König wrote:
> > >> I guess this is a duplicate of https://bugs.debian.org/1069301. There
> > >> are some reverts scheduled for 6.1.y, see https://bugs.debian.org/1069301#74
> > >> 
> > >> If you can provide test feedback that would be great.
> > > 
> > > It does appear to be similar, but I see no indication in any of the discussion
> > > of that bug affecting the latest 6.11 and 6.12 kernels, and there are not yet
> > > any later kernels packaged in Debian for me to test. The 6.1 kernel in Debian
> > > stable does not support my bluetooth interface and so does not show the bug.
> > 
> > It was assumed that #1069301 applied only to 6.1, as a result of a reports of it
> > not affecting 6.9-rc5[0], 6.10.11+bpo-amd64[1] and 6.6.13-1~bpo12+1[2].
> > 
> > [0] https://lore.kernel.org/all/ecee3a54-1a09-40fa-afdb-057ca02cb574@leemhuis.info/
> > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069301#62
> > [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1069301#67
> 
> Yes, you're entirely right, seems to be a different issue.
> 
> I took a quick look in the respective source code and checked if there
> are commits upstream that might address this issue, but I didn't find
> anything. I think the right thing to do is to report your issue
> upstream. For someone knowing about the bluetooth stack, the list
> poisoning might be actionable.
> 
> Do you want to do that, or should one of the Debian kernel team take
> care? If you do, please keep 1087748@bugs.debian.org in Cc:.

Any news here? Is the issue still triggered with a recent 6.12.25-1
(and/or 6.14.5-1~exp1)? If so have you seen the question from Uwe
about reporting upstream?

Regards,
Salvatore

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web