From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 215487] usb driver crash due to usbip events
Date: Fri, 08 Apr 2022 10:17:16 +0000 [thread overview]
Message-ID: <bug-215487-208809-oBRw3y92RH@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215487-208809@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215487
--- Comment #1 from Daniel Oltmanns (oltmanns@embedded.rwth-aachen.de) ---
UPDATE: We have upgraded to the new Bullseye 64Bit OS on the raspberry pi. We
now received the following error with the following Call trace:
Error: "Unable to handle kernel NULL pointer dereference at virtual address
000000000000004c"
Call Trace:
- stub_rx_loop+0x42c/0xb20 [usbip_host]
- kthread+0x140/0x158
- ret_from_fork+0x10/0x20
The full error message can be seen in the new attachment
'kernel_oops_bullseye'.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next parent reply other threads:[~2022-04-08 10:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-215487-208809@https.bugzilla.kernel.org/>
2022-04-08 10:17 ` bugzilla-daemon [this message]
2022-04-08 10:17 ` [Bug 215487] usb driver crash due to usbip events bugzilla-daemon
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=bug-215487-208809-oBRw3y92RH@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-usb@vger.kernel.org \
/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