From: Ingo Molnar <mingo@elte.hu>
To: Arjan van de Ven <arjan@infradead.org>, Avi Kivity <avi@redhat.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linus 2.6.29-rc4
Date: Mon, 9 Feb 2009 09:28:16 +0100 [thread overview]
Message-ID: <20090209082816.GA14808@elte.hu> (raw)
In-Reply-To: <20090208172111.6941cd3e@infradead.org>
* Arjan van de Ven <arjan@infradead.org> wrote:
> On Sun, 8 Feb 2009 13:01:04 -0800 (PST)
> Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> >
> > Another week (and a half), another -rc.
> >
> > Arch updates (sparc, blackfin), driver updates (dvb, mmc, ide), ACPI
> > updates, FS updates (ubifs, btrfs), you name it. It's all there.
> >
> > But more importantly, people really have been working on regressions,
> > and hopefully this closes a nice set of the top one, and hopefully
> > without introducing too many new ones.
> >
> > Linus
>
>
> I just looked at the top -rc3 oopses/warnings/etc
>
> quick summary of the top ones:
> (manual rather than the normal automated scripts, so the format is
> different)
> "regulars" that happened a lot prior to .29 (eg clearly non-regressions) I marked with a *
>
> Oopses: 78 oopses reported
> --------------------------
> 12 times i915_driver_irq_handler http://www.kerneloops.org/searchweek.php?search=i915_driver_irq_handler
> 8 times apic_mmio_read http://www.kerneloops.org/searchweek.php?search=apic_mmio_read
The last one seems KVM related.
Ingo
next prev parent reply other threads:[~2009-02-09 8:29 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 21:01 Linus Torvalds
2009-02-09 1:21 ` Arjan van de Ven
2009-02-09 8:28 ` Ingo Molnar [this message]
2009-02-09 12:18 ` Avi Kivity
2009-02-09 13:34 ` Gerd Hoffmann
2009-02-09 15:04 ` Steven Noonan
2009-02-09 18:26 ` Oopses and ACPI problems (Linus 2.6.29-rc4) Darren Salt
2009-02-09 23:49 ` Ingo Molnar
2009-02-10 14:12 ` Darren Salt
2009-02-10 14:54 ` [PATCH 2.6.29-rc4] Restore ACPI reporting via /proc/acpi/events for EeePC & other Asus laptops Darren Salt
2009-02-24 11:31 ` Corentin Chary
2009-02-10 15:04 ` Oopses and ACPI problems (Linus 2.6.29-rc4) Matthew Garrett
2009-02-10 15:15 ` Darren Salt
2009-02-10 15:45 ` Matthew Garrett
2009-02-10 16:03 ` Darren Salt
2009-02-23 16:39 ` Matthew Garrett
2009-02-24 15:29 ` Darren Salt
2009-02-24 16:00 ` Matthew Garrett
2009-02-24 19:45 ` Darren Salt
2009-02-10 16:06 ` Corentin Chary
2009-02-10 19:16 ` Darren Salt
2009-02-11 2:03 ` Matthew Garrett
2009-02-11 1:23 ` yakui_zhao
2009-04-19 1:56 ` [PATCH] eee-laptop: Register as a pci-hotplug device Matthew Garrett
2009-04-19 7:20 ` Corentin Chary
2009-04-19 15:13 ` Matthew Garrett
2009-04-25 14:12 ` Corentin Chary
2009-04-26 17:16 ` Matthew Garrett
2009-04-26 20:51 ` Corentin Chary
2009-02-10 1:06 ` Oopses and ACPI problems (Linus 2.6.29-rc4) yakui_zhao
2009-02-10 14:02 ` [PATCH] Do not account for the address space used by hugetlbfs using VM_ACCOUNT V2 (Was Linus 2.6.29-rc4) Mel Gorman
2009-02-10 23:45 ` Andrew Morton
2009-02-11 11:15 ` Mel Gorman
2009-02-11 9:43 ` Andy Whitcroft
2009-02-11 10:30 ` Mel Gorman
2009-02-11 12:03 ` Andy Whitcroft
2009-02-11 14:20 ` Mel Gorman
2009-02-11 16:03 ` Andy Whitcroft
2009-02-11 16:34 ` Mel Gorman
2009-02-11 16:43 ` Andy Whitcroft
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=20090209082816.GA14808@elte.hu \
--to=mingo@elte.hu \
--cc=arjan@infradead.org \
--cc=avi@redhat.com \
--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
all inboxes | Powered by JetHome®