From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linuxppc-dev@lists.ozlabs.org, Paul Mackerras <paulus@samba.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Regression in 32-bit ppc kernel
Date: Thu, 26 Apr 2012 07:44:17 +1000 [thread overview]
Message-ID: <1335390257.21961.53.camel@pasglop> (raw)
In-Reply-To: <4F98117C.7080309@lwfinger.net>
On Wed, 2012-04-25 at 10:00 -0500, Larry Finger wrote:
>
> After a few tries, I managed to change over to pata_macio.
> Fortunately, most of
> the system used dev-by-id or UUID, thus most of the process was
> getting all the
> kernel pieces built in.
>
> Unfortunately, the original problem remains. I have resumed the
> bisecting - only
> 11 steps to go. I should have it by Friday! :)
>
Thanks !
Do we know what the bad interrupt maps to ? Also what is the value of
NR_IRQ and do you have SPARSE_IRQ enabled ? Can you try with the latter
disabled and NR_IRQ set to something large, such as 128 ?
(You may be able to check the interrupt mapping in debugfs)
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: Regression in 32-bit ppc kernel
Date: Thu, 26 Apr 2012 07:44:17 +1000 [thread overview]
Message-ID: <1335390257.21961.53.camel@pasglop> (raw)
In-Reply-To: <4F98117C.7080309@lwfinger.net>
On Wed, 2012-04-25 at 10:00 -0500, Larry Finger wrote:
>
> After a few tries, I managed to change over to pata_macio.
> Fortunately, most of
> the system used dev-by-id or UUID, thus most of the process was
> getting all the
> kernel pieces built in.
>
> Unfortunately, the original problem remains. I have resumed the
> bisecting - only
> 11 steps to go. I should have it by Friday! :)
>
Thanks !
Do we know what the bad interrupt maps to ? Also what is the value of
NR_IRQ and do you have SPARSE_IRQ enabled ? Can you try with the latter
disabled and NR_IRQ set to something large, such as 128 ?
(You may be able to check the interrupt mapping in debugfs)
Cheers,
Ben.
next prev parent reply other threads:[~2012-04-25 21:44 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 22:58 Regression in 32-bit ppc kernel Larry Finger
2012-04-24 23:53 ` Benjamin Herrenschmidt
2012-04-24 23:53 ` Benjamin Herrenschmidt
2012-04-25 2:37 ` Larry Finger
2012-04-25 2:37 ` Larry Finger
2012-04-25 4:11 ` Benjamin Herrenschmidt
2012-04-25 4:11 ` Benjamin Herrenschmidt
2012-04-25 15:00 ` Larry Finger
2012-04-25 15:00 ` Larry Finger
2012-04-25 21:44 ` Benjamin Herrenschmidt [this message]
2012-04-25 21:44 ` Benjamin Herrenschmidt
2012-04-27 15:38 ` Larry Finger
2012-04-27 15:38 ` Larry Finger
2012-04-27 22:26 ` Benjamin Herrenschmidt
2012-04-27 22:26 ` Benjamin Herrenschmidt
2012-04-28 0:02 ` Larry Finger
2012-04-28 0:02 ` Larry Finger
2012-04-28 0:42 ` Benjamin Herrenschmidt
2012-04-28 0:42 ` Benjamin Herrenschmidt
2012-04-28 18:09 ` Larry Finger
2012-04-28 18:09 ` Larry Finger
2012-04-28 18:23 ` Andreas Schwab
2012-04-28 18:23 ` Andreas Schwab
2012-04-28 22:48 ` Benjamin Herrenschmidt
2012-04-28 22:48 ` Benjamin Herrenschmidt
2012-04-28 23:17 ` Larry Finger
2012-04-28 23:17 ` Larry Finger
2012-04-28 23:23 ` Benjamin Herrenschmidt
2012-04-28 23:23 ` Benjamin Herrenschmidt
2012-04-28 23:30 ` Larry Finger
2012-04-28 23:30 ` Larry Finger
2012-04-28 22:41 ` Benjamin Herrenschmidt
2012-04-28 22:41 ` Benjamin Herrenschmidt
2012-04-28 22:42 ` Benjamin Herrenschmidt
2012-04-28 22:42 ` Benjamin Herrenschmidt
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=1335390257.21961.53.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.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 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.