logo       
Google Custom Search
    AddThis Social Bookmark Button
-->

Re: [FC3] kernel panic after selinux-policy-targeted update: msg#00257

Subject: Re: [FC3] kernel panic after selinux-policy-targeted update
On Tue, 2005-06-28 at 17:15 +1000, Russell Coker wrote:
> 
> I've just tried reproducing this on a P4-1.5GHz machine specifically 
> installed 
> for the purpose.
> 
> I upgraded to all the latest packages including kernel-2.6.11-1.35_FC3 and 
> selinux-policy-targeted-sources-1.17.30-3.13.  Things worked fine.
> 
> Until I get more detail on this (type of CPU, kernel version, etc) I'll 
> conclude that it was a broken configuration.

Hi Russell,

I got hit by this one. Some details:

Dell Inspiron 8600 laptop, Centrino 1.6Ghz, running 2.6.11-1.27_FC3. An
"everything" installation of FC3, kept updated from fedora-updates and
livna. Using the 2100 wireless NIC at the time.

I did an update this afternoon, which included the selinux policy update
and the latest kernel (kernel-2.6.11-1.35_FC3). During the yum update,
things started breaking as the update applied the new policies (eg. I
couldn't use ssh from the laptop to other hosts).

When I tried to shutdown, I got many messages like this:

Jun 28 18:56:00 ben8600 kernel: audit(1119948960.209:0): avc:  denied
{ execmod } for  pid=13420 comm=mingetty path=/lib/tls/libc-2.3.5.so
dev=hda11 ino=20455 scontext=user_u:system_r:unconfined_t
tcontext=system_u:object_r:lib_t tclass=file

My only option was to power off the laptop. I then had to boot with
enforcing=0 (and a considerable amount of fscking) to get back up.

If there is any other information I can give you to help reproduce this,
let me know.

Cheers, Ben



-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list



<Prev in Thread] Current Thread [Next in Thread>