next-20081023 x86_64 boot hang: int3 - Kernel

This is a discussion on next-20081023 x86_64 boot hang: int3 - Kernel ; 2 out of 2 x86_64 SMP boots stop with: calling tcp_congestion_default+0x0/0x12 @ 1 initcall tcp_congestion_default+0x0/0x12 returned 0 after 2 usecs Freeing unused kernel memory: 448k freed Write protecting the kernel read-only data: 4816k int3: 0000 [#1] SMP last sysfs file: ...

+ Reply to Thread
Results 1 to 5 of 5

Thread: next-20081023 x86_64 boot hang: int3

  1. next-20081023 x86_64 boot hang: int3

    2 out of 2 x86_64 SMP boots stop with:

    calling tcp_congestion_default+0x0/0x12 @ 1
    initcall tcp_congestion_default+0x0/0x12 returned 0 after 2 usecs
    Freeing unused kernel memory: 448k freed
    Write protecting the kernel read-only data: 4816k
    int3: 0000 [#1] SMP
    last sysfs file:
    CPU 2
    Modules linked in:
    Pid: 0, comm: events/0 Not tainted 2.6.27-next-20081023 #1
    RIP: 0010:[] [] nmi_cpu_busy+0x1/0x15
    RSP: 0018:ffff88017faa7f80 EFLAGS: 00000086
    RAX: 00000000ffffffff RBX: ffff88027f60e000 RCX: ffff88017fa98000
    RDX: ffffffff807eb480 RSI: 0000000000000000 RDI: ffffffff807b9e5c
    RBP: ffff88017faa7f98 R08: 0000000000000000 R09: ffff88002802c768
    R10: 0000000000000000 R11: ffff88027e023e90 R12: 0000000000000002
    R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
    FS: 0000000000000000(0000) GS:ffff88017fa32280(0000) knlGS:0000000000000000
    CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
    CR2: 0000000000000000 CR3: 0000000000201000 CR4: 00000000000006e0
    DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    Process events/0 (pid: 0, threadinfo ffff88017fa8c000, task ffff88017fa98000)
    Stack:
    ffffffff80257afe ffffffff8076d938 0000000000000000 ffff88017faa7fa8
    ffffffff8021f1b0 ffff88017fa8de50 ffffffff8020cabb ffff88017fa8de50
    ffff88017fa8ded8 ffff88027e023e90 0000000000000000 ffff88002802c768
    Call Trace:
    <0> [] ? generic_smp_call_function_interrupt+0x35/0xd7
    [] smp_call_function_interrupt+0x1f/0x2f
    [] call_function_interrupt+0x6b/0x70
    <0> [] ? default_idle+0x2b/0x40
    [] ? c1e_idle+0xe5/0xec
    [] ? atomic_notifier_call_chain+0xf/0x11
    [] ? cpu_idle+0x48/0x66
    [] ? start_secondary+0x177/0x17c
    Code: cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc
    RIP [] nmi_cpu_busy+0x1/0x15
    RSP
    Kernel panic - not syncing: Fatal exception in interrupt


    Full boot log is at
    http://oss.oracle.com/~rdunlap/kerne...etcon-5175.log
    and .config is at http://oss.oracle.com/~rdunlap/kerne...s/kconfig-5175

    ---
    ~Randy
    --
    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/

  2. Re: next-20081023 x86_64 boot hang: int3

    [Cyrill Gorcunov - Thu, Oct 23, 2008 at 09:50:08PM +0400]
    ....
    |
    | Hi Randy,
    |
    | i don't remember the details -- these int3 opcodes are likely to
    | come from some paging or stack protector... hmm... can't remember
    | absolutely There was a thread on LKML about half a year ago about
    | why to fill pages with int3 opcode. But I may be absolutely wrong
    |
    | - Cyrill -

    Hmm, I think I'm not in touch don't play attention on this mail,
    sorry

    - Cyrill -
    --
    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/

  3. Re: next-20081023 x86_64 boot hang: int3

    [Randy Dunlap - Thu, Oct 23, 2008 at 10:43:40AM -0700]
    | 2 out of 2 x86_64 SMP boots stop with:
    |
    | calling tcp_congestion_default+0x0/0x12 @ 1
    | initcall tcp_congestion_default+0x0/0x12 returned 0 after 2 usecs
    | Freeing unused kernel memory: 448k freed
    | Write protecting the kernel read-only data: 4816k
    | int3: 0000 [#1] SMP
    | last sysfs file:
    | CPU 2
    | Modules linked in:
    | Pid: 0, comm: events/0 Not tainted 2.6.27-next-20081023 #1
    | RIP: 0010:[] [] nmi_cpu_busy+0x1/0x15
    | RSP: 0018:ffff88017faa7f80 EFLAGS: 00000086
    | RAX: 00000000ffffffff RBX: ffff88027f60e000 RCX: ffff88017fa98000
    | RDX: ffffffff807eb480 RSI: 0000000000000000 RDI: ffffffff807b9e5c
    | RBP: ffff88017faa7f98 R08: 0000000000000000 R09: ffff88002802c768
    | R10: 0000000000000000 R11: ffff88027e023e90 R12: 0000000000000002
    | R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
    | FS: 0000000000000000(0000) GS:ffff88017fa32280(0000) knlGS:0000000000000000
    | CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
    | CR2: 0000000000000000 CR3: 0000000000201000 CR4: 00000000000006e0
    | DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    | DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    | Process events/0 (pid: 0, threadinfo ffff88017fa8c000, task ffff88017fa98000)
    | Stack:
    | ffffffff80257afe ffffffff8076d938 0000000000000000 ffff88017faa7fa8
    | ffffffff8021f1b0 ffff88017fa8de50 ffffffff8020cabb ffff88017fa8de50
    | ffff88017fa8ded8 ffff88027e023e90 0000000000000000 ffff88002802c768
    | Call Trace:
    | <0> [] ? generic_smp_call_function_interrupt+0x35/0xd7
    | [] smp_call_function_interrupt+0x1f/0x2f
    | [] call_function_interrupt+0x6b/0x70
    | <0> [] ? default_idle+0x2b/0x40
    | [] ? c1e_idle+0xe5/0xec
    | [] ? atomic_notifier_call_chain+0xf/0x11
    | [] ? cpu_idle+0x48/0x66
    | [] ? start_secondary+0x177/0x17c
    | Code: cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc
    | RIP [] nmi_cpu_busy+0x1/0x15
    | RSP
    | Kernel panic - not syncing: Fatal exception in interrupt
    |
    |
    | Full boot log is at
    | http://oss.oracle.com/~rdunlap/kerne...etcon-5175.log
    | and .config is at http://oss.oracle.com/~rdunlap/kerne...s/kconfig-5175
    |
    | ---
    | ~Randy
    |

    Hi Randy,

    i don't remember the details -- these int3 opcodes are likely to
    come from some paging or stack protector... hmm... can't remember
    absolutely There was a thread on LKML about half a year ago about
    why to fill pages with int3 opcode. But I may be absolutely wrong

    - Cyrill -
    --
    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/

  4. Re: next-20081023 x86_64 boot hang: int3

    Randy Dunlap wrote:
    > 2 out of 2 x86_64 SMP boots stop with:
    >
    > calling tcp_congestion_default+0x0/0x12 @ 1
    > initcall tcp_congestion_default+0x0/0x12 returned 0 after 2 usecs
    > Freeing unused kernel memory: 448k freed
    > Write protecting the kernel read-only data: 4816k
    > int3: 0000 [#1] SMP
    > last sysfs file:
    > CPU 2
    > Modules linked in:
    > Pid: 0, comm: events/0 Not tainted 2.6.27-next-20081023 #1
    > RIP: 0010:[] [] nmi_cpu_busy+0x1/0x15
    > RSP: 0018:ffff88017faa7f80 EFLAGS: 00000086
    > RAX: 00000000ffffffff RBX: ffff88027f60e000 RCX: ffff88017fa98000
    > RDX: ffffffff807eb480 RSI: 0000000000000000 RDI: ffffffff807b9e5c
    > RBP: ffff88017faa7f98 R08: 0000000000000000 R09: ffff88002802c768
    > R10: 0000000000000000 R11: ffff88027e023e90 R12: 0000000000000002
    > R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
    > FS: 0000000000000000(0000) GS:ffff88017fa32280(0000) knlGS:0000000000000000
    > CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
    > CR2: 0000000000000000 CR3: 0000000000201000 CR4: 00000000000006e0
    > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    > DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    > Process events/0 (pid: 0, threadinfo ffff88017fa8c000, task ffff88017fa98000)
    > Stack:
    > ffffffff80257afe ffffffff8076d938 0000000000000000 ffff88017faa7fa8
    > ffffffff8021f1b0 ffff88017fa8de50 ffffffff8020cabb ffff88017fa8de50
    > ffff88017fa8ded8 ffff88027e023e90 0000000000000000 ffff88002802c768
    > Call Trace:
    > <0> [] ? generic_smp_call_function_interrupt+0x35/0xd7
    > [] smp_call_function_interrupt+0x1f/0x2f
    > [] call_function_interrupt+0x6b/0x70
    > <0> [] ? default_idle+0x2b/0x40
    > [] ? c1e_idle+0xe5/0xec
    > [] ? atomic_notifier_call_chain+0xf/0x11
    > [] ? cpu_idle+0x48/0x66
    > [] ? start_secondary+0x177/0x17c
    > Code: cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc
    > RIP [] nmi_cpu_busy+0x1/0x15
    > RSP
    > Kernel panic - not syncing: Fatal exception in interrupt
    >
    >
    > Full boot log is at
    > http://oss.oracle.com/~rdunlap/kerne...etcon-5175.log
    > and .config is at http://oss.oracle.com/~rdunlap/kerne...s/kconfig-5175


    Hi,

    this patch will fix this issue.
    http://marc.info/?l=linux-kernel&m=122482422513626&w=2

    thanks,
    Hiroshi Shimamoto

    --
    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/

  5. Re: next-20081023 x86_64 boot hang: int3

    On Thu, 23 Oct 2008 22:07:57 -0700 Hiroshi Shimamoto wrote:

    > Randy Dunlap wrote:
    > > 2 out of 2 x86_64 SMP boots stop with:
    > >
    > > calling tcp_congestion_default+0x0/0x12 @ 1
    > > initcall tcp_congestion_default+0x0/0x12 returned 0 after 2 usecs
    > > Freeing unused kernel memory: 448k freed
    > > Write protecting the kernel read-only data: 4816k
    > > int3: 0000 [#1] SMP
    > > last sysfs file:
    > > CPU 2
    > > Modules linked in:
    > > Pid: 0, comm: events/0 Not tainted 2.6.27-next-20081023 #1
    > > RIP: 0010:[] [] nmi_cpu_busy+0x1/0x15
    > > RSP: 0018:ffff88017faa7f80 EFLAGS: 00000086
    > > RAX: 00000000ffffffff RBX: ffff88027f60e000 RCX: ffff88017fa98000
    > > RDX: ffffffff807eb480 RSI: 0000000000000000 RDI: ffffffff807b9e5c
    > > RBP: ffff88017faa7f98 R08: 0000000000000000 R09: ffff88002802c768
    > > R10: 0000000000000000 R11: ffff88027e023e90 R12: 0000000000000002
    > > R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
    > > FS: 0000000000000000(0000) GS:ffff88017fa32280(0000) knlGS:0000000000000000
    > > CS: 0010 DS: 0018 ES: 0018 CR0: 000000008005003b
    > > CR2: 0000000000000000 CR3: 0000000000201000 CR4: 00000000000006e0
    > > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    > > DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    > > Process events/0 (pid: 0, threadinfo ffff88017fa8c000, task ffff88017fa98000)
    > > Stack:
    > > ffffffff80257afe ffffffff8076d938 0000000000000000 ffff88017faa7fa8
    > > ffffffff8021f1b0 ffff88017fa8de50 ffffffff8020cabb ffff88017fa8de50
    > > ffff88017fa8ded8 ffff88027e023e90 0000000000000000 ffff88002802c768
    > > Call Trace:
    > > <0> [] ? generic_smp_call_function_interrupt+0x35/0xd7
    > > [] smp_call_function_interrupt+0x1f/0x2f
    > > [] call_function_interrupt+0x6b/0x70
    > > <0> [] ? default_idle+0x2b/0x40
    > > [] ? c1e_idle+0xe5/0xec
    > > [] ? atomic_notifier_call_chain+0xf/0x11
    > > [] ? cpu_idle+0x48/0x66
    > > [] ? start_secondary+0x177/0x17c
    > > Code: cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc cc
    > > RIP [] nmi_cpu_busy+0x1/0x15
    > > RSP
    > > Kernel panic - not syncing: Fatal exception in interrupt
    > >
    > >
    > > Full boot log is at
    > > http://oss.oracle.com/~rdunlap/kerne...etcon-5175.log
    > > and .config is at http://oss.oracle.com/~rdunlap/kerne...s/kconfig-5175

    >
    > Hi,
    >
    > this patch will fix this issue.
    > http://marc.info/?l=linux-kernel&m=122482422513626&w=2


    Great. Thank you.

    ---
    ~Randy
    --
    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/

+ Reply to Thread