From: bugzilla-daemon@bugzilla.kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 206235] kernel BUG at mm/slub.c:294
Date: Sat, 07 Mar 2020 21:36:42 +0000 [thread overview]
Message-ID: <bug-206235-62941-FxTPjZ4tFs@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206235-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206235
Steffen Nurpmeso (steffen@sdaoden.eu) changed:
What |Removed |Added
----------------------------------------------------------------------------
Kernel Version|4.19.94 |4.19.107
--- Comment #3 from Steffen Nurpmeso (steffen@sdaoden.eu) ---
And one more addition, because whereas r8822be for Wifi is in staging in 4.19,
the bluetooth one is not, i think. (No idea of kernel, actually.) And the
rfkill(1) did only act on bluetooth here, since Wifi was gone before:
Mar 7 01:56:37 kent rfkill: block set for type wlan
..
Mar 7 01:56:37 kent dhcpcd[516]: script_runreason:
/lib/dhcpcd/dhcpcd-run-hooks: WEXITSTATUS 1
Mar 7 02:14:16 kent root/acpid[2549]: 3: button/lid LID close
...
Mar 7 02:14:37 kent root/zzz[2585]: ( rfkill block all ) </dev/null & sleep 2
...
Mar 7 02:14:41 kent root/zzz[2608]: sync
Mar 7 02:14:41 kent root/zzz[2610]: echo mem > /sys/power/state
Mar 7 02:15:02 kent root/zzz[2615]: echo mem > /sys/power/state
Mar 7 02:15:23 kent root/zzz[2618]: echo mem > /sys/power/state
..in a loop until i realized it..
Ciao, and a nice Sunday i wish from Germany
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2020-03-07 21:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 13:38 [Bug 206235] New: kernel BUG at mm/slub.c:294 bugzilla-daemon
2020-01-17 13:42 ` [Bug 206235] " bugzilla-daemon
2020-03-07 20:21 ` bugzilla-daemon
2020-03-07 20:25 ` bugzilla-daemon
2020-03-07 21:36 ` bugzilla-daemon [this message]
2020-07-04 15:26 ` 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-206235-62941-FxTPjZ4tFs@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-bluetooth@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;
as well as URLs for NNTP newsgroup(s).