[lkml]   [2008]   [Jul]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: next-0710: CONFIG_PARAVIRT broken on x86_64?
    At Thu, 10 Jul 2008 13:12:07 -0700,
    Jeremy Fitzhardinge wrote:
    > Takashi Iwai wrote:
    > > Native. Booted on a HP machine with two Intel x86-64 CPUs.
    > >
    > Is that the complete log of what it prints out? Does it print any
    > addresses or anything?
    > Could you try tip.git with the config to see if its there? I don't
    > think there should be anything relevent in -next, but there could be a
    > merge problem or something.

    Almost same result. The init segfaults at the very beginning.
    The below is the whole screen output I could copy by hand (may include
    some types).

    > Does booting with "init=/bin/sh" make any progress?

    No change.



    registered taskstats version 1
    Freeing unused kernel memory: 1220k freed
    init [1]: segfault at ffffffffffffffa8 ip 00007fe939b9235c sp 00007fff42971028 error 6 in[7fe939abe000+14f000]
    Kernel panic - not syncing: Attempt to kill init!
    Pid: 1, comm: init Not tainted 2.6.26-rc9-tip-test2 #2
    Call trace:
    [<ffffffff80252c7f>] ? blocking_notifier_call_chain+0xf/0x11
    [<ffffffff8023f9f9>] ? do_exit+0x78/0x6de
    [<ffffffff8024705f>] ? __dequeue_signal+0x114/0x177
    [<ffffffff802400dc>] ? do_group_exit+-x7d/0xaa
    [<ffffffff80248ce0>] ? get_signal_to_deliver+0x2fe/0x326
    [<ffffffff8020b3fa>] ? do_notify_resume+0xbf/0x8f4
    [<ffffffff8039029d>] ? sock_destroy_inode+0x14/0x16
    [<ffffffff802b6491>] ? iput+0x61/0x65
    [<ffffffff802b6491>] ? iput+0x61/0x65
    [<ffffffff803915b4>] ? sock_release+0x66/0x76
    [<ffffffff80391780>] ? __sock_create+0x180/0x19f
    [<ffffffff8020c964>] ? retint_signal+0x60/0xbc

     \ /
      Last update: 2008-07-11 13:17    [W:0.021 / U:0.476 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site