from:"Kent Baxley"

[Kernel-packages] [Bug 1206602] Re: Add hotplug support for Micron's PCIe-SSD devices

2014-09-03 Thread Kent Baxley

SRSI Support was added to the upstream kernel in November 2013.  The
Ubuntu Trusty kernels got this support for 'free'.

Checked the source code for Trusty to verify it was there:

http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-
trusty.git;a=commitdiff;h=8f8b899563f28ef26e381a6eb90d12dead77389f

Closing out as fix released.

** Changed in: dell-poweredge
   Status: In Progress = Fix Released

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

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

Title:
  Add hotplug support for Micron's PCIe-SSD devices

Status in The Dell PowerEdge project:
  Fix Released
Status in “linux” package in Ubuntu:
  Fix Released

Bug description:
  Add hotplug (SRSI) support for Micron's PCIe-SSD devices (mtip32xx
  driver).

  The patches that enable this functionality have been submitted to the
  linux-block mailing list:

  http://marc.info/?l=linux-kernelm=136812385512296

  Micron has been in direct conversations with Jens Axboe to merge these
  patches upstream, as far as I know there are no objections from the
  community and should just be a matter of time before they are merged
  upstream. They may not land in kernel 3.11, probably looking at 3.12.

  I tested these patches with the 3.10.2 kernel and both hot-removal and
  hot-insertion work ok. I had to pass the pci=pcie_bus_perf kernel
  parameter to avoid MaxPayload issues.

  Adding support in Saucy will pave the way for established support in
  the 14.04 LTS release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1206602/+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 1284334] Re: (regression?) openipmi fails to start on kernels 3.13.0-11-generic and 3.13.0-12-generic

2014-08-26 Thread Kent Baxley

The OpenIPMI portion of this issue now seems to be fixed in Utopic 
Trusty and I will try and verify the fix for Precise:

https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1309860

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

Title:
  (regression?) openipmi fails to start on kernels 3.13.0-11-generic and
  3.13.0-12-generic

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  When updating 14.04 to 3.13.0-12 I noticed that the openipmi service
  failed to start on reboot.  After running 'sudo service openipmi
  start', the service would still fail to start because it failed to
  load the ipmi modules.

  Kernel 3.13.0-8, which was previously on the system, works fine.

  I also  updated to linux-image 3.14.0-031400rc4-generic from the
  mainline site and the openipmi service starts working again.

  Steps to reproduce:

  Install 14.04 server, amd64 version.  Make sure kernel 3.13.0-11 or -12 are 
installed
  Install openipmi.
  Try to start the openipmi service (sudo service ipmi start)

  Actual results:
  openipmi fails to load the ipmi modules and the service fails to start

  Expected results:
  openipmi starts without problems. 

  This is an important issue because tools like ipmitool and Dell's
  iDRAC service module for Ubuntu rely on a working openipmi in order to
  function properly.  The 3.14 kernels seem to have a fix of some sort
  in them.

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

Re: [Kernel-packages] [Bug 1305522] Re: Backport Synaptics HID touchpad driver for 14.04

2014-07-25 Thread Kent Baxley

The patch does not improve this.

On Fri, Jul 25, 2014 at 10:45 AM, Tim Kuijsten
1305...@bugs.launchpad.net wrote:
 @Andy or anyone: can you maybe comment about false palm recognition and
 the disable keyboard while typing feature when holding both hands at
 the keyboard (and doing terminal work for example). Does this patch make
 any improvements in that area? Older kernels really suck at this and
 frustrated a smooth workflow for me.

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1305522

 Title:
   Backport Synaptics HID touchpad driver for 14.04

 Status in “linux” package in Ubuntu:
   Fix Released
 Status in “linux” source package in Trusty:
   Fix Released

 Bug description:
   Synaptics just upstreamed a new set of HID touchpad driver:

   
 http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.16/rmi4id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736

   It's better we can have it in 14.04 .

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


-- 
Kent Baxley
Field Engineer, Canonical
kent.bax...@canonical.com

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

Title:
  Backport Synaptics HID touchpad driver for 14.04

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Trusty:
  Fix Released

Bug description:
  Synaptics just upstreamed a new set of HID touchpad driver:

  
http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.16/rmi4id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736

  It's better we can have it in 14.04 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305522/+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 1305522] Re: Backport Synaptics HID touchpad driver for 14.04

2014-07-21 Thread Kent Baxley

@Gabriele and anyone else that sees power consumption problems,

Please open a separate bug on the power consumption.  This issue is to
inclue driver support for the touchpad, which Synaptics continues to
work on / refine upstream.

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

Title:
  Backport Synaptics HID touchpad driver for 14.04

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Trusty:
  Fix Released

Bug description:
  Synaptics just upstreamed a new set of HID touchpad driver:

  
http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.16/rmi4id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736

  It's better we can have it in 14.04 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305522/+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 1342153] [NEW] Enable CONFIG_GPIO_SYSFS option in the Kernel

2014-07-15 Thread Kent Baxley

Public bug reported:

It appears we don't set the CONFIG_GPIO_SYSFS on Trusty (or Utopic?) for
x86.

By enabled, I mean:

CONFIG_GPIO_SYSFS=y

This option (along with a few gpio devices) is needed to enable
programming of such things as the I2C Mux through via the CPLDs on some
OEM 'whitebox' switches that will leverage Software Defined Networking.

This option can, of course, be set and users can build their own
kernels, but, if at all possible they'd like to keep this as stock as
they can.

config GPIO_SYSFS
bool /sys/class/gpio/... (sysfs interface)
depends on SYSFS
help
  Say Y here to add a sysfs interface for GPIOs.

  This is mostly useful to work around omissions in a system's
  kernel support.  Those are common in custom and semicustom
  hardware assembled using standard kernels with a minimum of
  custom patches.  In those cases, userspace code may import
  a given GPIO from the kernel, if no kernel driver requested it.

  Kernel drivers may also request that a particular GPIO be
  exported to userspace; this can be useful when debugging.

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

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

Title:
  Enable CONFIG_GPIO_SYSFS option in the Kernel

Status in “linux” package in Ubuntu:
  New

Bug description:
  It appears we don't set the CONFIG_GPIO_SYSFS on Trusty (or Utopic?)
  for x86.

  By enabled, I mean:

  CONFIG_GPIO_SYSFS=y

  This option (along with a few gpio devices) is needed to enable
  programming of such things as the I2C Mux through via the CPLDs on
  some OEM 'whitebox' switches that will leverage Software Defined
  Networking.

  This option can, of course, be set and users can build their own
  kernels, but, if at all possible they'd like to keep this as stock as
  they can.

  config GPIO_SYSFS
  bool /sys/class/gpio/... (sysfs interface)
  depends on SYSFS
  help
Say Y here to add a sysfs interface for GPIOs.

This is mostly useful to work around omissions in a system's
kernel support.  Those are common in custom and semicustom
hardware assembled using standard kernels with a minimum of
custom patches.  In those cases, userspace code may import
a given GPIO from the kernel, if no kernel driver requested it.

Kernel drivers may also request that a particular GPIO be
exported to userspace; this can be useful when debugging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342153/+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 1342153] Re: Enable CONFIG_GPIO_SYSFS option in the Kernel

2014-07-15 Thread Kent Baxley

Request to turn on a kernel config option.  No logs required.

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

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

Title:
  Enable CONFIG_GPIO_SYSFS option in the Kernel

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  It appears we don't set the CONFIG_GPIO_SYSFS on Trusty (or Utopic?)
  for x86.

  By enabled, I mean:

  CONFIG_GPIO_SYSFS=y

  This option (along with a few gpio devices) is needed to enable
  programming of such things as the I2C Mux through via the CPLDs on
  some OEM 'whitebox' switches that will leverage Software Defined
  Networking.

  This option can, of course, be set and users can build their own
  kernels, but, if at all possible they'd like to keep this as stock as
  they can.

  config GPIO_SYSFS
  bool /sys/class/gpio/... (sysfs interface)
  depends on SYSFS
  help
Say Y here to add a sysfs interface for GPIOs.

This is mostly useful to work around omissions in a system's
kernel support.  Those are common in custom and semicustom
hardware assembled using standard kernels with a minimum of
custom patches.  In those cases, userspace code may import
a given GPIO from the kernel, if no kernel driver requested it.

Kernel drivers may also request that a particular GPIO be
exported to userspace; this can be useful when debugging.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1342153/+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 1305522] Re: Backport Synaptics HID touchpad driver for 14.04

2014-07-01 Thread Kent Baxley

@Sarubh,

Please file a separate bug for your issue as your touchpad does not
appear to be the same as what's being worked on here.  Alternatively,
you can add your comments to this bug, which I think covers your
touchpad device:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1307015

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

Title:
  Backport Synaptics HID touchpad driver for 14.04

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Trusty:
  Fix Released

Bug description:
  Synaptics just upstreamed a new set of HID touchpad driver:

  
http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.16/rmi4id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736

  It's better we can have it in 14.04 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305522/+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 1152580] Re: [Dell PowerEdge M520] BCM95720 Network disconnects and resets

2014-06-27 Thread Kent Baxley

*** This bug is a duplicate of bug 1331513 ***
https://bugs.launchpad.net/bugs/1331513

** This bug has been marked a duplicate of bug 1331513
   14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720

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

Title:
  [Dell PowerEdge M520] BCM95720 Network disconnects and resets

Status in The Dell PowerEdge project:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  The server is constantly going on and offline here are messages and hardware 
Details:
  [4.394703] tg3 :02:00.0: eth0: Tigon3 [partno(BCM95720) rev 572] 
(PCI Express) MAC address 90:b1:1c:0d:d4:aa
  [4.394713] tg3 :02:00.0: eth0: attached PHY is 5720C 
(10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
  [4.394720] tg3 :02:00.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] 
ASF[1] TSOcap[1]
  [4.394726] tg3 :02:00.0: eth0: dma_rwctrl[0001] dma_mask[64-bit]

  The dump to dmesg:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152580/+attachment/3939814/+files/log

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-38-generic 3.2.0-38.61
  ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37
  Uname: Linux 3.2.0-38-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 Mar  8 13:26 seq
   crw-rw---T 1 root audio 116, 33 Mar  8 13:26 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Date: Fri Mar  8 14:21:45 2013
  HibernationDevice: RESUME=UUID=f9a32355-70b4-462b-a01e-2665b81b2ec0
  InstallationMedia: Ubuntu-Server 12.04.1 LTS Precise Pangolin - Release 
amd64 (20120817.3)
  MachineType: Dell Inc. PowerEdge R520
  MarkForUpload: True
  PciMultimedia:

  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-38-generic 
root=UUID=0c0140bd-05eb-4e5c-9596-1cf4dee88ae4 ro
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-38-generic N/A
   linux-backports-modules-3.2.0-38-generic  N/A
   linux-firmware1.79.1
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.5
  dmi.board.name: 051XDX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.5:bd08/21/2012:svnDellInc.:pnPowerEdgeR520:pvr:rvnDellInc.:rn051XDX:rvrA00:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R520
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1152580/+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 1175278] Re: Please apply new upstream patches for mtip32xx

2014-06-27 Thread Kent Baxley

Now that 12.04.4 is out, we can close this as the patches are in the LTS
Enablement kernels.

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

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

Title:
  Please apply new upstream patches for mtip32xx

Status in The Dell PowerEdge project:
  Fix Released
Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Raring:
  Won't Fix

Bug description:
  Dell has requested that the latest batch of patches for the mtip32xx
  driver be applied to Ubuntu.  We should get these for free with 13.10.

  If possible, Dell would like to have them backported to 13.04, 12.10,
  and 12.04.2.  If 12.10 / 12.04.2 is not possible, then Dell can also
  wait until 12.04.3 with the HWE kernel from 13.04.

  The requested commits are everything after the Fix padding issue
  found here:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/block/mtip32xx

  Individual list of commits:

  
  mtip32xx: fix for a driver hang after a command timeout:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=47cd4b3c7e80cc8d5ac82930c5af835870b5aba1

  mtip32xx: fix for crash when device surprise removed during rebuild:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=58c49df378cde4ff64172483d593a1a5689c13a8

  mtip32xx: add work queue and NUMA support:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=16c906e51c6f08a15763a85b5686e1ded35e77ab

  mtip32xx: add TRIM support:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=152834694dcb90d3088bc77fa436755c66553929

  drivers/block/mtip32xx/mtip32xx.c:4029:1: sparse: symbol 'mtip_workq_sdbf0' 
was not declared. Should it be static?
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=25bac122b8d874d625982aead1974be819eca841

  drivers/block/mtip32xx/mtip32xx.c:1726:5: sparse: symbol 'mtip_send_trim' was 
not declared. Should it be static?
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=478c030eecbec927d62561c5f48a4515ea0fa21a

  drivers/block/mtip32xx: add missing GENERIC_HARDIRQS dependency
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=1262e24a59a052f9a98383e47e7c903712490d5c

  Merge branch 'stable/for-jens-3.9' of 
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen into for-3.9/drivers
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=d4308febf3551d46884561b7c3fdd62ad3ca7ff2

  mtip32xx: fix error return code in mtip_pci_probe()
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=d137c8306c748d89260400176613b5a85574b255

  mtip32xx: recovery from command timeout
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=d0d096b1d8b97172cee953f1a00b7d4379d398da

  mtip32xx: return 0 from pci probe in case of rebuild
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=6b06d35f3f63dbfde71c792b8584225f3d1fc7f2

  mtip32xx: Add debugfs entry device_status
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=0caff00390db41c98976e65f2ebc3eeaa4861358

  mtip32xx: fix two smatch warnings
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=c66bb3f075cfe2d17b2427e96e043622db02759c

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1175278/+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 1331513] Re: 14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720

2014-06-23 Thread Kent Baxley

Working on a reproducer. I've been able to set up the following:

A Xen HVM guest booting off of an iscsi-attached LVM LUN.
Guest is running Wheezy.
Dom0 is 12.04 on a PowerEdge R620, running the 3.11-based LTS kernels.
The eth1 NIC is being used for the iscsi traffic. This is one of the tg3-based
onboard NICs.

I've so far been importing different databases into the running mysql
database on the debian guest. No crashes, yet, but I'll keep playing
around with different database dumps to see if I can trigger anything.

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

Title:
14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720

Status in The Dell PowerEdge project:
Triaged
Status in “linux” package in Ubuntu:
Triaged
Status in “linux-lts-saucy” package in Ubuntu:
Confirmed

Bug description:
we have a problem with Dell PowerEdge machines, having the Broadcom
5720 chip. We have this problem on generation 12 systems, across
different models (R420, R620), with several combinations of bios
firmwares, lifecycle firmwares, etc... We see this on several versions
of the linux kernel, ranging from 3.2.x up tot 3.11, with several
versions of the tg3 driver, including a manually compiled latest
version (3.133d) loaded in a 3.11. The latest machine, where we can
reproduce the problem has Ubuntu Precise installed, but we also see
this behaviour on Debian machines. We run Xen on it, running HVM hosts
on it. Storage is handled over iSCSI (and it is the iSCSI interface we
can trigger this bug on in a reproducible way, while we have the
impression it also happens on other interfaces, but there we don't
have a solid case where we have e reproducible setup).

All this info actually points into the direction of the tg3 driver
and/or hardware below it not handling certain datastreams or data
patterns correctly, and finally crashing the system. It seems
unrelated to the version of kernel running, xen-version running,
amount of VM's running, firmwares and revisions running, etc...

We have been trying to pinpoint this for over a year now, being unable
to actually create a scenario where we could reproduce this. As of
this week, we finally found a specific setup where we could trigger
the error within a reasonable time.

The error is triggered by running a certain VM on the Xen stack, and
inside that VM, importing a mysqldump in a running mysql on that VM.
The VM has it's traffic on an iSCSI volume, so this effectually
generates a datastream over the eth1 interface of the machine. Within
a short amount of time, the system will crash in 2 steps. We first see
a timeout on the tg3 driver on the eth1 interface (dmesg output
section attached). This sometimes repeats two or three times, and
finally, step 2, the machine freezes and reboots.

While debugging, we noticed that the bug goes away when we disable sg
offloading with ethtool.

If you need any additional info, feel free to ask.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.11.0-19-generic 3.11.0-19.33~precise1
ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5
Uname: Linux 3.11.0-19-generic x86_64
AlsaDevices:
total 0
crw-rw---T 1 root audio 116, 1 Jun 18 16:36 seq
crw-rw---T 1 root audio 116, 33 Jun 18 16:36 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211
not found.
Date: Wed Jun 18 16:47:27 2014
HibernationDevice: RESUME=UUID=f3577e02-64e3-4cab-b6e7-f30efa111565
InstallationMedia: Ubuntu-Server 12.04.4 LTS Precise Pangolin - Release
amd64 (20140204)
MachineType: Dell Inc. PowerEdge R420
MarkForUpload: True
PciMultimedia:

ProcFB:

ProcKernelCmdLine: placeholder root=UUID=bbc71780-90bf-4647-b579-e48d5d8c2bce
ro vga=0x317
RelatedPackageVersions:
linux-restricted-modules-3.11.0-19-generic N/A
linux-backports-modules-3.11.0-19-generic N/A
linux-firmware 1.79.12
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux-lts-saucy
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/20/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.1.2
dmi.board.name: 0JD6X3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr2.1.2:bd01/20/2014:svnDellInc.:pnPowerEdgeR420:pvr:rvnDellInc.:rn0JD6X3:rvrA00:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R420
dmi.sys.vendor: Dell Inc.

To manage

[Kernel-packages] [Bug 1331513] Re: 14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720

2014-06-23 Thread Kent Baxley

@wonko,

If there's any more specific information about the Xen VM, please let me
know. What I'm looking for are any special storage or network drivers
that the VM is using outside of what the standard Xen VM would use. If
there's nothing special about the VM in that respect, then I'll continue
with what I have. Also, the Xen config file for the Debian guest you're
using might be helpful. No problem if you can't get if for me, though.

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

Title:
14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720

Status in The Dell PowerEdge project:
Triaged
Status in “linux” package in Ubuntu:
Triaged
Status in “linux-lts-saucy” package in Ubuntu:
Confirmed

While debugging, we noticed that the bug goes away when we disable sg
offloading with ethtool.

