linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "S. Gilles" <sgilles@terpmail.umd.edu>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: "S. Gilles" <sgilles@terpmail.umd.edu>,
	Chaoming Li <chaoming_li@realsil.com.cn>,
	linux-wireless@vger.kernel.org
Subject: Re: PROBLEM: Boot failure with bad RIP value
Date: Fri, 31 Oct 2014 23:41:18 -0400	[thread overview]
Message-ID: <20141101034118.GA20771@number18> (raw)
In-Reply-To: <5453A5CF.90107@lwfinger.net>

On Fri, Oct 31, 2014 at 10:07:59AM -0500, Larry Finger wrote:
> On 10/31/2014 08:56 AM, S. Gilles wrote:
> >> 03:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8188CE 802.11b/g/n WiFi Adapter [10ec:8176] (rev 01)
> >
> > Any progress on this, or duplication?  If this isn't replicable with
> > the information in Bugzilla, I can provide anything requested.
> 
> Thanks for posting the PCI ID. I am currently on a family vacation, and I have 
> had little time for driver problems, and none for chasing missing information.

My apologies, I didn't realize you were still away.

> The attached patches should fix the kernel crashes; however, I doubt that the 
> driver will work. There seems to be a problem with DMA buffers that I have not 
> had time to find.

For the sake of followp, I can confirm on my machine: the boot is fine
but no /dev/wlan0. Thanks for the patches, I'll remain available to
test any more if needed.

-- 
S. Gilles

      reply	other threads:[~2014-11-01  3:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-13 23:45 PROBLEM: Boot failure with bad RIP value S. Gilles
2014-10-14  3:41 ` Larry Finger
2014-10-14  4:13   ` S. Gilles
2014-10-21 22:35     ` S. Gilles
2014-10-31 13:56     ` S. Gilles
2014-10-31 15:07       ` Larry Finger
2014-11-01  3:41         ` S. Gilles [this message]

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=20141101034118.GA20771@number18 \
    --to=sgilles@terpmail.umd.edu \
    --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).