On Friday, July 09, 2010, Linus Torvalds wrote: > On Thu, Jul 8, 2010 at 4:33 PM, Rafael J. Wysocki <rjw@xxxxxxx> wrote: > > > > Unresolved regressions > > ---------------------- > > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16353 > > Subject : 2.6.35 regression > > Submitter : Zeev Tarantov <zeev.tarantov@xxxxxxxxx> > > Date : 2010-07-05 13:04 (4 days old) > > Message-ID : <loom.20100705T144459-919@xxxxxxxxxxxxxx> > > References : http://marc.info/?l=linux-kernel&m=127836002702522&w=2 > > This is a gcc-4.5 issue. Whether it's also something that we should > change in the kernel is unclear, but at least as of now, the rule is > that you cannot compile the kernel with gcc-4.5. No idea whether the > compiler is just entirely broken, or whether it's just that it > triggers something iffy by being overly clever. This claims to fix it, though: https://patchwork.kernel.org/patch/110988/ > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16346 > > Subject : 2.6.35-rc3-git8 - include/linux/fdtable.h:88 invoked rcu_dereference_check() without protection! > > Submitter : Miles Lane <miles.lane@xxxxxxxxx> > > Date : 2010-07-04 22:04 (5 days old) > > Message-ID : <AANLkTinof0k28rk4rMr66aubxcRL2rFa5ZEArj1lqD3o@xxxxxxxxxxxxxx> > > References : http://marc.info/?l=linux-kernel&m=127828107815930&w=2 > > I'm not entirely sure if these RCU proving things should count as regressions. > > Sure, the option to enable RCU proving is new, but the things it > reports about generally are not new - and they are usually not even > bugs in the sense that they necessarily cause any real problems. > > That particular one is in the single-thread optimizated case for fget_light, ie > > if (likely((atomic_read(&files->count) == 1))) { > file = fcheck_files(files, fd); > > where I think it should be entirely safe in all ways without any > locking. So I think it's a false positive too. OK, so I'm going to close these bugs. ... > > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16333 > > Subject : iwl3945: HARDWARE GONE?? > > Submitter : Priit Laes <plaes@xxxxxxxxx> > > Date : 2010-07-02 16:02 (7 days old) > > Message-ID : <1278086575.2889.8.camel@chi> > > References : http://marc.info/?l=linux-kernel&m=127808659705983&w=2 > > This either got fixed, or will be practically impossible to debug. The > reporter ends up being unable to reproduce the issue. Closed as unreproducible. ... > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16330 > > Subject : Dynamic Debug broken on 2.6.35-rc3? > > Submitter : Thomas Renninger <trenn@xxxxxxx> > > Date : 2010-07-01 15:44 (8 days old) > > Message-ID : <201007011744.19564.trenn@xxxxxxx> > > References : http://marc.info/?l=linux-kernel&m=127799907218877&w=2 > > There's a suggested patch in > > http://marc.info/?l=linux-kernel&m=127862524404291&w=2 > > but no reply to it yet. Patch information added to the bug entry (it's been confirmed to work). > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16329 > > Subject : 2.6.35-rc3: Load average climbing to 3+ with no apparent reason: CPU 98% idle, with hardly no I/O > > Submitter : Török Edwin <edwintorok@xxxxxxxxx> > > Date : 2010-07-01 7:40 (8 days old) > > Message-ID : <20100701104022.404410d6@debian> > > References : http://marc.info/?l=linux-kernel&m=127797005030536&w=2 > > This seems to be partly a confusion about what "load average" is. It's > not a CPU load, it's a system load average, and disk-wait processes > count towards it. He has some problem with his CD-ROM, and it sounds > like it might be hardware on the verge of going bad. Closed. > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16324 > > Subject : Oops while running fs_racer test on a POWER6 box against latest git > > Submitter : divya <dipraksh@xxxxxxxxxxxxxxxxxx> > > Date : 2010-06-30 11:34 (9 days old) > > Message-ID : <4C2B28F3.7000006@xxxxxxxxxxxxxxxxxx> > > References : http://marc.info/?l=linux-kernel&m=127789697303061&w=2 > > I wonder if this is the writeback problem. That POWER crash dump is > unreadable, so it's hard to tell, but the load in question makes that > at least likely. > > If so, it should hopefully be fixed in today's git (commit > 83ba7b071f30f7c01f72518ad72d5cd203c27502 and friends). OK, closed. > > Bug-entry : http://bugzilla.kernel.org/show_bug.cgi?id=16323 > > Subject : 2.6.35-rc3-git4 - kernel/sched.c:616 invoked rcu_dereference_check() without protection! > > Submitter : Miles Lane <miles.lane@xxxxxxxxx> > > Date : 2010-07-01 12:21 (8 days old) > > Message-ID : <AANLkTini6hz2LFeZi8CMUmY3xw1MU7NxmyesuxZ4oCdo@xxxxxxxxxxxxxx> > > References : http://marc.info/?l=linux-kernel&m=127798693125541&w=2 > > See earlier about these being marked as regressions, but it should be > fixed by commit dc61b1d6 ("sched: Fix PROVE_RCU vs cpu_cgroup"). Closed. ... > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16309 > > Subject : 2.6.35-rc3 oops trying to suspend. > > Submitter : Andrew Hendry <andrew.hendry@xxxxxxxxx> > > Date : 2010-06-27 12:40 (12 days old) > > Message-ID : <AANLkTinUH2p33-AWxOVDrLsNkn9rgEVrlwn5mfK7P8NH@xxxxxxxxxxxxxx> > > References : http://marc.info/?l=linux-kernel&m=127764249926781&w=2 > > I'm pretty sure this was fixed by Nick in commit 57439f878afa ("fs: > fix superblock iteration race"). Closed. ... > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16304 > > Subject : i915 - high number of wakeups > > Submitter : Enrico Bandiello <enban@xxxxxxxxxxxx> > > Date : 2010-06-27 09:52 (12 days old) > > Duplicate of that 16307 one. Closed. ... > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16230 > > Subject : inconsistent IN-HARDIRQ-W -> HARDIRQ-ON-W usage: fasync, 2.6.35-rc3 > > Submitter : Dominik Brodowski <linux@xxxxxxxxxxxxxxxxxxxx> > > Date : 2010-06-13 9:53 (26 days old) > > Message-ID : <20100613095305.GA13231@xxxxxxxxxxxxxxxxxxxxxxxxxx> > > References : http://marc.info/?l=linux-kernel&m=127642282208277&w=2 > > Fixed by commit f4985dc714d7. Closed. ... > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16205 > > Subject : acpi: freeing invalid memtype bf799000-bf79a000 > > Submitter : Marcin Slusarz <marcin.slusarz@xxxxxxxxx> > > Date : 2010-06-09 20:09 (30 days old) > > Message-ID : <20100609200910.GA2876@xxxxxxx> > > References : http://marc.info/?l=linux-kernel&m=127611427029914&w=2 > > http://marc.info/?l=linux-kernel&m=127688398513862&w=2 > > This should be fixed by commit b945d6b2554d ("rbtree: Undo augmented > trees performance damage and regression"). Yup, closed. > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16199 > > Subject : 2.6.35-rc2-git1 - include/linux/cgroup.h:534 invoked rcu_dereference_check() without protection! > > Submitter : Miles Lane <miles.lane@xxxxxxxxx> > > Date : 2010-06-07 18:14 (32 days old) > > Message-ID : <AANLkTin2pPqOUx--9fIX3BH3e-cU6oCRufijcx_4ozx5@xxxxxxxxxxxxxx> > > References : http://marc.info/?l=linux-kernel&m=127593447812015&w=2 > > Another RCU proving thing. And this one looks the same as the 16323 > one above, and fixed by the same commit as that one. Closed. > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16197 > > Subject : [BUG on 2.6.35-rc2] sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:11.0/0000:02:03.0/slot' > > Submitter : Ryan Wang <openspace.wang@xxxxxxxxx> > > Date : 2010-06-07 0:23 (32 days old) > > Message-ID : <AANLkTincwMZPnYW3S4uz4k2GOn52RpgBIBRfzyD010Yo@xxxxxxxxxxxxxx> > > References : http://marc.info/?l=linux-kernel&m=127587022219378&w=2 > > These should all be gone. See commit 3be434f0244ee by Jesse ('Revert > "PCI: create function symlinks in /sys/bus/pci/slots/N/"'). Yes, I've already closed it. ... > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16175 > > Subject : 2.6.35-rc1 system oom, many processes killed but memory not free > > Submitter : andrew hendry <andrew.hendry@xxxxxxxxx> > > Date : 2010-06-05 0:46 (34 days old) > > Message-ID : <AANLkTim7CiW-yfugZUAHZCqLvXKgt9CwolCvbLGdCLAk@xxxxxxxxxxxxxx> > > References : http://marc.info/?l=linux-kernel&m=127569877714937&w=2 > > Not a regression or a kernel bug at all. See the thread. Big ramdisk > filled up all of memory when it was filled by the builds. Closed. > > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=16145 > > Subject : Unable to boot unless "notsc" or "clocksource=hpet", or acpi_pad disabling the TSC > > Submitter : Tom Gundersen <teg@xxxxxxx> > > Date : 2010-06-07 13:11 (32 days old) > > Handled-By : Venkatesh Pallipadi <venki@xxxxxxxxxx> > > Len Brown <lenb@xxxxxxxxxx> > > This is not a regression. See the full bugzilla details. The same > problem persists at least back to 2.6.30 with his config. So it's > somehow specific to his particular config use that requires "notsc" to > boot. Dropped from the list. Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
