[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#345067: My understanding of the IDE mess, and why it does not make sense to apply the proposed patch

On Fri, 10 Mar 2006 17:07:34 +0100
Frans Pop <aragorn@tiscali.nl> wrote:

> On Friday 10 March 2006 15:29, Jonas Smedegaard wrote:
> > If modular-ide is the sole source of trouble here, then what worked
> > in 2.6.14-4 and earlier?
> <=2.6.12 used initrd-tools and that must still contain the correct
> magic to deal with this.
> 2.6.14 was the first kernel tested with yaird and initramfs-tools. 
> Probably -4 was the first to get wide exposure and thus no-one really 
> noticed the issue before then?

If upgrading from 2.6.14-4 to 2.6.14-5 I suspect the user was indeed
able to boot a 2.6.14 kernel. Theoretically all those users could of
course have been running 2.6.12 and only rebooting after several kernel
upgrades, but why would then none of them mention that?

I am referring to the bug reports collected at the wiki page. Here's an

Paulo Marcel Coelho Aragao <marcelpaulo@yahoo.com> in bug#343042:
> Right after I upgraded linux-image-2.6.14-2-686 to 2.6.14-5 and
> rebooted, boot is interrupted with repeated messages:
> /bin/cat: /sys/block/hda/hda1/dev: No such file or directory
> until it finally stops completely, with message:
> Device /sys/block/hda/hda1/dev seems to be down
> I'm having to reboot with 2.6.12.

Note the first line of the bugreport. The need to reboot with 2.6.12 is
because of the upgrade being irreversible (due to a bug in yaird
0.0.11 making it sometimes not fail on error).

The irreversability is actually a fine example of a good use of
superstrict yaird:

If in the above case the current yaird had been used instead, then the
user would not have to roll back to 2.6.12 (or boot from alternative
media if not so conveniently having a backup kernel installed and
still working). Instead, yaird would have failed and refused to report
the install as succesful, causing dpkg to roll back to 2.6.14-4!

Put to extremes, it could even be considered a RC bug for kernel
packages to use unreliable ramdisk generators like initramfs-tools (and
yaird with the discussed patch applied, which causes it to behave
like above for powerpc).

But all that was for the sake of explaining the reasoning behind
stricnes of yaird. I agree that the specific kernel bug is being hunted
down now, so no need to mention that the above is close to theoretical.

Nut my point of modular-ide not seeming to be the whole issue (if not
in reality dropped earlier than documented) persist.

 - Jonas


Was your dropping the bugreport from recipients intentional?

* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 - Enden er nær: http://www.shibumi.org/eoti.htm

Attachment: pgp7CGV9WB26c.pgp
Description: PGP signature

Reply to: