public inbox for linux-usb@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Robert NEMKIN <lists@buci.hu>
Cc: linux-usb@vger.kernel.org
Subject: Re: usb crash?
Date: Thu, 9 Jan 2025 13:09:28 +0100	[thread overview]
Message-ID: <2025010936-anthem-escapist-6e66@gregkh> (raw)
In-Reply-To: <a803932b-d0d2-4b32-8ef2-dc1beee7a47d@buci.hu>

On Thu, Jan 09, 2025 at 12:29:05PM +0100, Robert NEMKIN wrote:
> Hello everybody!
> 
> I saw a possibly kernel bug.
> It's a debian trixie with kernel compiled by myself.
> With 6.12.6 everything seems to be ok.
> With 6.12.7 and 6.12.8 I saw crasges in dmesg.
> I attached dmesg of some tries and lsusb.
> 
> Thanks for any hints.
> 
> Robert
> 

> dec 28 07:44:08 brick kernel: ------------[ cut here ]------------
> dec 28 07:44:08 brick kernel: WARNING: CPU: 0 PID: 296 at kernel/trace/trace_events.c:577 trace_event_raw_init+0x159/0x670
> dec 28 07:44:08 brick kernel: Modules linked in: xe(+) gpu_sched drm_suballoc_helper drm_gpuvm drm_exec drm_ttm_helper hid_generic usbhid hid i915 i2c_algo_bit drm_buddy drm_display_helper cec xhci_pci rc_core xhci_hcd ahci ttm libahci drm_kms_helper libata nvme intel_lpss_pci crc32_pclmul usbcore thunderbolt crc32c_intel drm scsi_mod igc intel_lpss i2c_i801 nvme_core idma64 scsi_common i2c_smbus video usb_common fan wmi

This isn't a USB issue, it's a tracing core issue with the xe driver.
It is fixed in commit afc6717628f9 ("tracing: Have process_string() also
allow arrays") which will be in the next 6.12.9 kernel release in a few
minutes.

It's a harmless warning for now, no need to worry.

thanks,

greg k-h

      reply	other threads:[~2025-01-09 12:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-09 11:29 usb crash? Robert NEMKIN
2025-01-09 12:09 ` Greg KH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2025010936-anthem-escapist-6e66@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lists@buci.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox