All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Maciej Rutecki <maciej.rutecki@gmail.com>,
	Florian Mickler <florian@mickler.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Kernel Testers List <kernel-testers@vger.kernel.org>,
	Network Development <netdev@vger.kernel.org>,
	Linux ACPI <linux-acpi@vger.kernel.org>,
	Linux PM List <linux-pm@lists.linux-foundation.org>,
	Linux SCSI List <linux-scsi@vger.kernel.org>,
	Linux Wireless List <linux-wireless@vger.kernel.org>,
	DRI <dri-devel@lists.freedesktop.org>
Subject: 3.3-rc6: Reported regressions from 3.2
Date: Sun,  4 Mar 2012 21:29:30 +0100 (CET)	[thread overview]
Message-ID: <FNlNbnGKWLP.A.dME.3F9UPB@chimera> (raw)

Hi all,

It looks like many people have switched away from the kernel Bugzilla
after the kernel.org outage and they are using various means of reporting
(and tracking) kernel bugs.  For this reason, it's becoming increasingly
difficult for us to track all of the possible sources of reports and we
are not aware of a number of them as a result.  To tackle this issue we
kindly request that regression reports be CCed or forwarded to the LKML
as stated below.

Thanks,
Rafael

-----------------------------------------------------------------------------

This message contains a list of some regressions from 3.2,
for which there are no fixes in the mainline known to the tracking team.
If any of them have been fixed already, please let us know.

If you know of any other unresolved regressions from 3.2, please let us
know either and we'll add them to the list.  Moreover, when you are
reporting a kernel regression, please send a CC of your report to the LKML
(or forward it to the LKML if you are not reporting the regression by e-mail)
with the word "regression" in the subject, as that will make it much
easier for us to find it.  Also, please let us know if any of the entries
below are invalid.

Each entry from the list will be sent additionally in an automatic reply
to this message with CCs to the people involved in reporting and handling
the issue.


Listed regressions statistics:

  Date          Total  Pending  Unresolved
  ----------------------------------------
  2012-03-04       23       15          15
  2012-02-23       15       13          13


Unresolved regressions
----------------------

Bug-Entry	: https://bugzilla.kernel.org/show_bug.cgi?id=42860
Subject		: 3.3.0-rc5: OOps in dql_completed (Broadcom tg3 driver)
Submitter	: Christoph Lameter <cl@gentwo.org>
Date		: 2012-03-01 21:13 (4 days old)
Message-ID	: <alpine.DEB.2.00.1203011505510.6685@router.home>
References	: http://marc.info/?l=linux-kernel&m=133063645224373&w=2


Bug-Entry	: https://bugzilla.kernel.org/show_bug.cgi?id=42850
Subject		: [BUG] Kernel Bug at fs/btrfs/volumes.c:3638
Submitter	: Nageswara R Sastry <rnsastry@linux.vnet.ibm.com>
Date		: 2012-02-24 10:53 (10 days old)
Message-ID	: <4F476959.2010400@linux.vnet.ibm.com>
References	: http://marc.info/?l=linux-kernel&m=133008013332251&w=2


Bug-Entry	: https://bugzilla.kernel.org/show_bug.cgi?id=42823
Subject		: WARNING: at block/genhd.c:1465
Submitter	: Christian Kujau <lists@nerdbynature.de>
Date		: 2012-02-21 11:00 (13 days old)
Message-ID	: <alpine.DEB.2.01.1202210246400.4930@trent.utfs.org>
References	: http://marc.info/?l=linux-kernel&m=132982259213941&w=2


Bug-Entry	: https://bugzilla.kernel.org/show_bug.cgi?id=42822
Subject		: [3.3.0-rc3][uvcvideo][regression] oops - uvc_video_clock_update
Submitter	: Shawn Starr <shawn.starr@rogers.com>
Date		: 2012-02-20 1:08 (14 days old)
Message-ID	: <5887142.ZMTDAjc4qf@segfault.sh0n.net>
References	: http://marc.info/?l=linux-kernel&m=132970057611642&w=2


Bug-Entry	: https://bugzilla.kernel.org/show_bug.cgi?id=42821
Subject		: alpha: futex regression bisected
Submitter	: Michael Cree <mcree@orcon.net.nz>
Date		: 2012-02-20 8:20 (14 days old)
First-Bad-Commit: http://git.kernel.org/linus/8d7718aa082aaf30a0b4989e1f04858952f941bc
Message-ID	: <4F420256.2090600@orcon.net.nz>
References	: http://marc.info/?l=linux-kernel&m=132972606917069&w=2


Bug-Entry	: https://bugzilla.kernel.org/show_bug.cgi?id=42776
Subject		: OF-related boot crash in 3.3.0-rc3-00188-g3ec1e88
Submitter	: Meelis Roos <mroos@linux.ee>
Date		: 2012-02-13 7:45 (21 days old)
Message-ID	: <alpine.SOC.1.00.1202130942030.1488@math.ut.ee>
References	: http://marc.info/?l=linux-kernel&m=132911916331615&w=2
		  http://marc.info/?l=linux-kernel&m=132993294018762&w=2


Bug-Entry	: https://bugzilla.kernel.org/show_bug.cgi?id=42761
Subject		: Possible circular locking dependency (3.3-rc2)
Submitter	: Felipe Balbi <balbi@ti.com>
Date		: 2012-02-08 12:41 (26 days old)
Message-ID	: <20120208124147.GF16334@legolas.emea.dhcp.ti.com>
References	: http://marc.info/?l=linux-kernel&m=132870492311858&w=2


Bug-Entry	: https://bugzilla.kernel.org/show_bug.cgi?id=42746
Subject		: 3.3-rc2 snd_pcm lockdep backtrace
Submitter	: Josh Boyer <jwboyer@redhat.com>
Date		: 2012-02-06 14:56 (28 days old)
Message-ID	: <20120206145621.GA4771@zod.bos.redhat.com>
References	: http://marc.info/?l=linux-kernel&m=132854040916172&w=2


Bug-Entry	: https://bugzilla.kernel.org/show_bug.cgi?id=42733
Subject		: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
Submitter	: Norbert Preining <preining@logic.at>
Date		: 2012-02-02 5:12 (32 days old)
Message-ID	: <20120202051258.GA15550@gamma.logic.tuwien.ac.at>
References	: http://marc.info/?l=linux-kernel&m=132815978615112&w=2


Bug-Entry	: https://bugzilla.kernel.org/show_bug.cgi?id=42713
Subject		: Regression in skge that started around acb42a3 (so past v3.3-rc1)
Submitter	: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Date		: 2012-01-30 15:58 (35 days old)
Message-ID	: <20120130155816.GA1400@phenom.dumpdata.com>
References	: http://marc.info/?l=linux-kernel&m=132793944220262&w=2


Bug-Entry	: https://bugzilla.kernel.org/show_bug.cgi?id=42707
Subject		: Hang deconfiguring network interface (in shutdown) on 3.3-rc1
Submitter	: James Bottomley <James.Bottomley@hansenpartnership.com>
Date		: 2012-01-28 19:56 (37 days old)
First-Bad-Commit: http://git.kernel.org/linus/92feeabf3f673767c6ee4cfc7fc224098446c1c1
Message-ID	: <1327780565.2924.24.camel@dabdike.int.hansenpartnership.com>
References	: http://marc.info/?l=linux-kernel&m=132778076214873&w=2


Bug-Entry	: https://bugzilla.kernel.org/show_bug.cgi?id=42686
Subject		: iwlagn is getting even worse with 3.3-rc1
Submitter	: Norbert Preining <preining@logic.at>
Date		: 2012-01-24 1:36 (41 days old)
Message-ID	: <20120124013625.GB18436@gamma.logic.tuwien.ac.at>
References	: http://marc.info/?l=linux-kernel&m=132736918325378&w=2


Bug-Entry	: https://bugzilla.kernel.org/show_bug.cgi?id=42683
Subject		: WARN... Device 'cpu1' does not have a release() function, it is broken and must be fixed. when doing 'xl vcpu-set <guest_id> 1'
Submitter	: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Date		: 2012-01-23 18:06 (42 days old)
Message-ID	: <20120123180601.GA24553@phenom.dumpdata.com>
References	: http://marc.info/?l=linux-kernel&m=132734233916154&w=2


Bug-Entry	: https://bugzilla.kernel.org/show_bug.cgi?id=42678
Subject		: [3.3-rc1] radeon stuck in kernel after lockup
Submitter	: Torsten Kaiser <just.for.lkml@googlemail.com>
Date		: 2012-01-21 19:03 (44 days old)
Message-ID	: <CAPVoSvSXMvRb=1itu9DjF+s=6zfAChvUxS-x=b8EV9kOZinNpA@mail.gmail.com>
References	: http://marc.info/?l=linux-kernel&m=132717279606670&w=2
Handled-By	: Jérôme Glisse <glisse@freedesktop.org>


Bug-Entry	: https://bugzilla.kernel.org/show_bug.cgi?id=42649
Subject		: Regression 3.2 -> 3.3-rc1 commit b4b583d4 inet/media keyboard: stuck "extra" keys
Submitter	: Duncan <1i5t5.duncan@cox.net>
Date		: 2012-01-24 18:18 (41 days old)
First-Bad-Commit: http://git.kernel.org/linus/b4b583d4e9a5ff28c4a150bb25a4fff5cd4dfbbd


