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

Bug#473398: marked as done (new "linux-image-2.6.24-1-amd64" does not boot anymore (semmes to be a problem with kernel-module "ata_generic"))

Your message dated Mon, 1 Feb 2010 14:27:16 +0100
with message-id <20100201132716.GF9849@stro.at>
and subject line Re: Bug#473398: new "linux-image-2.6.24-1-amd64" does not boot anymore (semmes to be a problem with kernel-module "ata_generic")
has caused the Debian Bug report #473398,
regarding new "linux-image-2.6.24-1-amd64" does not boot anymore (semmes to be a problem with kernel-module "ata_generic")
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.)


-- 
473398: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=473398
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.24-1-amd64
Version: 2.6.24-5

After a normal apt-get update && apt-get upgrade under deban sid it wanted to update my installed 2.6.24-kernel (amd64). After rebooting the machine the upgraded kernel told me that /dev/sda2" - my partition where debian is installed - can't be found.
After removing the "quiet" option I saw a lot of "unknown symbol"-strings coming up from the ata_generic-module.
One of them is (if you need the whole screen-output just tell me, but it's no fun to copy everything manually, because copy&pasting is not possible):
ata_generic: Unknown symbol ata_scsi_slave_config
My Harddisk is a SATA-disk and my setup is a cryptsetup on /dev/sda2 (dm-crypt/luks) and a LVM on the crypt (/dev/sda2_crypt).
Everything was working fine with the prior 2.6.24-image and the still being installed 2.6.22 is also working fine.
This whole setup was made with the normal debian-installer - I didn't change anything of the setup manually.
Seems that the ata_generic-driver is broken which is needed to recognize the paritition table of ma SATA-Device.

A CC was also sent to debian-kernel@lists.debian.org

Even if the E-mail-address is a spam-email-address i'll check the account for any non-spam-mail's so i'll read responses for sure.

Regards

Mirko (d@ten)

--- End Message ---
--- Begin Message --- 
On Fri, 14 Aug 2009, Moritz Muehlenhoff wrote:

> On Sun, Mar 30, 2008 at 02:22:44PM +0200, foobar wrote:
> > Package: linux-image-2.6.24-1-amd64
> > Version: 2.6.24-5
> > 
> > After a normal apt-get update && apt-get upgrade under deban sid it wanted to update my installed 2.6.24-kernel (amd64). After rebooting the machine the upgraded kernel told me that /dev/sda2" - my partition where debian is installed - can't be found.
> > After removing the "quiet" option I saw a lot of "unknown symbol"-strings coming up from the ata_generic-module.
> > One of them is (if you need the whole screen-output just tell me, but it's no fun to copy everything manually, because copy&pasting is not possible):
> > ata_generic: Unknown symbol ata_scsi_slave_config
> > My Harddisk is a SATA-disk and my setup is a cryptsetup on /dev/sda2 (dm-crypt/luks) and a LVM on the crypt (/dev/sda2_crypt).
> > Everything was working fine with the prior 2.6.24-image and the still being installed 2.6.22 is also working fine.
> > This whole setup was made with the normal debian-installer - I didn't change anything of the setup manually.
> > Seems that the ata_generic-driver is broken which is needed to recognize the paritition table of ma SATA-Device.
> > 
> > A CC was also sent to debian-kernel@lists.debian.org
> > 
> > Even if the E-mail-address is a spam-email-address i'll check the account for any non-spam-mail's so i'll read responses for sure.
> 
> Does it work with more recent kernels?

closing as no answer since.

if the bug can be reproduced with recent linux-2.6 this can be reopened.
thanks for the report

--- End Message ---
Reply to: