Am 20.08.2007 um 21:26 schrieb Blue Swirl:
On 8/19/07, Nigel Horne <[EMAIL PROTECTED]> wrote:
On the CVS version, networking has stopped working again with Sparc
guests running Debian Linux.
It had been working fine for a few weeks, but the latest version is
broken again, with the device
not b
On 8/19/07, Nigel Horne <[EMAIL PROTECTED]> wrote:
> On the CVS version, networking has stopped working again with Sparc
> guests running Debian Linux.
> It had been working fine for a few weeks, but the latest version is
> broken again, with the device
> not being found.
I cannot reproduce this o
On the CVS version, networking has stopped working again with Sparc
guests running Debian Linux.
It had been working fine for a few weeks, but the latest version is
broken again, with the device
not being found.
-Nigel
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
Once I got an infinite loop of esp0 timeout messages during boot
(not reproducable).
Just got it again, it's:
esp0: Data transfer overrun.
With the lance network fixed being able to do some more now, I am
seeing a number of other issues:
- When there is a network timeout the console starts
"scrolling" (text moves up and screen stays blank).
To reproduce, run svn checkout svn://10.0.0.1 (with 10.0.0.1 not
available). On others
Andreas Färber wrote:
Am 28.06.2007 um 17:26 schrieb Blue Swirl:
I found the problem, it wasn't related to Debian's 2.6 kernel after
all, but pcnet just didn't work on a 32-bit host. I'm committing a
fix.
Big thanks for fixing this! Works now. :-)
And here as well. Well done, thanks.
And
Am 28.06.2007 um 17:26 schrieb Blue Swirl:
I found the problem, it wasn't related to Debian's 2.6 kernel after
all, but pcnet just didn't work on a 32-bit host. I'm committing a
fix.
Big thanks for fixing this! Works now. :-)
Andreas
I found the problem, it wasn't related to Debian's 2.6 kernel after
all, but pcnet just didn't work on a 32-bit host. I'm committing a
fix.
On 6/28/07, Andreas Färber <[EMAIL PROTECTED]> wrote:
So maybe it's a more general problem with interrupt handling?
Lance complains about timeouts, too, and
Am 27.06.2007 um 22:43 schrieb Blue Swirl:
On 6/27/07, Nigel Horne <[EMAIL PROTECTED]> wrote:
Thiemo Seufer wrote:
> Blue Swirl wrote:
>> On 6/25/07, Thiemo Seufer <[EMAIL PROTECTED]> wrote:
>>> Nigel Horne wrote:
Good news, sparc emulation with -nographic no longer core dumps.
On 6/27/07, Nigel Horne <[EMAIL PROTECTED]> wrote:
Thiemo Seufer wrote:
> Blue Swirl wrote:
>> On 6/25/07, Thiemo Seufer <[EMAIL PROTECTED]> wrote:
>>> Nigel Horne wrote:
Good news, sparc emulation with -nographic no longer core dumps.
The bad news, networking still fails:
>>> FYI,
Thiemo Seufer wrote:
Blue Swirl wrote:
On 6/25/07, Thiemo Seufer <[EMAIL PROTECTED]> wrote:
Nigel Horne wrote:
Good news, sparc emulation with -nographic no longer core dumps.
The bad news, networking still fails:
FYI, I see a transmit error for ne2k_isa on mips r4k. Maybe that's
related.
O
Blue Swirl wrote:
> On 6/25/07, Thiemo Seufer <[EMAIL PROTECTED]> wrote:
> >Nigel Horne wrote:
> >> Good news, sparc emulation with -nographic no longer core dumps.
> >>
> >> The bad news, networking still fails:
> >
> >FYI, I see a transmit error for ne2k_isa on mips r4k. Maybe that's
> >related.
Am 25.06.2007 um 22:07 schrieb Nigel Horne:
Blue Swirl wrote:
On 6/25/07, Thiemo Seufer <[EMAIL PROTECTED]> wrote:
Nigel Horne wrote:
> Good news, sparc emulation with -nographic no longer core dumps.
>
> The bad news, networking still fails:
FYI, I see a transmit error for ne2k_isa on mips
Blue Swirl wrote:
On 6/25/07, Thiemo Seufer <[EMAIL PROTECTED]> wrote:
Nigel Horne wrote:
> Good news, sparc emulation with -nographic no longer core dumps.
>
> The bad news, networking still fails:
FYI, I see a transmit error for ne2k_isa on mips r4k. Maybe that's
related.
On my test cases t
On 6/25/07, Thiemo Seufer <[EMAIL PROTECTED]> wrote:
Nigel Horne wrote:
> Good news, sparc emulation with -nographic no longer core dumps.
>
> The bad news, networking still fails:
FYI, I see a transmit error for ne2k_isa on mips r4k. Maybe that's
related.
On my test cases the network is still
Nigel Horne wrote:
> Good news, sparc emulation with -nographic no longer core dumps.
>
> The bad news, networking still fails:
FYI, I see a transmit error for ne2k_isa on mips r4k. Maybe that's
related.
Thiemo
Good news, sparc emulation with -nographic no longer core dumps.
The bad news, networking still fails:
SunLance: using auto-carrier-detection.
eth0: LANCE 52:54:00:12:34:56
Skipping already loaded module esp.
Setting up networking...done.
Setting up IP spoofing protection: rp_filter.
Config
31 matches
Mail list logo