For details, please visit the bug entries and follow the links given in
references.

As you can see, there is a Bugzilla entry for each of the listed regressions.
There also is a Bugzilla entry used for tracking the regressions from 3.2,
unresolved as well as resolved, at:

http://bugzilla.kernel.org/show_bug.cgi?id=42644

Please let the tracking team know if there are any Bugzilla entries that
should be added to the list in there.

Thanks!


             reply	other threads:[~2012-03-04 20:49 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-04 20:29 Rafael J. Wysocki [this message]
2012-03-04 20:29 ` [Bug #42649] Regression 3.2 -> 3.3-rc1 commit b4b583d4 inet/media keyboard: stuck "extra" keys Rafael J. Wysocki
2012-03-04 21:03   ` Jiri Kosina
2012-03-04 21:03     ` Jiri Kosina
2012-03-04 21:43     ` Rafael J. Wysocki
2012-03-04 21:43       ` Rafael J. Wysocki
2012-03-05 19:43       ` Jiri Kosina
2012-03-05 19:43         ` Jiri Kosina
2012-03-05  1:06     ` Duncan
2012-03-05  9:22       ` Jiri Kosina
2012-03-05  9:22         ` Jiri Kosina
2012-03-04 20:31 ` [Bug #42683] WARN... Device 'cpu1' does not have a release() function, it is broken and must be fixed. when doing 'xl vcpu-set <guest_id> 1' Rafael J. Wysocki
2012-03-04 20:31   ` Rafael J. Wysocki
2012-03-04 20:31 ` [Bug #42678] [3.3-rc1] radeon stuck in kernel after lockup Rafael J. Wysocki
2012-03-04 20:31   ` Rafael J. Wysocki
2012-03-04 20:31 ` [Bug #42733] Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed Rafael J. Wysocki
2012-03-04 20:31   ` Rafael J. Wysocki
2012-03-04 20:31 ` [Bug #42707] Hang deconfiguring network interface (in shutdown) on 3.3-rc1 Rafael J. Wysocki
2012-03-04 20:31   ` Rafael J. Wysocki
2012-03-04 20:31 ` [Bug #42686] iwlagn is getting even worse with 3.3-rc1 Rafael J. Wysocki
2012-03-04 20:31 ` [Bug #42713] Regression in skge that started around acb42a3 (so past v3.3-rc1) Rafael J. Wysocki
2012-03-05  1:03   ` Paul Gortmaker
2012-03-05  1:03     ` Paul Gortmaker
2012-03-04 20:31 ` [Bug #42746] 3.3-rc2 snd_pcm lockdep backtrace Rafael J. Wysocki
2012-03-04 20:31 ` [Bug #42776] OF-related boot crash in 3.3.0-rc3-00188-g3ec1e88 Rafael J. Wysocki
2012-03-04 20:31   ` Rafael J. Wysocki
2012-03-05  7:26   ` Meelis Roos
2012-03-04 20:31 ` [Bug #42761] Possible circular locking dependency (3.3-rc2) Rafael J. Wysocki
2012-03-04 20:31   ` Rafael J. Wysocki
2012-03-04 20:31 ` [Bug #42822] [3.3.0-rc3][uvcvideo][regression] oops - uvc_video_clock_update Rafael J. Wysocki
2012-03-04 20:31 ` [Bug #42823] WARNING: at block/genhd.c:1465 Rafael J. Wysocki
2012-03-04 20:31 ` [Bug #42821] alpha: futex regression bisected Rafael J. Wysocki
2012-03-04 20:31 ` [Bug #42860] 3.3.0-rc5: OOps in dql_completed (Broadcom tg3 driver) Rafael J. Wysocki
2012-03-04 20:31 ` [Bug #42850] [BUG] Kernel Bug at fs/btrfs/volumes.c:3638 Rafael J. Wysocki
2012-03-04 20:31   ` Rafael J. Wysocki
2012-03-05 16:04 ` [linux-pm] 3.3-rc6: Reported regressions from 3.2 Alan Stern
2012-03-05 16:04   ` Alan Stern
2012-03-05 19:01   ` Maciej Rutecki
2012-03-05 19:01     ` Maciej Rutecki

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=FNlNbnGKWLP.A.dME.3F9UPB@chimera \
    --to=rjw@sisk.pl \
    --cc=akpm@linux-foundation.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=florian@mickler.org \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=maciej.rutecki@gmail.com \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.