Bugzilla – Bug 540482
chvt hangs & restart fails to restart computer [please read comment #120 for potential fix]
Last modified: 2016-04-15 09:53:26 UTC
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20090909 SUSE/3.5.3-1.1 Firefox/3.5.3 Running factory update from earlier today (Sept 18), however this has been a problem for the last couple of months (say around Milestone 4) and has been persistent across fresh installs. Clicking "Computer -> Shutdown -> Restart", only restarts the gnome desktop rather than restarting the computer. Note that this also applies to the equivalent command of "Shutdown". Generally speaking the second or third attempt to "restart" will actually restart the computer. Running "shutdown -r now" from the commandline as root works all the time, so I imagine that there is some sort of problem higher up in the stack. This is why I filed this problem against "GNOME". I haven't got a clue as which log I should be posting, so please let me know. Reproducible: Always
Both Shutdown and Restart buttons as well on Gnome in M7 as previous M6 returns just to the gdm login menu. Even not additional Shutdown from that menu does help. But I've experienced that entering Ctrl+Alt+F1 on the login menu level trigger the Shutdown/Restart process to fullfill. And as root in a terminal or console both 'init 0' and 'reboot' do work ok.
Meet the same problem, improve the priority.
It definitely isn't a problem in KDE4. I know you filed against Gnome, but I just thought I'd confirm that it is a Gnome problem for you.
I experience the same issue on a fresh install of the M7 DVD and the M7 Live CD. Restart and shutdown just restart GDM. Anecdotally, I believe it usually takes two tries for the computer to restart/shutdown.
Do you have polkit and polkit-gnome installed?
Yes, for my comment #1: ~> rpm -qa | grep polkit polkit-0.94-2.2.i586 libpolkit0-0.94-2.2.i586 polkit-gnome-0.94-1.4.i586 polkit-default-privs-0.1_200908281259-1.1.noarch
Hrm. That's the same issue Magnus experienced, then. I was never able to reproduce it. Are you using some encrypted partition by any chance? (note that it's important to distinguish the before M6 case to what we have now: M6 was missing some packages)
I have effectively the same versions of software installed as mentioned in comment 6, and do not have an encrypted partition. And to be precise, it takes exactly two attempts to get the machine to restart.
Created attachment 320325 [details] Screen shot of 'yast2 disk' on 11.2 M7 x86_64
Created attachment 320327 [details] Screen shot of 'yast2 disk' on 11.2 M7 i586
Comments to my screenshot comment #9 and #10 above: Neither I use any encrypted partitions. What I will remark as especial might be: Both my current machines x86_64 and i586 has been continued as multiboot configurations setup, with several openSUSE 11.1/11.2 and SLED 11 root partitions and lately with common /home, beside W2k or XP. All SUSE partitions use ext3 file systems, except the latest 11.2 root which is formatted ext4.
I tried to shutdown openSUSE 11.2 M8 in Gnome and was just auto-logged in again. After trying again, it somewhat worked and the system shut down. But still, it doesn't feel stable.
Is there not a log file or something that we can post here that could help identify the problem.
I'm happy to tell that after upgrading to 11.2 M8, Shutdown and Restart again works ok on both my test machines, x86_64 and i586. Tested from both the Gnome desktop and from the GDM login menu. (So far I haven't tested with Autologin enabled)
I'm seriously thinking this is just a side-effect of bug 532090 (gdm autologging you back on logout). I'm building gdm with a patch for this...
I was too fast in my conclusion. The same issue came back on both my machines after some shutdowns and Restarts.
Could people experiencing this bug please try the gdm package from GNOME:Factory? Unfortunately, it doesn't build right now (the build service seems to rebuild the package in a loop :/), so you'd have to build it locally. Or you can try the gdm packages for i586 that I put on http://tmp.vuntz.net/misc/.
(forgot to put NEEDINFO)
*** Bug 543699 has been marked as a duplicate of this bug. ***
The packages gdm-2.28.0-1.i586.rpm and gdm-lang-2.28.0-1.noarch.rpm installed ok The third gdm package resulted in a conflict # rpm -Uvh gdm-branding-upstream-2.28.0-1.i586.rpm Forbereder... ########################################### [100%] file /etc/gdm/custom.conf from install of gdm-branding-upstream-2.28.0-1.i586 conflicts with file from package gdm-branding-openSUSE-11.1-1.60.noarch But sorry, still the same shutdown/restart issue ......
Terje: just to clarify... You're logged in with your user, you click "Restart". Then what happens? Does it log you out to gdm? Or nothing at all?
When I click shutdown or restart, it auto log in again but when I do it 2nd time then shutdown. Using lenovo Sl500
Hrm, it shouldn't auto login again if you're using my gdm package. Can you paste here the beginning of "rpm -q --changelog gdm"?
File was not recognized was the message displayed while trying to install your gdm rpm. I'm using X86-64 bit.
(In reply to comment #24) > File was not recognized was the message displayed while trying to install your > gdm rpm. I'm using X86-64 bit. As I said, my packages are for i586 ;-) If you have a build service account, you can get the x86_64 packages from https://build.opensuse.org/package/show?package=gdm&project=GNOME%3AFactory (they're not yet published, since GNOME:Factory needs to be completely built for that).
(In reply to comment #21) > Terje: just to clarify... You're logged in with your user, you click "Restart". > Then what happens? Does it log you out to gdm? Or nothing at all? It logs me out to the gdm menu in almost all cases. But it looks remarkable random or unstable. In a few cases Restart has worked correct as it should. But in most cases I get the gdm login menu. Before that I see the broadcast from root telling the system is going down for reboot or halt. Well, my K7 i586 is slow, but just waiting for a pause or timeout at the gdm login menu doesn't seem to help. What is remarkable now, is that while I enter my password to re-login again from the menu, then the reboot process often continue correctly and fullfill. As I mentioned before, I could also trigger a similar behaviour by entering Ctrl+Alt+F1 after the gdm login menu was displayed after doing a Restart or Shutdown from the desktop. (Just to have it mentioned here in case it should have some relevance: I will post a bug report on issue with the Gnome panel. When launching applications or minimizing windows for them, these icons don't appear on the Gnome panel as they should. Looks like this part or field of the panel is hidden or the icons disappear)
I'd had this on 11.1/G:S:2.26 and 11.1/G:F but since the latest update of G:F it seems to be sorted for me, reboot and shutdown are behaving as they ought.
Actually, I take back comment 27 - just tested on my laptop and this behaviour persists. Seems that if the bootsplash screen is drawn before X/GDM restarts, it reboots/shuts down normally, if not, you have to drop to a text console and it then gets drawn.
*** Bug 544145 has been marked as a duplicate of this bug. ***
So, seems as if the shutdown hangs on "chvt 1" in /etc/init.d/rc Adding a "sleep 20" prior to chvt makes the shutdown work This is probably due to GDM/X restarting so we need to see why GDM doesn't exit, but restarts.
Created attachment 320945 [details] gdm --debug Log file from starting gdm --debug in init level 3. GDM seems to shutdown just fine, but immediately starts up again
(In reply to comment #30) > This is probably due to GDM/X restarting so we need to see why GDM doesn't > exit, but restarts. But why would GDM not restart a greeter? What GDM sees is that the user has logged out, and so it starts a new greeter. GDM will stop with "rcxdm stop", during the shutdown. Looking at the ConsoleKit code, when gnome-session tells ConsoleKit to restart, ConsoleKit will just call ck-system-restart which simply calls "shutdown -r now". So, to me, it's a bug somewhere else that shutdown blocks because GDM is doing something. Werner, can you take a quick look at this bug and give your opinion?
I can see that, when choosing shutdown/restart, it switches to the console to say that it is sending the other processes a kill. I'm not sure which console this is though. Comment#30 will also explain why it works the second time as the chvt will continue as soon as it goes to tty1
I can confirm that shutdown, restart and logout don´t work correctly in M8. Reproducible on real hardware, in VMware, from LiveCD and from installed system also. Logout : system always logs in back Restart: system is logs in back the first time, the second time is restarted Shutdown: system is logs in back the first time, the second time is halted.
Just to make it clear: the "it logs me back" issue should be fixed with the gdm from GNOME:Factory. The issue we're focusing on now is what we have in comments #28 to #33.
*** Bug 535487 has been marked as a duplicate of this bug. ***
(In reply to comment #32) Does this also happen using an other Display Manager? Does this happen also without installed ConsoleKit? IMHO there is a job which blocks the normal shutdown procedure (in history this had happend with both ConsoleKit and also with GDM/GNOME).
Here are some things to test for people who can reproduce it: + log in GNOME, open a xterm and type "sudo /sbin/shutdown -r now; killall gnome-session". Do you have the same issue? + log in icewm, open a xterm and type "sudo /sbin/shutdown -r now; killall icewm". Do you have the same issue? + edit /etc/sysconfig/displaymanager and set the DISPLAYMANAGER to xdm. Type "rcxdm restart" (warning, it will kill your X if you're doing that in X). Then log in from xdm, open a xterm and type "sudo /sbin/shutdown -r now; killall gnome-session". Do you have the same issue? If you have the same issue with one of the above, then ConsoleKit has nothing to do there. If you have the same issue with the third case, then it's also not a gdm issue at all. (my guess is that it's really just a race, though)
This happen with the default installation,but not every time.
(In reply to comment #38) > Here are some things to test for people who can reproduce it: > > + log in GNOME, open a xterm and type "sudo /sbin/shutdown -r now; killall > gnome-session". Do you have the same issue? > > + log in icewm, open a xterm and type "sudo /sbin/shutdown -r now; killall > icewm". Do you have the same issue? > > + edit /etc/sysconfig/displaymanager and set the DISPLAYMANAGER to xdm. Type > "rcxdm restart" (warning, it will kill your X if you're doing that in X). Then > log in from xdm, open a xterm and type "sudo /sbin/shutdown -r now; killall > gnome-session". Do you have the same issue? > No, i don't have the issues in all cases. The system is always restarted.
Simple command "sudo /sbin/shutdown -r now" works also.
(In reply to comment #41) This may work in your case, nevertheless Wing Shun has trouble with it. Now lets see what is the difference between your both systems. @ Wing Shun : Pleased could your try sudo /sbin/shutdown -r now several times to see if it happens with this (regular) unix command. Please also switch off splash screen in /etc/sysconfig/bootsplash (SPLASH="no") and if the systems hangs around instead of rebooting switch to the virtual console 1 (Ctrl+Alt+F1) and have a look which boot scripts are on the last few lines. You may also disable the parallel boot in /etc/sysconfig/boot (RUN_PARALLEL="no") which enables you to see the real last script which is hanging around. If the ``sudo /sbin/shutdown -r now'' is also hanging you try to add the line killproc -TERM /usr/sbin/console-kit-daemon before killproc -p $DBUS_DAEMON_PID -TERM $DBUS_DAEMON_BIN in /etc/init.d/dbus.
The "sudo /sbin/shutdown -r now"command normally restarts my system.
Hmmm ... your system hangs only if you're using the shutdown functionality of the desktop? Please try to disable the splash and have a look with Ctrl+Alt-F1 at which script this happens .. if any. If there is no message about a runlevel switch to runlevel 6 we see (as also report by Ted in the initial description of this bug) a problem in the desktop or its configuration.
I disabled the splash and run "sudo /sbin/shutdown -r now"command again，it still normally restarts,and how can I to saving the information from the text mode for you?
Please try to shutdown your system out from the desktop and not with the direct system command. This because I'd like to see why the way clicking "Computer -> Shutdown -> Restart" does not work. The log file you mean is simply the old boot log /var/log/boot.omsg after reboot ... or if reboot hasn't worked the current boot log file /var/log/boot.msg.
Werner, When shutdown is issued from the Desktop, X/GDM is restarted. This interferes with chvt in the /etc/init.d/rc script. chvt tried to switch to tty1, but can't since X/GDM restarts at the same time, so the command "hangs" there. This is why hitting ctrl+alt+F1 actually makes the machine shutdown (ie, the chvt command "succeeds" and the rest of the rc script continues) No other init scripts are involved at this stage. This also explains why the second shutdown works, since X/GDM now wants to restart again, we briefly end up on tty1, making chvt succeed so that the rest of the rc shutdown script can continue.
Normally on runlevel 0, 1, and 6 the Display Manager like xdm and kdm do not restart. Why does GDM restart here? And beside by this why does chvt block ... AFAIK the X-Server tries to open the next free virtual console which is IMHO not vt1 ... this indicates that GDM tries to set the virtual console for the X-Server to the current virtual console ... whereas xdm uses vt7 (see /etc/X11/xdm/Xservers).
From gdm.changes: Thu Dec 3 01:26:30 CST 2008 - hpj@novell.com - Replace gdm-2.21.5-vt7-temporary-hack.patch with gdm-vt-allocation-hack.patch. The new patch doesn't hardcode gdm to VT7, but instead scans for a free VT starting with VT7 (bug #434598).
AFAICS from the patch the scan start from vt7 which is not vt1. Therefore it should not block here.
Just to make sure, I'll compile a version of GDM without this patch and see how it works.
Removing the patch does not make a difference
Then within gdm_server_resolve_command_line() there is an argument which specifies the virtual console ... this is a guess as read from the last few lines from the patch: @@ -310,6 +398,11 @@ gdm_server_resolve_command_line (GdmServer *server, if (vtarg != NULL && ! gotvtarg) { argv[len++] = g_strdup (vtarg); + } else if (!query_in_arglist && !gotvtarg) { + gint vtnum = find_first_probably_free_vt (); + + if (vtnum > 0) + argv [len++] = g_strdup_printf ("vt%d", vtnum); } argv[len++] = NULL; ...
klogd 1.4.1, log source = ksyslog started. <6>[ 0.000000] Initializing cgroup subsys cpuset <6>[ 0.000000] Initializing cgroup subsys cpu <5>[ 0.000000] Linux version 2.6.31-10-default (geeko@buildhost) (gcc version 4.4.1 [gcc-4_4-branch revision 150839] (SUSE Linux) ) #1 SMP 2009-09-29 11:18:23 +0200 <6>[ 0.000000] KERNEL supported cpus: <6>[ 0.000000] Intel GenuineIntel <6>[ 0.000000] AMD AuthenticAMD <6>[ 0.000000] NSC Geode by NSC <6>[ 0.000000] Cyrix CyrixInstead <6>[ 0.000000] Centaur CentaurHauls <6>[ 0.000000] Transmeta GenuineTMx86 <6>[ 0.000000] Transmeta TransmetaCPU <6>[ 0.000000] UMC UMC UMC UMC <6>[ 0.000000] BIOS-provided physical RAM map: <6>[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable) <6>[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved) <6>[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved) <6>[ 0.000000] BIOS-e820: 0000000000100000 - 000000001bff0000 (usable) <6>[ 0.000000] BIOS-e820: 000000001bff0000 - 000000001bff8000 (ACPI data) <6>[ 0.000000] BIOS-e820: 000000001bff8000 - 000000001c000000 (ACPI NVS) <6>[ 0.000000] BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved) <6>[ 0.000000] BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved) <6>[ 0.000000] BIOS-e820: 00000000ffee0000 - 00000000fff00000 (reserved) <6>[ 0.000000] BIOS-e820: 00000000fffc0000 - 0000000100000000 (reserved) <6>[ 0.000000] DMI 2.3 present. <5>[ 0.000000] AMI BIOS detected: BIOS may corrupt low RAM, working around it. <7>[ 0.000000] e820 update range: 0000000000000000 - 0000000000010000 (usable) ==> (reserved) <6>[ 0.000000] last_pfn = 0x1bff0 max_arch_pfn = 0x100000 <7>[ 0.000000] MTRR default type: uncachable <7>[ 0.000000] MTRR fixed ranges enabled: <7>[ 0.000000] 00000-9FFFF write-back <7>[ 0.000000] A0000-BFFFF uncachable <7>[ 0.000000] C0000-DFFFF write-protect <7>[ 0.000000] E0000-EFFFF uncachable <7>[ 0.000000] F0000-FFFFF write-protect <7>[ 0.000000] MTRR variable ranges enabled: <7>[ 0.000000] 0 base 000000000 mask FF0000000 write-back <7>[ 0.000000] 1 base 010000000 mask FF8000000 write-back <7>[ 0.000000] 2 base 018000000 mask FFC000000 write-back <7>[ 0.000000] 3 disabled <7>[ 0.000000] 4 disabled <7>[ 0.000000] 5 disabled <7>[ 0.000000] 6 disabled <7>[ 0.000000] 7 base 0D0000000 mask FFC000000 write-combining <6>[ 0.000000] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 <6>[ 0.000000] Scanning 0 areas for low memory corruption <6>[ 0.000000] modified physical RAM map: <6>[ 0.000000] modified: 0000000000000000 - 0000000000010000 (reserved) <6>[ 0.000000] modified: 0000000000010000 - 000000000009fc00 (usable) <6>[ 0.000000] modified: 000000000009fc00 - 00000000000a0000 (reserved) <6>[ 0.000000] modified: 00000000000f0000 - 0000000000100000 (reserved) <6>[ 0.000000] modified: 0000000000100000 - 000000001bff0000 (usable) <6>[ 0.000000] modified: 000000001bff0000 - 000000001bff8000 (ACPI data) <6>[ 0.000000] modified: 000000001bff8000 - 000000001c000000 (ACPI NVS) <6>[ 0.000000] modified: 00000000fec00000 - 00000000fec01000 (reserved) <6>[ 0.000000] modified: 00000000fee00000 - 00000000fee01000 (reserved) <6>[ 0.000000] modified: 00000000ffee0000 - 00000000fff00000 (reserved) <6>[ 0.000000] modified: 00000000fffc0000 - 0000000100000000 (reserved) <7>[ 0.000000] initial memory mapped : 0 - 00c00000 <6>[ 0.000000] init_memory_mapping: 0000000000000000-000000001bff0000 <7>[ 0.000000] 0000000000 - 0000400000 page 4k <7>[ 0.000000] 0000400000 - 001bc00000 page 2M <7>[ 0.000000] 001bc00000 - 001bff0000 page 4k <7>[ 0.000000] kernel direct mapping tables up to 1bff0000 @ 10000-16000 <6>[ 0.000000] RAMDISK: 1b886000 - 1bfdf27c <4>[ 0.000000] ACPI: RSDP 000faa40 00014 (v00 AMI ) <4>[ 0.000000] ACPI: RSDT 1bff0000 0002C (v01 AMIINT SiS740XX 00001000 MSFT 0100000B) <4>[ 0.000000] ACPI: FACP 1bff0030 00081 (v01 AMIINT SiS740XX 00000011 MSFT 0100000B) <4>[ 0.000000] ACPI: DSDT 1bff0120 03300 (v01 SiS 746 00000100 INTL 02002024) <4>[ 0.000000] ACPI: FACS 1bff8000 00040 <4>[ 0.000000] ACPI: APIC 1bff00c0 0005A (v01 AMIINT SiS740XX 00001000 MSFT 0100000B) <7>[ 0.000000] ACPI: Local APIC address 0xfee00000 <5>[ 0.000000] 0MB HIGHMEM available. <5>[ 0.000000] 447MB LOWMEM available. <6>[ 0.000000] mapped low ram: 0 - 1bff0000 <6>[ 0.000000] low ram: 0 - 1bff0000 <6>[ 0.000000] node 0 low ram: 00000000 - 1bff0000 <6>[ 0.000000] node 0 bootmap 00012000 - 00015800 <6>[ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 001bff0000] <6>[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000] <6>[ 0.000000] #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000] <6>[ 0.000000] #2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000] <6>[ 0.000000] #3 [0000200000 - 0000a0a3a8] TEXT DATA BSS ==> [0000200000 - 0000a0a3a8] <6>[ 0.000000] #4 [001b886000 - 001bfdf27c] RAMDISK ==> [001b886000 - 001bfdf27c] <6>[ 0.000000] #5 [000009fc00 - 0000100000] BIOS reserved ==> [000009fc00 - 0000100000] <6>[ 0.000000] #6 [0000a0b000 - 0000a0e0c4] BRK ==> [0000a0b000 - 0000a0e0c4] <6>[ 0.000000] #7 [0000010000 - 0000012000] PGTABLE ==> [0000010000 - 0000012000] <6>[ 0.000000] #8 [0000012000 - 0000016000] BOOTMAP ==> [0000012000 - 0000016000] <6>[ 0.000000] found SMP MP-table at [c00fbc70] fbc70 <4>[ 0.000000] Zone PFN ranges: <4>[ 0.000000] DMA 0x00000010 -> 0x00001000 <4>[ 0.000000] Normal 0x00001000 -> 0x0001bff0 <4>[ 0.000000] HighMem 0x0001bff0 -> 0x0001bff0 <4>[ 0.000000] Movable zone start PFN for each node <4>[ 0.000000] early_node_map[2] active PFN ranges <4>[ 0.000000] 0: 0x00000010 -> 0x0000009f <4>[ 0.000000] 0: 0x00000100 -> 0x0001bff0 <7>[ 0.000000] On node 0 totalpages: 114559 <7>[ 0.000000] free_area_init_node: node 0, pgdat c0893020, node_mem_map c1000200 <7>[ 0.000000] DMA zone: 32 pages used for memmap <7>[ 0.000000] DMA zone: 0 pages reserved <7>[ 0.000000] DMA zone: 3951 pages, LIFO batch:0 <7>[ 0.000000] Normal zone: 864 pages used for memmap <7>[ 0.000000] Normal zone: 109712 pages, LIFO batch:31 <6>[ 0.000000] Using APIC driver default <6>[ 0.000000] ACPI: PM-Timer IO Port: 0x808 <7>[ 0.000000] ACPI: Local APIC address 0xfee00000 <6>[ 0.000000] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) <6>[ 0.000000] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) <6>[ 0.000000] ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0]) <6>[ 0.000000] IOAPIC[0]: apic_id 2, version 17, address 0xfec00000, GSI 0-23 <6>[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge) <6>[ 0.000000] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 low level) <7>[ 0.000000] ACPI: IRQ0 used by override. <7>[ 0.000000] ACPI: IRQ2 used by override. <7>[ 0.000000] ACPI: IRQ9 used by override. <6>[ 0.000000] Enabling APIC mode: Flat. Using 1 I/O APICs <6>[ 0.000000] Using ACPI (MADT) for SMP configuration information <6>[ 0.000000] SMP: Allowing 1 CPUs, 0 hotplug CPUs <7>[ 0.000000] nr_irqs_gsi: 24 <6>[ 0.000000] PM: Registered nosave memory: 000000000009f000 - 00000000000a0000 <6>[ 0.000000] PM: Registered nosave memory: 00000000000a0000 - 00000000000f0000 <6>[ 0.000000] PM: Registered nosave memory: 00000000000f0000 - 0000000000100000 <6>[ 0.000000] Allocating PCI resources starting at 1c000000 (gap: 1c000000:e2c00000) <6>[ 0.000000] NR_CPUS:32 nr_cpumask_bits:32 nr_cpu_ids:1 nr_node_ids:1 <6>[ 0.000000] PERCPU: Embedded 14 pages at c1382000, static data 33116 bytes <4>[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 113663 <5>[ 0.000000] Kernel command line: root=/dev/disk/by-id/ata-ST340016A_3HS62HN1-part1 resume=/dev/disk/by-id/ata-ST340016A_3HS62HN1-part5 splash=silent quiet vga=0x31a <6>[ 0.000000] bootsplash: silent mode. <4>[ 0.000000] PID hash table entries: 2048 (order: 11, 8192 bytes) <6>[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) <6>[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) <6>[ 0.000000] Enabling fast FPU save and restore... done. <6>[ 0.000000] Enabling unmasked SIMD FPU exception support... done. <6>[ 0.000000] Initializing CPU#0 <6>[ 0.000000] Initializing HighMem for node 0 (00000000:00000000) <6>[ 0.000000] Memory: 438244k/458688k available (4103k kernel code, 19852k reserved, 2674k data, 460k init, 0k highmem) <6>[ 0.000000] virtual kernel memory layout: <6>[ 0.000000] fixmap : 0xffd34000 - 0xfffff000 (2860 kB) <6>[ 0.000000] pkmap : 0xff400000 - 0xff800000 (4096 kB) <6>[ 0.000000] vmalloc : 0xdc7f0000 - 0xff3fe000 ( 556 MB) <6>[ 0.000000] lowmem : 0xc0000000 - 0xdbff0000 ( 447 MB) <6>[ 0.000000] .init : 0xc089f000 - 0xc0912000 ( 460 kB) <6>[ 0.000000] .data : 0xc0601d52 - 0xc089e728 (2674 kB) <6>[ 0.000000] .text : 0xc0200000 - 0xc0601d52 (4103 kB) <6>[ 0.000000] Checking if this processor honours the WP bit even in supervisor mode...Ok. <6>[ 0.000000] Hierarchical RCU implementation. <6>[ 0.000000] NR_IRQS:2304 nr_irqs:256 <4>[ 0.000000] Fast TSC calibration using PIT <4>[ 0.000000] Detected 1158.723 MHz processor. <4>[ 0.000132] Console: colour dummy device 80x25 <6>[ 0.000141] console [tty0] enabled <6>[ 0.000249] Calibrating delay loop (skipped), value calculated using timer frequency.. 2317.44 BogoMIPS (lpj=4634892) <4>[ 0.004932] kdb version 4.4 by Keith Owens, Scott Lurndal. Copyright SGI, All Rights Reserved <6>[ 0.005087] Security Framework initialized <6>[ 0.005147] AppArmor: AppArmor initialized <4>[ 0.005186] Mount-cache hash table entries: 512 <6>[ 0.005528] Initializing cgroup subsys ns <6>[ 0.005539] Initializing cgroup subsys cpuacct <6>[ 0.005549] Initializing cgroup subsys memory <6>[ 0.005564] Initializing cgroup subsys devices <6>[ 0.005570] Initializing cgroup subsys freezer <6>[ 0.005576] Initializing cgroup subsys net_cls <6>[ 0.005622] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) <6>[ 0.005629] CPU: L2 Cache: 256K (64 bytes/line) <6>[ 0.005640] mce: CPU supports 4 MCE banks <6>[ 0.005687] Performance Counters: AMD PMU driver. <6>[ 0.005714] ... version: 0 <6>[ 0.005718] ... bit width: 48 <6>[ 0.005722] ... generic counters: 4 <6>[ 0.005727] ... value mask: 0000ffffffffffff <6>[ 0.005731] ... max period: 00007fffffffffff <6>[ 0.005735] ... fixed-purpose counters: 0 <6>[ 0.005740] ... counter mask: 000000000000000f <6>[ 0.005758] Checking 'hlt' instruction... OK. <6>[ 0.020757] SMP alternatives: switching to UP code <6>[ 0.029784] Freeing SMP alternatives: 15k freed <6>[ 0.029846] ACPI: Core revision 20090521 <6>[ 0.043463] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 <6>[ 0.083161] CPU0: AMD Athlon(tm) XP stepping 02 <6>[ 0.084001] Brought up 1 CPUs <6>[ 0.084001] Total of 1 processors activated (2317.44 BogoMIPS). <7>[ 0.084001] CPU0 attaching NULL sched-domain. <6>[ 0.084001] devtmpfs: initialized <6>[ 0.084001] Booting paravirtualized kernel on bare hardware <6>[ 0.084001] regulator: core version 0.5 <4>[ 0.084001] Time: 2:50:40 Date: 10/09/09 <6>[ 0.084001] NET: Registered protocol family 16 <6>[ 0.084001] ACPI: bus type pci registered <6>[ 0.084760] PCI: PCI BIOS revision 2.10 entry at 0xfdb31, last bus=2 <6>[ 0.084766] PCI: Using configuration type 1 for base access <4>[ 0.086233] bio: create slab <bio-0> at 0 <7>[ 0.087677] ACPI: EC: Look up EC in DSDT <6>[ 0.099677] ACPI: Interpreter enabled <6>[ 0.099692] ACPI: (supports S0 S1 S4 S5) <6>[ 0.099746] ACPI: Using IOAPIC for interrupt routing <6>[ 0.108992] ACPI: Power Resource [URP1] (off) <6>[ 0.109066] ACPI: Power Resource [URP2] (off) <6>[ 0.109136] ACPI: Power Resource [FDDP] (off) <6>[ 0.109205] ACPI: Power Resource [LPTP] (off) <6>[ 0.109571] ACPI: No dock devices found. <6>[ 0.109893] ACPI: PCI Root Bridge [PCI0] (0000:00) <7>[ 0.110013] pci 0000:00:00.0: reg 10 32bit mmio: [0xd0000000-0xd3ffffff] <6>[ 0.110226] pci 0000:00:02.0: Enabling SiS 96x SMBus <7>[ 0.110300] pci 0000:00:02.1: reg 20 io port: [0xc00-0xc1f] <7>[ 0.110390] pci 0000:00:02.5: reg 20 io port: [0xff00-0xff0f] <7>[ 0.110467] pci 0000:00:02.7: reg 10 io port: [0xdc00-0xdcff] <7>[ 0.110480] pci 0000:00:02.7: reg 14 io port: [0xd800-0xd87f] <7>[ 0.110543] pci 0000:00:02.7: supports D1 D2 <6>[ 0.110549] pci 0000:00:02.7: PME# supported from D3hot D3cold <6>[ 0.110560] pci 0000:00:02.7: PME# disabled <7>[ 0.110602] pci 0000:00:03.0: reg 10 32bit mmio: [0xcfff9000-0xcfff9fff] <7>[ 0.110685] pci 0000:00:03.1: reg 10 32bit mmio: [0xcfffa000-0xcfffafff] <7>[ 0.110784] pci 0000:00:03.2: reg 10 32bit mmio: [0xcfffb000-0xcfffbfff] <6>[ 0.110852] pci 0000:00:03.2: PME# supported from D0 D3hot D3cold <6>[ 0.110860] pci 0000:00:03.2: PME# disabled <7>[ 0.110924] pci 0000:00:04.0: reg 10 io port: [0xd400-0xd4ff] <7>[ 0.110937] pci 0000:00:04.0: reg 14 32bit mmio: [0xcfff8000-0xcfff8fff] <7>[ 0.110977] pci 0000:00:04.0: reg 30 32bit mmio: [0xfffe0000-0xffffffff] <7>[ 0.111006] pci 0000:00:04.0: supports D1 D2 <6>[ 0.111011] pci 0000:00:04.0: PME# supported from D0 D1 D2 D3hot D3cold <6>[ 0.111020] pci 0000:00:04.0: PME# disabled <7>[ 0.111139] pci 0000:01:00.0: reg 10 32bit mmio: [0xc0000000-0xc7ffffff] <7>[ 0.111151] pci 0000:01:00.0: reg 14 32bit mmio: [0xcfee0000-0xcfefffff] <7>[ 0.111162] pci 0000:01:00.0: reg 18 io port: [0xbc00-0xbc7f] <7>[ 0.111212] pci 0000:01:00.0: supports D1 D2 <7>[ 0.111271] pci 0000:00:01.0: bridge io port: [0xb000-0xbfff] <7>[ 0.111280] pci 0000:00:01.0: bridge 32bit mmio: [0xcfd00000-0xcfefffff] <7>[ 0.111290] pci 0000:00:01.0: bridge 32bit mmio pref: [0xbfa00000-0xcfbfffff] <7>[ 0.111307] pci_bus 0000:00: on NUMA node 0 <7>[ 0.111318] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] <6>[ 0.133592] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 10 *11 12 14 15) <6>[ 0.133876] ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. <6>[ 0.134146] ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *10 11 12 14 15) <6>[ 0.134413] ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *10 11 12 14 15) <6>[ 0.134679] ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 *10 11 12 14 15) <6>[ 0.134956] ACPI: PCI Interrupt Link [LNKF] (IRQs *3 4 5 6 7 10 11 12 14 15) <6>[ 0.135240] ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. <6>[ 0.135506] ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 10 11 12 14 15) <5>[ 0.136029] SCSI subsystem initialized <6>[ 0.136376] usbcore: registered new interface driver usbfs <6>[ 0.136418] usbcore: registered new interface driver hub <6>[ 0.136507] usbcore: registered new device driver usb <6>[ 0.136641] PCI: Using ACPI for IRQ routing <6>[ 0.140398] AppArmor: AppArmor Filesystem Enabled <6>[ 0.140456] pnp: PnP ACPI init <6>[ 0.140513] ACPI: bus type pnp registered <6>[ 0.147018] pnp: PnP ACPI: found 12 devices <6>[ 0.147025] ACPI: ACPI bus type pnp unregistered <6>[ 0.147035] PnPBIOS: Disabled by ACPI PNP <6>[ 0.147070] system 00:01: ioport range 0x4d0-0x4d1 has been reserved <6>[ 0.147077] system 00:01: ioport range 0x295-0x296 has been reserved <6>[ 0.147085] system 00:01: ioport range 0x800-0x87f has been reserved <6>[ 0.147091] system 00:01: ioport range 0x880-0x8ff has been reserved <6>[ 0.147098] system 00:01: ioport range 0xc00-0xc1f has been reserved <6>[ 0.147107] system 00:01: iomem range 0xfee00000-0xfee00fff has been reserved <3>[ 0.182270] pci 0000:00:04.0: BAR 6: address space collision on of device [0xfffe0000-0xffffffff] <6>[ 0.182328] pci 0000:00:01.0: PCI bridge, secondary bus 0000:01 <6>[ 0.182337] pci 0000:00:01.0: IO window: 0xb000-0xbfff <6>[ 0.182351] pci 0000:00:01.0: MEM window: 0xcfd00000-0xcfefffff <6>[ 0.182361] pci 0000:00:01.0: PREFETCH window: 0xbfa00000-0xcfbfffff <7>[ 0.182390] pci_bus 0000:00: resource 0 io: [0x00-0xffff] <7>[ 0.182397] pci_bus 0000:00: resource 1 mem: [0x000000-0xffffffff] <7>[ 0.182403] pci_bus 0000:01: resource 0 io: [0xb000-0xbfff] <7>[ 0.182409] pci_bus 0000:01: resource 1 mem: [0xcfd00000-0xcfefffff] <7>[ 0.182415] pci_bus 0000:01: resource 2 pref mem [0xbfa00000-0xcfbfffff] <6>[ 0.182560] NET: Registered protocol family 2 <6>[ 0.182786] IP route cache hash table entries: 4096 (order: 2, 16384 bytes) <6>[ 0.183466] TCP established hash table entries: 16384 (order: 5, 131072 bytes) <6>[ 0.183868] TCP bind hash table entries: 16384 (order: 5, 131072 bytes) <6>[ 0.184326] TCP: Hash tables configured (established 16384 bind 16384) <6>[ 0.184334] TCP reno registered <6>[ 0.184610] NET: Registered protocol family 1 <6>[ 0.184803] Unpacking initramfs... <6>[ 0.546090] Freeing initrd memory: 7524k freed <6>[ 0.567933] Scanning for low memory corruption every 60 seconds <6>[ 0.568386] audit: initializing netlink socket (disabled) <5>[ 0.568459] type=2000 audit(1255056639.567:1): initialized <6>[ 0.582206] HugeTLB registered 4 MB page size, pre-allocated 0 pages <5>[ 0.582435] VFS: Disk quotas dquot_6.5.2 <4>[ 0.582509] Dquot-cache hash table entries: 1024 (order 0, 4096 bytes) <6>[ 0.582754] msgmni has been set to 217 <6>[ 0.582978] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 254) <6>[ 0.582987] io scheduler noop registered <6>[ 0.582992] io scheduler anticipatory registered <6>[ 0.582996] io scheduler deadline registered <6>[ 0.583015] io scheduler cfq registered (default) <7>[ 0.583269] pci 0000:01:00.0: Boot video device <4>[ 0.583465] pci-stub: invalid id string "" <6>[ 0.584249] vesafb: framebuffer at 0xc0000000, mapped to 0xdc880000, using 10240k, total 65472k <6>[ 0.584256] vesafb: mode is 1280x1024x16, linelength=2560, pages=2 <6>[ 0.584261] vesafb: protected mode interface info at c704:0000 <6>[ 0.584267] vesafb: pmi: set display start = c00c707a, set palette = c00c70d0 <6>[ 0.584272] vesafb: scrolling: redraw <6>[ 0.584280] vesafb: Truecolor: size=0:5:6:5, shift=0:11:5:0 <6>[ 0.585239] bootsplash 3.1.6-2004/03/31: looking for picture... <6>[ 0.629585] bootsplash: silentjpeg size 130564 bytes <7>[ 0.683989] Switched to high resolution mode on CPU 0 <6>[ 0.691792] bootsplash: ...found (1280x1024, 29083 bytes, v3). <4>[ 0.916415] Console: switching to colour frame buffer device 156x60 <6>[ 1.139652] fb0: VESA VGA frame buffer device <6>[ 1.139812] isapnp: Scanning for PnP cards... <6>[ 1.450118] isapnp: No Plug & Play device found <6>[ 1.453149] Non-volatile memory driver v1.3 <6>[ 1.453157] Linux agpgart interface v0.103 <6>[ 1.453219] Serial: 8250/16550 driver, 8 ports, IRQ sharing disabled <6>[ 1.453375] serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A <6>[ 1.454172] 00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A <6>[ 1.454506] Fixed MDIO Bus: probed <6>[ 1.454608] PNP: PS/2 Controller [PNP0303:PS2K,PNP0f03:PS2M] at 0x60,0x64 irq 1,12 <6>[ 1.455052] serio: i8042 KBD port at 0x60,0x64 irq 1 <6>[ 1.455073] serio: i8042 AUX port at 0x60,0x64 irq 12 <6>[ 1.455201] mice: PS/2 mouse device common for all mice <6>[ 1.455520] cpuidle: using governor ladder <6>[ 1.455527] cpuidle: using governor menu <6>[ 1.575700] TCP cubic registered <6>[ 1.575823] Using IPI No-Shortcut mode <7>[ 1.576089] PM: Checking image partition /dev/disk/by-id/ata-ST340016A_3HS62HN1-part5 <6>[ 1.589183] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 <7>[ 1.737028] psmouse serio1: ID: 10 00 64 <6>[ 2.469187] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input1 <7>[ 2.471835] PM: Resume from disk failed. <4>[ 2.471878] registered taskstats version 1 <4>[ 2.472104] Magic number: 13:695:813 <6>[ 2.472493] Freeing unused kernel memory: 460k freed <6>[ 2.473850] Write protecting the kernel text: 4104k <6>[ 2.473977] Write protecting the kernel read-only data: 2464k <7>[ 2.617221] libata version 3.00 loaded. <7>[ 2.621596] pata_sis 0000:00:02.5: version 0.5.2 <6>[ 2.622086] scsi0 : pata_sis <6>[ 2.622333] scsi1 : pata_sis <6>[ 2.624513] ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0xff00 irq 14 <6>[ 2.624521] ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0xff08 irq 15 <6>[ 2.796418] ata1.00: ATA-5: ST340016A, 3.19, max UDMA/100 <6>[ 2.796426] ata1.00: 78165360 sectors, multi 16: LBA <4>[ 2.796765] ata1.01: native sectors (19541087) is smaller than sectors (19541088) <6>[ 2.796774] ata1.01: ATA-5: ST310211A, 3.39, max UDMA/100 <6>[ 2.796780] ata1.01: 19541088 sectors, multi 16: LBA <6>[ 2.804426] ata1.00: configured for UDMA/100 <6>[ 2.820473] ata1.01: configured for UDMA/100 <5>[ 2.820823] scsi 0:0:0:0: Direct-Access ATA ST340016A 3.19 PQ: 0 ANSI: 5 <5>[ 2.821382] scsi 0:0:1:0: Direct-Access ATA ST310211A 3.39 PQ: 0 ANSI: 5 <5>[ 2.821704] sd 0:0:0:0: [sda] 78165360 512-byte logical blocks: (40.0 GB/37.2 GiB) <5>[ 2.821828] sd 0:0:0:0: [sda] Write Protect is off <7>[ 2.821836] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 <5>[ 2.821898] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA <6>[ 2.822226] sda: sda1 sda2 < sda5 <5>[ 2.844878] sd 0:0:1:0: [sdb] 19541088 512-byte logical blocks: (10.0 GB/9.31 GiB) <4>[ 2.851873] sda6 sda7 > <5>[ 2.867869] sd 0:0:0:0: [sda] Attached SCSI disk <5>[ 2.867946] sd 0:0:1:0: [sdb] Write Protect is off <7>[ 2.867954] sd 0:0:1:0: [sdb] Mode Sense: 00 3a 00 00 <5>[ 2.868040] sd 0:0:1:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA <6>[ 2.868352] sdb: sdb1 <5>[ 2.883645] sd 0:0:1:0: [sdb] Attached SCSI disk <6>[ 2.984316] ata2.00: ATAPI: PIONEER DVD-RW DVR-116, 1.04, max UDMA/66 <4>[ 2.984363] ata2.00: limited to UDMA/33 due to 40-wire cable <6>[ 3.000322] ata2.00: configured for UDMA/33 <5>[ 3.012825] scsi 1:0:0:0: CD-ROM PIONEER DVD-RW DVR-116 1.04 PQ: 0 ANSI: 5 <6>[ 3.052576] Uniform Multi-Platform E-IDE driver <6>[ 3.075059] processor LNXCPU:00: registered as cooling_device0 <6>[ 3.097126] udev: starting version 146 <6>[ 3.272504] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver <7>[ 3.272622] alloc irq_desc for 23 on node -1 <7>[ 3.272628] alloc kstat_irqs on node -1 <6>[ 3.272654] ehci_hcd 0000:00:03.2: PCI INT D -> GSI 23 (level, low) -> IRQ 23 <6>[ 3.272715] ehci_hcd 0000:00:03.2: EHCI Host Controller <6>[ 3.272819] ehci_hcd 0000:00:03.2: new USB bus registered, assigned bus number 1 <7>[ 3.272897] ehci_hcd 0000:00:03.2: cache line size of 64 is not supported <6>[ 3.272940] ehci_hcd 0000:00:03.2: irq 23, io mem 0xcfffb000 <6>[ 3.351001] rtc_cmos 00:03: RTC can wake from S4 <6>[ 3.351236] rtc_cmos 00:03: rtc core: registered rtc_cmos as rtc0 <6>[ 3.351293] rtc0: alarms up to one year, 114 bytes nvram <6>[ 3.362464] ehci_hcd 0000:00:03.2: USB 2.0 started, EHCI 1.00 <6>[ 3.362606] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002 <6>[ 3.362614] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 <6>[ 3.362621] usb usb1: Product: EHCI Host Controller <6>[ 3.362626] usb usb1: Manufacturer: Linux 2.6.31-10-default ehci_hcd <6>[ 3.362631] usb usb1: SerialNumber: 0000:00:03.2 <6>[ 3.362892] usb usb1: configuration #1 chosen from 1 choice <6>[ 3.362984] hub 1-0:1.0: USB hub found <6>[ 3.363020] hub 1-0:1.0: 6 ports detected <6>[ 3.379283] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver <7>[ 3.379389] alloc irq_desc for 20 on node -1 <7>[ 3.379396] alloc kstat_irqs on node -1 <6>[ 3.379419] ohci_hcd 0000:00:03.0: PCI INT A -> GSI 20 (level, low) -> IRQ 20 <6>[ 3.379491] ohci_hcd 0000:00:03.0: OHCI Host Controller <6>[ 3.379546] ohci_hcd 0000:00:03.0: new USB bus registered, assigned bus number 2 <6>[ 3.379615] ohci_hcd 0000:00:03.0: irq 20, io mem 0xcfff9000 <6>[ 3.434498] usb usb2: New USB device found, idVendor=1d6b, idProduct=0001 <6>[ 3.434514] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 <6>[ 3.434522] usb usb2: Product: OHCI Host Controller <6>[ 3.434527] usb usb2: Manufacturer: Linux 2.6.31-10-default ohci_hcd <6>[ 3.434532] usb usb2: SerialNumber: 0000:00:03.0 <6>[ 3.434844] usb usb2: configuration #1 chosen from 1 choice <6>[ 3.434929] hub 2-0:1.0: USB hub found <6>[ 3.434965] hub 2-0:1.0: 3 ports detected <7>[ 3.435144] alloc irq_desc for 21 on node -1 <7>[ 3.435151] alloc kstat_irqs on node -1 <6>[ 3.435173] ohci_hcd 0000:00:03.1: PCI INT B -> GSI 21 (level, low) -> IRQ 21 <6>[ 3.435243] ohci_hcd 0000:00:03.1: OHCI Host Controller <6>[ 3.435286] ohci_hcd 0000:00:03.1: new USB bus registered, assigned bus number 3 <6>[ 3.435355] ohci_hcd 0000:00:03.1: irq 21, io mem 0xcfffa000 <6>[ 3.490107] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 <6>[ 3.490123] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 <6>[ 3.490130] usb usb3: Product: OHCI Host Controller <6>[ 3.490135] usb usb3: Manufacturer: Linux 2.6.31-10-default ohci_hcd <6>[ 3.490140] usb usb3: SerialNumber: 0000:00:03.1 <6>[ 3.490506] usb usb3: configuration #1 chosen from 1 choice <6>[ 3.490604] hub 3-0:1.0: USB hub found <6>[ 3.490641] hub 3-0:1.0: 3 ports detected <6>[ 3.672051] usb 1-2: new high speed USB device using ehci_hcd and address 2 <6>[ 3.804855] usb 1-2: New USB device found, idVendor=0781, idProduct=5530 <6>[ 3.804869] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 <6>[ 3.804876] usb 1-2: Product: SanDisk Cruzer <6>[ 3.804881] usb 1-2: Manufacturer: SanDisk <6>[ 3.804886] usb 1-2: SerialNumber: 22036109D1113E04 <6>[ 3.805214] usb 1-2: configuration #1 chosen from 1 choice <7>[ 5.692628] PM: Marking nosave pages: 000000000009f000 - 0000000000100000 <7>[ 5.692645] PM: Basic memory bitmaps created <7>[ 5.714656] PM: Basic memory bitmaps freed <6>[ 5.788499] PM: Starting manual resume from disk <7>[ 5.788514] PM: Resume from partition 8:5 <7>[ 5.788518] PM: Checking hibernation image. <7>[ 5.789202] PM: Resume from disk failed. <6>[ 6.181479] kjournald starting. Commit interval 15 seconds <6>[ 6.181734] EXT3 FS on sda1, internal journal <6>[ 6.181748] EXT3-fs: mounted filesystem with ordered data mode. <7>[ 8.168503] preloadtrace: systemtap: 0.9.9/0.142, base: dd441000, memory: 34312+77204+11080+13600 data+text+ctx+net, probes: 34 <6>[ 9.706594] udev: starting version 146 <6>[ 9.805654] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 <6>[ 9.805817] ACPI: Power Button [PWRF] <6>[ 9.805946] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3 <6>[ 9.806007] ACPI: Power Button [PWRB] <6>[ 9.855215] Floppy drive(s): fd0 is 1.44M <6>[ 9.976989] gameport: NS558 PnP Gameport is pnp00:0b/gameport0, io 0x200, speed 755kHz <6>[ 9.991542] agpgart-sis 0000:00:00.0: SiS chipset [1039/0741] <6>[ 9.999815] agpgart-sis 0000:00:00.0: AGP aperture is 64M @ 0xd0000000 <6>[ 10.001133] FDC 0 is a post-1991 82077 <6>[ 10.015255] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 <6>[ 10.021455] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 <5>[ 10.063236] sd 0:0:0:0: Attached scsi generic sg0 type 0 <5>[ 10.063325] sd 0:0:1:0: Attached scsi generic sg1 type 0 <5>[ 10.063400] scsi 1:0:0:0: Attached scsi generic sg2 type 5 <6>[ 10.078998] parport_pc 00:0a: reported by Plug and Play ACPI <6>[ 10.079132] parport0: PC-style at 0x378 (0x778), irq 7, dma 0 [PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA] <6>[ 10.138058] sis900.c: v1.08.10 Apr. 2 2006 <7>[ 10.138171] alloc irq_desc for 19 on node -1 <7>[ 10.138178] alloc kstat_irqs on node -1 <6>[ 10.138201] sis900 0000:00:04.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 <6>[ 10.139454] 0000:00:04.0: Realtek RTL8201 PHY transceiver found at address 1. <6>[ 10.151740] 0000:00:04.0: Using transceiver found at address 1 as default <6>[ 10.153164] eth0: SiS 900 PCI Fast Ethernet at 0xd400, IRQ 19, 00:13:8f:a1:cd:ea <6>[ 10.168643] input: PC Speaker as /devices/platform/pcspkr/input/input4 <6>[ 10.204404] sis96x_smbus 0000:00:02.1: SiS96x SMBus base address: 0x0c00 <3>[ 10.204421] ACPI: I/O resource 0000:00:02.1 [0xc00-0xc1f] conflicts with ACPI region SMRG [0xc00-0xc1f] <6>[ 10.205089] ACPI: Device needs an ACPI driver <4>[ 10.205110] sis96x_smbus: probe of 0000:00:02.1 failed with error -16 <4>[ 10.324685] sr0: scsi3-mmc drive: 40x/40x writer dvd-ram cd/rw xa/form2 cdda tray <6>[ 10.324703] Uniform CD-ROM driver Revision: 3.20 <7>[ 10.325012] sr 1:0:0:0: Attached scsi CD-ROM sr0 <6>[ 10.402155] Initializing USB Mass Storage driver... <6>[ 10.520347] ppdev: user-space parallel port driver <6>[ 10.607820] scsi2 : SCSI emulation for USB Mass Storage devices <6>[ 10.608584] usbcore: registered new interface driver usb-storage <6>[ 10.608599] USB Mass Storage support registered. <7>[ 10.614178] usb-storage: device found at 2 <7>[ 10.614188] usb-storage: waiting for device to settle before scanning <7>[ 10.682566] alloc irq_desc for 18 on node -1 <7>[ 10.682578] alloc kstat_irqs on node -1 <6>[ 10.682600] Intel ICH 0000:00:02.7: PCI INT C -> GSI 18 (level, low) -> IRQ 18 <6>[ 11.008045] intel8x0_measure_ac97_clock: measured 55370 usecs (2664 samples) <6>[ 11.008059] intel8x0: clocking to 48000 <5>[ 11.612842] scsi 2:0:0:0: Direct-Access SanDisk SanDisk Cruzer 8.02 PQ: 0 ANSI: 0 CCS <5>[ 11.613345] sd 2:0:0:0: Attached scsi generic sg3 type 0 <5>[ 11.615863] scsi 2:0:0:1: CD-ROM SanDisk SanDisk Cruzer 8.02 PQ: 0 ANSI: 0 <5>[ 11.617855] sd 2:0:0:0: [sdc] 31301631 512-byte logical blocks: (16.0 GB/14.9 GiB) <5>[ 11.623476] sd 2:0:0:0: [sdc] Write Protect is off <7>[ 11.623526] sd 2:0:0:0: [sdc] Mode Sense: 45 00 00 08 <3>[ 11.623534] sd 2:0:0:0: [sdc] Assuming drive cache: write through <4>[ 11.626039] sr1: scsi3-mmc drive: 48x/48x tray <7>[ 11.626397] sr 2:0:0:1: Attached scsi CD-ROM sr1 <5>[ 11.626590] sr 2:0:0:1: Attached scsi generic sg4 type 5 <7>[ 11.628864] usb-storage: device scan complete <3>[ 11.630295] sd 2:0:0:0: [sdc] Assuming drive cache: write through <6>[ 11.630760] sdc: sdc1 sdc2 <3>[ 11.634913] sd 2:0:0:0: [sdc] Assuming drive cache: write through <5>[ 11.635375] sd 2:0:0:0: [sdc] Attached SCSI removable disk <6>[ 14.213351] Adding 1188768k swap on /dev/sda5. Priority:-1 extents:1 across:1188768k <6>[ 15.148043] device-mapper: uevent: version 1.0.3 <6>[ 15.149710] device-mapper: ioctl: 4.15.0-ioctl (2009-04-01) initialised: dm-devel@redhat.com <6>[ 15.574937] loop: module loaded <6>[ 16.401124] fuse init (API version 7.12) Kernel logging (ksyslog) stopped. Kernel log daemon terminating.
(In reply to comment #54) This log file seems to be shorten, that is that the part of the blogd is missed. Are you using fastboot or quiet within the kernels command line (report output `cat /proc/cmdline').
I just using the Shutdown button to shutdown and restart the system,the restart failed ，then I copy the boot.msg pasted here.
Please report the output of cat /proc/cmdline ... then we'll see if blogd is disabled. This because after the two lines Kernel logging (ksyslog) stopped. Kernel log daemon terminating. there should be something like Boot logging started on /dev/char/../tty1(/dev/console) at Mon Oct 5 12:23:45 2009 and a lot of other messages done by the boot scripts.
# cat /proc/cmdline root=/dev/disk/by-id/ata-ST340016A_3HS62HN1-part1 resume=/dev/disk/by-id/ata-ST340016A_3HS62HN1-part5 splash=silent quiet vga=0x31a
Same issue here. Open suse 11.1 with Gnome 2.26. As described in Comment #47, Ctrl+Alt+F1 unlocks the shutdown sequence.
(In reply to comment #58) there we have it ... `quiet' simply cause /etc/init.d/boot and /etc/init.d/rc not to start the blogd and therefore we do not have the script messages included. Guess it included in the grub file /boot/grub/menu.lst to speed up the boot scripts. Nevertheless it takes away debugging purpose. Stephan? Who is responsible
(In reply to comment #58) there we have it ... `quiet' simply cause /etc/init.d/boot and /etc/init.d/rc not to start the blogd and therefore we do not have the script messages included. Guess it included in the grub file /boot/grub/menu.lst to speed up the boot scripts. Nevertheless it takes away debugging purpose. Stephan? Who is responsible for this?
no idea, who disabled blogd for quiet. But quiet will stay in the cmdline because it improves the bototime of the kernel a lot.
Maybe but as already told it takes away debugging boot scripts. But if ``quiet'' is really that important we could skipt the chvt in /etc/init.d/rc for the case of DO_QUIET=yes ... but, nevertheless, the GDM should never restart its display in case of a shutdown and should always use VT7 and higher not any other virtual console. --- /etc/init.d/rc +++ /etc/init.d/rc 2009-10-12 15:01:52.299429195 +0200 @@ -176,7 +176,7 @@ test "$TERM" = "linux" -o -z "$TERM" && TERM=vt102 elif test "${REDIRECT%[0-9]}" = "/dev/ttyS" ; then test "$TERM" = "linux" -o -z "$TERM" && TERM=vt102 -else +elif test "$DO_BLOGD" = yes ; then # VGA if test "$RUNLEVEL" = "0" -o "$RUNLEVEL" = "6" ; then case "$REDIRECT" in /dev/tty[1-9]*)
@Vincent: Why does gdm cause the X-Server to use the current VT instead of using VT7 and above?
(In reply to comment #64) > @Vincent: Why does gdm cause the X-Server to use the current VT instead > of using VT7 and above? Hrm, what do you mean? GDM is always using vt7 or above. See this line in gdm-vt-allocation-hack.patch: for (vtno = 7, vtmask = 1 << vtno; vtmask; vtno++, vtmask <<= 1) {
If it might be of interest, I've booted 11.2 M8 some times in Failsafe mode, and there both Shutdown and Restart has worked so far.
I have the same problem. GDM restarts itself, but when I press "Ctrl+Alt+F1", the restart/shutdown process is continuing correctly.
(In reply to comment #65) Sorry about the question: are you pretty sure? This because the chvt to VT1 in /etc/init.d/rc interferes with the X-Servers VT switch.
(In reply to comment #66) Failsafe moide means normally use an XTerm as session controlling process. That is that no X-Server will be (re)started on shutdown. The question is why GDM (re)start an X-Server in case of system shutdown. It should no do that as this not only may lock chvt but also takes system resources during reboot/halt procedure.
(In reply to comment #68) > (In reply to comment #65) > > Sorry about the question: are you pretty sure? This because > the chvt to VT1 in /etc/init.d/rc interferes with the X-Servers > VT switch. I've never seen gdm start on something lower than vt7. I've seen it on vt7, vt8, and maybe also vt9, but that's all. So my understanding of the code and my experience makes me pretty sure (let's say 95% sure), yes. (In reply to comment #69) > (In reply to comment #66) > > Failsafe moide means normally use an XTerm as session controlling > process. That is that no X-Server will be (re)started on shutdown. > The question is why GDM (re)start an X-Server in case of system > shutdown. It should no do that as this not only may lock chvt > but also takes system resources during reboot/halt procedure. Here's what's happening: + gnome-session tells ConsoleKit to reboot + ConsoleKit call "shutdown -r now" + gnome-session exits + gdm sees that the user session has ended and so restarts a new greeter So, yes, gdm restarts a new X server because it's not aware of what ConsoleKit did and I'm not sure ConsoleKit has any way to tell it about this. However, I still don't see why gdm has to be aware of this. I see how having it aware of this would make this work, but this feels like a workaround to me, since I imagine the issue could happen in other cases. As far as I know, there's no way to tell gdm to not restart. We could possibly look at not attempting a restart of the interface if runlevel is now 0 or 6, but that might again be racy since the runlevel could be changed after that...
(In reply to comment #67) > I have the same problem. > GDM restarts itself, but when I press "Ctrl+Alt+F1", the restart/shutdown > process is continuing correctly. I need this procedure on RC1, also.
It's fixed with RC1.Thanks!
(In reply to comment #72 and comment #71) For you the race seems to be avoided (but IMHO it is there and is waiting) ... for Mario it seems to stay around. (In reply to comment #70) IMHO it could be that ConsoleKit has a problem in the case that `chvt' tries to switch the virtual console 1 and within the same schedule time frame an X-Server starts on an other virtual console equal or greater than 7. @Stephan: IMHO this smells like a little show stopper 8~(
it's already marked as one.
*** Bug 548020 has been marked as a duplicate of this bug. ***
FWIW, if we need a workaround for this in gdm, I believe the right place for this would be gdm_static_display_finish() in daemon/gdm-static-display.c. Instead of starting to manage again, we could look at the current runlevel (with getutent()) and not managing if the runlevel is 0 or 6.
Created attachment 323035 [details] Untested patch This is a patch that implements my previous comment. I didn't test it, nor even compiled it. It'd be great if someone can make a test gdm package with it so that people who can reproduce the issue can check if it helps or not.
*** Bug 548077 has been marked as a duplicate of this bug. ***
please notice that when restart/halt wont work properly, is enought to manually switch to tty (ctrl+alt+f1) to start shutdown process.
Created attachment 323336 [details] Updated patch There was some error in the previous patch. Can people able to reproduce the issue test the package: http://tmp.vuntz.net/misc/gdm-2.28.0-1.i586.rpm I don't have a x86_64 version, but you can build one from home:vuntz:branches:GNOME:Factory/gdm
downloading now. btw on my VirtualBox installation it also affects other DM like slim or xdm.
(In reply to comment #81) > btw on my VirtualBox installation it also affects other DM like slim or xdm. Interesting. That makes the bug a more generic one, as I expected. But if the gdm workaround helps, I guess that's still a good first step...
(In reply to comment #82) That would second my guess that ConsoleKit may cause this. Holger?
(In reply to comment #79) maybe you missed comment #79 but if that helps, is enouht t switch to tty1. maybe the bug is "simply" there
(In reply to comment #84) The Ctrl+Alt+F1 workaround was experienced already in my first comment #1 :)
Wyh should I miss comment #79? This commend is the reason for my guess as ConsoleKit hold open an inotfy for all virtual consoles to check for (login) activities. This may interfere with the chvt of the /etc/init.d/rc script and the X-Server restart. E.g. there could be a race of using the VT_GETSTATE ioctl to determine the active virtual console in ConsoleKit and the other VT switches as ConsoleKit uses also the VT_WAITACTIVE ioctl and therefor may block upto the switch onto VT1 done by pressing Ctr+Alt-F1. But that's a gues of mine.
(In reply to comment #80) > Created an attachment (id=323336) [details] > Updated patch > > There was some error in the previous patch. Can people able to reproduce the > issue test the package: http://tmp.vuntz.net/misc/gdm-2.28.0-1.i586.rpm > > I don't have a x86_64 version, but you can build one from > home:vuntz:branches:GNOME:Factory/gdm Patch works for me. I'd like to see the patch in next release as a workaround. However, it should be design problem for gnome-session and gdm. When gnome-session exited, gdm had no idea about the exit reason, and restarted the greeter with X all the time. It's better that gdm quietly quit when user select restarting the computer.
(In reply to comment #87) > However, it should be design problem for gnome-session and gdm. > When gnome-session exited, gdm had no idea about the exit reason, and restarted > the greeter with X all the time. > It's better that gdm quietly quit when user select restarting the computer. This is actually what the patch implements ;-) The thing is that you can't really say it's a gnome-session/gdm communication issue, since it will also be a xfce/gdm issue, or kde/gdm issue, or... With this patch, if reboot/shutdown has been asked by the user, then gdm will notice it via the runlevel and we'll be (relatively) happy. FWIW, I forwarded the patch upstream since, even if it's a workaround, it can be useful to make shutdown/reboot a tiny bit faster: https://bugzilla.gnome.org/show_bug.cgi?id=599180
I've submitted the fix for gdm. Moving the bug to ConsoleKit.
(gah, assignee was reset, sorry for the spam)
as the gdm work around is submitted, we can clear the ship stopper I hope
*** Bug 549896 has been marked as a duplicate of this bug. ***
I've just installed factory build 0337. Shutdown and restart seem to be working properly. Finally :-)
It works under RC2 also.
Thank God (well, the developers actually). Can anyone else confirm this as working with RC2?
I can confirm that it worked for me with rc2 and the other day it didn't work :-(
I can confirm this bug exist with rc2.In my case, the shutdown failed once，the restart failed three times,restarting hang up twice.openSUSE-DVD-Build0339-i586.iso.Gnome desktop.
Can we get more details on what's failing now? Do you click shutdown/reboot in the user session or in gdm? If in the user session, is gdm starting again or do you go back to console?
At least for I'm talking about when trying to shut down from within Gnome/my session. And as said it sometimes works and sometimes I just end up in gdm while switching to console again actually shuts finally down.
Hrm, that would mean that you go back to gdm before the runlevel is changed... Not much I can do there from a gdm perspective :/ If Werner is right in comment #86 (about the race in ioctl), then I have no idea what can be done... It looks actually like a bug to me that chvt can hang...
I just click shutdown/reboot in the user session.Sometimes the shutdown and restart failed,and back to the login dialog.By default I was setting automatic login.
on my netbook (dup from rc1 to rc2) always ask root password to halt/reboot/hybernate/suspend... (it's the usual consolekit pop-up) that can be related... i don't know if that problem comes out from the "dup"
Ok, I'm on opensuse 11.2 gnome, when I ask to shutdown, sometimes It shutdowns, others times it does like log out.
(In reply to comment #104) > Ok, > > I'm on opensuse 11.2 gnome, when I ask to shutdown, sometimes It shutdowns, > others times it does like log out. I can confirm this bug exist with openSUSE-11.2-DVD-i586.iso Gnome desktop.Sometimes when I press shutdown It back to the login dialog
I found something a gdm patch that could explain the issue, but it's hard to tell without testing. Can people who are able to reproduce this bug reliably install the gdm package from home:vuntz:11.2-testing and see if this still happens? Note that you will have to reboot once before it takes effect (so that gdm is restarted), so ignore the first reboot after the installation :-)
(In reply to comment #106) > > Can people who are able to reproduce this bug reliably install the gdm package > from home:vuntz:11.2-testing > Yes, but can you add the full path, please? (I did't find the above mentioned)
It's a standard build service projects :-) It ends up in http://download.opensuse.org/repositories/home://vuntz://11.2-testing/openSUSE_11.2/
*** Bug 560352 has been marked as a duplicate of this bug. ***
i586 ---- I installed the gdm-2.28.0-2.5.1.i586.rpm. Have tested about 12-15 times total. most restarts and fewer shutdowns, and have got 3 unsuccessful cases which resulted in just logout. The first unsuccessful case was after the first shutdown. I also tried to install gdm-branding-upstream-2.28.0-2.5.1.i586.rpm, but got the following error: # rpm -Uvh gdm-branding-upstream-2.28.0-2.5.1.i586.rpm warning: gdm-branding-upstream-2.28.0-2.5.1.i586.rpm: Header V3 DSA signature: NOKEY, key ID c4762ded Preparing... ########################################### [100%] file /etc/gdm/custom.conf from install of gdm-branding-upstream-2.28.0-2.5.1.i586 conflicts with file from package gdm-branding-openSUSE-11.1-2.1.noarch Notice: I use a common /home and therefore common Desktop for openSUSE 11.2 and 11.1 in dualboot. May this disturbe something? Is it possible to install the new gdm-branding package yet? x86_64 ------ I've installed also the gdm-2.28.0-2.5.1.x86:64.rpm. So far I haven't run into the same issue on my 64bit laptop after a handful restart/shutdown tests. On this machine I have common /home and Desktop for multiboot of openSUSE 11.1, 11.2, 11.2edu and SLED11.
Thanks for the test! Note that you don't need the branding package, so no need to install it. So, all in all, it's still a win even if it looks like there are a few cases where this still doesn't work?
I would say, no change for me. After the 11.2 release or later updates, the unsuccesful restart/shutdown from Gnome have occured no and then, not each time.
Sorry, a typo: It should be 'now and then'
I installed the x86-64 "testing" gdm package http://download.opensuse.org/repositories/home://vuntz://11.2-testing/openSUSE_11.2/ and I can confirm that this package has fixed the shut down issue only, I still cannot restart my machine as gdm diverts me to the login screen!
I was able to reproduce this here, finally. With some ssh debugging, I can confirm that the reboot/shutdown process is blocked by chvt not exiting. chvt itself is blocked on this line: if (ioctl(fd,VT_WAITACTIVE,num)) { (which is really the last thing it does before exiting) Looking at the code, it's indeed racy: it does a VT_ACTIVATE to num, and then the VT_WAITACTIVE for num. However, nothing guarantees that another VT_ACTIVATE is sent by another process before the VT_WAITACTIVE... Looking around, there seems to be various issues with doing this. Some people are using the patch at [1] to work around the issue -- the wait is simulated in the user space. The suspend people also implemented a similar workaround in s2ram [2]. And Debian worked around the issue in their splashy script instead of doing it in chvt [3]. Does anybody know if it would be acceptable to add a patch like [1] in our kbd package? This would also imply changing sysvinit to make sure the call to chvt uses the user space wait. [1] http://www.brontes3d.com/opensource/dist/v1.2/overlay/sys-apps/kbd/files/kbd-1.12-chvt-userwait.patch [2] http://thread.gmane.org/gmane.linux.kernel.suspend.devel/7117/focus=7119 [3] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=504389
Michal is probably the right person for my question in the last comment. Michal: we have a bug caused by chvt hanging forever, and blocking the reboot/shutdown process; see my previous comment for some analysis. There's a possible workaround by patching the kbd package, but I have no idea if this is acceptable.
Implementing a timeout makes sense IMO. I'll have a closer look and add it to our package. I'll also ask Alexey if he wants to merge the patch upstream.
*** Bug 561281 has been marked as a duplicate of this bug. ***
How do you install the 2 patches in comment 115?
(In reply to comment #119) > How do you install the 2 patches in comment 115? There's a kbd package in home:vuntz:11.2-testing with the mentioned patch, but you'll also need to change /etc/rc.d/rc to use "chvt --userwait" instead of "chvt". Note that this is only for testing, and I have no idea if this is what should get submitted for an update -- Michal would know.
Same issue here, only with one of my two laptops. Works fine with a Thinkpad T61 (64 bits), not with a T30 (32 bits). Both were freshly installed.
After https://bugzilla.novell.com/show_bug.cgi?id=558250#c6 I installed Gnome and I found three problems after it. One of them is the present one: When I choose to shutdown the system from the gnome menu it logs me out but doesn't shutdown the system. So, I have to shutdown my system from the login screen menu. However, once, the system didnot shutdown but kill the Xserver only. I logged in as root and order from bash init 0, but the system didnot shutdown but halted and I had to press the power button till the PC shutdown. I work with SuSE 11.2 Final (its Gnome official release), and, although I want it to be corrected, I am not a Gnome user, and after installing Gnome I have problems with my audio device, etc. So I think this issues are not mere cosmetic but profound. That is the reason I want to share with you this experience, thus I could help. I attach my hardware information an my installed packages.
Created attachment 333612 [details] hardware info
Created attachment 333614 [details] packages installed
same problem here (gdm OR kdm), shutdown or restart under gnome take me back to the login screen also (hope that's related), the only way i can hibernate my asus x51rl laptop is with a root pm-hibernate terminal call, and sometimes(~50%) when it resumes, it autolog me directly which is quit serious (security-wise) all in all the gnome desktop does feel very shaky,again i hope it's all related to this bug
There is something new from 2 weeks. It click on shutdown It came back to login screen I push shutdown button (hardware) not on the screen ! I click on shutdown (screen) Before it was allways shutdown, now It blocks sometime on a black screen with : broadcast message sent by root at (time)
(In reply to comment #117) > Implementing a timeout makes sense IMO. I'll have a closer look and add it to > our package. I'll also ask Alexey if he wants to merge the patch upstream. Michal: is this something we could release as a maintenance update for 11.2? A lot of people are hit by this :/ I have a kbd package ready in home:vuntz:11.2-testing, fwiw. We would also need an update to aaa_base to change /etc/rc.d/rc.
*** Bug 569897 has been marked as a duplicate of this bug. ***
(sorry for the noise, now it should be correctly assigned)
So what't the status here? Would Vincent's kbd package fix the issue?
*** Bug 557961 has been marked as a duplicate of this bug. ***
I'm experiencing the same problem. When I choose shut down or reboot and I get to the login screen. If I try to switch to a terminal at that point by hitting ctrl-alt-f1, then shutdown proceeds as expected.
(In reply to comment #131) > *** Bug 557961 has been marked as a duplicate of this bug. *** Why is my bug report tagged as RESOLVED when it isn't? Perhaps a better status should be applied? Also from the thread it seems this issue has been going around for some time now. I have installed GNOME:Factory and it is still the same.
I have also still the same issue. I run 11.2 with all updates and some community repos added.
(In reply to comment #133) > (In reply to comment #131) > > *** Bug 557961 has been marked as a duplicate of this bug. *** > > Why is my bug report tagged as RESOLVED when it isn't? Perhaps a better status > should be applied? Because we're tracking the issue in this bug. Your bug was closed as duplicate, not fixed. > Also from the thread it seems this issue has been going around for some time > now. I have installed GNOME:Factory and it is still the same. Please read the last few coments in this bug. This is an issue in kbd and aaa_base, not in packages from GNOME.
*** Bug 572672 has been marked as a duplicate of this bug. ***
So what can be done? This bug is so embarrassing! I can live with it but I recently installed to someone begining with computer : how could I explain to this person that in 2010 this OS is not able to restart a computer? For now I am hiding it thanks to suspend, but can't do it forever.
Please read comment #120.
Confirmed, the kbd package from Vincent's OBS repo works fine. I also added the chvt hack mentioned in #120.
I am new maintainer of kbd and I do not know the package yet, but I talked with Michal about it and he thinks that the patch is OK - so it is also OK for me.
(In reply to comment #140) > I am new maintainer of kbd and I do not know the package yet, but I talked with > Michal about it and he thinks that the patch is OK - so it is also OK for me. So will you push an online update for 11.2? :-)
I have the same problem. Pressing the "Shut Down" or "Restart" button does not perform shutdown or reboot respectively. It brings me back to login screen. Shutdown from there works in 50% of the cases. Computer freezes if I try to login back to GNOME desktop. Operating System: openSUSE 11.2 freshly installed, default configuration Hardware Configuration: HP Compaq DC7100, Intel Pentium 4 Processor 521, Intel 915G Express, D-Link DWL-510 AirPlus G Facts: I installation performed from openSUSE 11.2 DVD. Complete installation, not an upgrade. Installation DVD checked OK. I installed openSUSE 11.2 several times. The problem is 100% reproducible. Booting in failsafe mode does not get rid of the problem. Booting to runlevel 3 => login as root => startx. Shutdown works properly. Booting to runlevel 3 => login as user => startx. Shutdown brings a pop-up window with following message: ---------------------------------------------------------------------------- System policy prevents stopping the system An application is attempting to perform an action that requires privileges. Authentication as the super user is required to perform this action. Password for root:[ ] Details Action: org.freedesktop.consolekit.system.stop ----------------------------------------------------------------------------
Accidental I changed the status of this bug report. Please can someone set it back to "NEED INFO" Sorry
I set back the status to NEEDINFO due to the comment 143
(fixing NEEDINFO so that it's set to the right person)
set correct needinfo to opensuse maintenance. +1 for an update
yes, we should do an update +1
The SWAMPID for this issue is 30806. Please submit the patch and patchinfo file using this ID. (https://swamp.suse.de/webswamp/wf/30806)
Be so kind and submit the fixed sources and a patchinfo.
Seriously, can we expect 11.2 to process reboot correctly some day or are we waiting for 11.3 ??? It is going to be 6 months since it has been unfixed and it is both very annoying and embarrassing.
thats why we now started the update process. Holger? This is waiting for your submission.
Actually, this should probably be submitted by Anna. At least for the chvt part -- I'm not sure who would update the aaa_base part.
OK, I am going to submit your patch for 11.2 right away. As for aaa_base part, maybe we could ask Rudi who is the right person for it.
in home:oertel:branches:openSUSE:11.2/aaa_base, whenever you are ready.
i submitted a patchinfo that updates kbd,aaa_base This is the complete package list, right?
(In reply to comment #156) > This is the complete package list, right? Yes, AFAIK.
what about Factory ?
*** Bug 559049 has been marked as a duplicate of this bug. ***
both fixes are in factory now.
Marcus, is the update OK, can I close as fixed?
Update released for: aaa_base, aaa_base-debuginfo, aaa_base-debugsource, kbd, kbd-debuginfo, kbd-debugsource Products: openSUSE 11.2 (debug, i586, x86_64)
waited for 1 week in update-test and seems to be fine , so i released it just now. thanks!
This is an autogenerated message for OBS integration: This bug (540482) was mentioned in https://build.opensuse.org/request/show/22756 Factory / gdm https://build.opensuse.org/request/show/32043 11.2:Test / kbd