FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Redhat > Fedora Development

 
 
LinkBack Thread Tools
 
Old 06-14-2011, 10:02 AM
Lucas
 
Default system can't finish boot with systemd-28-4.fc16 and kernel-3.0-0.rc2.git0.2.fc16

My laptop can't finish boot with systemd-28-4.fc16 and kernel-3.0-0.rc2.git0.2.fc16 - the boot
process just stops at random points and CPU usage goes high.

systemd-28-3.fc16 and kernel-3.0-0.rc2.git0.2.fc16 - did not have this behavior.

The only possible way to boot is to add "selinux=0".
Especially for Daniel J Walsh, the addition of "enforcing=0" doesn't make any difference - boot stops.

Thanks.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 06-14-2011, 10:10 AM
Frank Murphy
 
Default system can't finish boot with systemd-28-4.fc16 and kernel-3.0-0.rc2.git0.2.fc16

On 14/06/11 11:02, Lucas wrote:
<snip>
> The only possible way to boot is to add "selinux=0".
> Especially for Daniel J Walsh, the addition of "enforcing=0" doesn't make any difference - boot stops.
>
> Thanks.

Last time I had similar problem, ended up:

rpm -e --nodeps selinux-policy selinux-policy-targeted
yum install selinux-policy selinux-policy-targeted
touch /.autorelabel; reboot

and then all was ok.
ymmv.


--
Regards,

Frank Murphy
UTF_8 Encoded
Friend of Fedora
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 06-14-2011, 10:37 AM
Lucas
 
Default system can't finish boot with systemd-28-4.fc16 and kernel-3.0-0.rc2.git0.2.fc16

On 06/14/2011 02:10 PM, Frank Murphy wrote:
> On 14/06/11 11:02, Lucas wrote:
> <snip>
>> The only possible way to boot is to add "selinux=0".
>> Especially for Daniel J Walsh, the addition of "enforcing=0" doesn't make any difference - boot stops.
>>
>> Thanks.
>
> Last time I had similar problem, ended up:
>
> rpm -e --nodeps selinux-policy selinux-policy-targeted
> yum install selinux-policy selinux-policy-targeted
> touch /.autorelabel; reboot
>
> and then all was ok.
> ymmv.
>
>

In my case relabeling did not help at all.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 06-14-2011, 05:32 PM
Lucas
 
Default system can't finish boot with systemd-28-4.fc16 and kernel-3.0-0.rc2.git0.2.fc16

On 06/14/2011 06:53 PM, Lennart Poettering wrote:
> On Tue, 14.06.11 18:48, Lucas (macachuto@gmail.com) wrote:
>
>>> Do you see any errors?
>>
>> Just checked it. Yum reinstalled selinux-policy-targeted, then relabeling, then reboot and process
>> stops on: Starting Remount Root FS. And nothing more, no errors, systemd hung.
>
> Boot with "systemd.log_level=debug systemd.log_target=kmsg
> rd_NO_PLYMOUTH plymouth.enable=0" on the kernel cmdline, and paste the
> last output generated output on the console somewhere, possibly take a
> photo of it, and upload it somewhere.
>
> Lennart
>

Did it, there is no any kind of debug messages on the screen.
Boot process just stops.

I updated to libselinux-2.0.102-6.fc16 and boot starts to go faster, but any way after few
successful times, it starts to stop again.

--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 06-14-2011, 05:57 PM
Lennart Poettering
 
Default system can't finish boot with systemd-28-4.fc16 and kernel-3.0-0.rc2.git0.2.fc16

On Tue, 14.06.11 21:32, Lucas (macachuto@gmail.com) wrote:

>
> On 06/14/2011 06:53 PM, Lennart Poettering wrote:
> > On Tue, 14.06.11 18:48, Lucas (macachuto@gmail.com) wrote:
> >
> >>> Do you see any errors?
> >>
> >> Just checked it. Yum reinstalled selinux-policy-targeted, then relabeling, then reboot and process
> >> stops on: Starting Remount Root FS. And nothing more, no errors, systemd hung.
> >
> > Boot with "systemd.log_level=debug systemd.log_target=kmsg
> > rd_NO_PLYMOUTH plymouth.enable=0" on the kernel cmdline, and paste the
> > last output generated output on the console somewhere, possibly take a
> > photo of it, and upload it somewhere.
> >
> > Lennart
> >
>
> Did it, there is no any kind of debug messages on the screen.

Did you also remove "quiet" and "rhgb" from the kernel cmdline? If you
leave that in all output will not be visible.

Lennart

--
Lennart Poettering - Red Hat, Inc.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 06-14-2011, 06:06 PM
Lucas
 
Default system can't finish boot with systemd-28-4.fc16 and kernel-3.0-0.rc2.git0.2.fc16

On 06/14/2011 09:57 PM, Lennart Poettering wrote:
> On Tue, 14.06.11 21:32, Lucas (macachuto@gmail.com) wrote:
>
>>
>> On 06/14/2011 06:53 PM, Lennart Poettering wrote:
>>> On Tue, 14.06.11 18:48, Lucas (macachuto@gmail.com) wrote:
>>>
>>>>> Do you see any errors?
>>>>
>>>> Just checked it. Yum reinstalled selinux-policy-targeted, then relabeling, then reboot and process
>>>> stops on: Starting Remount Root FS. And nothing more, no errors, systemd hung.
>>>
>>> Boot with "systemd.log_level=debug systemd.log_target=kmsg
>>> rd_NO_PLYMOUTH plymouth.enable=0" on the kernel cmdline, and paste the
>>> last output generated output on the console somewhere, possibly take a
>>> photo of it, and upload it somewhere.
>>>
>>> Lennart
>>>
>>
>> Did it, there is no any kind of debug messages on the screen.
>
> Did you also remove "quiet" and "rhgb" from the kernel cmdline? If you
> leave that in all output will not be visible.
>
> Lennart
>

Actually I never use them ("quiet" and "rhgb"), I prefer to see what is going on, and that is why I
know where the boot stops. There is no any debug or error messages.

May be I know what is going on. May be I did something.

I will let you know latter.

Thanks
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 06-14-2011, 06:25 PM
Matthew Miller
 
Default system can't finish boot with systemd-28-4.fc16 and kernel-3.0-0.rc2.git0.2.fc16

On Tue, Jun 14, 2011 at 06:48:43PM +0400, Lucas wrote:
> Just checked it. Yum reinstalled selinux-policy-targeted, then relabeling,
> then reboot and process stops on: Starting Remount Root FS. And nothing
> more, no errors, systemd hung.

Are you sure it's not doing an fsck? (There's an open bug for that.)

--
Matthew Miller <mattdm@mattdm.org>
Senior Systems Architect -- Instructional & Research Computing Services
Harvard School of Engineering & Applied Sciences
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 06-14-2011, 06:57 PM
Nicolas Mailhot
 
Default system can't finish boot with systemd-28-4.fc16 and kernel-3.0-0.rc2.git0.2.fc16

Le mardi 14 juin 2011 à 22:06 +0400, Lucas a écrit :

> May be I know what is going on. May be I did something.

FYI I have the same problem on my box. Was waiting for fixed 3.0 kernel
packages to report a bug. I suspect some kernel/systemd mismatch


--
Nicolas Mailhot



--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 06-14-2011, 07:03 PM
Lucas
 
Default system can't finish boot with systemd-28-4.fc16 and kernel-3.0-0.rc2.git0.2.fc16

I checked it again - it is not me.
Boot stops at random points - for example last time it stops at:
"Configure read-only root support"

So it can't even relabel FS, because it happens mush farther.

But option "selinux=0" solves this problem.


Thanks.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 
Old 06-14-2011, 07:16 PM
Jerry James
 
Default system can't finish boot with systemd-28-4.fc16 and kernel-3.0-0.rc2.git0.2.fc16

On Tue, Jun 14, 2011 at 12:25 PM, Matthew Miller <mattdm@mattdm.org> wrote:
> Are you sure it's not doing an fsck? (There's an open bug for that.)

I'm having the same problem with an i686 Rawhide virtual machine
(using KVM, on a Fedora 15 x86_64 host). The last few lines I see
before the hang are these:

