From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Omkhar Arasaratnam <iamroot@ca.ibm.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
tgall@us.ibm.com, antonb@au1.ibm.com,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: [BUG] 2.6.11- sym53c8xx Broken on pp64
Date: Thu, 10 Mar 2005 13:10:20 +1100 [thread overview]
Message-ID: <1110420620.32525.145.camel@gaston> (raw)
In-Reply-To: <422FA817.4060400@ca.ibm.com>
On Wed, 2005-03-09 at 19:51 -0600, Omkhar Arasaratnam wrote:
> Seems with 2.6.11 the sym53c8xx kernel module incorrectly identifies the
> cache being misconfigured on a p630 (ppc64, POWER4+). 2.6.9 correctly
> brings up this adaptor as does AIX with absolutely no indication of a
> misconfigured cache.
>
> Doing a simple diff I see ALOT of changes between 2.6.9 and 2.6.11
> pertaining to this module. Any ideas?
Are you sure it's plain 2.6.11 and not some bk clone of after 2.6.11 was
released ?
I just found a bug in the ppc64 ioremap code that got triggered by
the set_pte_at() patch that went into bk after 2.6.11 and that triggers
exactly that error, but I couldn't see anything wrong in 2.6.11 proper.
BTW, Linus: Any chance you ever change something to version or
extraversion in bk just after a release ? I know I already ask and it
degenerated into a flamefest, and I don't know if that is specifically
the case now, but I keep getting report of people saying "I have a bug
in 2.6.xx" while in fact, they have some kind of bk clone of sometime
after 2.6.xx...
Ben.
next prev parent reply other threads:[~2005-03-10 2:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 1:51 [BUG] 2.6.11- sym53c8xx Broken on pp64 Omkhar Arasaratnam
2005-03-10 2:10 ` Benjamin Herrenschmidt [this message]
2005-03-10 2:25 ` Linus Torvalds
2005-03-10 5:06 ` Ryan Anderson
2005-03-10 5:40 ` Sam Ravnborg
2005-03-13 4:32 ` [PATCH] Auto-append localversion for BK users needs to use CONFIG_SHELL Ryan Anderson
2005-04-03 19:17 ` Sam Ravnborg
2005-03-10 3:11 ` [BUG] 2.6.11- sym53c8xx Broken on pp64 Omkhar Arasaratnam
2005-03-10 3:34 ` Omkhar Arasaratnam
2005-03-10 3:47 ` Linus Torvalds
2005-03-10 4:53 ` Omkhar Arasaratnam
2005-03-10 5:59 ` Benjamin Herrenschmidt
2005-03-10 12:17 ` Matthew Wilcox
2005-03-10 15:17 ` James Bottomley
2005-03-10 17:05 ` Omkhar Arasaratnam
2005-03-10 22:02 ` Benjamin Herrenschmidt
2005-03-11 14:54 ` Omkhar Arasaratnam
2005-03-13 20:32 ` Omkhar Arasaratnam
2005-03-15 15:54 ` Omkhar Arasaratnam
2005-03-15 23:38 ` 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=1110420620.32525.145.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=antonb@au1.ibm.com \
--cc=iamroot@ca.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tgall@us.ibm.com \
--cc=torvalds@osdl.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