* [Qemu-devel] AHCI problems.
@ 2011-05-15 16:41 Alexey Zaytsev
2011-05-17 13:46 ` Alexander Graf
0 siblings, 1 reply; 11+ messages in thread
From: Alexey Zaytsev @ 2011-05-15 16:41 UTC (permalink / raw)
To: qemu-devel; +Cc: Kevin Wolf, Alexander Graf
[-- Attachment #1: Type: text/plain, Size: 2149 bytes --]
Hi again.
After reverting 667bb59, ahci works fine in Linux, if I boot it with
-kernel, but grub seems to have some problems.
Grub2 gets to the rescue prompt. The disk and its partitions seem to
be detected correctly, but not the filesystem.
Grub-legacy (from illumos) complains about checksum verification
failures, supposedly in stage2.
I'm running with the current seabios and qemu gits. The command is
/home/xl0/work/nex/qemu/x86_64-softmmu/qemu-system-x86_64 -serial
stdio -drive id=disk,file=debian.raw,if=none -device ahci,id=ahci
-device ide-drive,drive=disk,bus=ahci.0 -L
/home/xl0/work/nex/seabios-bin
In the seabios debug, I'm seeing a single ERROR from ahci, but not
sure if it's related:
init hard drives
ATA controller 0 at 1f0/3f4/c000 (irq 14 dev 9)
ATA controller 1 at 170/374/c008 (irq 15 dev 9)
init ahci
AHCI controller at 04.0, iobase f2060000, irq 11
32: pci read : f2060004
32: pci write: f2060004, 80000000 (0x00006ec4)
32: pci read : f2060000
32: pci read : f206000c
AHCI: cap 0x40141f05, ports_impl 0x3f
AHCI/0: probing
32: pci read : f2060118
32: pci read : f2060130
32: pci write: f2060114, 0 (0x00006e58)
32: pci read : f2060110
32: pci read : f2060120
32: pci read : f2060128
AHCI/0: link up
ebda moved from 9fc00 to 9f800
ebda moved from 9f800 to 9f400
32: pci write: f2060100, 9fc00 (0x00006c2c)
32: pci write: f2060108, 9fb00 (0x00006c2c)
32: pci read : f2060118
32: pci write: f2060118, 16 (0x00006c2c)
32: pci read : f2060118
32: pci write: f2060118, 4017 (0x00006c0c)
32: pci read : f2060138
AHCI/0: send cmd ...
32: pci write: f2060134, 1 (0x00006c04)
32: pci write: f2060138, 1 (0x00006c04)
32: pci read : f2060138
AHCI/0: ... finished, status 0x41, ERROR
32: pci read : f2060118
32: pci write: f2060118, c017 (0x00006c0c)
32: pci read : f2060138
AHCI/0: send cmd ...
32: pci write: f2060134, 1 (0x00006c04)
32: pci write: f2060138, 1 (0x00006c04)
32: pci read : f2060138
AHCI/0: ... finished, status 0x50, OK
AHCI/0: QEMU HARDDISK ATA-7 Hard-Disk (30720 MiBytes)
Registering bootable: AHCI/0: QEMU HARDDISK ATA-7 Hard-Disk (30720
MiBytes) (type:2 prio:101 data:fd610)
AHCI/1: probing
Full log attached.
[-- Attachment #2: seabios.log --]
[-- Type: text/x-log, Size: 12057 bytes --]
qemu: terminating on signal 2
/0 now 3/0
Start bios (version pre-0.6.3-20110515_192450-zaytsev)
enabling shadow ram
Find memory size
Ram Size=0x08000000 (0x0000000000000000 high)
malloc setup
Relocating init from 0x000e2fc0 to 0x07fe17c0 (size 59160)
init ivt
init bda
init pic
init timer
CPU Mhz=2463
math cp init
init mtrr
pci setup
PCI: pci_bios_init_bus_rec bus = 0x0
PIIX3/PIIX4 init: elcr=00 0c
PCI: bus=0 devfn=0x00: vendor_id=0x8086 device_id=0x1237
PCI: bus=0 devfn=0x08: vendor_id=0x8086 device_id=0x7000
PCI: bus=0 devfn=0x09: vendor_id=0x8086 device_id=0x7010
region 4: 0x0000c000
PCI: bus=0 devfn=0x0b: vendor_id=0x8086 device_id=0x7113
PCI: bus=0 devfn=0x10: vendor_id=0x1013 device_id=0x00b8
region 0: 0xf0000000
region 1: 0xf2000000
region 6: 0xf2010000
PCI: bus=0 devfn=0x18: vendor_id=0x8086 device_id=0x100e
region 0: 0xf2020000
region 1: 0x0000c040
region 6: 0xf2040000
PCI: bus=0 devfn=0x20: vendor_id=0x8086 device_id=0x2922
region 5: 0xf2060000
Found 1 cpu(s) max supported 1 cpu(s)
init bios32
init PMM
init PNPBIOS table
init keyboard
init mouse
init PIR table
init MPTable
MP table addr=0x000fd6e0 MPC table addr=0x000fd6f0 size=232
init SMBIOS tables
SMBIOS ptr=0x000fd6c0 table=0x07fffef0
init ACPI tables
ACPI tables: RSDP=0x000fd690 RSDT=0x07ffd6a0
Scan for VGA option rom
Running option rom at c000:0003
Turning on vga text mode console
init usb
init ps2port
Discarding ps2 data 1f (status=1d)
PS2 keyboard initialized
init lpt
Found 1 lpt ports
init serial
Found 1 serial ports
init floppy drives
init hard drives
ATA controller 0 at 1f0/3f4/c000 (irq 14 dev 9)
ATA controller 1 at 170/374/c008 (irq 15 dev 9)
init ahci
AHCI controller at 04.0, iobase f2060000, irq 11
32: pci read : f2060004
32: pci write: f2060004, 80000000 (0x00006ec4)
32: pci read : f2060000
32: pci read : f206000c
AHCI: cap 0x40141f05, ports_impl 0x3f
AHCI/0: probing
32: pci read : f2060118
32: pci read : f2060130
32: pci write: f2060114, 0 (0x00006e58)
32: pci read : f2060110
32: pci read : f2060120
32: pci read : f2060128
AHCI/0: link up
ebda moved from 9fc00 to 9f800
ebda moved from 9f800 to 9f400
32: pci write: f2060100, 9fc00 (0x00006c2c)
32: pci write: f2060108, 9fb00 (0x00006c2c)
32: pci read : f2060118
32: pci write: f2060118, 16 (0x00006c2c)
32: pci read : f2060118
32: pci write: f2060118, 4017 (0x00006c0c)
32: pci read : f2060138
AHCI/0: send cmd ...
32: pci write: f2060134, 1 (0x00006c04)
32: pci write: f2060138, 1 (0x00006c04)
32: pci read : f2060138
AHCI/0: ... finished, status 0x41, ERROR
32: pci read : f2060118
32: pci write: f2060118, c017 (0x00006c0c)
32: pci read : f2060138
AHCI/0: send cmd ...
32: pci write: f2060134, 1 (0x00006c04)
32: pci write: f2060138, 1 (0x00006c04)
32: pci read : f2060138
AHCI/0: ... finished, status 0x50, OK
AHCI/0: QEMU HARDDISK ATA-7 Hard-Disk (30720 MiBytes)
Registering bootable: AHCI/0: QEMU HARDDISK ATA-7 Hard-Disk (30720 MiBytes) (type:2 prio:101 data:fd610)
AHCI/1: probing
32: pci read : f2060198
32: pci read : f20601b0
32: pci write: f2060194, 0 (0x00006e58)
32: pci read : f2060190
32: pci read : f20601a0
32: pci read : f20601a8
AHCI/1: link down
AHCI/2: probing
32: pci read : f2060218
32: pci read : f2060230
32: pci write: f2060214, 0 (0x00006e58)
32: pci read : f2060210
32: pci read : f2060220
32: pci read : f2060228
AHCI/2: link down
AHCI/3: probing
32: pci read : f2060298
32: pci read : f20602b0
32: pci write: f2060294, 0 (0x00006e58)
32: pci read : f2060290
32: pci read : f20602a0
32: pci read : f20602a8
AHCI/3: link down
AHCI/4: probing
32: pci read : f2060318
32: pci read : f2060330
32: pci write: f2060314, 0 (0x00006e58)
32: pci read : f2060310
32: pci read : f2060320
32: pci read : f2060328
AHCI/4: link down
AHCI/5: probing
32: pci read : f2060398
32: pci read : f20603b0
32: pci write: f2060394, 0 (0x00006e58)
32: pci read : f2060390
32: pci read : f20603a0
32: pci read : f20603a8
AHCI/5: link down
init virtio-blk
Scan for option roms
Running option rom at c900:0003
pmm call arg1=1
pmm01: handle=18ae1000
pmm call arg1=0
pmm00: length=1060 handle=18ae1000 flags=2
pmm call arg1=1
pmm01: handle=18ae2004
pmm call arg1=0
pmm00: length=4000 handle=18ae2004 flags=2
Searching bootorder for: /pci@i0cf8/*@3
Registering bootable: iPXE (PCI 00:03.0) (type:128 prio:9999 data:c9000372)
Mapping hd drive 0x000fd610 to 0
drive 0x000fd610: PCHS=16383/16/63 translation=lba LCHS=1024/255/63 s=62914560
finalize PMM
malloc finalize
Returned 53248 bytes of ZoneHigh
e820 map has 6 items:
0: 0000000000000000 - 000000000009f400 = 1 RAM
1: 000000000009f400 - 00000000000a0000 = 2 RESERVED
2: 00000000000f0000 - 0000000000100000 = 2 RESERVED
3: 0000000000100000 - 0000000007ffd000 = 1 RAM
4: 0000000007ffd000 - 0000000008000000 = 2 RESERVED
5: 00000000fffc0000 - 0000000100000000 = 2 RESERVED
locking shadow ram
Jump to int19
enter handle_19:
NULL
16: pci read : f2060118
32: pci read : f2060118
16: pci write: f2060118, c017 (9f40:0x000002f0)
32: pci write: f2060118, c017 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: send cmd ...
16: pci write: f2060134, 1 (9f40:0x000002f0)
32: pci write: f2060134, 1 (0x0009f6f0)
16: pci write: f2060138, 1 (9f40:0x000002f0)
32: pci write: f2060138, 1 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: ... finished, status 0x50, OK
ahci disk read, lba 0, count 1, buf 0x00007c00, rc 0
Booting from 0000:7c00
16: pci read : f2060118
32: pci read : f2060118
16: pci write: f2060118, c017 (9f40:0x000002f0)
32: pci write: f2060118, c017 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: send cmd ...
16: pci write: f2060134, 1 (9f40:0x000002f0)
32: pci write: f2060134, 1 (0x0009f6f0)
16: pci write: f2060138, 1 (9f40:0x000002f0)
32: pci write: f2060138, 1 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: ... finished, status 0x50, OK
ahci disk read, lba 1, count 1, buf 0x00070000, rc 0
16: pci read : f2060118
32: pci read : f2060118
16: pci write: f2060118, c017 (9f40:0x000002f0)
32: pci write: f2060118, c017 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: send cmd ...
16: pci write: f2060134, 1 (9f40:0x000002f0)
32: pci write: f2060134, 1 (0x0009f6f0)
16: pci write: f2060138, 1 (9f40:0x000002f0)
32: pci write: f2060138, 1 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: ... finished, status 0x50, OK
ahci disk read, lba 2, count 2e, buf 0x00070000, rc 0
enter handle_12:
a=00000000 b=0010a480 c=00000000 d=00000000 ds=0000 es=0000 ss=0000
si=001069f0 di=000168c0 bp=00001ff0 sp=00001ff4 cs=0000 ip=8a9b f=0246
16: pci read : f2060118
32: pci read : f2060118
16: pci write: f2060118, c017 (9f40:0x000002f0)
32: pci write: f2060118, c017 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: send cmd ...
16: pci write: f2060134, 1 (9f40:0x000002f0)
32: pci write: f2060134, 1 (0x0009f6f0)
16: pci write: f2060138, 1 (9f40:0x000002f0)
32: pci write: f2060138, 1 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: ... finished, status 0x50, OK
ahci disk read, lba 0, count 8, buf 0x00068000, rc 0
16: pci read : f2060118
32: pci read : f2060118
16: pci write: f2060118, c017 (9f40:0x000002f0)
32: pci write: f2060118, c017 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: send cmd ...
16: pci write: f2060134, 1 (9f40:0x000002f0)
32: pci write: f2060134, 1 (0x0009f6f0)
16: pci write: f2060138, 1 (9f40:0x000002f0)
32: pci write: f2060138, 1 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: ... finished, status 0x50, OK
ahci disk read, lba 800, count 8, buf 0x00068000, rc 0
16: pci read : f2060118
32: pci read : f2060118
16: pci write: f2060118, c017 (9f40:0x000002f0)
32: pci write: f2060118, c017 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: send cmd ...
16: pci write: f2060134, 1 (9f40:0x000002f0)
32: pci write: f2060134, 1 (0x0009f6f0)
16: pci write: f2060138, 1 (9f40:0x000002f0)
32: pci write: f2060138, 1 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: ... finished, status 0x50, OK
ahci disk read, lba 808, count 8, buf 0x00068000, rc 0
16: pci read : f2060118
32: pci read : f2060118
16: pci write: f2060118, c017 (9f40:0x000002f0)
32: pci write: f2060118, c017 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: send cmd ...
16: pci write: f2060134, 1 (9f40:0x000002f0)
32: pci write: f2060134, 1 (0x0009f6f0)
16: pci write: f2060138, 1 (9f40:0x000002f0)
32: pci write: f2060138, 1 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: ... finished, status 0x50, OK
ahci disk read, lba 2818, count 5, buf 0x00068000, rc 0
16: pci read : f2060118
32: pci read : f2060118
16: pci write: f2060118, c017 (9f40:0x000002f0)
32: pci write: f2060118, c017 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: send cmd ...
16: pci write: f2060134, 1 (9f40:0x000002f0)
32: pci write: f2060134, 1 (0x0009f6f0)
16: pci write: f2060138, 1 (9f40:0x000002f0)
32: pci write: f2060138, 1 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: ... finished, status 0x50, OK
ahci disk read, lba 281d, count 3, buf 0x00068000, rc 0
16: pci read : f2060118
32: pci read : f2060118
16: pci write: f2060118, c017 (9f40:0x000002f0)
32: pci write: f2060118, c017 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: send cmd ...
16: pci write: f2060134, 1 (9f40:0x000002f0)
32: pci write: f2060134, 1 (0x0009f6f0)
16: pci write: f2060138, 1 (9f40:0x000002f0)
32: pci write: f2060138, 1 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: ... finished, status 0x50, OK
ahci disk read, lba 3818, count 4, buf 0x00068000, rc 0
16: pci read : f2060118
32: pci read : f2060118
16: pci write: f2060118, c017 (9f40:0x000002f0)
32: pci write: f2060118, c017 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: send cmd ...
16: pci write: f2060134, 1 (9f40:0x000002f0)
32: pci write: f2060134, 1 (0x0009f6f0)
16: pci write: f2060138, 1 (9f40:0x000002f0)
32: pci write: f2060138, 1 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: ... finished, status 0x50, OK
ahci disk read, lba 381c, count 4, buf 0x00068000, rc 0
16: pci read : f2060118
32: pci read : f2060118
16: pci write: f2060118, c017 (9f40:0x000002f0)
32: pci write: f2060118, c017 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: send cmd ...
16: pci write: f2060134, 1 (9f40:0x000002f0)
32: pci write: f2060134, 1 (0x0009f6f0)
16: pci write: f2060138, 1 (9f40:0x000002f0)
32: pci write: f2060138, 1 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: ... finished, status 0x50, OK
ahci disk read, lba 810, count 8, buf 0x00068000, rc 0
16: pci read : f2060118
32: pci read : f2060118
16: pci write: f2060118, c017 (9f40:0x000002f0)
32: pci write: f2060118, c017 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: send cmd ...
16: pci write: f2060134, 1 (9f40:0x000002f0)
32: pci write: f2060134, 1 (0x0009f6f0)
16: pci write: f2060138, 1 (9f40:0x000002f0)
32: pci write: f2060138, 1 (0x0009f6f0)
16: pci read : f2060138
32: pci read : f2060138
AHCI/0: ... finished, status 0x50, OK
ahci disk read, lba 8c0810, count 8, buf 0x00068000, rc 0
KBD: int09h_handler(): unknown scancode read: 0x5b!
KBD: int09h_handler(): unknown scancode read: 0x5b!
KBD: int09h_handler(): unknown scancode read: 0x5b!
KBD: int09h_handler(): unknown scancode read: 0x5b!
KBD: int09h_handler(): unknown scancode read: 0x5b!
KBD: int09h_handler(): unknown scancode read: 0x5b!
KBD: int09h_handler(): unknown scancode read: 0x5b!
KBD: int09h_handler(): unknown scancode read: 0x5b!
KBD: int09h_handler(): unknown scancode read: 0x5b!
KBD: int09h_handler(): unknown scancode read: 0x5b!
KBD: int09h_handler(): unknown scancode read: 0x5b!
KBD: int09h_handler(): unknown scancode read: 0x5b!
KBD: int09h_handler(): unknown scancode read: 0x5b!
KBD: int09h_handler(): unknown scancode read: 0x5b!
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Qemu-devel] AHCI problems.
2011-05-15 16:41 [Qemu-devel] AHCI problems Alexey Zaytsev
@ 2011-05-17 13:46 ` Alexander Graf
2011-05-17 14:07 ` René Rebe
2011-05-19 20:29 ` Alexey Zaytsev
0 siblings, 2 replies; 11+ messages in thread
From: Alexander Graf @ 2011-05-17 13:46 UTC (permalink / raw)
To: Alexey Zaytsev; +Cc: Kevin Wolf, qemu-devel
On 15.05.2011, at 18:41, Alexey Zaytsev wrote:
> Hi again.
>
> After reverting 667bb59, ahci works fine in Linux, if I boot it with
> -kernel, but grub seems to have some problems.
> Grub2 gets to the rescue prompt. The disk and its partitions seem to
> be detected correctly, but not the filesystem.
> Grub-legacy (from illumos) complains about checksum verification
> failures, supposedly in stage2.
So I just tried again and grub-legacy works just fine for me with an opensuse image, after rebuilding SeaBIOS to enable AHCI. I suppose you're trying this on Ubuntu?
Alex
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Qemu-devel] AHCI problems.
2011-05-17 13:46 ` Alexander Graf
@ 2011-05-17 14:07 ` René Rebe
2011-05-17 14:13 ` Alexander Graf
2011-05-19 20:29 ` Alexey Zaytsev
1 sibling, 1 reply; 11+ messages in thread
From: René Rebe @ 2011-05-17 14:07 UTC (permalink / raw)
To: Alexander Graf; +Cc: Kevin Wolf, Alexey Zaytsev, qemu-devel
Hi,
+
On 17.05.2011, at 15:46, Alexander Graf wrote:
>
> On 15.05.2011, at 18:41, Alexey Zaytsev wrote:
>
>> Hi again.
>>
>> After reverting 667bb59, ahci works fine in Linux, if I boot it with
>> -kernel, but grub seems to have some problems.
>> Grub2 gets to the rescue prompt. The disk and its partitions seem to
>> be detected correctly, but not the filesystem.
>> Grub-legacy (from illumos) complains about checksum verification
>> failures, supposedly in stage2.
>
> So I just tried again and grub-legacy works just fine for me with an opensuse image, after rebuilding SeaBIOS to enable AHCI. I suppose you're trying this on Ubuntu?
This is exactly the phenomena I was seeing the other week when I tested it. From a quick glance it looked like the BIOS returned errors when grub tried to read the FS.
René
--
René Rebe, ExactCODE GmbH, Jaegerstr. 67, DE-10117 Berlin
DE Legal: Amtsgericht Charlottenburg HRB 105123B, Tax-ID#: DE251602478
Managing Directors: Susanne Klaus, René Rebe
http://exactcode.com | http://t2-project.org | http://rene.rebe.de
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Qemu-devel] AHCI problems.
2011-05-17 14:07 ` René Rebe
@ 2011-05-17 14:13 ` Alexander Graf
0 siblings, 0 replies; 11+ messages in thread
From: Alexander Graf @ 2011-05-17 14:13 UTC (permalink / raw)
To: René Rebe; +Cc: Kevin Wolf, Alexey Zaytsev, qemu-devel
On 17.05.2011, at 16:07, René Rebe wrote:
> Hi,
> +
> On 17.05.2011, at 15:46, Alexander Graf wrote:
>
>>
>> On 15.05.2011, at 18:41, Alexey Zaytsev wrote:
>>
>>> Hi again.
>>>
>>> After reverting 667bb59, ahci works fine in Linux, if I boot it with
>>> -kernel, but grub seems to have some problems.
>>> Grub2 gets to the rescue prompt. The disk and its partitions seem to
>>> be detected correctly, but not the filesystem.
>>> Grub-legacy (from illumos) complains about checksum verification
>>> failures, supposedly in stage2.
>>
>> So I just tried again and grub-legacy works just fine for me with an opensuse image, after rebuilding SeaBIOS to enable AHCI. I suppose you're trying this on Ubuntu?
>
> This is exactly the phenomena I was seeing the other week when I tested it. From a quick glance it looked like the BIOS returned errors when grub tried to read the FS.
Hm. Ok, I'll give Ubuntu a spin then.
Alex
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Qemu-devel] AHCI problems.
2011-05-17 13:46 ` Alexander Graf
2011-05-17 14:07 ` René Rebe
@ 2011-05-19 20:29 ` Alexey Zaytsev
2011-05-20 17:27 ` Alexey Zaytsev
1 sibling, 1 reply; 11+ messages in thread
From: Alexey Zaytsev @ 2011-05-19 20:29 UTC (permalink / raw)
To: Alexander Graf; +Cc: Kevin Wolf, qemu-devel
On Tue, May 17, 2011 at 17:46, Alexander Graf <agraf@suse.de> wrote:
>
> On 15.05.2011, at 18:41, Alexey Zaytsev wrote:
>
>> Hi again.
>>
>> After reverting 667bb59, ahci works fine in Linux, if I boot it with
>> -kernel, but grub seems to have some problems.
>> Grub2 gets to the rescue prompt. The disk and its partitions seem to
>> be detected correctly, but not the filesystem.
>> Grub-legacy (from illumos) complains about checksum verification
>> failures, supposedly in stage2.
>
> So I just tried again and grub-legacy works just fine for me with an opensuse image, after rebuilding SeaBIOS to enable AHCI. I suppose you're trying this on Ubuntu?
>
>
Sorry for the delay. I see it's fixed now, so thanks a lot for that!
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Qemu-devel] AHCI problems.
2011-05-19 20:29 ` Alexey Zaytsev
@ 2011-05-20 17:27 ` Alexey Zaytsev
2011-05-21 9:08 ` Alexander Graf
0 siblings, 1 reply; 11+ messages in thread
From: Alexey Zaytsev @ 2011-05-20 17:27 UTC (permalink / raw)
To: Alexander Graf; +Cc: Kevin Wolf, qemu-devel
On Fri, May 20, 2011 at 00:29, Alexey Zaytsev <alexey.zaytsev@gmail.com> wrote:
> On Tue, May 17, 2011 at 17:46, Alexander Graf <agraf@suse.de> wrote:
>>
>> On 15.05.2011, at 18:41, Alexey Zaytsev wrote:
>>
>>> Hi again.
>>>
>>> After reverting 667bb59, ahci works fine in Linux, if I boot it with
>>> -kernel, but grub seems to have some problems.
>>> Grub2 gets to the rescue prompt. The disk and its partitions seem to
>>> be detected correctly, but not the filesystem.
>>> Grub-legacy (from illumos) complains about checksum verification
>>> failures, supposedly in stage2.
>>
>> So I just tried again and grub-legacy works just fine for me with an opensuse image, after rebuilding SeaBIOS to enable AHCI. I suppose you're trying this on Ubuntu?
>>
>>
>
> Sorry for the delay. I see it's fixed now, so thanks a lot for that!
>
Ok, this works for both grub and grub-legacy, and Linux is happy as
well. But illumos won't mount the root fs. From the AHCI debug I see:
ahci: process_ncq_command: [0] NCQ transfer LBA from 0 to -1, drive max 62914559
ahci: process_ncq_command: [0] NCQ reading 0 sectors from LBA 0, tag 0
and this looks a bit suspicious.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Qemu-devel] AHCI problems.
2011-05-20 17:27 ` Alexey Zaytsev
@ 2011-05-21 9:08 ` Alexander Graf
2011-05-21 10:26 ` Alexey Zaytsev
0 siblings, 1 reply; 11+ messages in thread
From: Alexander Graf @ 2011-05-21 9:08 UTC (permalink / raw)
To: Alexey Zaytsev; +Cc: Kevin Wolf, qemu-devel
On 20.05.2011, at 19:27, Alexey Zaytsev wrote:
> On Fri, May 20, 2011 at 00:29, Alexey Zaytsev <alexey.zaytsev@gmail.com> wrote:
>> On Tue, May 17, 2011 at 17:46, Alexander Graf <agraf@suse.de> wrote:
>>>
>>> On 15.05.2011, at 18:41, Alexey Zaytsev wrote:
>>>
>>>> Hi again.
>>>>
>>>> After reverting 667bb59, ahci works fine in Linux, if I boot it with
>>>> -kernel, but grub seems to have some problems.
>>>> Grub2 gets to the rescue prompt. The disk and its partitions seem to
>>>> be detected correctly, but not the filesystem.
>>>> Grub-legacy (from illumos) complains about checksum verification
>>>> failures, supposedly in stage2.
>>>
>>> So I just tried again and grub-legacy works just fine for me with an opensuse image, after rebuilding SeaBIOS to enable AHCI. I suppose you're trying this on Ubuntu?
>>>
>>>
>>
>> Sorry for the delay. I see it's fixed now, so thanks a lot for that!
>>
>
> Ok, this works for both grub and grub-legacy, and Linux is happy as
> well. But illumos won't mount the root fs. From the AHCI debug I see:
>
> ahci: process_ncq_command: [0] NCQ transfer LBA from 0 to -1, drive max 62914559
> ahci: process_ncq_command: [0] NCQ reading 0 sectors from LBA 0, tag 0
>
> and this looks a bit suspicious.
Ok, so I just installed the current OpenIndiana development build (http://dlc.openindiana.org/isos/148/oi-dev-148-text-x86.iso) on AHCI and booted from it. It works just fine for me :).
Alex
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Qemu-devel] AHCI problems.
2011-05-21 9:08 ` Alexander Graf
@ 2011-05-21 10:26 ` Alexey Zaytsev
2011-05-21 11:46 ` Alexey Zaytsev
0 siblings, 1 reply; 11+ messages in thread
From: Alexey Zaytsev @ 2011-05-21 10:26 UTC (permalink / raw)
To: Alexander Graf; +Cc: Kevin Wolf, qemu-devel
> Ok, so I just installed the current OpenIndiana development build (http://dlc.openindiana.org/isos/148/oi-dev-148-text-x86.iso) on AHCI and booted from it. It works just fine for me :).
>
Confirmed, works after a clean install. I'll see if I can get it into
non-working state.
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Qemu-devel] AHCI problems.
2011-05-21 10:26 ` Alexey Zaytsev
@ 2011-05-21 11:46 ` Alexey Zaytsev
2011-05-21 12:00 ` Alexander Graf
0 siblings, 1 reply; 11+ messages in thread
From: Alexey Zaytsev @ 2011-05-21 11:46 UTC (permalink / raw)
To: Alexander Graf; +Cc: Kevin Wolf, qemu-devel
On Sat, May 21, 2011 at 14:26, Alexey Zaytsev <alexey.zaytsev@gmail.com> wrote:
>> Ok, so I just installed the current OpenIndiana development build (http://dlc.openindiana.org/isos/148/oi-dev-148-text-x86.iso) on AHCI and booted from it. It works just fine for me :).
>>
>
> Confirmed, works after a clean install. I'll see if I can get it into
> non-working state.
>
Ok, I guess I got it. There is some incompatibility between ide and
ahci drivers. The first oi instance was installed usigned ide, and
won't work with ahci. The second one was installed on ahci, but won't
work with ide. This is supposed to work, right?
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Qemu-devel] AHCI problems.
2011-05-21 11:46 ` Alexey Zaytsev
@ 2011-05-21 12:00 ` Alexander Graf
2011-05-21 13:56 ` Alexey Zaytsev
0 siblings, 1 reply; 11+ messages in thread
From: Alexander Graf @ 2011-05-21 12:00 UTC (permalink / raw)
To: Alexey Zaytsev; +Cc: Kevin Wolf, qemu-devel
On 21.05.2011, at 13:46, Alexey Zaytsev wrote:
> On Sat, May 21, 2011 at 14:26, Alexey Zaytsev <alexey.zaytsev@gmail.com> wrote:
>>> Ok, so I just installed the current OpenIndiana development build (http://dlc.openindiana.org/isos/148/oi-dev-148-text-x86.iso) on AHCI and booted from it. It works just fine for me :).
>>>
>>
>> Confirmed, works after a clean install. I'll see if I can get it into
>> non-working state.
>>
> Ok, I guess I got it. There is some incompatibility between ide and
> ahci drivers. The first oi instance was installed usigned ide, and
> won't work with ahci. The second one was installed on ahci, but won't
> work with ide. This is supposed to work, right?
I'm not sure what Solaris does here, so I frankly have no idea if this is supposed to work. IDE and AHCI are different interfaces, so there's a good chance it simply doesn't work. How about real hardware? Can you take an openSolaris installation, install it using ICH in IDE mode, switch to AHCI mode and it works?
Alex
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [Qemu-devel] AHCI problems.
2011-05-21 12:00 ` Alexander Graf
@ 2011-05-21 13:56 ` Alexey Zaytsev
0 siblings, 0 replies; 11+ messages in thread
From: Alexey Zaytsev @ 2011-05-21 13:56 UTC (permalink / raw)
To: Alexander Graf; +Cc: Kevin Wolf, qemu-devel
On Sat, May 21, 2011 at 16:00, Alexander Graf <agraf@suse.de> wrote:
>
> On 21.05.2011, at 13:46, Alexey Zaytsev wrote:
>
>> On Sat, May 21, 2011 at 14:26, Alexey Zaytsev <alexey.zaytsev@gmail.com> wrote:
>>>> Ok, so I just installed the current OpenIndiana development build (http://dlc.openindiana.org/isos/148/oi-dev-148-text-x86.iso) on AHCI and booted from it. It works just fine for me :).
>>>>
>>>
>>> Confirmed, works after a clean install. I'll see if I can get it into
>>> non-working state.
>>>
>> Ok, I guess I got it. There is some incompatibility between ide and
>> ahci drivers. The first oi instance was installed usigned ide, and
>> won't work with ahci. The second one was installed on ahci, but won't
>> work with ide. This is supposed to work, right?
>
> I'm not sure what Solaris does here, so I frankly have no idea if this is supposed to work. IDE and AHCI are different interfaces, so there's a good chance it simply doesn't work. How about real hardware? Can you take an openSolaris installation, install it using ICH in IDE mode, switch to AHCI mode and it works?
I'll check this, but may take some time. From my understanding, it
should just work, but I might be wrong.
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2011-05-21 13:56 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-05-15 16:41 [Qemu-devel] AHCI problems Alexey Zaytsev
2011-05-17 13:46 ` Alexander Graf
2011-05-17 14:07 ` René Rebe
2011-05-17 14:13 ` Alexander Graf
2011-05-19 20:29 ` Alexey Zaytsev
2011-05-20 17:27 ` Alexey Zaytsev
2011-05-21 9:08 ` Alexander Graf
2011-05-21 10:26 ` Alexey Zaytsev
2011-05-21 11:46 ` Alexey Zaytsev
2011-05-21 12:00 ` Alexander Graf
2011-05-21 13:56 ` Alexey Zaytsev
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.