Click Here
home features news forums classifieds faqs links search
6128 members 
Amiga Q&A /  Free for All /  Emulation /  Gaming / (Latest Posts)
Login

Nickname

Password

Lost Password?

Don't have an account yet?
Register now!

Support Amigaworld.net
Your support is needed and is appreciated as Amigaworld.net is primarily dependent upon the support of its users.
Donate

Menu
Main sections
» Home
» Features
» News
» Forums
» Classifieds
» Links
» Downloads
Extras
» OS4 Zone
» IRC Network
» AmigaWorld Radio
» Newsfeed
» Top Members
» Amiga Dealers
Information
» About Us
» FAQs
» Advertise
» Polls
» Terms of Service
» Search

IRC Channel
Server: irc.amigaworld.net
Ports: 1024,5555, 6665-6669
SSL port: 6697
Channel: #Amigaworld
Channel Policy and Guidelines

Who's Online
22 crawler(s) on-line.
 95 guest(s) on-line.
 0 member(s) on-line.



You are an anonymous user.
Register Now!
 kolla:  12 mins ago
 monstercoder:  15 mins ago
 matthey:  40 mins ago
 Turk:  40 mins ago
 clint:  54 mins ago
 kamelito:  1 hr 38 mins ago
 choochy:  1 hr 39 mins ago
 F0L:  1 hr 46 mins ago
 OneTimer1:  2 hrs 5 mins ago
 zipper:  2 hrs 32 mins ago

/  Forum Index
   /  Amiga OS4.x \ Workbench 4.x
      /  Final OS4 update stability survey
Register To Post

Goto page ( Previous Page 1 | 2 | 3 | 4 )
PosterThread
STRICQ 
Re: Final OS4 update stability survey
Posted on 3-Jan-2007 2:33:54
#61 ]
Regular Member
Joined: 23-Mar-2003
Posts: 221
From: Colorado Springs, CO

@painter

Sounds like your RAM is incompatible. Get better RAM.

_________________
AmigaOne XE 800Mhz/1024MB
Radeon 9200 128MB
160GB HD/2x 4GB HD
SII0680 PATA133
Audigy 2
3Com 100Mb PCI Card

 Status: Offline
Profile     Report this post  
Kicko 
Re: Final OS4 update stability survey
Posted on 3-Jan-2007 3:24:59
#62 ]
Elite Member
Joined: 19-Jun-2004
Posts: 5009
From: Sweden

OS4Final seems stable here to. The program that crashes are often 3rd party. Some are updated to work good like dopus, tunenet etc. Snoopdos crashes when changing settings. I hope there will be updates. SashimiPPC is update on os4depot so that works fine.

Ibrowse worked nice but crashed everytime when i wanted to access the webinterface for my netgear RP614v3. The crash i got was when my internet provider "comhem" had a wrong configuration so that the modem didnt get any IP. So the netgear router wanted to start the "setup wizard" and thats when the crashes appeared. Now when my internet provider fixed my config and my modem and router gets the IP i dont get any crashes with IBrowse. Its only when i had problems the modem and router didnt get any IP.

I tried Aweb and it didnt crash. When i had the problem with getting no ip the setup wizard (on netgear webconfig) thought the modem was using static so it asked for manual setting. So i tested also when my internet worked and then the setup wizard saw it was dhcp and not static.

I hope you understand my english ;)

Oh not to forget, Epistula does freeze my system when using msn after a short time. Anyone else ?

 Status: Offline
Profile     Report this post  
Sandpiper 
Re: Final OS4 update stability survey
Posted on 3-Jan-2007 4:17:12
#63 ]
Regular Member
Joined: 11-Dec-2004
Posts: 206
From: Mississauga, Canada

@All,

I did an update install of OS4Final. Initially I experienced some instability with programs such as IBrowse 2.4 as reported elsewhere but as time goes on my µA1 is becoming more and more stable as I tweak (remove older update4 progs, libs, etc). I am very happy with it now. I am using Yam 2.5dev, IB2.4, GoldEd6, DOpus4.18, Samba 2.2.5, smbfs, PageStream (68k & OS4 version) + numerous utilities frequently and everything is running quite smoothly (and very snappy).

I am much impressed by the speed improvements. Very noticeable with apps like APDF. I have a WinXP box (Athlon 2600+) with Firefox 2 sitting right next to my µA1 running IB2.4. I am amazed by how fast IB is in comparison with Firefox on the WinXP box when loading the same website. Great job IB Team and the OS4 Team.

Brian

 Status: Offline
Profile     Report this post  
TetiSoft 
Re: Final OS4 update stability survey
Posted on 3-Jan-2007 13:48:47
#64 ]
Cult Member
Joined: 3-Mar-2005
Posts: 585
From: Germany

@painter

This crashlog snippet is missing nearly every important information.
It tells that the crash happened inside the kernel, but this probably
doesnt mean that there exists a bug in the kernel, only that a function
of the kernel was called with bad parameters, but we dont see from where,
and that makes it impossible to guess what went wrong.

> But unfortunately I can't remember what pgm I was running to get it

This proves that its even more impossible to reproduce the problem,
and fixing unreproduble problems is a difficult task.

When no user remembers which program caused the problem its probably
not an important program so its not urgent to fix something...

 Status: Offline
Profile     Report this post  
painter 
Re: Final OS4 update stability survey
Posted on 3-Jan-2007 15:46:52
#65 ]
Cult Member
Joined: 5-Oct-2003
Posts: 681
From: Manitoba, Canada

@TetiSoft

you're right one should pay attention to what you're running when crashes happen not assume that crashlog will have name of program in it's title. Which is what I did.
here's the whole audio.device crashlog/ As was evident from my other post I am not exactly sure how to read a crash log.

@Stircq
the ram was compatible with updates 1, 2, 3 and 4 doesn't make much sense to me that it is suddenly incompatible.

Crash log for task "audio.device"
Generated by GrimReaper 52.1
Crash occured in module kernel at address 0x0141541C
Type of crash: DSI (Data Storage Interrupt) exception

Register dump:
GPR (General Purpose Registers):
0: FEC00658 6D2371E0 FEFEFEFE FEC00654 6D3FFEC0 6D3FFEC0 00000007 01D93370
8: 00000002 00010180 0000016F 00000001 59F53E33 FEFEFEFE 6D6D3D94 80003000
16: 00000000 6D6D3A28 00000001 00000001 6D3FF560 00000001 00000000 1B52E260
24: 6D3FA910 00000001 00000000 6D6D39C4 FEC00640 00000007 6D3FFEC0 01C927D0


FPR (Floating Point Registers, NaN = Not a Number):
0: NaN 2.2 0.45455 0
4: 0 0 0 0
8: 0 0 0 0
12: NaN 1e-05 0 0
16: 0 0 0 0
20: 0 0 0 0
24: 0 0 0 0
28: 0 0 0 0

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


SPRs (Special Purpose Registers):
Machine State (msr) : 0x00005030
Condition (cr) : 0x99F53E39
Instruction Pointer (ip) : 0x0141541C
Xtended Exception (xer) : 0xE000FE7E
Count (ctr) : 0x0141542C
Link (lr) : 0x0141A288
DSI Status (dsisr) : 0x42000000
Data Address (dar) : 0x00010180



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 0x0141541C belongs to module "kernel" (HUNK/Kickstart)

Stack trace:
native kernel module kernel+0x0001541c
native kernel module kernel+0x0001a464
module DEVS:audio.device at 0x7FA59580 (section 4 @ 0x560)
module DEVS:audio.device at 0x7FA5A2F4 (section 4 @ 0x12D4)
native kernel module dos.library.kmod+0x0001dfdc


PPC disassembly:
01415414: 90040000 stw r0,0(r4)
01415418: 81230008 lwz r9,8(r3)
*0141541c: 90890000 stw r4,0(r9)
01415420: 91240004 stw r9,4(r4)
01415424: 90830008 stw r4,8(r3)

System information:

CPU
Model: Motorola MPC 7445/7455 Apollo V2.1
CPU speed: 933 MHz
FSB speed: 133 MHz
Extensions: performancemonitor altivec

Machine
Machine name: AmigaOne
Memory: 524288 KB
Extensions: bus.pci bus.agp

Expansion buses
PCI/AGP
00:00.0 Vendor 0x10CC Device 0x0660
Range 0: 00000000 - 00400000 (PREF.MEM)
00:01.0 Vendor 0x10CC Device 0x0661
00:06.0 Vendor 0x10B7 Device 0x9200
Range 0: 00802000 - 00802080 (IO)
Range 1: 98100000 - 98100080 (MEM)
00:07.0 Vendor 0x1106 Device 0x0686
00:07.1 Vendor 0x1106 Device 0x0571
Range 4: 0000CC00 - 0000CC10 (IO)
00:07.2 Vendor 0x1106 Device 0x3038
Range 4: 00802080 - 008020A0 (IO)
00:07.3 Vendor 0x1106 Device 0x3038
Range 4: 008020A0 - 008020C0 (IO)
00:07.4 Vendor 0x1106 Device 0x3057
00:07.5 Vendor 0x1106 Device 0x3058
Range 0: 00802100 - 00802200 (IO)
Range 1: 00802200 - 00802208 (IO)
Range 2: 00802200 - 00802208 (IO)
00:07.6 Vendor 0x1106 Device 0x3068
Range 0: 00802300 - 00802400 (IO)
00:08.0 Vendor 0x1000 Device 0x000C
Range 0: 00802400 - 00802500 (IO)
Range 1: 98100100 - 98100200 (MEM)
Range 2: 98101000 - 98102000 (MEM)
00:0A.0 Vendor 0x1102 Device 0x0002
Range 0: 00802500 - 00802520 (IO)
00:0A.1 Vendor 0x1102 Device 0x7002
Range 0: 00802520 - 00802528 (IO)
01:00.0 Vendor 0x1002 Device 0x5960
Range 0: 80000000 - 88000000 (PREF.MEM)
Range 1: 00002000 - 00002100 (IO)
Range 2: 88000000 - 88010000 (MEM)
01:00.1 Vendor 0x1002 Device 0x5940
Range 0: 90000000 - 98000000 (PREF.MEM)
Range 1: 98000000 - 98010000 (MEM)

