Re: 2.6.17-mm2 hrtimer code wedges at boot?

[Thomas Gleixner <tglx@linutronix.de>]

On Mon, 2006-06-26 at 22:12 -0400, Valdis.Kletnieks@vt.edu wrote:
> On Tue, 27 Jun 2006 01:27:09 +0200, Thomas Gleixner said:
> > On Mon, 2006-06-26 at 17:41 -0400, Valdis.Kletnieks@vt.edu wrote:
> > > On Sat, 24 Jun 2006 06:19:14 PDT, Andrew Morton said:
> > > > 
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.17/2.6.
> 17-mm2/
> > > 
> > > I'm seeing a 2-minute or so hang at system startup, seems to be hrtimer
> > > related.  
> > 
> > hrtimer is not really involved here.
> 
> OK, the fact that it was continually in kernel/hrtimer.c was a red herring? :)

Yup.

> [   24.292902] SELinux: initialized (dev bdev, type bdev), uses genfs_contexts
> [   24.311432] SELinux: initialized (dev rootfs, type rootfs), uses genfs_contexts
> [   24.330082] SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
> [   24.351494] audit(1151368041.674:2): policy loaded auid=4294967295
> [   24.370664] audit(1151368041.666:3): avc:  granted  { load_policy } for  pid=1 comm="init" scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:object_r:security_t:s0 tclass=security

<snip>

> [   88.467114]  <c01006c5> kernel_thread_helper+0x5/0xb 
> [   89.913214] Real Time Clock Driver v1.12ac
> [   90.489593] audit(1151368108.794:4): avc:  denied  { dac_override } for  pid=452 comm="dmesg" capability=1 scontext=system_u:system_r:dmesg_t:s0 tcontext=system_u:system_r:dmesg_t:s0 tclass=capability
> 
> And after that, things move along OK.

Hmm, does not help much. Wild guess: Can you turn off CONFIG_RTC and try
again ?

	tglx


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/