[Kernel-packages] [Bug 1946303] Re: No video after wake from S3 due to Nvidia driver crash

2022-05-02 Thread dhenry
This issue still exists with Ubuntu 22.04 and NVIDIA driver 510 (GeForce
GTX 980M).

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-470 in Ubuntu.
https://bugs.launchpad.net/bugs/1946303

Title:
  No video after wake from S3 due to Nvidia driver crash

Status in nvidia-graphics-drivers-470 package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-510 package in Ubuntu:
  Confirmed

Bug description:
  Since upgrading to Ubuntu 21.10, my computer sometimes fails to properly wake 
from suspend. It does start running again, but there is no video output. I'm 
attaching text for two crashes from kernel log output. First is:
  /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:3967 
nv_restore_user_channels+0xce/0xe0 [nvidia]
  Second is:
  /var/lib/dkms/nvidia/470.63.01/build/nvidia/nv.c:4162 
nv_set_system_power_state+0x2c8/0x3d0 [nvidia]

  Apparently I'm not the only one having this problem with 470 drivers.
  https://forums.linuxmint.com/viewtopic.php?t=354445
  
https://forums.developer.nvidia.com/t/fixed-suspend-resume-issues-with-the-driver-version-470/187150

  Driver 470 uses the new suspend mechanism via /usr/lib/systemd/system-
  sleep/nvidia. But I was using that mechanism with driver 460 in Ubuntu
  21.04 and sleep was reliable then. Right now I'm going back to driver
  460.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: nvidia-driver-470 470.63.01-0ubuntu4
  ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
  Uname: Linux 5.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu70
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct  6 23:24:02 2021
  SourcePackage: nvidia-graphics-drivers-470
  UpgradeStatus: Upgraded to impish on 2021-10-02 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1946303/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1970088] [NEW] Resume fail after suspend with NVIDIA driver on Ubuntu 22.04

2022-04-24 Thread dhenry
Public bug reported:

After upgrading from 21.10 to 22.04, the suspend/resume stopped working
on my laptop with an NVIDIA discrete card.

The computer goes in sleep mode, but when resuming, the screen remain
black.

The issue happens with both NVIDIA driver 470 and 510. Previously, I was
running the 470 because I use MATE and there was a bug with
Xorg/MATE/NVIDIA 510, so I don't know how it behave in Ubuntu 21.10 and
NVIDIA driver 510.

I could not try with an older kernel on Ubuntu 22.04, because DKMS
refused to build the driver for older kernels.


The dmesg/kern.log contains a backtrace:

Apr 24 11:26:16 thebat kernel: [   70.354793] [ cut here 
]
Apr 24 11:26:16 thebat kernel: [   70.354795] WARNING: CPU: 2 PID: 4127 at 
/var/lib/dkms/nvidia/510.60.02/build/nvidia/nv.c:3935 
nv_restore_user_channels+0xce/0xe0 [nvidia]
Apr 24 11:26:16 thebat kernel: [   70.354974] Modules linked in: vboxnetadp(OE) 
vboxnetflt(OE) vboxdrv(OE) nvme_fabrics rfcomm ccm xt_CHECKSUM xt_MASQUERADE 
xt_conntrack ipt_REJECT xt_tcpudp nft_compat nf_nat_tftp nft_objref 
nf_conntrack_tftp nft_counter nft_fib_inet nft_fib_ipv4 nft_fib_ipv6 nft_fib 
bridge stp llc nft_reject_inet nf_reject_ipv4 nf_reject_ipv6 nft_reject nft_ct 
nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 ip_set 
nf_tables nfnetlink cmac algif_hash algif_skcipher af_alg bnep intel_rapl_msr 
intel_rapl_common intel_tcc_cooling uvcvideo videobuf2_vmalloc videobuf2_memops 
x86_pkg_temp_thermal binfmt_misc intel_powerclamp snd_hda_codec_hdmi coretemp 
videobuf2_v4l2 clevo_xsm_wmi(OE) snd_hda_codec_realtek snd_hda_codec_generic 
videobuf2_common kvm_intel ledtrig_audio kvm videodev nls_iso8859_1 btusb rapl 
iwlmvm snd_hda_intel mc btrtl intel_cstate btbcm snd_seq_midi snd_intel_dspcfg 
snd_seq_midi_event btintel mac80211 snd_intel_sdw_acpi snd_rawmidi bluetooth 
ecdh_generic ecc libarc4 joydev
Apr 24 11:26:16 thebat kernel: [   70.355006]  input_leds snd_hda_codec snd_seq 
snd_hda_core iwlwifi snd_hwdep serio_raw intel_wmi_thunderbolt efi_pstore 
mxm_wmi wmi_bmof ee1004 snd_pcm snd_seq_device cfg80211 snd_timer snd mei_me 
soundcore mei intel_pch_thermal mac_hid acpi_pad nvidia_uvm(POE) sch_fq_codel 
ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp parport ip_tables x_tables 
autofs4 dm_crypt 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 nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) 
drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops cec 
crct10dif_pclmul rc_core crc32_pclmul ghash_clmulni_intel aesni_intel 
crypto_simd cryptd drm psmouse i2c_i801 nvme i2c_smbus sdhci_pci ahci xhci_pci 
alx cqhci xhci_pci_renesas nvme_core sdhci mdio libahci wmi video
Apr 24 11:26:16 thebat kernel: [   70.355040] CPU: 2 PID: 4127 Comm: 
nvidia-sleep.sh Tainted: P   OE 5.15.0-25-generic #25-Ubuntu
Apr 24 11:26:16 thebat kernel: [   70.355042] Hardware name: Notebook   
  P7xxDM(-G)  /P775DM(-G)  
, BIOS 1.05.09 12/28/2015
Apr 24 11:26:16 thebat kernel: [   70.355043] RIP: 
0010:nv_restore_user_channels+0xce/0xe0 [nvidia]
Apr 24 11:26:16 thebat kernel: [   70.355158] Code: b2 b3 fa be 01 00 00 00 4c 
89 ef e8 ec b3 00 00 48 89 df e8 14 b2 b3 fa ba 02 00 00 00 4c 89 ee 4c 89 e7 
e8 04 61 94 00 eb 93 <0f> 0b eb c6 41 be 51 00 00 00 eb 9e 66 0f 1f 44 00 00 0f 
1f 44 00
Apr 24 11:26:16 thebat kernel: [   70.355159] RSP: 0018:b5af83a5bd48 
EFLAGS: 00010206
Apr 24 11:26:16 thebat kernel: [   70.355160] RAX: 0003 RBX: 
8c4d1ec00800 RCX: b5af83a5bce0
Apr 24 11:26:16 thebat kernel: [   70.355161] RDX: 0087 RSI: 
0246 RDI: 8c4d00ee1068
Apr 24 11:26:16 thebat kernel: [   70.355162] RBP: b5af83a5bd70 R08: 
 R09: 8c54a65b1040
Apr 24 11:26:16 thebat kernel: [   70.355163] R10: 8c4d03d04660 R11: 
 R12: 8c4d1146b000
Apr 24 11:26:16 thebat kernel: [   70.355164] R13: 8c4d1ec00800 R14: 
0003 R15: 8c4d1ec00d10
Apr 24 11:26:16 thebat kernel: [   70.355165] FS:  7f14620a8740() 
GS:8c54a648() knlGS:
Apr 24 11:26:16 thebat kernel: [   70.355166] CS:  0010 DS:  ES:  CR0: 
80050033
Apr 24 11:26:16 thebat kernel: [   70.355167] CR2: 55bb914470c8 CR3: 
00010ee62003 CR4: 003706e0
Apr 24 11:26:16 thebat kernel: [   70.355168] DR0:  DR1: 
 DR2: 
Apr 24 11:26:16 thebat kernel: [   70.355168] DR3:  DR6: 
fffe0ff0 DR7: 0400
Apr 24 11:26:16 thebat kernel: [   70.355169] Call Trace:
Apr 24 11:26:16 thebat kernel: [   70.355170]  
Apr 24 11:26:16 thebat kernel: [   70.355172]  
nv_set_system_power_state+0x22b/0x3e0 [nvidia]
Apr 24 11:26:16 thebat kernel: [   70.355286]  
nv_procfs_write_suspend+0x100/0x180 [nvidia]
Apr 24 

[Kernel-packages] [Bug 1535470] Re: Backlight brightness keys not working

2016-06-07 Thread dhenry
Well, the main purpose of my comment was to give some hints to Ian with
his laptop, in case it could help him, because we have some common
hardware parts...

I can fill a new bug for my case, but what do you mean by "Ubuntu repository 
kernel"?
Currently, I'm running the 4.6 kernel from ~kernel-ppa/mainline/, which is also 
(in some way) an Ubuntu repository, isn't it?
Should I switch back to the standard 4.4 kernel from main repository in order 
to fill my bug?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1535470

