public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Ingo Molnar <mingo@elte.hu>
Cc: martin@dalecki.de, "Adam J. Richter" <adam@yggdrasil.com>,
	<alan@lxorguk.ukuu.org.uk>, <Andries.Brouwer@cwi.nl>,
	<johninsd@san.rr.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [bug, 2.5.29, IDE] partition table corruption?
Date: Thu, 8 Aug 2002 13:45:40 +0200	[thread overview]
Message-ID: <20020808114540.GA633@win.tue.nl> (raw)
In-Reply-To: <Pine.LNX.4.44.0208081139350.3618-100000@localhost.localdomain>

On Thu, Aug 08, 2002 at 12:01:27PM +0200, Ingo Molnar wrote:

> just tested 2.5.29-vanilla, it works, without and with linear.
> 2.5.30-vanilla is broken without linear, works with linear.

Excellent, precisely as expected.


[Yes, I don't know why an entire thread blossomed up around
something very well understood. Many wrong statements were
made, but I am too lazy to go and refute them all.

Concerning what happened: Long ago, the kernel did some more or
less silly things to get a geometry - for example, asking the
BIOS and the disk; but that did not produce the desired results
and someone added (in 1.3.61) some code to override the geometry
found this way by something guessed from the partition table,
in the good old tradition: is there a bug in a user space program?
fix it in the kernel. That is the [PTBL] you see in kernel boot
messages. Now that this kernel fix has been removed in a small
cleanup operation, lilo will have to be fixed, or people will
have to invoke lilo with linear, or so.

The full truth is more complicated, but this is the full
truth in your case.]

Andries

  reply	other threads:[~2002-08-08 11:42 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-08  9:08 [bug, 2.5.29, IDE] partition table corruption? Adam J. Richter
2002-08-08  9:24 ` Marcin Dalecki
2002-08-08  9:31   ` Ingo Molnar
2002-08-08  9:34     ` Marcin Dalecki
2002-08-08 10:01       ` Ingo Molnar
2002-08-08 11:45         ` Andries Brouwer [this message]
2002-08-08 12:30       ` Alan Cox
2002-08-08 11:22         ` Marcin Dalecki
2002-08-08 13:23           ` Alan Cox
2002-08-08 12:18             ` Marcin Dalecki
2002-08-08 18:11               ` Alan Cox
2002-08-09  0:11                 ` Thunder from the hill
2002-08-09  6:27                   ` Marcin Dalecki
     [not found]     ` <3D523B25.5 <20020808181100Z315277-685+26763@vger.kernel.org>
2002-08-09  6:25       ` Marcin Dalecki
  -- strict thread matches above, loose matches on Subject: below --
2002-08-08 18:22 Andries.Brouwer
2002-08-08 22:36 ` John Coffman
2002-08-09  6:06   ` H. Peter Anvin
2002-08-08 12:29 Andries.Brouwer
2002-08-07 18:43 Andries.Brouwer
2002-08-08  7:46 ` Marcin Dalecki
2002-08-06 22:27 Andries.Brouwer
2002-08-07 17:46 ` Ingo Molnar
2002-08-07 17:51   ` Ingo Molnar
2002-08-01 13:45 Ingo Molnar
2002-08-01 13:48 ` Marcin Dalecki
2002-08-01 16:16   ` Alan Cox
2002-08-01 15:02     ` Marcin Dalecki
2002-08-01 15:12 ` Alan Cox

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=20020808114540.GA633@win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=Andries.Brouwer@cwi.nl \
    --cc=adam@yggdrasil.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=johninsd@san.rr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin@dalecki.de \
    --cc=mingo@elte.hu \
    /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