From: Jason Gauthier <jgauthier@lastar.com>
To: Zwane Mwaikambo <zwane@fsmlabs.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: RE: 2.6.7 SMP trouble?
Date: Mon, 2 Aug 2004 09:14:47 -0400 [thread overview]
Message-ID: <2873B794CB1BE04F80E2968B438680E503C8C991@server6.ctg.com> (raw)
Sorry for the delay in reponse to this thread. I've been testing this out,
and it takes awhile.
Well, sadly, I was *wrong*. After a couple days my 2.4.26 kernel completely
died on me too.
So, I back tracked to 2.4.22, which I had previously thought stable. But
no, it also died.
So, I started at the beginning.
Here are my results:
2.4.0-2.4.9: Do not compile.
2.4.10-2.4.15: 'Oops' on boot.
2.4.16-2.4.17: skipped
2.4.18: Same SMP symptoms.
So, I could try 16/17, but I don't think it matter much at this point.
What should my next step be?
Thanks for all the help so far.
Jason
> -----Original Message-----
> From: Zwane Mwaikambo [mailto:zwane@fsmlabs.com]
> Sent: Tuesday, July 20, 2004 10:35 AM
> To: Jason Gauthier
> Cc: Linux Kernel
> Subject: RE: 2.6.7 SMP trouble?
>
> On Tue, 20 Jul 2004, Jason Gauthier wrote:
>
> > > It would actually help if you found the exact version
> which stopped
> > > working, then we can get it looked at and fixed.
> > >
> >
> > If it's in the middle of 2.5 development somewhere that
> could take me
> > months
> > :)
> > Assuming 1 day to download compile and start the tests,
> it's about a
> > day per kernel.
>
> Try the following kernels;
>
> 2.6.0
> 2.5.65
> 2.5.60
>
> Basically just make large strides, due to the lack of other
> data this may be the only way.
>
next reply other threads:[~2004-08-02 13:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 13:14 Jason Gauthier [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-20 14:21 Jason Gauthier
2004-07-20 14:34 ` Zwane Mwaikambo
2004-07-19 19:16 Jason Gauthier
2004-07-19 20:04 ` Richard B. Johnson
2004-07-20 14:22 ` Zwane Mwaikambo
2004-07-20 19:57 ` Bill Davidsen
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=2873B794CB1BE04F80E2968B438680E503C8C991@server6.ctg.com \
--to=jgauthier@lastar.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@fsmlabs.com \
/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
Powered by JetHome