From: Larry Stefani <lstefani@yahoo.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: linux-mips@linux-mips.org
Subject: Re: SB1250 locking up in init on current 2.6.16 kernel
Date: Tue, 25 Mar 2008 06:05:35 -0700 (PDT) [thread overview]
Message-ID: <64859.43533.qm@web38815.mail.mud.yahoo.com> (raw)
In-Reply-To: <20080324203311.GB15294@linux-mips.org>
Hello Ralf,
Thank you very much for the quick response. I know
you must be terribly busy with the server move, so I
won't take up too much more of your time.
I did find an old (possibly related) discussion you
were involved in:
http://www.linux-mips.org/archives/linux-mips/2006-09/msg00194.html
I can't tell from the thread whether it was a problem
seen on 2.6.16.29, but that might have been tip at the
time.
> It's a bug which should be fixed but nevertheless I
> can highly recommend
> something like a SiliconImage SATA controller - the
> onboard PIO PATA
> controller is so slow.
I understand, but changing that is not an option for
me today.
> I've pushed the tag again so now there is a tarball.
Thanks. I thought something was terribly wrong with
.28 for it to be skipped.
> If you need to track something like this you're
> probably best with
> git bisect which should bring you right to the
> offending commit.
I probably should have used that approach instead of
diffing .27 and .29 and narrowing the file list by
hand. As it was, there were changes to non-MIPS
platforms and devices I'm not using so those were easy
to apply to .27. Also, there were many file changes
for MT SMP support, and *most* (but not all) of those
changes were wrapped with conditional compiles, so
those were also easy to apply. I knew once I got to
these five files I was in some interesting code that
could point to the problems I'm seeing.
> Later kernels do run on bcm1480 which is close
> enough.
By "later kernels", do you mean 2.6.16.60 or different
kernel branches?
Perhaps, but I'm seeing identical failures in .29 and
.60, although that could be misleading. I do see
significant SMP-related changes in c-sb1.c between .29
and .60, and I am running in SMP. I wish there was an
easy way to know whether it's in the same code.
Anyway, in the interest of time I may revert to .27
which appears to work. I don't need any of the MT SMP
related changes that followed, and perhaps I can live
without the enhancements between .27 and .60 for now.
Thanks,
Larry Stefani
lstefani@yahoo.com
____________________________________________________________________________________
Never miss a thing. Make Yahoo your home page.
http://www.yahoo.com/r/hs
next prev parent reply other threads:[~2008-03-26 12:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 14:00 SB1250 locking up in init on current 2.6.16 kernel Larry Stefani
2008-03-24 20:33 ` Ralf Baechle
2008-03-25 13:05 ` Larry Stefani [this message]
2008-03-26 20:52 ` Larry Stefani
2008-03-28 13:43 ` Thiemo Seufer
2008-03-28 16:38 ` Larry Stefani
2008-03-28 17:11 ` Thiemo Seufer
2008-03-31 2:02 ` Larry Stefani
2008-03-25 15:37 ` Thiemo Seufer
2008-03-25 17:12 ` Thiemo Seufer
2008-03-25 17:12 ` Thiemo Seufer
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=64859.43533.qm@web38815.mail.mud.yahoo.com \
--to=lstefani@yahoo.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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