Re: 2.6.15-1-sparc64 issues on blade 100
Dear Luis,
On Mon, Feb 13, 2006 at 07:18:02PM -0500, Luis F. Ortiz wrote:
> I'm running OBP 4.5.9 (2002/02/07), which I think is the latest that
> can run
> on a Sparc Blade 100.
I have just upgraded to OBP 4.17.1 2005/04/11 14:31. This solved the issue of
'flickering' and red dots in Xorg. However, Xorg is still running at 1400x1050 @
60Hz, while with kernel 2.6.9 Xorg used to do 1400x1050 @ 85Hz. It appears that
1152x864 can be done at 85Hz, but 1280x960 and above are just 60 Hz. Is there
anyone on this list who can confirm this? (Or anyone who has 1280x960 at a
higher refresh rate than 60 Hz?)
I also note some flickering when I move a window in Xorg; the corruption is
gone if I stop moving.
Finally, it appears that my current kernel (2.6.16-rc2-sparc64 from Jurij) is
not very stable. If I play some music with quod libet and try to play/pause/next
a few times, I see this in /var/log/kern.log:
Feb 15 12:35:50 zonne kernel: Bad page state in process 'python'
Feb 15 12:35:50 zonne kernel: page:fffff800006a2b78 flags:0x0000000000000414 mapping:0000000000000000 mapcount:0 count:0
Feb 15 12:35:50 zonne kernel: Trying to fix it up, but a reboot is needed
Feb 15 12:35:50 zonne kernel: Backtrace:
Feb 15 12:35:50 zonne kernel: Call Trace:
Feb 15 12:35:50 zonne kernel: [0000000000460e1c] unmap_vmas+0x338/0x5e8
Feb 15 12:35:50 zonne kernel: [00000000004641f4] unmap_region+0x84/0x11c
Feb 15 12:35:50 zonne kernel: [0000000000464884] do_munmap+0x194/0x228
Feb 15 12:35:50 zonne kernel: [0000000000464934] sys_munmap+0x1c/0x38
Feb 15 12:35:50 zonne kernel: [0000000000407214] linux_sparc_syscall32+0x34/0x40
Feb 15 12:35:50 zonne kernel: [00000000722ed1f4] 0x722ed1f4
Feb 15 12:35:51 zonne kernel: Bad page state in process 'python'
Feb 15 12:35:51 zonne kernel: page:fffff800006a2bb0 flags:0x0000000000000414 mapping:0000000000000000 mapcount:0 count:0
Feb 15 12:35:51 zonne kernel: Trying to fix it up, but a reboot is needed
I've noticed this also with 2.6.15. Can anyone confirm this, or is there perhaps
something wrong with my hardware?
Best regards,
Admar
Reply to: