lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 23 Feb 2012 23:51:20 +0100 (CET)
From:	"Rafael J. Wysocki" <>
To:	Linux Kernel Mailing List <>
Cc:	Maciej Rutecki <>,
	Florian Mickler <>,
	Andrew Morton <>,
	Linus Torvalds <>,
	Kernel Testers List <>,
	Network Development <>,
	Linux ACPI <>,
	Linux PM List <>,
	Linux SCSI List <>,
	Linux Wireless List <>,
	DRI <>
Subject: 3.3-rc4+: Reported regressions from 3.2

Hi all,

We definitely aren't 100% in business yet with the tracking of regressions,
but since the Bugzilla is operational again, we can collect reports at least.

I'd like to use this opportunity to thank Maciej Rutecki and Florian Mickler
for their hard work on the regression tracking and to clarify some things that
seem to have caused some confusion to happen recently.  Namely, we use the
kernel Bugzilla ( for the tracking of regressions
for the simple reason that our scripts generate the lists that are posted
(like the one below) out of Bugzilla entries created by us (and sometimes
by other people).  Those entries are used by us as a storage of information,
so we're going to add them even though some kernel developers don't seem to
like that.  We don't require developers to actually use those entries for
handling bug reports, we only need people to let us know when they should be
closed, because the bug has been fixed in the Linus' tree, or when there's
a patch available for the bug (in which case we mark it as "resolved", but
we don't close it just yet).  There is no reason for you to be openly hostile
to Maciej, who's been creating those entries recently, because he's just been
doing his job.  However, you may not want us to track kernel regressions at
all, in which case please let us know about that and we will find some other,
presumably equally interesting things to do. :-)

Yes, we might have been more verbose about what _exactly_ we've been using the
Bugzilla for and what our workflow is, but at the same time people might have
been a bit less harsh to someone who's been doing a service to the community,
completely voluntarily.



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.  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-02-23       15       13          13

Unresolved regressions

Bug-Entry	:
Subject		: i915 regression with 3.3-rc3+git
Submitter	: Riccardo Magliocchetti <>
Date		: 2012-02-17 20:48 (7 days old)
Message-ID	: <>
References	:

Bug-Entry	:
Subject		: OF-related boot crash in 3.3.0-rc3-00188-g3ec1e88
Submitter	: Meelis Roos <>
Date		: 2012-02-13 7:45 (11 days old)
Message-ID	: <>
References	:

Bug-Entry	:
Subject		: Possible circular locking dependency (3.3-rc2)
Submitter	: Felipe Balbi <>
Date		: 2012-02-08 12:41 (16 days old)
Message-ID	: <>
References	:

Bug-Entry	:
Subject		: 3.3-rc2 snd_pcm lockdep backtrace
Submitter	: Josh Boyer <>
Date		: 2012-02-06 14:56 (18 days old)
Message-ID	: <>
References	:

Bug-Entry	:
Subject		: kobject (ffff88003ffbb4b8): tried to init an initialized object, something is seriously wrong.
Submitter	: Konrad Rzeszutek Wilk <>
Date		: 2012-02-03 20:59 (21 days old)
Message-ID	: <>
References	:

Bug-Entry	:
Subject		: dosemu graphics broken in v3.3-rc1
Submitter	: Hans de Bruin <>
Date		: 2012-02-02 22:25 (22 days old)
Message-ID	: <>
References	:
Handled-By	: Jesse Barnes <>

Bug-Entry	:
Subject		: Regression 3.2 -> 3.3-rc1 10 sec hang at boot and resume, COMRESET failed
Submitter	: Norbert Preining <>
Date		: 2012-02-02 5:12 (22 days old)
Message-ID	: <>
References	:

Bug-Entry	:
Subject		: Regression in skge that started around acb42a3 (so past v3.3-rc1)
Submitter	: Konrad Rzeszutek Wilk <>
Date		: 2012-01-30 15:58 (25 days old)
Message-ID	: <>
References	:

Bug-Entry	:
Subject		: Hang deconfiguring network interface (in shutdown) on 3.3-rc1
Submitter	: James Bottomley <>
Date		: 2012-01-28 19:56 (27 days old)
Message-ID	: <>
References	:

Bug-Entry	:
Subject		: iwlagn is getting even worse with 3.3-rc1
Submitter	: Norbert Preining <>
Date		: 2012-01-24 1:36 (31 days old)
Message-ID	: <>
References	:

Bug-Entry	:
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 <>
Date		: 2012-01-23 18:06 (32 days old)
Message-ID	: <>
References	:

Bug-Entry	:
Subject		: [3.3-rc1] radeon stuck in kernel after lockup
Submitter	: Torsten Kaiser <>
Date		: 2012-01-21 19:03 (34 days old)
Message-ID	: <>
References	:
Handled-By	: Jérôme Glisse <>

Bug-Entry	:
Subject		: 3.3-rc1: compiling problems  nvme , l2cap_sock , mc13892-regulator , and snd-pcsp don't work
Submitter	: werner <>
Date		: 2012-01-20 18:52 (35 days old)
Message-ID	: <>
References	:

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

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:

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


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists