Re: X fails to start with latest Linus git

2008-01-27 Thread Kevin Winchester
On Sun, 27 Jan 2008 13:42:44 +0100 Ingo Molnar <[EMAIL PROTECTED]> wrote: > > * Ingo Molnar <[EMAIL PROTECTED]> wrote: > > > hm, perhaps it's due to the xtime lock dependency: > > > > do { > > seq = read_seqbegin(&xtime_lock); > > getnstimeofday(ts); > >

Re: X fails to start with latest Linus git

2008-01-27 Thread Kevin Winchester
On Sun, 27 Jan 2008 13:42:44 +0100 Ingo Molnar <[EMAIL PROTECTED]> wrote: > > * Ingo Molnar <[EMAIL PROTECTED]> wrote: > > > hm, perhaps it's due to the xtime lock dependency: > > > > do { > > seq = read_seqbegin(&xtime_lock); > > getnstimeofday(ts); > >

Re: X fails to start with latest Linus git

2008-01-27 Thread Kevin Winchester
On Sun, 27 Jan 2008 13:37:02 +0100 Ingo Molnar <[EMAIL PROTECTED]> wrote: > > * Kevin Winchester <[EMAIL PROTECTED]> wrote: > > > Sure, the result of the script is at > > > > http://personal.nbnet.nb.ca/kwin/cfs-debug-info-2008.01.27-08.13.28 > > it seems you've got hpet active by default: >

Re: X fails to start with latest Linus git

2008-01-27 Thread Kevin Winchester
On Sun, 27 Jan 2008 13:35:14 +0100 Ingo Molnar <[EMAIL PROTECTED]> wrote: > > * Kevin Winchester <[EMAIL PROTECTED]> wrote: > > > although it is not complete. For some reason (xubuntu, probably) dash > > is my default shell and it does not like the for loop at line 69 of > > that script: > >

Re: X fails to start with latest Linus git

2008-01-27 Thread Ingo Molnar
* Ingo Molnar <[EMAIL PROTECTED]> wrote: > hm, perhaps it's due to the xtime lock dependency: > > do { > seq = read_seqbegin(&xtime_lock); > getnstimeofday(ts); > tomono = wall_to_monotonic; > > } while (read_seqretry(&xtime_lock,

Re: X fails to start with latest Linus git

2008-01-27 Thread Ingo Molnar
* Ingo Molnar <[EMAIL PROTECTED]> wrote: > it seems you've got hpet active by default: > > /sys/devices/system/clocksource/clocksource0/current_clocksource: > hpet > /sys/devices/system/clocksource/clocksource0/available_clocksource: > hpet acpi_pm pit jiffies tsc btw., it's quite mysteriou

Re: X fails to start with latest Linus git

2008-01-27 Thread Ingo Molnar
* Kevin Winchester <[EMAIL PROTECTED]> wrote: > Sure, the result of the script is at > > http://personal.nbnet.nb.ca/kwin/cfs-debug-info-2008.01.27-08.13.28 it seems you've got hpet active by default: /sys/devices/system/clocksource/clocksource0/current_clocksource: hpet /sys/devices/system

Re: X fails to start with latest Linus git

2008-01-27 Thread Ingo Molnar
* Kevin Winchester <[EMAIL PROTECTED]> wrote: > although it is not complete. For some reason (xubuntu, probably) dash > is my default shell and it does not like the for loop at line 69 of > that script: > > for ((i=0; i<5; i++)); do > echo "-- sched_debug #$i: --" >> $FILE > date

Re: X fails to start with latest Linus git

2008-01-27 Thread Jan Engelhardt
On Jan 27 2008 07:27, Ingo Molnar wrote: >* Kevin Winchester <[EMAIL PROTECTED]> wrote: > >> The machine boots normally, but without that revert, X locks up. Does >> that make sense to anyone? > >could you send your full bootlog? Also please send me the output of: > > http://people.redhat.com/mi

[git pull] printk fix (was: Re: X fails to start with latest Linus git)

2008-01-26 Thread Ingo Molnar
Linus, please pull the following printk fix: git://git.kernel.org/pub/scm/linux/kernel/git/mingo/linux-2.6-sched.git it reverts 19ef9309273d: Kevin Winchester reported a CONFIG_PRINTK_TIME=y related hang during X startup, and biscted it down to this commit. Ingo -

Re: X fails to start with latest Linus git

2008-01-26 Thread Ingo Molnar
* Kevin Winchester <[EMAIL PROTECTED]> wrote: > The machine boots normally, but without that revert, X locks up. Does > that make sense to anyone? could you send your full bootlog? Also please send me the output of: http://people.redhat.com/mingo/cfs-scheduler/tools/cfs-debug-info.sh and pl

Re: X fails to start with latest Linus git

2008-01-26 Thread Kevin Winchester
Kevin Winchester wrote: > Hi Ingo, > > Starting X (autostarted with GDM) manages to lock up my system > (requiring a hard reset) after the first few tree merges of the window, > and bisection shows: > > - > > 19ef9309273d26cb005cb23e6a370353dca91099 is first bad commit > commit 1