Re: [PATCH 00 of 11] x86: separate pmd lifetime from pgd

2008-01-28 Thread Jeremy Fitzhardinge

Ingo Molnar wrote:

and after a session of bisection, the winner patch is:

  Subject: x86: unify PAE/non-PAE pgd_ctor

which is a tad unexpected, given the relatively harmless nature of the 
patch. (but then again, nothing is really harmless in PAE land.)
  


Oh, well, good.  At least off-the-cuff diagnosis was right.  I must have 
overlooked some detail in that merge.


btw., this is not fair i think: your patch was apparently caught by the 
new debugging helper that tells about itself here:


  

[   29.389872] debug: unmapping init memory c0b03000..c0b6f000



note the close proximity of c0b6f000 and ebx = c0b6fc08. [ I regularly 
come up with such nasty tricks and debugging helpers like that to catch 
bad patches off-guard. You have been warned! ;-) ]
  


Hm, perhaps, but it could be as easily coincidence.  The place there 
initmem is freed is close to where it first needs to rely on a 
non-initmm pagetable.  I presume that message means that c0b6f000 was 
*not* freed.


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


Re: [PATCH 00 of 11] x86: separate pmd lifetime from pgd

2008-01-28 Thread Ingo Molnar

* Ingo Molnar <[EMAIL PROTECTED]> wrote:

> and after a session of bisection, the winner patch is:
> 
>   Subject: x86: unify PAE/non-PAE pgd_ctor
> 
> which is a tad unexpected, given the relatively harmless nature of the 
> patch. (but then again, nothing is really harmless in PAE land.)

ok, i merged up your series with this patch removed. (it was possible 
with a few manual fixups) That way the problem .config boots fine.

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


Re: [PATCH 00 of 11] x86: separate pmd lifetime from pgd

2008-01-28 Thread Ingo Molnar

* Ingo Molnar <[EMAIL PROTECTED]> wrote:

> hm, i tried this, and got an early crash:
> 
> [   29.389844] VFS: Mounted root (ext3 filesystem) readonly.
> [   29.389872] debug: unmapping init memory c0b03000..c0b6f000
> [   29.440139] PM: Adding info for No Bus:vcs1
> [   29.463676] khelper used greatest stack depth: 2404 bytes left
> [   29.467238] PM: Adding info for No Bus:vcsa1
> [   29.541785] PANIC: double fault, gdt at c1d16000 [255 bytes]
> [   29.541785] double fault, tss at c1d19100
> [   29.541785] eip = c011fa95, esp = c3bf6000
> [   29.541785] eax = c3bf6010, ebx = c0b6fc08, ecx = 007b, edx = 
> [   29.541785] esi = f76a7df4, edi = c011fa90
> 
> i think it's one of your patches :) Bisecting it down to the right one 
> now. Config attached.

and after a session of bisection, the winner patch is:

  Subject: x86: unify PAE/non-PAE pgd_ctor

which is a tad unexpected, given the relatively harmless nature of the 
patch. (but then again, nothing is really harmless in PAE land.)

btw., this is not fair i think: your patch was apparently caught by the 
new debugging helper that tells about itself here:

> [   29.389872] debug: unmapping init memory c0b03000..c0b6f000

note the close proximity of c0b6f000 and ebx = c0b6fc08. [ I regularly 
come up with such nasty tricks and debugging helpers like that to catch 
bad patches off-guard. You have been warned! ;-) ]

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


Re: [PATCH 00 of 11] x86: separate pmd lifetime from pgd

2008-01-28 Thread Jeremy Fitzhardinge

Ingo Molnar wrote:

* Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:

  
This series addresses various cleanups in pagetable allocation in the 
direction of unifying 32/64 bits (that's still a while off yet).



hm, i tried this, and got an early crash:

[   29.389844] VFS: Mounted root (ext3 filesystem) readonly.
[   29.389872] debug: unmapping init memory c0b03000..c0b6f000
[   29.440139] PM: Adding info for No Bus:vcs1
[   29.463676] khelper used greatest stack depth: 2404 bytes left
[   29.467238] PM: Adding info for No Bus:vcsa1
[   29.541785] PANIC: double fault, gdt at c1d16000 [255 bytes]
[   29.541785] double fault, tss at c1d19100
[   29.541785] eip = c011fa95, esp = c3bf6000
[   29.541785] eax = c3bf6010, ebx = c0b6fc08, ecx = 007b, edx = 
[   29.541785] esi = f76a7df4, edi = c011fa90

i think it's one of your patches :) Bisecting it down to the right one 
now.


Wouldn't surprise me.  Given that its a non-PAE config, most of the 
patches won't be in play, but perhaps I screwed up coping the kernel 
pagetable entries into the pgd somehow.


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


Re: [PATCH 00 of 11] x86: separate pmd lifetime from pgd

2008-01-28 Thread Ingo Molnar

* Jeremy Fitzhardinge <[EMAIL PROTECTED]> wrote:

> This series addresses various cleanups in pagetable allocation in the 
> direction of unifying 32/64 bits (that's still a while off yet).

hm, i tried this, and got an early crash:

[   29.389844] VFS: Mounted root (ext3 filesystem) readonly.
[   29.389872] debug: unmapping init memory c0b03000..c0b6f000
[   29.440139] PM: Adding info for No Bus:vcs1
[   29.463676] khelper used greatest stack depth: 2404 bytes left
[   29.467238] PM: Adding info for No Bus:vcsa1
[   29.541785] PANIC: double fault, gdt at c1d16000 [255 bytes]
[   29.541785] double fault, tss at c1d19100
[   29.541785] eip = c011fa95, esp = c3bf6000
[   29.541785] eax = c3bf6010, ebx = c0b6fc08, ecx = 007b, edx = 
[   29.541785] esi = f76a7df4, edi = c011fa90

i think it's one of your patches :) Bisecting it down to the right one 
now. Config attached.

Ingo
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.24
# Mon Jan 28 16:01:11 2008
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
# CONFIG_GENERIC_LOCKBREAK is not set
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_QUICKLIST=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
# CONFIG_GENERIC_GPIO is not set
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_CALIBRATE_DELAY=y
# CONFIG_GENERIC_TIME_VSYSCALL is not set
# CONFIG_HAVE_SETUP_PER_CPU_AREA is not set
CONFIG_ARCH_SUPPORTS_OPROFILE=y
# CONFIG_ZONE_DMA32 is not set
CONFIG_ARCH_POPULATES_NODE_MAP=y
# CONFIG_AUDIT_ARCH is not set
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_SMP=y
CONFIG_X86_32_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_KTIME_SCALAR=y
# CONFIG_BOOTPARAM_SUPPORT is not set
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=""
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
# CONFIG_SYSVIPC is not set
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
# CONFIG_TASK_XACCT is not set
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
# CONFIG_AUDIT is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=20
CONFIG_CGROUPS=y
CONFIG_CGROUP_DEBUG=y
CONFIG_CGROUP_NS=y
# CONFIG_CPUSETS is not set
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_FAIR_USER_SCHED is not set
CONFIG_FAIR_CGROUP_SCHED=y
# CONFIG_CGROUP_CPUACCT is not set
CONFIG_SYSFS_DEPRECATED=y
# CONFIG_RELAY is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_MODULES is not set
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_LBD=y
# CONFIG_BLK_DEV_IO_TRACE is not set
CONFIG_LSF=y
# CONFIG_BLK_DEV_BSG is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
# CONFIG_IOSCHED_CFQ is not set
# CONFIG_DEFAULT_AS is not set
CONFIG_DEFAULT_DEADLINE=y
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED="deadline"
CONFIG_CLASSIC_RCU=y
# CONFIG_PREEMPT_RCU is not set

#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
# CONFIG_NO_HZ is not set
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_X86_RDC321X is not set
# CONFIG_X86_VSMP is not set
CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
# CONFIG_PARAVIRT_GUEST is not set
# CONFIG_M386 is not set
CONFIG_M486=y
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# 

Re: [PATCH 00 of 11] x86: separate pmd lifetime from pgd

2008-01-28 Thread Ingo Molnar

* Jeremy Fitzhardinge [EMAIL PROTECTED] wrote:

 This series addresses various cleanups in pagetable allocation in the 
 direction of unifying 32/64 bits (that's still a while off yet).

hm, i tried this, and got an early crash:

[   29.389844] VFS: Mounted root (ext3 filesystem) readonly.
[   29.389872] debug: unmapping init memory c0b03000..c0b6f000
[   29.440139] PM: Adding info for No Bus:vcs1
[   29.463676] khelper used greatest stack depth: 2404 bytes left
[   29.467238] PM: Adding info for No Bus:vcsa1
[   29.541785] PANIC: double fault, gdt at c1d16000 [255 bytes]
[   29.541785] double fault, tss at c1d19100
[   29.541785] eip = c011fa95, esp = c3bf6000
[   29.541785] eax = c3bf6010, ebx = c0b6fc08, ecx = 007b, edx = 
[   29.541785] esi = f76a7df4, edi = c011fa90

i think it's one of your patches :) Bisecting it down to the right one 
now. Config attached.

Ingo
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.24
# Mon Jan 28 16:01:11 2008
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
# CONFIG_GENERIC_LOCKBREAK is not set
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_SEMAPHORE_SLEEPERS=y
CONFIG_MMU=y
CONFIG_ZONE_DMA=y
CONFIG_QUICKLIST=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_GENERIC_BUG=y
CONFIG_GENERIC_HWEIGHT=y
# CONFIG_GENERIC_GPIO is not set
CONFIG_ARCH_MAY_HAVE_PC_FDC=y
CONFIG_DMI=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ARCH_HAS_ILOG2_U32 is not set
# CONFIG_ARCH_HAS_ILOG2_U64 is not set
CONFIG_GENERIC_CALIBRATE_DELAY=y
# CONFIG_GENERIC_TIME_VSYSCALL is not set
# CONFIG_HAVE_SETUP_PER_CPU_AREA is not set
CONFIG_ARCH_SUPPORTS_OPROFILE=y
# CONFIG_ZONE_DMA32 is not set
CONFIG_ARCH_POPULATES_NODE_MAP=y
# CONFIG_AUDIT_ARCH is not set
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_GENERIC_PENDING_IRQ=y
CONFIG_X86_SMP=y
CONFIG_X86_32_SMP=y
CONFIG_X86_HT=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_X86_TRAMPOLINE=y
CONFIG_KTIME_SCALAR=y
# CONFIG_BOOTPARAM_SUPPORT is not set
CONFIG_DEFCONFIG_LIST=/lib/modules/$UNAME_RELEASE/.config

#
# General setup
#
CONFIG_EXPERIMENTAL=y
CONFIG_LOCK_KERNEL=y
CONFIG_INIT_ENV_ARG_LIMIT=32
CONFIG_LOCALVERSION=
CONFIG_LOCALVERSION_AUTO=y
CONFIG_SWAP=y
# CONFIG_SYSVIPC is not set
# CONFIG_POSIX_MQUEUE is not set
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_TASKSTATS=y
CONFIG_TASK_DELAY_ACCT=y
# CONFIG_TASK_XACCT is not set
# CONFIG_USER_NS is not set
# CONFIG_PID_NS is not set
# CONFIG_AUDIT is not set
# CONFIG_IKCONFIG is not set
CONFIG_LOG_BUF_SHIFT=20
CONFIG_CGROUPS=y
CONFIG_CGROUP_DEBUG=y
CONFIG_CGROUP_NS=y
# CONFIG_CPUSETS is not set
CONFIG_FAIR_GROUP_SCHED=y
# CONFIG_FAIR_USER_SCHED is not set
CONFIG_FAIR_CGROUP_SCHED=y
# CONFIG_CGROUP_CPUACCT is not set
CONFIG_SYSFS_DEPRECATED=y
# CONFIG_RELAY is not set
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set
CONFIG_SYSCTL=y
# CONFIG_EMBEDDED is not set
CONFIG_UID16=y
CONFIG_SYSCTL_SYSCALL=y
CONFIG_KALLSYMS=y
CONFIG_KALLSYMS_ALL=y
CONFIG_KALLSYMS_EXTRA_PASS=y
CONFIG_HOTPLUG=y
CONFIG_PRINTK=y
CONFIG_BUG=y
CONFIG_ELF_CORE=y
CONFIG_BASE_FULL=y
CONFIG_FUTEX=y
CONFIG_ANON_INODES=y
CONFIG_EPOLL=y
CONFIG_SIGNALFD=y
CONFIG_EVENTFD=y
CONFIG_SHMEM=y
CONFIG_VM_EVENT_COUNTERS=y
CONFIG_SLAB=y
# CONFIG_SLUB is not set
# CONFIG_SLOB is not set
CONFIG_SLABINFO=y
CONFIG_RT_MUTEXES=y
# CONFIG_TINY_SHMEM is not set
CONFIG_BASE_SMALL=0
# CONFIG_MODULES is not set
CONFIG_STOP_MACHINE=y
CONFIG_BLOCK=y
CONFIG_LBD=y
# CONFIG_BLK_DEV_IO_TRACE is not set
CONFIG_LSF=y
# CONFIG_BLK_DEV_BSG is not set

#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
# CONFIG_IOSCHED_CFQ is not set
# CONFIG_DEFAULT_AS is not set
CONFIG_DEFAULT_DEADLINE=y
# CONFIG_DEFAULT_CFQ is not set
# CONFIG_DEFAULT_NOOP is not set
CONFIG_DEFAULT_IOSCHED=deadline
CONFIG_CLASSIC_RCU=y
# CONFIG_PREEMPT_RCU is not set

#
# Processor type and features
#
CONFIG_TICK_ONESHOT=y
# CONFIG_NO_HZ is not set
CONFIG_HIGH_RES_TIMERS=y
CONFIG_GENERIC_CLOCKEVENTS_BUILD=y
CONFIG_SMP=y
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_X86_RDC321X is not set
# CONFIG_X86_VSMP is not set
CONFIG_SCHED_NO_NO_OMIT_FRAME_POINTER=y
# CONFIG_PARAVIRT_GUEST is not set
# CONFIG_M386 is not set
CONFIG_M486=y
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is 

Re: [PATCH 00 of 11] x86: separate pmd lifetime from pgd

2008-01-28 Thread Ingo Molnar

* Ingo Molnar [EMAIL PROTECTED] wrote:

 and after a session of bisection, the winner patch is:
 
   Subject: x86: unify PAE/non-PAE pgd_ctor
 
 which is a tad unexpected, given the relatively harmless nature of the 
 patch. (but then again, nothing is really harmless in PAE land.)

ok, i merged up your series with this patch removed. (it was possible 
with a few manual fixups) That way the problem .config boots fine.

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


Re: [PATCH 00 of 11] x86: separate pmd lifetime from pgd

2008-01-28 Thread Ingo Molnar

* Ingo Molnar [EMAIL PROTECTED] wrote:

 hm, i tried this, and got an early crash:
 
 [   29.389844] VFS: Mounted root (ext3 filesystem) readonly.
 [   29.389872] debug: unmapping init memory c0b03000..c0b6f000
 [   29.440139] PM: Adding info for No Bus:vcs1
 [   29.463676] khelper used greatest stack depth: 2404 bytes left
 [   29.467238] PM: Adding info for No Bus:vcsa1
 [   29.541785] PANIC: double fault, gdt at c1d16000 [255 bytes]
 [   29.541785] double fault, tss at c1d19100
 [   29.541785] eip = c011fa95, esp = c3bf6000
 [   29.541785] eax = c3bf6010, ebx = c0b6fc08, ecx = 007b, edx = 
 [   29.541785] esi = f76a7df4, edi = c011fa90
 
 i think it's one of your patches :) Bisecting it down to the right one 
 now. Config attached.

and after a session of bisection, the winner patch is:

  Subject: x86: unify PAE/non-PAE pgd_ctor

which is a tad unexpected, given the relatively harmless nature of the 
patch. (but then again, nothing is really harmless in PAE land.)

btw., this is not fair i think: your patch was apparently caught by the 
new debugging helper that tells about itself here:

 [   29.389872] debug: unmapping init memory c0b03000..c0b6f000

note the close proximity of c0b6f000 and ebx = c0b6fc08. [ I regularly 
come up with such nasty tricks and debugging helpers like that to catch 
bad patches off-guard. You have been warned! ;-) ]

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


Re: [PATCH 00 of 11] x86: separate pmd lifetime from pgd

2008-01-28 Thread Jeremy Fitzhardinge

Ingo Molnar wrote:

* Jeremy Fitzhardinge [EMAIL PROTECTED] wrote:

  
This series addresses various cleanups in pagetable allocation in the 
direction of unifying 32/64 bits (that's still a while off yet).



hm, i tried this, and got an early crash:

[   29.389844] VFS: Mounted root (ext3 filesystem) readonly.
[   29.389872] debug: unmapping init memory c0b03000..c0b6f000
[   29.440139] PM: Adding info for No Bus:vcs1
[   29.463676] khelper used greatest stack depth: 2404 bytes left
[   29.467238] PM: Adding info for No Bus:vcsa1
[   29.541785] PANIC: double fault, gdt at c1d16000 [255 bytes]
[   29.541785] double fault, tss at c1d19100
[   29.541785] eip = c011fa95, esp = c3bf6000
[   29.541785] eax = c3bf6010, ebx = c0b6fc08, ecx = 007b, edx = 
[   29.541785] esi = f76a7df4, edi = c011fa90

i think it's one of your patches :) Bisecting it down to the right one 
now.


Wouldn't surprise me.  Given that its a non-PAE config, most of the 
patches won't be in play, but perhaps I screwed up coping the kernel 
pagetable entries into the pgd somehow.


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


Re: [PATCH 00 of 11] x86: separate pmd lifetime from pgd

2008-01-28 Thread Jeremy Fitzhardinge

Ingo Molnar wrote:

and after a session of bisection, the winner patch is:

  Subject: x86: unify PAE/non-PAE pgd_ctor

which is a tad unexpected, given the relatively harmless nature of the 
patch. (but then again, nothing is really harmless in PAE land.)
  


Oh, well, good.  At least off-the-cuff diagnosis was right.  I must have 
overlooked some detail in that merge.


btw., this is not fair i think: your patch was apparently caught by the 
new debugging helper that tells about itself here:


  

[   29.389872] debug: unmapping init memory c0b03000..c0b6f000



note the close proximity of c0b6f000 and ebx = c0b6fc08. [ I regularly 
come up with such nasty tricks and debugging helpers like that to catch 
bad patches off-guard. You have been warned! ;-) ]
  


Hm, perhaps, but it could be as easily coincidence.  The place there 
initmem is freed is close to where it first needs to rely on a 
non-initmm pagetable.  I presume that message means that c0b6f000 was 
*not* freed.


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