Libraries
0x6e1a66d8: ISO-8859-15.charset V52.1
0x6e1a65d8: english_ISO-8859-15.language V52.1
0x01da3b4a: exec.library V52.2
0x6ff64174: vilintuisup.library V0.9
0x6ff64048: cgxvideo.library V42.1
0x6ff320e0: cybergraphics.library V43.0
0x6c81ad68: emu10kx.audio V6.7
0x6c8f0570: getscreenmode.gadget V52.1
0x6df08d80: slider.gadget V52.1
0x6df08e70: getfont.gadget V52.1
0x6d400900: getfile.gadget V52.1
0x6d119408: popupmenu.class V52.1
0x6d400698: clicktab.gadget V52.1
0x6d13d098: popupmenu.library V52.1
0x6d049d28: screenblanker.library V52.1
0x6cb083f0: checkbox.gadget V52.1
0x6d57a640: bitmap.image V52.1
0x6d1179e8: listbrowser.gadget V52.3
0x6d1177f4: asl.library V52.1
0x6cb060e0: mathieeedoubtrans.library V52.1
0x6d160d90: space.gadget V52.1
0x6deeeba0: mathieeesingbas.library V52.1
0x6d119888: chooser.gadget V52.1
0x6d57a440: penmap.image V52.1
0x6d1609d0: integer.gadget V52.1
0x6e15abe0: string.gadget V52.1
0x6e012c00: requester.class V51.18
0x6df08600: jpeg.datatype V52.1
0x6e016104: usergroup.library V4.29
0x6e178eb0: mathieeedoubbas.library V52.1
0x6e0101ac: massstorage.usbfd V52.2
0x6e00a490: bsdsocket.library V4.286
0x6dfb1bf0: label.image V52.1
0x6ff87d20: glyph.image V52.1
0x6dfb15b0: button.gadget V52.1
0x6ff87c20: scroller.gadget V52.1
0x6e156d20: bevel.image V52.1
0x6e1550fc: textclip.library V52.1
0x6dfaf0d8: layout.gadget V52.1
0x6ff87b20: drawlist.image V52.1
0x6e157b70: window.class V52.1
0x6e226e50: ilbm.datatype V52.1
0x6e156538: emulation.library V41.438
0x6e1d8c34: picture.datatype V52.1
0x6e226a90: png.datatype V52.1
0x6e2268d4: mpega.library V2.4
0x6e2279d8: timezone.library V52.1
0x6e1a6a58: application.library V52.1
0x6ff8793c: ft2.library V8.1
0x6ff537ac: workbench.library V52.1
0x6e22ad90: Picasso96API.library V2.343
0x6e18dcf0: gadtools.library V52.1
0x6e1a40ec: commodities.library V52.1
0x6e15b0cc: icon.library V52.2
0x6e1f4540: datatypes.library V52.1
0x6e825e48: version.library V52.1
0x6e24d2c0: iffparse.library V51.1
0x6ffb55cc: locale.library V52.1
0x6ff667ac: diskfont.library V52.1
0x6ff05868: petunia.library V52.1
0x6fdcc5e8: dos.library V52.2
0x6ff64354: usbprivate.library V52.2
0x6fe79128: bootkeyboard.usbfd V52.2
0x6fe790a8: bootmouse.usbfd V52.2
0x6ff053fc: hub.usbfd V52.1
0x6ff6325c: usbresource.library V52.2
0x6ff95c18: hunk.library V52.2
0x6ff93354: elf.library V52.1
0x6ff0a4d0: intuition.library V52.2
0x6ff52150: rtg.library V41.4288
0x6ff958a0: ATIRadeon.chip V52.5
0x6ff95824: PCIGraphics.card V52.2
0x6ffa9a10: keymap.library V52.1
0x6ff63140: layers.library V52.1
0x6ffb4420: graphics.library V52.1
0x6ff8a224: nonvolatile.library V52.1
0x6ffaa2b8: newlib.library V52.3
0x6ff941ac: utility.library V52.1
0x6ffa90a8: expansion.library V52.1
0x6e037cae: rexxsyslib.library V45.3 (Legacy)

Devices
0x6d43bb64: ahi.device V6.6
0x6d6d39c4: audio.device V52.1
0x6ff80364: printer.device V39.7 (Legacy)
0x6de5cbc4: eth3com.device V52.1
0x6e010298: usbmassstorage.device V52.2
0x6ff634d0: usbsys.device V52.2
0x6ff8acd0: uhci.usbhcd V52.2
0x6ff8a8e4: a1ide.device V52.1
0x6ff87218: a1floppy.device V52.2
0x6ffa8628: console.device V52.2
0x6fffe530: ramdrive.device V52.2
0x6ff663bc: input.device V52.1
0x6ffa8314: keyboard.device V52.1
0x6ffa9774: gameport.device V52.1
0x6fffe410: timer.device V52.1

Tasks
ahi.device Unit Process (Waiting)
Stack: 0x6d1fd000 - 0x6d209340, pointer @ 0x6d2092b0 (Cookie OK)
Signals: SigRec 0xf000c000, SigWait 0x00000000
State: Process (Waiting)
audio.device (Crashed)
Stack: 0x6d22b000 - 0x6d237344, pointer @ 0x6d2371e0 (Cookie OK)
Signals: SigRec 0x80003000, SigWait 0x80000100
State: Process (Crashed)
ClickToFront (Waiting)
Stack: 0x6d0c6000 - 0x6d0cdffc, pointer @ 0x6d0cdac0 (Cookie OK)
Signals: SigRec 0xc000d000, SigWait 0x00000000
State: Process (Waiting)
input.device (Waiting)
Stack: 0x6ff5a000 - 0x6ff62000, pointer @ 0x6ff61f70 (Cookie OK)
Signals: SigRec 0x80000000, SigWait 0x00000000
State: Task (Waiting)
USB stack (Waiting)
Stack: 0x6ffb8000 - 0x6ffbc000, pointer @ 0x6ffbbf50 (Cookie OK)
Signals: SigRec 0xf8007000, SigWait 0x00000000
State: Task (Waiting)
UHCI Controller Task Unit 1 (Waiting)
Stack: 0x6fe20000 - 0x6fe28000, pointer @ 0x6fe27f30 (Cookie OK)
Signals: SigRec 0xbc001000, SigWait 0x00000000
State: Task (Waiting)
UHCI Controller Task Unit 0 (Waiting)
Stack: 0x6fe70000 - 0x6fe78000, pointer @ 0x6fe77f30 (Cookie OK)
Signals: SigRec 0xbc001000, SigWait 0x00000000
State: Task (Waiting)
a1ide.device - chip 0 port 0 (Waiting)
Stack: 0x6fea4000 - 0x6feac000, pointer @ 0x6feabf50 (Cookie OK)
Signals: SigRec 0xc0000000, SigWait 0x20000000
State: Task (Waiting)
eth3com.device (Waiting)
Stack: 0x6d592000 - 0x6d599ffc, pointer @ 0x6d599f50 (Cookie OK)
Signals: SigRec 0xe0001000, SigWait 0x10000010
State: Process (Waiting)
a1ide.device - chip 0 port 1 (Waiting)
Stack: 0x6fe8c000 - 0x6fe94000, pointer @ 0x6fe93f50 (Cookie OK)
Signals: SigRec 0xc0000000, SigWait 0x00000000
State: Task (Waiting)
MainPC0 (Waiting)
Stack: 0x6dfc4000 - 0x6dfcbffc, pointer @ 0x6dfcbf40 (Cookie OK)
Signals: SigRec 0x40000100, SigWait 0x20000000
State: Process (Waiting)
CD0 (Waiting)
Stack: 0x6fb80000 - 0x6fb81ffc, pointer @ 0x6fb81f50 (Cookie OK)
Signals: SigRec 0x00000100, SigWait 0x00000000
State: Process (Waiting)
RAM (Waiting)
Stack: 0x6e2eb000 - 0x6e2ecffc, pointer @ 0x6e2eccf0 (Cookie OK)
Signals: SigRec 0xc0000100, SigWait 0x00000000
State: Process (Waiting)
DH3 (Waiting)
Stack: 0x6f601000 - 0x6f602ffc, pointer @ 0x6f602f30 (Cookie OK)
Signals: SigRec 0xa8000100, SigWait 0x00000000
State: Process (Waiting)
DH9 (Waiting)
Stack: 0x6e812000 - 0x6e813ffc, pointer @ 0x6e813f30 (Cookie OK)
Signals: SigRec 0xa8000100, SigWait 0x00000000
State: Process (Waiting)
DH1 (Waiting)
Stack: 0x6fa4e000 - 0x6fa4fffc, pointer @ 0x6fa4ff30 (Cookie OK)
Signals: SigRec 0xa8000100, SigWait 0x00000000
State: Process (Waiting)
DH4 (Waiting)
Stack: 0x6f3e2000 - 0x6f3e3ffc, pointer @ 0x6f3e3f30 (Cookie OK)
Signals: SigRec 0xa8000100, SigWait 0x00000000
State: Process (Waiting)
DH10 (Waiting)
Stack: 0x6e585000 - 0x6e586ffc, pointer @ 0x6e586f30 (Cookie OK)
Signals: SigRec 0xa8000100, SigWait 0x00000000
State: Process (Waiting)
DH5 (Waiting)
Stack: 0x6f1a8000 - 0x6f1a9ffc, pointer @ 0x6f1a9f30 (Cookie OK)
Signals: SigRec 0xa8000100, SigWait 0x00000000
State: Process (Waiting)
DH6 (Waiting)
Stack: 0x6ef72000 - 0x6ef73ffc, pointer @ 0x6ef73f30 (Cookie OK)
Signals: SigRec 0xa8000100, SigWait 0x00000000
State: Process (Waiting)
DH0 (Waiting)
Stack: 0x6fd97000 - 0x6fd98ffc, pointer @ 0x6fd98f30 (Cookie OK)
Signals: SigRec 0xa8000100, SigWait 0x00000000
State: Process (Waiting)
FD0 (Waiting)
Stack: 0x6fa61000 - 0x6fa62ffc, pointer @ 0x6fa62f30 (Cookie OK)
Signals: SigRec 0xa8000100, SigWait 0x00000000
State: Process (Waiting)
DH7 (Waiting)
Stack: 0x6ed5b000 - 0x6ed5cffc, pointer @ 0x6ed5cf30 (Cookie OK)
Signals: SigRec 0xa8000100, SigWait 0x00000000
State: Process (Waiting)
DH2 (Waiting)
Stack: 0x6f837000 - 0x6f838ffc, pointer @ 0x6f838f30 (Cookie OK)
Signals: SigRec 0xa8000100, SigWait 0x00000000
State: Process (Waiting)
DH8 (Waiting)
Stack: 0x6eaca000 - 0x6eacbffc, pointer @ 0x6eacbf30 (Cookie OK)
Signals: SigRec 0xa8000100, SigWait 0x00000000
State: Process (Waiting)
console.device (Waiting)
Stack: 0x6feb4000 - 0x6febc000, pointer @ 0x6febbf70 (Cookie OK)
Signals: SigRec 0xf0000000, SigWait 0x00000000
State: Task (Waiting)
dos_flc_handler (Waiting)
Stack: 0x6ff3e000 - 0x6ff3fffc, pointer @ 0x6ff3ff40 (Cookie OK)
Signals: SigRec 0x00000100, SigWait 0x00000000
State: Process (Waiting)
dos_nbmd_process (Waiting)
Stack: 0x6fdb8000 - 0x6fdb9ffc, pointer @ 0x6fdb9f60 (Cookie OK)
Signals: SigRec 0x00000100, SigWait 0x00000000
State: Process (Waiting)
RAW (Waiting)
Stack: 0x6e2f8000 - 0x6e2f9ffc, pointer @ 0x6e2f9e40 (Cookie OK)
Signals: SigRec 0x80000100, SigWait 0x00000000
State: Process (Waiting)
CON (Waiting)
Stack: 0x6e2e2000 - 0x6e2e3ffc, pointer @ 0x6e2e3e40 (Cookie OK)
Signals: SigRec 0x80000100, SigWait 0x00000000
State: Process (Waiting)
CON (Waiting)
Stack: 0x6e2b2000 - 0x6e2b3ffc, pointer @ 0x6e2b3e40 (Cookie OK)
Signals: SigRec 0x80000100, SigWait 0x00000000
State: Process (Waiting)
AUDIO (Waiting)
Stack: 0x6dfa2004 - 0x6dfa9ffc, pointer @ 0x6dfa9ec0 (Cookie OK)
Signals: SigRec 0x00000100, SigWait 0x00000000
State: Process (Waiting)
FD0 (Waiting)
Stack: 0x6ffa6000 - 0x6ffa7f40, pointer @ 0x6ffa7e90 (Cookie OK)
Signals: SigRec 0x10000000, SigWait 0x00000000
State: Task (Waiting)
CON (Waiting)
Stack: 0x6d0cf000 - 0x6d0d6ffc, pointer @ 0x6d0d6e40 (Cookie OK)
Signals: SigRec 0x80000100, SigWait 0x00000000
State: Process (Waiting)
CON (Waiting)
Stack: 0x6d0a4000 - 0x6d0abffc, pointer @ 0x6d0abe40 (Cookie OK)
Signals: SigRec 0x80000100, SigWait 0x00000000
State: Process (Waiting)
CON (Waiting)
Stack: 0x6d4db000 - 0x6d4e2ffc, pointer @ 0x6d4e2e40 (Cookie OK)
Signals: SigRec 0x80000100, SigWait 0x00000000
State: Process (Waiting)
CON (Waiting)
Stack: 0x6d468000 - 0x6d46fffc, pointer @ 0x6d46fe40 (Cookie OK)
Signals: SigRec 0x80000100, SigWait 0x00000000
State: Process (Waiting)
PC0 (Waiting)
Stack: 0x6dfd5000 - 0x6dfdcffc, pointer @ 0x6dfdcee0 (Cookie OK)
Signals: SigRec 0x00010100, SigWait 0x00000000
State: Process (Waiting)
ENV (Waiting)
Stack: 0x6e200000 - 0x6e207ffc, pointer @ 0x6e207e40 (Cookie OK)
Signals: SigRec 0x80000000, SigWait 0x00000100
State: Process (Waiting)
MassStorage Device Task (Waiting)
Stack: 0x6deaf000 - 0x6deb7000, pointer @ 0x6deb6c90 (Cookie OK)
Signals: SigRec 0x04000000, SigWait 0x00000010
State: Task (Waiting)
RexxMaster [] (Waiting)
Stack: 0x6dee2004 - 0x6dee9ffc, pointer @ 0x6dee9f50 (Cookie OK)
Signals: SigRec 0xc0000000, SigWait 0x00000000
State: Process (Waiting)
TEXTCLIP (Waiting)
Stack: 0x6dfb3000 - 0x6dfbaffc, pointer @ 0x6dfbaef0 (Cookie OK)
Signals: SigRec 0x80000000, SigWait 0x00000100
State: Process (Waiting)
Workbench Clipboard Server (Waiting)
Stack: 0x6d59b000 - 0x6d5a2ffc, pointer @ 0x6d5a2f40 (Cookie OK)
Signals: SigRec 0x80000000, SigWait 0x00000100
State: Process (Waiting)
Workbench DosList Notify (Waiting)
Stack: 0x6d16a000 - 0x6d171ffc, pointer @ 0x6d171f80 (Cookie OK)
Signals: SigRec 0x00003000, SigWait 0x00000100
State: Process (Waiting)
string.gadget server (Waiting)
Stack: 0x6d02c000 - 0x6d033ffc, pointer @ 0x6d033e30 (Cookie OK)
Signals: SigRec 0x40000000, SigWait 0x00000100
State: Process (Waiting)
ContextMenus Command Dispatcher [ContextMenus Command Dispatcher] (Waiting)
Stack: 0x6d3d4000 - 0x6d3ddc3c, pointer @ 0x6d3ddbc0 (Cookie OK)
Signals: SigRec 0x80001000, SigWait 0x00000000
State: Process (Waiting)
Workbench [Workbench] (Waiting)
Stack: 0x6ddf2000 - 0x6ddf9ffc, pointer @ 0x6ddf9e70 (Cookie OK)
Signals: SigRec 0x80000000, SigWait 0x00008100
State: Process (Waiting)
hub.usbfd (Waiting)
Stack: 0x6fddc000 - 0x6fde4000, pointer @ 0x6fde3f50 (Cookie OK)
Signals: SigRec 0xa0000000, SigWait 0x00000000
State: Task (Waiting)
hub.usbfd (Waiting)
Stack: 0x6fde4000 - 0x6fdec000, pointer @ 0x6fdebf50 (Cookie OK)
Signals: SigRec 0xa0000000, SigWait 0x00000000
State: Task (Waiting)
application.library messageserver (Waiting)
Stack: 0x6e153000 - 0x6e153fa0, pointer @ 0x6e153f10 (Cookie OK)
Signals: SigRec 0xc0000000, SigWait 0x00000000
State: Task (Waiting)
datatypes.library (Waiting)
Stack: 0x6e199000 - 0x6e1a0ffc, pointer @ 0x6e1a0f50 (Cookie OK)
Signals: SigRec 0x00001100, SigWait 0x00000000
State: Process (Waiting)
USB stack Process (Waiting)
Stack: 0x6dff6000 - 0x6dffdffc, pointer @ 0x6dffdf50 (Cookie OK)
Signals: SigRec 0x80001000, SigWait 0x00000100
State: Process (Waiting)
ConClip (Waiting)
Stack: 0x6ded1000 - 0x6ded8ffc, pointer @ 0x6ded8ef0 (Cookie OK)
Signals: SigRec 0x80000000, SigWait 0x00000000
State: Process (Waiting)
TCP/IP Log (Waiting)
Stack: 0x6dec8000 - 0x6decfffc, pointer @ 0x6decff50 (Cookie OK)
Signals: SigRec 0x80003000, SigWait 0x00000000
State: Process (Waiting)
Background CLI [Turboprint:turbo/tp8] (Waiting)
Stack: 0x6cb5f004 - 0x6cb66ffc, pointer @ 0x6cb66f60 (Cookie OK)
Signals: SigRec 0x80001000, SigWait 0x00000100
State: Process (Waiting)
FKey [] (Waiting)
Stack: 0x6d0f5000 - 0x6d0fcffc, pointer @ 0x6d0fcbe0 (Cookie OK)
Signals: SigRec 0xc000d000, SigWait 0x00000100
State: Process (Waiting)
RAWBInfo (Waiting)
Stack: 0x6d4f5000 - 0x6d4fcffc, pointer @ 0x6d4fcf00 (Cookie OK)
Signals: SigRec 0x80001000, SigWait 0x00000100
State: Process (Waiting)
ASYNCWB (Waiting)
Stack: 0x6d4c2000 - 0x6d4c9ffc, pointer @ 0x6d4c9ed0 (Cookie OK)
Signals: SigRec 0x80001000, SigWait 0x00000100
State: Process (Waiting)
DefIcons (Waiting)
Stack: 0x6d4ec000 - 0x6d4f3ffc, pointer @ 0x6d4f3e00 (Cookie OK)
Signals: SigRec 0x80009000, SigWait 0x00000100
State: Process (Waiting)
ContextMenus [] (Waiting)
Stack: 0x6d0e8000 - 0x6d0efffc, pointer @ 0x6d0efd50 (Cookie OK)
Signals: SigRec 0xe0001000, SigWait 0x00000000
State: Process (Waiting)
ScreenBlankerEngine (Waiting)
Stack: 0x6d0b5000 - 0x6d0bcffc, pointer @ 0x6d0bcd10 (Cookie OK)
Signals: SigRec 0xe0001000, SigWait 0x00000100
State: Process (Waiting)
TCP/IP Configuration (Waiting)
Stack: 0x6deb7000 - 0x6debeffc, pointer @ 0x6debee50 (Cookie OK)
Signals: SigRec 0xf8003000, SigWait 0x00000110
State: Process (Waiting)
« IPrefs » (Waiting)
Stack: 0x6e1d9000 - 0x6e1e0ffc, pointer @ 0x6e1e0590 (Cookie OK)
Signals: SigRec 0x0000f000, SigWait 0xc0000100
State: Process (Waiting)
ramlib (Waiting)
Stack: 0x6e259000 - 0x6e260ffc, pointer @ 0x6e260f60 (Cookie OK)
Signals: SigRec 0x80000000, SigWait 0x00000100
State: Process (Waiting)
VistaPro3.0 (Waiting)
Stack: 0x6c857004 - 0x6c86334c, pointer @ 0x6c863170 (Cookie OK)
Signals: SigRec 0x00000010, SigWait 0xc0000000
State: Process (Waiting)
reaper.task (Waiting)
Stack: 0x6e250000 - 0x6e257ffc, pointer @ 0x6e257ef0 (Cookie OK)
Signals: SigRec 0x00007000, SigWait 0x00000000
State: Process (Waiting)
AmiDock (Waiting)
Stack: 0x6d489000 - 0x6d490ffc, pointer @ 0x6d490b20 (Cookie OK)
Signals: SigRec 0x7e00d000, SigWait 0x00000000
State: Process (Waiting)
TCP/IP Superserver [TCP/IP Superserver] (Waiting)
Stack: 0x6de96000 - 0x6de9dffc, pointer @ 0x6de9da40 (Cookie OK)
Signals: SigRec 0xd0000080, SigWait 0x00000100
State: Process (Waiting)
TCP/IP Control (Waiting)
Stack: 0x6de85000 - 0x6de8cffc, pointer @ 0x6de8ce20 (Cookie OK)
Signals: SigRec 0xf8009080, SigWait 0x00000000
State: Process (Waiting)
screenblanker.library timing dispatcher (Waiting)
Stack: 0x6d481000 - 0x6d483000, pointer @ 0x6d482ec0 (Cookie OK)
Signals: SigRec 0x40000000, SigWait 0x80000000
State: Task (Waiting)
Picasso96 (Waiting)
Stack: 0x6e14a000 - 0x6e151ffc, pointer @ 0x6e151e00 (Cookie OK)
Signals: SigRec 0x80000000, SigWait 0x00000100
State: Process (Waiting)
dos_signal_server (Waiting)
Stack: 0x6fdc1000 - 0x6fdc2ffc, pointer @ 0x6fdc2f60 (Cookie OK)
Signals: SigRec 0x0000e000, SigWait 0x00000000
State: Process (Waiting)
idle.task (Ready)
Stack: 0x6ff86000 - 0x6ff87000, pointer @ 0x6ff86fd0 (Cookie OK)
Signals: SigRec 0x00000000, SigWait 0x00000000
State: Task (Ready)

painter

 Status: Offline
Profile     Report this post  
Metalheart 
Re: Final OS4 update stability survey
Posted on 3-Jan-2007 15:55:48
#66 ]
Elite Member
Joined: 21-Aug-2003
Posts: 2969
From: Somewhere in the Dutch mountains....

@Sandpiper

Quote:
I am using Yam 2.5dev, IB2.4, GoldEd6, DOpus4.18, Samba 2.2.5, smbfs, PageStream (68k & OS4 version) + numerous utilities frequently and everything is running quite smoothly (and very snappy).


Wich OS4 version of Pagestream are you using ? I've only got the 68k version working....

Cheers,

Martin

_________________
Theres a time to live and a time to die
When its time to meet the maker
Theres a time to live but isnt it strange
That as soon as you're born you're dying

 Status: Offline
Profile     Report this post  
TetiSoft 
Re: Final OS4 update stability survey
Posted on 3-Jan-2007 16:21:19
#67 ]
Cult Member
Joined: 3-Mar-2005
Posts: 585
From: Germany

@painter

> you're right one should pay attention to what you're running when crashes
> happen not assume that crashlog will have name of program in it's title.
> Which is what I did.

Crashlogs have the name of the task or process in the title. This name has
nothing to do with program names. And even when you told that the task was
"audio.device" this didnt help because the information which program called
audio.device in which way and where exactly audio.device called which kernel
function which crashed was missing.

> Data Address (dar) : 0x00010180

A read attempt from the read-protected zeropage.

> Stack trace:
> native kernel module kernel+0x0001541c
> native kernel module kernel+0x0001a464
> module DEVS:audio.device at 0x7FA59580 (section 4 @ 0x560)
> module DEVS:audio.device at 0x7FA5A2F4 (section 4 @ 0x12D4)

The task cleanup code of audio.device wanted to abort the still playing
sound, called ReplyMsg() and that crashed. Probable reason: The calling
application did quit without waiting for the sound to finish, or it
freed the IORequest before it was replied, something like that.

> VistaPro3.0 (Waiting)

Thats the only non-OS4 task/process name in your crashlog which I could
spot, maybe that was causing the crash. Try to reproduce it and when you
succeed, send the crashlog to the VistaPro author.

 Status: Offline
Profile     Report this post  
NutsAboutAmiga 
Re: Final OS4 update stability survey
Posted on 3-Jan-2007 16:22:47
#68 ]
Elite Member
Joined: 9-Jun-2004
Posts: 12988
From: Norway

@TetiSoft

Quote:

See the doc file for bootmenu (IIRC Documentation/Kickstart/bootmenu.doc),
and dont forget that only the OS4final version of bootmenu supports the
BootDevice feature, so you should make sure that you are loading the OS4final
version, not the update4 version of bootmenu.kmod in the KickLayout file
in the config section which describes what to load for update4. To be on the
safe side, also use the OS4final version of Loader. Yes, I can confirm both
of them do work when loaded together with update4 modules, tested it.


I tried you advice about using bootmenu.kmod and Loader form OS4 final to load update 4 modules, that did not work yellow guru,


This is what I will try to do next, I will set the DH1 whit the highest boot priority, then I will try to force OS4 final to boot on DH0,

this is how it looks in UBOOT bootmenu right now:

DH0 Boot OS4 Final
DH0 Update4

When I have module called BootDevice in the leayout file, I can see no indication that DH0 change to DH1 in the menu options, do you have any example of any kickstart layout files that works whit predefined boot partitions?

Last edited by NutsAboutAmiga on 03-Jan-2007 at 04:24 PM.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

 Status: Offline
Profile     Report this post  
TetiSoft 
Re: Final OS4 update stability survey
Posted on 3-Jan-2007 17:00:14
#69 ]
Cult Member
Joined: 3-Mar-2005
Posts: 585
From: Germany

@NutsAboutAmiga

> I tried you advice about using bootmenu.kmod and Loader form OS4 final to load update 4 modules, that did not work yellow guru,

Did you also read the advice that you need SLB V1.16 or higher installed
on the boot drive or its possible that the machine will crash?
AFAIK Media ToolBox can tell you which SLB is installed.

> this is how it looks in UBOOT bootmenu right now:
>
> DH0 Boot OS4 Final
> DH0 Update4
>
> When I have module called BootDevice in the leayout file, I can see no
> indication that DH0 change to DH1 in the menu options,

The menu is from SLB, when this is displayed, bootmenu didnt run yet,
ergo you cant expect that a config change in bootmenu affects SLB in any way.

If you want to see a clear indication that bootmenu was able to find
the BootDevice setting in your KickLayout file, was able to parse it
and was able to find the partition which was described as boot partition
in the file, then enter bootmenu :)
The "BootDevice" partition will have a boot priority of 127 IIRC, thats
much higher than all known defaults and thats the complete magic trick
hidden in the new bootmenu...

> do you have any example of any kickstart layout files that works whit
> predefined boot partitions?

Yes, the KickLayout file of my A4k contains a BootDevice entry because
the partition with the highest boot priority is still my OS3 partition
(just in case I mess something up I want to have a possibility to boot).

The A1SE KickLayout file looks like this:

[...]
LABEL Default
EXEC Kickstart/loader
MODULE Kickstart/kernel.debug
[...]
MODULE Kickstart/bootmenu.kmod
[...]
LABEL AmigaOS4.0
EXEC Kickstart/OS4final/loader
MODULE Kickstart/OS4final/kernel.debug
[...]
MODULE Kickstart/OS4final/bootmenu.kmod
[...]
MODULE Kickstart/OS4final/BootDevice

and the file Kickstart/OS4final/BootDevice looks like
----snip----
DH4
----snip----

