[Bug 333658] New: lots of "Out of SW-IOMMU space" log messages from SATA disks with XEN
https://bugzilla.novell.com/show_bug.cgi?id=333658#c1 Summary: lots of "Out of SW-IOMMU space" log messages from SATA disks with XEN Product: openSUSE 10.3 Version: Final Platform: x86-64 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Xen AssignedTo: cgriffin@novell.com ReportedBy: tilman@imap.cc QAContact: qa@suse.de Found By: Customer Intel Pentium D940 on Intel DQ965GF board, two SATA hard disks fresh install of openSUSE 10.3 64 bit with all available updates ts@xenon:~> uname -a Linux xenon 2.6.22.9-0.4-xen #1 SMP 2007/10/05 21:32:04 UTC x86_64 x86_64 x86_64 GNU/Linux When booting with XEN, /var/log/messages shows many error messages like the following: Oct 13 13:27:36 xenon kernel: PCI-DMA: Out of SW-IOMMU space for 32768 bytes at device 0000:00:1f.2 Oct 13 13:27:36 xenon kernel: ata2.00: exception Emask 0x0 SAct 0x10 SErr 0x0 action 0x0 Oct 13 13:27:36 xenon kernel: ata2.00: cmd 60/f8:20:87:3c:d6/02:00:02:00:00/40 tag 4 cdb 0x0 data 389120 in Oct 13 13:27:36 xenon kernel: res 40/00:08:e7:30:d6/00:00:02:00:00/40 Emask 0x40 (internal error) followed by what looks like a reset of the affected disk: Oct 13 13:27:36 xenon kernel: ata2.00: configured for UDMA/133 Oct 13 13:27:36 xenon kernel: ata2: EH complete Oct 13 13:27:36 xenon kernel: sd 1:0:0:0: [sdb] 156301488 512-byte hardware sectors (80026 MB) Oct 13 13:27:36 xenon kernel: sd 1:0:0:0: [sdb] Write Protect is off Oct 13 13:27:36 xenon kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00 Oct 13 13:27:36 xenon kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA The frequency of these messages is about 10 per minute after boot but seems to ebb down later. The affected hard disk is mostly sdb (ata2) which hosts the root partition, but occasionally also sda (ata1) where /boot and /home reside. When booting without XEN, no such messages appear. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=333658 Lynn Bendixsen <lbendixs@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |lbendixs@novell.com AssignedTo|cgriffin@novell.com |dpmerrill@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=333658 User dpmerrill@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=333658#c2 Douglas Merrill <dpmerrill@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|dpmerrill@novell.com | --- Comment #2 from Douglas Merrill <dpmerrill@novell.com> 2008-05-01 15:45:17 MST --- It looks like the same error, on a different distribution. It would be helpful to have them try the tip mentioned in comment #11 of bug 381107 and see if that fixes the issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=333658 Douglas Merrill <dpmerrill@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |tilman@imap.cc -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=333658 User poswald@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=333658#c3 --- Comment #3 from Philip Oswald <poswald@novell.com> 2008-05-01 16:05:58 MST --- Tilman, Here is the tip mentioned in bug 381107: Then, using a tip from a test engineer here, I added "dom0_mem=512" to the kernel parameter. This seemed to work as I was able to run i/o to 20 luns without error. ---- This may be a little out of context so if you need more into please do not hesitate to ask. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=333658 User tilman@imap.cc added comment https://bugzilla.novell.com/show_bug.cgi?id=333658#c4 Tilman Schmidt <tilman@imap.cc> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|tilman@imap.cc | --- Comment #4 from Tilman Schmidt <tilman@imap.cc> 2008-05-11 07:02:04 MST --- Adding "dom0_mem=512" to the "Boot Options" line of GRUB (so that it gets appended to the "kernel /xen.gz" line) causes boot failure. The machine briefly displays a message with lots of asterisks and a text along the lines of: "Panic: Dom0 allocation too small for kernel image, rebooting" and then reboots. I found no way of keeping the message on screen long enough to copy the full text. Adding "dom0_mem=512" to the "More Options" line of GRUB (which ends up on the "module /vmlinuz" line, ie. on the Linux kernel parameters) does not have any noticeable effect. Adding "swiotlb=96" to the "More Options" line seems to fix the problem, ie. no "Out of SW-IOMMU space" messages appear in /var/log/messages. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=333658 User lbendixs@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=333658#c5 --- Comment #5 from Lynn Bendixsen <lbendixs@novell.com> 2008-05-12 10:58:41 MST --- I have a few hints which may be helpful here: (In reply to comment #4 from Tilman Schmidt)
Adding "dom0_mem=512" to the "Boot Options" line of GRUB (so that it gets appended to the "kernel /xen.gz" line) causes boot failure.
I think its supposed to be "dom0_mem=512M" (defaults to bytes)
I found no way of keeping the message on screen long enough to copy the full text.
The way to keep the messages on the screen is to put "noreboot" on the "kernel /xen.gz" line
Adding "swiotlb=96" to the "More Options" line seems to fix the problem, ie. no "Out of SW-IOMMU space" messages appear in /var/log/messages.
this workaround fixed your problem then? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=333658 Jason Douglas <jdouglas@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|lbendixs@novell.com |jbeulich@novell.com, | |jdouglas@novell.com QAContact|qa@suse.de |jdouglas@novell.com -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=333658 User jbeulich@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=333658#c6 Jan Beulich <jbeulich@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #6 from Jan Beulich <jbeulich@novell.com> 2009-03-10 02:10:16 MST ---
this workaround fixed your problem then?
Assumed so (given there was no response for over 9 months). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=333658 User tilman@imap.cc added comment https://bugzilla.novell.com/show_bug.cgi?id=333658#c7 --- Comment #7 from Tilman Schmidt <tilman@imap.cc> 2009-03-10 02:24:30 MST --- Sorry, I had thought my last comment was clear enough. Yes, the problem was fixed at the time by the "swiotlb=96" workaround. I cannot contribute more as I've abandoned XEN in the meantime. (For other reasons.) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com