Started udev Kernel Device Manager.
Starting Stdio Syslog Bridge...
Started Stdio Syslog Bridge.
Started udev Coldplug all Devices.
Starting udev Wait for Complete Device Initialization...
[ 9.542951] EXT4-fs (dm-1): re-mounted. Opts: (null)
Started Remount API VFS.
Started Remount Root FS.
Started Apply Kernel Variables.
Starting File System Quota Check...
Starting Configure read-only root support...

At that point output stops for awhile. The "CPU usage" graph on
virt-manager jumps up to about 25% to 30% (eyeballing it), and the
"Disk I/O" graph drops to zero. If I leave it like that for awhile to
see if anything else will happen, I eventually start seeing messages
about CPU stalls.

Just in case it is relevant, earlier in the boot, I see this:
[ 2.540079] ------------[ cut here ]------------
[ 2.541048] WARNING: at arch/x86/mm/highmem_32.c:81
__kunmap_atomic+0x64/0xbd()
[ 2.542788] Hardware name: Bochs
[ 2.543587] Modules linked in:
[ 2.544668] Pid: 123, comm: udevd Not tainted
3.0-0.rc2.git0.1.fc16.i686.PAE #1
[ 2.546240] Call Trace:
[ 2.547040] [<c0855051>] ? printk+0x2d/0x2f
[ 2.547852] [<c0443638>] warn_slowpath_common+0x7c/0x91
[ 2.548750] [<c042d22f>] ? __kunmap_atomic+0x64/0xbd
[ 2.550188] [<c042d22f>] ? __kunmap_atomic+0x64/0xbd
[ 2.551140] [<c044366f>] warn_slowpath_null+0x22/0x24
[ 2.552109] [<c042d22f>] __kunmap_atomic+0x64/0xbd
[ 2.553178] [<c04db063>] unmap_vmas+0x47d/0x570
[ 2.554534] [<c04dfbe5>] exit_mmap+0x90/0xe0
[ 2.555625] [<c046d4a1>] ? trace_hardirqs_off+0xc/0xd
[ 2.556779] [<c044167f>] mmput+0x68/0xd2
[ 2.557786] [<c0505133>] flush_old_exec+0x427/0x4db
[ 2.558660] [<c05369a1>] load_elf_binary+0x2c3/0x1012
[ 2.559539] [<c046d4a0>] ? trace_hardirqs_off+0xb/0xd
[ 2.560428] [<c0462129>] ? local_clock+0x32/0x49
[ 2.561326] [<c0504b2f>] search_binary_handler+0xb0/0x20e
[ 2.562308] [<c05366de>] ? load_elf_library+0x20d/0x20d
[ 2.563325] [<c05355fd>] load_script+0x1b1/0x1cc
[ 2.564262] [<c046d4a0>] ? trace_hardirqs_off+0xb/0xd
[ 2.565157] [<c0462129>] ? local_clock+0x32/0x49
[ 2.566036] [<c046d96b>] ? lock_release_holdtime.part.8+0x5d/0x63
[ 2.566938] [<c046d4a0>] ? trace_hardirqs_off+0xb/0xd
[ 2.567804] [<c0462129>] ? local_clock+0x32/0x49
[ 2.568692] [<c046d96b>] ? lock_release_holdtime.part.8+0x5d/0x63
[ 2.569579] [<c0470413>] ? lock_release+0x163/0x184
[ 2.570489] [<c0504b2f>] search_binary_handler+0xb0/0x20e
[ 2.571445] [<c053544c>] ? bm_status_write+0xa2/0xa2
[ 2.572363] [<c05057f7>] do_execve+0x15f/0x220
[ 2.573339] [<c040f682>] sys_execve+0x36/0x5d
[ 2.574599] [<c0864412>] ptregs_execve+0x12/0x18
[ 2.575488] [<co86431f>] ? sysenter_do_call+0x12/0x38
[ 2.576359] --[end trace ed088c908e3ad521 ]---

Regards,
--
Jerry James
http://www.jamezone.org/
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
 

Thread Tools




All times are GMT. The time now is 10:05 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ©2007 - 2008, www.linux-archive.org