from:"Mark W Wenning"

[Bug 1680553] Re: cpufreqd/loadcpufreq fails in trusty

2017-04-06 Thread Mark W Wenning

Customer posted their debug output: 
We get an error during:
 
root@plxtil03:~# /etc/init.d/loadcpufreq start
* Loading cpufreq kernel modules... 
 [fail]
 
 
Here’s debug output when starting loadcpufreq:
 
root@plxtil03:~# /etc/init.d/loadcpufreq start
+ PATH=/sbin:/bin:/usr/sbin:/usr/bin
+ NAME=loadcpufreq
+ . /lib/lsb/init-functions
+ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
+ [ -r /lib/lsb/init-functions.d/01-upstart-lsb ]
+ . /lib/lsb/init-functions.d/01-upstart-lsb
+ unset UPSTART_SESSION
+ _RC_SCRIPT=/etc/init.d/loadcpufreq
+ [ -r /etc/init//etc/init.d/loadcpufreq.conf ]
+ _UPSTART_JOB=loadcpufreq
+ [ -r /etc/init/loadcpufreq.conf ]
+ [ -r /lib/lsb/init-functions.d/20-left-info-blocks ]
+ . /lib/lsb/init-functions.d/20-left-info-blocks
+ [ -r /lib/lsb/init-functions.d/50-ubuntu-logging ]
+ . /lib/lsb/init-functions.d/50-ubuntu-logging
+ LOG_DAEMON_MSG=
+ FANCYTTY=
+ [ -e /etc/lsb-base-logging.sh ]
+ true
+ [ -f /etc/default/rcS ]
+ . /etc/default/rcS
+ UTC=yes
+ ENABLE=true
+ [ -f /etc/default/loadcpufreq ]
+ set -e
+ [ true = true ]
+ MODPROBE=modprobe -b
+ log_action_begin_msg Loading cpufreq kernel modules
+ log_daemon_msg Loading cpufreq kernel modules...
+ [ -z Loading cpufreq kernel modules... ]
+ log_use_fancy_output
+ TPUT=/usr/bin/tput
+ EXPR=/usr/bin/expr
+ [ -t 1 ]
+ [ xxterm-256color != x ]
+ [ xxterm-256color != xdumb ]
+ [ -x /usr/bin/tput ]
+ [ -x /usr/bin/expr ]
+ /usr/bin/tput hpa 60
+ /usr/bin/tput setaf 1
+ [ -z ]
+ FANCYTTY=1
+ true
+ /usr/bin/tput xenl
+ /usr/bin/tput cols
+ COLS=158
+ [ 158 ]
+ [ 158 -gt 6 ]
+ /usr/bin/expr 158 - 7
+ COL=151
+ log_use_plymouth
+ [ n = y ]
+ plymouth --ping
+ printf  * Loading cpufreq kernel modules...  
 * Loading cpufreq kernel modules...   + /usr/bin/expr 158 - 1
+ /usr/bin/tput hpa 157

 + 
printf 
 + [ -f /proc/modules ]
+ load_modules
+ /sbin/lsmod
+ awk !/Module/ {print $1}
+ LIST=autofs4
dcdbas
x86_pkg_temp_thermal
coretemp
kvm_intel
kvm
crct10dif_pclmul
crc32_pclmul
aesni_intel
aes_x86_64
lrw
gf128mul
glue_helper
ablk_helper
cryptd
dm_multipath
scsi_dh
joydev
shpchp
ipmi_si
acpi_power_meter
mac_hid
lp
parport
nfsd
auth_rpcgss
nfs_acl
nfs
lockd
sunrpc
fscache
hid_generic
usbhid
hid
i40e
igb
i2c_algo_bit
vxlan
dca
ip_tunnel
ptp
ahci
megaraid_sas
pps_core
libahci
+ uname -r
+ LOC=/lib/modules/3.13.0-100-generic/kernel/drivers/cpufreq
+ [ -d /lib/modules/3.13.0-100-generic/kernel/drivers/cpufreq ]
+ + find /lib/modules/3.13.0-100-generic/kernel/drivers/cpufreq -type f -name 
cpufreq_*.o -printf basename %f .o\n
/bin/sh
+ find /lib/modules/3.13.0-100-generic/kernel/drivers/cpufreq -type f -name 
cpufreq_*.ko -printf basename %f .ko\n
+ MODAVAIL=
+ uname -m
+ [ x86_64 = ppc ]
+ [ !  =  ]
+ load_detected_cpufreq_modules
+ CPUINFO=/proc/cpuinfo
+ IOPORTS=/proc/ioports
+ [ ! -f /proc/cpuinfo ]
+ grep ^model name /proc/cpuinfo
+ head -1
+ sed -e s/^.*: //;
+ MODEL_NAME=Intel(R) Xeon(R) Gold 6152 CPU @ 2.10GHz
+ grep+  -E ^model[[:space:]]+: /proc/cpuinfo
head -1
+ sed -e s/^.*: //;
+ MODEL_ID=85
+ grep -E ^cpud[^:]+: /proc/cpuinfo
+ head -1
+ sed -e s/^.*: //;
+ CPU=
+ + grep -E ^vendor_id[^:]+: /proc/cpuinfo
head -1
+ sed -e s/^.*: //;
+ VENDOR_ID=GenuineIntel
+ sed -e /^cpu family/ {s/.*: //;p;Q};d /proc/cpuinfo
+ CPU_FAMILY=6
+ MODULE=
+ MODULE_FALLBACK=acpi-cpufreq
+ [ -f /proc/ioports ]
+ grep -q Intel .*ICH /proc/ioports
+ PIII_MODULE=speedstep-smi
+ grep est /proc/cpuinfo
+ [ flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat 
epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase 
tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm avx512f rdseed adx smap 
avx512cd
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr 
pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall 
nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat 
epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase 
tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm avx512f rdseed adx smap 
avx512cd
flags   : fpu vme de pse tsc

[Bug 1680553] Re: cpufreqd/loadcpufreq fails in trusty

2017-04-06 Thread Mark W Wenning

AT customer posted their debug output: 
We get an error during:
 
root@plxtil03:~# /etc/init.d/loadcpufreq start
* Loading cpufreq kernel modules... 
 [fail]
 
 
Here’s debug output when starting loadcpufreq:
 
root@plxtil03:~# /etc/init.d/loadcpufreq start
+ PATH=/sbin:/bin:/usr/sbin:/usr/bin
+ NAME=loadcpufreq
+ . /lib/lsb/init-functions
+ run-parts --lsbsysinit --list /lib/lsb/init-functions.d
+ [ -r /lib/lsb/init-functions.d/01-upstart-lsb ]
+ . /lib/lsb/init-functions.d/01-upstart-lsb
+ unset UPSTART_SESSION
+ _RC_SCRIPT=/etc/init.d/loadcpufreq
+ [ -r /etc/init//etc/init.d/loadcpufreq.conf ]
+ _UPSTART_JOB=loadcpufreq
+ [ -r /etc/init/loadcpufreq.conf ]
+ [ -r /lib/lsb/init-functions.d/20-left-info-blocks ]
+ . /lib/lsb/init-functions.d/20-left-info-blocks
+ [ -r /lib/lsb/init-functions.d/50-ubuntu-logging ]
+ . /lib/lsb/init-functions.d/50-ubuntu-logging
+ LOG_DAEMON_MSG=
+ FANCYTTY=
+ [ -e /etc/lsb-base-logging.sh ]
+ true
+ [ -f /etc/default/rcS ]
+ . /etc/default/rcS
+ UTC=yes
+ ENABLE=true
+ [ -f /etc/default/loadcpufreq ]
+ set -e
+ [ true = true ]
+ MODPROBE=modprobe -b
+ log_action_begin_msg Loading cpufreq kernel modules
+ log_daemon_msg Loading cpufreq kernel modules...
+ [ -z Loading cpufreq kernel modules... ]
+ log_use_fancy_output
+ TPUT=/usr/bin/tput
+ EXPR=/usr/bin/expr
+ [ -t 1 ]
+ [ xxterm-256color != x ]
+ [ xxterm-256color != xdumb ]
+ [ -x /usr/bin/tput ]
+ [ -x /usr/bin/expr ]
+ /usr/bin/tput hpa 60
+ /usr/bin/tput setaf 1
+ [ -z ]
+ FANCYTTY=1
+ true
+ /usr/bin/tput xenl
+ /usr/bin/tput cols
+ COLS=158
+ [ 158 ]
+ [ 158 -gt 6 ]
+ /usr/bin/expr 158 - 7
+ COL=151
+ log_use_plymouth
+ [ n = y ]
+ plymouth --ping
+ printf  * Loading cpufreq kernel modules...  
 * Loading cpufreq kernel modules...   + /usr/bin/expr 158 - 1
+ /usr/bin/tput hpa 157

 + 
printf 
 + [ -f /proc/modules ]
+ load_modules
+ /sbin/lsmod
+ awk !/Module/ {print $1}
+ LIST=autofs4
dcdbas
x86_pkg_temp_thermal
coretemp
kvm_intel
kvm
crct10dif_pclmul
crc32_pclmul
aesni_intel
aes_x86_64
lrw
gf128mul
glue_helper
ablk_helper
cryptd
dm_multipath
scsi_dh
joydev
shpchp
ipmi_si
acpi_power_meter
mac_hid
lp
parport
nfsd
auth_rpcgss
nfs_acl
nfs
lockd
sunrpc
fscache
hid_generic
usbhid
hid
i40e
igb
i2c_algo_bit
vxlan
dca
ip_tunnel
ptp
ahci
megaraid_sas
pps_core
libahci
+ uname -r
+ LOC=/lib/modules/3.13.0-100-generic/kernel/drivers/cpufreq
+ [ -d /lib/modules/3.13.0-100-generic/kernel/drivers/cpufreq ]
+ + find /lib/modules/3.13.0-100-generic/kernel/drivers/cpufreq -type f -name 
cpufreq_*.o -printf basename %f .o\n
/bin/sh
+ find /lib/modules/3.13.0-100-generic/kernel/drivers/cpufreq -type f -name 
cpufreq_*.ko -printf basename %f .ko\n
+ MODAVAIL=
+ uname -m
+ [ x86_64 = ppc ]
+ [ !  =  ]
+ load_detected_cpufreq_modules
+ CPUINFO=/proc/cpuinfo
+ IOPORTS=/proc/ioports
+ [ ! -f /proc/cpuinfo ]
+ grep ^model name /proc/cpuinfo
+ head -1
+ sed -e s/^.*: //;
+ MODEL_NAME=Intel(R) Xeon(R) Gold 6152 CPU @ 2.10GHz
+ grep+  -E ^model[[:space:]]+: /proc/cpuinfo
head -1
+ sed -e s/^.*: //;
+ MODEL_ID=85
+ grep -E ^cpud[^:]+: /proc/cpuinfo
+ head -1
+ sed -e s/^.*: //;
+ CPU=
+ + grep -E ^vendor_id[^:]+: /proc/cpuinfo
head -1
+ sed -e s/^.*: //;
+ VENDOR_ID=GenuineIntel
+ sed -e /^cpu family/ {s/.*: //;p;Q};d /proc/cpuinfo
+ CPU_FAMILY=6
+ MODULE=
+ MODULE_FALLBACK=acpi-cpufreq
+ [ -f /proc/ioports ]
+ grep -q Intel .*ICH /proc/ioports
+ PIII_MODULE=speedstep-smi
+ grep est /proc/cpuinfo
+ [ flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge 
mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat 
epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase 
tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm avx512f rdseed adx smap 
avx512cd
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr 
pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall 
nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor ds_cpl vmx smx est 
tm2 ssse3 fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat 
epb xsaveopt pln pts dtherm tpr_shadow vnmi flexpriority ept vpid fsgsbase 
tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm avx512f rdseed adx smap 
avx512cd
flags   : fpu vme de pse tsc

[Bug 1680553] [NEW] cpufreqd/loadcpufreq fails in trusty

2017-04-06 Thread Mark W Wenning

Public bug reported:

Install 14.04.5 hwe-t on a node using maas, then install cpufreqd and 
cpufrequtils.   
Then run sudo /etc/init.d/loadcpufreq start .
Fails to start.   This happens on an AT system, I will post his output 
shortly.  
I get a similar failure on my system .

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: cpufreqd 2.4.2-2ubuntu1
ProcVersionSignature: User Name 3.13.0-115.162-generic 3.13.11-ckt39
Uname: Linux 3.13.0-115-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Thu Apr  6 18:24:30 2017
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: cpufreqd
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.cpufreqd.conf: 2017-04-05T19:13:09.632907

** Affects: cpufreqd (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug trusty uec-images

** Summary changed:

- cpufreqd/cpufreqinit fails in trusty
+ cpufreqd/loadcpufreq fails in trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1680553

Title:
  cpufreqd/loadcpufreq fails in trusty

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cpufreqd/+bug/1680553/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1643087] Re: Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

2017-02-03 Thread Mark W Wenning

Tim, good news, the upgraded machine returns the right number:

ubuntu@good-hawk:~$ cat /proc/cpuinfo | grep 'processor' | wc -l
272
ubuntu@good-hawk:~$ Intel(R) Xeon(R) CPU E3-1225 v5 @ 3.30GHz

Intel(R) Xeon(R) CPU E3-1225 v5 @ 3.30GHz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643087

Title:
  Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1640547] Re: stress-ng based disk tests failing

2017-02-01 Thread Mark W Wenning

** Attachment added: "submission_2017-02-01T15.41.41.527613.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/plainbox-provider-checkbox/+bug/1640547/+attachment/4811956/+files/submission_2017-02-01T15.41.41.527613.tar.xz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640547

Title:
  stress-ng based disk tests failing

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1640547/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1640547] Re: stress-ng based disk tests failing

2017-02-01 Thread Mark W Wenning

Got some different errors this time, attaching the test output.

ubuntu@ubuntu-DSS1500:~/good-hawk$ cat stress-ng.txt 
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version   Architecture Description
+++-==-=--==
ii  stress-ng  0.07.16-1ppa1 amd64tool to load and stress a computer
ubuntu@ubuntu-DSS1500:~/good-hawk$ 


** Attachment added: "submission_2017-02-01T15.41.41.527613.xml"
   
https://bugs.launchpad.net/ubuntu/+source/plainbox-provider-checkbox/+bug/1640547/+attachment/4811955/+files/submission_2017-02-01T15.41.41.527613.xml

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1640547

Title:
  stress-ng based disk tests failing

To manage notifications about this bug go to:
https://bugs.launchpad.net/stress-ng/+bug/1640547/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1643087] Re: Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

2017-01-30 Thread Mark W Wenning

Hi Tim,
I have the C6320P back and running.   Do you hae a new 4.9 kernel to try, or 
should I apply the same one above?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643087

Title:
  Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu

2017-01-11 Thread Mark W Wenning

Bjorn Helgaas, have you looked at the ACPI dump?   Any suggestions on
how to proceed?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571798

Title:
  Broadwell ECRC Support missing in Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571798/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1643087] Re: Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

2017-01-09 Thread Mark W Wenning

Hi Tim, I'm sure I loaded the right kernel.  
Unfortunately I've lost access to the machine, when I can find another I will 
update this bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643087

Title:
  Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1651851] [NEW] [190247-S5B|]Not all the NVMe can be detected when install Ubuntu 16.04 / 16.04.1 with system connected 12x NVMe

2016-12-21 Thread Mark W Wenning

Public bug reported:

1. Setup system w/ NVMe full install
2. Boot from PXE and install Ubuntu 16.04
3. Check the NVMe detected at partition disk selection list.
4. Not all the NVMe can be detected , and system cannot finished the 
installation.
5. Pls refer to attachment only 3x NVMe detected.(800.2 GB x3 ;512.1 GB is M.2 
device.)

The system config:
CPU:CPU,Skylake-EP,16 Core,2.4GHz,2666,B0,LGA 
3647,256KB/core,165W,22MB,QL28,949716,10.4GT/s,NA,NA,ES2,NA
Storage:Intel P3700,SSDPE2MD800G4,PCI-e,800GB,Gen3 X4 U.2,2.5 - 15mm * 12

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1651851

Title:
  [190247-S5B|]Not all the NVMe can be detected when install Ubuntu
  16.04 / 16.04.1 with system connected 12x NVMe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651851/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1650032] Re: [189162-S5B]System received Call trace and NMI watchdog when boot into Ubuntu 16.04 and system will hang up soon.

2016-12-14 Thread Mark W Wenning

** Attachment added: "Ubuntu_idle.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1650032/+attachment/4791767/+files/Ubuntu_idle.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650032

Title:
  [189162-S5B]System received Call trace and NMI watchdog when boot into
  Ubuntu 16.04 and system will hang up soon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1650032/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1650032] [NEW] [189162-S5B]System received Call trace and NMI watchdog when boot into Ubuntu 16.04 and system will hang up soon.

2016-12-14 Thread Mark W Wenning

Public bug reported:

Steps to reproduce the problem
==
1. Install Ubuntu 16.04 on the toshiba device (M.2 pcie-ssd).
2. Boot to Ubuntu 16.04 and used command :dmesg (have Call trace)
3. And system will showed NMI watchdog and be hang up soon.

The system config:
Toshiba THNSN5512GPU7 SSD,PCI-e,512GB,80mm M.2,Daughter card,Gen3 X4,NA,MP
Storage:Intel,SSDPE2MD800G4,PCI-e,800GB,Gen3 X4 U.2,2.5 - 15mm * 12
CPU:CPU,Skylake-EP,16 Core,2.4GHz,2666,B0,LGA 
3647,256KB/core,165W,22MB,QL28,949716,10.4GT/s,NA,NA,ES2,NA

** Affects: debian-installer (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650032

Title:
  [189162-S5B]System received Call trace and NMI watchdog when boot into
  Ubuntu 16.04 and system will hang up soon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1650032/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1650032] Re: [189162-S5B]System received Call trace and NMI watchdog when boot into Ubuntu 16.04 and system will hang up soon.

2016-12-14 Thread Mark W Wenning

** Attachment added: "Ubuntu_idle2.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1650032/+attachment/4791769/+files/Ubuntu_idle2.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650032

Title:
  [189162-S5B]System received Call trace and NMI watchdog when boot into
  Ubuntu 16.04 and system will hang up soon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1650032/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1650032] Re: [189162-S5B]System received Call trace and NMI watchdog when boot into Ubuntu 16.04 and system will hang up soon.

2016-12-14 Thread Mark W Wenning

** Attachment added: "F2_1_Ubuntu_scheduling.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1650032/+attachment/4791768/+files/F2_1_Ubuntu_scheduling.jpg

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650032

Title:
  [189162-S5B]System received Call trace and NMI watchdog when boot into
  Ubuntu 16.04 and system will hang up soon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1650032/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1650030] [NEW] [189212-S5B]System cannot install Ubuntu 16.04 on this cfg#F2_1 , will hang up soon at partition disk selection list. Edit

2016-12-14 Thread Mark W Wenning

Public bug reported:

[189212-S5B]System cannot install Ubuntu 16.04 on this cfg#F2_1 , will hang up 
soon at partition disk selection list. Steps to reproduce the problem
1. Setup system w/ NVMe full install
2. Boot from PXE and install Ubuntu 16.04 on P3700 pcie-ssd
3. Idle for a while when install progress at partition disk selection list.
4. The system will hang up soon , and SEL w/o any abnormal logs.

Verified more info as below:
a. Ubuntu 16.04 -- > NG
b. Ubuntu 16.04.01 -- > NG
c. Ubuntu 15.10 -- > Pass
d. P3500 PCIE-ssd is passed
The system config:
CPU:CPU,Skylake-EP,16 Core,2.4GHz,2666,B0,LGA 
3647,256KB/core,165W,22MB,QL28,949716,10.4GT/s,NA,NA,ES2,NA
Storage:Intel P3700,SSDPE2MD800G4,PCI-e,800GB,Gen3 X4 U.2,2.5 - 15mm * 12

** Affects: debian-installer (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1650030

Title:
  [189212-S5B]System cannot install Ubuntu 16.04 on this cfg#F2_1 , will
  hang up soon at partition disk selection list. Edit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1650030/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1648388] Re: Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system hangs while rebooting

2016-12-08 Thread Mark W Wenning

** Project changed: magnum => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1648388

Title:
  Install Ubuntu16.04 in RAID1 created by Intel RSTe and the system
  hangs while rebooting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1648388/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1640547] Re: stress-ng based disk tests failing

2016-12-05 Thread Mark W Wenning

Mike, will this fix the stress-related errors I'm seeing in Xeon Phi on
Dell C6320p?
https://certification.canonical.com/hardware/201611-25216/

Thanks,

Mark Wenning
Technical Partner Manager, Cloud Alliances
Canonical, Ltd
mark.wenn...@canonical.com
-
"We will encourage you to develop the three great virtues of a programmer:
laziness, impatience, and hubris." -- Larry Wall, Programming Perl (1st
edition), Oreilly And Associates


On Mon, Dec 5, 2016 at 10:17 AM, Mike Rushton 
wrote:

> stress-ng was at 0.05.23-1ubuntu2 for the above tests.
>
> I have now upgraded stress-ng from the package in Xenial to that from
> Zesty:
>
> $ sudo apt-cache policy stress-ng
> stress-ng:
>   Installed: 0.07.08-1
>   Candidate: 0.07.08-1
>   Version table:
>  *** 0.07.08-1 500
> 500 http://ports.ubuntu.com/ubuntu-ports zesty/universe ppc64el
> Packages
> 100 /var/lib/dpkg/status
>  0.05.23-1ubuntu2 500
> 500 http://ports.ubuntu.com/ubuntu-ports xenial-updates/universe
> ppc64el Packages
>  0.05.23-1 500
> 500 http://ports.ubuntu.com/ubuntu-ports xenial/universe ppc64el
> Packages
>
> $ sudo stress-ng --sync-file 1
> stress-ng: info:  [2626] defaulting to a 86400 second run per stressor
> stress-ng: info:  [2626] dispatching hogs: 1 sync-file
> stress-ng: info:  [2626] cache allocate: using built-in defaults as unable
> to determine cache details
> stress-ng: info:  [2626] cache allocate: default cache size: 2048K
> stress-ng: info:  [2627] stress-ng-sync-file: this stressor is not
> implemented on this system: ppc64le Linux 4.4.0-51-generic
> stress-ng: info:  [2626] successful run completed in 0.00s
>
>
> Mind you, this sync-file stressor is more of a red herring and isn't the
> cause of the system lockups.
>
> I have also found that this bug shows up on all 3 open power servers
> running petitboot that I have access to at the moment. If I had access
> to a Tuleta, I'm going to guess this would also affect that as well. I
> have a good feeling this is just like the memory test[0] (still not
> resolved). As of now, the stress_ng memory and disk tests both fail with
> really similar results (system/session lockup).
>
> [0] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573062
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1640547
>
> Title:
>   stress-ng based disk tests failing
>
> Status in Stress-ng:
>   In Progress
> Status in plainbox-provider-checkbox package in Ubuntu:
>   Triaged
> Status in plainbox-provider-checkbox source package in Xenial:
>   Triaged
>
> Bug description:
>   When running the stress-ng disk test, we are seeing the following
>   failures as well as I/O lockup:
>
>   /dev/sda is a block device
>   Found largest partition: "/dev/sda2"
>   Test will use /dev/sda2, mounted at "/", using "ext4"
>   test_dir is /tmp/disk_stress_ng
>   Estimated total run time is 4560 seconds
>
>   Running stress-ng aio stressor for 240 seconds
>   stress-ng: info:  [4305] dispatching hogs: 160 aio
>   stress-ng: info:  [4305] cache allocate: using built-in defaults as
> unable to determine cache details
>   stress-ng: info:  [4305] cache allocate: default cache size: 2048K
>   stress-ng: info:  [4305] successful run completed in 240.27s (4 mins,
> 0.27 secs)
>   return_code is 0
>   Running stress-ng aiol stressor for 240 seconds
>   stress-ng: info:  [4917] dispatching hogs: 160 aio-linux
>   stress-ng: info:  [4917] cache allocate: using built-in defaults as
> unable to determine cache details
>   stress-ng: info:  [4917] cache allocate: default cache size: 2048K
>   stress-ng: fail:  [5002] stress-ng-aio-linux: io_setup failed, errno=1
> (Operation not permitted)
>   stress-ng: fail:  [5012] stress-ng-aio-linux: io_setup failed, errno=1
> (Operation not permitted)
>   stress-ng: fail:  [5020] stress-ng-aio-linux: io_setup failed, errno=1
> (Operation not permitted)
>   stress-ng: fail:  [5018] stress-ng-aio-linux: io_setup failed, errno=1
> (Operation not permitted)
>   stress-ng: fail:  [5019] stress-ng-aio-linux: io_setup failed, errno=1
> (Operation not permitted)
>   stress-ng: fail:  [5013] stress-ng-aio-linux: io_setup failed, errno=1
> (Operation not permitted)
>   stress-ng: fail:  [4959] stress-ng-aio-linux: io_setup failed, errno=1
> (Operation not permitted)
>   stress-ng: fail:  [5032] stress-ng-aio-linux: io_setup failed, errno=1
> (Operation not permitted)
>   stress-ng: fail:  [5041] stress-ng-aio-linux: io_setup failed, errno=1
> (Operation not permitted)
>   stress-ng: fail:  [5017] stress-ng-aio-linux: io_setup failed, errno=1
> (Operation not permitted)
>   stress-ng: fail:  [5022] stress-ng-aio-linux: io_setup failed, errno=1
> (Operation not permitted)
>   stress-ng: fail:  [5016] stress-ng-aio-linux: io_setup failed, errno=1
> (Operation not permitted)
>   stress-ng: fail:  [5038] stress-ng-aio-linux: io_setup failed, errno=1
>

[Bug 1643087] Re: Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

2016-12-02 Thread Mark W Wenning

Tim, it came up OK with the new kernel, no segfaults that I see.  cat
/proc/cpuinfo | grep 'cpu id' | wc -l returns 256 .

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643087

Title:
  Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1643087] Re: Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

2016-12-02 Thread Mark W Wenning

Ok Tim, looks like it's back up.   What do you want to see?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643087

Title:
  Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1643087] Re: Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

2016-12-01 Thread Mark W Wenning

Ok Tim, tryng it now.
How is this different than the one Joe set up in the bug?

Mark Wenning
Technical Partner Manager, Cloud Alliances
Canonical, Ltd
mark.wenn...@canonical.com
-
"We will encourage you to develop the three great virtues of a programmer:
laziness, impatience, and hubris." -- Larry Wall, Programming Perl (1st
edition), Oreilly And Associates


On Thu, Dec 1, 2016 at 4:04 PM, Tim Gardner 
wrote:

> Mark,
>
> mkdir 4.9.0.5.6
> cd 4.9.0.5.6
> wget http://kernel.ubuntu.com/~rtg/linux-4.9.0.5.6/linux-image-4.
> 9.0-5-generic_4.9.0-5.6_amd64.deb
> wget http://kernel.ubuntu.com/~rtg/linux-4.9.0.5.6/linux-image-
> extra-4.9.0-5-generic_4.9.0-5.6_amd64.deb
> sudo dpkg -i *.deb
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1643087
>
> Title:
>   Yakkety failures on Xeon Phi (Dell Poweredge C6320p)
>
> Status in linux package in Ubuntu:
>   Confirmed
> Status in linux source package in Yakkety:
>   Confirmed
>
> Bug description:
>   Dell Poweredge C6320p machine with Intel Xeon Phi processor, running
> certification tests.
>   I see 2 segfaults in the logs, there are more errors in the cert tests
> which I will post later.
>
>   Linux brief-badger 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13
>   UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1643087/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643087

Title:
  Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1646277] [NEW] Xenial desktop 16.04.x will have a black screen after PXE installation

2016-11-30 Thread Mark W Wenning

Public bug reported:


The display will keep black screen after install 16.04.x via PXE(need use 
"Ctrl+Alt+F1" to change to terminal 1, then can see text mode screen)

Quanta team is installing Xenial desktop using PXE boot.   After the
installation, the console will show a black screen.   Hitting ctl-alt-f1
displays the text mode screen OK.

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1646277

Title:
  Xenial desktop 16.04.x will have a black screen after PXE installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1646277/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1643087] Re: Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

2016-11-30 Thread Mark W Wenning

Sure Tim, let me know when it's done building and a link to get to it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643087

Title:
  Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1643087] Re: Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

2016-11-29 Thread Mark W Wenning

Tried with Joe's kernel above:
ubuntu@brief-badger:~$ uname -a
Linux brief-badger 4.9.0-040900rc6-generic #201611201731 SMP Sun Nov 20 
22:33:21 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

** Attachment added: "c6320p_info_kernel_4.9-rc6.tgz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+attachment/4784802/+files/c6320p_info_kernel_4.9-rc6.tgz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643087

Title:
  Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1643087] Re: Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

2016-11-29 Thread Mark W Wenning

Xiong, the BIOS level on the machine is 1.0.0 .  Where would I get the
latest BIOS?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643087

Title:
  Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1643087] Re: Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

2016-11-22 Thread Mark W Wenning

Joseph, 
This is a pretty new machine, as far as I know it's been tested with Xenial and 
Yakkety.  
I will try to run the test kernel next week when I get back.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643087

Title:
  Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1643087] Re: Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

2016-11-18 Thread Mark W Wenning

Got the following when I tried to run apport-collect:
ubuntu@brief-badger:~$ apport-collect 1643087
The authorization page:
 
(https://launchpad.net/+authorize-token?oauth_token=0h42c3flxcPFlcTk6RqB_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
ERROR: connecting to Launchpad failed: local variable 'browser_obj' referenced 
before assignment
You can reset the credentials by removing the file 
"/home/ubuntu/.cache/apport/launchpad.credentials"
ubuntu@brief-badger:~$ 

This is a server (maas node) so no browser was available.   Opened the url in 
my laptop and authorized, nothing exciting happened.  
Marking confirmed.


** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643087

Title:
  Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1643087] Re: Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

2016-11-18 Thread Mark W Wenning

** Attachment added: "lspci-vnvn.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+attachment/4779652/+files/lspci-vnvn.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643087

Title:
  Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1643087] Re: Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

2016-11-18 Thread Mark W Wenning

Tar file with all the logs:
C6320p_info:
total 892
drwxrwxr-x   2 mwenning mwenning   4096 Nov 18 17:09 ./
drwxr-xr-x 102 mwenning mwenning  12288 Nov 18 17:24 ../
-rw-r--r--   1 mwenning mwenning   5321 Nov 18 17:09 alternatives.log
-rw-r-   1 mwenning mwenning490 Nov 18 17:09 apport.log
-rw-r-   1 mwenning mwenning   3187 Nov 18 17:09 auth.log
-rw-r--r--   1 mwenning mwenning 157698 Nov 18 17:09 cloud-init.log
-rw-r--r--   1 mwenning mwenning   4622 Nov 18 17:09 cloud-init-output.log
-rw-rw-r--   1 mwenning mwenning 266308 Nov 18 17:09 cpuinfo.txt
-rw-rw-r--   1 mwenning mwenning  82262 Nov 18 17:09 dmesg.txt
-rw-r--r--   1 mwenning mwenning 217921 Nov 18 17:09 dpkg.log
-rw-r--r--   1 mwenning mwenning510 Nov 18 17:09 fontconfig.log
-rw-r-   1 mwenning mwenning 124475 Nov 18 17:09 kern.log
-rw-rw-r--   1 mwenning mwenning111 Nov 18 17:09 uname.txt


** Attachment added: "C6320p_info.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+attachment/4779651/+files/C6320p_info.tar.gz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643087

Title:
  Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1643087] [NEW] Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

2016-11-18 Thread Mark W Wenning

Public bug reported:

Dell Poweredge C6320p machine with Intel Xeon Phi processor, running 
certification tests.
I see 2 segfaults in the logs, there are more errors in the cert tests which I 
will post later.  

Linux brief-badger 4.8.0-27-generic #29-Ubuntu SMP Thu Oct 20 21:03:13
UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1643087

Title:
  Yakkety failures on Xeon Phi (Dell Poweredge C6320p)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1643087/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1638753] Re: 185175_[F06G]System dmesg and messages will occur some abnormall messages after install Ubuntu14.04.2 with OCE14102-UM PCIe card.

2016-11-02 Thread Mark W Wenning

This is a similar issue to
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1491654

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638753

Title:
  185175_[F06G]System dmesg and messages will occur some abnormall
  messages after install Ubuntu14.04.2 with OCE14102-UM PCIe card.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1638753] Re: 185175_[F06G]System dmesg and messages will occur some abnormall messages after install Ubuntu14.04.2 with OCE14102-UM PCIe card.

2016-11-02 Thread Mark W Wenning

** Attachment added: "sosreport.7z"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638753/+attachment/4771466/+files/sosreport.7z

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638753

Title:
  185175_[F06G]System dmesg and messages will occur some abnormall
  messages after install Ubuntu14.04.2 with OCE14102-UM PCIe card.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1638753] [NEW] 185175_[F06G]System dmesg and messages will occur some abnormall messages after install Ubuntu14.04.2 with OCE14102-UM PCIe card.

2016-11-02 Thread Mark W Wenning

Public bug reported:

Steps to reproduce the problem
==
1. Plug-in PCIe card OCE14102-UM.
2. Install Ubuntu14.04.2 UEFI mode by PXE.
3. After OS installation finished, use WhiteList tool to check if there has 
error messages or not.

Please help clarify below error message could be ignore, or not.
dmesg:
FAIL Aug 9 10:53:17 quanta kernel: [ 2.327316] be2net :01:00.0: PCIe error 
reporting enabled
FAIL Aug 9 10:53:17 quanta kernel: [ 3.266823] be2net :01:00.1: PCIe error 
reporting enabled
FAIL Aug 9 10:53:17 quanta dhclient: Error getting interface address for 
'eth2'; No such device
FAIL Aug 9 10:53:17 quanta dhclient: Error getting interface information.
FAIL Aug 9 11:04:57 quanta dhclient: Error getting interface address for 
'eth1'; No such device
FAIL Aug 9 11:04:57 quanta dhclient: Error getting interface information.
messages:
FAIL [ 2.211792] be2net :01:00.0: PCIe error reporting enabled
FAIL [ 3.151426] be2net :01:00.1: PCIe error reporting enabled

