Looks like that there are lots[1] of issues involved with .17 This bug should be used to track them and hopefully decide about it. [1]http://www.ppczone.org/forums/viewtopic.php?t=650
The possible issues so far are: Marvell Network driver panics the kernel Clock Skew under load JFS corruption XFS corruption (unverified) The Marvell Network issue might be a show stopper on PegII boards. dholm is going to try to get the panic message so we can look into it. I'm not sure what to say about the Clock Skew under load issue, perhaps a preempt or HZ setting. We would need to look into it, but it's certainly not happening on all machines. The JFS issue linked by Luca was after two lockups. Since this was on a PegII as well, perhaps it's possible that the JFS corruption is from the dirty shutdown from the Marvell panic. The XFS issue has been open since 2.6.15 with nobody else confirming or denying. Does anyone have anything else to add?
* Hardware clock on the Pegasos reset
* Hardware clock on the Pegasos reset it shows now May 24 1970 * cryptsetup-luks isn't able to locate the luks-header and the stored password without any application-change, it works again with gentoo-sources-2.6.16-r9
For every bug which one of you can reproduce, please make sure it is filed on http://bugzilla.kernel.org and one of you are on the CC list. When a patch becomes available and gets merged, let me know.
I've got a panic and can reproduce the marvell issue. I'll look into getting it fixed.
*** Bug 140407 has been marked as a duplicate of this bug. ***
Perhaps the XFS issue was related to this, it's fixed in the latest stable 2.6.17: http://marc.theaimsgroup.com/?l=linux-kernel&m=115070320401919&w=2 As for the marvell error, I don't see where it's coming from. My PegII is now so unstable (random memory/cpu bit flipping) that I can't get any useful testing done with it since it locks up randomly anyway. I've put photos of the marvell oops on http://dev.gentoo.org/~josejx/marvell/ if anyone wants to take a look. (Thanks Stu)
(In reply to comment #2) > * Hardware clock on the Pegasos reset
(In reply to comment #2) > * Hardware clock on the Pegasos reset it shows now May 24 1970 > * cryptsetup-luks isn't able to locate the luks-header and the stored password > without any application-change, it works again with gentoo-sources-2.6.16-r9 I booted gentoo-sources-2.6.17-r3 on my Pegasos and don't have any issues. cryptsetup and the hwclock are both working.
What is the status of getting this stablized for ppc soon? I would like to be able to use the bcm43xx drivers that are in this release.
It will be stabled shortly, but you certainly can help to test it out now, there's no reason for you to wait if you don't have a PegII.
Already marked stable.
