Bug#695658: BUG: unable to handle kernel paging request at ffff8803c1bcb000
Same thing for me on a Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz on a P8H77-M PRO. I triggered this one in ssh in the dom0. [30713.352192] BUG: unable to handle kernel paging request at 8803c1bcb000 [30713.352251] IP: [81015d7f] __sanitize_i387_state+0x24/0xe1 [30713.352297] PGD 1606067 PUD ccac6067 PMD ccad4067 PTE 0 [30713.352375] Oops: [#4] SMP [30713.352426] CPU 0 [30713.352440] Modules linked in: microcode xt_tcpudp xt_state xt_physdev iptable_filter xen_netback xen_blkback xen_evtchn xenfs bridge stp dummy ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables sit tunnel4 ext3 jbd evdev snd_pcm snd_timer i2c_i801 video snd soundcore snd_page_alloc thermal_sys coretemp i2c_core pcspkr serio_raw ext4 mbcache jbd2 crc16 sha256_generic dm_crypt dm_mod raid1 md_mod sd_mod crc_t10dif crc32c_intel ghash_clmulni_intel ahci aesni_intel cryptd libahci aes_x86_64 ehci_hcd aes_generic libata scsi_mod r8169 mii usbcore usb_common [last unloaded: scsi_wait_scan] [30713.353420] [30713.353445] Pid: 8655, comm: bash Tainted: G D 3.2.0-0.bpo.4-amd64 #1 Debian 3.2.35-2~bpo60+1 System manufacturer System Product Name/P8H77-M PRO [30713.353531] RIP: e030:[81015d7f] [81015d7f] __sanitize_i387_state+0x24/0xe1 [30713.353587] RSP: e02b:8802f5de9e10 EFLAGS: 00010246 [30713.353617] RAX: RBX: 7fff9573b6c0 RCX: 0200 [30713.353648] RDX: 8803c1bcae00 RSI: 8802f5de9fd8 RDI: 8803c1ba4fa0 [30713.353680] RBP: 8803c1ba4fa0 R08: 7fff9573b820 R09: 0101010101010101 [30713.353711] R10: 0008 R11: 00445000 R12: [30713.353742] R13: 7fff9573b4f8 R14: 8803c1ba4fa0 R15: 7fff9573b6c0 [30713.353776] FS: 7fe8988a2700() GS:8803d6e0() knlGS: [30713.353818] CS: e033 DS: ES: CR0: 8005003b [30713.353847] CR2: 8803c1bcb000 CR3: 0002f5de2000 CR4: 2660 [30713.353878] DR0: DR1: DR2: [30713.353910] DR3: DR6: 0ff0 DR7: 0400 [30713.353941] Process bash (pid: 8655, threadinfo 8802f5de8000, task 8803c1ba4fa0) [30713.353984] Stack: [30713.354008] 81015f54 8802f5de9f58 0011 8803c1ba5440 [30713.354098] 8100e132 8803c1ba4fa0 8136b20e 0011 [30713.354189] 00040001 21d1 8803 [30713.354279] Call Trace: [30713.354306] [81015f54] ? save_i387_xstate+0x118/0x1e2 [30713.354337] [8100e132] ? do_signal+0x21f/0x635 [30713.354368] [8136b20e] ? do_page_fault+0x311/0x34c [30713.354398] [81368002] ? _raw_spin_lock_irq+0x7/0x22 [30713.354429] [8100e56d] ? do_notify_resume+0x25/0x67 [30713.354460] [810588ca] ? sys_rt_sigprocmask+0x5a/0x96 [30713.354491] [8136d920] ? int_signal+0x12/0x17 [30713.354520] Code: c1 ea 20 0f 01 d1 c3 48 8b 97 58 04 00 00 48 85 d2 0f 84 d0 00 00 00 83 bf 50 04 00 00 00 74 04 0f 0b eb fe 48 8b 05 b1 a7 72 00 48 8b b2 00 02 00 00 48 89 c1 48 21 f1 48 39 c1 0f 84 a6 00 00 [30713.355368] RIP [81015d7f] __sanitize_i387_state+0x24/0xe1 [30713.355411] RSP 8802f5de9e10 [30713.355438] CR2: 8803c1bcb000 [30713.355465] ---[ end trace 7caac314f2a1b625 ]--- Regards, D. -- Dmitry Nedospasov dmi...@nedos.net -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632185: igb: missing support for Intel 82576 ET2 Quad Port (8086:a06c)
Any news on this? I would love to help test if that will help. We just got a couple of these cards. D. -- Dmitry Nedospasov dmi...@nedos.net -- Twitter: @nedos Web: http://nedos.net -- Github: http://github.com/nedos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#632185: igb: missing support for Intel 82576 ET2 Quad Port (8086:a06c)
On Sat, Sep 03, 2011 at 04:55:39PM +0200, Julien Cristau wrote: http://people.debian.org/~benh/packages/ has candidate packages. Is there any way to confirm that these packages include the igb module with ET2 support (other than installing it)? Thanks, Dmitry -- Dmitry Nedospasov dmi...@nedos.net -- Twitter: @nedos Web: http://nedos.net -- Github: http://github.com/nedos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#484652: Fixed in upstream!
Hey Teodor, 2 years and several developers later, this got fixed upstream [1] :) The error was actually a mistake in an if statement which checked for both a root device and swap. I guess this shows the both of us, how few people run swapless ;) In any case, thanks for the bugreport! All the best, Dmitry [1] http://gitorious.org/xen-tools/xen-tools/commit/1e8b4d -- Dmitry Nedospasov dmi...@nedos.net -- Twitter: @nedos Web: http://nedos.net -- Github: http://github.com/nedos -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588811: upgraded to 4.0.1~rc5-1 - same problem
Today i Upgraded to 4.0.1~rc5-1, this overwrote my local changes to /lib/xen-default/bin/pygrub, and pygrub began to silently fail again. Can we please just apply my patch. This simply moves the line calling xenlovel to the line after which the path can be correctly resolved. As of now, pygrub simply fails silently, which is very, very, very confusing, and apparently I get to encounter this on every upgrade :) Regards, Dmitry -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588784: xen-tools: Using the same initrd as dom0 makes domU unbootable.
Hello, On Mon, Jul 12, 2010 at 11:27:42AM +0200, Witold Baryluk wrote: I have dom0 with encrypted partition and LVM on it, etc. It used UUIDs everwhere to reference disk, partitions, encrypted volumins, VG, LV, etc. UUID of partition which contains encrypted partition is embeded directly into initrd by update-initramfs. (kernel's root=UUID=xxx referenced decrypted volume). As xen-tools by default use the same initramfs, and same scripts, all I see on console is this: The preffered sollution for such cases currently is NOT to use the dom0's kernel or initrd and use pygrub instead. Pvgrub is on the TODO list, but AFAIK isn't working currently. You can simply specify the --pygrub flag when installing, and you should be good to go. This will install a kernel and initrd to the guest which pygrub (part of xen-utils) will then boot when you do an xm create. Hope that cleared things up, I don't really see this as a bug though. Regards, Dmitry -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588811: pygrub fails to import xen.lowlevel.xc
Package: xen-utils-4.0 Version: 4.0.1~rc3-1 Severity: important When invoking pygrub either via command line or via bootloader being set in the configuration file, pygrub fails because it cannot import xen.lowlevel.xc. Example output: # /usr/lib/xen-default/bin/pygrub Traceback (most recent call last): File /usr/lib/xen-default/bin/pygrub, line 20, in module import xen.lowlevel.xc ImportError: No module named xen.lowlevel.xc -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xen-utils-4.0 depends on: ii e2fslibs1.41.12-2ext2/ext3/ext4 file system librari ii iproute 20100519-2 networking and traffic control too ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libncurses5 5.7+20100313-2 shared libraries for terminal hand ii libxenstore3.0 4.0.1~rc3-1 Xenstore communications library fo ii python-support 1.0.9automated rebuilding support for P ii python2.5 2.5.5-6 An interactive high-level object-o ii udev158-1/dev/ and hotplug management daemo ii xen-utils-common4.0.0-1 XEN administrative tools - common ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages xen-utils-4.0 recommends: ii bridge-utils 1.4-5 Utilities for configuring the Linu ii xen-hypervisor-4.0-amd64 [xe 4.0.1~rc3-1 The Xen Hypervisor on AMD64 Versions of packages xen-utils-4.0 suggests: pn xen-docs-4.0 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#588811: [Patch] Import xen.lowlevel.xc later in pygrub
This is a relatively simple fix i found, I don't know if it need to be reported to upstream. Since the script resolves additional dependencies anyway by appending the path, we simply move the import xen.lowlevel.xc line to below the line that appends path. Worked like a charm for me. Rergards, Dmitry diff --git a/tools/pygrub/src/pygrub b/tools/pygrub/src/pygrub index d0d8844..f8d8f37 100644 --- a/tools/pygrub/src/pygrub +++ b/tools/pygrub/src/pygrub @@ -17,13 +17,13 @@ import os, sys, string, struct, tempfile, re import copy import logging import platform -import xen.lowlevel.xc import curses, _curses, curses.wrapper, curses.textpad, curses.ascii import getopt sys.path.insert(1, sys.path[0] + '/../lib/python') +import xen.lowlevel.xc import fsimage import grub.GrubConf import grub.LiloConf
Bug#588811: [Pkg-xen-devel] Bug#588811: [Patch] Import xen.lowlevel.xc later in pygrub
Hello Bastian, On Mon, Jul 12, 2010 at 07:18:28PM +0200, Bastian Blank wrote: I would believe that the correct fix is to remove the usage of the lowlevel interface. I think i agree. I just took a glance over the code, and also fired up a python shell to see what the code is actually used for. From what i can tell xen.lowlevel.xc allows the script to find out the capabilities of the enviorment, in the script it is *only* called when checking if the dom0 supports running 64-bit pvguests, i.e. the supports64bitPVguest() function. Anyway it doesn't seem like a piece of code that is necessary for most users. In fact, deleting this import line worked just as well. The only thing that bothers me is that it is called used in the bit of code labeled: If nothing has been specified, look for a Solaris domU I don't have (nor do i want) any solaris domU's to test this code with. However i can say that both this import line, as well as the supports64bitPVguest function and the subsequent calls to it are absent in the Xen installation i have on one of my CentOS machines (xen 3.4.2). The version listed at the top of the script in that installation is also 0.6. Anyway I think it'd be best to prepare a patch to delete this cruft in the Debian package. It's a shame that it breaks pygrub right now. Regards, Dmitry -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#588839: Include pv-grub to securely boot guest kernels
Package: xen-utils-4.0 Version: 4.0.1~rc3-1 Severity: wishlist Please include pv-grub images in xen-utils or as a seperate package. Pv-grub allows securely booting guest kernels. [0] http://wiki.xensource.com/xenwiki/PvGrub -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xen-utils-4.0 depends on: ii e2fslibs1.41.12-2ext2/ext3/ext4 file system librari ii iproute 20100519-2 networking and traffic control too ii libc6 2.11.2-2 Embedded GNU C Library: Shared lib ii libncurses5 5.7+20100313-2 shared libraries for terminal hand ii libxenstore3.0 4.0.1~rc3-1 Xenstore communications library fo ii python-support 1.0.9automated rebuilding support for P ii python2.5 2.5.5-6 An interactive high-level object-o ii udev158-1/dev/ and hotplug management daemo ii xen-utils-common4.0.0-1 XEN administrative tools - common ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime Versions of packages xen-utils-4.0 recommends: ii bridge-utils 1.4-5 Utilities for configuring the Linu ii xen-hypervisor-4.0-amd64 [xe 4.0.1~rc3-1 The Xen Hypervisor on AMD64 Versions of packages xen-utils-4.0 suggests: pn xen-docs-4.0 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#492583: xen-tools: hostname -f no longer returns the full hostname
Hello Martin, On 6/23/10 4:26 AM, Martin Goldman wrote: It appears that, possibly as a result of this change, hostname -f no longer returns the machine's FQDN; instead, it just returns the machine's short name (the one that's displayed if you simply type hostname). This is a problem for applications that need your FQDN. One way of fixing this is by writing something like this to /etc/hosts: a.b.c.d myhost.mydomain.com myhost instead of writing 2 separate lines for myhost.mydomain.com and myhost as xen-tools is currently doing. I just fixed this in our upstream [1]. Thanks for bringing this to our attention. Hopefully Axel packages this pretty quickly :D Regards, Dmitry [1] http://gitorious.org/xen-tools/xen-tools/commit/8834e669dd00b5569fac107ec00481a1582396be -- Dmitry Nedospasov dmi...@nedos.net - http://nedos.net GPG: 0x5EED4EED - Twitter: @nedos signature.asc Description: OpenPGP digital signature
