[Kernel-packages] [Bug 1336541] Re: No TRIM via USB

2016-10-30 Thread Elias Abacioglu
similar or same bug reported at upstream
https://bugzilla.kernel.org/show_bug.cgi?id=83181

** Bug watch added: Linux Kernel Bug Tracker #83181
   http://bugzilla.kernel.org/show_bug.cgi?id=83181

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

Title:
  No TRIM via USB

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  As USB attached SSDs are becoming quite big and affordable, along comes the 
idea of installing systems on these.
  But with current USB drivers, some functionality seems to be missing from USB 
subsystem.

  The system does not recognize it is an SSD, but it is corrected manually:
  # cat /etc/udev/rules.d/10-forcessd.rules
  SUBSYSTEM=="block", ATTRS{vendor}=="SanDisk", ATTRS{model}=="Extreme", 
KERNEL=="sd?", ATTR{queue/rotational}="0"

  # cat /sys/block/sdb/queue/rotational
  0

  Checked hdparm, it is saying I have TRIM on the device:
  # hdparm -I /dev/sdb

  /dev/sdb:

  ATA device, with non-removable media
   Model Number:   SanDisk pSSD
  (...)
  Commands/features:
   Enabled  Supported:
  (...)
  * Data Set Management TRIM supported (limit 8 blocks)
  * Deterministic read ZEROs after TRIM
  (...)

  Here is appropriate dmesg:
  [3.815604] usb 2-8: Manufacturer: SunplusIT INC.
  [4.122002] usb 3-3: new SuperSpeed USB device number 2 using xhci_hcd
  [4.138402] usb 3-3: New USB device found, idVendor=0781, idProduct=5580
  [4.138404] usb 3-3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [4.138405] usb 3-3: Product: Extreme
  [4.138406] usb 3-3: Manufacturer: SanDisk
  [4.138407] usb 3-3: SerialNumber: AA011109131654094942
  [4.141393] usb-storage 3-3:1.0: USB Mass Storage device detected
  [4.141431] scsi0 : usb-storage 3-3:1.0
  [4.141703] usbcore: registered new interface driver usb-storage

  And:
  [5.331311] sd 0:0:0:0: [sdb] 122544516 512-byte logical blocks: (62.7 
GB/58.4 GiB)
  [5.331608] sd 0:0:0:0: [sdb] Write Protect is off
  [5.331611] sd 0:0:0:0: [sdb] Mode Sense: 33 00 00 08
  [5.331855] sd 0:0:0:0: [sdb] Write cache: disabled, read cache: enabled, 
doesn't support DPO or FUA
  [5.339849]  sdb: sdb1 sdb2 sdb3 < sdb5 >
  [5.340783] sd 0:0:0:0: [sdb] Attached SCSI disk

  From here I'll be using /boot formatted to ext4 to eliminate luks,lvm
  and btrfs from the equasion:

  # mount |grep sdb2
  /dev/sdb2 on /boot type ext4 (rw,noexec,discard)

  # fstrim -v /boot/
  fstrim: /boot/: FITRIM ioctl failed: Operation not supported

  # strace fstrim -v /boot/
  (...)
  open("/boot/", O_RDONLY)= 3
  ioctl(3, FITRIM, 0x7fffdded85c0)= -1 EOPNOTSUPP (Operation not 
supported)
  (...)

  During debugging, I've tried compiling a kernel with UAS module to
  check, it booted, system was g changed with the trim - as it wouldn't
  been used at all.

  Any ideas why TRIM is not working on USB?
  Any timeframes for possible fix?
  Any workarounds maybe?
  --- 
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  dome   2460 F pulseaudio
   /dev/snd/pcmC1D0p:   dome   2460 F...m pulseaudio
   /dev/snd/controlC0:  dome   2460 F pulseaudio
  DistroRelease: Ubuntu 14.04
  HibernationDevice: RESUME=UUID=bafebd1d-6988-438f-afd4-b41bb8608616
  InstallationDate: Installed on 2014-06-12 (56 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 20AR001AUK
  Package: linux (not installed)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-24-generic 
root=/dev/mapper/system-root ro rootflags=subvol=@ 
cryptopts=target=crypter,source=/dev/disk/by-uuid/dc149cdf-62f9-4e29-a048-dd0403f51d56,lvm=system,discard
 quiet splash crashkernel=384M-:128M vt.handoff=7
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-24-generic N/A
   linux-backports-modules-3.13.0-24-generic  N/A
   linux-firmware 1.127.5
  Tags:  trusty
  Uname: Linux 3.13.0-24-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  _MarkForUpload: True
  dmi.bios.date: 03/28/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GJET75WW (2.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AR001AUK
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 PRO
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  

[Kernel-packages] [Bug 1483214] Re: ipmi_si module spams kernel log with "ipmi_si 00:05: Could not set the global enables: 0xcc."

2016-04-27 Thread Elias Abacioglu
I'm running trusty with wily kernel 4.2.0-35-generic, linux-generic-lts-
wily.

It's also affected by the same problem.

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

Title:
  ipmi_si module spams kernel log with "ipmi_si 00:05: Could not set the
  global enables: 0xcc."

Status in linux package in Ubuntu:
  Fix Released
Status in openipmi package in Ubuntu:
  Invalid
Status in linux source package in Vivid:
  Fix Released
Status in openipmi source package in Vivid:
  Invalid

Bug description:
  Hello,

  after upgrading my system to 14.04.3 LTS and installing the Vivid-LTS-
  Enablement-Stack the kernel log of my system is spammed with the
  following message by the "impi_si" kernel module:

  ...
  [ 2268.244383] ipmi_si 00:05: Could not set the global enables: 0xcc.
  [ 2269.451974] ipmi_si 00:05: Could not set the global enables: 0xcc.
  [ 2270.252290] ipmi_si 00:05: Could not set the global enables: 0xcc.
  [ 2271.452749] ipmi_si 00:05: Could not set the global enables: 0xcc.
  [ 2272.253057] ipmi_si 00:05: Could not set the global enables: 0xcc.
  ...

  This bug is already known to the ipmi_si kernel module maintainer and
  seems to be fixed in 4.0+ kernels.

  Is it possible to backport this fix to the Vivid 3.19 kernel?

  Please see this mail thread: https://www.mail-archive.com/openipmi-
  develo...@lists.sourceforge.net/msg02425.html

  IPMI functionality seems to be unaffected by this bug but as I said it
  spams the kernel log and that is rather annoying.

  System information:

  lsb_release -rd:
  Description:Ubuntu 14.04.3 LTS
  Release:14.04

  apt-cache policy openipmi:

  openipmi:
Installiert:   2.0.18-0ubuntu7.1
Installationskandidat: 2.0.18-0ubuntu7.1
Versionstabelle:
   *** 2.0.18-0ubuntu7.1 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty-updates/main 
amd64 Packages
  100 /var/lib/dpkg/status
   2.0.18-0ubuntu7 0
  500 http://de.archive.ubuntu.com/ubuntu/ trusty/main amd64 
Packages

  Greetings,
  Felix

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