Date: Mon, 29 Jan 2007 20:50:33 -0500 From: "Alexandre \"Sunny\" Kovalenko" <Alex.Kovalenko@verizon.net> To: Divacky Roman <xdivac02@stud.fit.vutbr.cz> Cc: emulation@freebsd.org, Alexander Leidinger <Alexander@Leidinger.net> Subject: Re: CFT/HEADS-UP: linux 2.6.16 emulation Message-ID: <1170121834.860.4.camel@RabbitsDen.RabbitsLawn.verizon.net> In-Reply-To: <20070129090447.GA18900@stud.fit.vutbr.cz> References: <20070120170723.34c223fb@Magellan.Leidinger.net> <1169604069.1132.3.camel@RabbitsDen.RabbitsLawn.verizon.net> <20070124090227.GA71602@stud.fit.vutbr.cz> <1169642370.1132.4.camel@RabbitsDen.RabbitsLawn.verizon.net> <20070124143357.GA24993@stud.fit.vutbr.cz> <1169686662.33062.7.camel@RabbitsDen.RabbitsLawn.verizon.net> <20070125082553.m64yjmoku88kgg8s@webmail.leidinger.net> <1170031737.7409.7.camel@RabbitsDen.RabbitsLawn.verizon.net> <20070129090447.GA18900@stud.fit.vutbr.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2007-01-29 at 10:04 +0100, Divacky Roman wrote: > On Sun, Jan 28, 2007 at 07:48:57PM -0500, Alexandre Sunny Kovalenko wrote: > > On Thu, 2007-01-25 at 08:25 +0100, Alexander Leidinger wrote: > > > Quoting "Alexandre \Sunny\ Kovalenko" <Alex.Kovalenko@verizon.net> > > > (from Wed, 24 Jan 2007 19:57:41 -0500): > > > > > > > > I can't test myself ATM, is there some text in dmesg / on the console > > > after doing the ping? Could you please run the LTP tests (described at > > > http://wiki.FreeBSD.org/linux-kernel) on your SMP system and compare > > > it with the results we have (http://wiki.FreeBSD.org/linux-kernel/ltp)? > > Is there any way to get to your raw LTP logs (as opposed to the pretty > > page)? At the moment, I have 130 failures in 2.4 mode and 138 failures > > in 2.6 mode. I can post logs and/or diffs someplace if they are of any > > interest. My system is current as 01/23/2007. > > > > I have also contracted panic while running 'growfiles' test in 2.4 mode, > > but I was not able to repeat that, and I was running some other stuff on > > the background, so it might not have been related to the linuxolator. If > > you'd like kernel dump from that, I can post it somewhere as well. > > I am definitely interested in the panic backtrace. Alexander is right -- looks like VM related thing: Unread portion of the kernel message buffer: Kernel page fault with the following non-sleepable locks held: exclusive sleep mutex vm object (standard object) r = 0 (0xc71e4000) locked @ /usr/src/sys/kern/vfs_bio.c:3427 KDB: stack backtrace: db_trace_self_wrapper(c068d13f) at db_trace_self_wrapper+0x25 kdb_backtrace(1,c4e136c0,c,e38a5a8c,e38a5a80,...) at kdb_backtrace+0x29 witness_warn(5,0,c06adc74) at witness_warn+0x192 trap(e38a5a8c) at trap+0x10f calltrap() at calltrap+0x6 --- trap 0xd8d65070, eip = 0, esp = 0x10202, ebp = 0x1d1c000 --- Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x42 fault code = supervisor read, page not present instruction pointer = 0x20:0xc0530fad stack pointer = 0x28:0xe38a5acc frame pointer = 0x28:0xe38a5ae4 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 34 (bufdaemon) I have switched to 2.6 mode and started emerge --sync, got two LORs and a panic afterwards. I was running X (silly me), so no backtrace this time: Jan 28 19:53:36 RabbitsDen kernel: lock order reversal: Jan 28 19:53:36 RabbitsDen kernel: 1st 0xc52918a0 emuldata->shared lock (emuldata->shared lock) @ /usr/src/sys/modules/li nux/../../compat/linux/linux_emul.c:117 Jan 28 19:53:36 RabbitsDen kernel: 2nd 0xc52918e0 emuldata lock (emuldata lock) @ /usr/src/sys/modules/linux/../../compat /linux/linux_emul.c:67 Jan 28 19:53:36 RabbitsDen kernel: KDB: stack backtrace: Jan 28 19:53:36 RabbitsDen kernel: db_trace_self_wrapper(c068d13f) at db_trace_self_wrapper+0x25 Jan 28 19:53:36 RabbitsDen kernel: kdb_backtrace(0,ffffffff,c070f1a0,c070f1c8,c06ca0ec,...) at kdb_backtrace+0x29 Jan 28 19:53:36 RabbitsDen kernel: witness_checkorder(c52918e0,9,c528e066,43) at witness_checkorder+0x586 Jan 28 19:53:36 RabbitsDen kernel: _sx_xlock(c52918e0,c528e066,43,c646e3a0,1d3e,...) at _sx_xlock+0x50 Jan 28 19:53:36 RabbitsDen kernel: em_find(c7bcc900,1,c52918a0,c528e066,75,...) at em_find+0x51 Jan 28 19:53:36 RabbitsDen kernel: linux_proc_init(c7bce1b0,1d3e,7d0f00,0,16,...) at linux_proc_init+0xbd Jan 28 19:53:36 RabbitsDen kernel: linux_clone(c7bce1b0,e864bd00) at linux_clone+0x8b Jan 28 19:53:36 RabbitsDen kernel: syscall(e864bd38) at syscall+0x256 Jan 28 19:53:36 RabbitsDen kernel: Xint0x80_syscall() at Xint0x80_syscall+0x20 Jan 28 19:53:36 RabbitsDen kernel: --- syscall (690504900), eip = 0x2, esp = 0xe864bd74, ebp = 0xbfbfe0bc --- Jan 28 19:53:36 RabbitsDen kernel: lock order reversal: Jan 28 19:53:36 RabbitsDen kernel: 1st 0xc52918e0 emuldata lock (emuldata lock) @ /usr/src/sys/modules/linux/../../compat /linux/linux_emul.c:67 Jan 28 19:53:36 RabbitsDen kernel: 2nd 0xc0700e00 proctree (proctree) @ /usr/src/sys/modules/linux/../../i386/linux/linux _machdep.c:461 Jan 28 19:53:36 RabbitsDen kernel: KDB: stack backtrace: Jan 28 19:53:36 RabbitsDen kernel: db_trace_self_wrapper(c068d13f) at db_trace_self_wrapper+0x25 Jan 28 19:53:36 RabbitsDen kernel: kdb_backtrace(0,ffffffff,c070f1c8,c0711978,c06ca0ec,...) at kdb_backtrace+0x29 Jan 28 19:53:36 RabbitsDen kernel: witness_checkorder(c0700e00,9,c528e50d,1cd) at witness_checkorder+0x586 Jan 28 19:53:36 RabbitsDen kernel: _sx_xlock(c0700e00,c528e50d,1cd,0,16,...) at _sx_xlock+0x50 Jan 28 19:53:36 RabbitsDen kernel: linux_clone(c7bce1b0,e864bd00) at linux_clone+0x2a8 Jan 28 19:53:36 RabbitsDen kernel: syscall(e864bd38) at syscall+0x256 Jan 28 19:53:36 RabbitsDen kernel: Xint0x80_syscall() at Xint0x80_syscall+0x20 Jan 28 19:53:36 RabbitsDen kernel: --- syscall (690504900), eip = 0x2, esp = 0xe864bd74, ebp = 0xbfbfe0bc --- Do you have wiki page with known LORs and/or panics to ignore for now? -- Alexandre "Sunny" Kovalenko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1170121834.860.4.camel>