If you need any additional info, feel free to ask.

ProcFB:

To manage notifications about this bug go to:

[Kernel-packages] [Bug 1331513] Re: 14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720

2014-06-20 Thread Kent Baxley

Understood. I didn't realize it was *that* specific. How big is the
database you are importing and is there anything special about the VM
itself? I'll try and get this as close as possible.

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

Title:
14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720

Status in The Dell PowerEdge project:
Triaged
Status in “linux” package in Ubuntu:
Triaged
Status in “linux-lts-saucy” package in Ubuntu:
Confirmed

While debugging, we noticed that the bug goes away when we disable sg
offloading with ethtool.

If you need any additional info, feel free to ask.

ProcFB:

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1331513/+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 1331513] Re: 14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720

2014-06-19 Thread Kent Baxley

Bernard,

I may also want to go ahead and get a soup-to-nuts list of how to set up
a machine to reproduce this.  I've got an R620 and access to an iscsi
volume in my lab.  I'm trying currently to reproduce on a simpler scale,
but, not having much luck at this time (which is no  surprise).

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

Title:
  14e4:165f tg3 eth1: transmit timed out, resetting on BCM5720

Status in The Dell PowerEdge project:
  Triaged
Status in “linux” package in Ubuntu:
  Triaged
Status in “linux-lts-saucy” package in Ubuntu:
  Confirmed

Bug description:
  we have a problem with Dell PowerEdge machines, having the Broadcom
  5720 chip. We have this problem on generation 12 systems, across
  different models (R420, R620), with several combinations of bios
  firmwares, lifecycle firmwares, etc... We see this on several versions
  of the linux kernel, ranging from 3.2.x up tot 3.11, with several
  versions of the tg3 driver, including a manually compiled latest
  version (3.133d) loaded in a 3.11. The latest machine, where we can
  reproduce the problem has Ubuntu Precise installed, but we also see
  this behaviour on Debian machines. We run Xen on it, running HVM hosts
  on it. Storage is handled over iSCSI (and it is the iSCSI interface we
  can trigger this bug on in a reproducible way, while we have the
  impression it also happens on other interfaces, but there we don't
  have a solid case where we have e reproducible setup).

  All this info actually points into the direction of the tg3 driver
  and/or hardware below it not handling certain datastreams or data
  patterns correctly, and finally crashing the system. It seems
  unrelated to the version of kernel running, xen-version running,
  amount of VM's running, firmwares and revisions running, etc...

  We have been trying to pinpoint this for over a year now, being unable
  to actually create a scenario where we could reproduce this. As of
  this week, we finally found a specific setup where we could trigger
  the error within a reasonable time.

  The error is triggered by running a certain VM on the Xen stack, and
  inside that VM, importing a mysqldump in a running mysql on that VM.
  The VM has it's traffic on an iSCSI volume, so this effectually
  generates a datastream over the eth1 interface of the machine.  Within
  a short amount of time, the system will crash in 2 steps. We first see
  a timeout on the tg3 driver on the eth1 interface (dmesg output
  section attached). This sometimes repeats two or three times, and
  finally, step 2, the machine freezes and reboots.

  While debugging, we noticed that the bug goes away when we disable sg
  offloading with ethtool.

  If you need any additional info, feel free to ask.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.11.0-19-generic 3.11.0-19.33~precise1
  ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 Jun 18 16:36 seq
   crw-rw---T 1 root audio 116, 33 Jun 18 16:36 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed Jun 18 16:47:27 2014
  HibernationDevice: RESUME=UUID=f3577e02-64e3-4cab-b6e7-f30efa111565
  InstallationMedia: Ubuntu-Server 12.04.4 LTS Precise Pangolin - Release 
amd64 (20140204)
  MachineType: Dell Inc. PowerEdge R420
  MarkForUpload: True
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: placeholder root=UUID=bbc71780-90bf-4647-b579-e48d5d8c2bce 
ro vga=0x317
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-19-generic N/A
   linux-backports-modules-3.11.0-19-generic  N/A
   linux-firmware 1.79.12
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux-lts-saucy
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.2
  dmi.board.name: 0JD6X3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.2:bd01/20/2014:svnDellInc.:pnPowerEdgeR420:pvr:rvnDellInc.:rn0JD6X3:rvrA00:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R420
  dmi.sys.vendor: Dell Inc.

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

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

[Kernel-packages] [Bug 1331513] Re: tg3 eth1: transmit timed out, resetting on BCM5720

2014-06-18 Thread Kent Baxley

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

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

Title:
  tg3 eth1: transmit timed out, resetting on BCM5720

Status in The Dell PowerEdge project:
  Incomplete
Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux-lts-saucy” package in Ubuntu:
  Confirmed

Bug description:
  we have a problem with Dell PowerEdge machines, having the Broadcom
  5720 chip. We have this problem on generation 12 systems, across
  different models (R420, R620), with several combinations of bios
  firmwares, lifecycle firmwares, etc... We see this on several versions
  of the linux kernel, ranging from 3.2.x up tot 3.11, with several
  versions of the tg3 driver, including a manually compiled latest
  version (3.133d) loaded in a 3.11. The latest machine, where we can
  reproduce the problem has Ubuntu Precise installed, but we also see
  this behaviour on Debian machines. We run Xen on it, running HVM hosts
  on it. Storage is handled over iSCSI (and it is the iSCSI interface we
  can trigger this bug on in a reproducible way, while we have the
  impression it also happens on other interfaces, but there we don't
  have a solid case where we have e reproducible setup).

  All this info actually points into the direction of the tg3 driver
  and/or hardware below it not handling certain datastreams or data
  patterns correctly, and finally crashing the system. It seems
  unrelated to the version of kernel running, xen-version running,
  amount of VM's running, firmwares and revisions running, etc...

  We have been trying to pinpoint this for over a year now, being unable
  to actually create a scenario where we could reproduce this. As of
  this week, we finally found a specific setup where we could trigger
  the error within a reasonable time.

  The error is triggered by running a certain VM on the Xen stack, and
  inside that VM, importing a mysqldump in a running mysql on that VM.
  The VM has it's traffic on an iSCSI volume, so this effectually
  generates a datastream over the eth1 interface of the machine.  Within
  a short amount of time, the system will crash in 2 steps. We first see
  a timeout on the tg3 driver on the eth1 interface (dmesg output
  section attached). This sometimes repeats two or three times, and
  finally, step 2, the machine freezes and reboots.

  While debugging, we noticed that the bug goes away when we disable sg
  offloading with ethtool.

  If you need any additional info, feel free to ask.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.11.0-19-generic 3.11.0-19.33~precise1
  ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5
  Uname: Linux 3.11.0-19-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 Jun 18 16:36 seq
   crw-rw---T 1 root audio 116, 33 Jun 18 16:36 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Wed Jun 18 16:47:27 2014
  HibernationDevice: RESUME=UUID=f3577e02-64e3-4cab-b6e7-f30efa111565
  InstallationMedia: Ubuntu-Server 12.04.4 LTS Precise Pangolin - Release 
amd64 (20140204)
  MachineType: Dell Inc. PowerEdge R420
  MarkForUpload: True
  PciMultimedia:
   
  ProcFB:
   
  ProcKernelCmdLine: placeholder root=UUID=bbc71780-90bf-4647-b579-e48d5d8c2bce 
ro vga=0x317
  RelatedPackageVersions:
   linux-restricted-modules-3.11.0-19-generic N/A
   linux-backports-modules-3.11.0-19-generic  N/A
   linux-firmware 1.79.12
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux-lts-saucy
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/20/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.1.2
  dmi.board.name: 0JD6X3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.1.2:bd01/20/2014:svnDellInc.:pnPowerEdgeR420:pvr:rvnDellInc.:rn0JD6X3:rvrA00:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R420
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1331513/+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 1305522] Re: Backport Synaptics HID touchpad driver for 14.04

2014-06-02 Thread Kent Baxley

Hi David,  I still can't reproduce any jumpy mouse behavior on my
touchpad, even with your steps.

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

Title:
  Backport Synaptics HID touchpad driver for 14.04

Status in “linux” package in Ubuntu:
  In Progress
Status in “linux” source package in Trusty:
  In Progress

Bug description:
  Synaptics just upstreamed a new set of HID touchpad driver:

  
http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.16/rmi4id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736

  It's better we can have it in 14.04 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305522/+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 1305522] Re: Backport Synaptics HID touchpad driver for 14.04

2014-05-30 Thread Kent Baxley

Hi AceLan,

So far I can't reproduce the jumpy mouse issues.

@David,

If you have any more specifics about what will reproduce it or how long
it takes to see the issue after booting up and loggin in,  I'll be glad
to try it out on my sample here.  I've tried both single-finger tap as
well as doing a physical press on the touchpad itself.

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

Title:
  Backport Synaptics HID touchpad driver for 14.04

Status in “linux” package in Ubuntu:
  In Progress
Status in “linux” source package in Trusty:
  In Progress

Bug description:
  Synaptics just upstreamed a new set of HID touchpad driver:

  
http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.16/rmi4id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736

  It's better we can have it in 14.04 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305522/+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 1305522] Re: Backport Synaptics HID touchpad driver for 14.04

