I updated the machine to get the rc3 kernel, and rebooted. I got a
hang in the same place. I'm starting to think the "hung task"
messages that result from waiting long enough deserve a closer look.
Here's the first one:
[ 75.420108] INFO: rcu_sched_state detected stalls on CPUs/tasks: {
1} (de
On Tue, Jun 14, 2011 at 3:08 PM, Daniel J Walsh wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 06/14/2011 04:42 PM, Jerry James wrote:
[snip]
>> Like Lucas, I can boot with selinux=0. I did so, and upgraded to
>> today's Rawhide packages. Since reinstalling selinux-policy and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/14/2011 04:42 PM, Jerry James wrote:
> On Tue, Jun 14, 2011 at 1:16 PM, Jerry James wrote:
>> 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 ha
On Tue, Jun 14, 2011 at 1:16 PM, Jerry James wrote:
> 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:
Like Lucas, I can boot with selinux=0. I did so, and upgraded to
today's Rawhid
On Tue, Jun 14, 2011 at 12:25 PM, Matthew Miller 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 ud
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.fedoraproj
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
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 f
On 06/14/2011 09:57 PM, Lennart Poettering wrote:
> On Tue, 14.06.11 21:32, Lucas (macach...@gmail.com) wrote:
>
>>
>> On 06/14/2011 06:53 PM, Lennart Poettering wrote:
>>> On Tue, 14.06.11 18:48, Lucas (macach...@gmail.com) wrote:
>>>
> Do you see any errors?
Just checked it. Yum rei
On Tue, 14.06.11 21:32, Lucas (macach...@gmail.com) wrote:
>
> On 06/14/2011 06:53 PM, Lennart Poettering wrote:
> > On Tue, 14.06.11 18:48, Lucas (macach...@gmail.com) wrote:
> >
> >>> Do you see any errors?
> >>
> >> Just checked it. Yum reinstalled selinux-policy-targeted, then relabeling,
>
On 06/14/2011 06:53 PM, Lennart Poettering wrote:
> On Tue, 14.06.11 18:48, Lucas (macach...@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
On Tue, 14.06.11 18:48, Lucas (macach...@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
On 06/14/2011 04:38 PM, Daniel J Walsh wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 06/14/2011 06:37 AM, Lucas wrote:
>> On 06/14/2011 02:10 PM, Frank Murphy wrote:
>>> On 14/06/11 11:02, Lucas wrote:
>>>
The only possible way to boot is to add "selinux=0".
Especially
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/14/2011 06:37 AM, Lucas wrote:
> On 06/14/2011 02:10 PM, Frank Murphy wrote:
>> On 14/06/11 11:02, Lucas wrote:
>>
>>> The only possible way to boot is to add "selinux=0".
>>> Especially for Daniel J Walsh, the addition of "enforcing=0" doesn't
On 06/14/2011 02:10 PM, Frank Murphy wrote:
> On 14/06/11 11:02, Lucas wrote:
>
>> 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, e
On 14/06/11 11:02, Lucas wrote:
> 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-
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".
Espec
17 matches
Mail list logo
