3.5.x is not yet ready to move to [core],
- ext4 regression is not fixed yet, will be fixed in 3.5.3
- watchdogs are completely broken
I'm not sure how much of a showstopper the watchdogs are, so please
shout out if this is a real problem.
If you have any other showstopper please let me know.
3.5.x is not yet ready to move to [core],
- ext4 regression is not fixed yet, will be fixed in 3.5.3
- watchdogs are completely broken
I'm not sure how much of a showstopper the watchdogs are, so please
shout out if this is a real problem.
If you have any other showstopper please let me know.
Am Donnerstag, den 23.08.2012, 16:10 +0200 schrieb Tobias Powalowski:
> Hi guys,
>
> 3.5.x is not yet ready to move to [core],
> - ext4 regression is not fixed yet, will be fixed in 3.5.3
> - watchdogs are completely broken
> I'm not sure how much of a showstopper the watchdogs are, so please
> shout out if this is a real problem.
> If you have any other showstopper please let me know.
On my Dell Latitude D410, it crashes on boot:
http://pastie.org/4575177
Am 23.08.2012 18:10, schrieb Bjoern Franke:
> Am Donnerstag, den 23.08.2012, 16:10 +0200 schrieb Tobias Powalowski:
>> Hi guys,
>>
>> 3.5.x is not yet ready to move to [core],
>> - ext4 regression is not fixed yet, will be fixed in 3.5.3
>> - watchdogs are completely broken
>> I'm not sure how much of a showstopper the watchdogs are, so please
>> shout out if this is a real problem.
>> If you have any other showstopper please let me know.
>
> On my Dell Latitude D410, it crashes on boot:
> http://pastie.org/4575177
>
> The graphics-chip is a "Intel 915GM/GMS/910GML".
I don't think we will block the move to core on an isolated hardware
crash that affects only a single user.
Still, can you give us the link to the kernel bugzilla report for this
crash?
08-23-2012, 04:29 PM
Geert Hendrickx
linux-3.5.x status
On Thu, Aug 23, 2012 at 16:10:26 +0200, Tobias Powalowski wrote:
> Hi guys,
>
> 3.5.x is not yet ready to move to [core],
> - ext4 regression is not fixed yet, will be fixed in 3.5.3
> - watchdogs are completely broken
> I'm not sure how much of a showstopper the watchdogs are, so please
> shout out if this is a real problem.
> If you have any other showstopper please let me know.
Since upgrading to 3.5.x, my system with mdraid mirror boots with either
a degraded RAID array, or not auto-discovering the RAID at all.
The disks are fine, confirmed by both SMART selftest and badblocks scan.
Downgraded back to 3.4.9 and the problem went away.
Anyone else experienced this? My setup should be common, with /boot on
/dev/md0 over sda1+sdb1, and the rest on LVM on /dev/md1 over sda2+sdb2.
Geert
--
geert.hendrickx.be :: geert@hendrickx.be :: PGP: 0xC4BB9E9F
This e-mail was composed using 100% recycled spam messages!
08-23-2012, 04:34 PM
Thomas Bächler
linux-3.5.x status
Am 23.08.2012 18:29, schrieb Geert Hendrickx:
> Since upgrading to 3.5.x, my system with mdraid mirror boots with either
> a degraded RAID array, or not auto-discovering the RAID at all.
>
> The disks are fine, confirmed by both SMART selftest and badblocks scan.
> Downgraded back to 3.4.9 and the problem went away.
>
> Anyone else experienced this? My setup should be common, with /boot on
> /dev/md0 over sda1+sdb1, and the rest on LVM on /dev/md1 over sda2+sdb2.
At home, I have sda1+sdb1 on md0 and sda4+sdb4 on md1, and I don't see
any problems.
08-23-2012, 04:52 PM
Bjoern Franke
linux-3.5.x status
>
> I don't think we will block the move to core on an isolated hardware
> crash that affects only a single user.
Sure.
> Still, can you give us the link to the kernel bugzilla report for this
> crash?
>
Am 23.08.2012 18:52, schrieb Bjoern Franke:
>
>>
>> I don't think we will block the move to core on an isolated hardware
>> crash that affects only a single user.
>
> Sure.
>
>> Still, can you give us the link to the kernel bugzilla report for this
>> crash?
>>
>
> https://bugzilla.kernel.org/show_bug.cgi?id=46381
That was quick.
We should probably add [1] to our 3.5.3 kernel as well, if it isn't int
he stable kernel already. According to the bug report, this will fix
your problem.
I have another problem - on my atom 570 kvm causes qemu to segfault.
08-26-2012, 01:04 PM
Bjoern Franke
linux-3.5.x status
Hi,
>
> We should probably add [1] to our 3.5.3 kernel as well, if it isn't int
> he stable kernel already. According to the bug report, this will fix
> your problem.
This would be nice. Yes, the issue seems to be fixed in 3.6rc3, it
doesn't appear on my laptop.
linux-3.5.x status
