Crash bug in console.device

[samo79]

When the shell is busy by compiling something, if i try to open another programs in background, sometimes i got this kind of DSI ... the issue seems harmless but a bit boring
_____________
Crash log for task "WinFrame 1 Process"
Generated by GrimReaper 53.19
Crash occured in module kernel at address 0x0182E210
Type of crash: DSI (Data Storage Interrupt) exception
Alert number: 0x80000003

Register dump:
GPR (General Purpose Registers):
0: 01910370 53286D40 00000000 67636320 54097E48 53043598 00000048 00000000
8: 00000048 0182E1FC 5FF9C648 01B3E270 00000794 00000000 000A0000 5FEAAC58
16: 02010E48 800003F2 00000000 5FEAAC58 5FEAA0C0 02010E74 00000057 00000000
24: 202D5765 5FF9C648 00000030 0000002F 5FEAADA0 00000000 54097E48 5FEAAC58


FPR (Floating Point Registers, NaN = Not a Number):
0: nan 8 305 22
4: 10 29.8 40.8 22
8: 10 2.14748e+09 29.8 40.8
12: 16 336 0 -5.05923e-321
16: 0 0 0 0
20: 0 0 0 1.61895e-319
24: 8.39912e-323 0 1.08779e-311 0
28: 0 1.35808e-312 1.3581e-312 -0.234375

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


SPRs (Special Purpose Registers):
Machine State (msr) : 0x0002F030
Condition (cr) : 0x51748DC0
Instruction Pointer (ip) : 0x0182E210
Xtended Exception (xer) : 0x0183B24C
Count (ctr) : 0x00000000
Link (lr) : 0x00000000
DSI Status (dsisr) : 0x0185BB0C
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 0x0182E210 belongs to module "kernel" (HUNK/Kickstart)

Stack trace:
native kernel module kernel+0x0002e210
native kernel module console.device.kmod+0x00017ed4
native kernel module console.device.kmod+0x0000af30
native kernel module console.device.kmod+0x00009ef8
native kernel module console.device.kmod+0x0000dcc4
native kernel module console.device.kmod+0x0000f824
native kernel module dos.library.kmod+0x0002a490
native kernel module kernel+0x00057104
native kernel module kernel+0x0005717c

PPC disassembly:
0182e208: 2f830000 cmpwi cr7,r3,0
0182e20c: 4d9e0020 beqlr- cr7
*0182e210: 81230000 lwz r9,0(r3)
0182e214: 21290000 subfic r9,r9,0
0182e218: 7d294910 subfe r9,r9,r9

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

[Raziel]

@samo79
@devs

I caught the exact (i think) same console crash today and i can reproduce it 100% (maybe it helps the cause?)

Attached is a file that causes the console to crash when used in that script.
I have no idea why, i doubt it's some buffer problem, because a simple text file (a guide from the manuals drawers), that was even bigger in size, went by fine.
I assume it could be because the printed characters somehow (wrongly) trigger a command to be executed in console and make it crash.

Be it as it may, it shouldn't crash and it would be great if this could be taken care of.

Below is the simple script that reads in the file (save it anywhere and execute it with "RX")
It will read in 32768 bytes in a loop and displays (SAY command) them to the console until EOF would be reached, alas it's not.

Code: Select all

/*
*/

OPTIONS FAILAT 21

y=1

IF ~OPEN(fileCrashConsole,'CrashConsole.file','R') THEN
	SAY 'File CrashConsole.file opening failed!'

DO WHILE ~EOF(fileCrashConsole)
	dataCrashConsole = READCH(fileCrashConsole,32768)
	SAY dataCrashConsole
	SAY y 'times 32768 bytes read!'
	y=y+1
END

CALL CLOSE(fileCrashConsole)
EXIT

[samo79]

@Raziel

Yeah seems i can reproduce it, same issue ...
Maybe any betatesters around could check this and eventually open a new ticket/report?

[javierdlr]

Done (BZ 10493)