Test configuration:
=
MB:MB: Product=[F06G-AST2400], P/N=[31F06MB00Y0], S/N=[BSX61600044]
CPLD:CPLD: Device ID=[], Version=[]CPU0 VR: Version 0=[], Version 1=[]CPU1 VR: 
Version 0=[], Version 1=[]DIMM_AB VR: Version 0=[], Version 1=[]DIMM_CD VR: 
Version 0=[], Version 1=[]DIMM_EF VR: Version 0=[], Version 1=[]DIMM_GH VR: 
Version 0=[], Version 1=[]
OS:OS: Kernel=[3.16.0-30-generic], Description=[Ubuntu 14.04.2 LTS], Boot 
Mode=[UEFI]Network: Interface=[eth0], IPv4 Addr=[192.168.124.41], IPv6 
Link-Local Addr=[fe80::56ab:3aff:fe74:407e], IPv6 
Addr=[3ffe:124::56ab:3aff:fe74:407e]
Storage:SOM-C610(F06G-sSATA-AHCI), FW=[TBD], Driver=[3.0]
SOM-C610(F06G-SATA-AHCI), FW=[TBD], Driver=[3.0]
MTFDDAT128MBF(MTFDDAT128MBF-1AN), FW=[MU01], Driver=[NA]

CPU:E5-2643 v4(CM8066002041500),3.4GHz,QS
E5-2643 v4(CM8066002041500),3.4GHz,QS
Memory:HMA41GR7AFR8N-UH,19200(2400MHz),8GB,DDR4,Slot=[A0]
HMA41GR7AFR8N-UH,19200(2400MHz),8GB,DDR4,Slot=[A1]
HMA41GR7AFR8N-UH,19200(2400MHz),8GB,DDR4,Slot=[A4]
HMA41GR7AFR8N-UH,19200(2400MHz),8GB,DDR4,Slot=[A5]
HMA41GR7AFR8N-UH,19200(2400MHz),8GB,DDR4,Slot=[B0]
HMA41GR7AFR8N-UH,19200(2400MHz),8GB,DDR4,Slot=[B1]
HMA41GR7AFR8N-UH,19200(2400MHz),8GB,DDR4,Slot=[B2]
HMA41GR7AFR8N-UH,19200(2400MHz),8GB,DDR4,Slot=[B3]
HMA41GR7AFR8N-UH,19200(2400MHz),8GB,DDR4,Slot=[B4]
HMA41GR7AFR8N-UH,19200(2400MHz),8GB,DDR4,Slot=[B5]
HMA41GR7AFR8N-UH,19200(2400MHz),8GB,DDR4,Slot=[B6]
HMA41GR7AFR8N-UH,19200(2400MHz),8GB,DDR4,Slot=[B7]
Networking:LOM-i210(F06G-LOM-i210), FW=[3.25,NA], Driver=[5.2.13-k]
 ON 10GbE X540(37S2SLB0020), FW=[4.04.0,NA], Driver=[3.19.1-k]
ID=[10df:0720,10df:e800], FW=[10.2.370.19], Driver=[10.2u]

VGA:AST2x00(Need submit eTrack to correct SVID), FW=[1.00.07],
Driver=[OS Native]

TPM:TPM: None
Others:USB Controller: ID=[8086:8d2d,152d:89b4], Bus Addr=[:00:1a.0], 
Description=[Intel Corporation C610/X99 series chipset USB Enhanced Host 
Controller #2 (rev 05)], Version=[2.0]USB Controller: ID=[8086:8d26,152d:89b4], 
Bus Addr=[:00:1d.0], Description=[Intel Corporation C610/X99 series chipset 
USB Enhanced Host Controller #1 (rev 05)], Version=[2.0]USB Device: 
ID=[046b:ff10], Bus Addr=[:00:1a.0], Description=[American Megatrends, Inc. 
Virtual Keyboard and Mouse], Version=[1.10]
Power Supply:PSU: PSU Status not Found in SDR
Chassis:System: Product=[F06G-AST2400], Project=[3C05]
FRU/SDR:SDR: Version=[0x51]FRU: Board FRU ID=[FRU Ver 0.01]FRU: Builtin FRU 
Device (ID 0), [Chassis Type]=Rack Mount Chassis, [Chassis 
Serial]=QTFCKQ44603A6, [Board Mfg Date]=Fri Apr 15 13:05:00 2016, [Board 
Mfg]=Quanta Cloud Technology Inc., [Board Product]=F06G-AST2400, [Board 
Serial]=BSX61600044, [Board Part Number]=31F06MB00Y0, [Product 
Manufacturer]=Quanta Cloud Technology Inc., [Product Name]=F06G-AST2400, 
[Product Part Numb

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "20160809_191326.7z"
   
https://bugs.launchpad.net/bugs/1638753/+attachment/4771465/+files/20160809_191326.7z

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638753

Title:
  185175_[F06G]System dmesg and messages will occur some abnormall
  messages after install Ubuntu14.04.2 with OCE14102-UM PCIe card.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1638753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1606940] Re: A a single PCI read or write appears twice on the PCIe bus. This happens when using the SR-IOV feature with some PCI devices

2016-10-18 Thread Mark W Wenning

This bug can be marked as resolved.

From: "Panicker, Manojkumar" 
To: Bug 1606940 <1606...@bugs.launchpad.net>
Cc: 
Date: Mon, 17 Oct 2016 04:50:08 +
Subject: RE: [Bug 1606940] Re: A a single PCI read or write appears twice on 
the PCIe bus. This happens when using the SR-IOV feature with some PCI devices
I believe we have already indicated that the patch works to resolve this 
problem. Please let us know if you are looking for something more specific.

Manoj

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1606940

Title:
  A a single PCI read or write appears twice on the PCIe bus. This
  happens when using the SR-IOV feature with some PCI devices

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1606940/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1592571] [NEW] lshw B.02.17 is missing system information

2016-06-14 Thread Mark W Wenning

Public bug reported:

Systems:  multiple, example below is on Ubuntu Wily. This also happens on 
Xenial.
$ lsb_release -rd
Description:Ubuntu 15.10
Release:15.10
$ 

Trusty uses lshw B.02.16 and does not see this bug.


lshw facility does not report all the system information in the current version 
(B.02.17) :
$ sudo lshw -version
B.02.17
$ sudo lshw -class system
virgil
description: Computer
width: 64 bits
capabilities: smbios-2.7 vsyscall32
$ 

Version B.02.16 displays product, vendor, version, etc.  
Compiling and running the new version (B.02.18) also displays all the 
information :
$ sudo ./lshw-static -class system
virgil  
description: Laptop
product: Latitude E7440 (Latitude E7440)
vendor: Dell Inc.
version: 01
serial: ***
width: 4294967295 bits
capabilities: smbios-2.7 dmi-2.7 smp vsyscall32
configuration: administrator_password=disabled boot=normal chassis=laptop 
frontpanel_password=disabled keyboard_password=disabled 
power-on_password=disabled sku=Latitude E7440 uuid=**
$

** Affects: lshw (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1592571

Title:
  lshw B.02.17 is missing system information

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1592571/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu

2016-04-21 Thread Mark W Wenning

Fantastic, thanks John.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571798

Title:
  Broadwell ECRC Support missing in Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571798/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1571798] Re: Broadwell ECRC Support missing in Ubuntu

2016-04-20 Thread Mark W Wenning

Thanks John,

Can you test some earlier versions of Ubuntu 14.04 and see if you have
the same problem?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571798

Title:
  Broadwell ECRC Support missing in Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571798/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1571798] [NEW] Broadwell ECRC Support missing in Ubuntu

2016-04-18 Thread Mark W Wenning

Public bug reported:

Here is the problem statement from the Dell team:

When booting into Ubuntu 14.04.4 with a Broadwell CPU and an Intel Quick
Assist Card, the memory location that corresponds to ECRC is set to
0x01e0, when the BIOS is setting this location 0x00a0 pre-OS boot.  This
causes the card to not function unless we implement the following
workaround using setpci.

“setpci –s AA:BB.C 160.w=0”, where AA:BB.C is the PCI Root Path for the
Intel Quick Assit Card.

We’ve verified the memory location is correct when booting to other
OSes, such as RHEL 7.2 and Windows Server 2012 R2.

If there is any information you can give as to why this may be occurring
in Ubuntu or where we may start to debug when the memory is changed, we
would appreciate it.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571798

Title:
  Broadwell ECRC Support missing in Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1571798/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1518095] [NEW] lshw reports "Bus Error" or nothing on arm7l machine

2015-11-19 Thread Mark W Wenning

Public bug reported:

lshw reports "Bus Error" or nothing when run on an arm7 machine

ISEE IGEPv2 board:
OMAP 3520 (ARM Cortex A-8)
SDRAM 512 MB
Flash 512 MB
Ubuntu 12.05.5 LTS

-
( log in) 
Welcome to Ubuntu 12.04.5 LTS (GNU/Linux 2.6.37 armv7l)

 * Documentation:  https://help.ubuntu.com/

  System information as of Sun Jan  2 21:27:03 UTC 2000

  System load:  0.39  Processes:   75
  Usage of /:   27.9% of 1.80GB   Users logged in: 1
  Memory usage: 22%   IP address for eth0: 192.168.1.16
  Swap usage:   0%

  Graph this data and manage this system at:
https://landscape.canonical.com/
Last login: Sun Jan  2 21:25:00 2000 from 192.168.1.13
root@igep00x0:~# uname -a
Linux igep00x0 2.6.37 #1 Thu Jun 5 19:12:04 CEST 2014 armv7l armv7l armv7l 
GNU/Linux
root@igep00x0:~# sudo lshw -v
Hardware Lister (lshw) - B.02.15
usage: lshw [-format] [-options ...]
   lshw -version

-versionprint program version (B.02.15)

format can be
-html   output hardware tree as HTML
-xmloutput hardware tree as XML
-short  output hardware paths
-businfooutput bus information

options can be
-class CLASSonly show a certain class of hardware
-C CLASSsame as '-class CLASS'
-c CLASSsame as '-class CLASS'
-disable TEST   disable a test (like pci, isapnp, cpuid, etc. )
-enable TESTenable a test (like pci, isapnp, cpuid, etc. )
-quiet  don't display status
-sanitize   sanitize output (remove sensitive information like 
serial numbers, etc.)
-numericoutput numeric IDs (for PCI, USB, etc.)

root@igep00x0:~#
root@igep00x0:~# lshw -short
Bus error
root@igep00x0:~# lshw -html 
Bus error
root@igep00x0:~# lshw -xml
Bus error
root@igep00x0:~# ^C
root@igep00x0:~# 
 
 

Normally I would try Trusty, but I don't think it is supported.

** Affects: lshw (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1518095

Title:
  lshw reports "Bus Error" or nothing on arm7l machine

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lshw/+bug/1518095/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1423343] Re: [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v

2015-10-22 Thread Mark W Wenning

Marked Invalid, Josh will submit in a set of different bug(s)

** Changed in: linux (Ubuntu)
   Status: Triaged => Invalid

** Changed in: linux (Ubuntu Vivid)
   Status: Triaged => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423343

Title:
  [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423343/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1490545] Re: [Hyper-V] lis daemons not active after install on Ubuntu 15.10 Wily Werewolf

2015-10-22 Thread Mark W Wenning

Considered fixed, marking invalid.

** Changed in: linux (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: linux (Ubuntu Wily)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1490545

Title:
  [Hyper-V] lis daemons not active after install on  Ubuntu 15.10 Wily
  Werewolf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1490545/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1463584] Re: [Hyper-V] Add support for VMBus panic notifier handler

2015-07-22 Thread Mark W Wenning

From tpp-hyperv buglist, Microsoft states:

We've also verified on Hyper-V both Trusty and Utopic and the behavior is as 
expected.
Can be removed from the tpp list

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1463584

Title:
  [Hyper-V] Add support for VMBus panic notifier handler

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1463584/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1434247] Re: [FFE] Upstream patches to Libvirt for vivid

2015-03-20 Thread Mark W Wenning

#2 , that is correct, I opened the bug in the wrong category.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434247

Title:
  [FFE] Upstream patches to Libvirt for vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1434247/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1434247] Re: [FFE] Upstream patches to Libvirt for vivid

2015-03-20 Thread Mark W Wenning

** Description changed:

+ Libvirt now has native support for pluging vNICs into the midonet
+ overlay.
  
- Libvirt now has native support for pluging vNICs into the midonet overlay.
+ The change in libvirt would make Ubuntu Openstack with MidoNet use a
+ supported interface mode of libvirt instead of a domain tainting mode;
+ this would allow for a cleaner back-end plumbing as today a separate
+ tool is used.
  
  Proposing that these upstream patches go into Vivid release.
  
  Patches to ibvirt:
  
http://libvirt.org/git/?p=libvirt.git;a=commit;h=e1f64856941630c0e4944c43384aa3ddbe9db810
  
http://libvirt.org/git/?p=libvirt.git;a=commit;h=a9fbe3b15740856863561b809e8196b2d87adce2
  
http://libvirt.org/git/?p=libvirt.git;a=commit;h=d490f47ba373226b65bbff750fd14254a47057a1
  
  MidoNet issue tracking this change:
  https://midonet.atlassian.net/browse/MNA-97

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434247

Title:
  [FFE] Upstream patches to Libvirt for vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1434247/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1434247] [NEW] Upstream patches to Libvirt for vivid

2015-03-19 Thread Mark W Wenning

Public bug reported:


Libvirt now has native support for pluging vNICs into the midonet overlay.

Proposing that these upstream patches go into Vivid release.

Patches to ibvirt:
http://libvirt.org/git/?p=libvirt.git;a=commit;h=e1f64856941630c0e4944c43384aa3ddbe9db810
http://libvirt.org/git/?p=libvirt.git;a=commit;h=a9fbe3b15740856863561b809e8196b2d87adce2
http://libvirt.org/git/?p=libvirt.git;a=commit;h=d490f47ba373226b65bbff750fd14254a47057a1

MidoNet issue tracking this change:
https://midonet.atlassian.net/browse/MNA-97

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Incomplete


** Tags: vivid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434247

Title:
  Upstream patches to Libvirt for vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1434247/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1434257] [NEW] MAAS should set dnssec-validation to no in /etc/bind/named.conf.options

2015-03-19 Thread Mark W Wenning

Public bug reported:

Several enterprise customers have had problems bootstrapping juju,
getting errors like:

Download failed. wait 15s\nAttempt 5 to download tools from
https://streams.canonic al.com/juju/tools/releases/juju-1.21.3-trusty-
amd64.tgz...\ncurl: (6) Could not resolve host: streams.canonica
l.com\ntools from
https://streams.canonical.com/juju/tools/releases/juju-1.21.3-trusty-
amd64.tgz downloaded: H TTP 000; time 9.519s; size 0 bytes; speed 0.000
bytes/s sha256sum: /var/lib/juju/tools/1.21.3-trusty-amd64/too
ls.tar.gz: No such file or directory\nERROR failed to bootstrap
environment: subprocess encountered error code 1\n', 'status': 1}'
[DEBUG ?? 03-19 13:21:00] ?? cloudinstall.utils ?? (utils.py,
global_exchandler, 62)] Traceback (most recent call last): File
/usr/share/openstack/cloudinstall/utils.py, line 77, in run
super().run() File /usr/lib/python3.4/threading.py, line 868, in run
self._target(*self._args, **self._kwargs) File
/usr/share/openstack/cloudinstall/machinewait.py, line 127, in
do_continue self.installer.do_install() File
/usr/share/openstack/cloudinstall/multi_install.py, line 144, in
do_install raise Exception(Problem with juju bootstrap.) Exception:
Problem with juju bootstrap.

solution turned out to be editing /etc/bind/named.conf.options and changing the 
line 
dnssec-validation auto; 
to 
dnssec-validation no;

** Affects: maas (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1434257

Title:
  MAAS should set dnssec-validation to no in
  /etc/bind/named.conf.options

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1434257/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1434257] [NEW] MAAS should set dnssec-validation to no in /etc/bind/named.conf.options

2015-03-19 Thread Mark W Wenning

Public bug reported:

Several enterprise customers have had problems bootstrapping juju,
getting errors like:

Download failed. wait 15s\nAttempt 5 to download tools from
https://streams.canonic al.com/juju/tools/releases/juju-1.21.3-trusty-
amd64.tgz...\ncurl: (6) Could not resolve host: streams.canonica
l.com\ntools from
https://streams.canonical.com/juju/tools/releases/juju-1.21.3-trusty-
amd64.tgz downloaded: H TTP 000; time 9.519s; size 0 bytes; speed 0.000
bytes/s sha256sum: /var/lib/juju/tools/1.21.3-trusty-amd64/too
ls.tar.gz: No such file or directory\nERROR failed to bootstrap
environment: subprocess encountered error code 1\n', 'status': 1}'
[DEBUG ?? 03-19 13:21:00] ?? cloudinstall.utils ?? (utils.py,
global_exchandler, 62)] Traceback (most recent call last): File
/usr/share/openstack/cloudinstall/utils.py, line 77, in run
super().run() File /usr/lib/python3.4/threading.py, line 868, in run
self._target(*self._args, **self._kwargs) File
/usr/share/openstack/cloudinstall/machinewait.py, line 127, in
do_continue self.installer.do_install() File
/usr/share/openstack/cloudinstall/multi_install.py, line 144, in
do_install raise Exception(Problem with juju bootstrap.) Exception:
Problem with juju bootstrap.

solution turned out to be editing /etc/bind/named.conf.options and changing the 
line 
dnssec-validation auto; 
to 
dnssec-validation no;

** Affects: maas (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1434257

Title:
  MAAS should set dnssec-validation to no in
  /etc/bind/named.conf.options

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1434257/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1177148] Re: DVD medium locked and not released by Ubuntu on Windows server 2012 and OS133/134

2015-03-18 Thread Mark W Wenning

** Changed in: ubuntu
   Status: Confirmed = Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1177148

Title:
  DVD medium locked and not released by Ubuntu on Windows server 2012
  and OS133/134

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1177148/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1413020] Re: [Hyper-V] IP injection adds the line “# The following stanza(s) added by hv_set_ifconfig” for every pass.

2015-02-19 Thread Mark W Wenning

Verified in Dell RR5 HyperV cluster lab using trusty-proposed and
utopic-proposed.

** Tags removed: verification-needed-trusty verification-needed-utopic
** Tags added: verification-done-trusty verification-done-utopic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413020

Title:
  [Hyper-V] IP injection adds  the line “# The following stanza(s) added
  by hv_set_ifconfig” for every pass.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413020/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1423343] Re: [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v

2015-02-18 Thread Mark W Wenning

These are requested patches from the Microsoft Hyper-v team, I don't
think apport will do much.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423343

Title:
  [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423343/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1423343] Re: [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v

2015-02-18 Thread Mark W Wenning

** Changed in: linux (Ubuntu)
   Status: Incomplete = Opinion

** Changed in: linux (Ubuntu)
   Status: Opinion = Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423343

Title:
  [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1423343/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1423343] [NEW] [Hyper-V][ubuntu 15.04] various upstream patches for hyper-v

2015-02-18 Thread Mark W Wenning

Public bug reported:

Following patches are missing from ubuntu vivid 15.04 compared to latest
upstream (linux-next) , please include them in ubuntu vivid , all the
patches listed here are already upstream .

/arch/x86/include/uapi/asm/hyperv.h

1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2
2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9e7827b5ea4ca93b4d864bc07c0fafb838d496b1

/drivers/hv/hyperv_vmbus.h
1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2

drivers/hv/vmbus_drv.c
1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=a45de93eb10ae6aec2c73d722562ab46092a
2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d8a60e000c951f845d9a5fb3e67853e0e63a5659
3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4061ed9e2aaac31daef44f06e9b83143c78b24b2
4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=90f3453585479d5beb75058da46eb573ced0e6ac
5. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=302a3c0f2757ae1a3e7df3f9fa1f20e2214ab945
6. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=b0209501dc7586cbfbf6d023f2dd3ce4621aff2c

/drivers/hv/hv_snapshot.c
1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8d9560ebcc6448472b3afe8f36f37d6b0de8f5a4
2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=649142074d86afebe0505431a93957505d244dd6

/drivers/hv/hv_kvp.c
1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=8d9560ebcc6448472b3afe8f36f37d6b0de8f5a4

/drivers/hv/hv_fcopy.c
1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d9b1652947c695d247b5e4603a16213ec55661ed

/drivers/hv/channel.c
1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67fae053bfc6e84144150e4c6c62670abb215c33
2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d61031ee8df6214d58371a1cc36a0591e242fba0
3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9f52a1630922bcdab75fc72e59ed58db8e164314

/drivers/hv/channel_mgmt.c
1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d7f2fbafb4f84306436277664cf28042beaf252a
2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=67fae053bfc6e84144150e4c6c62670abb215c33
3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9c3a6f7e476fc4961297fc66b1177f9f8c8dd238
4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=87712bf81dd092821c406ea3fb47a07222484a64
5. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c3582a2c4d0baf1fa3955c8b3d3d61308df474c7

/drivers/hv/hv_balloon.c
1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=ab3de22bb4a3d4bda2d0ec8bebcb76a40f1cbf9b
2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=22f88475b62ac826acae2f77c3e1bd9543e87b2a
3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=79208c57da5311860f165b613c89b3f647e357cd
4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=f6712238471a8afdbfcea482483fc121281292d8

/tools/hv/hv_vss_daemon.c
1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=9e5db05aae4657c7ade34ccc4b93f27ab647498e
2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=7a401744d517864f8f2f2afba589e58a71d03aa6
3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=170f4bea2008054e5098f99359e29823a7b4b1b9
4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4f689190bb55d171d2f6614f8a6cbd4b868e48bd

/tools/hv/hv_fcopy_daemon.c
1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c1136da62170465920eea1ae9ba9ce2234091f77
2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=aba474b8185d60ca8cdbf3049fe6d655aa761e23

/drivers/net/hyperv/netvsc.c
1. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=da19fcd0d85f36420f578fe6dfe7a2a581b4fa6e
2. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=d953ca4ddf71aa91a4596b2ff7ff1598f6ad4708
3. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=7390fe9c9a7ffdb0947add66efe7dedbe6b1cb6f
4. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=c51ed18257e731e15541324cd58bd3761d9d3b1c
5. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=aa99c47933d2c9a7622440d1b08ebb46ad8bd741
6. 
http://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/commit/?id=4d3c9d37f77566b04216dfc9a6513082002d7a1f

[Bug 1404509] Re: [precise, trusty] udev does not automatically load modules with kernel = 3.11

2015-02-13 Thread Mark W Wenning

Tested and verified on PowerEdge R620 with trusty-proposed.  
After updating and dist-upgrade, /dev/ipmi0 shows up as a device.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1404509

Title:
  [precise, trusty] udev does not automatically load modules with kernel
  = 3.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1404509/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1331214] Re: MAAS (amttool) cannot control AMT version 8

2015-02-13 Thread Mark W Wenning

Verified on several VPro machines in the Dell lab, with different AMT
firmware levels.

##  PowerEdge T20 FW 9.0.21-build 1462works

##  Laptop: E6400   FW 4.2.60-build 1060works
##  Laptop: E6520   FW 7.1.4-build  1068works
##  Laptop: E6430  FW 8.0.1-build  1399works
##  Laptop: M4700FW 8.1.40-build 1416works

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1331214

Title:
  MAAS (amttool) cannot control AMT version  8

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1331214/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1331214] Re: MAAS (amttool) cannot control AMT version 8

2015-02-13 Thread Mark W Wenning

Verified on several VPro machines in the Dell lab, with different AMT
firmware levels.

##  PowerEdge T20 FW 9.0.21-build 1462works

##  Laptop: E6400   FW 4.2.60-build 1060works
##  Laptop: E6520   FW 7.1.4-build  1068works
##  Laptop: E6430  FW 8.0.1-build  1399works
##  Laptop: M4700FW 8.1.40-build 1416works

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1331214

Title:
  MAAS (amttool) cannot control AMT version  8

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1331214/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1363719] Re: efibootmgr may create a duplicated boot entry, breaking UEFI boot.

2015-01-28 Thread Mark W Wenning

** Also affects: grub2 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1363719

Title:
  efibootmgr may create a duplicated boot entry, breaking UEFI boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1363719/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1413020] Re: [Hyper-V] IP injection adds the line “# The following stanza(s) added by hv_set_ifconfig” for every pass.

2015-01-23 Thread Mark W Wenning

Mike Schroeder and I verified that the script attached by Andy in #2
fixes the problem.  Thanks Andy.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413020

Title:
  [Hyper-V] IP injection adds  the line “# The following stanza(s) added
  by hv_set_ifconfig” for every pass.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413020/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1359980] Re: [Hyper-V] Unable to perform a full kernel crash on Ubuntu 14.10

2015-01-20 Thread Mark W Wenning

Fix for this needs to be decided by the kexec-tools team, moving over
there.

** Package changed: linux (Ubuntu) = kexec-tools (Ubuntu)

** Changed in: kexec-tools (Ubuntu)
 Assignee: Andy Whitcroft (apw) = (unassigned)

** Changed in: kexec-tools (Ubuntu Utopic)
 Assignee: Andy Whitcroft (apw) = (unassigned)

** Changed in: kexec-tools (Ubuntu)
   Status: In Progress = New

** Changed in: kexec-tools (Ubuntu Utopic)
   Status: In Progress = New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1359980

Title:
  [Hyper-V] Unable to perform a full kernel crash on Ubuntu 14.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kexec-tools/+bug/1359980/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1413020] [NEW] [Hyper-V] IP injection adds the line “# The following stanza(s) added by hv_set_ifconfig” for every pass.

2015-01-20 Thread Mark W Wenning

Public bug reported:

This is new bug branched off Bug
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360580

The IP injection problem has been fixed, but a small problem remains:
 
There is one small glitch in how hv_set_ifconfig runs, as after several runs it 
keeps adding the line “# The following stanza(s) added by hv_set_ifconfig” for 
every pass.

This is the setip execution output:
PS C:\Users\Administrator\Desktop .\setip.ps1
-
SetGuestNetworkAdapterConfiguration
-

Msvm_GuestNetworkAdapterConfiguration before update .. please make sure
that VM is running ...

IPAddresses: : {10.100.20.108, fe80::215:5dff:fe01:6c76}
ProtocolIFType: : 4098
DHCPEnabled: : True
InstanceID: : 
Microsoft:GuestNetwork\9ADF60A7-E268-4039-88B0-372D3F2703D1\1A2B0CAB-5074-4551-88A8-EE39EC094A26
Subnets: : {255.255.255.0, /64}
DNSServers: : {8.8.8.8}
DefaultGateways: : {10.100.20.1}

SetGuestNetworkAdapterConfiguration
SetGuestNetworkAdapterConfiguration success.
Msvm_GuestNetworkAdapterConfiguration After update .. please make sure VM is 
running ...
IPAddresses: : {10.100.20.208, fe80::215:5dff:fe01:6c76}
ProtocolIFType: : 4098
DHCPEnabled: : False
InstanceID: : 
Microsoft:GuestNetwork\9ADF60A7-E268-4039-88B0-372D3F2703D1\1A2B0CAB-5074-4551-88A8-EE39EC094A26
Subnets: : {255.0.0.0, /64}
DNSServers: : {8.8.8.8, 8.8.4.4}
DefaultGateways: : {10.100.20.1}

Sample interfaces file content after running the script 3 times:

root@ubuntu1410:~# cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
# The following stanza(s) added by hv_set_ifconfig
# The following stanza(s) added by hv_set_ifconfig
# The following stanza(s) added by hv_set_ifconfig
auto eth0
iface eth0 inet static
address 10.100.20.108
gateway 10.100.20.1
dns-nameservers 8.8.4.4

#End of hv_set_ifconfig stanzas

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1413020

Title:
  [Hyper-V] IP injection adds  the line “# The following stanza(s) added
  by hv_set_ifconfig” for every pass.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413020/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1360580] Re: [Hyper-V] IP injection does not occur on Ubuntu 14.10

2015-01-20 Thread Mark W Wenning

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1413020 has been
opened to deal with the stanza problem.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1360580

Title:
  [Hyper-V] IP injection does not occur on Ubuntu 14.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360580/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1360580] Re: [Hyper-V] IP injection does not occur on Ubuntu 14.10

2015-01-20 Thread Mark W Wenning

IP Injecting testing was successful using the released Ubuntu 14.10 x64 .iso.  
The remaining issue is the stanza issue pointed out in Abhishek’s response #13. 
 I will open a new bug to deal with this.  

** Changed in: linux (Ubuntu)
   Status: In Progress = Fix Released

** Changed in: linux (Ubuntu Utopic)
   Status: In Progress = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1360580

Title:
  [Hyper-V] IP injection does not occur on Ubuntu 14.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1360580/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1301019] Re: hyper-v: ifdown command not working due to bad ifstate

2015-01-07 Thread Mark W Wenning

Bug is stale, marked invalid at Microsoft's request

** Changed in: linux (Ubuntu)
   Status: Confirmed = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301019

Title:
  hyper-v: ifdown command not working due to bad ifstate

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301019/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1311070] Re: hyper-v:IP Injection on Ubuntu 13.10 guest during Failover and Test Failover is corrupting the existing entries

2015-01-07 Thread Mark W Wenning

Stale bug, closed out at Microsoft's request.

** Changed in: linux (Ubuntu)
   Status: Confirmed = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311070

Title:
  hyper-v:IP Injection on Ubuntu 13.10 guest during Failover and Test
  Failover is corrupting the existing entries

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1311070/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1379926] Re: gedit crashed with signal 5 in _XReply()

2014-12-15 Thread Mark W Wenning

The fix in #1376494 seems to work for me:

 sudo apt-get install ibus-gtk
log out/in

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1379926

Title:
  gedit crashed with signal 5 in _XReply()

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/1379926/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1285977] Re: Ubuntu 14.04 daily build crash after install

2014-12-10 Thread Mark W Wenning

Doesn't apply anymore, marking invalid

** Changed in: compiz (Ubuntu)
   Status: Confirmed = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1285977

Title:
  Ubuntu 14.04 daily build crash after install

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1285977/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider

2014-11-22 Thread Mark W Wenning

I'm seeing the same error on my hardware MAAS cluster with the latest
maas stable and juju stable .   Failing bridge on the bootstrap node is
called juju-br0.   I will post more info on Monday.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1271144

Title:
  br0 not brought up by cloud-init script with MAAS provider

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1271144] Re: br0 not brought up by cloud-init script with MAAS provider

2014-11-22 Thread Mark W Wenning

I'm seeing the same error on my hardware MAAS cluster with the latest
maas stable and juju stable .   Failing bridge on the bootstrap node is
called juju-br0.   I will post more info on Monday.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1271144

Title:
  br0 not brought up by cloud-init script with MAAS provider

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju-core/+bug/1271144/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1321885] Re: IPMI detection and automatic setting fail in ubuntu 14.04 maas

2014-11-19 Thread Mark W Wenning

Verified that the fix works on Dell PowerEdge R805 .

maas 1.7.0+bzr3299-0ubuntu1~trusty

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openipmi in Ubuntu.
https://bugs.launchpad.net/bugs/1321885

Title:
  IPMI detection and automatic setting fail in ubuntu 14.04 maas

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1321885/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1321885] Re: IPMI detection and automatic setting fail in ubuntu 14.04 maas

2014-11-19 Thread Mark W Wenning

Verified that the fix works on Dell PowerEdge R805 .

maas 1.7.0+bzr3299-0ubuntu1~trusty

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1321885

Title:
  IPMI detection and automatic setting fail in ubuntu 14.04 maas

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1321885/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1216059] Re: Firefox difficulties with https and IPv6 addresses

2014-09-25 Thread Mark W Wenning

** Changed in: dell-poweredge
 Assignee: Kent Baxley (kentb) = Mark W Wenning (mwenning)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1216059

Title:
  Firefox difficulties with https and IPv6 addresses

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1216059/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1370368] Re: Failed to install Ubuntu 14.04.1 LTS on Dell C6220

2014-09-17 Thread Mark W Wenning

I tried it here on a C6220 in the Dell lab and found the same thing.
The tar'ed var/log dir is attached.

Notes:

##  BIOS boot, not UEFI 
##  ubuntu-14.04.1-server-amd64.iso  - usb disk 
##  Add a second disk to array, hit ctl-I on way up and set up RAID1 array
##  - exit, status of RAID1 disk is Rebuild
##  Trusty Server install disk finds the raid 1 and seems to ask the right 
questions.  
##  Nope.  fails to boot.  ctl-alt-delete, reboot
##  f11 to boot to usb drive  (note:  raid1 comes up with degraded status)
walk thru standard stuff (keyboard, network, hostname, login, encrypt home?, 
ntp, etc) until:
One or more drives containing MDADM containers (Intel/DDF RAID) have been 
found.  
Do you wish to acivate these RAID devices?
##  say yes
ne or more drives containing Serial ATA RAID configurations have been found.  
Do you wish to acivate these RAID devices?
##  say yes
##  partitioner will come up with guided - use entire disk and set up LVM

https://help.ubuntu.com/12.04/serverguide/advanced-installation.html
## select Manual, follow above directions, still will not boot into hd
##  at some point it asks where to install grub, select default
grub-install /dev/md126p1  

## reboot, hangs, doesn't even seem to get to grub

** Attachment added: tar file of var/log dir on /dev/md126p1
   
https://bugs.launchpad.net/ubuntu/+bug/1370368/+attachment/4206853/+files/logs.tgz

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1370368

Title:
  Failed to install Ubuntu 14.04.1 LTS on Dell C6220

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1370368/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349920] Re: ledmon does not work in Ubuntu 14.04

2014-09-03 Thread Mark W Wenning

** Changed in: dell-poweredge
   Status: Fix Committed = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349920

Title:
  ledmon does not work in Ubuntu 14.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1349920/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1301019] Re: hyper-v: ifdown command not working due to bad ifstate

2014-08-26 Thread Mark W Wenning

Abishek, can you give more information on how to duplicate this problem? 
What I did was: 
Installed ubuntu-14.04.1-server-amd64.iso as a VM under Hyper-V (Windows Server 
2008R2SP1)
Installed  linux-cloud-tools-3.13.0-32-generic

hv_set_ifconfig seems to work OK.
/run/network/ifstate  seems to contain the correct information.

If you could let me know what environment you are using, where and how
you got the disk image, etc. I think we could dig into it deeper.

Thanks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1301019

Title:
  hyper-v: ifdown command not working due to bad ifstate

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1301019/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1349920] Re: ledmon does not work in Ubuntu 14.04

2014-08-05 Thread Mark W Wenning

Verified on Dell Poweredge R820 .

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1349920

Title:
  ledmon does not work in Ubuntu 14.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1349920/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

73 matches

Mail list logo