https://bugzilla.novell.com/show_bug.cgi?id=383866 User markgray+to-suse@puck.nac.net added comment https://bugzilla.novell.com/show_bug.cgi?id=383866#c1 --- Comment #1 from Mark Gray 2008-04-25 11:33:36 MST --- Created an attachment (id=210568) --> (https://bugzilla.novell.com/attachment.cgi?id=210568) y2log-1 of installation of 11.0-Beta1 There was also a y2log created, but it appears to only include output generated during the install of the bootloader. (I will attach it too if you think it might be significant.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=383866 User markgray+to-suse@puck.nac.net added comment https://bugzilla.novell.com/show_bug.cgi?id=383866#c3 --- Comment #3 from Mark Gray 2008-04-26 10:24:53 MST --- Okay -- I reinstalled openSUSE-11.0-Beta1 on a ext3 partition using 128 byte inodes so I could boot it using 10.2's grub (which cannot read 11.0's default 256 byte inodes BTW), and the installation died in the same manner. I reinstalled 10.2's grub to get past the infinite "failure to boot" loop and booted the installed 11.0-Beta1 passing it the irqpoll boot parameter. The installed system successfully booted and the configuration proceeded until it reached 95% into the hardware configuration at which point the system hung with the CapsLock and ScrollLock keyboard lights flashing on and off. Both the keyboard and mouse were totally unresponsive, so after waiting a while I powered the computer off and rebooted again, (once again using the irqpoll boot parameter.) This time the configuration proceeded to completion and I had a fully functional 11.0-Beta1 at the end of it. Not sure if this additional information changes the bug responsibility from the kernel to some installation or configuration utility, but in any case I am quite happy to provide any additional information which might make 11.0 install easier on computers like mine. (10.0, 10.1, 10.2 and 10.3 installed without any hassles at all (apart from some video bios annoyances)). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=383866 User markgray+to-suse@puck.nac.net added comment https://bugzilla.novell.com/show_bug.cgi?id=383866#c5 --- Comment #5 from Mark Gray 2008-04-29 10:41:56 MST --- I just tried kernel-default-2.6.25-19.x86_64.rpm from factory, and it still requires irqpoll in order to boot -- same bug. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=383866 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=383866#c9 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |markgray+to-suse@puck.nac.net --- Comment #9 from Tejun Heo 2008-04-30 03:50:07 MST --- Mark, can you please post /var/log/boot.msg and does kernel parameter "noacpi" or "noapic" make any difference? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=383866 User markgray+to-suse@puck.nac.net added comment https://bugzilla.novell.com/show_bug.cgi?id=383866#c11 --- Comment #11 from Mark Gray 2008-04-30 07:09:11 MST --- Created an attachment (id=211503) --> (https://bugzilla.novell.com/attachment.cgi?id=211503) /var/log/boot.msg from successful boot using noapic Hope this helps. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=383866 User trenn@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=383866#c13 Thomas Renninger changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kasievers@novell.com, gregkh@novell.com --- Comment #13 from Thomas Renninger 2008-04-30 20:13:27 MST --- I first thought noirqbalance could help (heard about problems here), but it seems we do have: # CONFIG_IRQBALANCE is not set I can remember that Greg and Kai had plans (AFAIK they stopped them again long ago) to parallize the boot process for boot speed-ups. If something like this really is related (as Mark states above), Greg or Kai might know -> adding to CC. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=383866 User markgray+to-suse@puck.nac.net added comment https://bugzilla.novell.com/show_bug.cgi?id=383866#c15 --- Comment #15 from Mark Gray 2008-05-01 10:33:19 MST --- I think I found the culprit: snd-hda-intel -- this machine "thinks" it has two sound cards, a "Hewlett-Packard Company IXP SB400 AC'97 Audio Controller" which uses the snd-atiixp kernel module, and an "ATI Audio device" which uses the snd-hda-intel kernel module. Prior to 11.0 only the snd-atiixp device was configured, but 11.0 also auto-configures the snd-hda-intel device. Deleting the snd-hda-intel device using yast and removing the snd-hda-intel.ko module from /lib/modules/ allows 11.0 to boot without using either irqpoll or noapic as a kernel parameter. As a test to see what 10.2 would do if the snd-hda-intel were configured, I tried to do so on a running system and the machine hung semi-solid (it was pingable, but the SATA disk had its interrupt disabled making the machine useless.) I suspect that the second audio card is not "really" a card which the snd-hda-intel driver is capable of handling, and it might not even be a sound card at all, since there are only audio jacks for one card and the snd-atiixp card has always worked perfectly with the machine (since openSUSE 10.0). As I see it, there are two separate bugs here: 1. The snd-hda-intel problem, and 2. The fact that the first boot of the installed system does not allow you to easily add kernel parameters if the first try fails. The user is trapped in a boot failure loop until he uses a rescue disk to reinstall grub, and manually edit the menu.lst -- not a situation you want an inexperienced user to have to endure. I will try 11.0-Beta2 when I can get it, and I am quite willing to try anything else with Beta1 in the meantime. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=383866 User tiwai@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=383866#c17 --- Comment #17 from Takashi Iwai 2008-05-02 08:38:46 MST --- It looks weird that the system shows both PCI devices. They usually don't support both at once, and one of them should be disabled by BIOS. I guess the driver is loaded even though the device actually doesn't work (and crash with AC97 bus). The problem appears newly because now sound drivers are loaded via udev, too. On 10.2, the sound driver was loaded via hwcfg. Now, all drivers assigned to available PCI devices are loaded automatically. That's why it appears now. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=383866 User kasievers@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=383866#c19 Kay Sievers changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |markgray+to-suse@puck.nac.net --- Comment #19 from Kay Sievers 2008-05-03 11:22:17 MST --- I doubt that this can, or needs to be fixed at the udev level. Besides that there are possibly "too many" PCI devices, loading a module should not just "crash" the box. It likely needs a fix in the driver. Anyway, does adding: blacklist snd-hda-intel to: /etc/modprobe.conf.local makes the system boot as expected? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=383866 User kasievers@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=383866#c21 Kay Sievers changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |markgray+to-suse@puck.nac.net --- Comment #21 from Kay Sievers 2008-05-03 14:10:59 MST --- Great, thanks to for the quick response. Does: modprobe snd-hda-intel after bootup, break the box again? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=383866 User markgray+to-suse@puck.nac.net added comment https://bugzilla.novell.com/show_bug.cgi?id=383866#c23 --- Comment #23 from Mark Gray 2008-05-04 13:59:39 MST --- I just tried 11.0-Beta2 and encounter the same problems with snd-hda-intel -- a hang during the initial boot of the installed system for the second stage of the install. But this time after powering down and booting again I am presented with a grub menu which allows me to add kernel parameters to finish up the installation properly. I tried installing using "brokenmodules=snd-hda-intel" and while "blacklist snd-hda-intel" was added to /etc/modprobe.d/blacklist, the hardware configuration does an explicit modprobe snd-hda-intel causing a system hang anyway, although at a later stage of the installation, so it is still necessary to boot using either "irqpoll" or "noapic" and delete the snd-hda-intel configuration from the running system in order for the blacklist to prevent problems. 10.2 has "blacklist snd-hda-intel" in /etc/modprobe.d/blacklist from day 0, so I suspect snd-hda-intel is a known problem module from wayback. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=383866 User markgray+to-suse@puck.nac.net added comment https://bugzilla.novell.com/show_bug.cgi?id=383866#c25 Mark Gray changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|markgray+to-suse@puck.nac.net | --- Comment #25 from Mark Gray 2008-05-05 10:57:53 MST --- Bingo! I updated to BIOS version 3.15 01/25/2007 and surprise, surprise -- the HDA Audio device has disappeared completely from both Linux and Win-XP. Thank you! I will leave it up to you people to close the bug using whichever label you prefer. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.