from:"jeffrey leung"

[Bug 1859099] Re: BUG: unable to handle kernel paging request at fffffe000010fff8

2020-01-10 Thread jeffrey leung via ubuntu-bugs

They are running Intel Xeon Gold 5120 CPU so will recommend that as
well, thanks.

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

Title:
  BUG: unable to handle kernel paging request at fe10fff8

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

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

[Bug 1859099] Re: BUG: unable to handle kernel paging request at fffffe000010fff8

2020-01-10 Thread jeffrey leung via ubuntu-bugs

Thanks for the recommendation. Thought the same but wanted to be sure
that would be recommended POA for this. Will forward to customer and
work with them.

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

Title:
  BUG: unable to handle kernel paging request at fe10fff8

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

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

[Bug 1859099] [NEW] BUG: unable to handle kernel paging request at fffffe000010fff8

2020-01-09 Thread jeffrey leung via ubuntu-bugs

Public bug reported:

I have a customer running a cluster of servers on Ubuntu 16.04.1, kernel
4.15.0-43-generic. Two of the nodes on separate occasions experienced
kernel OOPS on Dec 21st and Dec 26th with similar call trace messaging:

Dec 21 10:18:27.200 node1 kernel: [1179506.273413] BUG: unable to handle kernel 
paging request at fe10fff8
Dec 21 10:18:27.200 node1 kernel: [1179506.273520] IP: 
__do_page_fault+0x4f/0x500
Dec 21 10:18:27.200 node1 kernel: [1179506.273571] PGD 123ffca067 P4D 
123ffca067 PUD 123ffc8067 PMD 123ffc7067 PTE 80123fd89163
Dec 21 10:18:27.200 node1 kernel: [1179506.273665] Oops:  [#1] SMP NOPTI
Dec 21 10:18:27.200 node1 kernel: [1179506.273712] Modules linked in: tcp_diag 
inet_diag nfsv3 rpcsec_gss_krb5 nfsv4 btrfs zstd_compress ufs msdos xfs 
vmw_vsock_vmci_transport vsock dm_crypt xt_nat iptable_nat nf_nat_ipv4 nf_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 xt_tcpudp xt_owner xt_conntrack nf_conntrack 
iptable_filter ip_tables x_tables vmw_balloon crct10dif_pclmul crc32_pclmul 
ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd 
joydev input_leds serio_raw cdc_ether usbnet mii vmw_vmci nfsd auth_rpcgss 
nfs_acl nfs lockd grace sunrpc fscache vmd(OE) raid10 raid456 async_raid6_recov 
async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 
multipath linear hid_generic usbhid hid psmouse vmxnet3 mpt3sas(OE) ahci mptspi 
e1000 scsi_transport_spi libahci raid_class scsi_transport_sas mptscsih mptbase
Dec 21 10:18:27.200 node1 kernel: [1179506.274426] CPU: 6 PID: 12457 Comm: 
AIOGRP0 Comp Tainted: G   OE4.15.0-43-generic #46~16.04.1-Ubuntu
Dec 21 10:18:27.200 node1 kernel: [1179506.274530] Hardware name: VMware, Inc. 
VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 09/19/2018
Dec 21 10:18:27.200 node1 kernel: [1179506.274640] RIP: 
0010:__do_page_fault+0x4f/0x500
Dec 21 10:18:27.200 node1 kernel: [1179506.274696] RSP: :aff89186b040 
EFLAGS: 00010046
Dec 21 10:18:27.200 node1 kernel: [1179506.274763] RAX: 91392d884ab0 RBX: 
 RCX: ae2009e7
Dec 21 10:18:27.201 node1 kernel: [1179506.274850] RDX: af13b740 RSI: 
 RDI: aff89186b0e8
Dec 21 10:18:27.201 node1 kernel: [1179506.274935] RBP: aff89186b0a8 R08: 
 R09: 
Dec 21 10:18:27.201 node1 kernel: [1179506.275024] R10:  R11: 
 R12: aff89186b0e8
Dec 21 10:18:27.201 node1 kernel: [1179506.275109] R13: af13b740 R14: 
91392d884a40 R15: 
Dec 21 10:18:27.201 node1 kernel: [1179506.275212] FS:  7f09ebb6a700() 
GS:91397fd8() knlGS:
Dec 21 10:18:27.201 node1 kernel: [1179506.275308] CS:  0010 DS:  ES:  
CR0: 80050033
Dec 21 10:18:27.201 node1 kernel: [1179506.275376] CR2: fe10fff8 CR3: 
0011e6376002 CR4: 003606e0
Dec 21 10:18:27.201 node1 kernel: [1179506.275510] DR0:  DR1: 
 DR2: 
Dec 21 10:18:27.201 node1 kernel: [1179506.275607] DR3:  DR6: 
fffe0ff0 DR7: 0400
Dec 21 10:18:27.201 node1 kernel: [1179506.275692] Call Trace:
Dec 21 10:18:27.201 node1 kernel: [1179506.275749]  do_page_fault+0x2e/0xf0
Dec 21 10:18:27.201 node1 kernel: [1179506.275807]  page_fault+0x25/0x50
Dec 21 10:18:27.201 node1 kernel: [1179506.275857] RIP: 
0010:__do_page_fault+0x4f/0x500
Dec 21 10:18:27.201 node1 kernel: [1179506.275918] RSP: :aff89186b190 
EFLAGS: 00010046
Dec 21 10:18:27.201 node1 kernel: [1179506.275982] RAX: 91392d884ab0 RBX: 
 RCX: ae2009e7
Dec 21 10:18:27.201 node1 kernel: [1179506.276068] RDX: af13b740 RSI: 
 RDI: aff89186b238
Dec 21 10:18:27.201 node1 kernel: [1179506.276154] RBP: aff89186b1f8 R08: 
 R09: 
Dec 21 10:18:27.201 node1 kernel: [1179506.276240] R10:  R11: 
 R12: aff89186b238
Dec 21 10:18:27.201 node1 kernel: [1179506.276327] R13: af13b740 R14: 
91392d884a40 R15: 
Dec 21 10:18:27.201 node1 kernel: [1179506.276415]  ? native_iret+0x7/0x7
Dec 21 10:18:27.202 node1 kernel: [1179506.276479]  do_page_fault+0x2e/0xf0
Dec 21 10:18:27.202 node1 kernel: [1179506.276530]  page_fault+0x25/0x50
Dec 21 10:18:27.202 node1 kernel: [1179506.276578] RIP: 
0010:__do_page_fault+0x4f/0x500
Dec 21 10:18:27.202 node1 kernel: [1179506.276639] RSP: :aff89186b2e0 
EFLAGS: 00010046
Dec 21 10:18:27.202 node1 kernel: [1179506.276702] RAX: 91392d884ab0 RBX: 
 RCX: ae2009e7
Dec 21 10:18:27.202 node1 kernel: [1179506.276789] RDX: af13b740 RSI: 
 RDI: aff89186b388
Dec 21 10:18:27.202 node1 kernel: [1179506.276873] RBP: aff89186b348 R08: 
 R09: 
Dec 21 10:18:27.202 node1 kernel: [1179506.276961] R10:

[Bug 1768667] [NEW] bionic amd64 choose-mirror still pointing to artful

2018-05-02 Thread jeffrey leung

Public bug reported:

I downloaded the latest live-server iso for Ubuntu 18.04 server amd64. I
am trying to setup unattended PXE boot but running into an issue when
trying to reach the remote mirror. I looked at the syslog and the
choose-mirror package still seems to be trying to point to
/dists/artful/Release instead of bionic:

May  2 00:01:05 choose-mirror[3603]: WARNING **: broken mirror: invalid Suite 
or Codename in Release file for artful
May  2 00:01:07 choose-mirror[3603]:DEBUG: command: wget --no-verbose 
http://172.100.1.1/os/linux/ubuntu/18/ubuntu-18.04-ga/dists/artful/Release -0 - 
| grep -E'^(Suite|Codename|Architectures):'

** Affects: choose-mirror (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/1768667

Title:
  bionic amd64 choose-mirror still pointing to artful

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/choose-mirror/+bug/1768667/+subscriptions

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

[Bug 1661131] Re: kernel crash when NVMe drive inserted in one slot

2017-03-10 Thread jeffrey leung

Got it working 2nd try, enabling -proposed in Xenial resolved the issue.

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

Title:
  kernel crash when NVMe drive inserted in one slot

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

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

[Bug 1661131] Re: kernel crash when NVMe drive inserted in one slot

2017-03-08 Thread jeffrey leung

May have spoken too soon, found server went into a kernel panic after I
got back from lunch. There's some complaints about the controller so I
am going to try the 4.4.47 kernel again to be sure it's not the
hardware.

Is there anything that needs to be ran besides "apt-get update" after
enabling proposed? What can I run to be sure the fix was applied after
enabling -proposed?

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

Title:
  kernel crash when NVMe drive inserted in one slot

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

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

[Bug 1661131] Re: kernel crash when NVMe drive inserted in one slot

2017-03-08 Thread jeffrey leung

Sorry for the delay, had to wait for another issue to be debugged before
I could take over the hardware again. I enabled -proposed and performed
an apt-get update and fix is working.

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

Title:
  kernel crash when NVMe drive inserted in one slot

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

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

[Bug 1661131] Re: kernel crash when NVMe drive inserted in one slot

2017-02-22 Thread jeffrey leung

v4.4.47 kernel has the fix and is working with the NVMe drive in the
"bad" slot.

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

Title:
  kernel crash when NVMe drive inserted in one slot

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

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

[Bug 1661131] Re: kernel crash when NVMe drive inserted in one slot

2017-02-21 Thread jeffrey leung

I was able to git clone the v4.4.47 kernel over to the machine having
issues. When trying to apply the patches after 0001, it's unable to
locate the file to patch for some. I am seeing this same error on
another machine I've previously successfully upgraded to the 4.4.47
kernel with the same files.

root@savbu-qa-colusa3-24-2:~# patch -p1 < 
0002-UBUNTU-SAUCE-add-vmlinux.strip-to-BOOT_TARGETS1-on-p.patch
can't find file to patch at input line 16
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--
|From 87f65999aab113d4ecf0d7fedfa5a4cc9c1141b5 Mon Sep 17 00:00:00 2001
|From: Andy Whitcroft 
|Date: Fri, 9 Sep 2016 14:02:29 +0100
|Subject: [PATCH 2/6] UBUNTU: SAUCE: add vmlinux.strip to BOOT_TARGETS1 on
| powerpc
|
|Signed-off-by: Andy Whitcroft 
|---
| arch/powerpc/Makefile | 2 +-
| 1 file changed, 1 insertion(+), 1 deletion(-)
|
|diff --git a/arch/powerpc/Makefile b/arch/powerpc/Makefile
|index 96efd82..96f49dd 100644
|--- a/arch/powerpc/Makefile
|+++ b/arch/powerpc/Makefile
--
File to patch: ^C
root@savbu-qa-colusa3-24-2:~#


root@savbu-qa-colusa3-24-2:~# patch -p1 < 
0003-UBUNTU-SAUCE-tools-hv-lsvmbus-add-manual-page.patch
patching file tools/hv/lsvmbus.8


root@savbu-qa-colusa3-24-2:~# patch -p1 < 
0004-UBUNTU-SAUCE-no-up-disable-pie-when-gcc-has-it-enabl.patch
can't find file to patch at input line 37
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--
|From 5d5e1ec9dcd36f965aee2285f678b7fcc3553c2f Mon Sep 17 00:00:00 2001
|From: Steve Beattie 
|Date: Tue, 10 May 2016 12:44:04 +0100
|Subject: [PATCH 4/6] UBUNTU: SAUCE: (no-up) disable -pie when gcc has it
| enabled by default
|
|In Ubuntu 16.10, gcc's defaults have been set to build Position
|Independent Executables (PIE) on amd64 and ppc64le (gcc was configured
|this way for s390x in Ubuntu 16.04 LTS). This breaks the kernel build on
|amd64. The following patch disables pie for x86 builds (though not yet
|verified to work with gcc configured to build PIE by default i386 --
|we're not planning to enable it for that architecture).
|
|The intent is for this patch to go upstream after expanding it to
|additional architectures where needed, but I wanted to ensure that
|we could build 16.10 kernels first. I've successfully built kernels
|and booted them with this patch applied using the 16.10 compiler.
|
|Patch is against yakkety.git, but also applies with minor movement
|(no fuzz) against current linus.git.
|
|Signed-off-by: Steve Beattie 
|[a...@canonical.com: shifted up so works in arch/http://bugs.launchpad.net/bugs/1574982
|Signed-off-by: Andy Whitcroft 
|Acked-by: Tim Gardner 
|Acked-by: Stefan Bader 
|Signed-off-by: Kamal Mostafa 
|---
| Makefile | 6 ++
| 1 file changed, 6 insertions(+)
|
|diff --git a/Makefile b/Makefile
|index 7b233ac..3c6e704 100644
|--- a/Makefile
|+++ b/Makefile
--
File to patch:

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

Title:
  kernel crash when NVMe drive inserted in one slot

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

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

[Bug 1661131] Re: kernel crash when NVMe drive inserted in one slot

2017-02-17 Thread jeffrey leung

Hi Joseph,

To confirm, in order to correctly install the v4.4.47 kernel, we need to
do the git clone and apply the patches before installing the kernel .deb
packages correct? My colleague was only copying the .deb packages which
may be causing us to see the root device timeout. I was able to
successfully install v4.4.47 kernel in my own environment following the
instructions you provided with no issues.

Thanks,
Jeff

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

Title:
  kernel crash when NVMe drive inserted in one slot

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

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

[Bug 1661131] Re: kernel crash when NVMe drive inserted in one slot

2017-02-08 Thread jeffrey leung

We tried with the 4.4.47 kernel but when booting it gives up waiting on
the root device. We are troubleshooting to try and get it to boot.

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

Title:
  kernel crash when NVMe drive inserted in one slot

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

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

[Bug 1661131] Re: kernel crash when NVMe drive inserted in one slot

2017-02-07 Thread jeffrey leung

** Tags added: kernel-fixed-upstream

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

Title:
  kernel crash when NVMe drive inserted in one slot

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

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

[Bug 1661131] Re: kernel crash when NVMe drive inserted in one slot

2017-02-06 Thread jeffrey leung

The mainline kernel seems to have resolved the issue so far. We're
running some IO just to make sure it's stable. I will update the tag
once we have confirmation.

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

Title:
  kernel crash when NVMe drive inserted in one slot

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

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

[Bug 1661131] Re: kernel crash when NVMe drive inserted in one slot

2017-02-02 Thread jeffrey leung

I've asked the engineer to try the latest v4.10-rc6 kernel. This is
their first test with 16.04.1, so unknown if it works with previous
kernel version. I've asked them to check older versions to see if it
exists.

I'll update the tag and comment when I hear back from them. Thanks for
the recommendation.

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

Title:
  kernel crash when NVMe drive inserted in one slot

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

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

[Bug 1661131] [NEW] kernel crash when NVMe drive inserted in one slot

2017-02-01 Thread jeffrey leung

Public bug reported:

Opening this on behalf of one of my colleagues at Cisco, we're seeing an
issue on our new S-series S3260 server that's causing the kernel to
crash.

If we have an NVMe device inserted into one of two drive slots, we will
see kernel crash only with Ubuntu. With an NVMe drive in the bad slot,
other OS's will work fine. If we move the NVMe drive out of the bad slot
and into the other slot, everything is working fine as expected. We only
see the kernel crash with an NVMe drive in that bad slot when using
Ubuntu. We tested with HGST and Intel NVMe drives and were able to
reproduce the issue with both. HGST reviewed some logs and they don't
believe at this time the issue is with the NVMe drives.

We're hoping someone from Canonical can take a look to understand what
is the difference between the working and failing slot. The data
collection was done with the NVMe drive inserted in the working slot so
we could access the OS.

I had a connection time out when trying to use ubuntu-bug, so I saved
the apport file and will attach to the bug. I have collected the kernel
and syslog as well, but they are ~9GB. I found a call trace in the
kernel log start on Jan 25 06:02:54 and floods the logs afterwards. I
will include the call trace in a separate text file on the attachment.

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

** Attachment added: "contains apport, call trace, lspci, uname, version_sig"
   
https://bugs.launchpad.net/bugs/1661131/+attachment/4811959/+files/colusa2bug.zip

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

Title:
  kernel crash when NVMe drive inserted in one slot

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

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

[Bug 1655437] Re: 16.04 fails to boot with kernel 4.4.0-22-generic

2017-01-12 Thread jeffrey leung

Thanks Joseph, it's working fine. We can close this out, I don't see a
point in pushing to get this specific kernel issue with 4.4.0-22
resolved by Canonical. I'll work with my manager to get the bug closed
out on our end internally.

Should I set this to won't fix or invalid?

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

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

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

[Bug 1655437] Re: 16.04 fails to boot with kernel 4.4.0-22-generic

2017-01-11 Thread jeffrey leung

I ran apport-collect after booting up with the 4.4.0-21-generic kernel.
I was not able to boot into the OS with the 4.4.0-22-generic kernel to
run the command.

When boot fails and it drops to shell, it doesn't appear to be accepting
keyboard input. I found some old issues with USB drivers not being
installed yet but they are pretty old. Digging deeper into that
information to see if I can recover and boot into 16.04 with
4.4.0-22-generic kernel.

** 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/1655437

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

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

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

[Bug 1655437] Lspci.txt

2017-01-10 Thread jeffrey leung

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1655437/+attachment/4802610/+files/Lspci.txt

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

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

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

[Bug 1655437] ProcCpuinfo.txt

2017-01-10 Thread jeffrey leung

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1655437/+attachment/4802611/+files/ProcCpuinfo.txt

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

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

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

[Bug 1655437] CurrentDmesg.txt

2017-01-10 Thread jeffrey leung

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1655437/+attachment/4802608/+files/CurrentDmesg.txt

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

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

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

[Bug 1655437] ProcInterrupts.txt

2017-01-10 Thread jeffrey leung

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1655437/+attachment/4802612/+files/ProcInterrupts.txt

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

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

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

[Bug 1655437] UdevDb.txt

2017-01-10 Thread jeffrey leung

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1655437/+attachment/4802614/+files/UdevDb.txt

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

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

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

[Bug 1655437] WifiSyslog.txt

2017-01-10 Thread jeffrey leung

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1655437/+attachment/4802615/+files/WifiSyslog.txt

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

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

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

[Bug 1655437] ProcModules.txt

2017-01-10 Thread jeffrey leung

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1655437/+attachment/4802613/+files/ProcModules.txt

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

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

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

[Bug 1655437] Re: 16.04 fails to boot with kernel 4.4.0-22-generic

2017-01-10 Thread jeffrey leung

apport information

** Tags added: apport-collected xenial

** Description changed:

  During ENIC driver development on our end, there was a mistake and the
  driver was built on the 4.4.0-22-generic kernel but we intended it to be
  on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when
  testing the ENIC driver, it required a kernel upgrade and afterwards we
  found it wasn't able to boot due to some volume group issues it appears
  from the error messages.
  
  We fixed the driver issue on our end to target the correct inbox kernel
  version and it's working fine. We also haven't seen any issues with
  16.04 and newer kernels. However, management is still concerned about
  the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is it
  possible to look into this issue? Or maybe would it be possible to get
  that kernel version removed from the package so a customer doesn't
  upgrade to that kernel after an offline install?
  
  I am able to replicate the issue easily by doing an offline install of
  16.04 so the kernel does not get automatically upgraded, then upgrading
  to 4.4.0-22-generic and rebooting after install.
  
  1. If I install 16.04 with auto partitioning, after updating the kernel
  to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found errors.
  I’ve attached ubuntu.jpg for this.
  
  2. If I install 16.04 with manual partitioning, I don’t see the vg not
  found, but OS still fails to boot and goes to shell. I’ve attached
  ubuntu2.jpg for this.
  
  Thanks,
  Jeff
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2
+ Architecture: amd64
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=545c0ff1-8be4-4ca3-95ad-7e971f832aba
+ InstallationDate: Installed on 2017-01-10 (0 days ago)
+ InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
+ IwConfig:
+  enp138s0  no wireless extensions.
+  
+  enp133s0  no wireless extensions.
+  
+  lono wireless extensions.
+ Lsusb:
+  Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and 
Mouse
+  Bus 002 Device 002: ID 8087:8002 Intel Corp. 
+  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+  Bus 001 Device 002: ID 8087:800a Intel Corp. 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: Cisco Systems Inc UCSB-B420-M4
+ Package: linux (not installed)
+ ProcEnviron:
+  LANGUAGE=en_US
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 VESA VGA
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=9c7d131f-2177-40d2-8418-f8581a8d4ef5 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
+ PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
+ RelatedPackageVersions:
+  linux-restricted-modules-4.4.0-21-generic N/A
+  linux-backports-modules-4.4.0-21-generic  N/A
+  linux-firmware1.157
+ RfKill:
+  
+ Tags:  xenial
+ Uname: Linux 4.4.0-21-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups:
+  
+ _MarkForUpload: True
+ dmi.bios.date: 11/07/2016
+ dmi.bios.vendor: Cisco Systems, Inc.
+ dmi.bios.version: B420M4.3.1.2f.0.110720161154
+ dmi.board.name: UCSB-B420-M4
+ dmi.board.vendor: Cisco Systems Inc
+ dmi.board.version: 73-16458-06
+ dmi.chassis.type: 18
+ dmi.chassis.vendor: Cisco Systems Inc
+ dmi.chassis.version: 68-4777-02
+ dmi.modalias: 
dmi:bvnCiscoSystems,Inc.:bvrB420M4.3.1.2f.0.110720161154:bd11/07/2016:svnCiscoSystemsInc:pnUCSB-B420-M4:pvr03:rvnCiscoSystemsInc:rnUCSB-B420-M4:rvr73-16458-06:cvnCiscoSystemsInc:ct18:cvr68-4777-02:
+ dmi.product.name: UCSB-B420-M4
+ dmi.product.version: 03
+ dmi.sys.vendor: Cisco Systems Inc

** Attachment added: "AlsaInfo.txt"
   
https://bugs.launchpad.net/bugs/1655437/+attachment/4802606/+files/AlsaInfo.txt

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

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

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

[Bug 1655437] JournalErrors.txt

2017-01-10 Thread jeffrey leung

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1655437/+attachment/4802609/+files/JournalErrors.txt

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

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

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

[Bug 1655437] CRDA.txt

2017-01-10 Thread jeffrey leung

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1655437/+attachment/4802607/+files/CRDA.txt

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

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

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

[Bug 1655437] Re: 16.04 fails to boot with kernel 4.4.0-22-generic

2017-01-10 Thread jeffrey leung

** Package changed: ubuntu => 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/1655437

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

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

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

[Bug 1655437] Re: 16.04 fails to boot with kernel 4.4.0-22-generic

2017-01-10 Thread jeffrey leung

** Attachment added: "error with manual partitioning"
   
https://bugs.launchpad.net/ubuntu/+bug/1655437/+attachment/4802496/+files/ubuntu2.jpg

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

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

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

[Bug 1655437] [NEW] 16.04 fails to boot with kernel 4.4.0-22-generic

2017-01-10 Thread jeffrey leung

Public bug reported:

During ENIC driver development on our end, there was a mistake and the
driver was built on the 4.4.0-22-generic kernel but we intended it to be
on the inbox kernel with 16.04 which is 4.4.0-21-generic. So when
testing the ENIC driver, it required a kernel upgrade and afterwards we
found it wasn't able to boot due to some volume group issues it appears
from the error messages.

We fixed the driver issue on our end to target the correct inbox kernel
version and it's working fine. We also haven't seen any issues with
16.04 and newer kernels. However, management is still concerned about
the issue with 16.04 xenial xerus at 4.4.0-22-generic kernel. Is it
possible to look into this issue? Or maybe would it be possible to get
that kernel version removed from the package so a customer doesn't
upgrade to that kernel after an offline install?

I am able to replicate the issue easily by doing an offline install of
16.04 so the kernel does not get automatically upgraded, then upgrading
to 4.4.0-22-generic and rebooting after install.

1. If I install 16.04 with auto partitioning, after updating the kernel
to 4.4.0-22-generic and rebooting, I see ubuntu-vg not found errors.
I’ve attached ubuntu.jpg for this.

2. If I install 16.04 with manual partitioning, I don’t see the vg not
found, but OS still fails to boot and goes to shell. I’ve attached
ubuntu2.jpg for this.

Thanks,
Jeff

** Affects: ubuntu
 Importance: Undecided
 Status: New

** Attachment added: "ubuntu-vg not found"
   https://bugs.launchpad.net/bugs/1655437/+attachment/4802495/+files/ubuntu.jpg

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

Title:
  16.04 fails to boot with kernel 4.4.0-22-generic

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

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

[Bug 1616258] Re: Ubuntu 16.04 server PXE installs correctly but loads to a blank screen instead of login

2016-08-23 Thread jeffrey leung

** Package changed: xorg (Ubuntu) => grub-installer (Ubuntu)

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

Title:
  Ubuntu 16.04 server PXE installs correctly but loads to a blank screen
  instead of login

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

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

[Bug 1616258] [NEW] Ubuntu 16.04 server PXE installs correctly but loads to a blank screen instead of login

2016-08-23 Thread jeffrey leung

Public bug reported:

When trying to do a PXE install for Ubuntu 16.04 and 16.04.1 server
version, after OS install is complete and the machine reboots the OS
loads into a blank screen instead of a login prompt. The screen stays
blank and does not respond to key or mouse input. If I try Alt + F1-F6,
I am able to open a terminal and see a login prompt.

We do have a workaround for this. I was looking up similar symptoms on
the forums and found issues with NVIDIA drivers and found this
fix:http://askubuntu.com/questions/383636/12-04-3-can-start-only-after-
press-resume-in-rescue-mode-every-boot-proble/391608#391608

I edited the /etc/default/grub file and edited the
GRUB_CMDLINE_LINUX_DEFAULT and added the "nomodeset" to the end at first
and ran update-grub which did not work. I removed the "nomodeset" as
well as the "quiet splash" and updated the grub. After disabling the
boot splash screen and reboot, the OS boots up fine and is working as
expected.

We also found another workaround by adding lines to disable the boot splash 
screen in the preseed:
# No boot splash screen.
d-i debian-installer/quiet boolean false
d-i debian-installer/splash boolean false

** Affects: xorg (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/1616258

Title:
  Ubuntu 16.04 server PXE installs correctly but loads to a blank screen
  instead of login

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

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

[Bug 1578022] Re: dmidecode fails to output smibios 3.0 info

2016-05-18 Thread jeffrey leung

Hi Adam, after enabling -proposed and installing the
dmidecode_3.0-2ubuntu0.1 package, it resolved the dmidecode issue.

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

Title:
  dmidecode fails to output smibios 3.0 info

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

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

[Bug 1575652] Re: PXE install prefixes /cdrom to squashfs location, fails to find it

2016-05-12 Thread jeffrey leung

I am also running into this issue with the added /cdrom prefixed to the
url with 16.04 image.

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

Title:
  PXE install prefixes /cdrom to squashfs location, fails to find it

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

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

[Bug 1580949] Re: Trusty: 1024x768 resolution not available to connect to Cisco KVM

2016-05-12 Thread jeffrey leung

xorg.conf file edit

** Attachment added: "xorg.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1580949/+attachment/4661205/+files/xorg.png

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

Title:
  Trusty: 1024x768 resolution not available to connect to Cisco KVM

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

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

[Bug 1580949] [NEW] Trusty: 1024x768 resolution not available to connect to Cisco KVM

2016-05-12 Thread jeffrey leung

Public bug reported:

1024x768 resolution is not available by default in Ubuntu Trusty when
connecting to Cisco KVM. It works fine with RHEL 6.5 (xorg-xserver
x1.13.0) and SLES 11.4 (xorg-xserver v1.6.5).

The workaround to enable display in Ubuntu Trusty is:
1. Stop lightdm (service lightdm stop)
2. Generate an xorg.conf file. Item #54 you need to add -> Modes "1024x768" 
(will attach screenshot in comments)
3. Copy the file to /etc
4. Start lightdm again (service lightdm start)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.19.0-25.26~14.04.1-generic 3.19.8-ckt2
Uname: Linux 3.19.0-25-generic x86_64
.tmp.unity.support.test.1:
 
ApportVersion: 2.14.1-0ubuntu3.11
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Thu May 12 05:42:15 2016
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DkmsStatus: fwts-efi-runtime-dkms, 16.03.00, 3.19.0-25-generic, x86_64: 
installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Matrox Electronics Systems Ltd. MGA G200e [Pilot] ServerEngines (SEP1) 
[102b:0522] (rev 02) (prog-if 00 [VGA controller])
   Subsystem: Cisco Systems Inc Device [1137:0101]
Lsusb:
 Bus 002 Device 003: ID 0624:0402 Avocent Corp. Cisco Virtual Keyboard and Mouse
 Bus 002 Device 002: ID 8087:8002 Intel Corp. 
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 8087:800a Intel Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Cisco Systems Inc UCSB-B200-M4
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic 
root=UUID=4830d061-2379-455a-acd2-ef982a6b658b ro
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/11/2016
dmi.bios.vendor: Cisco Systems, Inc.
dmi.bios.version: B200M4.3.1.2.4.041120161047
dmi.board.name: UCSB-B200-M4
dmi.board.vendor: Cisco Systems Inc
dmi.board.version: 73-15862-03
dmi.chassis.type: 18
dmi.chassis.vendor: Cisco Systems Inc
dmi.chassis.version: 68-4777-02
dmi.modalias: 
dmi:bvnCiscoSystems,Inc.:bvrB200M4.3.1.2.4.041120161047:bd04/11/2016:svnCiscoSystemsInc:pnUCSB-B200-M4:pvr1:rvnCiscoSystemsInc:rnUCSB-B200-M4:rvr73-15862-03:cvnCiscoSystemsInc:ct18:cvr68-4777-02:
dmi.product.name: UCSB-B200-M4
dmi.product.version: 1
dmi.sys.vendor: Cisco Systems Inc
version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu May 12 05:40:24 2016
xserver.configfile: /etc/xorg.conf
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputAvocent Cisco USB Composite Device-0 KEYBOARD, id 8
 inputAvocent Cisco USB Composite Device-0 TOUCHSCREEN, id 9
 inputAvocent Cisco USB Composite Device-0 MOUSE, id 10
xserver.errors:
 MGA(0): V_BIOS address 0xd00 out of range
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2.7

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu uec-images

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

Title:
  Trusty: 1024x768 resolution not available to connect to Cisco KVM

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

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

[Bug 1578022] Re: dmidecode fails to output smibios 3.0 info

2016-05-10 Thread jeffrey leung

Hi Colin,

We ran into this at Cisco during 16.04 certification, Samantha asked me
to collect the data you requested to see if we can be of any help.

kernel versions:
Ubuntu 16.04: 4.4.0-21-generic
RHEL 7.2: 3.10.0-327.el7.x86_64

I've attached dmi_cisco.rar which will have a screenshot with dmidecode
output same as Samantha's above, along with the /sys/firmware
directories for Ubuntu 16.04 and a fresh install of RHEL 7.2. I executed
as root and was able to poke around the directories, but if any issues
with the data I can try to recollect.

Thanks,
Jeff

** Attachment added: "screenshot and /sys/firmware directories"
   
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1578022/+attachment/4660356/+files/dmi_cisco.rar

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

Title:
  dmidecode fails to output smibios 3.0 info

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

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

37 matches

Mail list logo