2014-05-29 Thread Kent Baxley

For those with the XPS 13's that still have a PS/2 interface showing up,
it looks as if that doesn't seem to 'break' anything.  The model I have
in the lab has a much older touchpad firmware on it than the ones you
guys have, so, that may be why things are showing up on your systems
like they are.

@Jens, I would probably wait for an official fix rather than try and
build and install your own kernel, especially if you haven't done it
before.  I would, however, give the test kernels a try  here:

http://people.canonical.com/~acelan/bugs/lp1305522/20140523/

The XPS12 has the same i2c touchpad as the XPS13, but, I'm not positive
about whether the touchscreens are the same though.  I may have an XPS12
in the lab that I can try this on, provided it will power up :)

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

Title:
  Backport Synaptics HID touchpad driver for 14.04

Status in “linux” package in Ubuntu:
  In Progress
Status in “linux” source package in Trusty:
  In Progress

Bug description:
  Synaptics just upstreamed a new set of HID touchpad driver:

  
http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.16/rmi4id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736

  It's better we can have it in 14.04 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305522/+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 1305522] Re: Backport Synaptics HID touchpad driver for 14.04

2014-05-29 Thread Kent Baxley

Also for everyone that still sees a PS/2 device in xinput after applying
AceLan's kernels, can you please paste the output of the following
command in this bug?:

dmesg | grep psmouse


lsmod | grep psmouse

Thanks!

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

Title:
  Backport Synaptics HID touchpad driver for 14.04

Status in “linux” package in Ubuntu:
  In Progress
Status in “linux” source package in Trusty:
  In Progress

Bug description:
  Synaptics just upstreamed a new set of HID touchpad driver:

  
http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.16/rmi4id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736

  It's better we can have it in 14.04 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305522/+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 1305522] Re: Backport Synaptics HID touchpad driver for 14.04

2014-05-29 Thread Kent Baxley

Thanks, all.

It turns out on my XPS 13 that I was booted to the wrong kernel, which
is why the PS/2 mouse device wasn't showing up.  Once I booted into
Aclean's test kernel the PS/2 device shows up in xinput.

My dmesg output is the same as what Hans is seeing.  The psmouse module
is loading up but fails to enable the mouse (which makes sense since we
are in i2c mode)...just not sure why it wants to load in the first
place.

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

Title:
  Backport Synaptics HID touchpad driver for 14.04

Status in “linux” package in Ubuntu:
  In Progress
Status in “linux” source package in Trusty:
  In Progress

Bug description:
  Synaptics just upstreamed a new set of HID touchpad driver:

  
http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.16/rmi4id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736

  It's better we can have it in 14.04 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305522/+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 1305522] Re: Backport Synaptics HID touchpad driver for 14.04

2014-05-27 Thread Kent Baxley

AceLan and Arash,

I also have an XPS13 Haswell Edition in the Dell lab.  This unit does
NOT reproduce what Arash is seeing with your test kernel.  In other
words, the PS/2 mouse does not show up in the xinput list.  For my
system, xinput reports things as I expect to see them.

The touchscreen and touchpad are both working great.   Also see my
earlier posts about tests in non-i2c synatpics hardware to ensure that
those devices did not regress.

Arash, did you happen to have any of the earlier workarounds in place
before applying Acelan's kernels, such as blacklisting the i2c_hid
drivers?

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

Title:
  Backport Synaptics HID touchpad driver for 14.04

Status in “linux” package in Ubuntu:
  In Progress
Status in “linux” source package in Trusty:
  In Progress

Bug description:
  Synaptics just upstreamed a new set of HID touchpad driver:

  
http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.16/rmi4id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736

  It's better we can have it in 14.04 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305522/+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 1318477] Re: [Dell XPS 15 9530] Wakes from sleep after exactly 24 hours + 3-5 seconds

2014-05-16 Thread Kent Baxley

Can't reproduce this on an XPS 15 here in the Dell lab.

This one has:

Intel Graphics
Qualcomm Wifi / bluetooth (I think Dell calls this the DW1420 or something like
that)
Quad-core i7
8GB RAM
Seagate 500GB Hybrid drive

I put it to sleep at 14:30 yesterday by closing the lid. At 15:30 today
I checked on the system and looked to see if it maybe woke itself up
along the way. From the log output in pm-suspend.log I saw no evidence
of this in the last 24 hours. The only awake event I got was when I
opened the lid up today.

There is a USB wake setting in the BIOS of my machine that is disabled,
but that's the only wake-related setting I can find. Please let me know
if there's anything else you need on this. Thanks.

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

Title:
[Dell XPS 15 9530] Wakes from sleep after exactly 24 hours + 3-5
seconds

Status in Dell Sputnik:
New
Status in “linux” package in Ubuntu:
Confirmed

Bug description:
Symptoms: The system will wake itself from sleep after very nearly exactly 24
hours, + / - 10 seconds or so. /var/log/pm-suspend.log will show this:
Sat May 10 22:08:49 MDT 2014: performing suspend
Sun May 11 22:08:54 MDT 2014: Awake.

In this case the system has resumed after 24 hours and 5 seconds with
no user request to do so. Steps to reproduce: Suspend machine by
closing lid. The system can be plugged in to charge while it is
suspended, and then subsequently unplugged, but the suspend occurs on
battery power, and when the resume occurs the system is also not
plugged in. I have not tested other permutations. No other action is
necessary. The system will randomly resume 24 hours + 3-5 seconds
later.

---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: dpoler 2444 F pulseaudio
/dev/snd/pcmC1D0p: dpoler 2444 F...m pulseaudio
/dev/snd/controlC0: dpoler 2444 F pulseaudio
CurrentDesktop: Unity
CurrentDmesg:
Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg
-'] failed with exit code 1: comm: /var/log/dmesg: Permission denied
dmesg: write failed: Broken pipe
DistroRelease: Ubuntu 14.04
EcryptfsInUse: Yes
InstallationDate: Installed on 2014-05-06 (6 days ago)
InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Release amd64 (20140417)
MachineType: Dell Inc. XPS 15 9530
NonfreeKernelModules: nvidia
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic.efi.signed
root=UUID=02812295-4462-4c5a-9e17-32d49164caf2 ro acpi=force quiet splash
vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
Tags: trusty
Uname: Linux 3.13.0-24-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: bumblebee libvirtd sudo
WifiSyslog:

_MarkForUpload: True
dmi.bios.date: 09/17/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A00
dmi.board.name: XPS 15 9530
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: Not Specified
dmi.modalias:
dmi:bvnDellInc.:bvrA00:bd09/17/2013:svnDellInc.:pnXPS159530:pvrA00:rvnDellInc.:rnXPS159530:rvrA00:cvnDellInc.:ct8:cvrNotSpecified:
dmi.product.name: XPS 15 9530
dmi.product.version: A00
dmi.sys.vendor: Dell Inc.

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

[Kernel-packages] [Bug 1305522] Re: Backport Synaptics HID touchpad driver for 14.04

2014-05-15 Thread Kent Baxley

Tested here with our lab sample.  Touchscreen is working again and the
touchpad is working even better than it did with the previous test
kernels.

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

Title:
  Backport Synaptics HID touchpad driver for 14.04

Status in “linux” package in Ubuntu:
  In Progress
Status in “linux” source package in Trusty:
  In Progress

Bug description:
  Synaptics just upstreamed a new set of HID touchpad driver:

  
http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.16/rmi4id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736

  It's better we can have it in 14.04 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305522/+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 1305522] Re: Backport Synaptics HID touchpad driver for 14.04

2014-05-15 Thread Kent Baxley

Also tested acelan's kernels with an XPS15 (model 9530) which has the
same touchscreen but a non i2c synaptics touchpad.  The touchscreen and
touchpad both work fine and I don't see an regression in behavior.  This
machine survived 30 S3's.

The Inspiron 14 (3421) with just a non-i2c synaptics touchpad was tested
as well.  No big regressions found on that one either.  Touchpad
continues to function and suspend/resume don't seem to be affected.

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

Title:
  Backport Synaptics HID touchpad driver for 14.04

Status in “linux” package in Ubuntu:
  In Progress
Status in “linux” source package in Trusty:
  In Progress

Bug description:
  Synaptics just upstreamed a new set of HID touchpad driver:

  
http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.16/rmi4id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736

  It's better we can have it in 14.04 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305522/+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 1305522] Re: Backport Synaptics HID touchpad driver for 14.04

2014-04-29 Thread Kent Baxley

Tested an Inspiron 3421, which also has a non-i2c synaptics touchpad.  I
tested the same components as earlier along with suspend and resume.  So
far so good.

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

Title:
  Backport Synaptics HID touchpad driver for 14.04

Status in “linux” package in Ubuntu:
  In Progress
Status in “linux” source package in Trusty:
  In Progress

Bug description:
  Synaptics just upstreamed a new set of HID touchpad driver:

  
http://git.kernel.org/cgit/linux/kernel/git/jikos/hid.git/commit/?h=for-3.16/rmi4id=9fb6bf02e3ad04c20edb8e46536ce3eeda32c736

  It's better we can have it in 14.04 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305522/+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 1284334] Re: (regression?) openipmi fails to start on kernels 3.13.0-11-generic and 3.13.0-12-generic

2014-03-04 Thread Kent Baxley

Ok. I'll not test those if that's the case.

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

Title:
  (regression?) openipmi fails to start on kernels 3.13.0-11-generic and
  3.13.0-12-generic

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  When updating 14.04 to 3.13.0-12 I noticed that the openipmi service
  failed to start on reboot.  After running 'sudo service openipmi
  start', the service would still fail to start because it failed to
  load the ipmi modules.

  Kernel 3.13.0-8, which was previously on the system, works fine.

  I also  updated to linux-image 3.14.0-031400rc4-generic from the
  mainline site and the openipmi service starts working again.

  Steps to reproduce:

  Install 14.04 server, amd64 version.  Make sure kernel 3.13.0-11 or -12 are 
installed
  Install openipmi.
  Try to start the openipmi service (sudo service ipmi start)

  Actual results:
  openipmi fails to load the ipmi modules and the service fails to start

  Expected results:
  openipmi starts without problems. 

  This is an important issue because tools like ipmitool and Dell's
  iDRAC service module for Ubuntu rely on a working openipmi in order to
  function properly.  The 3.14 kernels seem to have a fix of some sort
  in them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284334/+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 1284334] Re: (regression?) openipmi fails to start on kernels 3.13.0-11-generic and 3.13.0-12-generic

2014-03-03 Thread Kent Baxley

Hi Joseph,

Thanks.  I can check the 3.14rc1 kernel and see.  I'll also be glad to
try out a test kernel from you with the handler set back to module.

I'll let you know as soon as I find something out with 3.14rc1

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

Title:
  (regression?) openipmi fails to start on kernels 3.13.0-11-generic and
  3.13.0-12-generic

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  When updating 14.04 to 3.13.0-12 I noticed that the openipmi service
  failed to start on reboot.  After running 'sudo service openipmi
  start', the service would still fail to start because it failed to
  load the ipmi modules.

  Kernel 3.13.0-8, which was previously on the system, works fine.

  I also  updated to linux-image 3.14.0-031400rc4-generic from the
  mainline site and the openipmi service starts working again.

  Steps to reproduce:

  Install 14.04 server, amd64 version.  Make sure kernel 3.13.0-11 or -12 are 
installed
  Install openipmi.
  Try to start the openipmi service (sudo service ipmi start)

  Actual results:
  openipmi fails to load the ipmi modules and the service fails to start

  Expected results:
  openipmi starts without problems. 

  This is an important issue because tools like ipmitool and Dell's
  iDRAC service module for Ubuntu rely on a working openipmi in order to
  function properly.  The 3.14 kernels seem to have a fix of some sort
  in them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284334/+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 1284334] Re: (regression?) openipmi fails to start on kernels 3.13.0-11-generic and 3.13.0-12-generic

2014-03-03 Thread Kent Baxley

Trusty 3.13.0-14-generic config shows IPMI_HANDLER option set to Y:

CONFIG_ACPI_IPMI=m
CONFIG_IPMI_HANDLER=y
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m

..with the 3.13.0-8 kernel it is set to m, and this was the last
kernel that I ran where openipmi didn't have issues


Joseph's test kernel shows this and it works as expected with openipmi in that 
the service starts properly.  IPMI_HANDLER is set to 'm':

CONFIG_ACPI_IPMI=m
CONFIG_IPMI_HANDLER=y
# CONFIG_IPMI_PANIC_EVENT is not set
CONFIG_IPMI_DEVICE_INTERFACE=m
CONFIG_IPMI_SI=m
CONFIG_IPMI_WATCHDOG=m
CONFIG_IPMI_POWEROFF=m

I will test rc1 tomorrow as I ran out of time today.

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

Title:
  (regression?) openipmi fails to start on kernels 3.13.0-11-generic and
  3.13.0-12-generic

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  When updating 14.04 to 3.13.0-12 I noticed that the openipmi service
  failed to start on reboot.  After running 'sudo service openipmi
  start', the service would still fail to start because it failed to
  load the ipmi modules.

  Kernel 3.13.0-8, which was previously on the system, works fine.

  I also  updated to linux-image 3.14.0-031400rc4-generic from the
  mainline site and the openipmi service starts working again.

  Steps to reproduce:

  Install 14.04 server, amd64 version.  Make sure kernel 3.13.0-11 or -12 are 
installed
  Install openipmi.
  Try to start the openipmi service (sudo service ipmi start)

  Actual results:
  openipmi fails to load the ipmi modules and the service fails to start

  Expected results:
  openipmi starts without problems. 

  This is an important issue because tools like ipmitool and Dell's
  iDRAC service module for Ubuntu rely on a working openipmi in order to
  function properly.  The 3.14 kernels seem to have a fix of some sort
  in them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284334/+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 1284334] Re: (regression?) openipmi fails to start on kernels 3.13.0-11-generic and 3.13.0-12-generic

2014-02-28 Thread Kent Baxley

Any updates on this?

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

Title:
  (regression?) openipmi fails to start on kernels 3.13.0-11-generic and
  3.13.0-12-generic

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  When updating 14.04 to 3.13.0-12 I noticed that the openipmi service
  failed to start on reboot.  After running 'sudo service openipmi
  start', the service would still fail to start because it failed to
  load the ipmi modules.

  Kernel 3.13.0-8, which was previously on the system, works fine.

  I also  updated to linux-image 3.14.0-031400rc4-generic from the
  mainline site and the openipmi service starts working again.

  Steps to reproduce:

  Install 14.04 server, amd64 version.  Make sure kernel 3.13.0-11 or -12 are 
installed
  Install openipmi.
  Try to start the openipmi service (sudo service ipmi start)

  Actual results:
  openipmi fails to load the ipmi modules and the service fails to start

  Expected results:
  openipmi starts without problems. 

  This is an important issue because tools like ipmitool and Dell's
  iDRAC service module for Ubuntu rely on a working openipmi in order to
  function properly.  The 3.14 kernels seem to have a fix of some sort
  in them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284334/+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 1265885] Re: regression with respect touchpad

2014-02-27 Thread Kent Baxley

I think I know what might be happening here...

The firmware on these Synaptics touchpads supports i2c mode as well as
psmouse mode.  Older kernels prior to 3.11 didn't have very good i2c
support and the firmware on the touchpad would fall back to psmouse
mode.  psmouse mode worked nicely on machines pre-loaded with 12.04 and
probably worked OK up until 13.04.   Once the Saucy kernels were
introduced, the 3.11 kernels had better i2c support and thus the
touchpad would load up in i2c mode.

Synaptics was supposed to be working on some hid-multitouch i2c drivers
and I thought they would have been upstreamed by now.  Without them, the
touchpad will operate in *very* basic i2c mode.  This also explains the
difference between what you see in xinput with the older kernels (PS/2)
versus newer ones (DLL060A:00 06CB:2734).  So, yes, blacklisting i2c_hid
is one way to work around the problem.

I'll find out what the deal is with Synaptics...

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

Title:
  regression with respect touchpad

Status in “linux” package in Ubuntu:
  In Progress

Bug description:
  This regression occurs somewhere between 3.11.0-14-generic (latest on
  saucy) and 3.13.0-031300rc6-generic (a test kernel). On the earlier
  kernel, I actually  get settings for setting up my touchpad in the
  unity interface. With the updated kernel, those options disappear. I
  only get one set of options both my mouse and my touchpad instead of
  each one independently. It means that I can't set the pointer speed
  differently or turn on natural scrolling for my touchpad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1265885/+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 1284334] Re: (regression?) openipmi fails to start on kernels 3.13.0-11-generic and 3.13.0-12-generic

2014-02-25 Thread Kent Baxley

Here's the apport when booted to 3.13.0-8.  I'm wondering if that is
indeed the case.  I saw a changelog for the -11 kernel stating IPMI
modules were set to 'y'.

** Attachment added: openipmi-38.apport
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284334/+attachment/3996426/+files/openipmi-38.apport

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

Title:
  (regression?) openipmi fails to start on kernels 3.13.0-11-generic and
  3.13.0-12-generic

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  When updating 14.04 to 3.13.0-12 I noticed that the openipmi service
  failed to start on reboot.  After running 'sudo service openipmi
  start', the service would still fail to start because it failed to
  load the ipmi modules.

  Kernel 3.13.0-8, which was previously on the system, works fine.

  I also  updated to linux-image 3.14.0-031400rc4-generic from the
  mainline site and the openipmi service starts working again.

  Steps to reproduce:

  Install 14.04 server, amd64 version.  Make sure kernel 3.13.0-11 or -12 are 
installed
  Install openipmi.
  Try to start the openipmi service (sudo service ipmi start)

  Actual results:
  openipmi fails to load the ipmi modules and the service fails to start

  Expected results:
  openipmi starts without problems. 

  This is an important issue because tools like ipmitool and Dell's
  iDRAC service module for Ubuntu rely on a working openipmi in order to
  function properly.  The 3.14 kernels seem to have a fix of some sort
  in them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284334/+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 1284334] Re: (regression?) openipmi fails to start on kernels 3.13.0-11-generic and 3.13.0-12-generic

2014-02-25 Thread Kent Baxley

