Bugzilla – Bug 548108
DVD-Installation System hangs after kernel has been loaded
Last modified: 2018-07-03 20:18:02 UTC
User-Agent: Mozilla/5.0 (compatible; Konqueror/4.3; Linux) KHTML/4.3.1 (like Gecko) SUSE DVD installation, after pressing Installation on DVD menue, status bar indicates that kernel being loaded until it reaches 100% system stops. Last message line on console being displayed is "0.1880001 [<ffffffff8100d6ca child_rip+0xa/0x20>] Reproducible: Always Steps to Reproduce: 1.Start DVD Installation process description in german and Hardwareinfo - more in detail Installations-DVD startet wie gewohnt, Lässt mich die Bootoptionen (Sprache, Auflösung, ...) wie gewohnt auswählen, nach dem drücken auf Installation wird wie gewohnt der Statusbalken für den Kernel angezeigt, nachdem der Kernel geladen ist - schwarzer Schirm - die Insallation stoppt. Beim Start mit der VGA - Auflösung oder textbasirte Install. sieht man nach dem Kernelstart einen Screen voll acpi-Meldungen die bei folgenden Eintrag abbrechen: 0.188001 [< ffffffff8100d6ca child_rip+0xa/0x20>] Habe bios geflasht, DVD auf dem Notebook getestet und opensuse 11.2. ohne Probleme installieren können, dann das Gleiche mit 11.2. milestone7 probiert - selber Effekt. Am berteffenden Rechner habe ich alle bisherigen Suseversionen installieren können. Mainbord: Gigabyte GA-MA69GM-S2H, AMD 690G Chipset, Giabite HD4850 Graka, 3 Festplatten S-ATA, 1 Brenner Plextor, LG 245 TFT
Not YaST-Installer related
I have the same problem with the retail installation DVD. openSUSE 11.1 installed without problems on the same system with the same BIOS settings. My hardware configuration (from my 11.1 installation)is here: https://bugzilla.novell.com/attachment.cgi?id=236430 I experimented with BIOS settings without any success. With "Safe settings" or without acpi it boots into the installation system but fails to detect my SATA disk drives. POTENTIAL SOLUTION: By trial and error I found that kernel parameter "acpi=ht" seems to help, i.e. it boots into the installation system and sees my SATA disk drives. I did not yet install actually, because I want to investigate potential side effects of the setting "acpi=ht" first, before I overwrite my running 11.1 installation. Booting my existing openSUSE 11.1 system with "acpi=ht" seems to work, except that the computer did not power off automatically at shutdown as usual. What is the difference between openSUSE 11.1 and 11.2 installation creating this problem?
The problem seems not to be only with the installation kernel. I have the strong suspicion that the following thread in the forum relates to the same problem: http://forums.opensuse.org/install-boot-login/426112-install-boot-11-2-kernel-hang.html
I have the same problem here. openSuse since version 11.0 and several other distros ran well on my computer, but openSuse 11.2 won't run wihtout acpi=off. This is really annoying, because the computer won't power off properly. Some interesting lines in my dmesg are the following: [ 16.905223] powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core Processor 6000+ processors (2 cpu cores) (version 2.20.00) [ 16.905223] [Firmware Bug]: powernow-k8: No compatible ACPI _PSS objects found. [ 16.905223] [Firmware Bug]: powernow-k8: Try again with latest BIOS.
I installed openSUSE 11.2 on a separate partition of my computer and did some investigations. - Also the installed system only boots with "acpi=ht", see attached picture for messages before freeze when booting with ACPI on - During boot with "acpi=ht" I get some scary messages and the boot process hangs at "Creating devices" until timeout - see separate bug 559048 - Cannot configure SCSI scanner, no detection by YaST, sane-find-printer hangs, see separate bug 559046 -Shutdown does not terminate regularly, disks are not properly unmounted, see separate bug 559049 With the above experience I decide not to switch to 11.2 until the problem is solved. 11.2 is basically unusable for me in the current status. Therefore I vote for upgrading this bug to "Critical". I repeated everything that failed on 11.2 on my installed 11.1 system on the same computer - it worked without any problem, a perfectly stable system.
Created attachment 329915 [details] Messages before freeze when booting with ACPI on
Same problem with GA-MA790X-DS4 motherboard.
Created attachment 330598 [details] Messages when booting with the installed kernel and "acpi=ht"
Hardware: - CPU: AMD Phenom X4 9550 4x2.2GHz (95W) 65nm Quad Core - Memory: 4GB - 2x2048MB DDR2-800 CL5, Dual Channel 2x1024MB - Motherboard: GIGABYTE GA-MA770-DS3, AMD 770 / SB600 chipsets - Graphics: NVidia GeForce 7300 GS, 256MB, TV-Out, DVI, PCIe - Floppy: 1.44MB - 1. hard disk: 500GB Seagate 7200 RPM SATA II - 2. hard disk: 500GB Seagate 7200 RPM SATA II - DVD-ROM: Optiarc DDU 1615 16x/48x, IDE - DVD-RW: NEC AD-7200, IDE - SCSI-Controller: Adaptec 2940 SCSI adapter, SCSI ID: 7 - Tape Streamer: Seagate (CONNER) CTT8000-S SCSI Tr 4, SCSI ID: 4 - Scanner: UMAX Astra 610S SCSI SCSI ID: 5 - Card Reader: Apacer AE101, 16 card types - DVB Controller: Technotrend/Hauppauge DVB card rev2.1
I have the same problem with a Gigabyte GA-MA69GM-S2H. Opensuse 11.2 (64) works only with ACPI off; acpi=ht doesn't change anything. I was triggered by this message: [ 12.654606] powernow-k8: Found 1 AMD Athlon(tm) X2 Dual Core Processor BE-2400 processors (2 cpu cores) (version 2.20.00) [ 12.654630] [Firmware Bug]: powernow-k8: No compatible ACPI _PSS objects found. [ 12.654631] [Firmware Bug]: powernow-k8: Try again with latest BIOS. I upgraded the BIOS van F5 to F7b. No difference; With 11.1 i don't have this problem. With ACPI ON I have exactly the same 'hang' as Alexander showed with his attachment.
Same pb here with hardware ( see attachement ) bug with this start line it works root=/dev/disk/by-label/SLASH instmode=http keyboard=fr-ch-latin1 acpi=ht resume=/dev/disk/by-label/SWAP1 splash=verbose verbose elevator=cfq apic=verbose lapic pci=acpi acpi_irq_balance vga=0x31a dmesg & hardware info will follow. In comparaison : ubuntu 9.10 ( 2.6.31 is working also a sysrescuecd 1.3.2 )
Created attachment 331572 [details] HWINFO Mobo gygabytes MA-790FX-DQ6 the complet hwinfo.
Make a mistake (suse-install leave me a acpi=ht ) So for the moment it boot only with acpi=ht or apci=off I will try the 2.6.32 HEAD Factory kernel comming from here http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_Factory/x86_64/kernel-default-2.6.32-39.1.x86_64.rpm + base See you in some time
Not working ! Trying a kernel-vanilla + kerneloops But as I have to start with acpi=ht some modules are missing during the mkinitrd process Récupération de paquet kerneloops-0.12-32.4.x86_64 (1/2), 23,0 KiB (38,0 KiB decompressé) Récupération: kerneloops-0.12-32.4.x86_64.rpm [fait] Installation: kerneloops - 0.12-32.4 [fait] Récupération de paquet kernel-vanilla-2.6.31.5-0.1.1.x86_64 (2/2), 29,4 MiB (109,4 MiB decompressé) Récupération: kernel-vanilla-2.6.31.5-0.1.1.x86_64.rpm [fait] Installation: kernel-vanilla - 2.6.31.5-0.1.1 [fait] Additional rpm output: Kernel image: /boot/vmlinuz-2.6.31.5-0.1-vanilla Initrd image: /boot/initrd-2.6.31.5-0.1-vanilla Root device: /dev/disk/by-id/ata-WDC_WD1500HLFS-01G6U0_WD-WXL808006411-part3 (/dev/sda3) (mounted on / as ext4) Resume device: /dev/disk/by-label/SWAP1 (/dev/sda2) modprobe: Module ahci not found. WARNING: no dependencies for kernel module 'ahci' found. modprobe: Module sd_mod not found. WARNING: no dependencies for kernel module 'sd_mod' found. modprobe: Module uhci_hcd not found. WARNING: no dependencies for kernel module 'uhci-hcd' found. Kernel Modules: pata_jmicron pata_atiixp ata_generic ide-core atiixp ide-pci-generic thermal_sys processor thermal fan crc16 jbd2 ext4 Features: block usb resume.userspace resume.kernel Bootsplash: openSUSE (1280x1024) 29567 blocks
ok vanilla kernel is booting normally this prove that something is clearly wrong in suse patch for kernel ( including next 2.6.32 ). As said before this computer have correctly works for opensuse 11.0 & 11.1 I push the vanilla dmesg in attachment
Created attachment 331577 [details] dmesg from working vanilla Same hardware
Many more examples for this problem at bug 557586
Vanilla kernel boots on my system without any problems with acpi switched on linux-3yrb:/home/alexande/support # uname -a Linux linux-3yrb 2.6.32-41-vanilla #1 SMP 2009-12-11 11:05:24 -0500 x86_64 x86_64 x86_64 GNU/Linux See attachment of dmesg with vanilla kernel
Created attachment 332349 [details] Output of demesg after booting with vanilla kernel
I installed the latest default kernel from SUSE Factory from http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_Factory/x86_64/kernel-default-2.6.32-41.2.x86_64.rpm linux-3yrb:/home/alexande/support # uname -a Linux linux-3yrb 2.6.32-41-default #1 SMP 2009-12-11 11:05:24 -0500 x86_64 x86_64 x86_64 GNU/Linux and system boots and runs with acpi (same hardware, same BIOS settings). I also tried the default kernel 2.6.31.5-0.1 from the distribution - this one does NOT work
Created attachment 333014 [details] dmesg with default kernel 2.6.32-41.2
Looking at comment 14 and comment 20 it appears that the problem was solved between kernel versions 2.6.32-39 and 2.6.32-41. A backport of this fix to 2.6.31 and release as online update would be desirable.
Customer lend me the problematic computer. So I will retry the lastest 2.6.32 and see if it works. I'm totally agree about the patch NOW for the 11.2. As all other distributions are working we are just loosing customers and new users as the just tend to go to something working : ubuntu,fedora,mandriva,windows ;-( Perharps Roland would agree to change the subject to something more explicit opensuse 11.2 kernel crash with acpi on gigabytes AMD motherboard. Come back in a few hours
Created attachment 333226 [details] Detailled Hardware screen The capture of the start screen bios details
Created attachment 333228 [details] Screenshot of the crash (Best Effort) Here's the best screenshot I can have. There's a serial com1 port but no more null modem cable here. Can have debug on netconsole trash before. Can we help more with some kernel flavor ( -debug, kerneloops ? )
So bad news here, even after upgrading to F6 firmware. I've just try my best to get the complete backtrace, but I would certainly need a step by step howto install debug package and something to catch this oops. I've the computer with me, so it's more easy to try and debug with it, but only for the next 10 days.
Change installation to kernel as only kernel suse's patched are involved. I can get kernel-debug booting version 2.6.32-41 the last part seen before entering kdb 0.309442 Freeing initrd memory: 6894k freed 0.312001 Setting APIC routing to flat 0.312001 weird, boot CPU(#0) not listed by the Bios 0.312001 SMP Motherboard not detected 0.312001 BUG: unable to handle kernel NULL pointer dereference at 000000000000025 0.312001 IP: [<ffffffff81268b97>] dmar_ir_support+0x7/0x10 0.312001 PGD 0 0.312001 Oops: 0000 [#1] SMP 0.312001 last sysfs file: .... I can make a lot of manipulation. Just help me to debug one of the suse patch ( vanilia kernel is working with no trouble )
Created attachment 334327 [details] Stack trace with kernel-debug 2.6.32-41
Don't forget, the i686 install/kernel work normally on the same hardware ...
ok after having very big doubts about hardware, here's what have been done. Update firmware to beta7, downgrade to F5 and finally put the F6 specifying the replace dmi code. After that enter bios setup choose "optimized settings" Have put all ide to sata->ahci. Activated some cpu thermal check and fan warning save by F10. I've used firstly the debug kernel, without any cmdline parms. As it boot successfully I give a try to the normal 2.6.31 11.2 released kernel. And this one is also working. Very strange. I put in attachement the lastest running & working 2.6.31 dmesg
Created attachment 334328 [details] the dmesg of working kernel works for me
Created attachment 334329 [details] ACPI still 'hangs' after apply suggestion comment 30 & 31
It does not work for me. I CAN work/live with OpenSUSE 11.2 with ACPI off but testing the suggestions in comment 30 does not solve this problem with ACPI 'activated' (Gigabyte GA-MA69GM-S2H)
WAIT, wait It WORKS! I thought that Bruno in comment 30 was mentioning F6 as Function-key F6 in the BIOS menu (Load Default settings) but BIOS version F6 does the trick; Powernow also works fine here. Thanx!
F5 F6 F7 is the BIOS LEVEL not the Function Key.
For 2.6.32, I've added a patch to avoid the oops on boot. It was due to the kernel looking for a DMAR ACPI table and not finding one but then expecting it to be there later. Please test a KOTD master kernel with: - patches.fixes/dmar-fix-oops-with-no-dmar-table: dmar: Fix oops with no DMAR table (bnc#548108). .. in the changelog.
Do I understand correctly that the installation kernel works with BIOS version F6 and mainboards MA-790FX-DQ6 and GA-MA69GM-S2H? I have mainboard GA-MA770-DS3 and BIOS version F6. - The installation kernel does NOT work with ACPI - The vanilla kernel works with ACPI - The factory kernel kernel-default-2.6.32-41.2.x86_64.rpm DOES WORK with ACPI There is a F7 BIOS (from January 2009) available for my mainboard - should I give it a try? Nevertheless, I'd prefer to have an installation kernel on 11.2 that works on a system that worked without problems on 11.0 and 11.1.
Hi Alex. It has worked for me. Try the step I've made #C30 Don't forget to update also DMI part of the bios as by default it was uncheck. I've firstly update to F6 and then to F7 (but a beta bios which doesn't contain pxe boot). After I've downgrade to F5 and at least to F6 each time upgrading DMI + resetting the bios to "optimal settings" After that the debug kernel was working, and after the 2.6.32 & 2.6.31 are running magically . Be the force with you too :-)
Hi Bruno, F7 is the latest stable version for my mainboard, there is a beta F8F. So I'll try F7. Which BIOS flash procedure did you use? DOS boot disk or Q-Flash? I can't use @BIOS because I have no native Windows on this computer. Where can I check that the DMI part is updated? I don't find any such option in the descriptions of Q-Flash or BIOS update with DOS disk as provided on the Gigabyte web site.
*** Bug 559680 has been marked as a duplicate of this bug. ***
I should have looked a bit closer at the BIOS update instruction - it was too late last night ;-). This morning I updated my BIOS to version F7 (MB GA-MA770-DS3 rev. 1) using Q-flash -- the installation kernel works with ACPI switched on now !!!! :-)). Thanks to all and especially to Bruno. However I still recommend to investigate why a BIOS, which worked perfectly with 11.0, 11.1 and with the vanilla kernel, fails with the standard 11.2 SUSE kernel.
(In reply to comment #36) > For 2.6.32, I've added a patch to avoid the oops on boot. It was due to the > kernel looking for a DMAR ACPI table and not finding one but then expecting it > to be there later. > > Please test a KOTD master kernel with: > - patches.fixes/dmar-fix-oops-with-no-dmar-table: dmar: Fix oops > with no DMAR table (bnc#548108). > > .. in the changelog. Hi Jeff, don't know if I've got the kernel version you mention. The lastest available today from http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_Factory/x86_64 has been build on Dec 14th. Sources are marked from Dec 11th. Is the one you want to test store elsewhere ? Actually what we seen here, is that there's a big interaction between the hardware (level of bios and method of applying) and the Suse patches. The most funny is that the "buggy" 11.2 stock kernel is working nicely for the last days here. and as Alexander mention it, every mobo tested by users are working with 11.1 or other distributions kernel, or vanilia kernel.
The builds on Factory seem to be hung up on dependencies. Just grab a kernel from http://download.opensuse.org/repositories/Kernel:/HEAD/openSUSE_11.2/ instead
Created attachment 334827 [details] dmesg with lastest 2.6.32 kernel-debug (working) Hi Jeff, I think you find the needed info. If not just change the status. I will provide you (next attachement the hwinfo & lspci )
Created attachment 334828 [details] hwinfo full. Sorry to send this in gz ( limit of upload )
Created attachment 334831 [details] lspci MA-790FX-DQ6 As I've previously said. With the manipulation done in C30, (reseting hardly bios) the pc work perfectly also with 2.6.31-5 from the install et update of normal 11.2. I've tested also to start an install 11.1 at it work also. Don't hesitate to ask if you need something else.
I have different hardware than the other mentioned above. The problem still persists with the Vanilla-Kernel. I already tried the latest official Kernel-Release from the official opensuse-repositories today and the problem is still there. For me the problem happenes 100% of my tries (I did not try it too often, though) I add my hwinfo for further information. As others mentioned above already the problem came with opensuse 11.2 and I had no problems with older opensuse versions nor with other distributions on the same hardware.
Created attachment 334850 [details] Complete hwinfo from my system
*** Bug 558163 has been marked as a duplicate of this bug. ***
Created attachment 335058 [details] boot.msg when booting with the SUSE kernel with ACPI on Although my system boots with the SUSE kernel after BIOS update, I am concerned of some scary traceback messages in boot.msg that might be related to our problem, e.g. <3>[ 0.219145] BUG: scheduling while atomic: swapper/0/0x10000002 <4>[ 0.219152] Modules linked in: <4>[ 0.219155] Pid: 0, comm: swapper Not tainted 2.6.31.8-0.1-desktop #1 <4>[ 0.219157] Call Trace: <4>[ 0.219164] [<ffffffff81011a19>] try_stack_unwind+0x189/0x1b0 <4>[ 0.219168] [<ffffffff8101025d>] dump_trace+0xad/0x3a0 <4>[ 0.219177] [<ffffffff81011524>] show_trace_log_lvl+0x64/0x90 <4>[ 0.219181] [<ffffffff81011573>] show_trace+0x23/0x40 <4>[ 0.219185] [<ffffffff815524d2>] dump_stack+0x81/0x9e <4>[ 0.219190] [<ffffffff81056ef2>] __schedule_bug+0x92/0xa0 <4>[ 0.219194] [<ffffffff8155340f>] thread_return+0x2a7/0x3c8 <4>[ 0.219199] [<ffffffff81060d88>] __cond_resched+0x38/0x80 <4>[ 0.219203] [<ffffffff815536cd>] _cond_resched+0x4d/0x60 <4>[ 0.219212] [<ffffffff81100dfa>] generic_perform_write+0x15a/0x220 <4>[ 0.219217] [<ffffffff81100f50>] generic_file_buffered_write+0x90/0x160 <4>[ 0.219221] [<ffffffff8110170f>] __generic_file_aio_write_nolock+0x28f/0x4d0 <4>[ 0.219226] [<ffffffff81101aaf>] generic_file_aio_write+0x7f/0x110 <4>[ 0.219230] [<ffffffff8114bb12>] do_sync_write+0x102/0x160 <4>[ 0.219234] [<ffffffff8114be98>] vfs_write+0xd8/0x1c0 <4>[ 0.219238] [<ffffffff8114c82b>] sys_write+0x5b/0xa0 <4>[ 0.219243] [<ffffffff819d5034>] do_copy+0x3e/0xd7 <4>[ 0.219252] [<ffffffff819d49c9>] flush_buffer+0x8c/0xc8 <4>[ 0.219256] [<ffffffff81a01140>] gunzip+0x425/0x500 <4>[ 0.219261] [<ffffffff819d4ed1>] unpack_to_rootfs+0x2f6/0x41b <4>[ 0.219265] [<ffffffff819d59e3>] populate_rootfs+0x72/0x13a <4>[ 0.219269] [<ffffffff819d3639>] start_kernel+0x3bf/0x3e6 <4>[ 0.219274] [<ffffffff819d268d>] x86_64_start_reservations+0x134/0x14f <4>[ 0.219278] [<ffffffff819d2803>] x86_64_start_kernel+0x15b/0x17e <6>[ 0.221594] Freeing initrd memory: 6812k freed <6>[ 0.225253] ACPI: Core revision 20090521 <3>[ 0.233365] BUG: scheduling while atomic: swapper/0/0x10000002 <4>[ 0.233372] Modules linked in: <4>[ 0.233376] Pid: 0, comm: swapper Not tainted 2.6.31.8-0.1-desktop #1 <4>[ 0.233378] Call Trace: <4>[ 0.233393] [<ffffffff81011a19>] try_stack_unwind+0x189/0x1b0 <4>[ 0.233398] [<ffffffff8101025d>] dump_trace+0xad/0x3a0 <4>[ 0.233403] [<ffffffff81011524>] show_trace_log_lvl+0x64/0x90 <4>[ 0.233408] [<ffffffff81011573>] show_trace+0x23/0x40 <4>[ 0.233413] [<ffffffff815524d2>] dump_stack+0x81/0x9e <4>[ 0.233419] [<ffffffff81056ef2>] __schedule_bug+0x92/0xa0 <4>[ 0.233424] [<ffffffff8155340f>] thread_return+0x2a7/0x3c8 <4>[ 0.233430] [<ffffffff81060d88>] __cond_resched+0x38/0x80 <4>[ 0.233434] [<ffffffff815536cd>] _cond_resched+0x4d/0x60 <4>[ 0.233440] [<ffffffff8130544e>] acpi_ps_complete_op+0x2c2/0x2eb <4>[ 0.233445] [<ffffffff81305979>] acpi_ps_parse_loop+0x371/0x3d0 <4>[ 0.233450] [<ffffffff81304666>] acpi_ps_parse_aml+0x119/0x404 <4>[ 0.233455] [<ffffffff81303218>] acpi_ns_one_complete_parse+0x144/0x175 <4>[ 0.233460] [<ffffffff813032a3>] acpi_ns_parse_table+0x5a/0xb3 <4>[ 0.233464] [<ffffffff812fede3>] acpi_ns_load_table+0x87/0x138 <4>[ 0.233469] [<ffffffff813084ee>] acpi_tb_load_namespace+0x80/0x163 <4>[ 0.233474] [<ffffffff813085ee>] acpi_load_tables+0x1d/0x5c <4>[ 0.233480] [<ffffffff81a07186>] acpi_early_init+0x85/0x12e <4>[ 0.233486] [<ffffffff819d363e>] start_kernel+0x3c4/0x3e6 <4>[ 0.233491] [<ffffffff819d268d>] x86_64_start_reservations+0x134/0x14f <4>[ 0.233496] [<ffffffff819d2803>] x86_64_start_kernel+0x15b/0x17e <6>[ 0.241050] Setting APIC routing to flat see all messages in the full boot.msg attached
Revisiting this one. The traces in comment #50 are the infamous acpi table scheduling atomic report that there are lot of dupes for. WRT comment #47, you mention that you don't have success with kernel-vanilla but yet other distros are working properly. Any idea what patch they're using to fix it? Generally when hardware breaks when it worked on a previous version it's due to enabling some new feature that may not be properly implemented on that hardware. Given that switching the bios around fixes the issue, that points to bad hardware that we're not working around properly. There are a number of pci quirk tables that are used to work around issues like that. I'm going to pass this one off to an ACPI expert.
(In reply to comment #51) > WRT comment #47, you mention that you don't have success with kernel-vanilla > but yet other distros are working properly. Any idea what patch they're using > to fix it? I am sorry, I have probably been misunderstood. I was testing different distros before I used openSuse. All of them had older kernels than current 11.2. As my tests were over a year ago. I tested Fedora, Kubuntu, Mandriva and openSolaris. I don't remember the versions, though (But as I said over 1 year old). > Generally when hardware breaks when it worked on a previous version it's due to > enabling some new feature that may not be properly implemented on that > hardware. Given that switching the bios around fixes the issue, that points to > bad hardware that we're not working around properly. That might be true, but when system doesn't boot up after a (supported) kernel update, when the old system was running without problems, it is not acceptable and should NEVER happen.
Any chance this will be fixed in one of the upcoming kernel updates? Many motherboards/pcs can not use powersaving features because of this problem which appears only in the SuSE kernel.
*** Bug 353612 has been marked as a duplicate of this bug. ***
I spent last weekend installing 11.2 into old VIA-based system and got the same problem - kernel load stops at 98%. Then I tested it on Athlon system - the same result. I didn't see this bug, so I experimented and found: 1. older boards with ATA (EIDE) don't boot, newer one works. 2. 11.2 copied to USB flash drive with help of Unetbootin - WORKS on the same older boards. So, reading this, I guess - DVD image should have kernel located in first 500MB, because a kernel boot process may use BIOS help to read kernel image and that may don't support well 4.2GB DVDs. See this for details - http://homepage.ntlworld.com./jonathan.deboynepollard/FGA/os2-disc-and-volume-size-limits.html
Additional info - 3. NET installation boots fine on any my boards.
kernel _is_ located within the first 500mb. otoh, (older) bioses have lots of bugs when it comes to cdrom reading.
openSUSE 11.2 is now in security/corruption maintenance mode. Please reopen if you are able to reproduce with openSUSE 11.3 or openSUSE Factory.
openSUSE 11.4 - the system doesn't turn off, but in 11.3 works fine. CPU: AMD Phenom(tm) II X6 1075T Processor (6 cpu cores) (version 2.20.00) MB: MSI 870U-G55, Bios ver. 25.0 /var/log/messages: Mar 17 20:21:08 Heldar kernel: [ 15.034317] powernow-k8: Found 1 AMD Phenom(tm) II X6 1075T Processor (6 cpu cores) (version 2.20.00) Mar 17 20:21:08 Heldar kernel: [ 15.034326] powernow-k8: Core Performance Boosting: on. Mar 17 20:21:08 Heldar kernel: [ 15.034336] [Firmware Bug]: powernow-k8: No compatible ACPI _PSS objects found. Mar 17 20:21:08 Heldar kernel: [ 15.034337] [Firmware Bug]: powernow-k8: Try again with latest BIOS. Workaround - enable Cool'n'Quiet technology.
@(In reply to comment #60) > openSUSE 11.4 - the system doesn't turn off, but in 11.3 works fine. This is not the same issue. Please open a new bug. Re-closing.
Please review bug 548108. I will reopen same. FBD
Wrong Bug Please forgive me
Please correct status