Title:
  Backlight brightness keys not working

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Originally described in bug 1533221. This is a new bug to track this
  additional issue separately.

  The above bug has h/w info attached etc. This is a new skylake
  chipset.

  Backlight function keys are not working. I have tried various
  combinations of:

  acpi_osi=Linux acpi_backlight=native
  acpi_osi=Linux acpi_backlight=vendor
  acpi_osi=! acpi_backlight=vendor
  etc, etc

  with no luck.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian2218 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=df036c01-8f22-4d8f-ad55-6add4f99f5f4
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:066d Acer, Inc 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_P67RGRERA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-0-generic 
root=UUID=2077d068-d7ee-4407-89e1-7d2b884173de ro acpi_osi=Linux 
acpi_backlight=native drm.debug=14
  ProcVersionSignature: Ubuntu 4.4.0-0.12-generic 4.4.0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-0-generic N/A
   linux-backports-modules-4.4.0-0-generic  N/A
   linux-firmware   1.155
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.4.0-0-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.10
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.10:bd11/20/2015:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65_P67RGRERA
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1535470] Re: Backlight brightness keys not working

2016-06-06 Thread dhenry
I have a different Clevo model (P751DM-G) but with same issue: the
backlight Fn-keys doesn't work neither out of the box, nor with a kernel
4.6. Well, in fact, they work until I suspend/resume, and then they no
longer work. Looking at acpi_listen, I noticed that after first
suspend/resume cycle, some ACPI events where no longer triggered (like
the backlight Fn-keys, but also the lid close!).

I found a fix by loading a clevo-wmi driver. There are several clevo-wmi 
drivers on the internet (various attempts to write a driver for it...). For my 
laptop, I use:
* https://bitbucket.org/lynthium/clevo-xsm-wmi (it aims at supporting all Clevo 
models)

Since the clevo-xsm-wmi driver doesn't seem to handle your P65 model, you may 
need to try some other ones, like this one:
* https://github.com/gamaral/clevo-wmi
Maybe it could help for you too.

To be honest, I have no idea why it did fix my backlight fn-keys, as
those drivers are supposed to handle different features (keyboard
backlight, rfkill switch, hw monitoring). Nevertheless, if I unload the
module, then the issue happen again.

Note that this workaround fixes the Fn-keys: the backlight popup notification 
appears and I can increase/decrease value, however it has no effect on the 
screen. This is just ACPI event that has been fixed.
In order to really adjust LCD backlight, I have to play with nvidia-settings 
(with proprietary driver). Example, to set backlight brightness at 50%:

nvidia-settings -n -a BacklightBrightness=50

Some glue is still missing to link ACPI events with nvidia-settings.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1535470

Title:
  Backlight brightness keys not working

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Originally described in bug 1533221. This is a new bug to track this
  additional issue separately.

  The above bug has h/w info attached etc. This is a new skylake
  chipset.

  Backlight function keys are not working. I have tried various
  combinations of:

  acpi_osi=Linux acpi_backlight=native
  acpi_osi=Linux acpi_backlight=vendor
  acpi_osi=! acpi_backlight=vendor
  etc, etc

  with no luck.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ian2218 F pulseaudio
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 15.10
  HibernationDevice: RESUME=UUID=df036c01-8f22-4d8f-ad55-6add4f99f5f4
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:066d Acer, Inc 
   Bus 001 Device 003: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_P67RGRERA
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-0-generic 
root=UUID=2077d068-d7ee-4407-89e1-7d2b884173de ro acpi_osi=Linux 
acpi_backlight=native drm.debug=14
  ProcVersionSignature: Ubuntu 4.4.0-0.12-generic 4.4.0
  RelatedPackageVersions:
   linux-restricted-modules-4.4.0-0-generic N/A
   linux-backports-modules-4.4.0-0-generic  N/A
   linux-firmware   1.155
  Tags:  wily
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  Uname: Linux 4.4.0-0-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/20/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.10
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.10:bd11/20/2015:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.name: P65_P67RGRERA
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook

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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp


[Kernel-packages] [Bug 1432405] Re: [Toshiba Equium A100-306] WARNING: CPU: 0 PID: 968 at /build/buildd/linux-3.19.0/drivers/gpu/drm/drm_irq.c:1121 drm_wait_one_vblank+0x170/0x180 [drm]()

2015-05-23 Thread dhenry
Seems to be fixed in kernel 3.19.0-18, isn't it?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1432405

Title:
  [Toshiba Equium A100-306] WARNING: CPU: 0 PID: 968 at
  /build/buildd/linux-3.19.0/drivers/gpu/drm/drm_irq.c:1121
  drm_wait_one_vblank+0x170/0x180 [drm]()

Status in The Linux Kernel:
  Confirmed
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Noticed during boot of vivid after upgrade:

  [   54.762967] [ cut here ]
  [   54.763009] WARNING: CPU: 1 PID: 968 at 
/build/buildd/linux-3.19.0/drivers/gpu/drm/drm_irq.c:1121 
drm_wait_one_vblank+0x170/0x180 [drm]()
  [   54.763012] vblank not available on crtc 0, ret=-22
  [   54.763014] Modules linked in: binfmt_misc snd_hda_codec_si3054 arc4 
snd_hda_codec_realtek snd_hda_codec_generic snd_hda_intel iwl3945 
snd_hda_controller iwlegacy snd_hda_codec mac80211 snd_hwdep pcmcia snd_pcm 
snd_seq_midi snd_seq_midi_event snd_rawmidi yenta_socket cfg80211 coretemp 
pcmcia_rsrc tifm_7xx1 snd_seq pcmcia_core tifm_core joydev lpc_ich serio_raw 
snd_seq_device snd_timer irda snd soundcore toshiba_bluetooth toshiba_haps 
crc_ccitt 8250_fintek tpm_infineon shpchp mac_hid parport_pc ppdev lp parport 
autofs4 psmouse firewire_ohci pata_acpi e100 sdhci_pci mii i915 sdhci 
firewire_core i2c_algo_bit crc_itu_t drm_kms_helper drm video
  [   54.763065] CPU: 1 PID: 968 Comm: Xorg Tainted: GW  
3.19.0-9-generic #9-Ubuntu
  [   54.763068] Hardware name: TOSHIBA Equium A100/MPAD-MSAE Customer 
Reference Boards, BIOS 2.1010/23/2006
  [   54.763070]  c02e2b70 8800ba62b738 817c09b5 
0007
  [   54.763075]  8800ba62b788 8800ba62b778 8107595a 
8800ba62b758
  [   54.763079]  88003548 880035fb2000  
88003548
  [   54.763083] Call Trace:
  [   54.763094]  [817c09b5] dump_stack+0x45/0x57
  [   54.763099]  [8107595a] warn_slowpath_common+0x8a/0xc0
  [   54.763103]  [810759d6] warn_slowpath_fmt+0x46/0x50
  [   54.763118]  [c02b5e80] drm_wait_one_vblank+0x170/0x180 [drm]
  [   54.763155]  [c03c53af] ? gen4_read32+0x4f/0xc0 [i915]
  [   54.763186]  [c0417955] intel_enable_tv+0x25/0x60 [i915]
  [   54.763212]  [c03e2d1b] i9xx_crtc_enable+0x3fb/0x4c0 [i915]
  [   54.763239]  [c03e12b2] __intel_set_mode+0x882/0xc80 [i915]
  [   54.763266]  [c03e6dfd] intel_set_mode+0x6d/0x90 [i915]
  [   54.763293]  [c03e7096] intel_get_load_detect_pipe+0x276/0x600 
[i915]
  [   54.763298]  [811989d0] ? zone_statistics+0x80/0xa0
  [   54.763328]  [c0418555] intel_tv_detect+0x135/0x670 [i915]
  [   54.763342]  [c0322b13] 
drm_helper_probe_single_connector_modes_merge_bits+0x303/0x460 [drm_kms_helper]
  [   54.763350]  [c0322c83] 
drm_helper_probe_single_connector_modes+0x13/0x20 [drm_kms_helper]
  [   54.763369]  [c02c216f] drm_mode_getconnector+0x43f/0x4b0 [drm]
  [   54.763383]  [c02b3adf] drm_ioctl+0x1df/0x680 [drm]
  [   54.763390]  [812077b0] do_vfs_ioctl+0x2e0/0x4e0
  [   54.763394]  [811f5755] ? __sb_end_write+0x35/0x70
  [   54.763399]  [811f31c2] ? vfs_write+0x1b2/0x1f0
  [   54.763403]  [81207a31] SyS_ioctl+0x81/0xa0
  [   54.763407]  [817c7aed] system_call_fastpath+0x16/0x1b
  [   54.763410] ---[ end trace 959064f9168f0b5b ]---

  repeats quite a few times during the boot.
  (3.19.0-9-generic #9-Ubuntu)
  Oldish Core2 laptop, internal LCD only running KDE.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-generic 3.19.0.9.8
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dg 2008 F pulseaudio
  Date: Sun Mar 15 17:49:05 2015
  HibernationDevice: RESUME=/dev/mapper/davros--vg-swap_1
  InstallationDate: Installed on 2013-11-15 (485 days ago)
  InstallationMedia: Ubuntu-Server 14.04 LTS Trusty Tahr - Alpha amd64 
(20131115)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: TOSHIBA Equium A100
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-9-generic 
root=/dev/mapper/hostname--vg-root ro
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-9-generic N/A
   linux-backports-modules-3.19.0-9-generic  N/A
   linux-firmware