From: bugzilla-daemon@bugzilla.kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 206365] New: kernel NULL pointer dereference when charger is unplugged
Date: Fri, 31 Jan 2020 08:22:53 +0000 [thread overview]
Message-ID: <bug-206365-208809@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=206365
Bug ID: 206365
Summary: kernel NULL pointer dereference when charger is
unplugged
Product: Drivers
Version: 2.5
Kernel Version: 5.3.4-300.fc31.x86_64
Hardware: x86-64
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: USB
Assignee: drivers_usb@kernel-bugs.kernel.org
Reporter: andrea.lagala@gmail.com
Regression: No
Created attachment 287039
--> https://bugzilla.kernel.org/attachment.cgi?id=287039&action=edit
lshw output
Every time I unplug my charger, I get a oops about a NULL pointer dereference.
The computer then slows down to a crawl, up until it fully freezes. ABRT tries
to get a report, but never gets to write any data. I installed kdump and forced
the panic on oops setting to get as much data as possible. I initially thought
that tlp was the culprit; deactivating it yielded no improvements. Then,
reading dmesg while troubleshooting I noticed lockdown was blocking direct
writes to registers. I disabled Secure Boot but the problem still is there.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2020-01-31 8:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-31 8:22 bugzilla-daemon [this message]
2020-01-31 8:27 ` [Bug 206365] kernel NULL pointer dereference when charger is unplugged bugzilla-daemon
2020-01-31 8:28 ` bugzilla-daemon
2020-01-31 8:30 ` [Bug 206365] New: " Greg KH
2020-01-31 8:30 ` [Bug 206365] " 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-206365-208809@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.