1. 26 Sep, 2006 3 commits
    • keith mannthey's avatar
      [PATCH] i386 bootioremap / kexec fix · 24fd425e
      keith mannthey authored
      With CONFIG_PHYSICAL_START set to a non default values the i386
      boot_ioremap code calculated its pte index wrong and users of boot_ioremap
      have their areas incorrectly mapped (for me SRAT table not mapped during
      early boot).  This patch removes the addr < BOOT_PTE_PTRS constraint.
      
      [ Keith says this is applicable to 2.6.16 and 2.6.17 as well ]
      
      Signed-off-by: Keith Mannthey<kmannth@us.ibm.com>
      Cc: Vivek Goyal <vgoyal@in.ibm.com>
      Cc: Dave Hansen <haveblue@us.ibm.com>
      Cc: <stable@kernel.org>
      Cc: Adrian Bunk <bunk@stusta.de>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      24fd425e
    • Peter Zijlstra's avatar
      [PATCH] rtc: lockdep fix/workaround · 0b16f21f
      Peter Zijlstra authored
      BUG: warning at kernel/lockdep.c:1816/trace_hardirqs_on() (Not tainted)
       [<c04051ee>] show_trace_log_lvl+0x58/0x171
       [<c0405802>] show_trace+0xd/0x10
       [<c040591b>] dump_stack+0x19/0x1b
       [<c043abee>] trace_hardirqs_on+0xa2/0x11e
       [<c06143c3>] _spin_unlock_irq+0x22/0x26
       [<c0541540>] rtc_get_rtc_time+0x32/0x176
       [<c0419ba4>] hpet_rtc_interrupt+0x92/0x14d
       [<c0450f94>] handle_IRQ_event+0x20/0x4d
       [<c0451055>] __do_IRQ+0x94/0xef
       [<c040678d>] do_IRQ+0x9e/0xbd
       [<c0404a49>] common_interrupt+0x25/0x2c
      DWARF2 unwinder stuck at common_interrupt+0x25/0x2c
      Signed-off-by: default avatarPeter Zijlstra <a.p.zijlstra@chello.nl>
      Acked-by: default avatarIngo Molnar <mingo@elte.hu>
      Cc: <stable@kernel.org>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      0b16f21f
    • Ian Kent's avatar
      [PATCH] autofs4: zero timeout prevents shutdown · c0ba7e51
      Ian Kent authored
      If the timeout of an autofs mount is set to zero then umounts are disabled.
       This works fine, however the kernel module checks the expire timeout and
      goes no further if it is zero.  This is not the right thing to do at
      shutdown as the module is passed an option to expire mounts regardless of
      their timeout setting.
      
      This patch allows autofs to honor the force expire option.
      Signed-off-by: default avatarIan Kent <raven@themaw.net>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      c0ba7e51
  2. 25 Sep, 2006 7 commits
  3. 24 Sep, 2006 12 commits
  4. 25 Sep, 2006 18 commits