mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Barry K. Nathan" <barryn@pobox.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Andrew Morton" <akpm@osdl.org>,
	linux-kernel@vger.kernel.org,
	"Arjan van de Ven" <arjan@infradead.org>
Subject: Re: 2.6.17-rc5-mm2
Date: Sat, 3 Jun 2006 19:29:58 -0700	[thread overview]
Message-ID: <986ed62e0606031929g41ad18fbrb1788c26da86287f@mail.gmail.com> (raw)
In-Reply-To: <986ed62e0606031410h48efd8b7i3a89e1c7ba1cd778@mail.gmail.com>

On 6/3/06, Barry K. Nathan <barryn@pobox.com> wrote:
> I was already doing OPTIMIZE_FOR_SIZE. I didn't think of disabling
> FORCED_INLINING, thanks for reminding me of that. I managed to trim
> the kernel in other ways.

Hmm... disabling FORCED_INLINING didn't make much if any difference.

> > also, the latest combo patch:
> >
> >   http://redhat.com/~mingo/lockdep-patches/lockdep-combo-2.6.17-rc5-mm2.patch
> >
> > should have the floppy bug(s) fixed.
>
> I'll try that later today (and I'll also provide the
> /proc/latency_trace to help figure out the warning). In the meantime,
[snip]

Yes, the latest combo patch works. It still gives the warning, too
(copied here since it looks slightly different with the latency trace
patch added):

[  197.343620] (            idle-0    |#0): new 120978036 us user-latency.
[  197.343807] stopped custom tracer.
[  197.343948] BUG: warning at kernel/lockdep.c:1856/trace_hardirqs_on()
[  197.345928]  [<c010329b>] show_trace_log_lvl+0x5b/0x105
[  197.346359]  [<c0103896>] show_trace+0x1b/0x20
[  197.346759]  [<c01038ed>] dump_stack+0x1f/0x24
[  197.347159]  [<c012efa2>] trace_hardirqs_on+0xfb/0x185
[  197.348873]  [<c029b009>] _spin_unlock_irq+0x24/0x2d
[  197.350620]  [<e09034e8>] do_tx_done+0x171/0x179 [ns83820]
[  197.350895]  [<e090445c>] ns83820_irq+0x149/0x20b [ns83820]
[  197.351166]  [<c013b4b8>] handle_IRQ_event+0x1d/0x52
[  197.353216]  [<c013c6c2>] handle_level_irq+0x97/0xe1
[  197.355157]  [<c01048c3>] do_IRQ+0x8b/0xac
[  197.355612]  [<c0102d9d>] common_interrupt+0x25/0x2c

I've posted the /proc/latency_trace here:
http://members.cox.net/barrykn/linux/trace/latency_trace.bz2

It turns out that I was *way* off on the size in my last mail. It's
actually close to 9MB decompressed, 370K bz2-compressed.
-- 
-Barry K. Nathan <barryn@pobox.com>

  reply	other threads:[~2006-06-04  2:29 UTC|newest]

Thread overview: 97+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01  8:48 2.6.17-rc5-mm2 Andrew Morton
2006-06-01  9:30 ` 2.6.17-rc5-mm2 Mike Galbraith
2006-06-01  9:45   ` 2.6.17-rc5-mm2 Jens Axboe
2006-06-01  9:48   ` 2.6.17-rc5-mm2 Andrew Morton
2006-06-01  9:34 ` 2.6.17-rc5-mm2 Reuben Farrelly
2006-06-01  9:56   ` 2.6.17-rc5-mm2 Andrew Morton
2006-06-01 10:11     ` 2.6.17-rc5-mm2 Reuben Farrelly
2006-06-01 10:33       ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-01 10:53         ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-01 11:25           ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-01 11:59             ` 2.6.17-rc5-mm2 Reuben Farrelly
2006-06-01 16:22               ` 2.6.17-rc5-mm2 Andrew Morton
2006-06-01 22:15                 ` 2.6.17-rc5-mm2 Reuben Farrelly
2006-06-01 12:20           ` 2.6.17-rc5-mm2 Jan Beulich
2006-06-01 16:19             ` 2.6.17-rc5-mm2 Andrew Morton
2006-06-01 18:34               ` 2.6.17-rc5-mm2 Andrew Morton
2006-06-02  6:54             ` 2.6.17-rc5-mm2 Jan Beulich
2006-06-02  7:09               ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-02  7:22                 ` 2.6.17-rc5-mm2 Andrew Morton
2006-06-02  7:21                   ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-02  7:13               ` 2.6.17-rc5-mm2 Andrew Morton
2006-06-02  7:37             ` 2.6.17-rc5-mm2 Jan Beulich
2006-06-02  7:51               ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-02 20:53                 ` 2.6.17-rc5-mm2 Daniel Jacobowitz
2006-06-01 10:23     ` 2.6.17-rc5-mm2 Jeff Garzik
2006-06-01 11:42 ` 2.6.17-rc5-mm2 another compile error Helge Hafting
2006-06-01 16:29   ` Andrew Morton
2006-06-21 12:07     ` Adrian Bunk
2006-06-01 11:54 ` 2.6.17-rc5-mm2 stack unwind compile failure Helge Hafting
2006-06-01 16:30   ` Andrew Morton
2006-06-01 12:35 ` 2.6.17-rc5-mm2 md cause BUGs, and readahead speedup Helge Hafting
2006-06-01 12:54   ` Arjan van de Ven
2006-06-01 13:03 ` 2.6.17-rc5-mm2 link issues on s390 Cedric Le Goater
2006-06-01 13:28   ` Martin Schwidefsky
2006-06-01 13:53     ` Cedric Le Goater
2006-06-08  7:28       ` Heiko Carstens
2006-06-08  9:13         ` Cedric Le Goater
2006-06-08 11:02           ` Heiko Carstens
2006-06-08 12:45             ` Cedric Le Goater
2006-06-09  7:58               ` Heiko Carstens
2006-06-01 15:35 ` 2.6.17-rc5-mm2 Jiri Slaby
2006-06-01 15:49   ` 2.6.17-rc5-mm2 Arjan van de Ven
2006-06-01 16:35     ` 2.6.17-rc5-mm2 Ben Collins
2006-06-05 11:28       ` [PATCH 2.6.17-rc5-mm3] ieee1394: hl_irqs_lock is taken in hardware interrupt context Stefan Richter
2006-06-05 11:31         ` [PATCH 2.6.17-rc5-mm3] ieee1394: adjust code formatting in highlevel.c Stefan Richter
2006-06-05 12:07         ` [PATCH 2.6.17-rc5-mm3] ieee1394: hl_irqs_lock is taken in hardware interrupt context Stefan Richter
2006-06-01 15:51 ` 2.6.17-rc5-mm2 Michal Piotrowski
2006-06-01 17:20   ` 2.6.17-rc5-mm2 Arjan van de Ven
2006-06-01 17:35     ` 2.6.17-rc5-mm2 Andrew Morton
2006-06-01 17:36       ` 2.6.17-rc5-mm2 Arjan van de Ven
2006-06-01 19:04     ` 2.6.17-rc5-mm2 Michal Piotrowski
2006-06-01 22:30       ` 2.6.17-rc5-mm2 Michal Piotrowski
2006-06-01 17:22   ` 2.6.17-rc5-mm2 Andrew Morton
2006-06-01 17:27     ` 2.6.17-rc5-mm2 Arjan van de Ven
2006-06-01 17:40       ` 2.6.17-rc5-mm2 Andrew Morton
2006-06-01 19:31         ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-01 21:51 ` 2.6.17-rc5-mm2 Jesper Juhl
2006-06-01 21:52   ` 2.6.17-rc5-mm2 Jesper Juhl
2006-06-01 22:25   ` 2.6.17-rc5-mm2 Barry K. Nathan
2006-06-01 22:40     ` 2.6.17-rc5-mm2 Andrew Morton
2006-06-01 22:32   ` 2.6.17-rc5-mm2 Barry K. Nathan
2006-06-01 22:52     ` 2.6.17-rc5-mm2 Andrew Morton
2006-06-02  0:07       ` 2.6.17-rc5-mm2 Barry K. Nathan
2006-06-02  0:28         ` 2.6.17-rc5-mm2 Andrew Morton
2006-06-02  0:43           ` 2.6.17-rc5-mm2 Barry K. Nathan
2006-06-02  0:58 ` 2.6.17-rc5-mm2 Barry K. Nathan
2006-06-02  1:38   ` 2.6.17-rc5-mm2 Andrew Morton
2006-06-02  6:02     ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-02 13:14     ` 2.6.17-rc5-mm2 Barry K. Nathan
2006-06-02 14:20       ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-02 18:01         ` 2.6.17-rc5-mm2 Barry K. Nathan
2006-06-02 18:06           ` 2.6.17-rc5-mm2 Barry K. Nathan
2006-06-02 20:53           ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-02 22:33             ` 2.6.17-rc5-mm2 Barry K. Nathan
2006-06-03  7:13               ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-03 14:41                 ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-03 21:10                   ` 2.6.17-rc5-mm2 Barry K. Nathan
2006-06-04  2:29                     ` Barry K. Nathan [this message]
2006-06-04  8:33                       ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-04  7:57                     ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-02 15:51       ` 2.6.17-rc5-mm2 Alan Cox
2006-06-02 18:21         ` 2.6.17-rc5-mm2 Barry K. Nathan
2006-06-02 18:25       ` 2.6.17-rc5-mm2 Andrew Morton
2006-06-02  3:23 ` 2.6.17-rc5-mm2 KAMEZAWA Hiroyuki
2006-06-02  5:06   ` 2.6.17-rc5-mm2 Andrew Morton
2006-06-02 10:09 ` 2.6.17-rc5-mm2 Paolo Ornati
2006-06-02 11:10   ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-02 11:17     ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-02 11:34       ` 2.6.17-rc5-mm2 Paolo Ornati
2006-06-02 14:13         ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-02 14:46           ` 2.6.17-rc5-mm2 Paolo Ornati
2006-06-02 15:10             ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-02 19:49             ` 2.6.17-rc5-mm2 Ingo Molnar
2006-06-02 20:09               ` 2.6.17-rc5-mm2 Paolo Ornati
2006-06-02 18:38 ` 2.6.17-rc5-mm2 Mel Gorman
2006-06-02 18:59   ` 2.6.17-rc5-mm2 Andrew Morton
2006-06-03 15:29     ` 2.6.17-rc5-mm2 Mel Gorman

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=986ed62e0606031929g41ad18fbrb1788c26da86287f@mail.gmail.com \
    --to=barryn@pobox.com \
    --cc=akpm@osdl.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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

all inboxes | Powered by JetHome®