(Auto)Switch-off monitor bug (ScreenBlanker)

A forum for general AmigaOS 4.x support questions that are not platform-specific

Re: (Auto)Switch-off monitor bug (ScreenBlanker)

Postby xenic » Wed Jan 29, 2014 10:41 pm

@all
I read this topic this morning but didn't test the problem. However, this afternoon I left my computer in the middlle of typing a message in an editor and returned about an hour later. My screen was dark but moving/clicking the mouse or typing on the keyboard or hitting the keyboard "Esc" key didn't bring my screen back. Finally, I noticed that the monitor light was off and switched the monitor back on. When the screen reappeared, Odyssey was frozen but that may have been a result of all the mouse & keyboard activity.

My monitor has never turned off by itself before. I do not have the Screenblanker Prefs/Timing/Power-off delay checkmarked. I would set a "Power-off delay" delay if it turned off the computer too; otherwise I see no point. After I finish this post, I'm going to leave my computer on while I go to the store to see if I can repeat the problem.
AmigaOne X1000 with 2GB memory - OS4.1 FE
xenic
 
Posts: 1112
Joined: Sun Jun 19, 2011 1:06 am

Re: (Auto)Switch-off monitor bug (ScreenBlanker)

Postby nbache » Thu Jan 30, 2014 1:07 am

samo79 wrote:@nbache
Have you maybe done something special about task priorities, e.g. set the video player up in priority or something?
No absolutely, i didn't change the task priorities ..

Eventually is there any other place we can check ?
Ranger would be a good way to check the priorities of running tasks. Maybe some of them set their own priority?

.. and just a curiosity, what OS4 machine are you using for this test ?
This was on my X1000.

Best regards,

Niels
User avatar
nbache
Beta Tester
Beta Tester
 
Posts: 1265
Joined: Mon Dec 20, 2010 8:25 pm
Location: Copenhagen, Denmark

Re: (Auto)Switch-off monitor bug (ScreenBlanker)

Postby samo79 » Sat Feb 01, 2014 5:40 pm

@nbache

Do i need to check the priority of the ScreenBlanker.library right ?
I now verified with SysMon and its priority is: 01

Is the same for you ?
Consider that it is the default one and i never touch it

As i said early in screen blanker prefs the "Ignore mouse when in DPMS mode" is unselected
User avatar
samo79
 
Posts: 519
Joined: Sat Jun 18, 2011 12:13 am
Location: Italy

Re: (Auto)Switch-off monitor bug (ScreenBlanker)

Postby xenic » Sat Feb 01, 2014 6:20 pm

@samo79
I tried to reproduce the "monitor shut off" problem I mentioned earlier and have not been able to reproduce it. I'm also using an X1000, so it could be possible that some hardware is less suceptible to the problem.
AmigaOne X1000 with 2GB memory - OS4.1 FE
xenic
 
Posts: 1112
Joined: Sun Jun 19, 2011 1:06 am

Re: (Auto)Switch-off monitor bug (ScreenBlanker)

Postby samo79 » Sun Feb 02, 2014 12:39 am

@xenic

Pretty possible, at this point would be interesting to verify under another Sam440 ..
Hey any OS4 betatester with Sam440 availible ? :D

P.S.
Xenic a question, what version of ScreenBlanker.library do you have installed ?
User avatar
samo79
 
Posts: 519
Joined: Sat Jun 18, 2011 12:13 am
Location: Italy

Re: (Auto)Switch-off monitor bug (ScreenBlanker)

Postby samo79 » Fri Oct 10, 2014 4:02 am

Aniway many time passed and so many test done, to conclude i can reproduce the issue in this method:

1) open a video with your preferred video player, no matter what player: DvPlayer and MPlayer is exactly the same
2) then put your video in pause
3) then just waiting for some time/minutes until your monitor will be switched off, aka when your screen will be "totally black"

Now try if moving your mouse or pressing any other key in order to reactivate the screen will work on you ..
(here neither ESC seems able to resume!) .. so in this situation the only method is an hard reboot ..
User avatar
samo79
 
Posts: 519
Joined: Sat Jun 18, 2011 12:13 am
Location: Italy

Re: (Auto)Switch-off monitor bug (ScreenBlanker)

Postby Raziel » Fri Oct 10, 2014 12:12 pm

samo79 wrote:Aniway many time passed and so many test done, to conclude i can reproduce the issue in this method:

1) open a video with your preferred video player, no matter what player: DvPlayer and MPlayer is exactly the same
2) then put your video in pause
3) then just waiting for some time/minutes until your monitor will be switched off, aka when your screen will be "totally black"

Now try if moving your mouse or pressing any other key in order to reactivate the screen will work on you ..
(here neither ESC seems able to resume!) .. so in this situation the only method is an hard reboot ..

I haven't read the whole thread, but did you try to let a radio stream or music loop run in the background when doing the tests?
If the stream still plays when everything else has stopped working it could be reduced to either being an input problem (input.device crashed) or a problem with your gfx card returning aka everything runs fine, but your gfx card output has stopped working?
Do you mabye have the possibilty to add a second card and check the output there?

Just some more ideas i would check...
If slaughterhouses had glass walls, everyone would be a vegetarian. ~ Sir Paul McCartney
-
Did everything just taste purple for a second? ~ Philip J. Fry
-
Ain't got no cash, ain't got no style, ladies vomit when I smile. ~ Dr. John Zoidberg
User avatar
Raziel
 
Posts: 795
Joined: Sat Jun 18, 2011 5:00 pm
Location: A haunted Castle somewhere in the Bavarian Mountains

