Bug#547495: Debian Lenny 5.0.2 -- XEN Hypervisor 3.2.1 ; linux-image-2.6.26-2-xen-amd64 ; Hang under boot
Ian Campbell skrev: On Sun, 2009-09-20 at 12:51 +0200, Henrik Dige Semark wrote: [7.611998] Fatal DMA error! Please use 'swiotlb=force' [7.612033] [ cut here ] [7.612036] kernel BUG at arch/x86/kernel/pci-nommu-xen.c:70! Did you try this? Note that it should be added to the domU command line. Ian. Yes I have try to add swiotlb=force to my grup menu.lst domU: # cat /boot/grub/menu.lst [ ... ] title Xen 3.2-1-amd64 / Debian GNU/Linux, kernel 2.6.26-2-xen-amd64 root(hd0,1) kernel /xen-3.2-1-amd64.gz iommu=1 swiotlb=force module /vmlinuz-2.6.26-2-xen-amd64 root=/dev/mapper/system-server ro console=tty0 pciback.hide=(03:05.0)(03:06.0)(03:07.0) module /initrd.img-2.6.26-2-xen-amd64 [ ... ] And still no different in the error --- Med Venlig Hilsen / Best regards Henrik Dige Semark
Bug#547495: Debian Lenny 5.0.2 -- XEN Hypervisor 3.2.1 ; linux-image-2.6.26-2-xen-amd64 ; Hang under boot
Ian Campbell skrev: On Thu, 2009-09-24 at 11:06 +0200, Henrik Dige Semark wrote: Ian Campbell skrev: On Sun, 2009-09-20 at 12:51 +0200, Henrik Dige Semark wrote: [7.611998] Fatal DMA error! Please use 'swiotlb=force' [7.612033] [ cut here ] [7.612036] kernel BUG at arch/x86/kernel/pci-nommu-xen.c:70! Did you try this? Note that it should be added to the domU command line. Ian. Yes I have try to add swiotlb=force to my grup menu.lst It should go on the Linux kernel command line, not the hypervisor command line e.g.: domU: # cat /boot/grub/menu.lst [ ... ] title Xen 3.2-1-amd64 / Debian GNU/Linux, kernel 2.6.26-2-xen-amd64 root(hd0,1) kernel /xen-3.2-1-amd64.gz iommu=1 module /vmlinuz-2.6.26-2-xen-amd64 swiotlb=force root=/dev/mapper/system-server ro console=tty0 pciback.hide=(03:05.0)(03:06.0)(03:07.0) module /initrd.img-2.6.26-2-xen-amd64 [ ... ] Those pciback.hide bits are spurious in a domU I should think. If I don't have pciback.hide=(03:05.0)(03:06.0)(03:07.0) in my grub menu.lst on dom0; domU can't use use them. # cat /etc/xen/webserver.cfg [ ... ] vif = [ 'mac=00:16:3E:39:2D:0A' ] pci= [ ':03:05.0', ':03:06.0', ':03:07.0' ] [ ... ] I have tryed to change grub, so on next reboot I will see if che changes have worked :) --- Med Venlig Hilsen / Best regards Henrik Dige Semark smime.p7s Description: S/MIME Cryptographic Signature
Bug#547495: Debian Lenny 5.0.2 -- XEN Hypervisor 3.2.1 ; linux-image-2.6.26-2-xen-amd64 ; Hang under boot
On Thu, 2009-09-24 at 12:35 +0200, Henrik Dige Semark wrote: Ian Campbell skrev: Those pciback.hide bits are spurious in a domU I should think. If I don't have pciback.hide=(03:05.0)(03:06.0)(03:07.0) in my grub menu.lst on dom0; domU can't use use them. But you claimed that this was the _domU_ grub configuration. I think you need to carefully think about where the command lines for each of your dom0 and domUs comes from and ensure that they are configured as appropriate. Ian. -- Ian Campbell Current Noise: Nine Inch Nails - Closer My sister opened a computer store in Hawaii. She sells C shells down by the seashore. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. Sorry, that was a typo, pcibackend.hide is in _dom0_ menu.lst and swiotlb=force is now also set in _dom0_. in the _domU_ config is this [ ... ] vif = [ 'mac=00:16:3E:39:2D:0A' ] pci= [ ':03:05.0', ':03:06.0', ':03:07.0' ] [ ... ] I will return when the server is returned to live after reboot later today. --- Med Venlig Hilsen / Best regards Henrik Dige Semark -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#547495: Debian Lenny 5.0.2 -- XEN Hypervisor 3.2.1 ; linux-image-2.6.26-2-xen-amd64 ; Hang under boot
Ian Campbell skrev: On Thu, 2009-09-24 at 13:57 +0200, Henrik Dige Semark wrote: On Thu, 2009-09-24 at 12:35 +0200, Henrik Dige Semark wrote: Ian Campbell skrev: Those pciback.hide bits are spurious in a domU I should think. If I don't have pciback.hide=(03:05.0)(03:06.0)(03:07.0) in my grub menu.lst on dom0; domU can't use use them. But you claimed that this was the _domU_ grub configuration. I think you need to carefully think about where the command lines for each of your dom0 and domUs comes from and ensure that they are configured as appropriate. Ian. -- Ian Campbell Current Noise: Nine Inch Nails - Closer My sister opened a computer store in Hawaii. She sells C shells down by the seashore. -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. Sorry, that was a typo, pcibackend.hide is in _dom0_ menu.lst and swiotlb=force is now also set in _dom0_. For the nth time: *** swiotlb=force is needed on the _domU_ command line *** That means either you are using pygrub and it should be in menu.lst _inside_the_guest_ or you need to add 'extras=swiotlb=force' to your domU configuration. in the _domU_ config is this [ ... ] vif = [ 'mac=00:16:3E:39:2D:0A' ] pci= [ ':03:05.0', ':03:06.0', ':03:07.0' ] [ ... ] I will return when the server is returned to live after reboot later today. --- Med Venlig Hilsen / Best regards Henrik Dige Semark I have added it as an extra in my webserver.cfg and now it works.! thanx Ian. Case closed. --- Med Venlig Hilsen / Best regards Henrik Dige Semark smime.p7s Description: S/MIME Cryptographic Signature
Bug#547495: Debian Lenny 5.0.2 -- XEN Hypervisor 3.2.1 ; linux-image-2.6.26-2-xen-amd64 ; Hang under boot
Package: linux-image-2.6.26-2-xen-amd64 Version: 2.6.26-19 Severity: critical Justification: breaks the whole system I have an new installed Debian Lenny 5.0.2 (AMD64) install, I use stock debian kernel and Hypervisor; DomO OS: Debian Lenny 5.0.3 Kernel: 2.6.26-2-xen-amd64 Hyper: 3.2.1 PCI-backend: yes Name: master DomU OS: Debian Lenny 5.0.3 Kernel: 2.6.26-2-xen-amd64 Name: webserver The problem is that I wants to pass-throe to NIC's and one ISDN card to DomU. And it works when I passes one NIC and the ISDN card, but when I try to pass the 2x NIC it starts normally, and then suddenly just hang up. With the only message in the console: /sbin/dhclient-script: line 139: 1265 Segmentation fault ifconfig $interface inet 0 up [ 16.013890] eth0: no IPv6 routers present At first the to NIC was from same vendor and batch, so I thought it might had something to do with that, so I changed one of the NIC's to a 3Com 10/100 instead. But it is still same error. LOG with to identical NIC's: # xm start webserver -c [0.680186] Initializing cgroup subsys ns [0.680191] Initializing cgroup subsys cpuacct [0.680194] Initializing cgroup subsys devices [0.680212] CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line) [0.680217] CPU: L2 Cache: 512K (64 bytes/line) [0.680222] CPU: Physical Processor ID: 0 [0.680224] CPU: Processor Core ID: 3 [0.680235] SMP alternatives: switching to UP code [0.685734] Freeing SMP alternatives: 21k freed [0.685825] Brought up 1 CPUs [0.688573] net_namespace: 1224 bytes [0.688698] NET: Registered protocol family 16 [0.689506] Brought up 1 CPUs [0.689519] PCI: Fatal: No config space access function found [0.689524] PCI: setting up Xen PCI frontend stub [0.689925] ACPI: Interpreter disabled. [0.689932] Linux Plug and Play Support v0.97 (c) Adam Belay [0.689953] pnp: PnP ACPI: disabled [0.690126] suspend: event channel 7 [0.690441] xen_mem: Initialising balloon driver. [0.692429] usbcore: registered new interface driver usbfs [0.692474] usbcore: registered new interface driver hub [0.692510] usbcore: registered new device driver usb [0.692628] PCI: System does not support PCI [0.692632] PCI: System does not support PCI [0.692937] pcifront pci-0: Installing PCI frontend [0.693022] pcifront pci-0: Creating PCI Frontend Bus :00 [0.704735] NET: Registered protocol family 2 [0.740470] IP route cache hash table entries: 32768 (order: 6, 262144 bytes) [0.740631] TCP established hash table entries: 131072 (order: 9, 2097152 bytes) [0.741215] TCP bind hash table entries: 65536 (order: 8, 1048576 bytes) [0.741512] TCP: Hash tables configured (established 131072 bind 65536) [0.741517] TCP reno registered [0.752477] NET: Registered protocol family 1 [0.752544] checking if image is initramfs... it is [0.765260] Freeing initrd memory: 22036k freed [0.771426] platform rtc_cmos: registered platform RTC device (no PNP device found) [0.771642] audit: initializing netlink socket (disabled) [0.771654] type=2000 audit(1253380351.924:1): initialized [0.771798] VFS: Disk quotas dquot_6.5.1 [0.771816] Dquot-cache hash table entries: 512 (order 0, 4096 bytes) [0.771831] msgmni has been set to 2091 [0.771889] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 253) [0.771894] io scheduler noop registered [0.771897] io scheduler anticipatory registered [0.771899] io scheduler deadline registered [0.771905] io scheduler cfq registered (default) [0.772773] Linux agpgart interface v0.103 [0.772802] Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled [0.773598] brd: module loaded [0.773643] input: Macintosh mouse button emulation as /class/input/input0 [0.773687] Xen virtual console successfully installed as hvc0 [0.773717] Event-channel device installed. [0.779980] netfront: Initialising virtual ethernet driver. [0.783113] PNP: No PS/2 controller found. Probing ports directly. [0.783929] i8042.c: No controller found. [0.784464] xen-vbd: registered block device major 202 [0.784475] blkfront: xvda1: barriers enabled [0.788666] blkfront: xvda2: barriers enabled [0.792074] mice: PS/2 mouse device common for all mice [0.792146] rtc_cmos rtc_cmos: rtc core: registered rtc_cmos as rtc0 [0.792217] No iBFT detected. [0.792475] TCP cubic registered [0.792479] NET: Registered protocol family 17 [0.792533] registered taskstats version 1 [0.792561] XENBUS: Device with no driver: device/console/0 [0.792564] drivers/rtc/hctosys.c: unable to open rtc device (rtc0) [0.792571] Freeing unused kernel memory: 216k freed Loading, please wait... Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... FATAL: Error inserting fan
Bug#515255: linux-image-2.6.18-6-xen-vserver-686: No grub entry's after install of kernel, and when I add it by hand the kernel can't start
I have found the answer :) You just have to download and install xen-linux-system-2.6.18-6-xen-vserver-686 or (amd64) This have to be an dependent, cause, the kernel is not usable if that module is not pressent ? Sorry for my bad english --- Med Venlig Hilsen / Bedst Regards Henrik Dige Semark -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#515255: linux-image-2.6.18-6-xen-vserver-686: No grub entry's after install of kernel, and when I add it by hand the kernel can't start
Package: linux-image-2.6.18-6-xen-vserver-686 Version: 2.6.18.dfsg.1-24 Severity: important This is a very big problem for my anyway, I have to use both Xen and Vserver, and the kernel can provide my both, but when I install it, (both amd64 and 686 kernel) it says “Changing /boot/grub/menu.lst” but there is nothing changed in menu.lst so I can't start the kernel, then I entered it by hand (see my menu.lst below) and rebooted and tried to start the new kernel, but then it boots and stops with “waiting for root filesystem... ...” and then never continues *** My menu.lst *** ## ## End Default Options ## title Debian GNU/Linux, kernel 2.6.18-6-686 root(hd2,0) kernel /boot/vmlinuz-2.6.18-6-686 root=/dev/md1 ro initrd /boot/initrd.img-2.6.18-6-686 savedefault title Debian GNU/Linux, kernel 2.6.18-6-xen-vserver-686 root(hd2,0) kernel /boot/vmlinuz-2.6.18-6-xen-vserver-686 root=/dev/md1 ro initrd /boot/initrd.img-2.6.18-6-xen-vserver-686 savedefault title Debian GNU/Linux, kernel 2.6.18-6-vserver-686 root(hd2,0) kernel /boot/vmlinuz-2.6.18-6-vserver-686 root=/dev/md1 ro initrd /boot/initrd.img-2.6.18-6-vserver-686 savedefault *** ls -a of /boot *** config-2.6.18-6-486 config-2.6.18-6-686 config-2.6.18-6-vserver-686 config-2.6.18-6-xen-vserver-686 grub initrd.img-2.6.18-6-486 initrd.img-2.6.18-6-486.bak initrd.img-2.6.18-6-686 initrd.img-2.6.18-6-vserver-686 initrd.img-2.6.18-6-xen-vserver-686 initrd.img-2.6.18-6-xen-vserver-686.bak System.map-2.6.18-6-486 System.map-2.6.18-6-686 System.map-2.6.18-6-vserver-686 System.map-2.6.18-6-xen-vserver-686 vmlinuz-2.6.18-6-486 vmlinuz-2.6.18-6-686 vmlinuz-2.6.18-6-vserver-686 vmlinuz-2.6.18-6-xen-vserver-686 -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-686 Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8) Versions of packages linux-image-2.6.18-6-xen-vserver-686 depends on: ii initramfs-tools 0.85itools for generating an initramfs ii linux-modules-2.6.18-6- 2.6.18.dfsg.1-24 Linux 2.6.18 modules on i686 Versions of packages linux-image-2.6.18-6-xen-vserver-686 recommends: pn libc6-xen none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#501556: ipp2p module is missing
Package: iptables Version: 1.3.6.0debian1-5 Severity: important As issuing iptables to call ipp2p shows can not open libipt_ipp2p.so. This is the capture. iptables -m ipp2p --help iptables v1.3.6: Couldn't load match `ipp2p':/lib/iptables/libipt_ipp2p.so: cannot open shared object file: No such file or directory Try `iptables -h' or 'iptables --help' for more information. I checked that /lib/iptables/libipt_ipp2p.so really does not exist. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-486 Locale: LANG=da_DK.UTF-8, LC_CTYPE=da_DK.UTF-8 (charmap=UTF-8) Versions of packages iptables depends on: ii libc6 2.3.6.ds1-13etch7 GNU C Library: Shared libraries ii libselinux11.32-3SELinux shared libraries iptables recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
