[Kernel-packages] [Bug 1940713] [NEW] llvm-9, llvm-11 and llvm-12 contain a zero-byte manpage

2021-08-20 Thread Horst Schirmeier
Public bug reported:

The llvm-mcmarkup manpage is empty for llvm-9 (1:9.0.1-16.1ubuntu1),
llvm-11 (1:11.0.1-2ubuntu5) and llvm-12 (1:12.0.1-1):

llvm-9: /usr/share/man/man1/llvm-mcmarkup-9.1.gz
llvm-11: /usr/share/man/man1/llvm-mcmarkup-11.1.gz
llvm-12: /usr/share/man/man1/llvm-mcmarkup-12.1.gz

These 20-byte .gz files are all compressed zero-byte manpages.

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: llvm-12 1:12.0.1-1
ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
Uname: Linux 5.11.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Fri Aug 20 21:21:54 2021
InstallationDate: Installed on 2016-11-26 (1728 days ago)
InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
RebootRequiredPkgs:
 linux-image-5.13.0-14-generic
 linux-base
SourcePackage: llvm-toolchain-12
UpgradeStatus: Upgraded to impish on 2021-08-08 (12 days ago)

** Affects: llvm-toolchain-12 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug impish

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

Title:
  llvm-9, llvm-11 and llvm-12 contain a zero-byte manpage

Status in llvm-toolchain-12 package in Ubuntu:
  New

Bug description:
  The llvm-mcmarkup manpage is empty for llvm-9 (1:9.0.1-16.1ubuntu1),
  llvm-11 (1:11.0.1-2ubuntu5) and llvm-12 (1:12.0.1-1):

  llvm-9: /usr/share/man/man1/llvm-mcmarkup-9.1.gz
  llvm-11: /usr/share/man/man1/llvm-mcmarkup-11.1.gz
  llvm-12: /usr/share/man/man1/llvm-mcmarkup-12.1.gz

  These 20-byte .gz files are all compressed zero-byte manpages.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: llvm-12 1:12.0.1-1
  ProcVersionSignature: Ubuntu 5.11.0-25.27-generic 5.11.22
  Uname: Linux 5.11.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Fri Aug 20 21:21:54 2021
  InstallationDate: Installed on 2016-11-26 (1728 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  RebootRequiredPkgs:
   linux-image-5.13.0-14-generic
   linux-base
  SourcePackage: llvm-toolchain-12
  UpgradeStatus: Upgraded to impish on 2021-08-08 (12 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-12/+bug/1940713/+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 1866984] Re: linux-5.4 regression: hibernate-disk resumes instantly

2020-03-11 Thread Horst Schirmeier
** Summary changed:

- hibernate-disk resumes instantly
+ linux-5.4 regression: hibernate-disk resumes instantly

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

Title:
  linux-5.4 regression: hibernate-disk resumes instantly

Status in hibernate package in Ubuntu:
  Confirmed
Status in linux-5.4 package in Ubuntu:
  New

Bug description:
  Since upgrading from 19.10 (eoan) to 20.04 (focal), hibernate-disk
  fails to properly hibernate and shutdown the system; instead, Ubuntu
  resumes instantly.

  $ sudo hibernate-disk
  [sudo] password for xyz: 
  hibernate-disk:Warning: Tuxonice binary signature file not found.
  $

  (Note that this warning has been there earlier and is presumably not
  associated with this bug.)

  Expected: Switch to console, memory-page writeout progress indication,
  poweroff

  Observed: Switch to console, very quickly switch back to X11

  Excerpt from dmesg:

  [  418.377514] usbcore: deregistering interface driver uvcvideo
  [  419.227465] Filesystems sync: 0.006 seconds
  [  419.227468] Freezing user space processes ... (elapsed 0.002 seconds) done.
  [  419.229889] OOM killer disabled.
  [  419.230429] PM: Marking nosave pages: [mem 0x-0x0fff]
  [  419.230432] PM: Marking nosave pages: [mem 0x0009d000-0x000f]
  [  419.230440] PM: Marking nosave pages: [mem 0x99438000-0x]
  [  419.233760] PM: Basic memory bitmaps created
  [  419.234176] PM: Preallocating image memory... done (allocated 1188843 
pages)
  [  420.040021] PM: Allocated 4755372 kbytes in 0.80 seconds (5944.21 MB/s)
  [  420.040021] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  420.041324] printk: Suspending console(s) (use no_console_suspend to debug)
  [  420.041755] wlp3s0: deauthenticating from cc:ce:1e:61:2e:d0 by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [  421.278599] ACPI: EC: interrupt blocked
  [  421.297107] ACPI: Preparing to enter system sleep state S4
  [  421.301832] ACPI: EC: event blocked
  [  421.301833] ACPI: EC: EC stopped
  [  421.301834] PM: Saving platform NVS memory
  [  421.302557] Disabling non-boot CPUs ...
  [  421.303996] smpboot: CPU 1 is now offline
  [  421.307624] smpboot: CPU 2 is now offline
  [  421.309904] IRQ 129: no longer affine to CPU3
  [  421.310921] smpboot: CPU 3 is now offline
  [  421.314818] smpboot: CPU 4 is now offline
  [  421.317033] IRQ 16: no longer affine to CPU5
  [  421.317040] IRQ 132: no longer affine to CPU5
  [  421.318049] smpboot: CPU 5 is now offline
  [  421.320365] IRQ 126: no longer affine to CPU6
  [  421.320373] IRQ 130: no longer affine to CPU6
  [  421.321405] smpboot: CPU 6 is now offline
  [  421.325743] smpboot: CPU 7 is now offline
  [  421.330059] PM: Creating hibernation image:
  [  422.045974] PM: Need to copy 1182218 pages
  [  422.045977] PM: Normal pages needed: 1182218 + 1024, available pages: 
7053219
  [  423.427947] PM: Hibernation image created (1182218 pages copied)
  [  421.330504] PM: Restoring platform NVS memory
  [  421.330638] ACPI: EC: EC started
  [  421.331412] Enabling non-boot CPUs ...
  [  421.331453] x86: Booting SMP configuration:
  [  421.331454] smpboot: Booting Node 0 Processor 1 APIC 0x2
  [  421.332297] CPU1 is up
  [  421.332327] smpboot: Booting Node 0 Processor 2 APIC 0x4
  [  421.333137] CPU2 is up
  [  421.333164] smpboot: Booting Node 0 Processor 3 APIC 0x6
  [  421.333987] CPU3 is up
  [  421.334013] smpboot: Booting Node 0 Processor 4 APIC 0x1
  [  421.334926] CPU4 is up
  [  421.334956] smpboot: Booting Node 0 Processor 5 APIC 0x3
  [  421.335640] CPU5 is up
  [  421.335666] smpboot: Booting Node 0 Processor 6 APIC 0x5
  [  421.336447] CPU6 is up
  [  421.336469] smpboot: Booting Node 0 Processor 7 APIC 0x7
  [  421.337232] CPU7 is up
  [  421.340095] ACPI: Waking up from system sleep state S4
  [  421.347884] ACPI: EC: interrupt unblocked
  [  421.390488] ACPI: EC: event unblocked
  [  421.391425] tpm tpm0: tpm_try_transmit: send(): error -5
  [  421.403775] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM
  [  421.553049] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM
  [  421.603306] [drm] Reducing the compressed framebuffer size. This may lead 
to less power savings than a non-reduced-size. Try to increase stolen memory 
size if available in BIOS.
  [  421.634367] iwlwifi :03:00.0: FW already configured (0) - 
re-configuring
  [  421.714565] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [  421.715010] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
  [  421.715012] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
  [  421.715083] ata1.00: ACPI cmd ef/10:09:00:00:00:a0 (SET FEATURES) succeeded
  [  421.715396] ata1.00: supports DRM functions and may not be fully accessible
  [  421.716087] ata1.00: disabling queued TRIM support
  [  

[Kernel-packages] [Bug 1866984] Re: hibernate-disk resumes instantly

2020-03-11 Thread Horst Schirmeier
This seems to be caused by Focal's 5.4 kernel: after booting Ubuntu
19.10's linux-image-5.3.0-40-generic (5.3.0-40.32), which remained on
the system after upgrading to 20.04, hibernate-disk (and resume
afterwards) works fine.

** Also affects: linux-5.4 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  linux-5.4 regression: hibernate-disk resumes instantly

Status in hibernate package in Ubuntu:
  Confirmed
Status in linux-5.4 package in Ubuntu:
  New

Bug description:
  Since upgrading from 19.10 (eoan) to 20.04 (focal), hibernate-disk
  fails to properly hibernate and shutdown the system; instead, Ubuntu
  resumes instantly.

  $ sudo hibernate-disk
  [sudo] password for xyz: 
  hibernate-disk:Warning: Tuxonice binary signature file not found.
  $

  (Note that this warning has been there earlier and is presumably not
  associated with this bug.)

  Expected: Switch to console, memory-page writeout progress indication,
  poweroff

  Observed: Switch to console, very quickly switch back to X11

  Excerpt from dmesg:

  [  418.377514] usbcore: deregistering interface driver uvcvideo
  [  419.227465] Filesystems sync: 0.006 seconds
  [  419.227468] Freezing user space processes ... (elapsed 0.002 seconds) done.
  [  419.229889] OOM killer disabled.
  [  419.230429] PM: Marking nosave pages: [mem 0x-0x0fff]
  [  419.230432] PM: Marking nosave pages: [mem 0x0009d000-0x000f]
  [  419.230440] PM: Marking nosave pages: [mem 0x99438000-0x]
  [  419.233760] PM: Basic memory bitmaps created
  [  419.234176] PM: Preallocating image memory... done (allocated 1188843 
pages)
  [  420.040021] PM: Allocated 4755372 kbytes in 0.80 seconds (5944.21 MB/s)
  [  420.040021] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) 
done.
  [  420.041324] printk: Suspending console(s) (use no_console_suspend to debug)
  [  420.041755] wlp3s0: deauthenticating from cc:ce:1e:61:2e:d0 by local 
choice (Reason: 3=DEAUTH_LEAVING)
  [  421.278599] ACPI: EC: interrupt blocked
  [  421.297107] ACPI: Preparing to enter system sleep state S4
  [  421.301832] ACPI: EC: event blocked
  [  421.301833] ACPI: EC: EC stopped
  [  421.301834] PM: Saving platform NVS memory
  [  421.302557] Disabling non-boot CPUs ...
  [  421.303996] smpboot: CPU 1 is now offline
  [  421.307624] smpboot: CPU 2 is now offline
  [  421.309904] IRQ 129: no longer affine to CPU3
  [  421.310921] smpboot: CPU 3 is now offline
  [  421.314818] smpboot: CPU 4 is now offline
  [  421.317033] IRQ 16: no longer affine to CPU5
  [  421.317040] IRQ 132: no longer affine to CPU5
  [  421.318049] smpboot: CPU 5 is now offline
  [  421.320365] IRQ 126: no longer affine to CPU6
  [  421.320373] IRQ 130: no longer affine to CPU6
  [  421.321405] smpboot: CPU 6 is now offline
  [  421.325743] smpboot: CPU 7 is now offline
  [  421.330059] PM: Creating hibernation image:
  [  422.045974] PM: Need to copy 1182218 pages
  [  422.045977] PM: Normal pages needed: 1182218 + 1024, available pages: 
7053219
  [  423.427947] PM: Hibernation image created (1182218 pages copied)
  [  421.330504] PM: Restoring platform NVS memory
  [  421.330638] ACPI: EC: EC started
  [  421.331412] Enabling non-boot CPUs ...
  [  421.331453] x86: Booting SMP configuration:
  [  421.331454] smpboot: Booting Node 0 Processor 1 APIC 0x2
  [  421.332297] CPU1 is up
  [  421.332327] smpboot: Booting Node 0 Processor 2 APIC 0x4
  [  421.333137] CPU2 is up
  [  421.333164] smpboot: Booting Node 0 Processor 3 APIC 0x6
  [  421.333987] CPU3 is up
  [  421.334013] smpboot: Booting Node 0 Processor 4 APIC 0x1
  [  421.334926] CPU4 is up
  [  421.334956] smpboot: Booting Node 0 Processor 5 APIC 0x3
  [  421.335640] CPU5 is up
  [  421.335666] smpboot: Booting Node 0 Processor 6 APIC 0x5
  [  421.336447] CPU6 is up
  [  421.336469] smpboot: Booting Node 0 Processor 7 APIC 0x7
  [  421.337232] CPU7 is up
  [  421.340095] ACPI: Waking up from system sleep state S4
  [  421.347884] ACPI: EC: interrupt unblocked
  [  421.390488] ACPI: EC: event unblocked
  [  421.391425] tpm tpm0: tpm_try_transmit: send(): error -5
  [  421.403775] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM
  [  421.553049] iwlwifi :03:00.0: Applying debug destination EXTERNAL_DRAM
  [  421.603306] [drm] Reducing the compressed framebuffer size. This may lead 
to less power savings than a non-reduced-size. Try to increase stolen memory 
size if available in BIOS.
  [  421.634367] iwlwifi :03:00.0: FW already configured (0) - 
re-configuring
  [  421.714565] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
  [  421.715010] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded
  [  421.715012] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) 
filtered out
  [  421.715083] ata1.00: ACPI cmd 

[Kernel-packages] [Bug 1723680] Re: GPU Hang in Xorg rcs0 drm/i915

2017-12-18 Thread Horst Schirmeier
Possibly this bug? https://bugs.freedesktop.org/show_bug.cgi?id=102435
-> Ubuntu 17.10's Mesa 17.2.2 seems to be broken

** Bug watch added: freedesktop.org Bugzilla #102435
   https://bugs.freedesktop.org/show_bug.cgi?id=102435

-- 
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/1723680

Title:
  GPU Hang in Xorg rcs0 drm/i915

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Zesty:
  Triaged
Status in linux source package in Artful:
  Triaged

Bug description:
  Distributor ID:   Ubuntu
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10
  Codename: artful

  When using linux kernel linux-image-4.13.0-12-generic to linux-
  image-4.13.0-16-generic Xorg fails to start with kernel error messages
  below. Kernel boots and displays messages allows for GUI to enter disk
  encryption key then tries to start Xorg login.  Shows blank screen,
  sometimes part of login dialog.  Then hangs and goes blank usually
  showing the low graphics mode error screen from Xorg and no
  functionality after a while.  Can ctrl+alt+f1 to console.  Using
  linux-image-4.10.0-35-generic everything works as expected.  System
  worked without issue with Ubuntu 17.04

  Kernel error messages:
  [   43.836641] [drm] GPU HANG: ecode 8:0:0x00df, in Xorg [1027], reason: 
Hang on rcs0, action: reset
  [   43.836645] [drm] GPU hangs can indicate a bug anywhere in the entire gfx 
stack, including userspace.
  [   43.836646] [drm] Please file a _new_ bug report on bugs.freedesktop.org 
against DRI -> DRM/Intel
  [   43.836647] [drm] drm/i915 developers can then reassign to the right 
component if it's not a kernel issue.
  [   43.836648] [drm] The gpu crash dump is required to analyze gpu hangs, so 
please always attach it.
  [   43.836649] [drm] GPU crash dump saved to /sys/class/drm/card0/error
  [   43.836718] drm/i915: Resetting chip after gpu hang
  [   55.812149] drm/i915: Resetting chip after gpu hang
  [   63.840645] drm/i915: Resetting chip after gpu hang
  [   71.836614] drm/i915: Resetting chip after gpu hang
  [   79.836882] drm/i915: Resetting chip after gpu hang
  [   88.828508] drm/i915: Resetting chip after gpu hang

  have tried kernel parameter intel_iommu=off, intel_iommu=igfx_off, 
i915.enable_rc6=0 with no better results.
  lshw, dmesg and card0/error file attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1723680/+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 1702368] Re: Mounted sshfs filesystems sometimes prevent suspend

2017-09-01 Thread Horst Schirmeier
I'm consistently seeing this on Zesty (linux-image-4.10.0-33-generic),
the same fuse mount didn't prevent suspending before Ubuntu 17.04:

[262730.781448] Freezing of tasks failed after 20.009 seconds (1 tasks refusing 
to freeze, wq_busy=0):
[262730.781679] FileInfoThread  D0 10555   1869 0x0104
[262730.781684] Call Trace:
[262730.781695]  __schedule+0x233/0x6f0
[262730.781699]  schedule+0x36/0x80
[262730.781705]  request_wait_answer+0x14b/0x210
[262730.781711]  ? wake_atomic_t_function+0x60/0x60
[262730.781716]  __fuse_request_send+0x84/0x90
[...]

-- 
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/1702368

Title:
  Mounted sshfs filesystems sometimes prevent suspend

Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Triaged
Status in sshfs-fuse package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu artful with linux-image-4.10.0-26-generic 4.10.0-26.30
  and sshfs 2.8-1. I use "sshfs -o reconnect" and often run gvim against
  a file on an sshfs filesystem.

  Sometimes when I suspend I get:

  Jul  4 20:59:08 xps kernel: [46684.608740] PM: Syncing filesystems ... done.
  Jul  4 20:59:08 xps kernel: [46684.613278] PM: Preparing system for sleep 
