I am seeing a kernel message, "hdc: lost interrupt", when running LTP
on
the xen0 domain. The first time I saw the ''kernel: hdc: lost
interrupt''
in /var/log/messages, I was running LTP on both xen0 and xenU domains.
The xenU domain was totally hung at this point. Suspecting a setup
error, I re-checked the installation and reran LTP on xen0 alone,
without having anything running on xenU. Again, I saw the error. To rule
out a hardware problem, I decided to run the same tests on a regular
kernel from kernel.org (2.6.10) and on the RHEL 4 kernel from Red Hat,
both of which ran without showing the error. I don''t know what to make
of it. I am not suspecting a hardware error since the message does not
show up when running on non-xen kernels.
Setup
Platform: RHEL 4 Beta 3
Hw: IBM xSeries 200, with a 866Mhz Pentium III and 512MB RAM,
IDE drive: 00:07.1 IDE interface: VIA Technologies, Inc.
VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
The machine is not the most modern, but it has worked reliably.
Regards,
David Barrera
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/xen-devel
> I am seeing a kernel message, "hdc: lost interrupt", when > running LTP on > the xen0 domain. The first time I saw the ''kernel: hdc: lost > interrupt'' > in /var/log/messages, I was running LTP on both xen0 and xenU > domains.We''ve had one or two reports of interrupt related weirdness. We''re hoping (perhaps optimistically) that these might go away when the IOAPIC configuration code gets moved out of Xen and into domain 0, getting upgraded to 2.6 code in the process. Ian ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
>> I am seeing a kernel message, "hdc: lost interrupt", when >> running LTP on >> the xen0 domain. The first time I saw the ''kernel: hdc: lost >> interrupt'' >> in /var/log/messages, I was running LTP on both xen0 and xenU >> domains. > > We''ve had one or two reports of interrupt related weirdness. We''re > hoping (perhaps optimistically) that these might go away when the IOAPIC > configuration code gets moved out of Xen and into domain 0, getting > upgraded to 2.6 code in the process.I''m not sure if it is xen related or not but when I put following in /etc/exports / 10.0.10.5/24(ro,sync,no_root_squash) and then procedeed to use dom0 as nfs root server, it would hung pretty reliably with "dma timeout" errors, and require power-cycle. the fix was to replace "sync" with "async" as shown below. / 10.0.10.5/24(ro,async,no_root_squash) that was for xen 2.0.1 and 2.6.9 FWIW. ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> I''m not sure if it is xen related or not but when I put following in > /etc/exports > > / 10.0.10.5/24(ro,sync,no_root_squash) > > and then procedeed to use dom0 as nfs root server, it would > hung pretty > reliably with "dma timeout" errors, and require power-cycle. > the fix was > to replace "sync" with "async" as shown below. > > / 10.0.10.5/24(ro,async,no_root_squash) > > that was for xen 2.0.1 and 2.6.9Weird. Could you try just running domain 0, then mounting localhost:/ somewhere. See if exercising the mount causes the same problem. It would then be nice to repeat the experiment with a stock kernel. BTW: exporting / is probably not such a great idea as it will allow other domains to read your ssh host keys... Ian ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
> We''ve had one or two reports of interrupt related weirdness. We''re > hoping (perhaps optimistically) that these might go away when the IOAPIC > configuration code gets moved out of Xen and into domain 0, getting > upgraded to 2.6 code in the process.I''ve started looking at the work involved to move the IOAPIC configuration code to domain 0. Is anyone actively working on this task right now? Any information you can share about the plan of attack? I''d be happy to help with development, testing, etc. Natasha ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel
On Fri, Jan 21, 2005 at 04:08:07PM -0600, David F Barrera wrote:> I am seeing a kernel message, "hdc: lost interrupt", when running LTP on > the xen0 domain. The first time I saw the ''kernel: hdc: lost interrupt'' > in /var/log/messages, I was running LTP on both xen0 and xenU domains. > The xenU domain was totally hung at this point. Suspecting a setup > error, I re-checked the installation and reran LTP on xen0 alone, > without having anything running on xenU. Again, I saw the error. To rule > out a hardware problem, I decided to run the same tests on a regular > kernel from kernel.org (2.6.10) and on the RHEL 4 kernel from Red Hat, > both of which ran without showing the error. I don''t know what to make > of it. I am not suspecting a hardware error since the message does not > show up when running on non-xen kernels.This may be a false lead, but I saw this (and other significant IO-related weirdness) when I moved hardware around and forgot to enable kernel DMA support for the IDE chipset. Overall system performance tanked (obviously), I got a large number of hdX: Lost interrupt warnings, and even some outright panics. Turning on DMA in dom0''s kernel config cleared it all up. Might be worth investigating anyhow, -m ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Xen-devel mailing list Xen-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xen-devel