similar to: NLS equation self starting non linear

I thought I'd chime in and say that I'm seeing the same kernel-plus boot failure that Shaun Reitan reported earlier. Is there likely to be another build 3.10 kernel build coming down the pipeline that might fix this issue? Here's the output of my failed PV domU boot: [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000]

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9 On a fresh installation of Debian Jessie, when I try to start a domU, it try to access to a dom0 LVM Volume Group : [...] (I put all the boot at the end) Begin: Loading essential drivers ... done. Begin: Running /scripts/init-premount ... done. Begin: Mounting root file system ... Begin: Running /scripts/local-top ... Begin: Assembling all MD

Hi, I have an Optimus-enabled laptop with a GTX 1060m. I never got it to fully work with Nouveau even after Pascal support was added. I need to run the kernel with nouveau.runpm=0 to get it to work. Unfortunately without proper power mangement support, my laptop will run out of battery after about 1h30, so I'd love to get Optimus working. What I can see is that when the extra GPU is not in

Folk, My network is described and illustrated here. http://carnot.yi.org/NetworksPage.html To allow Cantor and Dalton, in the vpn zone connected to Joule through tun0, to SMTP to my ISP, I tried this in /etc/shorewall/masq. #INTERFACE SOURCE ADDRESS PROTO PORT(S) IPSEC MARK eth0 tun0 Shorewall complains. 07:21:58 Setting up Masquerading/SNAT... 07:21:58 To 0.0.0.0/0

On Wed, 2016-02-03 at 15:28 -0500, Konrad Rzeszutek Wilk wrote: > > > And I wonder if the XEN_DOMCTL_irq_permission aka, > > > xc_domain_irq_permission > > > had been called. I remember that at some point we missed it for > > > Xend.. > > > > > False alarm. > > It was all in Linux. Attached are four patches (the first two > are for

Source: xen Severity: normal Dear Maintainer, After an upgrade, my passthroughed NIC stopped working. I created a new jessie domU and tried to passthrough some PCI devices and found that both USB3 host controller and tg3 NIC generated these lines in domU dmesg: xen:events: Failed to obtain physical IRQ 31 xen:events: Failed to obtain physical IRQ 32 xen:events: Failed to obtain physical IRQ 33

[ 0.000000] microcode: CPU0 microcode updated early to revision 0x1b, date = 2014-05-29 [ 0.000000] Initializing cgroup subsys cpuset [ 0.000000] Initializing cgroup subsys cpu [ 0.000000] Initializing cgroup subsys cpuacct [ 0.000000] Linux version 4.4.0-rc3+ (airlied at crackbookpro) (gcc version 5.1.1 20150618 (Red Hat 5.1.1-4) (GCC) ) #44 SMP Sat Dec 5 16:05:39 AEST 2015 [

Hei, 839ca903f12e (drm/nouveau/kms/nv50: transition to atomic interfaces internally, 2016-11-04) seems to introduce a regression on my machine. Attached dmesg output. Has anyone else seen this on a MacBookPro? Thanks. -- Mit freundlichen Grüßen Alexander Alemayhu -------------- next part -------------- [ 0.000000] microcode: microcode updated early to revision 0x16, date = 2016-04-01 [

Hello, I am encountering a 30 second hang during boot, in the Xorg process just before the display manager comes up. I have bisected the problem to the following commit: commit 2b700825e7a7702fb862edba1262c98040dc1bf6 Author: Ben Skeggs <bskeggs at redhat.com> Date: Thu Aug 20 14:54:22 2015 +1000 drm/nouveau/mc: move device irq handling to platform-specific code The hang only

Xen developers, After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed NIC stopped working. This bug was probably introduced in Debian Jessie sometime between 2015-12-30 and 2016-01-08 as 2015-12-30 as 2015-12-30 was the last time I upgraded without any problems according to my dpkg.log. This bug has also been reported to Debian Bug (https://bugs.debian.org/810379), where I got

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u1 Severity: important I already posted this on the xen-devel-mailinglist but no one seems to have an answer. I'm posting it here because perhaps someone using Debian and Virtualization might have an idea about this? Since Debian 8 I observe that live migrating a PVM on XEN 4.4.1 (also 4.5.1) and Linux Kernel 4.1.0 (also 3.18) requires

On Wed, Jan 27, 2016 at 7:30 PM, Konrad Rzeszutek Wilk < konrad.wilk at oracle.com> wrote: > On Sat, Jan 23, 2016 at 05:12:04PM +0100, Tommi Airikka wrote: > > Xen developers, > > > > After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed > > NIC stopped working. > > This bug was probably introduced in Debian Jessie sometime > > between

Hello, following up on myself, it was suggested on IRC that I better attach a dmesg output. Here's the output of a clean boot & echo 0f > /sys/.../pstate cycle. I can't spot a message that relates to the reclock action, and there's only one weird "nouveau 0000:04:00.0: clk: base: 7 MHz, boost: 7 MHz" message. On the other hand: # cat

> On 23 Dec 2014, at 12:59, Ian Campbell <ijc at debian.org> wrote: > > Control: reassign -1 xen-utils-common 4.4.1-6 > Control: retitle -1 /etc/init.d/xen fails when run in a guest, causing postinst to fail. > > Seems like this issue is in the Xen packages not in the xen-linux-system > metapackage, so reassigning. > > On Mon, 2014-12-22 at 23:01 +0100, Sydney

Does ssh check /etc/default/security file. Is there any patches available to support this. -- Joule __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

Hello Ian, i?ve tried to install "xen-linux-system-amd64" on a VMware host again and everything went fine. The Installation completes and i can boot into Xen und boot up the Dom0. So, you were right. It seems to be a problem with the initscript, but as far as i can tell, only when running xen under xen. To me, this specific issue is resolved, since the meta-package seems to install

Am 25.12.2015 um 18:43 schrieb Pierre Moreau: > Hello, > > Maybe my e-mail client is messing with me, but I couldn't find any dmesg output > attached to your e-mail. Could you please try to attach it again? > > By the way, since you have a Kepler, you should try booting with > "nouveau.War00C800_0=1". That workaround is enabled by default in 4.4-rc5 > (IIRC),

Hi Sydney, Thanks for all the info. I'd like to have the initscript work sensibly in this scenario at some point (not for Jessie though, it's too late now) so I think we may as well keep this bug around to track that since it already contains a bunch of useful information. Thanks, Ian. On Tue, 2014-12-30 at 00:39 +0100, Sydney Meyer wrote: > Hello Ian, > > i?ve tried to

https://bugs.freedesktop.org/show_bug.cgi?id=83271 Priority: medium Bug ID: 83271 Assignee: nouveau at lists.freedesktop.org Summary: Windowed mode causes framebuffer not to refresh with PRIME on optimus/kepler discrete GPU QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified

On Sun, Oct 29, 2017 at 11:51:55PM +0100, Fengguang Wu wrote: >Hi Linus, > >Up to now we see the below boot error/warnings when testing v4.14-rc6. > >They hit the RC release mainly due to various imperfections in 0day's >auto bisection. So I manually list them here and CC the likely easy to >debug ones to the corresponding maintainers in the followup emails. >