(mem)
  Jul  4 20:59:08 xps kernel: [46684.613788] Freezing user space processes ... 
  Jul  4 20:59:08 xps kernel: [46704.620140] Freezing of tasks failed after 
20.006 seconds (1 tasks refusing to freeze, wq_busy=0):
  Jul  4 20:59:08 xps kernel: [46704.620534] gvimD0 11155   
1336 0x0004
  Jul  4 20:59:08 xps kernel: [46704.620541] Call Trace:
  Jul  4 20:59:08 xps kernel: [46704.620556]  __schedule+0x233/0x6f0
  ...
  Jul  4 20:59:08 xps kernel: [46704.620679]  
entry_SYSCALL_64_fastpath+0x1e/0xad
  ...
  Jul  4 20:59:08 xps kernel: [46704.620711] Restarting tasks ... done.

  ...and the system fails to suspend.

  AFAICT, this is https://bugzilla.redhat.com/show_bug.cgi?id=656992 and
  https://lists.debian.org/debian-kernel/2011/10/msg00412.html has an
  extensive explanation. The corresponding Debian bug was closed long
  ago due to inactivity. It isn't exactly bug 388419 though since that
  is about behaviour after resume, rather than failure to suspend.

  This affects sshfs-fuse, but it sounds like a full fix would be in the
  kernel. I wonder if it's possible to work around in userspace
  packaging in sshfs-fuse, though, by arranging some action in userspace
  before suspend?

  It seems unlikely that this will be addressed any time soon, but it'd be nice 
to keep a bug open in Launchpad so that users can have a single rallying point.
  --- 
  ApportVersion: 2.20.5-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robie  1519 F pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 17.10
  HibernationDevice: RESUME=UUID=ae23a431-2f44-4c12-992a-a0da8186bfcc
  InstallationDate: Installed on 2017-05-11 (54 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:568b Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  Package: sshfs-fuse
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-26-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.10.0-26.30-generic 4.10.17
  RelatedPackageVersions:
   linux-restricted-modules-4.10.0-26-generic N/A
   linux-backports-modules-4.10.0-26-generic  N/A
   linux-firmware 1.167
  Tags:  artful
  Uname: Linux 4.10.0-26-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.2
  dmi.board.name: 00GCYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.2:bd01/18/2017:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1702368/+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 995218] Re: 1180:0822 SD card not detected on insertion

2014-09-29 Thread Horst Schirmeier
This problem persists in Ubuntu 14.04 with x86_64 kernel
3.13.0-36-generic.

-- 
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/995218

Title:
  1180:0822 SD card not detected on insertion

Status in The Linux Kernel:
  New
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Quite simply, when I insert an SD card (which works fine inserted into
  the camera or my wife's laptop), nothing happens. No icons, no
  filebrowser opening. Also, no noticeable activity in /var/log. The
  device is visible on the PCI, with or without card.

  Also occurs in 3.4.0-999. The file was called linux-
  image-3.4.0-999-generic_3.4.0-999.201205060405_amd64.deb .

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-24-generic 3.2.0-24.37
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: fglrx
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  AplayDevices:
    List of PLAYBACK Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 1/1
     Subdevice #0: subdevice #0
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
     Subdevices: 2/2
     Subdevice #0: subdevice #0
     Subdevice #1: subdevice #1
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  feenstra   3889 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xd842 irq 49'
     Mixer name : 'Analog Devices AD1984A'
     Components : 'HDA:11d4194a,103c30dc,00100400'
     Controls  : 18
     Simple ctrls  : 11
  Date: Sat May  5 20:39:22 2012
  HibernationDevice: RESUME=UUID=92c92b0a-05c8-423e-a01a-5e80e3b0af85
  MachineType: Hewlett-Packard HP EliteBook 6930p
  PccardctlStatus:
   Socket 0:
     3.3V
    16-bit
    PC Card
     Subdevice 0 (function 0) bound to driver pata_pcmcia
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic 
root=UUID=21da2f5d-74ae-4f92-bafe-1ee80dcee5c9 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-24-generic N/A
   linux-backports-modules-3.2.0-24-generic  N/A
   linux-firmware1.79
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PCD Ver. F.12
  dmi.board.name: 30DC
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 87.27
  dmi.chassis.asset.tag: CZC9351JJ6
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PCDVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DC:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 6930p
  dmi.product.version: F.12
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/995218/+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 730820] Re: [Latitude E6510] ricoh e822: SD card is unable to mount

