Bug 818846

Summary: reboot again and again after update the latest version
Product: [Fedora] Fedora Reporter: Zhouping Liu <zliu>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 17CC: gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, nobody+295318
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-07 06:20:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
the error log from screen none

Description Zhouping Liu 2012-05-04 07:39:06 UTC 
Description of problem:

after I updated f17 today, and reboot system, then system reboot constantly.
once I login the X windows, the system will reboot after about 2 minutes.

also there was one time, system failed when booting, and I caught the screen by my mobile phone, I will attached the screen.

at last, I switched an old kernel version, it can start up, and I checked /var/log/messages, found some error log, which maybe were related to the version:
****** cat /var/log/messages ******
...
May  4 11:21:04 ZhoupingLiu gdm-welcome][913]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
May  4 11:21:04 ZhoupingLiu gdm-welcome][913]: GLib-GObject-CRITICAL: g_object_unref: assertion `G_IS_OBJECT (object)' failed
...

Version-Release number of selected component (if applicable):
kernel version: 3.3.4-3.fc17.x86_64

How reproducible:


Steps to Reproduce:
1. # yum -y update --skip-broken (skipped samba4 updating)
2. # reboot

Actual results:
the system auto-reboot constantly 

Expected results:
system can boot up without the above issue.
Comment 1 Zhouping Liu 2012-05-04 07:41:59 UTC 
Created attachment 582046 [details]
the error log from screen
Comment 2 Josh Boyer 2012-05-04 11:28:17 UTC 
If you boot into runlevel 3, does it auto-reboot?

The error picture isn't an error, it's just telling you it's relabling the filesystem.  You can temporarily avoid that by adding 'enforcing=0' to the grub command line.  If you do, you might want to remove rhgb and quiet and see if there is any more information available.

The gdm-welcome error is a problem in GDM, not the kernel.  So far, there's nothing here to really point to a kernel problem aside from the rebooting.  Does /var/log/messages show anything else?
Comment 3 Zhouping Liu 2012-05-07 06:20:32 UTC 
hi, Josh

the issue was fixed, it's a mistake, after several checking, I found it's my personal wrong configure which caused the issue, after I corrected the configure, the issue was gone, so I'll closed the bug. thanks for your tracking.

Thanks,
Zhouping