From: Ingo Molnar <mingo@elte.hu>
To: Hugh Dickins <hugh@veritas.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Greg KH <greg@kroah.com>, Jeff Garzik <jeff@garzik.org>,
Dave Jones <davej@redhat.com>
Subject: Re: Top kernel oopses/warnings for the week of May 30th 2008
Date: Mon, 9 Jun 2008 18:32:54 +0200 [thread overview]
Message-ID: <20080609163254.GA17191@elte.hu> (raw)
In-Reply-To: <Pine.LNX.4.64.0806030000110.9919@blonde.site>
* Hugh Dickins <hugh@veritas.com> wrote:
> Veering off at a tangent away from the oops: I was rather sobered to
> see all those traces of execve using kmap, I thought we were avoiding
> kmap like BKL in common paths these days (though it is convenient for
> symlinks). Would a patch something like that below, copying the
> filemap.c trick, be welcome?
FYI, i stuck this into -tip for testing and after some time i started
getting:
[ 8.540917] Freeing unused kernel memory: 304k freed
[ 12.368096] BUG: scheduling while atomic: ifup-eth/1820/0x10000001
[ 12.374144] Modules linked in:
[ 12.377175] Pid: 1820, comm: ifup-eth Not tainted 2.6.26-rc5-00029-ga252672-dirty #3490
[ 12.384031] [<c0131a39>] __schedule_bug+0x59/0x60
[ 12.388031] [<c06b1375>] schedule+0x465/0x8c0
[ 12.392031] [<c013eecf>] ? update_process_times+0x4f/0x60
[ 12.396031] [<c013b50f>] ? irq_exit+0x3f/0x70
[ 12.400451] [<c012164b>] ? smp_apic_timer_interrupt+0x5b/0x90
[ 12.406248] [<c0117038>] ? apic_timer_interrupt+0x28/0x30
[ 12.411702] [<c0131a58>] __cond_resched+0x18/0x30
[ 12.416466] [<c06b1838>] _cond_resched+0x28/0x30
[ 12.421141] [<c03720bb>] strnlen_user+0x2b/0x60
[ 12.425728] [<c018dd53>] copy_strings+0x63/0x210
[ 12.430403] [<c018f986>] do_execve+0x176/0x200
[ 12.434903] [<c0372007>] ? strncpy_from_user+0x37/0x60
[ 12.440031] [<c0114ade>] sys_execve+0x2e/0x60
[ 12.444447] [<c01165ae>] sysenter_past_esp+0x6a/0x90
[ 12.449469] =======================
[ 12.736676] eth1: link down
[ 12.736919] ADDRCONF(NETDEV_UP): eth1: link is not ready
it would occur about every 10 bootups with the same config. Bisection
led me to your patch.
Ingo
next prev parent reply other threads:[~2008-06-09 16:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 16:39 Top kernel oopses/warnings for the week of May 30th 2008 Arjan van de Ven
2008-05-30 19:19 ` Hugh Dickins
2008-05-30 21:43 ` Linus Torvalds
2008-05-30 21:49 ` Arjan van de Ven
2008-05-30 22:17 ` Arjan van de Ven
2008-05-30 22:00 ` Arjan van de Ven
2008-05-30 22:30 ` Linus Torvalds
2008-05-30 22:34 ` Arjan van de Ven
2008-05-30 22:55 ` Linus Torvalds
2008-05-31 0:41 ` Dave Jones
2008-06-02 23:44 ` Hugh Dickins
2008-06-03 0:00 ` Andrew Morton
2008-06-03 0:41 ` Hugh Dickins
2008-06-03 1:19 ` Andrew Morton
2008-06-09 16:32 ` Ingo Molnar [this message]
2008-06-10 12:42 ` Hugh Dickins
2008-05-30 22:34 ` Jochen Voß
2008-05-30 22:36 ` Arjan van de Ven
2008-06-02 0:02 ` James Morris
2008-06-02 2:27 ` Arjan van de Ven
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080609163254.GA17191@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=arjan@linux.intel.com \
--cc=davej@redhat.com \
--cc=greg@kroah.com \
--cc=hugh@veritas.com \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox