-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WATCHDOG TIMEOUT when using latest release 23.05.25 #231
Comments
[9913ms] DBG -- BUS_BUSY [9913ms] DBG ---- SELECTION: 0 [9915ms] DBG ---- COMMAND: Read6 [9915ms] DBG ------ OUT: 0x08 0x00 0x00 0x20 0x00 0x00 [9915ms] DBG ------ Read 0x2048 starting at 32 [9916ms] DBG ---- DATA_IN [9917ms] DBG ------ Found 0 sectors in prefetch cache [9917ms] DBG ---- Total IN: 0 OUT: 0 CHECKSUM: 0 [9918ms] DBG ---- STATUS: 0 GOOD From SCSI-2 spec:
but the new code added in fcac5ae lacks the special case of 0 = 256. I'll get this fixed, thanks for the report! |
Block count of 0 means 256 blocks in SCSI READ(6) command. This bug was introduced in commit fcac5ae and is present in versions 2023-05-24 and 2023-05-25.
There is a test build here that you can try (download zip at bottom of page): |
@WhatIsTheWeather thanks for the report. Please try the build @PetteriAimonen linked to above if you're able to. |
Thanks for getting a new build created so quickly. I can confirm that the new build has fixed the issue. I have installed two ZuluSCSI units into the machine to replace the A and B side CD drives and both are working fine with the latest build. I will keep updating both with the new releases as they appear and will report any further bugs I find. Thanks :). |
Fix regression in CD-ROM READ(6) command (#231)
When using the latest ZuluSCSI release with my digital master unit I have been experiencing the error WATCHDOG TIMEOUT, followed by a bus reset, with the machine unable to read the iso stored on the SD card. I can confirm that this error is not present in the previous ZuluSCSI release. I have attached a log from the previous release that works with the machine and log from the newest release with the bug. The ZULUSCSI is set up as a CDROM and I have not changed the iso when testing both versions. Previous versions since read lead-out area information was added work fine, just not the latest release.
zululogworking.txt
zululog.txt
The text was updated successfully, but these errors were encountered: