Lukas Czerner | 10 May 2010 17:38
Picon
Favicon

uml: Error with Linked list debugging on

Hi,

I have got an error when booting uml with Linked list manipulation
debugging turned on. The crash occurs in the exact moment when the
consoles are showing up - it just blinks and crush. Here is the
backtrace:

#0  0x0000003cb8233e14 in abort () from /lib64/libc.so.6
#1  0x00000000600220b2 in os_dump_core () at arch/um/os-Linux/util.c:119
#2  0x00000000600147c1 in panic_exit (self=<value optimized out>, unused1=<value optimized out>, 
    unused2=<value optimized out>) at arch/um/kernel/um_arch.c:233
#3  0x0000000060045996 in notifier_call_chain (nl=<value optimized out>, val=0, v=0x602ffb40, 
nr_to_call=-2, nr_calls=<value optimized out>) at kernel/notifier.c:93
#4  0x00000000600459e4 in __atomic_notifier_call_chain (nh=<value optimized out>, 
val=<value optimized out>, v=<value optimized out>) at kernel/notifier.c:182
#5  atomic_notifier_call_chain (nh=<value optimized out>, val=<value optimized out>, 
v=<value optimized out>) at kernel/notifier.c:191
#6  0x00000000601a56d0 in panic (fmt=0x601f3050 "Kernel mode fault at addr 0x%lx, ip 0x%lx")
at kernel/panic.c:115
#7  0x00000000600145df in segv (fi=..., ip=1611852984, is_user=0, regs=0x6024fa10)
at arch/um/kernel/trap.c:201
#8  0x000000006001463e in segv_handler (sig=<value optimized out>, regs=<value optimized out>)
at arch/um/kernel/trap.c:147
#9  0x00000000600211a4 in sig_handler_common (sig=11, sc=0x6024fbe8) at arch/um/os-Linux/signal.c:49
#10 0x00000000600212ea in sig_handler (sig=<value optimized out>, sc=<value optimized out>)
at arch/um/os-Linux/signal.c:226
#11 0x000000006002151c in handle_signal (sig=<value optimized out>, sc=0x6024fbe8)
    at arch/um/os-Linux/signal.c:158
#12 0x0000000060022e9c in hard_handler (sig=<value optimized out>)
at arch/um/os-Linux/sys-x86_64/signal.c:15
(Continue reading)

Lukas Czerner | 10 May 2010 18:58
Picon
Favicon

Re: uml: Error with Linked list debugging on

On Mon, 10 May 2010, Lukas Czerner wrote:

> Hi,
> 
> I have got an error when booting uml with Linked list manipulation
> debugging turned on. The crash occurs in the exact moment when the
> consoles are showing up - it just blinks and crush. Here is the
> backtrace:
> 
> 
> #0  0x0000003cb8233e14 in abort () from /lib64/libc.so.6
> #1  0x00000000600220b2 in os_dump_core () at arch/um/os-Linux/util.c:119
> #2  0x00000000600147c1 in panic_exit (self=<value optimized out>, unused1=<value optimized out>, 
>     unused2=<value optimized out>) at arch/um/kernel/um_arch.c:233
> #3  0x0000000060045996 in notifier_call_chain (nl=<value optimized out>, val=0, v=0x602ffb40, 
> nr_to_call=-2, nr_calls=<value optimized out>) at kernel/notifier.c:93
> #4  0x00000000600459e4 in __atomic_notifier_call_chain (nh=<value optimized out>, 
> val=<value optimized out>, v=<value optimized out>) at kernel/notifier.c:182
> #5  atomic_notifier_call_chain (nh=<value optimized out>, val=<value optimized out>, 
> v=<value optimized out>) at kernel/notifier.c:191
> #6  0x00000000601a56d0 in panic (fmt=0x601f3050 "Kernel mode fault at addr 0x%lx, ip 0x%lx")
> at kernel/panic.c:115
> #7  0x00000000600145df in segv (fi=..., ip=1611852984, is_user=0, regs=0x6024fa10)
> at arch/um/kernel/trap.c:201
> #8  0x000000006001463e in segv_handler (sig=<value optimized out>, regs=<value optimized out>)
> at arch/um/kernel/trap.c:147
> #9  0x00000000600211a4 in sig_handler_common (sig=11, sc=0x6024fbe8) at arch/um/os-Linux/signal.c:49
> #10 0x00000000600212ea in sig_handler (sig=<value optimized out>, sc=<value optimized out>)
> at arch/um/os-Linux/signal.c:226
> #11 0x000000006002151c in handle_signal (sig=<value optimized out>, sc=0x6024fbe8)
(Continue reading)

Jan Kiszka | 10 May 2010 19:43
Picon

Re: uml: Error with Linked list debugging on

Lukas Czerner wrote:
> Hi,
> 
> I have got an error when booting uml with Linked list manipulation
> debugging turned on. The crash occurs in the exact moment when the
> consoles are showing up - it just blinks and crush. Here is the
> backtrace:
> 
> 
> #0  0x0000003cb8233e14 in abort () from /lib64/libc.so.6
> #1  0x00000000600220b2 in os_dump_core () at arch/um/os-Linux/util.c:119
> #2  0x00000000600147c1 in panic_exit (self=<value optimized out>, unused1=<value optimized out>, 
>     unused2=<value optimized out>) at arch/um/kernel/um_arch.c:233
> #3  0x0000000060045996 in notifier_call_chain (nl=<value optimized out>, val=0, v=0x602ffb40, 
> nr_to_call=-2, nr_calls=<value optimized out>) at kernel/notifier.c:93
> #4  0x00000000600459e4 in __atomic_notifier_call_chain (nh=<value optimized out>, 
> val=<value optimized out>, v=<value optimized out>) at kernel/notifier.c:182
> #5  atomic_notifier_call_chain (nh=<value optimized out>, val=<value optimized out>, 
> v=<value optimized out>) at kernel/notifier.c:191
> #6  0x00000000601a56d0 in panic (fmt=0x601f3050 "Kernel mode fault at addr 0x%lx, ip 0x%lx")
> at kernel/panic.c:115
> #7  0x00000000600145df in segv (fi=..., ip=1611852984, is_user=0, regs=0x6024fa10)
> at arch/um/kernel/trap.c:201
> #8  0x000000006001463e in segv_handler (sig=<value optimized out>, regs=<value optimized out>)
> at arch/um/kernel/trap.c:147
> #9  0x00000000600211a4 in sig_handler_common (sig=11, sc=0x6024fbe8) at arch/um/os-Linux/signal.c:49
> #10 0x00000000600212ea in sig_handler (sig=<value optimized out>, sc=<value optimized out>)
> at arch/um/os-Linux/signal.c:226
> #11 0x000000006002151c in handle_signal (sig=<value optimized out>, sc=0x6024fbe8)
>     at arch/um/os-Linux/signal.c:158
(Continue reading)

Paolo Giarrusso | 16 May 2010 14:43
Picon
Gravatar

Re: uml: Error with Linked list debugging on

On Mon, May 10, 2010 at 19:43, Jan Kiszka <jan.kiszka <at> web.de> wrote:
> Lukas Czerner wrote:
>> Hi,
>>
>> I have got an error when booting uml with Linked list manipulation
>> debugging turned on. The crash occurs in the exact moment when the
>> consoles are showing up - it just blinks and crush. Here is the
>> backtrace:
>>
>>
>> #0  0x0000003cb8233e14 in abort () from /lib64/libc.so.6
>> #1  0x00000000600220b2 in os_dump_core () at arch/um/os-Linux/util.c:119
>> #2  0x00000000600147c1 in panic_exit (self=<value optimized out>, unused1=<value optimized out>,
>>     unused2=<value optimized out>) at arch/um/kernel/um_arch.c:233
>> #3  0x0000000060045996 in notifier_call_chain (nl=<value optimized out>, val=0, v=0x602ffb40,
>> nr_to_call=-2, nr_calls=<value optimized out>) at kernel/notifier.c:93
>> #4  0x00000000600459e4 in __atomic_notifier_call_chain (nh=<value optimized out>,
>> val=<value optimized out>, v=<value optimized out>) at kernel/notifier.c:182
>> #5  atomic_notifier_call_chain (nh=<value optimized out>, val=<value optimized out>,
>> v=<value optimized out>) at kernel/notifier.c:191
>> #6  0x00000000601a56d0 in panic (fmt=0x601f3050 "Kernel mode fault at addr 0x%lx, ip 0x%lx")
>> at kernel/panic.c:115
>> #7  0x00000000600145df in segv (fi=..., ip=1611852984, is_user=0, regs=0x6024fa10)
>> at arch/um/kernel/trap.c:201
>> #8  0x000000006001463e in segv_handler (sig=<value optimized out>, regs=<value optimized out>)
>> at arch/um/kernel/trap.c:147
>> #9  0x00000000600211a4 in sig_handler_common (sig=11, sc=0x6024fbe8) at arch/um/os-Linux/signal.c:49
>> #10 0x00000000600212ea in sig_handler (sig=<value optimized out>, sc=<value optimized out>)
>> at arch/um/os-Linux/signal.c:226
>> #11 0x000000006002151c in handle_signal (sig=<value optimized out>, sc=0x6024fbe8)
(Continue reading)

Jan Kiszka | 16 May 2010 15:16
Picon

Re: uml: Error with Linked list debugging on

Paolo Giarrusso wrote:
> On Mon, May 10, 2010 at 19:43, Jan Kiszka <jan.kiszka <at> web.de> wrote:
>> Lukas Czerner wrote:
>>> Hi,
>>>
>>> I have got an error when booting uml with Linked list manipulation
>>> debugging turned on. The crash occurs in the exact moment when the
>>> consoles are showing up - it just blinks and crush. Here is the
>>> backtrace:
>>>
>>>
>>> #0  0x0000003cb8233e14 in abort () from /lib64/libc.so.6
>>> #1  0x00000000600220b2 in os_dump_core () at arch/um/os-Linux/util.c:119
>>> #2  0x00000000600147c1 in panic_exit (self=<value optimized out>, unused1=<value optimized out>,
>>>     unused2=<value optimized out>) at arch/um/kernel/um_arch.c:233
>>> #3  0x0000000060045996 in notifier_call_chain (nl=<value optimized out>, val=0, v=0x602ffb40,
>>> nr_to_call=-2, nr_calls=<value optimized out>) at kernel/notifier.c:93
>>> #4  0x00000000600459e4 in __atomic_notifier_call_chain (nh=<value optimized out>,
>>> val=<value optimized out>, v=<value optimized out>) at kernel/notifier.c:182
>>> #5  atomic_notifier_call_chain (nh=<value optimized out>, val=<value optimized out>,
>>> v=<value optimized out>) at kernel/notifier.c:191
>>> #6  0x00000000601a56d0 in panic (fmt=0x601f3050 "Kernel mode fault at addr 0x%lx, ip 0x%lx")
>>> at kernel/panic.c:115
>>> #7  0x00000000600145df in segv (fi=..., ip=1611852984, is_user=0, regs=0x6024fa10)
>>> at arch/um/kernel/trap.c:201
>>> #8  0x000000006001463e in segv_handler (sig=<value optimized out>, regs=<value optimized out>)
>>> at arch/um/kernel/trap.c:147
>>> #9  0x00000000600211a4 in sig_handler_common (sig=11, sc=0x6024fbe8) at arch/um/os-Linux/signal.c:49
>>> #10 0x00000000600212ea in sig_handler (sig=<value optimized out>, sc=<value optimized out>)
>>> at arch/um/os-Linux/signal.c:226
(Continue reading)

Jan Kiszka | 16 May 2010 16:07
Picon

Re: uml: Error with Linked list debugging on

