2.6.39-rc3-git3 problem etc , reset-resistent problem
Pls see the enclosed screen foto.
After the crashs of 2.6.39-rcX , which I already reclaimed, and after -rc3-git4 and the patch suggested me to try out, the computer in vesa grafic mode crashs quickly, in fbdev only after longer time. After this crash, on re-booting, happens early during the boot process a next kind of crash. This don't go away on reset nor on power off, i.e. booting 2.6.39-rc3-git4-patchs again, it repeats. Only after rebooting with 2.6.38.2 or another working kernel, one can booting again with 2.6.39-rc3-git4-patchs -- until after its next crash, when the same happens again.
Some of these secondary crashs show a message: ata1: nv: stopping hardreset on occupied port, and after this the system attempts wrongly to understand the nv grafic card as a hard disc, and claims about read errors, until it crash.
Some of these secondary crashs, instead, look like the enclosed foto, also understanding something wrongly as an ata1 device.
I hope someone can find and correct that error.
W.Landgraf
---
Professional hosting for everyone - http://www.host.ru
Quoted 22 lines · werner
Pls see the enclosed screen foto.
After the crashs of 2.6.39-rcX , which I already reclaimed, and after -rc3-git4 and the patch suggested me to try out, the computer in vesa grafic mode crashs
quickly, in fbdev only after longer time. After this
crash, on re-booting, happens early during the boot
process a next kind of crash. This don't go away on
reset nor on power off, i.e. booting
2.6.39-rc3-git4-patchs again, it repeats. Only after
rebooting with 2.6.38.2 or another working kernel, one can booting again with 2.6.39-rc3-git4-patchs -- until after its next crash, when the same happens again.Some of these secondary crashs show a message: ata1:
nv: stopping hardreset on occupied port, and after
this the system attempts wrongly to understand the nv grafic card as a hard disc, and claims about read errors, until it crash.
Quoted 3 lines
Some of these secondary crashs, instead, look like the enclosed foto, also understanding something wrongly as an ata1 device.
Any chance you can setup a network console or serial console and capture all of those messages?
Signature · 1 line
Jens Axboe