Bugzilla – Bug 121891
System freezes on login
Last modified: 2005-10-25 14:04:26 UTC
I installed openSuSE 10.0 on my machine, and it only started successfully, when I started just after the installation. But after I made a restart, it didn't show the graphical log-in screen. only console was avalible, and on the first try, it froze, when I pressed enter after the login name, on the second try, I could write the password too, but after it wrote "Have fun...", it froze. It wrote an error while starting the firewall, but I couldn't read it. If you send me a reiserfs-reader for windows, I could send a log file. I don't know, if it important, but I installed an i386 version on my Pentium4 machine, but my machine supports 64-bit processing, the installer warned me, that I have a 64-bit system too. And a note, I had Fedora core 4 too on this system, and after I updated it to the 2.6.13 kernel, it wrote many errors, and the smp kernel didn't start, I could only run the default kernel, and wrote errors on starting the system-logger.
Created attachment 52046 [details] /var/log/messages file I can start the system in safe mode, and started the X with startx command successfully, and I send the /var/log/messages file.
Which openSUSE are you using? The SUSE LINUX 10 box, or the free download version SUSE LINUX 10.1 Alpha 1. This because you have choosen `customer'. For this you should provide a customer number. Beside this it seems to be a hardware problem, therefore this is not a blocker. There are many systems out there including the systems under my desk which work flawless. Please report the _exact_ mainbord with the _exact_ BIOS revision together with the _exact_ CPU you are using with the mainboard.
I use the free download version of the opensuse, that's the released version, 10.0. I have an ABIT AA8-Duramax mainboard with BIOS version i925X-W83627-6A79FA19C-22, it's release date is 03/23/2005, and I have an Intel Pentium 4 630. Should I send any log file? I ask, because I downloaded the x86-64 version today, and I would try that, but if you need an other log file too, I keep the system, or tell me if you need any file, and I make a copy of them to an other partition.
Free download is not that what I'd like to call a customer. This is more for free developers. Beside this you're using a brand new mainboard with new CPU. The question is about the support of the current kernel and/or gcc.
Your system seems to have problems with ACPI cpufreq. It will likely work if you do chkconfig powersaved off and reboot. Probably the other problems follow from that. Missing _PPC looks like a buggy BIOS, but acpi cpufreq's fallback path for that case is broken. Venkatesh, do you agree? Oct 9 19:08:40 Flatroncomp kernel: IA-32 Microcode Update Driver v1.14 unregistered Oct 9 19:08:40 Flatroncomp kernel: ACPI-0304: *** Error: Looking up [_PPC] in namespace, AE_ALREADY_EXISTS Oct 9 19:08:40 Flatroncomp kernel: ACPI-0622: *** Warning: During name lookup/catalog, AE_ALREADY_EXISTS Oct 9 19:08:40 Flatroncomp kernel: ACPI-1174: *** Error: Method execution failed [\_PR_.CPU1._PDC] (Node dffd6e80), AE_ALREADY_EXISTS Oct 9 19:08:40 Flatroncomp kernel: powernow: This module only works with AMD K7 CPUs Oct 9 19:08:40 Flatroncomp kernel: acpi-cpufreq: CPU0 - ACPI performance management activated. Oct 9 19:08:40 Flatroncomp kernel: ACPI-0304: *** Error: Looking up [_PPC] in namespace, AE_ALREADY_EXISTS Oct 9 19:08:40 Flatroncomp kernel: ACPI-0622: *** Warning: During name lookup/catalog, AE_ALREADY_EXISTS Oct 9 19:08:40 Flatroncomp kernel: ACPI-1174: *** Error: Method execution failed [\_PR_.CPU1._PDC] (Node dffd6e80), AE_ALREADY_EXISTS Oct 9 19:08:40 Flatroncomp kernel: acpi-cpufreq: CPU1 - ACPI performance management activated. Oct 9 19:08:40 Flatroncomp kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000001 Oct 9 19:08:40 Flatroncomp kernel: printing eip: Oct 9 19:08:40 Flatroncomp kernel: c01b2f1f Oct 9 19:08:40 Flatroncomp kernel: *pde = 00000000 Oct 9 19:08:40 Flatroncomp kernel: Oops: 0000 [#1] Oct 9 19:08:40 Flatroncomp kernel: SMP Oct 9 19:08:40 Flatroncomp kernel: Modules linked in: acpi_cpufreq speedstep_lib freq_table snd_pcm_oss snd_mixer_oss snd_seq snd_seq_device button battery ac edd ip6t_REJECT usbhid ipt_REJ ECT ipt_state ohci1394 ieee1394 r8169 i2c_i801 i2c_core generic ide_core ehci_hcd snd_hda_intel iptable_mangle snd_hda_codec uhci_hcd hw_random usbcore shpchp pci_hotplug snd_pcm snd_timer s nd soundcore snd_page_alloc iptable_nat iptable_filter ip6table_mangle ip_conntrack ip_tables ip6table_filter ip6_tables ipv6 parport_pc lp parport nls_iso8859_1 nls_cp437 vfat fat nls_utf8 ntfs dm_mod reiserfs fan thermal processor sr_mod cdrom sg ata_piix ahci libata sd_mod scsi_mod Oct 9 19:08:40 Flatroncomp kernel: CPU: 0 Oct 9 19:08:40 Flatroncomp kernel: EIP: 0060:[<c01b2f1f>] Not tainted VLI Oct 9 19:08:40 Flatroncomp kernel: EFLAGS: 00010246 (2.6.13-15-smp) Oct 9 19:08:40 Flatroncomp kernel: EIP is at create_dir+0x2f/0x190 Oct 9 19:08:40 Flatroncomp kernel: eax: 00000000 ebx: dea54300 ecx: ffffffff edx: dffc7b50 Oct 9 19:08:40 Flatroncomp kernel: esi: 00000001 edi: 00000001 ebp: df858e88 esp: dc241e34 Oct 9 19:08:40 Flatroncomp kernel: ds: 007b es: 007b ss: 0068 Oct 9 19:08:40 Flatroncomp kernel: Process modprobe (pid: 5337, threadinfo=dc240000 task=dbe77a60) Oct 9 19:08:40 Flatroncomp kernel: Stack: 00000001 00027100 00000000 dea54300 00000000 c045c174 00000001 c01b30ca Oct 9 19:08:40 Flatroncomp kernel: dc241e58 00000000 dea54300 c021bf5b dea54300 fffffffe c021c1b1 dea54300 Oct 9 19:08:40 Flatroncomp kernel: ffffffea c03bbacc c021c232 dc241e60 dea54280 dea54344 dea54280 dea54344 Oct 9 19:08:40 Flatroncomp kernel: Call Trace: Oct 9 19:08:40 Flatroncomp kernel: [<c01b30ca>] sysfs_create_dir+0x2a/0x70 Oct 9 19:08:40 Flatroncomp kernel: [<c021bf5b>] create_dir+0x1b/0x60 Oct 9 19:08:40 Flatroncomp kernel: [<c021c1b1>] kobject_add+0x71/0xd0 Oct 9 19:08:40 Flatroncomp kernel: [<c021c232>] kobject_register+0x22/0x70 Oct 9 19:08:40 Flatroncomp kernel: [<c02bc0f9>] cpufreq_add_dev+0x1b9/0x3c0 Oct 9 19:08:40 Flatroncomp kernel: [<c028a46a>] sysdev_driver_register+0x5a/0xa0 Oct 9 19:08:40 Flatroncomp kernel: [<c02bcf36>] cpufreq_register_driver+0x66/0x110 Oct 9 19:08:40 Flatroncomp kernel: [<c01438ec>] sys_init_module+0xcc/0x1e0 Oct 9 19:08:40 Flatroncomp kernel: [<c01042ab>] sysenter_past_esp+0x54/0x79 Oct 9 19:08:40 Flatroncomp kernel: Code: 5c 24 0c 89 c3 89 74 24 10 89 ce 89 6c 24 18 89 d5 89 7c 24 14 8b 52 0c f0 ff 4a 74 0f 88 be 0c 00 00 31 c0 b9 ff ff ff ff 89 f7 <f2> ae f7 d1 49 89 ea 89 f0 e8 63 d8 fc ff 8b 54 24 20 3d 18 fc Oct 9 19:08:40 Flatroncomp kernel: <6>r8169: eth0: link down
I don't exactly understand, what you say. You tell, that I must run the 'chkconfig powersaved off'? And you say, that maybe a buggy BIOS cause the error. I can update the BIOS with some click with flashmenu. Do I do that, or firstly, do what you told?
Update the BIOS first and see if that helps.
I updatesd BIOS, and now, the system booted well. Thanks for your help.
My happiness was early. After I made a reboot, that problem started again. Now, when I typed the username and password, I get the answer, that Init "1' respawning too fast, waining 5 seconds". I changed terminal with Crtl+Alt+F2, and there I logged in, and started X, and I got the answer there, that the powersaver daemon don't run, and there was a command to start that.
Please just ignore the powersaved message. Are you trying to log in on the X login or on the console? And please attach the logfiles again.
Now, the graphical log-in screen loaded, but when I entered the login data, it show the system load screen, not the desktop enviroment-load screen. and there was the text on the bottom left corner, press Esc for more information. I pressed, and the last messages were these: Oct 10 16:17:46 Flatroncomp init: Id "2" respawning too fast: disabled for 5 minutes Oct 10 16:17:46 Flatroncomp init: Id "3" respawning too fast: disabled for 5 minutes Oct 10 16:17:46 Flatroncomp init: Id "4" respawning too fast: disabled for 5 minutes Oct 10 16:17:46 Flatroncomp init: Id "5" respawning too fast: disabled for 5 minutes Oct 10 16:17:46 Flatroncomp init: Id "6" respawning too fast: disabled for 5 minutes Oct 10 16:17:46 Flatroncomp init: Id "1" respawning too fast: disabled for 5 minutes Oct 10 16:17:46 Flatroncomp init: no more processes left in this runlevel After that, I tried to change terminal, but the others show only the cursor.
Created attachment 52084 [details] new messages log file
I started the system in safe mode, and turned off the powersave daemon with the "chkconfig powersaved off" command, and now the system works well. As I wrote earlier, I downloaded the 64 bit version too, and I would try with that if it works. Do you need any more information, log file etc., or I could install the 64-bit version?
Don't need any further information. Still need to fix that buggy fallback path though.
I installed the 64 bit system, and it worked well for the first some start, but on the previourus reboot it froze on the Starting powersaved... .
You of course have to disable it on 64bit too.
I have already done it.
When will this problem solved? The solution will be a BIOS, or a kernel update?
*** This bug has been marked as a duplicate of 121839 ***