| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <20090205082843.GD15052@edu.joroinen.fi> Date: Thu, 5 Feb 2009 10:28:43 +0200 From: Pasi Kärkkäinen <pasik@....fi> To: linux-kernel@...r.kernel.org Cc: linux-ide@...r.kernel.org Subject: Suggestions for debugging ata_piix and ahci driver failures on Xen pv_ops dom0 kernel (2.6.29-rcX) Hello! I'm trying to figure out what's wrong with the pv_ops dom0 kernel/patches [1] causing at least ata_piix and ahci drivers to fail to work. There was legacy IRQ enabling problem earlier with the pv_ops dom0 patches, which pretty much prevented the disks from being detected.. but that got fixed. It could still be something related to Xen/dom0 irq handling.. I'd be glad if someone could take a look at this 2.6.29-rc3-tip pv_ops dom0 kernel boot log and comment about _possible_ causes for such behaviour of ata_piix and ahci: http://pasik.reaktio.net/xen/pv_ops-dom0-debug/pv_ops-dom0-bootlog-11-xen331-linux-2.6.29-rc3-atadebug3.txt In that testing box I have just one IDE hdd attached to ata_piix controller, the AHCI controller doesn't have any disks attached. The exact same kernel works OK without problems on baremetal without Xen hypervisor. [1] http://xenbits.xen.org/paravirt_ops/patches.hg/ and http://wiki.xensource.com/xenwiki/XenParavirtOps -- Pasi -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists