@Maijestro

Using the existing 2.9 build, Rhea crashes, is this something you've been able to look into?

https://bugs.scummvm.org/ticket/15865

@joerg
Quote:
I checked everything before: none works. I tested many versions of rtl8139 with no luck, same as ne2000 (didnt eork at all on qemu) and so on.


As for interrupts and speed:

Why then on all machines include x5000 rtl8139 show no bugs ? Too slow in compare with qemu ? But imho x5000 faster than qemu emulation, shouldnt be issue with too many irqs ?

Also, all in all, we can try non interrupt way for virtionet.device , i mean this busy-waiting/polling by cpu instead of irqs ? I tried it on real x1000 now (i mean non interrupt way) and while have ai bugs it works, and i didnt see lot of cpu loading (if at all) probably because roadshow limited speed anyway .. maybe as test worth of try ?

@smarkusg
I betatester so were able to test many versions : none works ..

@kas1e
I thought that RTL8139 only works well under Windows
The only person who did not report any problems was using Windows (he did not specify which driver version he was using)
It does not work properly on any emulated machine (A1, Peg2, and Sam460 - official driver even 53.11 and unofficial 53.7).
What version of the RTL8139 driver are you using?
The 53.7 driver can be easily identified even when starting the system with debug
it prints additional information that is not available in the final versions
--
[HW_BoardReset] PCI Vendor ID...: 0x10EC
PCI Device ID...: 0x8139
PCI Capabilities: 0x00000003
PCI IO Range....: 0x00001200
[HW_SpeedSetup] Unit 0: 100Mbps full-duplex operation!
[HW_BoardInit] Board at unit 0 ready for operation!
--
There was a discussion about problems with RTl8139 two years ago. You would have to go through all these topics, which could take a long time.
I also don't remember how MorphOS worked with RTL8139 and Qemu.

@joerg
I changed the IRQ for A1 and PEG2 - it didn't help. The problem was the same - complete disconnection of the driver/device after a while.
RTL8129 does not work under QEMU and ASO4.

The best test would be to insert an RTL8139 PCI card into a machine with QEMU PCI passthrough.
Pass the RTL8139 card directly to AOS4 on Peg2 or A1 emulation and check.
My machine is packed away in a cupboard. Maybe I'll run it when QEMU-11 comes out.
If anyone has a machine with QEMU PCI passthrough, they can check it themselves.

@msteed

Quote:
It was a race condition. More details in my next blog post

@trixie

Quote:
With all the weird symptoms, I'm curious what the problem turned out to be.

@kas1e
Quote:From the Ranger screenshot: "Interrupt: Line 0x09, PIN: A"
Looks like Pegasos2 emulation. That will never work reliable, at least not with any of the public kernel versions...
Try AmigaOne or Sam460 emulation instead.

@trixieQuote:
Thank to both of you!

@smarkusg
Using RTL8139 with QEmu doesn't make any sense, instead you should always try to emulate the simplest hardware as it's less likely to have emulation bugs and emulating simple hardware is usually faster than emulating more complex hardware.
For example NE2000 (rtl8029.device), or if it's supported by QEmu the 3Com (AmigaOne) or VIA Rhine (Pegasos2).

Also very important: Make sure the IRQ used for the network card (emulation) isn't shared with other PCI devices.
Ethernet I/O causes a huge number of IRQs per second anyway, with fast emulation maybe more than the kernel, other parts of the OS or drivers can handle, but if the same IRQ is shared with other PCI devices as well it's nearly guarantied to fail...
It may be a problem on the Pegasos2 which AFAIK uses a single IRQ for all PCI devices, but on the AmigaOne you have 4 IRQs which are freely configurable for each PCI port.

In case there is a problem in the kernel, the TCP/IP stack or the SANA-II drivers handling thousands of IRQs per second it's getting worse with virtio: Less overhead -> more speed -> more IRQs and task switches per second.

@Tuvok

Welcome to the the top ten high score list at amiboing.de

@ graff

Thanks

@smarkusg
I read somewhere that issues with rtl driver happens only on the windows version of qemu, did i get it right that you have them on linux too ? (just want to understand the patterns with both rtl and virtio drivers issues)

That's amazing afxgroup. Many thanks for all your work!!!

@kas1e

I have to mention this: You did check your cell battery, right?

Sorry if of course you already checked this, but so often problems similar to yours are caused by a slightly (or more) worn out battery.

BTW, my X1000 also does not show this problem, although it is connected to a switch, not directly to the router, but that's probably not relevant.

Best regards,

Niels

@graff

Thanks for the hint.

I am using a KVM, yes but the issue appeared after installing update 3. I was using the same kvm with update 2.

However, I will try your suggestion.

@balatonQuote:

How to check memory?
There is memtester on os4depot but it I wonder if the test itself is any good as it can not test the whole memory I suppose. At least not the part already used by the OS and Kickstart.

There is some memory test in CFE, but I never really understand how to make it work for all the installed memory. it just hangs.

C64 2D Cartoon Animation Demo | Commodore-64 Graphics PixelArt 8Bit LowRes 16 Colors



for more videos please subscribe to my youtube channel

Here i am sharing the Part 4 of VHS video of Amiga Deluxe Paint Video titleing Cartoon Style Animations ads overlay on 1990s Indian VHS Movies in Pakistan and India.

They all commercial ads animations are made with Amiga Deluxe Paint Animation Software. So please appreciate the creativity of those hardwork animators in 1990s.

Here is the link of the youtube video part 4, i made from Old VHS tape:



Previous Parts:
Link of forum post for Part 1
Link of forum post for Part 2
Link of forum post for Part 3

I will add more Amiga Deluxe Paint Animation videos to my channel so please subscribe it.
Hope you will like it.
Happy Amiga...!

Video Link is Updated

Video Link is Updated

Video Link is Updated

@joerg
Quote:
Yes, I use this driver. It works quite well for my purposes, and I have no complaints about it.
But it can also crash.
For example, if you start copying a large number of very small files (such as program sources via RNOXfer), the driver will stop working.
But I've learned how to use it.
Quote:
MTU cannot be changed to AOS4 above the value of 1500. Above this value, e.g., 9000, they change to 1500.
It is possible to change something using Roadshowcontrol.
Changing the tcp.sendspace/tcp.recvspace value to the minimum value with the virtio-net.device driver causes a very quick “TransmitPacket: TX timout ..” error.
I don't really know where this comes from and where the value 1000000 comes from.

I tried on the qemu side and with the virtio-net-pci options to limit the RX buffer and speed, but it didn't help.
But as I wrote, after the error “TransmitPacket: TX timout ..” appeared, the driver
It still works. Something has stifled it.

I have no idea how to quickly clear buffers in AOS4, reset certain things like in Linux. It's hard to find any documentation for AOS4.

The virtio-net.device driver is definitely faster than RTL8139.
Maybe the symptoms show up faster, but is that a problem with the early version of the virtio-net.device driver?

I'll play around with it some more