From: Jean Delvare <jdelvare@suse.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Chaoming Li <chaoming_li@realsil.com.cn>, linux-wireless@vger.kernel.org
Subject: Re: rtl8192ce:rtl92ce_get_hw_reg():<0-0> switch case not processed
Date: Thu, 22 Sep 2016 19:05:40 +0200 [thread overview]
Message-ID: <20160922190540.08bf6335@endymion> (raw)
In-Reply-To: <83974845-037d-0cde-00b1-ec7b28eeb15f@lwfinger.net>
On Thu, 22 Sep 2016 10:09:58 -0500, Larry Finger wrote:
> On 09/22/2016 04:51 AM, Jean Delvare wrote:
> > Hello,
> >
> > I bought an Asus PCE-N10 PCIe Wi-Fi N card to install in my wife's
> > computer. This morning it stopped working suddenly. Investigating the
> > kernel logs, the following error message caught my eye:
> >
> > rtl8192ce:rtl92ce_get_hw_reg():<0-0> switch case not processed
> >
> > It was printed twice, 3.5 hours apart, the second time at the moment
> > the network stopped working. I guess this is not supposed to happen.
> > What additional information can I provide to help you debug the issue?
> > That's the device:
> >
> > 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter [10ec:8176] (rev 01)
> > Subsystem: ASUSTeK Computer Inc. Device [1043:84b5]
> > Flags: bus master, fast devsel, latency 0, IRQ 17
> > I/O ports at e800 [size=256]
> > Memory at febfc000 (64-bit, non-prefetchable) [size=16K]
> > Capabilities: <access denied>
> > Kernel driver in use: rtl8192ce
> > Kernel modules: rtl8192ce
> >
> > Kernel version is 4.5.4-1-default x86_64 (openSUSE Tumbleweed.)
> >
> > Reloading the rtl8192ce module and restarting the network service got
> > everything back up.
>
> Unfortunately, that message is not as helpful as it might be.
>
> Do you build your own kernel, or are you using openSUSE's supplied version? If
> the latter, I will need to think how we might debug the issue. If the former,
> please add the attached patch.
I'm a kernel dev :-) I'll test your patch and report, thanks.
That being said, I agree it's better if drivers have useful debug
messages... Makes things faster. So something like your patch should go
upstream anyway. And the same improvement could be applied to various
other messages of the rtlwifi driver family.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2016-09-22 17:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-22 9:51 rtl8192ce:rtl92ce_get_hw_reg():<0-0> switch case not processed Jean Delvare
2016-09-22 15:09 ` Larry Finger
2016-09-22 17:05 ` Jean Delvare [this message]
2016-09-22 21:01 ` Jean Delvare
2016-09-23 12:16 ` Jean Delvare
2016-09-23 18:10 ` Larry Finger
2016-09-24 15:25 ` Jean Delvare
2016-09-23 18:12 ` Joe Perches
2016-09-23 18:27 ` [PATCH] realtek: Add switch variable to 'switch case not processed' messages Joe Perches
2016-09-23 18:59 ` Larry Finger
2016-09-23 19:02 ` Joe Perches
2016-09-24 15:55 ` Jean Delvare
2016-09-24 16:15 ` Joe Perches
2016-09-24 16:35 ` Larry Finger
2016-09-24 17:32 ` Joe Perches
2016-09-24 19:06 ` Larry Finger
2016-09-24 20:02 ` Jes Sorensen
2016-09-24 20:29 ` Joe Perches
2016-09-24 20:35 ` Jes Sorensen
2016-09-26 9:33 ` David Laight
2016-09-23 19:07 ` Larry Finger
2016-09-27 15:45 ` rtlwifi: " Kalle Valo
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=20160922190540.08bf6335@endymion \
--to=jdelvare@suse.de \
--cc=Larry.Finger@lwfinger.net \
--cc=chaoming_li@realsil.com.cn \
--cc=linux-wireless@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).