From: Arjan van de Ven <arjan@linux.intel.com>
To: "Jochen Voß" <jochen.voss@googlemail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Top kernel oopses/warnings for the week of May 30th 2008
Date: Fri, 30 May 2008 15:36:00 -0700 [thread overview]
Message-ID: <48408150.5030501@linux.intel.com> (raw)
In-Reply-To: <ef1cd66f0805301534t2dca0f4eh97dac71e10d3d683@mail.gmail.com>
Jochen Voß wrote:
> Hi Arjan,
>
> 2008/5/30 Arjan van de Ven <arjan@linux.intel.com>:
>> Rank 2: sysfs_add_one (warning)
>> Reported 243 times (759 total reports)
> [...]
>> Rank 3: mark_buffer_dirty (warning)
>> Reported 222 times (759 total reports)
>
> It seems like a strange coincidence that the first two entries have
> the same number of total reports. Is this really the case or is there
> something mixed up?
coincidence; I just recreated a new version of the report (so several hours later) and they're 1 appart now.
next prev parent reply other threads:[~2008-05-30 22:36 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
2008-06-10 12:42 ` Hugh Dickins
2008-05-30 22:34 ` Jochen Voß
2008-05-30 22:36 ` Arjan van de Ven [this message]
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=48408150.5030501@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=jochen.voss@googlemail.com \
--cc=linux-kernel@vger.kernel.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