From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262918AbVG2VfZ (ORCPT ); Fri, 29 Jul 2005 17:35:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262878AbVG2VfS (ORCPT ); Fri, 29 Jul 2005 17:35:18 -0400 Received: from pop.gmx.de ([213.165.64.20]:31423 "HELO mail.gmx.net") by vger.kernel.org with SMTP id S262905AbVG2Vep (ORCPT ); Fri, 29 Jul 2005 17:34:45 -0400 X-Authenticated: #8834078 From: Dominik Karall To: Andrew Morton Subject: Re: 2.6.12-rc6-mm1 Date: Fri, 29 Jul 2005 23:37:14 +0200 User-Agent: KMail/1.8.2 Cc: linux-kernel@vger.kernel.org References: <20050607042931.23f8f8e0.akpm@osdl.org> <200507292319.21167.dominik.karall@gmx.net> <20050729142703.7e9494c4.akpm@osdl.org> In-Reply-To: <20050729142703.7e9494c4.akpm@osdl.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3490847.9MOpt1ekGm"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200507292337.14784.dominik.karall@gmx.net> X-Y-GMX-Trusted: 0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org --nextPart3490847.9MOpt1ekGm Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Friday 29 July 2005 23:27, Andrew Morton wrote: > Dominik Karall wrote: > > On Friday 29 July 2005 20:22, Andrew Morton wrote: > > > Dominik Karall wrote: > > > > On Friday 29 July 2005 06:54, Andrew Morton wrote: > > > > > Dominik Karall wrote: > > > > > > On Tuesday 07 June 2005 13:29, Andrew Morton wrote: > > > > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6= /2 > > > > > > >.6.1 2-rc 6/2. 6.12-rc6-mm1/ > > > > > > > > > > > > After looking in my dmesg output today, I saw following error > > > > > > with 2.6.12-rc6-mm1, maybe it's usefull to you. I don't know wh= en > > > > > > it exactly happens, cause I never used mono last time, I just d= id > > > > > > an emerge mono on my gentoo system, maybe this forced the > > > > > > failure. > > > > > > > > > > > > note: mono[26736] exited with preempt_count 1 > > > > > > scheduling while atomic: mono/0x10000001/26736 > > > > > > > > > > > > Call Trace:{schedule+122} > > > > > > {vprintk+635} > > > > > > {cond_resched+56} > > > > > > {unmap_vmas+1587} > > > > > > {exit_mmap+128} {mmput+31} > > > > > > {do_exit+438} > > > > > > {__dequeue_signal+501} > > > > > > {do_group_exit+280} > > > > > > {get_signal_to_deliver+1575} > > > > > > {do_signal+162} > > > > > > {default_wake_function+0} > > > > > > {sys_rt_sigreturn+577} > > > > > > {sysret_signal+28} > > > > > > {ptregscall_common+103} > > > > > > > > > > A couple of people reported this, but all seems to have gone quie= t. > > > > > Is it fixed in later -mm's? Is 2.6.13-rc4 running OK? > > > > > > > > > > Thanks. > > > > > > > > hi andrew! > > > > > > > > I'm sorry, but it's not fixed in current 2.6.13-rc3-mm3. I did an > > > > emerge mono right now to test it, and I got this one: > > > > Jul 29 15:26:37 [kernel] note: mono[11138] exited with preempt_count > > > > 1 Jul 29 15:26:50 [kernel] file[14627]: segfault at 00002aaaab453000 > > > > rip 00002aaaaaf652cf rsp 00007fffffe43b50 error 4 > > > > Jul 29 15:26:50 [kernel] file[14633]: segfault at 00002aaaab453000 > > > > rip 00002aaaaaf652cf rsp 00007fffffcc87a0 error 4 > > > > Jul 29 15:26:51 [kernel] file[14669]: segfault at 00002aaaab453000 > > > > rip 00002aaaaaf652cf rsp 00007fffff905f80 error 4 > > > > > > > > DEBUG_KERNEL/ PREEMPT/ SPINLOCK are enabled, but I didn't get more > > > > info about the bug. Did I forget any debug option? > > > > > > Gee, I don't know how to find this one. Do you know if the problem is > > > specific to -mm? > > > > Tested with 2.6.13-rc4 and it seems to work. Didn't get any error. > > Great, thanks for that. > > > So it seems to be -mm related. Do you suspect any patch which could cau= se > > the error? > > I wouldn't know, sorry. Possible the scheduler patches, possibly an > x86_64-specific patch. Is the problem repeatable? If so, a binary search > would only take ten build-n-boots ;) Yes, it is repeatable. I tested on lastest -mm about 4 times. Ok, I will tr= y=20 to find the right patch tomorrow, 10 build-n-boots would end up in morning = ;) btw, as the error occured in 2.6.12-rc6-mm1 too, it must be an old patch wh= ich=20 wasn't merged to linus tree till now...hope there aren't a lot of them :) --nextPart3490847.9MOpt1ekGm Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1-ecc0.1.6 (GNU/Linux) iQCVAwUAQuqhigvcoSHvsHMnAQJtAwP/YYo5JKuUvgllNKZbILfPNsQghGfzr9iT d6oBZ+187Dnsqkw7gcg9rDYa1ZKFlnA2WVEv8sHj3EfSyYxNrwVDtppikUfKHjQs o05mwg/GtkI0BFrmqFeevYPuWgyHQmge+8DFGfp8SOAcPJbyEX5O81rptv5H7al8 8ZCrlDNr6MU= =xc55 -----END PGP SIGNATURE----- --nextPart3490847.9MOpt1ekGm--