bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

driver problems of Hurd in qemu


From: Da Zheng
Subject: driver problems of Hurd in qemu
Date: Tue, 04 May 2010 17:28:42 +0800
User-agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4

Hello,

I ran different versions of gnumach in different versions of qemu. I got the
Hurd image for qemu from
http://ftp.debian-ports.org/debian-cd/K16/debian-hurd-k16-qemu.img.tar.gz. The
gnumach in the original image runs well in qemu v0.9.1. I built the gnumach from
the master branch of the git repository and got the error:
start /hurd/ext2fs.static: hd0: irq timeout: status=0xd8 { Busy }
hd0: disabled DMA
hd1: disabled DMA
ide0: reset: success
Hurd server bootstrap: ext2fs.static[device:hd0s1] exec init proc authswapon:
/dev/hd0s2: Linux 2.2 swap signature v1, 532220k swap-space (excludes 8k at end
of partition)

Then I tried to run hurd in qemu v0.12.3 because I need the e1000 NIC card.
Again, I first ran gnumach in the original image and got the message as follows:
task loaded: /lib/ld.so.1 /hurd/exec start /hurd/ext2fs.static:
hd0: read_intr: status=0x41 { DriveReady Error }
hd0: read_intr: error=0x04 { DriveStatusError }
hd0: read_intr: status=0x41 { DriveReady Error }
hd0: read_intr: error=0x04 { DriveStatusError }
hd0: read_intr: status=0x41 { DriveReady Error }
hd0: read_intr: error=0x04 { DriveStatusError }
hd0: read_intr: status=0x41 { DriveReady Error }
hd0: read_intr: error=0x04 { DriveStatusError }
ide0: reset: success
hd0: read_intr: status=0x41 { DriveReady Error }
hd0: read_intr: error=0x04 { DriveStatusError }
hd0: read_intr: status=0x41 { DriveReady Error }
hd0: read_intr: error=0x04 { DriveStatusError }
hd0: read_intr: status=0x41 { DriveReady Error }
hd0: read_intr: error=0x04 { DriveStatusError }
hd0: read_intr: status=0x41 { DriveReady Error }
hd0: read_intr: error=0x04 { DriveStatusError }
ide0: reset: success
hd0: read_intr: status=0x41 { DriveReady Error }
hd0: read_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev 03:02, sector 28
Hurd server bootstrap: ext2fs.static[device:hd0s1] exec init proc auth

Then I ran gnumach in the git repository, and got similar errors:
start /hurd/ext2fs.static: hd0: dma_intr: status=0x41 { DriveReady Error }
hd0: dma_intr: error=0x04 { DriveStatusError }
hd0: dma_intr: status=0x41 { DriveReady Error }
hd0: dma_intr: error=0x04 { DriveStatusError }
hd0: dma_intr: status=0x41 { DriveReady Error }
hd0: dma_intr: error=0x04 { DriveStatusError }
hd0: dma_intr: status=0x41 { DriveReady Error }
hd0: dma_intr: error=0x04 { DriveStatusError }
hd0: disabled DMA
hd1: disabled DMA
ide0: reset: success
hd0: read_intr: status=0x41 { DriveReady Error }
hd0: read_intr: error=0x04 { DriveStatusError }
hd0: read_intr: status=0x41 { DriveReady Error }
hd0: read_intr: error=0x04 { DriveStatusError }
hd0: read_intr: status=0x41 { DriveReady Error }
hd0: read_intr: error=0x04 { DriveStatusError }
hd0: read_intr: status=0x41 { DriveReady Error }
hd0: read_intr: error=0x04 { DriveStatusError }
ide0: reset: success
hd0: read_intr: status=0x41 { DriveReady Error }
hd0: read_intr: error=0x04 { DriveStatusError }
end_request: I/O error, dev 03:02, sector 28
Hurd server bootstrap: ext2fs.static[device:hd0s1] exec init proc auth

It seems that when using the gnumach from the git repository, DMA is disabled
and the system is very slow especially when I compile programs. And the system
hangs very easily.

Are these known problems? I didn't find any discussion on this mailing list. Is
there any easy fix?

Best regards,
Zheng Da




reply via email to

[Prev in Thread] Current Thread [Next in Thread]