Bug#568088: marked as done (cdrom: Debian does not boot right after installation)

[owner@bugs.debian.org (Debian Bug Tracking System)]

Your message dated Mon, 29 Aug 2011 16:38:57 -0500
with message-id <20110829213856.GH9045@elie.gateway.2wire.net>
and subject line Re: cdrom: Debian does not boot right after installation
has caused the Debian Bug report #568088,
regarding cdrom: Debian does not boot right after installation
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
568088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568088
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- Begin Message ---

• To: Debian Bug Tracking System <submit@bugs.debian.org>
• Subject: cdrom: Debian does not boot right after installation
• From: Volodymyr Shcherbyna <volodymyr@shcherbyna.com>
• Date: Mon, 01 Feb 2010 22:46:28 +0100
• Message-id: <20100201214628.3219.73848.reportbug@sv1>

Package: cdrom
Severity: critical
Justification: breaks the whole system

After installation of debian 5.0.3 x64 the OS does not boot. If I load kernel with "noapic nolapic acpi=off ide=nodma" it works. Should you have any questions about my configuration does not hesitate to ask ;)

-- System Information:
Debian Release: 5.0.4
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.26-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_CH.UTF-8, LC_CTYPE=fr_CH.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

--- End Message ---

--- Begin Message ---

• To: Volodymyr Shcherbyna <volodymyr@shcherbyna.com>
• Cc: 568088-done@bugs.debian.org
• Subject: Re: cdrom: Debian does not boot right after installation
• From: Jonathan Nieder <jrnieder@gmail.com>
• Date: Mon, 29 Aug 2011 16:38:57 -0500
• Message-id: <20110829213856.GH9045@elie.gateway.2wire.net>
• In-reply-to: <[🔎] CADWBAjaWdLJSB+jbcxd-krRXiLtOndj=Q5RyW5xuexF6gEY=jQ@mail.gmail.com>
• References: <9aa74afc1002020340y2f9a6ff5pdc2349e8d85364c3@mail.gmail.com> <20100201214628.3219.73848.reportbug@sv1> <20110126171303.GA25609@radis.liafa.jussieu.fr> <[🔎] 20110826023850.GA2681@elie.gateway.2wire.net> <[🔎] CADWBAjaWdLJSB+jbcxd-krRXiLtOndj=Q5RyW5xuexF6gEY=jQ@mail.gmail.com>

Version: 2.6.32-35
tags 568088 - moreinfo
quit

Volodymyr Shcherbyna wrote:
> 2011/8/26 Jonathan Nieder <jrnieder@gmail.com>

>> Do you remember what this was about?  Does that machine boot a more
>> recent kernel without requiring special flags now, and if so, which
>> one?
>
> I have never experienced this bug since 6.x Debian. So, I guess it is fixed.

Thanks, marking as fixed in current stable.

--- End Message ---