From: Peter Zijlstra <peterz@infradead.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Maciej Rutecki <maciej.rutecki@gmail.com>,
Florian Mickler <florian@mickler.org>
Subject: Re: [Bug #38292] slab vs lockdep vs debugobjects
Date: Mon, 27 Jun 2011 00:01:48 +0200 [thread overview]
Message-ID: <1309125708.4756.1.camel@twins> (raw)
In-Reply-To: <XWjMN7gBoXK.A.1zC.RZ6BOB@chimera>
On Sun, 2011-06-26 at 23:23 +0200, Rafael J. Wysocki wrote:
> This message has been generated automatically as a part of a summary report
> of recent regressions.
>
> The following bug entry is on the current list of known regressions
> from 2.6.39. Please verify if it still should be listed and let the tracking team
> know (either way).
who said its a regression?
next prev parent reply other threads:[~2011-06-26 22:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-26 21:18 3.0-rc4: Reported regressions from 2.6.39 Rafael J. Wysocki
2011-06-26 21:18 ` [Bug #36302] SandyBridge can't do s2disk with linux 3.0-rc1 Rafael J. Wysocki
2011-06-26 21:23 ` [Bug #37232] [3.0-rc1][NMI/DMAR][iwlagn] errors - PCI system error (SERR) for reason a1 on CPU 0 Rafael J. Wysocki
2011-06-27 23:37 ` Shawn Starr
2011-06-29 19:32 ` Rafael J. Wysocki
2011-06-30 3:57 ` Shawn Starr
2011-07-02 19:54 ` Florian Mickler
2011-06-26 21:23 ` [Bug #37432] sdhci-pci fails on 3.0.0-rc1 on Dell E6510 Rafael J. Wysocki
2011-06-26 21:23 ` [Bug #36452] Artifacts with 3.0-rc1 on SandyBridge Rafael J. Wysocki
2011-06-29 16:47 ` Jesse Barnes
2011-06-29 17:02 ` Alexander Zhaunerchyk
2011-06-29 19:28 ` Rafael J. Wysocki
2011-06-26 21:23 ` [Bug #36972] 3.0-rc1: DMAR errors from iwlagn Rafael J. Wysocki
2011-06-26 21:23 ` [Bug #37482] Driver: i915 - Starting with kernel 3.0.0-rc3, dual monitor freezes a Dell Latitude E6410 when a second monitor is connected at boot time Rafael J. Wysocki
2011-06-26 21:23 ` [Bug #37542] [OOPS] 3.0-rc1 cifs Rafael J. Wysocki
2011-06-26 22:05 ` Martijn Uffing
2011-06-26 22:37 ` Rafael J. Wysocki
2011-06-26 21:23 ` [Bug #37562] /scripts/depmod.sh ends up -rw-r--r-- 1 depmod.sh Rafael J. Wysocki
2011-06-26 21:23 ` [Bug #38012] Missing code to load firmware Rafael J. Wysocki
2011-06-26 22:10 ` Larry Finger
2011-06-26 22:38 ` Rafael J. Wysocki
2011-06-26 21:23 ` [Bug #38152] acpi_power_off lockdep splat Rafael J. Wysocki
2011-06-26 21:23 ` [Bug #38142] i915, framebuffer: wrong xoffset? Rafael J. Wysocki
2011-06-26 21:23 ` [Bug #38122] 3.0-rc3 WARNING: at drivers/gpu/drm/i915/i915_drv.c:340 gen6_gt_force_wake_put+0x29/0x52 [i915]() Rafael J. Wysocki
2011-06-27 7:33 ` Jens Axboe
2011-06-27 19:19 ` Rafael J. Wysocki
2011-06-26 21:23 ` [Bug #38292] slab vs lockdep vs debugobjects Rafael J. Wysocki
2011-06-26 22:01 ` Peter Zijlstra [this message]
2011-06-26 22:31 ` Ingo Molnar
2011-06-26 22:40 ` Rafael J. Wysocki
2011-06-26 22:52 ` Peter Zijlstra
2011-06-26 21:23 ` [Bug #38302] NFS crash in un-modified 3.0.0-rc3+, list corruption Rafael J. Wysocki
2011-06-26 21:50 ` 3.0-rc4: Reported regressions from 2.6.39 maximilian attems
2011-06-26 22:43 ` Rafael J. Wysocki
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=1309125708.4756.1.camel@twins \
--to=peterz@infradead.org \
--cc=florian@mickler.org \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.rutecki@gmail.com \
--cc=rjw@sisk.pl \
/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