From: Jaroslaw Fedewicz <jafd-cTM//Nd5/DKCo84Yma55WQ@public.gmane.org> To: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org Cc: linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org Subject: [Bug?] Machine hangs, rtl8192se possible cause Date: Mon, 1 Aug 2011 16:26:49 +0300 [thread overview] Message-ID: <CAFdoEiT54o+NQKO=dAcOXgyf6GJ1E51w_H_p7PJyRmynz8Sbzg@mail.gmail.com> (raw) Hello, I own a Thinkpad Edge 13 (AMD, machine type 0197) laptop, which is shipped with a Realtek 8192 SE WLAN card. The WLAN support with this particular card was never brilliant under Linux, first with (very) flakey drivers from Realtek which would stop transmitting packets every so often or panic after a few hours of usage. The in-tree drivers are better in this respect, but I'm experiencing mysterious hangups every once in a while. The machine is effectively dead and has to be power-cycled — no oops, no kernel panic, no nothing, it just hangs and that's it. I'm sure this is not a regression because the hangups were right there from the start. The last meaningful message which might be helpful was: "wait for BIT(6) return value X" (I don't remember what X was, it was a while ago and only once). I don't know if there are other means to debug (netconsole over eth0?) those hangs. The only other thing I know for sure that I can get a week long uptime if I blacklist rtl8192se.ko from loading. If I can provide any additional information to track the bug (or a faulty piece of hardware?) down, please tell me. Google tells me nobody reported this before, or it was just me feeding incorrect keywords. Thanks for your kind attention. P. S. Tried netconsole before, got nothing to pinpoint the error. The only recurring pattern I could see in it was that almost every time the machine hanged was after ip6tables initialized, at least it was the last message in the log. P. P. S. I don't track netdev@ and linux-wireless@ lists, so please Cc: me. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Jaroslaw Fedewicz <jafd@netstyle.com.ua> To: linux-kernel@vger.kernel.org Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org, Larry.Finger@lwfinger.net Subject: [Bug?] Machine hangs, rtl8192se possible cause Date: Mon, 1 Aug 2011 16:26:49 +0300 [thread overview] Message-ID: <CAFdoEiT54o+NQKO=dAcOXgyf6GJ1E51w_H_p7PJyRmynz8Sbzg@mail.gmail.com> (raw) Hello, I own a Thinkpad Edge 13 (AMD, machine type 0197) laptop, which is shipped with a Realtek 8192 SE WLAN card. The WLAN support with this particular card was never brilliant under Linux, first with (very) flakey drivers from Realtek which would stop transmitting packets every so often or panic after a few hours of usage. The in-tree drivers are better in this respect, but I'm experiencing mysterious hangups every once in a while. The machine is effectively dead and has to be power-cycled — no oops, no kernel panic, no nothing, it just hangs and that's it. I'm sure this is not a regression because the hangups were right there from the start. The last meaningful message which might be helpful was: "wait for BIT(6) return value X" (I don't remember what X was, it was a while ago and only once). I don't know if there are other means to debug (netconsole over eth0?) those hangs. The only other thing I know for sure that I can get a week long uptime if I blacklist rtl8192se.ko from loading. If I can provide any additional information to track the bug (or a faulty piece of hardware?) down, please tell me. Google tells me nobody reported this before, or it was just me feeding incorrect keywords. Thanks for your kind attention. P. S. Tried netconsole before, got nothing to pinpoint the error. The only recurring pattern I could see in it was that almost every time the machine hanged was after ip6tables initialized, at least it was the last message in the log. P. P. S. I don't track netdev@ and linux-wireless@ lists, so please Cc: me.
next reply other threads:[~2011-08-01 13:26 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-01 13:26 Jaroslaw Fedewicz [this message] 2011-08-01 13:26 ` [Bug?] Machine hangs, rtl8192se possible cause Jaroslaw Fedewicz [not found] ` <CAFdoEiT54o+NQKO=dAcOXgyf6GJ1E51w_H_p7PJyRmynz8Sbzg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2011-08-01 15:30 ` Larry Finger 2011-08-01 15:30 ` Larry Finger [not found] ` <4E36C693.6000705-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org> 2011-08-01 23:10 ` Jaroslaw Fedewicz 2011-08-01 23:10 ` Jaroslaw Fedewicz [not found] ` <CAFdoEiRBPMx0C+YXwd4-Q=_nHpOb+r2+GspwujZrPh6S4tDwEQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org> 2011-08-02 3:45 ` Larry Finger 2011-08-02 3:45 ` Larry Finger 2011-09-22 16:06 ` Edwin 2011-09-22 16:38 ` Larry Finger 2011-12-05 18:20 Ewan Higgs 2011-12-05 18:42 ` Borislav Petkov
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='CAFdoEiT54o+NQKO=dAcOXgyf6GJ1E51w_H_p7PJyRmynz8Sbzg@mail.gmail.com' \ --to=jafd-ctm//nd5/dkco84yma55wq@public.gmane.org \ --cc=Larry.Finger-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org \ --cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \ --cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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: linkBe 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.