Re: (Auto)Switch-off monitor bug (ScreenBlanker)

Postby samo79 » Tue Apr 17, 2018 12:12 am

Not directly related with the old report, however the argument is similar ..
Since latest OS 4.1 update i have some crashes with the blanker engine ... no action by me with the system, i just leave the computer alone and after a while a GR appear ...

Crash log for task "ScreenBlankerEngine"
Generated by GrimReaper 53.19
Crash occured in module graphics.library.kmod at address 0x01A368CC
Type of crash: DSI (Data Storage Interrupt) exception
Alert number: 0x80000003

Register dump:
GPR (General Purpose Registers):
0: 0198E0A4 55612280 00000000 5FFFA800 2083C000 00000000 006CB100 5FFA3420
8: 00036588 00000000 20916000 011E5680 46442882 558DCCBC 2083C000 22442224
16: 00000690 00000000 00000690 02270000 3A884908 00000000 5FFFA800 0000041A
24: 00000690 00000000 32A1B000 00000008 00000000 00000000 3A882478 00000006


FPR (Floating Point Registers, NaN = Not a Number):
0: nan 323 31 0
4: 11 1277.8 30.8 0
8: 11 4.5036e+15 1277.8 30.8
12: 1601 51 0 0
16: 0 0 0 0
20: 0 0 0 1.61895e-319
24: 0 0 2.65249e-315 0
28: 0 1.35808e-312 1.3581e-312 nan

FPSCR (Floating Point Status and Control Register): 0x82004000


SPRs (Special Purpose Registers):
Machine State (msr) : 0x0002F030
Condition (cr) : 0x22CAADA0
Instruction Pointer (ip) : 0x01A368CC
Xtended Exception (xer) : 0x018233AC
Count (ctr) : 0x00000000
Link (lr) : 0x00000000
DSI Status (dsisr) : 0x01842B34
Data Address (dar) : 0x00000000



680x0 emulated registers:
DATA: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
ADDR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
FPU0: 0 0 0 0
FPU4: 0 0 0 0



Symbol info:
Instruction pointer 0x01A368CC belongs to module "graphics.library.kmod" (HUNK/Kickstart)

Stack trace:
native kernel module graphics.library.kmod+0x000ab4ac
native kernel module graphics.library.kmod+0x00003048
native kernel module graphics.library.kmod+0x000035e8
native kernel module intuition.library.kmod+0x00061938
native kernel module intuition.library.kmod+0x00061bac
native kernel module intuition.library.kmod+0x0006cbb0
native kernel module intuition.library.kmod+0x00021448
native kernel module intuition.library.kmod+0x000215ec
native kernel module intuition.library.kmod+0x0006c944
module IPrefs at 0x6FF33FDC (section 5 @ 0xDFB8)
native kernel module intuition.library.kmod+0x0006cc04
module LIBS:screenblanker.library at 0x6FB32C00 (section 5 @ 0x3BDC)
module LIBS:screenblanker.library at 0x6FB30A98 (section 5 @ 0x1A74)
module ScreenBlankerEngine at 0x6FA7634C (section 5 @ 0x1328)
module ScreenBlankerEngine at 0x6FA76F08 (section 5 @ 0x1EE4)
native kernel module newlib.library.kmod+0x000020ac
native kernel module newlib.library.kmod+0x00002d5c
native kernel module newlib.library.kmod+0x00002ef0
ScreenBlankerEngine:_start()+0x170 (section 1 @ 0x16C)
native kernel module dos.library.kmod+0x000255c8
native kernel module kernel+0x0003e7b4
native kernel module kernel+0x0003e7fc

PPC disassembly:
01a368c4: 39080001 addi r8,r8,1
01a368c8: 7d0903a6 mtctr r8
*01a368cc: 912a0000 stw r9,0(r10)
01a368d0: 394a0020 addi r10,r10,32
01a368d4: 912affe4 stw r9,-28(r10)

System information:

CPU
Model: AMCC PPC440EP V1.3
CPU speed: 799 MHz
FSB speed: 133 MHz
Extensions:

Machine
Machine name: Sam440EP
Memory: 1048576 KB
Extensions: bus.pci
User avatar
samo79
 
Posts: 519
Joined: Sat Jun 18, 2011 12:13 am
Location: Italy

Re: (Auto)Switch-off monitor bug (ScreenBlanker)

Postby xenic » Tue Apr 17, 2018 4:02 pm

samo79 wrote:Not directly related with the old report, however the argument is similar ..
Since latest OS 4.1 update i have some crashes with the blanker engine ... no action by me with the system, i just leave the computer alone and after a while a GR appear ...

If you search for "boingball" in these forums, you will find at least several reports of the screenblanker "boingball" module causing freezes/crashes. You might try removing the "boingball" module from the "Active" module list and place it in the "Inactive" list in ScreenBlanker prefs.

Personally, I've been operating my system with the Screenblanker "boingball" module deactivated and the "Power-off" deactivated for years now.
AmigaOne X1000 with 2GB memory - OS4.1 FE
xenic
 
Posts: 1112
Joined: Sun Jun 19, 2011 1:06 am

Re: (Auto)Switch-off monitor bug (ScreenBlanker)

Postby samo79 » Wed Apr 18, 2018 12:40 am

I know, but i've disabled it long ago so it can be a problem related to this specific screensaver ...
User avatar
samo79
 
Posts: 519
Joined: Sat Jun 18, 2011 12:13 am
Location: Italy

Previous

Return to General AmigaOS

Who is online

Users browsing this forum: No registered users and 2 guests