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

Bug#315923: marked as done (Kernel panic after Sarge installation on Dell with SATA drive)

Your message dated Sun, 14 May 2006 20:57:43 -0300
with message-id <87y7x4i2h4.fsf@nurf.casa>
and subject line Should be fixed in current images of installer
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: install
Version: debian-31r0a-i386-binary-1.iso
Severity: critical

I attempted to install Sarge (2.6.8-2-686) today on a Dell
Dimension 8400 desktop.  Upon reboot after installation,
there was a kernel panic with the following error messages:

pivot_root: No such file or directory
/sbin/init: 432: cannot open dev/console: No such file
Kernel panic: Attempted to kill init!

Just before this, the messages indicate that the kernel has found
the hard disk (Serial ATA Maxtor 6Y160M0):

scsi0: ata_piix
Using anticipatory io scheduler

  [drive info]

ata2: SATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xFFA8 irq 15

and so on (I am typing this by hand, since the machine then
crashed and there are no logs).

By replacing "hda" with "sda" in the following line in
/boot/grub/menu.lst, I was able to prevent the panic:

kernel            /vmlinuz-2.6.8-2-686 root=/dev/hda6 ro

The boot then failed when it tried to fsck the swap and
remaining ext3 partitions until I made similar replacements
of "hda" with "sda" in /etc/fstab.  This allowed the boot
process to finish, but then the kernel would not recognize
the cdrom drive.

This may be related to bugs #299478 and #285981.

Other people have described this problem here:


The same problem appears here:


without attribution or a bug reference.

Everett Lipman

--- End Message ---
--- Begin Message ---

Looks like your bug is fixed in current installer. Would be good if
you could see if it still reproducable and reopen the bug in case.

Thanks in advance,

p.s.: You can get a new installer image in

        O T A V I O    S A L V A D O R
 E-mail: otavio@debian.org      UIN: 5906116
 GNU/Linux User: 239058     GPG ID: 49A5F855
 Home Page: http://www.freedom.ind.br/otavio
"Microsoft gives you Windows ... Linux gives
 you the whole house."

--- End Message ---

Reply to: