2022-05-24.log

+ gdonner (gdonner@c-98-253-93-116.hsd1.in.comcast.net)01:00
gdonnerRe: Super Buster revs: Yeah, my A3000 is one of the early 16 MHz '030s, and it had a rev. 7 Super Buster in it. One of the first things I did when upgrading it was replace it with a rev. 11 chip.01:01
gdonnerMy A4000 had a rev. 9; also got swiftly replaced with a rev. 11 (among other upgrades).01:03
gdonnerIf socketed, very easy to upgrade with the right chip puller :)01:04
- gdonner (QUIT: ) (gdonner@c-98-253-93-116.hsd1.in.comcast.net)01:11
+ mnemotron (mnemotron@194.135.47.239)08:07
mnemotrongood morning08:07
+ CottonUndies (~CottonUnd@2405:6580:33c0:b400:3884:240d:eb9a:34e6)08:13
CottonUndiesmnemotron good day to you08:13
mnemotronhey there08:13
mnemotrondid you get your problems sorted out?08:14
CottonUndiesminute I think I've found the culprit for my freezes. The happy outcome of non-stop testing......08:14
CottonUndiesI'm pretty sure I know whats causing ATK to freeze between 1.10FW and 1.11FW.08:14
CottonUndiesI'm not sure if its documented in the release notes, but the closest I can find that associates with my fix for the issue is....... none other than... the first and foremost on the list!!!!08:16
CottonUndies"Improves/Fixes ZZ9000AX playback on many Amiga models through improved IRQ behavior (also improves Ethernet)"08:16
CottonUndiesI say this, becuase if I comment out of my s:network-startup "AddNetInterface DEVS:NetInterfaces/~(#?.info) QUIET , then ATK no longer freezes. The only device in that location is ZZ9000Net08:17
CottonUndiesThis also might explain while Ibrowse freezes occasionally while scrolling.08:18
mnemotronInteresting!08:23
mnemotronDid you also try to disable the cpu data cache like on my 3000?08:23
mnemotronI only start networking with MiamiDX when I need it08:23
CottonUndiesNo, as I now know this is the problem for me I need to see how the boss views this, as the difference between 1.10 and 1.11 was to also "improve Ethernet" "through improved IRQ behavior". So I'm sure this isn't "my problem" per say. Also, in a properly working system, I would never want to turn off any CPU caching, the performance hit is08:26
CottonUndiessignificant.08:26
mnemotronYeah, of course. I meant it only for double-checking08:27
mnemotronor cross-checking08:27
CottonUndiesBTW, you say you only start networking when you need it, but in your startup when/where do you eventually do the ""AddNetInterface DEVS:NetInterfaces/~(#?.info) QUIET " as I assume you need to to that as well at some point?08:28
mnemotroni don't think so. it's all in MiamiDX08:31
mnemotronI start the MiamiDX gui08:31
CottonUndiesWithout starting MiamiDX does Sysinfo show under DEVICES ZZ9000Net V1.2?08:37
mnemotronwait08:37
mnemotronwhen i look in ShowConfig it only lists zzusb.device under Devices08:38
CottonUndiesDo you have Sysinfo? What argurments do you use for SHowConfig?08:39
mnemotronno arguments with ShowConfig. it's in Tools08:40
mnemotronhm, i should have sysinfo somewhere08:40
mnemotronah. Work: Download/SysInfo :)08:41
CottonUndiesMy Showconfig doesn't show that level of detail.... my version is 45.208:41
mnemotroni have OS 3.2.108:41
CottonUndiesthat might explain it, I think I'm 3.208:41
mnemotronsysinfo shows zzusb V43.0 in Devices08:41
CottonUndiesok, well, the bad news is I don't have a solution for you. The good news is you don't need to be concerned about my issue potentially being your issue, as I assume your testing/crashing happens without you loading MiamiDX, and therefore at that time the device.08:43
mnemotronsysinfo: https://i.imgur.com/f9EZ6Nk.jpg08:45
mnemotronshowconfig https://i.imgur.com/tT1Wrqh.jpg08:45
mnemotronCottonUndies: yep08:45
CottonUndiesOhhh, very nice looking showconfig!08:46
mnemotronindeed08:54
minuteCottonUndies: i see, good investigation08:56
_BnuAlso yes, IRQ problems are the main reason for Amiga Test Kit locking up or crashing to the debug trace screen.08:56
minutethis is why i did the "weird" old IRQ behavior where the interrupt was just a pulse, because sometimes, things would hang 08:57
_BnuBut the AX IRQ shouldn't be active unless the driver has enabled it.08:57
minuteit's not AX, it's ethernet08:57
_BnuAh, I see.08:57
minutei have rewritten how both of the interrupts work08:58
minute(in 1.11)08:58
minutefor example, if something like ATK prevents interrupts from being handled, but it doesn't shut down ethernet before, this makes sense09:00
_BnuI don't know much about what Amiga Test Kit does if you launch it from Workbench, never tried.09:02
_BnuI always boot it from floppy to avoid problems with random libraries that may be loaded.09:02
mnemotronany quick idea why my a3000 is 0.88 as fast as an a3000? https://i.imgur.com/w4A3gLJ.jpg09:06
CottonUndiesCould this also be why I get freezes when scrolling in IBrowse09:06
CottonUndies?09:06
mnemotroni enabled the datacache for this. without it was 0.7709:06
minuteCottonUndies: well, you can test that by opening a website, then calling c:netshutdown in a shell while keeping the browser open, and then scroll the website a lot09:08
_Bnumnemotron: Probably because you're using the physical Kickstart ROM rather than having it mapped to Fast RAM.09:32
_BnuIt slows things down quite a bit.09:33
mnemotronoh? let me enable fastrom then... sec09:33
CottonUndiesminute It seemed better for a moment, then froze. One thing I did check before scrolling the 2nd time was check the device in Sysinfo, and it was still showing up, even though I had issued c:netshutdown09:35
mnemotronhaha, now it's slower... only 0.80 instead of 0.8809:35
CottonUndieseven the locally loaded iBrowse splash screen feezes. Let me try not loading the device the first time.09:36
CottonUndiesfreeze happens even if I dont add the net device. hmmm.09:38
mnemotronaha!09:45
- CottonUndies (QUIT: Quit: Client closed) (~CottonUnd@2405:6580:33c0:b400:3884:240d:eb9a:34e6)10:12
_Bnu('A`)10:13
_BnuIs the Fast RAM on the A3000 motherboard that slow?10:13
_BnuI'm not familiar with the 3000, really.10:13
_BnuBut typically you get really good speeds in SysInfo with a 68030...10:14
+ CottonUndies (~CottonUnd@2405:6580:33c0:b400:3884:240d:eb9a:34e6)10:15
mnemotronstrange11:50
Jopeamiga test kit will definitely hang your system if you start it from the wb with a tcp stack running12:22
Jopesame problem as with whdload if you leave your tcp stack up when you start a game12:22
Jopethe hang comes from the network hw interrupt that is no longr served when the os is thrown out12:22
CottonUndiesNot under 1.10FW12:41
CottonUndiesat least that is my own repeatable testing result!12:41
CottonUndiesInteresting whdload comment, as I also use it without problems (with roadshow running) up to FW1.10, haven't tried 1.11FW and whdload yet. Something to try!12:42
CottonUndiesminute iBrowse scrolling also prolematic under 1.10FW. Just did a quick test.12:52
CottonUndiesJope Whdload seems to be working for me with my stack loaded on FW1.11.13:06
- CottonUndies (QUIT: Quit: Client closed) (~CottonUnd@2405:6580:33c0:b400:3884:240d:eb9a:34e6)13:20
+ CottonUndies (~CottonUnd@2405:6580:33c0:b400:3884:240d:eb9a:34e6)14:50
_BnuIt's very hit and miss in my experience.16:04
- CottonUndies (QUIT: Quit: Client closed) (~CottonUnd@2405:6580:33c0:b400:3884:240d:eb9a:34e6)16:50
- mnemotron (QUIT: Quit: L8r) (mnemotron@194.135.47.239)17:07
+ xet7 (~xet7@user/xet7)20:38
- xet7 (QUIT: Remote host closed the connection) (~xet7@user/xet7)20:40
+ xet7 (~xet7@user/xet7)20:41

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!