Kernel oops with pata_sis

[Patrick Hoffmann]

Binary package hint: linux-image-2.6.20-15-generic

I can't boot Ubuntu Feisty because of a bug in the pata_sis driver.
This bug has been fixed by Alan Cox.

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=235902#c14

[Dan O'Huiginn (daniel-ohuiginn)]

Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description doesn't yet have enough information.

Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] http://wiki.ubuntu.com/KernelTeamBugPolicies.

Note that there have been various recent problems with pata drives, which have been fixed very recently. See bug #82314, for example.
Thanks in advance!

[Patrick Hoffmann (sobran)]

From the LiveCD:
Linux ubuntu 2.6.20-15-generic #2 SMP Sun Apr 15 07:36:31 UTC 2007 i686 GNU/Linux

[BastiBense (basti-bense)]

Using Ubuntu Feisty 7.04 final.
I can confirm this on my Gericom Frontman Force.
LiveCD-Installation works fine, after reboot the whole system hangs with problem in pata_sis.
Worked fine with Feisty beta.

[Peter Chabada (ubuntu-chabada)]

I can confirm this bug on my system too when booting from alternative cd. I cannot install feisty from alternative cd iso, but I can install dapper and then upgrade it to feisty and then feisty boots without this bug.

[David Brown (dmlb2000)]

Should the pata drivers not be put into the default initramfs then? I had upgrade issues from 6.10 to 7.04 because the initramfs created tried to load this driver and wouldn't ever get to the root hard-drive.

When will this be fixed? eta? I'd like to revert the changes I made to the initramfs package so I can use the default configuration again.

[azium (azium)]

David -- I agree, this needs to be fixed ASAP. My box is dead until this is
resolved. The old 6.10 was wiped by the install, but 7.04 dies in initramfs
- so I'm left with nothing.

On 26/04/07, David Brown <email address hidden> wrote:
>
> Should the pata drivers not be put into the default initramfs then? I
> had upgrade issues from 6.10 to 7.04 because the initramfs created tried
> to load this driver and wouldn't ever get to the root hard-drive.
>
> When will this be fixed? eta? I'd like to revert the changes I made to
> the initramfs package so I can use the default configuration again.
>
> --
> Kernel oops with pata_sis
> https://bugs.launchpad.net/bugs/107774
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[David Brown (dmlb2000)]

well the work around while the kernel is getting built is to go in and change the initramfs package to only use the files listed.
I don't have an ubuntu box in front of me so bear with me...
edit /etc/initramfs-tools/initramfs.conf (??) and switch the first option to list (iirc). Then edit the /etc/initramfs-tools/modules.list file and add the appropriate ide drivers for the root hard drive, remember to include the filesystem drivers as well. I ended up having something like:

sis5513
reiserfs
ide-core
ide-disk
generic

Then regenerate the initramfs file (mkinitramfs -o /boot/initrd.img-2.6.20-4-386 2.6.20-4-386 && mkinitramfs -o /boot/initrd.img-2.6.20-4-generic 2.6.20-4-generic) and I was able to boot just fine, udev didn't even try to autoload the pata driver so you should be good.

[Eugene Cormier (eugene-cormier)]

Thanks David, your fix worked great for me....I have an Aopen motherboard using the pata_sis and I used (I have ext3 file system instead of reiser):
sis5513
ext3
ide-core
ide-disk
generic

I was using and older kernel that I grabbed off the first alpha of feisty, but now I can get back to regular life :)

Thanks again

Eugene

[xNalam (felipeap)]

Thanks too David ... worked like-a-charm in my Asus P4S333 (SiS 645 Chipset / SiS 5513 IDE Controller).

After 9 days since I've downloaded Feisty I'm finally able to actually use it =D

Good luck for all who still have this dark-side-evil-bug !

(Do I really need to patch my pata_sis.c or should I keep use the modified initrd ???)

[David Brown (dmlb2000)]

You could keep the modified initrd just fine, the way I recommended you modify the initrd should keep across upgrades and such.

I experienced this bug with 2.6.20-4-386 and 2.6.20-4-generic, which means by 2.6.20-5-386 and 2.6.20-5-generic it should be fixed. However, I'm not an ubuntu kernel guy, just a regular kernel guy so I don't know what sort of distro policies they have in place for releasing important critical parts of a linux system. 2.6.20 in general was a much better release of the linux kernel than most of the other releases (imho), so any continued work on that version of the kernel should only get better.

[BastiBense (basti-bense)]

FYI, i did a clean install of Ubuntu 6.10 on my Gericom Frontman Force, then updated 6.10, afterwards did an dist-upgrade to Feisty. Everything works just fine.

[David Brown (dmlb2000)]

This may only happen on specific sis hardware, specifically mine is an
older pentium4 that uses sdram the newer sis motherboards may not have
this issue.

On 4/29/07, Cheetahcat <email address hidden> wrote:
> FYI, i did a clean install of Ubuntu 6.10 on my Gericom Frontman Force,
> then updated 6.10, afterwards did an dist-upgrade to Feisty. Everything
> works just fine.
>
> --
> Kernel oops with pata_sis
> https://bugs.launchpad.net/bugs/107774
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[FuturePast (4uturepast)]

Problem seen here too.
initramfs workaround fixed for me.

Good work, thanks!

00:00.0 Host bridge: Silicon Integrated Systems [SiS] 650/M650 Host (rev 01)
00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP)
00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS961 [MuTIOL Media IO] (rev 10)
00:02.1 SMBus: Silicon Integrated Systems [SiS] SiS961/2 SMBus Controller
00:02.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 07)
00:02.3 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 07)
00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (rev d0)
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] AC'97 Sound Controller (rev a0)

[georgielove (gorkaamor)]

I am in the same situation:

First of all i will describe my sistem:
Pentium IV 1.5 Mhz on a SiS 645DX/961B (NS70-EL from DFI) chipset board, with two ATA Hard Disk. I am trying to install feisty, and with the feisty livecd, hard disks are partitioned like this:

First Hard Disk 40 gb (Master of IDE1)
hda1-> Windows XP (30 gb). I want to keep it aswell.
hda2-> / (8.5 gb approx)
hda3-> swap (1.5 gb approx)

Second Hard Disk 120 gb (Slave of IDE1)
hdb-> /home (120 gb)

After installing, i reboot and the remove the livecd, and when when grub loads, I select the latest Kernel (2.6.20-15), and then the progressbar does not make any progress. (Same bug in the Kernel (2.6.20-12 to 2.6.20-15 last one). After one or two minutes i can see this:

"Udevd-event [1950]: run-program: '/sbin/modprobe' abnormal exit

BusyBox v.1.1.3 (Debian 1:1.1.3-3ubuntu3) Built-install (ash)

/bin/sh: can access tty; jub control turned off (initramfs)"

and this:

"ALERT! /dev/disk/by-uuid/xxxxxxxxxxx Does not exist, dropping to a shell"

i thinks that "xxxxxxxxxxxx" is the by-uuid identificator for the system disk "/"
The number of Udevd-event [xxxx] can vary from 1950 to 1960 (in other install tryings)
The system works perfectly with Edgy with the same partitioning configuration.

[Valerio F. Laube (vflaube-gmail)]

For reference only: the same bug is also discussed on:

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/107976

http://ubuntuforums.org/showthread.php?p=2525534#post2525534

https://answers.launchpad.net/ubuntu/+question/4147

[Valerio F. Laube (vflaube-gmail)]

How can we obtain a iso image for installing Feisty with this bug fixed ?

[Christopher Hoyt (christopher-hoyt4)]

This problem was with ubuntu feisty, kernel 2.6.20-16-generic. Sis 5513 controller.
This problem showed up with me as long boot time, the system couldn't identify me secondary ide controller, but took time to try.
In 'System/Preferences/Hardware Information' , 'Device Manager', the second CD drive wasn't identified, the first CD drive was identified.
After reading about the 'initrd' troubles above, I replaced the faulty 'initrd' with the one from UbuntuStudio, on the same machine.
UbuntuStudio didn't have the problem.
I verified that all was well by looking at 'Device Manager': both CD drives were identified.

[Leann Ogasawara (leannogasawara)]

Just cleaning up this report. The patch to fix this bug was included in the Ubuntu Feisty kernel. I'll include the git commit id and description. Marking this 'Fix Released'. Thanks.

commit 1b27e19fa9145a1579cfecccf7d5be7d7e242e46
Author: Phillip Lougher <email address hidden>
Date: Tue May 1 17:06:51 2007 +0100

    UBUNTU: Fix pata_sis crashes preventing booting
    OriginalAuthor: Alan Cox <email address hidden>
    Bug: 107774

    Signed-off-by: Phillip lougher <email address hidden>

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.