Bug 152176

Hello David,

when reporting bugs for SUSE Linux, don't choose component `openSUSE', this is for the Wiki at opensuse.org only. Always chose the correct version and milestone, too.

This might be related to 151473, but I don't think so. What patch exactly did you install?

Your comments duly noted.  The patch is the following I believe:

  Package:                kernel
  Announcement ID:        SUSE-SA:2006:006
  Date:                   Thu, 09 Feb 2006 16:00:00 +0000
  Affected Products:      SUSE LINUX 10.0
  Vulnerability Type:     remote denial of service
  Severity (1-10):        9
  SUSE Default Package:   yes
  Cross-References:       CVE-2005-3356, CVE-2005-3358, CVE-2005-3623
                          CVE-2005-3808, CVE-2005-4605, CVE-2005-4635
                          CVE-2006-0454

I cannot see how this should be related, did this patch really touch any of the filesystem code in the kernel? Did you install more patches than this one?

The history of this issue is as follows:

1) Installed 10.0 and did online update as part of the installation.  Install completed successfully but on reboot the reported error occured.

2) Reinstalled 10.0 but did NOT do online update during install.  Install completed succesfully and no problems after reboot.  Then installed all outstanding patches (OOo & KDE updates etc), including Kernel update and reported problem occured on reboot.

3) Reinstalled 10.0 but did NOT do online update.  Install completed succesfully and no problems after reboot.  Then installed all outstanding patches (OOo, KDE updates etc) but NOT including Kernel update.  System reboots properly.  Then installed the kernel update and on reboot the reported error occurs.

Current status is that system is reinstalled without the kernel update.  i am reminded when I log in that there is a security update available.

OK then this should be checked by the kernel maintainers. The patch seems to break SATA-support in some cases.

Please attach `hwinfo --storage-ctl' boot.msg and 500 lines of the syslog of the _broken_ installation here.

Does this not mean I will have to download the patch and effectively break my system again?  If so, is there some sort of repair I can do afterwords to avoid having to do yet another complete re-install?       

Sorry but unless we have further information, how should be debug this? Normally test machines are thought for such purposes.

If it is a kernel patch, you can backup the current kernel and re-install it with a rescue system (disk 1) after you did the testing.

Ok, but it will be a few days before i can do this.  I have to wait until the family Tuxracer championships have finished.

OK then please reopen this report once you can provide the information.

I'm expierencing the same problem. The only difference is that I didn't do the online upgrade. But I installed through FTP so perhaps the patch was already committed to the installation sources.

I tried to get the information available that was asked a couple of posts earlier. But the boot process stops at an very early time. Therefore "hwinfo --storage-ctrl" is not recognized as a command. "cat /var/log/boot.msg" doesn't work either: no such file or directory. Which seems kinda logical to me since it can't find my /dev/sda7 which is my root partition.

I've written down a number of lines that become visible during the boot process. Perhaps that these help:

SCSI subsystem initialized
Loading sata_via
ACPI-0212: Warning device not power manageable
ata1: SATA max UDMA/133    irq 11
ata2: SATA max UDMA/133
SCSI0: sata_via
SCSI1: sata_via
       Vendor: ATA        Model: Maxtor 7L300S0   Rev: BACE
       Type: Direct address     ANSI SCSI rev: 05
SCSI device sda
sda sda1 sda2 <sda5 sda6 sda7>
Attached SCSI disk sda at SCSI0, channel 0, id 0, lun 0
Loading via 82cxx
IRQ 9 nobody cared (some additional comments)
Then follows a table with IRQ's.
Disabling IRQ 9. Try option "irqpoll"

Waiting for resume device /dev/sda6 not found (ignoring)
Waiting for device /dev/sda7 to appear not found exiting to /bin/sh

Then it's dead.

I also tried that option "irqpoll". That leads to the following kernel panic.
Kernel-panic - not syncing Attempted to kill init.

Regarding my hardware:
I installed opensuse 10.0 on a Maxtor 7L300S0 sata disk, that's attached to an ASUS A7V600-X motherboard, with bios revision 1004.

mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)

mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)

mass reopening all SuSE Linux bugs that are set to REMIND+LATER to change the resolution to WONTFIX (adapting to new policy)

Closing old LATER+REMIND bugs as WONTFIX - if you still plan to work on it, feel free to reopen and set to ASSIGNED.

In case the report saw repeated reopen comments, it's due to bugzilla timing out on the huge request ;(