Re: Linux 2.6.16-rc3

[Patrizio Bassi]

Andrew Morton ha scritto:
> We still have some serious bugs, several of which are in 2.6.15 as well:
>
> - The scsi_cmd leak, which I don't think is fixed.
>
> - The some-x86_64-boxes-use-GFP_DMA-from-bio-layer bug, which causes
>   oom-killings.
>
> - The skbuff_head_cache leak, which has been around since at least
>   2.6.11.  Another box-killer, but is seems very hard to hit. 
>   (mki@xxxxxxxxxx, "the dreaded oom-killer (reproducable in 2.6.11 -
>   2.6.16-rc1) :(")
>
> - http://bugzilla.kernel.org/show_bug.cgi?id=6060: an apparent ACPI
>   regression.
>
> - Nathan's "sysfs-related oops during module unload", which Greg seems to
>   have under control.
>
> - http://bugzilla.kernel.org/show_bug.cgi?id=6049 - another acpi
>   regression.  We have the actual offending commit here.
>
> - A couple of random tty-related oopses reported by Jesper Juhl.  We
>   don't know why these happened - they appear to not be related to the tty
>   buffering changes.
>
> - http://bugzilla.kernel.org/show_bug.cgi?id=6038, another box-killing
>   acpi regression.
>
> - Various reports similar to
>   http://bugzilla.kernel.org/show_bug.cgi?id=6011, seemingly related to USB
>   PCI quirk handling.
>
> - "Ben Castricum" <lk@xxxxxxxxxxxxxxx> reports that ppp has started
>   exhibiting mysterious failures (again).
>
> - Nasty warnings from scsi about kobject-layer things being called from
>   irq context.  James has a push-it-to-process-context patch which sadly
>   assumes kmalloc() is immortal, but no other fix seems to have offered
>   itself.
>
> - In http://bugzilla.kernel.org/show_bug.cgi?id=5989, Sanjoy Mahajan has
>   another regression, but he's off collecting more info.
>
> - Helge Hafting reports a usb printer regression - I don't know if that's
>   still live?
>
> - "Carlo E.  Prelz" <fluido@xxxxxxxxx> has another USB/ehci regression
>   ("ATI RS480-based motherboard: stuck while booting with kernel >= 2.6.15
>   rc1").
>
> - Gerrit Bruchhuser <gbruchhaeuser@xxxxxx> seems to have an aic7xxx
>   regression ("AHA-7850 doesn't detect scanner anymore") but he doesn't say
>   which kernel got it right.
>
> - http://bugzilla.kernel.org/show_bug.cgi?id=5914 - a sata bug (which is
>   quite unremarkable :(), but this one is reported to eat filesystems.
>
> - Patrizio Bassi <patrizio.bassi@xxxxxxxxx> has an alsa suspend
>   regression ("alsa suspend/resume continues to fail for ens1370")
>
> - Bjorn Nilsson <bni.swe@xxxxxxxxx> has an sk99lin regression ("3COM
>   3C940, does not work anymore after upgrade to 2.6.15")
>
> - Andrey Borzenkov <arvidjaar@xxxxxxx> has an acpi-cpufreq regression
>   ("cannot unload acpi-cpufreq")
>
> - "P.  Christeas" <p_christ@xxxxxx> had an autofs regression ("Regression
>   in Autofs, 2.6.15-git"), whic might be fixed now?
>
> - ghrt <ghrt@xxxxxxxxxxxxx> reports an alsa regression ("PROBLEM: SB
>   Live!  5.1 (emu10k1, rev.  0a) doesn't work with 2.6.15")
>
> - jinhong hu <jinhong.hu@xxxxxxxxx> reports what appears to be a qlogic
>   regression ("kernel 2.6.15 scsi problem")
>
> - Benjamin LaHaise <bcrl@xxxxxxxxx> had an NFS problem ("NFS processes
>   gettting stuck in D with currrent git").
>
>
>
> These are clear regressions, reported in the last month by people who are
> willing to test patches.  They're almost all in subsystems which have
> active and professional maintainers.
>
>   
Really sad to say, but my Alsa ens1370 regression due to suspend problem
is still there.
Only fix is reboot actually. Ready to patch :)

PS.

i have a bug similar to:
http://bugzilla.kernel.org/show_bug.cgi?id=6038 (marked as blocking by
Andrew)
on my laptop.

but my dma expiry problem only happens during suspend.
I have a Sis 630 chipset with a 2.5" hitachi drive.
Been there...for ages..i can say: always...never got a working 2.6 kernel.
However in my poor opinion it's not blocking on my system, just boring.


Patrizio
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/