From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 204119] scsi_mod: Could not allocate 4104 bytes percpu data
Date: Sat, 10 Aug 2019 11:55:13 +0000 [thread overview]
Message-ID: <bug-204119-11613-ubUJrEBZtK@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204119-11613@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204119
Yill Din (justincase@yopmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |justincase@yopmail.com
--- Comment #9 from Yill Din (justincase@yopmail.com) ---
When find the patch the way into the 5.2 Kernel?
I got the same bug. I can't use any usb device. Nothing happens. But I'm not
able to build my own kernel. I tried all Kernel-Versions of 5.2 (5.2.1 - 5.2.7
(arch Linux)).
--
You are receiving this mail because:
You are the assignee for the bug.
next parent reply other threads:[~2019-08-10 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-204119-11613@https.bugzilla.kernel.org/>
2019-08-10 11:55 ` bugzilla-daemon [this message]
2019-08-14 21:04 ` [Bug 204119] scsi_mod: Could not allocate 4104 bytes percpu data bugzilla-daemon
2019-08-23 10:33 ` 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-204119-11613-ubUJrEBZtK@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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).