NetBSD-Bugs archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: port-sparc/46530 (Install failure of NetBSD/sparc 5.1.2and6.0_BETA2 on qemu-1.0.1 and 1.1.0)
The following reply was made to PR port-sparc/46530; it has been noted by GNATS.
From: Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: tsutsui%ceres.dti.ne.jp@localhost
Subject: Re: port-sparc/46530 (Install failure of NetBSD/sparc 5.1.2and6.0_BETA2
on qemu-1.0.1 and 1.1.0)
Date: Sat, 29 Sep 2012 02:40:39 +0900
> On qemu-0.15.1 and -0.14, I have gotten timeout errors.
> I cannot understand why I had missed these errors...
Are these errors are reproducible everytime?
On my environment, !TC (stat 0x83) errors *sometimes* happen.
> 6.0_RC2 on qemu-1.2.0
>
> sd0 at scsibus0 target 0 lun 0: <QEMU, QEMU HARDDISK, 1.2.> disk fixed
> sd0: 3072 MB, 6241 cyl, 16 head, 63 sec, 512 bytes/sect x 6291456 sectors
Note on qemu-1.2.0 it doesn't print the following line:
>> sd0: async, 8-bit transfers
This is probably because QEMU's esp.c returns all bits of CFG2 register
(so our ncr53c9x recognizes it as ESP200 and assumes SELATN3 is valid)
but QEMU doesn't implement SELATN3 command.
Making QEMU's esp.c ignores CFG2 and CFG3 registers
seems to fix !TC messages, but now it *sometimes* gets
following error:
>> esp0: unexpected status after select: [intr 10, stat 97, step 0]
so I'm still afraid QEMU has some timing issue between scsi and esp.
---
@@ -537,10 +556,12 @@
case ESP_WBUSID ... ESP_WSYNO:
break;
case ESP_CFG1:
- case ESP_CFG2: case ESP_CFG3:
case ESP_RES3: case ESP_RES4:
s->rregs[saddr] = val;
break;
+ case ESP_CFG2: case ESP_CFG3:
+ s->rregs[saddr] = 0;
+ break;
case ESP_WCCF ... ESP_WTEST:
break;
default:
---
Izumi Tsutsui
Home |
Main Index |
Thread Index |
Old Index