Also just tested the 3.13.5 from mainline and noticed that openipmi does
not start there, either.  Same symptoms.

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

Title:
  (regression?) openipmi fails to start on kernels 3.13.0-11-generic and
  3.13.0-12-generic

Status in “linux” package in Ubuntu:
  Triaged

Bug description:
  When updating 14.04 to 3.13.0-12 I noticed that the openipmi service
  failed to start on reboot.  After running 'sudo service openipmi
  start', the service would still fail to start because it failed to
  load the ipmi modules.

  Kernel 3.13.0-8, which was previously on the system, works fine.

  I also  updated to linux-image 3.14.0-031400rc4-generic from the
  mainline site and the openipmi service starts working again.

  Steps to reproduce:

  Install 14.04 server, amd64 version.  Make sure kernel 3.13.0-11 or -12 are 
installed
  Install openipmi.
  Try to start the openipmi service (sudo service ipmi start)

  Actual results:
  openipmi fails to load the ipmi modules and the service fails to start

  Expected results:
  openipmi starts without problems. 

  This is an important issue because tools like ipmitool and Dell's
  iDRAC service module for Ubuntu rely on a working openipmi in order to
  function properly.  The 3.14 kernels seem to have a fix of some sort
  in them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284334/+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 1284334] Re: (regression?) openipmi fails to start on kernels 3.13.0-11-generic and 3.13.0-12-generic

2014-02-24 Thread Kent Baxley

This is the kernel that worked for me:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc4-trusty/

I can also go back and test the others until I find one that breaks.

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

Title:
  (regression?) openipmi fails to start on kernels 3.13.0-11-generic and
  3.13.0-12-generic

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  When updating 14.04 to 3.13.0-12 I noticed that the openipmi service
  failed to start on reboot.  After running 'sudo service openipmi
  start', the service would still fail to start because it failed to
  load the ipmi modules.

  Kernel 3.13.0-8, which was previously on the system, works fine.

  I also  updated to linux-image 3.14.0-031400rc4-generic from the
  mainline site and the openipmi service starts working again.

  Steps to reproduce:

  Install 14.04 server, amd64 version.  Make sure kernel 3.13.0-11 or -12 are 
installed
  Install openipmi.
  Try to start the openipmi service (sudo service ipmi start)

  Actual results:
  openipmi fails to load the ipmi modules and the service fails to start

  Expected results:
  openipmi starts without problems. 

  This is an important issue because tools like ipmitool and Dell's
  iDRAC service module for Ubuntu rely on a working openipmi in order to
  function properly.  The 3.14 kernels seem to have a fix of some sort
  in them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284334/+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 1284334] [NEW] (regression?) openipmi fails to start on kernels 3.13.0-11-generic and 3.13.0-12-generic

2014-02-24 Thread Kent Baxley

Public bug reported:

When updating 14.04 to 3.13.0-12 I noticed that the openipmi service
failed to start on reboot.  After running 'sudo service openipmi start',
the service would still fail to start because it failed to load the ipmi
modules.

Kernel 3.13.0-8, which was previously on the system, works fine.

I also  updated to linux-image 3.14.0-031400rc4-generic from the
mainline site and the openipmi service starts working again.

Steps to reproduce:

Install 14.04 server, amd64 version.  Make sure kernel 3.13.0-11 or -12 are 
installed
Install openipmi.
Try to start the openipmi service (sudo service ipmi start)

Actual results:
openipmi fails to load the ipmi modules and the service fails to start

Expected results:
openipmi starts without problems. 

This is an important issue because tools like ipmitool and Dell's iDRAC
service module for Ubuntu rely on a working openipmi in order to
function properly.  The 3.14 kernels seem to have a fix of some sort in
them.

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

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

Title:
  (regression?) openipmi fails to start on kernels 3.13.0-11-generic and
  3.13.0-12-generic

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  When updating 14.04 to 3.13.0-12 I noticed that the openipmi service
  failed to start on reboot.  After running 'sudo service openipmi
  start', the service would still fail to start because it failed to
  load the ipmi modules.

  Kernel 3.13.0-8, which was previously on the system, works fine.

  I also  updated to linux-image 3.14.0-031400rc4-generic from the
  mainline site and the openipmi service starts working again.

  Steps to reproduce:

  Install 14.04 server, amd64 version.  Make sure kernel 3.13.0-11 or -12 are 
installed
  Install openipmi.
  Try to start the openipmi service (sudo service ipmi start)

  Actual results:
  openipmi fails to load the ipmi modules and the service fails to start

  Expected results:
  openipmi starts without problems. 

  This is an important issue because tools like ipmitool and Dell's
  iDRAC service module for Ubuntu rely on a working openipmi in order to
  function properly.  The 3.14 kernels seem to have a fix of some sort
  in them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284334/+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 1284334] Re: (regression?) openipmi fails to start on kernels 3.13.0-11-generic and 3.13.0-12-generic

2014-02-24 Thread Kent Baxley

I've uploaded the .apport file, since the server can't get out to the
internet very easily. Let me know if you need anything else.

** Attachment added: openipmi.apport

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284334/+attachment/3994996/+files/openipmi.apport

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

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

Title:
(regression?) openipmi fails to start on kernels 3.13.0-11-generic and
3.13.0-12-generic

Status in “linux” package in Ubuntu:
Confirmed

Bug description:
When updating 14.04 to 3.13.0-12 I noticed that the openipmi service
failed to start on reboot. After running 'sudo service openipmi
start', the service would still fail to start because it failed to
load the ipmi modules.

Kernel 3.13.0-8, which was previously on the system, works fine.

I also updated to linux-image 3.14.0-031400rc4-generic from the
mainline site and the openipmi service starts working again.

Steps to reproduce:

Install 14.04 server, amd64 version. Make sure kernel 3.13.0-11 or -12 are
installed
Install openipmi.
Try to start the openipmi service (sudo service ipmi start)

Actual results:
openipmi fails to load the ipmi modules and the service fails to start

Expected results:
openipmi starts without problems.

This is an important issue because tools like ipmitool and Dell's
iDRAC service module for Ubuntu rely on a working openipmi in order to
function properly. The 3.14 kernels seem to have a fix of some sort
in them.

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

[Kernel-packages] [Bug 1274471] [NEW] S3 Failures on certain Dell Haswell systems with 3.11 and 3.13 Kernels

2014-01-30 Thread Kent Baxley

Public bug reported:

Dell has reported that certain models of their Haswell-based systems
have been having issues with S3, starting with the 3.11 kernels in
13.10.

Here are some data points for now:

1) Doesn't happen on ubuntu or debian with 3.7
2) Doesn't happen on 13.04 with stock 3.8 kernel
3) Happens on stock kernel for 13.10
4) Happens on 3.13-rc8
5) Specific to Dell HSW HW.  Not happening on other OEM HSW HW from what has 
been reported.

Business-Client machines (such as Optiplex, Latitiude, etc) seem to
reproduce the issue, but, systems like the XPS 13 with Haswell do not.

Some tests are being run on an Optiplex 9020 to try and narrow down what
exactly might be wrong.

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

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

Title:
  S3 Failures on certain Dell Haswell systems with 3.11 and 3.13 Kernels

Status in “linux” package in Ubuntu:
  New

Bug description:
  Dell has reported that certain models of their Haswell-based systems
  have been having issues with S3, starting with the 3.11 kernels in
  13.10.

  Here are some data points for now:

  1) Doesn't happen on ubuntu or debian with 3.7
  2) Doesn't happen on 13.04 with stock 3.8 kernel
  3) Happens on stock kernel for 13.10
  4) Happens on 3.13-rc8
  5) Specific to Dell HSW HW.  Not happening on other OEM HSW HW from what has 
been reported.

  Business-Client machines (such as Optiplex, Latitiude, etc) seem to
  reproduce the issue, but, systems like the XPS 13 with Haswell do not.

  Some tests are being run on an Optiplex 9020 to try and narrow down
  what exactly might be wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274471/+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 1274471] Re: S3 Failures on certain Dell Haswell systems with 3.11 and 3.13 Kernels

2014-01-30 Thread Kent Baxley

Yes.  Someone will be able to do this once they get online this morning.
I've let them know the bug number so they can start logging results
here.

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

Title:
  S3 Failures on certain Dell Haswell systems with 3.11 and 3.13 Kernels

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Dell has reported that certain models of their Haswell-based systems
  have been having issues with S3, starting with the 3.11 kernels in
  13.10.

  Here are some data points for now:

  1) Doesn't happen on ubuntu or debian with 3.7
  2) Doesn't happen on 13.04 with stock 3.8 kernel
  3) Happens on stock kernel for 13.10
  4) Happens on 3.13-rc8
  5) Specific to Dell HSW HW.  Not happening on other OEM HSW HW from what has 
been reported.

  Business-Client machines (such as Optiplex, Latitiude, etc) seem to
  reproduce the issue, but, systems like the XPS 13 with Haswell do not.

  Some tests are being run on an Optiplex 9020 to try and narrow down
  what exactly might be wrong.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1274471/+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 1152580] Re: [Dell PowerEdge M520] BCM95720 Network disconnects and resets

2014-01-03 Thread Kent Baxley

** Changed in: dell-poweredge
   Importance: High = Medium

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

Title:
  [Dell PowerEdge M520] BCM95720 Network disconnects and resets

Status in The Dell PowerEdge project:
  Confirmed
Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  The server is constantly going on and offline here are messages and hardware 
Details:
  [4.394703] tg3 :02:00.0: eth0: Tigon3 [partno(BCM95720) rev 572] 
(PCI Express) MAC address 90:b1:1c:0d:d4:aa
  [4.394713] tg3 :02:00.0: eth0: attached PHY is 5720C 
(10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
  [4.394720] tg3 :02:00.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] 
ASF[1] TSOcap[1]
  [4.394726] tg3 :02:00.0: eth0: dma_rwctrl[0001] dma_mask[64-bit]

  The dump to dmesg:
  
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1152580/+attachment/3939814/+files/log

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-38-generic 3.2.0-38.61
  ProcVersionSignature: Ubuntu 3.2.0-38.61-generic 3.2.37
  Uname: Linux 3.2.0-38-generic x86_64
  AlsaDevices:
   total 0
   crw-rw---T 1 root audio 116,  1 Mar  8 13:26 seq
   crw-rw---T 1 root audio 116, 33 Mar  8 13:26 timer
  AplayDevices: Error: [Errno 2] No such file or directory
  ApportVersion: 2.0.1-0ubuntu17.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: Error: [Errno 2] No such file or directory
  Date: Fri Mar  8 14:21:45 2013
  HibernationDevice: RESUME=UUID=f9a32355-70b4-462b-a01e-2665b81b2ec0
  InstallationMedia: Ubuntu-Server 12.04.1 LTS Precise Pangolin - Release 
amd64 (20120817.3)
  MachineType: Dell Inc. PowerEdge R520
  MarkForUpload: True
  PciMultimedia:

  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.2.0-38-generic 
root=UUID=0c0140bd-05eb-4e5c-9596-1cf4dee88ae4 ro
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-38-generic N/A
   linux-backports-modules-3.2.0-38-generic  N/A
   linux-firmware1.79.1
  RfKill: Error: [Errno 2] No such file or directory
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/21/2012
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.5
  dmi.board.name: 051XDX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.5:bd08/21/2012:svnDellInc.:pnPowerEdgeR520:pvr:rvnDellInc.:rn051XDX:rvrA00:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R520
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1152580/+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 1263219] Re: kernel panics with BUG

2014-01-02 Thread Kent Baxley

@Warren,

What they're suggesting by development release is downloading the latest
iso for 14.04 and trying it as well.  Those kernels are (I think) still
on version 3.12 instead of the release-candidate 3.13 ones.  I believe
the idea is that if the problem is fixed in 3.12-based kernels it'll
probably help narrow things down a bit.

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

Title:
  kernel panics with BUG

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  I have a Dell Sputnik 3 that I just got and upgraded it to
  12.10-13.04-13.10. On boot the kernel crashes with a BUG.  Attached
  is a dmesg output from after the loading of the module.

  WORKAROUND: I can prevent the crash by blacklisting the iwlwifi module
  and I can cause the BUG by manually loading the module.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1263219/+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 1175278] Re: Please apply new upstream patches for mtip32xx

2013-10-31 Thread Kent Baxley

Turns out these patches were too invasive to port to 13.04.  They do
look to be in 13.10 and these should also be available in the 12.04.4
Saucy HWE kernel once it releases in January.

** Changed in: dell-poweredge
   Status: In Progress = Fix Committed

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

Title:
  Please apply new upstream patches for mtip32xx

Status in The Dell PowerEdge project:
  Fix Committed
Status in “linux” package in Ubuntu:
  Confirmed
Status in “linux” source package in Raring:
  In Progress

Bug description:
  Dell has requested that the latest batch of patches for the mtip32xx
  driver be applied to Ubuntu.  We should get these for free with 13.10.

  If possible, Dell would like to have them backported to 13.04, 12.10,
  and 12.04.2.  If 12.10 / 12.04.2 is not possible, then Dell can also
  wait until 12.04.3 with the HWE kernel from 13.04.

  The requested commits are everything after the Fix padding issue
  found here:

  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/block/mtip32xx

  Individual list of commits:

  
  mtip32xx: fix for a driver hang after a command timeout:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=47cd4b3c7e80cc8d5ac82930c5af835870b5aba1

  mtip32xx: fix for crash when device surprise removed during rebuild:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=58c49df378cde4ff64172483d593a1a5689c13a8

  mtip32xx: add work queue and NUMA support:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=16c906e51c6f08a15763a85b5686e1ded35e77ab

  mtip32xx: add TRIM support:
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=152834694dcb90d3088bc77fa436755c66553929

  drivers/block/mtip32xx/mtip32xx.c:4029:1: sparse: symbol 'mtip_workq_sdbf0' 
was not declared. Should it be static?
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=25bac122b8d874d625982aead1974be819eca841

  drivers/block/mtip32xx/mtip32xx.c:1726:5: sparse: symbol 'mtip_send_trim' was 
not declared. Should it be static?
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=478c030eecbec927d62561c5f48a4515ea0fa21a

  drivers/block/mtip32xx: add missing GENERIC_HARDIRQS dependency
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=1262e24a59a052f9a98383e47e7c903712490d5c

  Merge branch 'stable/for-jens-3.9' of 
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen into for-3.9/drivers
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=d4308febf3551d46884561b7c3fdd62ad3ca7ff2

  mtip32xx: fix error return code in mtip_pci_probe()
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=d137c8306c748d89260400176613b5a85574b255

  mtip32xx: recovery from command timeout
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=d0d096b1d8b97172cee953f1a00b7d4379d398da

  mtip32xx: return 0 from pci probe in case of rebuild
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=6b06d35f3f63dbfde71c792b8584225f3d1fc7f2

  mtip32xx: Add debugfs entry device_status
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=0caff00390db41c98976e65f2ebc3eeaa4861358

  mtip32xx: fix two smatch warnings
  
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/block/mtip32xx?id=c66bb3f075cfe2d17b2427e96e043622db02759c

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1175278/+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 1206602] Re: Add hotplug support for Micron's PCIe-SSD devices

2013-10-31 Thread Kent Baxley

** Changed in: dell-poweredge
   Status: Confirmed = In Progress

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

Title:
  Add hotplug support for Micron's PCIe-SSD devices

Status in The Dell PowerEdge project:
  In Progress
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Add hotplug (SRSI) support for Micron's PCIe-SSD devices (mtip32xx
  driver).

  The patches that enable this functionality have been submitted to the
  linux-block mailing list:

  http://marc.info/?l=linux-kernelm=136812385512296

  Micron has been in direct conversations with Jens Axboe to merge these
  patches upstream, as far as I know there are no objections from the
  community and should just be a matter of time before they are merged
  upstream. They may not land in kernel 3.11, probably looking at 3.12.

  I tested these patches with the 3.10.2 kernel and both hot-removal and
  hot-insertion work ok. I had to pass the pci=pcie_bus_perf kernel
  parameter to avoid MaxPayload issues.

  Adding support in Saucy will pave the way for established support in
  the 14.04 LTS release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1206602/+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 1206602] Re: Add hotplug support for Micron's PCIe-SSD devices

2013-07-30 Thread Kent Baxley

** Information type changed from Proprietary to Public

** Changed in: dell-poweredge
   Status: New = Confirmed

** Changed in: dell-poweredge
 Assignee: (unassigned) = Kent Baxley (kentb)

** Changed in: dell-poweredge
   Importance: Undecided = Wishlist

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

** Changed in: dell-poweredge
   Status: Confirmed = Won't Fix

** Changed in: dell-poweredge
   Status: Won't Fix = Confirmed

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

Title:
  Add hotplug support for Micron's PCIe-SSD devices

Status in The Dell PowerEdge project:
  Confirmed
Status in “linux” package in Ubuntu:
  New

Bug description:
  Add hotplug (SRSI) support for Micron's PCIe-SSD devices (mtip32xx
  driver).

  The patches that enable this functionality have been submitted to the
  linux-block mailing list:

  http://marc.info/?l=linux-kernelm=136812385512296

  Micron has been in direct conversations with Jens Axboe to merge these
  patches upstream, as far as I know there are no objections from the
  community and should just be a matter of time before they are merged
  upstream. They may not land in kernel 3.11, probably looking at 3.12.

  I tested these patches with the 3.10.2 kernel and both hot-removal and
  hot-insertion work ok. I had to pass the pci=pcie_bus_perf kernel
  parameter to avoid MaxPayload issues.

  Adding support in Saucy will pave the way for established support in
  the 14.04 LTS release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1206602/+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 1152580] Re: BCM95720 Network disconnects and resets with new Dell R520 server

2013-07-30 Thread Kent Baxley

** Changed in: dell-poweredge
   Status: New = Confirmed

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

Title:
  BCM95720 Network disconnects and resets with new Dell R520 server

Status in The Dell PowerEdge project:
  Confirmed
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  The server is constantly going on and offline here are messages and
  details

  Linux xx 3.2.0-38-generic #61-Ubuntu SMP Tue Feb 19
  12:18:21 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=12.04
  DISTRIB_CODENAME=precise
  DISTRIB_DESCRIPTION=Ubuntu 12.04.2 LTS

  Hardware Details:
  [4.394703] tg3 :02:00.0: eth0: Tigon3 [partno(BCM95720) rev 572] 
