From: Michael Straube <straube.linux@gmail.com>
To: gregkh@linuxfoundation.org
Cc: Larry.Finger@lwfinger.net, phil@philpotter.co.uk,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
Michael Straube <straube.linux@gmail.com>
Subject: [BUG] staging: r8188eu: driver stopped working with commit ("staging: r8188eu: add check for kzalloc")
Date: Wed, 8 Jun 2022 08:50:05 +0200 [thread overview]
Message-ID: <ded4b3f5-a9bc-4612-33cc-68bd85cb92fe@gmail.com> (raw)
In-Reply-To: <20220606064055.12565-1-straube.linux@gmail.com>
Hi all,
The driver does not work anymore on my system. In dmesg there is:
"r8188eu 1-4:1.0: _rtw_init_xmit_priv failed"
I bisected it to commit f94b47c6bde ("staging: r8188eu: add check for
kzalloc").
~/kernels/staging> git bisect bad
f94b47c6bde624d6c07f43054087607c52054a95 is the first bad commit
At the moment I have no time to look further into it.
regards,
Michael
dmesg after plugging in the device:
[15075.514705] usb 1-4: new high-speed USB device number 4 using xhci_hcd
[15075.750717] usb 1-4: New USB device found, idVendor=0bda,
idProduct=8179, bcdDevice= 0.00
[15075.750729] usb 1-4: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
[15075.750734] usb 1-4: Product: 802.11n NIC
[15075.750738] usb 1-4: Manufacturer: Realtek
[15075.750742] usb 1-4: SerialNumber: 200DB02CEF8F
[15075.767685] Chip Version Info:
CHIP_8188E_Normal_Chip_TSMC_D_CUT_1T1R_RomVer(0)
[15076.121994] EEPROM ID = 0x8129
[15076.123218] r8188eu 1-4:1.0: _rtw_init_xmit_priv failed
[15076.321389] usb 1-4: reset high-speed USB device number 4 using xhci_hcd
next prev parent reply other threads:[~2022-06-08 7:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 6:40 [PATCH] staging: r8188eu: remove HW_VAR_SLOT_TIME from SetHwReg8188EU() Michael Straube
2022-06-08 6:50 ` Michael Straube [this message]
2022-06-08 9:27 ` [BUG] staging: r8188eu: driver stopped working with commit ("staging: r8188eu: add check for kzalloc") Martin Kaiser
2022-06-08 9:34 ` Pavel Skripkin
2022-06-08 10:45 ` Greg KH
2022-06-08 12:21 ` Michael Straube
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=ded4b3f5-a9bc-4612-33cc-68bd85cb92fe@gmail.com \
--to=straube.linux@gmail.com \
--cc=Larry.Finger@lwfinger.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=phil@philpotter.co.uk \
/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