2014-09-19 Thread Horst Schirmeier
Should I report a new bug, or should this one be reopened? The problem
is definitely back again.

-- 
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/730820

Title:
  [Latitude E6510] ricoh e822: SD card is unable to mount

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Maverick:
  Fix Released
Status in “linux” source package in Natty:
  Fix Released

Bug description:
  Inserting an sd card does not cause the card to be mounted
  automatically. Nothing is displayed to the use in regard to the sd
  card. Card works perfectly on multiple other machines.

  Card: Kingston 2GB micro SD card (model SDC/2GB)

  dmesg snip: 
  [ 8536.437530] mmc0: ADMA error
  [ 8536.439580] mmc0: Got data interrupt 0x0018 even though no data 
operation was in progress.
  [ 8536.440741] mmc0: error -5 whilst initialising SD card

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: linux-image-2.6.35-22-generic 2.6.35-22.33
  Regression: No
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1498 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0x5696 irq 47'
 Mixer name : 'Intel IbexPeak HDMI'
 Components : 'HDA:111d76d5,1028040b,00100104 
HDA:80862804,80860101,0010'
 Controls  : 22
 Simple ctrls  : 11
  Date: Mon Mar  7 13:29:24 2011
  HibernationDevice: RESUME=UUID=5fb4d9d1-02a8-4ad6-9e81-6971e122d37a
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  Lsusb:
   Bus 002 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E6510
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic 
root=UUID=a72f2ab3-fea2-4b13-ba07-1a50f37d9dde ro quiet splash
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: linux-firmware 1.38
  RfKill:
   
  SourcePackage: linux
  dmi.bios.date: 11/20/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 02K3Y4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd11/20/2010:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/730820/+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 730820] Re: [Latitude E6510] ricoh e822: SD card is unable to mount

2014-08-17 Thread Horst Schirmeier
This bug seems to have reappeared with Ubuntu 14.04 (linux-image-
extra-3.13.0-34-generic 3.13.0-34.60). I have a Dell Latitude E6400 with
SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host
Adapter (rev 21) (1180:0822). The workaround in comment #3 fixes the
problem. Please reopen.

-- 
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/730820

Title:
  [Latitude E6510] ricoh e822: SD card is unable to mount

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Maverick:
  Fix Released
Status in “linux” source package in Natty:
  Fix Released

Bug description:
  Inserting an sd card does not cause the card to be mounted
  automatically. Nothing is displayed to the use in regard to the sd
  card. Card works perfectly on multiple other machines.

  Card: Kingston 2GB micro SD card (model SDC/2GB)

  dmesg snip: 
  [ 8536.437530] mmc0: ADMA error
  [ 8536.439580] mmc0: Got data interrupt 0x0018 even though no data 
operation was in progress.
  [ 8536.440741] mmc0: error -5 whilst initialising SD card

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: linux-image-2.6.35-22-generic 2.6.35-22.33
  Regression: No
  Reproducible: Yes
  ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
  Uname: Linux 2.6.35-22-generic i686
  NonfreeKernelModules: wl
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
  Architecture: i386
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  u  1498 F pulseaudio
  CRDA: Error: [Errno 2] No such file or directory
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0x5696 irq 47'
 Mixer name : 'Intel IbexPeak HDMI'
 Components : 'HDA:111d76d5,1028040b,00100104 
HDA:80862804,80860101,0010'
 Controls  : 22
 Simple ctrls  : 11
  Date: Mon Mar  7 13:29:24 2011
  HibernationDevice: RESUME=UUID=5fb4d9d1-02a8-4ad6-9e81-6971e122d37a
  InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007)
  Lsusb:
   Bus 002 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications 
Processor
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E6510
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic 
root=UUID=a72f2ab3-fea2-4b13-ba07-1a50f37d9dde ro quiet splash
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: linux-firmware 1.38
  RfKill:
   
  SourcePackage: linux
  dmi.bios.date: 11/20/2010
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 02K3Y4
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd11/20/2010:svnDellInc.:pnLatitudeE6510:pvr0001:rvnDellInc.:rn02K3Y4:rvrA02:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E6510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/730820/+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