(PCI Express) MAC address 90:b1:1c:0d:d4:aa
  [4.394713] tg3 :02:00.0: eth0: attached PHY is 5720C 
(10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
  [4.394720] tg3 :02:00.0: eth0: RXcsums[1] LinkChgREG[0] MIirq[0] 
ASF[1] TSOcap[1]
  [4.394726] tg3 :02:00.0: eth0: dma_rwctrl[0001] dma_mask[64-bit]

  The dump to dmesg:
  [ 1836.538377] tg3 :02:00.0: eth0: transmit timed out, resetting
  [ 1837.804044] tg3 :02:00.0: eth0: 0x: 0x165f14e4, 0x00100406, 
0x0200, 0x00800010
  [ 1837.812650] tg3 :02:00.0: eth0: 0x0010: 0xd90a000c, 0x, 
0xd90b000c, 0x
  [ 1837.821272] tg3 :02:00.0: eth0: 0x0020: 0xd90c000c, 0x, 
0x, 0x04f61028
  [ 1837.830323] tg3 :02:00.0: eth0: 0x0030: 0xdd00, 0x0048, 
0x, 0x010f
  [ 1837.839735] tg3 :02:00.0: eth0: 0x0040: 0x, 0x0300, 
0xc8035001, 0x64002008
  [ 1837.849390] tg3 :02:00.0: eth0: 0x0050: 0x818c5803, 0x7800, 
0x0086a005, 0x
  [ 1837.859425] tg3 :02:00.0: eth0: 0x0060: 0x, 0x, 
0xf298, 0x00380081
  [ 1837.869992] tg3 :02:00.0: eth0: 0x0070: 0x000710b0, 0xff401a00, 
0x0001421c, 0x
  [ 1837.880661] tg3 :02:00.0: eth0: 0x0080: 0x0001, 0x80f8, 
0x, 0x0a64
  [ 1837.891604] tg3 :02:00.0: eth0: 0x0090: 0x, 0x, 
0x, 0x0232
  [ 1837.903145] tg3 :02:00.0: eth0: 0x00a0: 0x8010ac11, 0x0004, 
0x1004, 0x00020010
  [ 1837.915190] tg3 :02:00.0: eth0: 0x00b0: 0x10008d81, 0x0010240e, 
0x0004cc22, 0x10120040
  [ 1837.927652] tg3 :02:00.0: eth0: 0x00d0: 0x001f, 0x0006, 
0x, 0x0001
  [ 1837.940125] tg3 :02:00.0: eth0: 0x00f0: 0x, 0x0572, 
0x, 0xf8daf5ff
  [ 1837.952612] tg3 :02:00.0: eth0: 0x0100: 0x13c10001, 0x, 
0x00018000, 0x000e7030
  [ 1837.965116] tg3 :02:00.0: eth0: 0x0110: 0x2000, 0x31c0, 
0x00a0, 0x
  [ 1837.977630] tg3 :02:00.0: eth0: 0x0130: 0x, 0x, 
0x, 0x15010003
  [ 1837.990144] tg3 :02:00.0: eth0: 0x0140: 0x1c0dd4aa, 0x90b1, 
0x, 0x
  [ 1838.002660] tg3 :02:00.0: eth0: 0x0150: 0x16010004, 0x, 
0x0007811b, 0x0001
  [ 1838.015173] tg3 :02:00.0: eth0: 0x0160: 0x23010002, 0x, 
0x, 0x
  [ 1838.027663] tg3 :02:00.0: eth0: 0x0170: 0x, 0x80ff, 
0x, 0x
  [ 1838.040168] tg3 :02:00.0: eth0: 0x0200: 0x, 0x0300, 
0x, 0x8b00
  [ 1838.052644] tg3 :02:00.0: eth0: 0x0210: 0x, 0xe300, 
0x, 0xc100
  [ 1838.065114] tg3 :02:00.0: eth0: 0x0220: 0x, 0x4500, 
0x, 0x
  [ 1838.077580] tg3 :02:00.0: eth0: 0x0260: 0x, 0x, 
0x, 0x0232
  [ 1838.090045] tg3 :02:00.0: eth0: 0x0280: 0x, 0x0a64, 
0x, 0x00c0
  [ 1838.102479] tg3 :02:00.0: eth0: 0x0290: 0x, 0x04d8, 
0x, 0x016e
  [ 1838.114912] tg3 :02:00.0: eth0: 0x0300: 0x, 0x018a, 
0x, 0x00e5
  [ 1838.127346] tg3 :02:00.0: eth0: 0x0400: 0x18e04808, 0x0040, 
0x1000, 0x0880
  [ 1838.139783] tg3 :02:00.0: eth0: 0x0410: 0x90b1, 0x1c0dd4aa, 
0x90b1, 0x1c0dd4aa
  [ 1838.152219] tg3 :02:00.0: eth0: 0x0420: 0x90b1, 0x1c0dd4aa, 
0x90b1, 0x1c0dd4aa
  [ 1838.164677] tg3 :02:00.0: eth0: 0x0430: 0x0400, 0x, 
0x0276, 0x05f2
  [ 1838.177118] tg3 :02:00.0: eth0: 0x0440: 0x, 0x, 
0x, 0x04380400
  [ 1838.189564] tg3 :02:00.0: eth0: 0x0450: 0x0001, 0x8000, 
0x, 0x0102
  [ 1838.202031] tg3 :02:00.0: eth0: 0x0460: 0x0008, 0x2620, 
0x01ff0102, 0x
  [ 1838.214498] tg3 :02:00.0: eth0: 0x0480: 0x4200, 0x7fff, 
0x0604, 0x7fff
  [ 1838.226968] tg3 :02:00.0: eth0: 0x0500: 0x0008, 0x0002, 
0x, 0x

[Kernel-packages] [Bug 1206602] Re: Add hotplug support for Micron's PCIe-SSD devices

2013-07-30 Thread Kent Baxley

This is a request to consider adding a new feature to the mptip32xx
driver.  There's no bug or breakage at this time.

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

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

Title:
  Add hotplug support for Micron's PCIe-SSD devices

Status in The Dell PowerEdge project:
  Confirmed
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  Add hotplug (SRSI) support for Micron's PCIe-SSD devices (mtip32xx
  driver).

  The patches that enable this functionality have been submitted to the
  linux-block mailing list:

  http://marc.info/?l=linux-kernelm=136812385512296

  Micron has been in direct conversations with Jens Axboe to merge these
  patches upstream, as far as I know there are no objections from the
  community and should just be a matter of time before they are merged
  upstream. They may not land in kernel 3.11, probably looking at 3.12.

  I tested these patches with the 3.10.2 kernel and both hot-removal and
  hot-insertion work ok. I had to pass the pci=pcie_bus_perf kernel
  parameter to avoid MaxPayload issues.

  Adding support in Saucy will pave the way for established support in
  the 14.04 LTS release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-poweredge/+bug/1206602/+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 1169376] Re: XPS13 backlight stopped working after update 3.8.0-18.28

2013-07-29 Thread Kent Baxley

A patch is being worked on to fix this once and for all.   We got an FHD
system into the hands of someone to hammer all of this out.

There is some upstream ACPI stuff that needs to settle first, but, this
should be happening very soon if not already.   Once that's done the
13.10 development release will pick this up first, followed by a
backport to 13.04.

3.8.0-27 doesn't  have any fixes in it yet.

I don't have an exact ETA on when all of this will be pushed out right
but it will be soon.

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

Title:
  XPS13 backlight stopped working after update 3.8.0-18.28

Status in Dell Sputnik:
  Confirmed
Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  I'm on 13.04 beta 2 and I've been updating daily. After today's
  update, I was asked to restart and, after the restart, the backlight
  stopped working. What's worse is that the backlight is stuck in the
  lowest possible setting. I can barely see enough to type out this bug
  report. This is not a hardware problem. When I restart the computer
  the backlight turns on property  but burns off when the Ubuntu
  encryption screen comes up (I'm using full disk encryption). Please
  fix this as soon as possible.

  XPS 13 version: L322x
  Display version: FHD (1080p)
  --- 
  ApportVersion: 2.9.2-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  cr45h  1901 F pulseaudio
  DistroRelease: Ubuntu 13.04
  HibernationDevice: RESUME=UUID=a5d2ab8b-a068-4a69-95a6-b4e955b290f5
  InstallationDate: Installed on 2013-04-08 (9 days ago)
  InstallationMedia: Ubuntu 13.04 Raring Ringtail - Alpha amd64 (20130402.1)
  MachineType: Dell Inc. Dell System XPS L322X
  MarkForUpload: True
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.8.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 3.8.0-18.28-generic 3.8.6
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-18-generic N/A
   linux-backports-modules-3.8.0-18-generic  N/A
   linux-firmware1.105
  Tags:  raring
  Uname: Linux 3.8.0-18-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  dmi.bios.date: 01/22/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0PJHXN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd01/22/2013:svnDellInc.:pnDellSystemXPSL322X:pvr:rvnDellInc.:rn0PJHXN:rvrA00:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System XPS L322X
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1169376/+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

44 matches

Mail list logo