Reproduced this bug on 2.6.35-17 i386 (linux-image-2.6.35-17-generic 2.6.35-17.23). The humour of the "fix" is the following: -17 kernel doesn't catch any stack trace so I can't collect any debug info - there're no information in logs after reboot.
Reproduced this bug on 2.6.35-17 i386 (linux- image-2. 6.35-17- generic 2.6.35-17.23).
The humour of the "fix" is the following: -17 kernel doesn't catch any stack trace so I can't collect any debug info - there're no information in logs after reboot.