public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Mike Galbraith <efault@gmx.de>
Cc: Thomas Molina <tmolina@cox.net>, linux-kernel@vger.kernel.org
Subject: Re: loadlin with 2.5.?? kernels
Date: 24 Oct 2002 02:07:32 -0600	[thread overview]
Message-ID: <m18z0os1iz.fsf@frodo.biederman.org> (raw)
In-Reply-To: <5.1.0.14.2.20021021192410.00b4ffb8@pop.gmx.net>

Mike Galbraith <efault@gmx.de> writes:

> At 01:58 PM 10/20/2002 -0500, Thomas Molina wrote:
> >On Sun, 20 Oct 2002, Mike Galbraith wrote:
> >
> > > At 08:17 AM 10/20/2002 -0500, Thomas Molina wrote:
> > > >On Sun, 20 Oct 2002, Mike Galbraith wrote:
> > > >
> > > > > Greetings,
> > > > >
> > > > > I hadn't had time to build/test kernels since 2.5.8-pre3.  I now find
> > that
> > > > > loadlin doesn't work on my box any more.  Is this a known problem?  If
> > so,
> > > > > when did it quit working?  (loadlin obsolete?  other?)
> > > >
> > > >I'm carrying an open problem report from Rene Blokland on this issue.
> > > >What version of the kernel did you try?
> > >
> > > Only 2.5.42.virgin, 2.5.42-mm, 2.5.43-mm and 2.5.44.virgin.  Binary search
> > > pending.
> >
> >The report stated the problem was noted with 2.5.4x.  One of the
> >developers might want to speak up as to whether finding the exact point of
> >breakage is useful.
> 
> 2.5.32 is the breakage point here.  I hope someone _else_ can salvage loadlin :)
> 
> 
> (lions and tigers and bears - oh my GDT!)

Cool, thanks, for the confirmation.  Other people are seeing breaking a little
later.  Just to clarify.  .30 or .31 is the last version that worked and .32
does not?

If it is really the gdt I have some old patches that roughly do the
right thing, and I just need to dust them off.

Eric

  reply	other threads:[~2002-10-24  8:03 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-20 12:51 loadlin with 2.5.?? kernels Mike Galbraith
2002-10-20 13:17 ` Thomas Molina
2002-10-20 17:34   ` Mike Galbraith
2002-10-20 18:58     ` Thomas Molina
2002-10-21 11:28       ` Denis Vlasenko
2002-10-21 17:36       ` Mike Galbraith
2002-10-24  8:07         ` Eric W. Biederman [this message]
2002-10-24  8:26           ` Mike Galbraith
2002-10-25 12:21             ` Eric W. Biederman
2002-10-25 13:30               ` Mike Galbraith
2002-10-25 22:00               ` robert w hall
2002-10-26  4:56                 ` Eric W. Biederman
2002-10-26  5:02                 ` Mike Galbraith
2002-10-26  5:20                   ` Eric W. Biederman
2002-10-26  5:49                     ` Mike Galbraith
2002-10-26  6:32                       ` Rene Blokland
2002-10-26  7:34                         ` Mike Galbraith
2002-10-26  9:24                       ` Eric W. Biederman
2002-10-26 10:37                         ` robert w hall
2002-10-30  1:29                           ` Eric W. Biederman
2002-10-31 21:24                             ` robert w hall
2002-10-26  8:22                     ` robert w hall
     [not found] <1a9.a96af34.2ae43a18@aol.com>
2002-10-20 17:40 ` Mike Galbraith
     [not found] <002f01c27c2a$d4c758a0$6400a8c0@mikeg>
2002-10-25 18:42 ` Mike Galbraith

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=m18z0os1iz.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=efault@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tmolina@cox.net \
    /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