Your message dated Wed, 12 Aug 2015 15:17:08 +0200 with message-id <1439385428.10857.70.camel@decadent.org.uk> and subject line Re: xen-linux-system-3.2.0-4-amd64: xen kernel appears misconfigured for uvesafb has caused the Debian Bug report #761469, regarding xen-linux-system-3.2.0-4-amd64: xen kernel appears misconfigured for uvesafb to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 761469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761469 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: xen-linux-system-3.2.0-4-amd64: xen kernel appears misconfigured for uvesafb
- From: Dylan Cali <calid1984@gmail.com>
- Date: Sun, 14 Sep 2014 00:16:34 -0500
- Message-id: <20140914051634.4647.41271.reportbug@xen-host>
Package: xen-linux-system-3.2.0-4-amd64 Version: 3.2.60-1+deb7u3 Severity: important Dear Maintainer, Original symptom: under x11 switching tty's causes blank screen and monitor going to sleep. Researching indicated this could be related to having a Nvidia graphics card as well as a missing or misconfigured uvesafb module. [1] Checking dmesg showed the following error: [ 4.796570] uvesafb: Getting VBE info block failed (eax=0x4f00, err=0) [ 4.796635] uvesafb: vbe_init() failed with -22 [ 4.796688] uvesafb: probe of uvesafb.0 failed with error -22 Also /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes did not exist. When booting with the standard Debian linux kernel instead of xen tty switching under x11 worked as expected. There were no errors in demsg output: [ 3.275811] uvesafb: NVIDIA Corporation, GF110 Board - 12610002, Chip Rev , OEM: NVIDIA, VBE v3.0 [ 3.385649] uvesafb: VBIOS/hardware doesn't support DDC transfers [ 3.385651] uvesafb: no monitor limits have been set, default refresh rate will be used [ 3.386354] uvesafb: scrolling: redraw [ 3.563068] uvesafb: framebuffer at 0xf1000000, mapped to 0xffffc90006680000, using 14336k, total 14336k Also /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes existed with expected content. This seems to indicate the Debian xen kernel has not been correctly configured for use with the uvesafb module. [1] https://bbs.archlinux.org/viewtopic.php?id=120326 -- System Information: Debian Release: 7.6 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/8 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-linux-system-3.2.0-4-amd64 depends on: ii linux-image-3.2.0-4-amd64 3.2.60-1+deb7u3 ii xen-system-amd64 4.1.4-3+deb7u2 xen-linux-system-3.2.0-4-amd64 recommends no packages. xen-linux-system-3.2.0-4-amd64 suggests no packages. -- no debconf information
--- End Message ---
--- Begin Message ---
- To: 761469-done@bugs.debian.org
- Subject: Re: xen-linux-system-3.2.0-4-amd64: xen kernel appears misconfigured for uvesafb
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Wed, 12 Aug 2015 15:17:08 +0200
- Message-id: <1439385428.10857.70.camel@decadent.org.uk>
- In-reply-to: <20140914051634.4647.41271.reportbug@xen-host>
- References: <20140914051634.4647.41271.reportbug@xen-host>
This is not a configuration issue. uvesafb requires making BIOS calls, but Xen PV domains do not have access to the BIOS. Ben. -- Ben Hutchings Teamwork is essential - it allows you to blame someone else.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---