I reworked the interrupt handling so that both e2fsck and SMP work.
Previously there may have been lost or spurious interrupts, now they
should be fixed. I pushed the interrupt priority handling from
SLAVIO to CPU.
I seem to have reverted the patch here:
http://cvs.savannah.gnu.org/viewvc/qemu/qemu/hw/slavio_intctl.c?r1=1.15&r2=1.16
But I still get SCSI errors when using e2fsck with this change.
On 8/3/07, Andreas Färber <[EMAIL PROTECTED]> wrote:
>
> Am 03.08.2007 um 16:54 schrieb Aurelien Jarno:
>
> >>> I
Am 03.08.2007 um 16:54 schrieb Aurelien Jarno:
I suggest to read the description of the problem from last time:
http://www.mail-archive.com/qemu-devel%40nongnu.org/msg08828.html
I guess there is still one case when this can happen. The only
solution
I see to avoid that is to fix the bug (the p
Andreas Färber a écrit :
> Am 03.08.2007 um 16:15 schrieb Aurelien Jarno:
>
>> Andreas Färber a écrit :
>>> Am 03.08.2007 um 13:52 schrieb Aurelien Jarno:
>>>
The problem appears when one interrupt on the SCSI controller is
triggered twice by the interrupt controller, the second interrup
Am 03.08.2007 um 16:15 schrieb Aurelien Jarno:
Andreas Färber a écrit :
Am 03.08.2007 um 13:52 schrieb Aurelien Jarno:
The problem appears when one interrupt on the SCSI controller is
triggered twice by the interrupt controller, the second interrupt
disturb the driver.
I have fixed one prob
Am 03.08.2007 um 14:02 schrieb Nigel Horne:
Guest: Linux/sparc
Host: Linux/x86
From time to time I am getting SCSI errors from the guest
using the
latest CVS:
scsi : aborting command due to timeout : pid 50803, scsi0,
channel 0, id 0, lun 0 0x2a 00 00 3d be 84 00 00 08 00 esp0:
Aborting co
Andreas Färber a écrit :
> Am 03.08.2007 um 13:52 schrieb Aurelien Jarno:
>
>> The problem appears when one interrupt on the SCSI controller is
>> triggered twice by the interrupt controller, the second interrupt
>> disturb the driver.
>>
>> I have fixed one problem like that a few months ago in t
Am 03.08.2007 um 13:52 schrieb Aurelien Jarno:
The problem appears when one interrupt on the SCSI controller is
triggered twice by the interrupt controller, the second interrupt
disturb the driver.
I have fixed one problem like that a few months ago in the CVS, so it
happens less often, but th
> Am 03.08.2007 um 12:42 schrieb Nigel Horne:
>
> > Andreas Färber wrote:
> >> Am 03.08.2007 um 10:45 schrieb Nigel Horne:
> >>> Guest: Linux/sparc
> >>> Host: Linux/x86
> >>>
> From time to time I am getting SCSI errors from the guest using the
> >>> latest CVS:
> >>>
> >>> scsi : aborting c
Andreas Färber a écrit :
> Am 03.08.2007 um 10:45 schrieb Nigel Horne:
>
>> Guest: Linux/sparc
>> Host: Linux/x86
>>
>>> From time to time I am getting SCSI errors from the guest using the
>> latest CVS:
>>
>> scsi : aborting command due to timeout : pid 50803, scsi0, channel
>> 0, id 0, lun 0 0
Am 03.08.2007 um 12:42 schrieb Nigel Horne:
Andreas Färber wrote:
Am 03.08.2007 um 10:45 schrieb Nigel Horne:
Guest: Linux/sparc
Host: Linux/x86
From time to time I am getting SCSI errors from the guest using the
latest CVS:
scsi : aborting command due to timeout : pid 50803, scsi0,
cha
Andreas Färber wrote:
Am 03.08.2007 um 10:45 schrieb Nigel Horne:
Guest: Linux/sparc
Host: Linux/x86
From time to time I am getting SCSI errors from the guest using the
latest CVS:
scsi : aborting command due to timeout : pid 50803, scsi0, channel 0,
id 0, lun 0 0x2a 00 00 3d be 84 00 00
Am 03.08.2007 um 10:45 schrieb Nigel Horne:
Guest: Linux/sparc
Host: Linux/x86
From time to time I am getting SCSI errors from the guest using the
latest CVS:
scsi : aborting command due to timeout : pid 50803, scsi0, channel
0, id 0, lun 0 0x2a 00 00 3d be 84 00 00 08 00 esp0: Aborting c
Guest: Linux/sparc
Host: Linux/x86
From time to time I am getting SCSI errors from the guest using the
latest CVS:
scsi : aborting command due to timeout : pid 50803, scsi0, channel 0, id 0, lun 0 0x2a 00 00 3d be 84 00 00 08 00
esp0: Aborting command
esp0: dumping state
esp0: dma -- cond_re
14 matches
Mail list logo