Jan Kiszka wrote:
> Paolo Giarrusso wrote:
>> On Mon, May 10, 2010 at 19:43, Jan Kiszka <jan.kiszka <at> web.de> wrote:
>>> Lukas Czerner wrote:
>>>> Hi,
>>>>
>>>> I have got an error when booting uml with Linked list manipulation
>>>> debugging turned on. The crash occurs in the exact moment when the
>>>> consoles are showing up - it just blinks and crush. Here is the
>>>> backtrace:
>>>>
>>>>
>>>> #0  0x0000003cb8233e14 in abort () from /lib64/libc.so.6
>>>> #1  0x00000000600220b2 in os_dump_core () at arch/um/os-Linux/util.c:119
>>>> #2  0x00000000600147c1 in panic_exit (self=<value optimized out>, unused1=<value optimized out>,
>>>>     unused2=<value optimized out>) at arch/um/kernel/um_arch.c:233
>>>> #3  0x0000000060045996 in notifier_call_chain (nl=<value optimized out>, val=0, v=0x602ffb40,
>>>> nr_to_call=-2, nr_calls=<value optimized out>) at kernel/notifier.c:93
>>>> #4  0x00000000600459e4 in __atomic_notifier_call_chain (nh=<value optimized out>,
>>>> val=<value optimized out>, v=<value optimized out>) at kernel/notifier.c:182
>>>> #5  atomic_notifier_call_chain (nh=<value optimized out>, val=<value optimized out>,
>>>> v=<value optimized out>) at kernel/notifier.c:191
>>>> #6  0x00000000601a56d0 in panic (fmt=0x601f3050 "Kernel mode fault at addr 0x%lx, ip 0x%lx")
>>>> at kernel/panic.c:115
>>>> #7  0x00000000600145df in segv (fi=..., ip=1611852984, is_user=0, regs=0x6024fa10)
>>>> at arch/um/kernel/trap.c:201
>>>> #8  0x000000006001463e in segv_handler (sig=<value optimized out>, regs=<value optimized out>)
>>>> at arch/um/kernel/trap.c:147
>>>> #9  0x00000000600211a4 in sig_handler_common (sig=11, sc=0x6024fbe8) at arch/um/os-Linux/signal.c:49
>>>> #10 0x00000000600212ea in sig_handler (sig=<value optimized out>, sc=<value optimized out>)
(Continue reading)

Paolo Giarrusso | 17 May 2010 02:30
Picon
Gravatar

Re: uml: Error with Linked list debugging on

On Sun, May 16, 2010 at 16:07, Jan Kiszka <jan.kiszka <at> web.de> wrote:
> Jan Kiszka wrote:
>> Paolo Giarrusso wrote:
>>> On Mon, May 10, 2010 at 19:43, Jan Kiszka <jan.kiszka <at> web.de> wrote:
>>>> Lukas Czerner wrote:

>> Right, there was more broken. Besides the locking fix, this should do
>> the trick by avoiding the recursive free_winch call:

>> diff --git a/arch/um/drivers/line.c b/arch/um/drivers/line.c
>> index d85fcb9..fa66eb4 100644
>> --- a/arch/um/drivers/line.c
>> +++ b/arch/um/drivers/line.c
>>  <at>  <at>  -731,8 +731,10  <at>  <at>  static void free_winch(struct winch *winch, int free_irq_ok)
>>
>>       if (winch->pid != -1)
>>               os_kill_process(winch->pid, 1);
>> -     if (winch->fd != -1)
>> +     if (winch->fd != -1) {
>>               os_close_file(winch->fd);
>> +             winch->fd = -1;
>> +     }
>>       if (winch->stack != 0)
>>               free_stack(winch->stack, 0);
>>       if (free_irq_ok)
>>
>> (note: untested)
>
> Well, thought about it again, this is the result:

(Continue reading)

Antoine Martin | 19 May 2010 14:57
Picon
Favicon

something broke hppfs

   LD      fs/hostfs/hostfs.o
   LD      fs/hostfs/built-in.o
   CC      fs/hppfs/hppfs.o
