linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>,
	Carsten Emde <C.Emde@osadl.org>
Cc: linux-rt-users <linux-rt-users@vger.kernel.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: 3.10.20-rt17, BUG and Oops
Date: Sat, 30 Nov 2013 21:39:20 +0100	[thread overview]
Message-ID: <20131130203920.GB24080@linutronix.de> (raw)
In-Reply-To: <529A1511.5050801@osadl.org>

* Carsten Emde | 2013-11-30 17:40:49 [+0100]:

># addr2line -e vmlinux 0xffffffff81298301
>/usr/src/kernels/linux-3.12.0-rt2/drivers/acpi/ec.c:186
>
>        if (t->wlen > t->wi) {
>                if ((status & ACPI_EC_FLAG_IBF) == 0)
>                        acpi_ec_write_data(ec,
>---->                           t->wdata[t->wi++]);
>                else
>                        goto err;

based on the assembly, I *think* this is 
 t->wdata[x]

wher X is outside of wdata's range. But then  the pointer is almost
NULL. Could one of you check with the acpi folks if they know some
tricks how to debug this ACPI thingy?

Is this any help?

diff --git a/drivers/acpi/ec.c b/drivers/acpi/ec.c
index a06d983..d3add07 100644
--- a/drivers/acpi/ec.c
+++ b/drivers/acpi/ec.c
@@ -175,16 +175,19 @@ static void start_transaction(struct acpi_ec *ec)
 static void advance_transaction(struct acpi_ec *ec, u8 status)
 {
 	unsigned long flags;
-	struct transaction *t = ec->curr;
+	struct transaction *t;
 
 	spin_lock_irqsave(&ec->lock, flags);
+	t = ec->curr;
 	if (!t)
 		goto unlock;
 	if (t->wlen > t->wi) {
-		if ((status & ACPI_EC_FLAG_IBF) == 0)
+		if ((status & ACPI_EC_FLAG_IBF) == 0) {
+			if (WARN_ON_ONCE(!t->wdata))
+				goto err;
 			acpi_ec_write_data(ec,
 				t->wdata[t->wi++]);
-		else
+		} else
 			goto err;
 	} else if (t->rlen > t->ri) {
 		if ((status & ACPI_EC_FLAG_OBF) == 1) {

Sebastian

  reply	other threads:[~2013-11-30 20:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-30  7:56 3.10.20-rt17, BUG and Oops Fernando Lopez-Lezcano
2013-11-30 16:40 ` Carsten Emde
2013-11-30 20:39   ` Sebastian Andrzej Siewior [this message]
2013-11-30 22:47     ` Carsten Emde
2013-12-02  8:27       ` Sebastian Andrzej Siewior
2013-12-15 14:53       ` Sebastian Andrzej Siewior
2013-12-15 23:50         ` Carsten Emde
2013-12-16  8:09           ` Sebastian Andrzej Siewior
2013-12-21 21:23             ` Carsten Emde
2013-12-17 19:40         ` Fernando Lopez-Lezcano
2013-12-17 19:42           ` Sebastian Andrzej Siewior

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=20131130203920.GB24080@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=C.Emde@osadl.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=nando@ccrma.Stanford.EDU \
    --cc=rostedt@goodmis.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).