Dont forget that this setup is the reverse case of yours, here
OS4final is the *old* configuration and Default is my current OS4.
DH0 has the highest boot priority and contains the current WB files,
DH4 has a lower boot priority and the OS4final WB files.
The Kickstart files on DH4 from the OS4final install are not used.

 Status: Offline
Profile     Report this post  
NutsAboutAmiga 
Re: Final OS4 update stability survey
Posted on 3-Jan-2007 17:23:33
#70 ]
Elite Member
Joined: 9-Jun-2004
Posts: 12988
From: Norway

@TetiSoft

Quote:

Did you also read the advice that you need SLB V1.16 or higher installed
on the boot drive or its possible that the machine will crash?
AFAIK Media ToolBox can tell you which SLB is installed.


I believe I checked that,

Quote:

If you want to see a clear indication that bootmenu was able to find
the BootDevice setting in your KickLayout file, was able to parse it
and was able to find the partition which was described as boot partition
in the file, then enter bootmenu :)


So bootmenu is the kickstart bootmenu, now I understand

In my kickstart layout file I have BootDevice first then Bootmenu, I don’t know if that’s the problem, it’s not written where it need to placed in the kickstart layout file,
some thing like this:

LABEL AmigaOS Final
EXEC Kickstart/loader
MODULE Kickstart/kernel.debug
[...]
MODULE Kickstart/bootmenu.kmod
[...]

LABEL AmigaOS update 4
MODULE Kickstart/update4/BootDevice
EXEC Kickstart/update4/loader
MODULE Kickstart/update4/kernel.debug
[...]
MODULE Kickstart/update4/bootmenu.kmod
[...]

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

 Status: Offline
Profile     Report this post  
painter 
Re: Final OS4 update stability survey
Posted on 3-Jan-2007 19:06:29
#71 ]
Cult Member
Joined: 5-Oct-2003
Posts: 681
From: Manitoba, Canada

@TetiSoft

Thank you. And Inow know more about reading what's important on a crashlog.


painter

 Status: Offline
Profile     Report this post  
TetiSoft 
Re: Final OS4 update stability survey
Posted on 3-Jan-2007 20:59:40
#72 ]
Cult Member
Joined: 3-Mar-2005
Posts: 585
From: Germany

@NutsAboutAmiga

> In my kickstart layout file I have BootDevice first then Bootmenu,
> I don't know if that's the problem, it's not written where it need to placed
> in the kickstart layout file,

Currently I'm not aware if the SLB needs a specific order of keywords or
not, I know that older versions of Loader required the kernel to be the
first MODULE entry. To be on the safe side, just follow the general layout
order of all existing KickLayout files, which is

LABEL Short text
EXEC Path/loader
MODULE Path/kernel
MODULE Path/module
MODULE Path/module2
[...]

Lines which start with ";" are comments, empty lines should be used
to separate different configs (and to terminate the last config,
just to be sure), no empty lines inside a config(!), each config should
start with the LABEL line followed by the EXEC line which must name the loader,
followed by multiple MODULE lines, the first MODULE line should name the kernel.

So in your example I'd move the MODULE line which specifies BootDevice
after the MODULE line which specifies the kernel.

 Status: Offline
Profile     Report this post  
NutsAboutAmiga 
Re: Final OS4 update stability survey
Posted on 4-Jan-2007 14:10:24
#73 ]
Elite Member
Joined: 9-Jun-2004
Posts: 12988
From: Norway

@TetiSoft

It’s working now.

When I changed boot priority of update4 to 5 and OS4 final back to 0, then kickstart modules where loaded from update 4, so after moving the kickstart stuff over to update 4, and forcing OS4 final to boot from DH0 using the BootDevice module in kicklayout , every thing worked.


_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

 Status: Offline
Profile     Report this post  
AV 
Re: Final OS4 update stability survey
Posted on 4-Jan-2007 15:33:15
#74 ]
Regular Member
Joined: 1-Aug-2003
Posts: 184
From: Unknown

@TetiSoft

Quote:

Currently I'm not aware if the SLB needs a specific order of keywords or
not, I know that older versions of Loader required the kernel to be the
first MODULE entry.


SLB doesn't care about the order of entries: it just loads them one after the other.
The module list is then passed to Loader for relocation. That's it.

 Status: Offline
Profile     Report this post  
khayoz 
Re: Final OS4 update stability survey
Posted on 4-Jan-2007 22:10:29
#75 ]
Regular Member
Joined: 26-Dec-2004
Posts: 216
From: Stockholm, Sweden

@virgolamobile

It's steady as a rock over here, formated the hdd and did a clean install.
I didnt have much trouble with the last update either, but this one is faster.
Had 1 Reaper when i extracted a 68k sfx archive to RAD:, but it did't stop it from being extracted and the system went on as usual with TuneNet and IBrowse open. 2 years of waiting is over :)

_________________

 Status: Offline
Profile     Report this post  
fricopal! 
Re: Final OS4 update stability survey
Posted on 20-Mar-2025 2:44:52
#76 ]
Cult Member
Joined: 12-Mar-2025
Posts: 799
From: Unknown

Quote:
by STRICQ on 3-Jan-2007 2:33:54

@painter

Sounds like your RAM is incompatible. Get better RAM.


The user's computer likely has a memory issue due to using non-compliant RAM sticks, and they should consider upgrading with compatible ones for optimal performance.

 Status: Offline
Profile     Report this post  
Goto page ( Previous Page 1 | 2 | 3 | 4 )

[ home ][ about us ][ privacy ] [ forums ][ classifieds ] [ links ][ news archive ] [ link to us ][ user account ]
Copyright (C) 2000 - 2019 Amigaworld.net.
Amigaworld.net was originally founded by David Doyle