fs/hppfs/hppfs.c: In function 'hppfs_fill_super':
fs/hppfs/hppfs.c:721: error: dereferencing pointer to incomplete type
make[2]: *** [fs/hppfs/hppfs.o] Error 1
make[1]: *** [fs/hppfs] Error 2
make: *** [fs] Error 2

------------------------------------------------------------------------------
Toralf Förster | 22 May 2010 17:36
Picon
Picon

kernel crash with 2.6.34-07097-gf4b87de

Well,

probably too early b/c the merge window is open yet but anyway:
here's the what happend at a ThinkPad T400 running a vanilla 2.6.34 kernel as 
the host system at an almost stable Gentoo:

tfoerste <at> n22 ~ $ start_uml.sh ~/devel/linux-2.6/linux 
Locating the bottom of the address space ... 0x1000
Locating the top of the address space ... 0xc0000000
Core dump limits :
        soft - NONE
        hard - NONE
Checking that ptrace can change system call numbers...OK
Checking syscall emulation patch for ptrace...OK
Checking advanced syscall emulation patch for ptrace...OK
Checking for tmpfs mount on /dev/shm...OK
Checking PROT_EXEC mmap in /dev/shm/...OK
Checking for the skas3 patch in the host:
  - /proc/mm...not found: No such file or directory
  - PTRACE_FAULTINFO...not found
  - PTRACE_LDT...not found
UML running in SKAS0 mode
Adding 31469568 bytes to physical memory to account for exec-shield gap
Linux version 2.6.34-07097-gf4b87de (tfoerste <at> n22) (gcc version 4.3.4 (Gentoo 
4.3.4 p1.1, pie-10.1.5) ) #1 Sat May 22 10:53:57 CEST 2010
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 72646
Kernel command line: ubda=/home/tfoerste/virtual/uml/gentoo_root_fs 
ubdb=/home/tfoerste/virtual/uml/swap_fs eth0=tuntap,,,192.168.0.253 mem=256M 
root=98:0
PID hash table entries: 2048 (order: 1, 8192 bytes)
(Continue reading)

Geert Uytterhoeven | 30 May 2010 17:18

Re: current git kernel crashes UML system during boot

On Sun, May 30, 2010 at 17:02, Borislav Petkov <bp <at> alien8.de> wrote:
> From: Geert Uytterhoeven <geert <at> linux-m68k.org>
> Date: Sun, May 30, 2010 at 01:57:05PM +0200
>
>> On Sun, May 30, 2010 at 13:39, Geert Uytterhoeven <geert <at> linux-m68k.org> wrote:
>> > 2010/5/27 Toralf Förster <toralf.foerster <at> gmx.de>:
>> >> I bisected it to this :
>>
>> > After fixing the missing/superfluous slab inclusion issues, I bisected
>> > it further to
>> >
>> > commit d61931d89be506372d01a90d1755f6d0a9fafe2d
>> > Author: Borislav Petkov <borislav.petkov <at> amd.com>
>> > Date:   Fri Mar 5 17:34:46 2010 +0100
>> >
>> >    x86: Add optimized popcnt variants
>> >
>> >    Add support for the hardware version of the Hamming weight function,
>> >    popcnt, present in CPUs which advertize it under CPUID, Function
>> >    0x0000_0001_ECX[23]. On CPUs which don't support it, we fallback to the
>> >    default lib/hweight.c sw versions.
>> >
>> >    A synthetic benchmark comparing popcnt with __sw_hweight64 showed almost
>> >    a 3x speedup on a F10h machine.
>> >
>> >    Signed-off-by: Borislav Petkov <borislav.petkov <at> amd.com>
>> >    LKML-Reference: <20100318112015.GC11152 <at> aftab>
>> >    Signed-off-by: H. Peter Anvin <hpa <at> zytor.com>
>> >
>> > I reverted that commit on top of current mainline (and fixed up the
(Continue reading)


Gmane