[Kernel-packages] [Bug 1737640] Re: [SRU] /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

2018-01-25 Thread Narinder Gupta 
** Changed in: opnfv
   Status: Fix Committed => Invalid

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

Title:
  [SRU] /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Invalid
Status in OPNFV:
  Invalid
Status in ubuntu-fan package in Ubuntu:
  Fix Released
Status in ubuntu-fan source package in Xenial:
  Fix Released
Status in ubuntu-fan source package in Zesty:
  Won't Fix
Status in ubuntu-fan source package in Artful:
  In Progress
Status in ubuntu-fan source package in Bionic:
  Fix Released

Bug description:
  [Impact]

   * This bug effects anyone deploying LXD with juju on a machine with
  interfaces configured as IP/mask. Since this is a very common use
  case, SRU is needed.

  [Test Case]

   * Detailed process can be seen at https://paste.ubuntu.com/26169937/

  [Regression Potential]

   * Potential for regression is low because of the nature of the error.
  It's just missing a case stanza for interfaces that are defined with
  IP/mask

  [Other Info]

   * Original report:

  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1737640/+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 1591609] Re: [Feature]Memory Bandwidth Monitoring(MBM) port to new Cache Quality Monitoring (CQM)

2018-01-09 Thread Narinder Gupta 
** Changed in: intel
   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/1591609

Title:
  [Feature]Memory Bandwidth Monitoring(MBM) port to new Cache Quality
  Monitoring (CQM)

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux source package in Artful:
  Fix Released

Bug description:
  Google has sent a new cqm patch with a lot of fixes to the existing
  cqm which is upstream. The MBM was based on the old cqm and now needs
  to be ported on top of the new version of cqm. The google patch is
  enormous and hence mbm requires a lot of changes to work on top of it.
  However This wont impact the openstack usage of cqm/mbm as the name of
  the events would still be the same and they can just be used like
  before - only that there may be some features which wernt working will
  work now.

  Platform:  BDW-EP or BDW-EX

  upstream schedule: 4.13 kernel

To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1591609/+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 1737640] Re: /usr/sbin/fanctl: arithmetic expression: expecting primary | unconfigured interfaces cause ifup failures

2017-12-15 Thread Narinder Gupta 
The workaround by adding the proposed repository into package
repositories in MAAS worked for me.

** Also affects: opnfv
   Importance: Undecided
   Status: New

** Changed in: opnfv
   Status: New => Fix Committed

** Changed in: opnfv
   Importance: Undecided => Critical

** Changed in: opnfv
 Assignee: (unassigned) => Narinder Gupta (narindergupta)

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

Title:
  /usr/sbin/fanctl: arithmetic expression: expecting primary |
  unconfigured interfaces cause ifup failures

Status in juju:
  Triaged
Status in OPNFV:
  Fix Committed
Status in ubuntu-fan package in Ubuntu:
  Confirmed
Status in ubuntu-fan source package in Xenial:
  Fix Committed

Bug description:
  I'm seeing this error as the status of multiple containers in my
  deploy:

  http://paste.ubuntu.com/26166720/

  I can't connect to the parent machines anymore either - it seems
  networking is totally hosed on the machines.

  This is with juju 2.3.1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1737640/+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 1729608] Re: arithmetic expression: expecting primary: " (32-)/4 "

2017-12-12 Thread Narinder Gupta 
can reproduce this issue with juju deploy pike bundle on xenial

** Also affects: opnfv
   Importance: Undecided
   Status: New

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

Title:
  arithmetic expression: expecting primary: " (32-)/4 "

Status in juju:
  New
Status in OPNFV:
  New
Status in ubuntu-fan package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I've configured a bridge interface (named vlan0) through interfaces,
  but can't take it up with ifup, since the if-up-script from ubuntu-fan
  aborts with error status

  
  reason:

  # fanctl net start vlan0
  /usr/sbin/fanctl: 41: /usr/sbin/fanctl: arithmetic expression: expecting 
primary: " (32-)/4 "


  As far as I can see the problem is that in cmd_net_up() the line

  
  addr="${addr%/*}"

  cuts the mask from the interface config and passes the pure ip address
  only, but later config_filename() calls width_to_mask(), which tries
  to use the (now missing) mask.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ubuntu-fan 0.12.6
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Nov  2 14:26:42 2017
  InstallationDate: Installed on 2017-10-24 (9 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  PackageArchitecture: all
  SourcePackage: ubuntu-fan
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juju/+bug/1729608/+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 1721381] [NEW] smartpqi patches for Artful

2017-10-04 Thread Narinder Gupta 
Public bug reported:

Narinder,
Below are smartpqi patches from the 4.14 kernel we would like Canonical to 
consider for the 4.13 kernel expected in the Ubuntu 17.10 release.

http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=58322fe0069a2ae2a19cf29023cc0b82c7245762
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=b6d478119edeaca964b46796fd26893b81f8a561
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=336b68193165b1215d21dd05619dc262340e404b
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=557900640b06752fc6a7f6ed545ad1f8e00face9
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=4f078e24080626764896055d857719cd886e6321
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=41555d540f18f72e8a52d5c4bc14c36413d09916
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=b98117caa0e3d99e4aee1114bcb03ae9ad02bf22

Thank you,

Gerry Morong
ESC - Smart Storage
Microsemi Corporation

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

Title:
  smartpqi patches for Artful

Status in linux package in Ubuntu:
  New

Bug description:
  Narinder,
  Below are smartpqi patches from the 4.14 kernel we would like Canonical to 
consider for the 4.13 kernel expected in the Ubuntu 17.10 release.

  
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=58322fe0069a2ae2a19cf29023cc0b82c7245762
  
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=b6d478119edeaca964b46796fd26893b81f8a561
  
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=336b68193165b1215d21dd05619dc262340e404b
  
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=557900640b06752fc6a7f6ed545ad1f8e00face9
  
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=4f078e24080626764896055d857719cd886e6321
  
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=41555d540f18f72e8a52d5c4bc14c36413d09916
  
http://git.kernel.org/?p=linux/kernel/git/jejb/scsi.git;a=commit;h=b98117caa0e3d99e4aee1114bcb03ae9ad02bf22

  Thank you,

  Gerry Morong
  ESC - Smart Storage
  Microsemi Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1721381/+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 1679208] Re: Zesty (4.10.0-14) won't boot on HP ProLiant DL360 Gen9 with intel_iommu=on

2017-09-15 Thread Narinder Gupta 
I have subscribed to HPE Eddie and Ganesh to this bug whether they have
tested this with old kernel or some parameter needs to be added.

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

Title:
  Zesty (4.10.0-14) won't boot on HP ProLiant DL360 Gen9 with
  intel_iommu=on

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  TL;DR
  - one of our HP ProLiant DL360 Gen9 fails to boot with intel_iommu=on
  - the Disk controller fails
  - Xenial seems to work for a while but then fails
  - Zesty 100% crashes on boot
  - An identical system seems to work, so need HW replace to finally confirm

  After reboot one sees a HW report like this:
  After the boot I see the HW telling me this on boot:
  Embedded RAID : Smart HBA H240ar Controller - Operation Failed
   - 1719-Slot 0 Drive Array  - A controller failure event occurred prior
 to this power-up. (Previous lock up code = 0x13)

  
  I tried several things (In between always redeploy zesty with MAAS).
  I think my debugging might be helpful, but I wanted to keep the documentation 
in the bug in case you'd go another route or that others find useful 
information in here.

  0. I retried what I did twice, fully reproducible
 That is:
 0.1 install zesty 
 0.2 change grub default cmdline in /etc/default/grub.d/50- to add 
intel_iommu=on
 0.3 sudo update-grub
 0.4 reboot


  1. I tried a Recovery boot from the boot options in gub.
 => Failed as well


  2. iLO rebooted vis "request reboot" and as well via "full system reset"
 => both Failed


  3. Reboot the system as deployed by MAAS
 # /proc/cmdline before that
 BOOT_IMAGE=/boot/vmlinuz-4.10.0-14-generic 
root=UUID=2137c19a-d441-43fa-82e2-f2b7e3b2727b ro
 The orig grub.cfg is like http://paste.ubuntu.com/24305945/
 It reboots as-is.
 => Reboot worked


  4. without a change to anything in /etc run update-grub
 $ sudo update-grub
 Generating grub configuration file ...
 Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT 
is set is no longer supported.
 Found linux image: /boot/vmlinuz-4.10.0-14-generic
 Found initrd image: /boot/initrd.img-4.10.0-14-generic
 Adding boot menu entry for EFI firmware configuration
 done

 There was no diff between the new grub.cfg and the one I saved.
 => Reboot worked


  5. add the intel_iommu=on arg
$ sudo sed -i 
's/GRUB_CMDLINE_LINUX_DEFAULT=""/GRUB_CMDLINE_LINUX_DEFAULT="intel_iommu=on"/' 
/etc/default/grub.d/50-curtin-settings.cfg
$ sudo update-grub
# Diff in grub.cfg really only is the iommu setting
=> Reboot Failed
So this doesn't seem so much of a cloud-init/curtin/maas bug anymore to me 
- maybe intel_iommu bheaves different?
  - Check grub cfg pre/post - not change but the expected?


  6. Install Xenial and do the same
 => Reboot working


  7. Upgrade to Z
 Since the Xenial system just worked and one can assume that almost only 
kernel is working so early in the boot process I upgraded the working system 
with intel_iommu=on to Zesty.
 That would be 4.4.0-71-generic to 4.10.0-1
 On this upgrade I finally saw my I/O errors again :-/
 Note: these issues are hard to miss as they mount root as read-only.
 I wonder if they only ever appear with intel_iommu=on as this is the only 
combo I ever saw them,


  8. Redeploy and upgrade to Z without intel_iommu=on enabled
 Then enable intel_iommu=on and reboot
 => Reboot Fail
 From here I rebooted into the Xenial kerenl (that since this is an update 
was still there)
 Here I saw:
  Loading Linux 4.4.0-71-generic ...
  Loading initial ramdisk ...
  error: invalid video mode specification `text'.
  Booting in blind mode
 Hrm, as outlined above the "blind mode" might be a red herring, but since 
this kernel worked before it might still be a red herring that swims in the 
initrd that got regenerated on the upgrade.
 => Xenial Kernel Reboot - works !!
 So "blind mode" is a red herring of some sort.
 
 But this might allow to find some logs
 => No
 This appears as if the Failing boot has never made it to the point to 
actually write anything.
 I see:
  1. the original xenial
  2. the upgraded zesty
  3. NOT THE zesty+iommu
  4. the xenial+iommu

  $ egrep 'kernel:.*(Linux version|Command line)' /var/log/syslog 
  Apr  3 12:15:20 node-horsea kernel: [0.00] Linux version 
4.4.0-71-generic (buildd@lcy01-05) (gcc version 5.4.0 20160609 (Ubuntu 
5.4.0-6ubuntu1~16.04.4) ) #92-Ubuntu SMP Fri Mar 24 12:59:01 UTC 2017 (Ubuntu 
4.4.0-71.92-generic 4.4.49)
  Apr  3 12:15:20 node-horsea kernel: [0.00] Command line: 
BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=2137c19a-d441-43fa-82e2-f2b7e3b2727b ro
  Apr  3 12:47:45 node-horsea kernel: [0.00] Linux version

[Kernel-packages] [Bug 1693337] Re: Enable Matrox driver for Ubuntu 16.04.3

2017-06-29 Thread Narinder Gupta 
** Tags removed: verification-needed-zesty
** Tags added: verification-done-zesty

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

Title:
  Enable Matrox driver for Ubuntu 16.04.3

Status in linux package in Ubuntu:
  Fix Committed
Status in linux source package in Zesty:
  Fix Released

Bug description:
  This request is to enable Matrox driver and backport the enablement
  paatch from 4.11 kernel to 4.10 kernel for Ubuntu 16.04.3.

  This will get tested on HPE platform after the modification.

  Following config and patch changes are needed.

  CONFIG_DRM_MGAG200=m

  commit f0493e653f9679114d1dfd54ab88b54ce95576e1
  Author: Mathieu Larouche 
  Date:   Fri Oct 21 12:47:07 2016 -0400

  drm/mgag200: Added support for the new device G200eH3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693337/+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 1693337] Re: Enable Matrox driver for Ubuntu 16.04.3

2017-05-26 Thread Narinder Gupta 
I tested both the kernels on HPE gen8 and Gen10 platform and it seems to
loading fine and i can confirm that driver is in use with Matrox grpahics
controller for both Gen8 and Gen10 platform. Below is the syslog from the
server tested for this bug.

gen10 http://paste.ubuntu.com/24668361/
gen8  http://paste.ubuntu.com/24668369


Thanks and Regards,
Narinder Gupta (PMP)   narinder.gu...@canonical.com
Canonical, Ltd.narindergupta [irc.freenode.net]
+1.281.736.5150narindergupta2007[skype]

Ubuntu- Linux for human beings | www.ubuntu.com | www.canonical.com


On Thu, May 25, 2017 at 11:30 AM, Joseph Salisbury <
joseph.salisb...@canonical.com> wrote:

> I built a Zesty test kernel with CONFIG_DRM_MGAG200 set to m and a pick
> of commit f0493e653f9679114d1dfd54ab88b54ce95576e1.  The test kernel can
> be downloaded from:
>
> http://kernel.ubuntu.com/~jsalisbury/lp1693337/
>
> Can you give this kernel a test?
>
> Thanks in advance!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1693337
>
> Title:
>   Enable Matrox driver for Ubuntu 16.04.3
>
> Status in linux package in Ubuntu:
>   In Progress
> Status in linux source package in Zesty:
>   In Progress
>
> Bug description:
>   This request is to enable Matrox driver and backport the enablement
>   paatch from 4.11 kernel to 4.10 kernel for Ubuntu 16.04.3.
>
>   This will get tested on HPE platform after the modification.
>
>   Following config and patch changes are needed.
>
>   CONFIG_DRM_MGAG200=m
>
>   commit f0493e653f9679114d1dfd54ab88b54ce95576e1
>   Author: Mathieu Larouche <mathieu.larou...@matrox.com>
>   Date:   Fri Oct 21 12:47:07 2016 -0400
>
>   drm/mgag200: Added support for the new device G200eH3
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/
> 1693337/+subscriptions
>

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

Title:
  Enable Matrox driver for Ubuntu 16.04.3

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Zesty:
  In Progress

Bug description:
  This request is to enable Matrox driver and backport the enablement
  paatch from 4.11 kernel to 4.10 kernel for Ubuntu 16.04.3.

  This will get tested on HPE platform after the modification.

  Following config and patch changes are needed.

  CONFIG_DRM_MGAG200=m

  commit f0493e653f9679114d1dfd54ab88b54ce95576e1
  Author: Mathieu Larouche <mathieu.larou...@matrox.com>
  Date:   Fri Oct 21 12:47:07 2016 -0400

  drm/mgag200: Added support for the new device G200eH3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693337/+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 1693337] [NEW] Enable Matrox driver for Ubuntu 16.04.3

2017-05-24 Thread Narinder Gupta 
Public bug reported:

This request is to enable Matrox driver and backport the enablement
paatch from 4.11 kernel to 4.10 kernel for Ubuntu 16.04.3.

This will get tested on HPE platform after the modification.

Following config and patch changes are needed.

CONFIG_DRM_MGAG200=m

commit f0493e653f9679114d1dfd54ab88b54ce95576e1
Author: Mathieu Larouche 
Date:   Fri Oct 21 12:47:07 2016 -0400

drm/mgag200: Added support for the new device G200eH3

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

Title:
  Enable Matrox driver for Ubuntu 16.04.3

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  This request is to enable Matrox driver and backport the enablement
  paatch from 4.11 kernel to 4.10 kernel for Ubuntu 16.04.3.

  This will get tested on HPE platform after the modification.

  Following config and patch changes are needed.

  CONFIG_DRM_MGAG200=m

  commit f0493e653f9679114d1dfd54ab88b54ce95576e1
  Author: Mathieu Larouche 
  Date:   Fri Oct 21 12:47:07 2016 -0400

  drm/mgag200: Added support for the new device G200eH3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1693337/+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 1689980] Re: AACRAID for power9 platform

2017-05-10 Thread Narinder Gupta 
This is driver enablement for Power 9 so apport-collect does not make
sense.

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

Title:
  AACRAID for power9 platform

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hello team,
  It seems Microsemi team has requested to backport few AACRAID driver patches 
for Power 9 platform for 17.04 and 16.04.3 kernel.

  Hi Narinder,

  We have submitted a handful of critical fixes for the AACRAID driver
  on to the kernel.org, targeting 4.11. These patches are bug fixes and
  our customer IBM is expecting these patches to go into the 16.04.3
  release, for to use with the Power9 platforms.

  Can you please let me know if these patches will be backported by your
  kernel team on to the upcoming 16.04.3? Do you also have a schedule in
  place for 16.04.3 release?

  Thanks,
  Gana

  Below are the patch details.

  Subject: [PATCH V2 00/19] aacraid: Patchset with reset rework and misc
  fixes

  This patchset primarily focuses on tweaking and hardening the
  controller reset support for both ARC and HBA1000 devices. Now the
  driver can only reset the controller thru eh reset. Included a srb
  memory fix and pci dma allocation fix.

  Changes in V2:
   - Corrected heading and description for srb memory patch and removed stray
 comment.
   - Removed incorrect up function call and cleared fib wait flag after call
 to down interruptible in the ioctl return on ctrl reset patch.
   - Added review acknowledgements by David Carroll thank you Dave for
 finding the above issues in the above 2 patches.

  Raghava Aditya Renukunta (19):
  [SCSI] aacraid: Remove __GFP_DMA for raw srb memory  
  [SCSI] aacraid: Fix DMAR issues with  iommu=pt  
  [SCSI] aacraid: Added 32 and 64 queue depth for arc natives  
  [SCSI] aacraid: Set correct Queue Depth for HBA1000 RAW disks  
  [SCSI] aacraid: Remove reset support from check_health  
  [SCSI] aacraid: Change wait time for fib completion  
  [SCSI] aacraid: Log count info of scsi cmds before reset  
  [SCSI] aacraid: Print ctrl status before eh reset  
  [SCSI] aacraid: Using single reset mask for IOP reset  
  [SCSI] aacraid: Rework IOP reset  
  [SCSI] aacraid: Add periodic checks to see IOP reset status  
  [SCSI] aacraid: Rework SOFT reset code  
  [SCSI] aacraid: Rework aac_src_restart  
  [SCSI] aacraid: Use correct function to get ctrl health  
  [SCSI] aacraid: Make sure ioctl returns on controller reset  
  [SCSI] aacraid: Enable ctrl reset for both hba and arc  
  [SCSI] aacraid: Add reset debugging statements  
  [SCSI] aacraid: Remove reference to Series-9  
  [SCSI] aacraid: Update driver version to 50834

  drivers/scsi/aacraid/aachba.c   |  17 ++-
  drivers/scsi/aacraid/aacraid.h  |  22 +++-  
  drivers/scsi/aacraid/commctrl.c |  15 ++-  
  drivers/scsi/aacraid/comminit.c |  18 +---  
  drivers/scsi/aacraid/commsup.c  |  78 +++---
  drivers/scsi/aacraid/linit.c| 232 
  drivers/scsi/aacraid/src.c  | 136 +--

   7 files changed, 298 insertions(+), 220 deletions(-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1689980/+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 1689980] [NEW] AACRAID for power9 platform

2017-05-10 Thread Narinder Gupta 
Public bug reported:

Hello team,
It seems Microsemi team has requested to backport few AACRAID driver patches 
for Power 9 platform for 17.04 and 16.04.3 kernel.

Hi Narinder,

We have submitted a handful of critical fixes for the AACRAID driver on
to the kernel.org, targeting 4.11. These patches are bug fixes and our
customer IBM is expecting these patches to go into the 16.04.3 release,
for to use with the Power9 platforms.

Can you please let me know if these patches will be backported by your
kernel team on to the upcoming 16.04.3? Do you also have a schedule in
place for 16.04.3 release?

Thanks,
Gana

Below are the patch details.

Subject: [PATCH V2 00/19] aacraid: Patchset with reset rework and misc
fixes

This patchset primarily focuses on tweaking and hardening the controller
reset support for both ARC and HBA1000 devices. Now the driver can only
reset the controller thru eh reset. Included a srb memory fix and pci
dma allocation fix.

Changes in V2:
 - Corrected heading and description for srb memory patch and removed stray
   comment.
 - Removed incorrect up function call and cleared fib wait flag after call
   to down interruptible in the ioctl return on ctrl reset patch.
 - Added review acknowledgements by David Carroll thank you Dave for
   finding the above issues in the above 2 patches.

Raghava Aditya Renukunta (19):
[SCSI] aacraid: Remove __GFP_DMA for raw srb memory  
[SCSI] aacraid: Fix DMAR issues with  iommu=pt  
[SCSI] aacraid: Added 32 and 64 queue depth for arc natives  
[SCSI] aacraid: Set correct Queue Depth for HBA1000 RAW disks  
[SCSI] aacraid: Remove reset support from check_health  
[SCSI] aacraid: Change wait time for fib completion  
[SCSI] aacraid: Log count info of scsi cmds before reset  
[SCSI] aacraid: Print ctrl status before eh reset  
[SCSI] aacraid: Using single reset mask for IOP reset  
[SCSI] aacraid: Rework IOP reset  
[SCSI] aacraid: Add periodic checks to see IOP reset status  
[SCSI] aacraid: Rework SOFT reset code  
[SCSI] aacraid: Rework aac_src_restart  
[SCSI] aacraid: Use correct function to get ctrl health  
[SCSI] aacraid: Make sure ioctl returns on controller reset  
[SCSI] aacraid: Enable ctrl reset for both hba and arc  
[SCSI] aacraid: Add reset debugging statements  
[SCSI] aacraid: Remove reference to Series-9  
[SCSI] aacraid: Update driver version to 50834

drivers/scsi/aacraid/aachba.c   |  17 ++-
drivers/scsi/aacraid/aacraid.h  |  22 +++-  
drivers/scsi/aacraid/commctrl.c |  15 ++-  
drivers/scsi/aacraid/comminit.c |  18 +---  
drivers/scsi/aacraid/commsup.c  |  78 +++---
drivers/scsi/aacraid/linit.c| 232 
drivers/scsi/aacraid/src.c  | 136 +--

 7 files changed, 298 insertions(+), 220 deletions(-)

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

Title:
  AACRAID for power9 platform

Status in linux package in Ubuntu:
  New

Bug description:
  Hello team,
  It seems Microsemi team has requested to backport few AACRAID driver patches 
for Power 9 platform for 17.04 and 16.04.3 kernel.

  Hi Narinder,

  We have submitted a handful of critical fixes for the AACRAID driver
  on to the kernel.org, targeting 4.11. These patches are bug fixes and
  our customer IBM is expecting these patches to go into the 16.04.3
  release, for to use with the Power9 platforms.

  Can you please let me know if these patches will be backported by your
  kernel team on to the upcoming 16.04.3? Do you also have a schedule in
  place for 16.04.3 release?

  Thanks,
  Gana

  Below are the patch details.

  Subject: [PATCH V2 00/19] aacraid: Patchset with reset rework and misc
  fixes

  This patchset primarily focuses on tweaking and hardening the
  controller reset support for both ARC and HBA1000 devices. Now the
  driver can only reset the controller thru eh reset. Included a srb
  memory fix and pci dma allocation fix.

  Changes in V2:
   - Corrected heading and description for srb memory patch and removed stray
 comment.
   - Removed incorrect up function call and cleared fib wait flag after call
 to down interruptible in the ioctl return on ctrl reset patch.
   - Added review acknowledgements by David Carroll thank you Dave for
 finding the above issues in the above 2 patches.

  Raghava Aditya Renukunta (19):
  [SCSI] aacraid: Remove __GFP_DMA for raw srb memory  
  [SCSI] aacraid: Fix DMAR issues with  iommu=pt  
  [SCSI] aacraid: Added 32 and 64 queue depth for arc natives  
  [SCSI] aacraid: Set correct Queue Depth for HBA1000 RAW disks  
  [SCSI] aacraid: Remove reset support from check_health  
  [SCSI] aacraid: Change wait time for fib completion  
  [SCSI] aacraid: Log count info of scsi cmds before reset  
  [SCSI] aacraid: Print ctrl status before eh reset  
  [SCSI]

[Kernel-packages] [Bug 1680156] [NEW] smartpqi driver needed in initram disk and installer

2017-04-05 Thread Narinder Gupta 
Public bug reported:

In 17.04 we included the smartPQI driver from Microsemi and this request
is to include the driver into initram disk so that udeb can be created
and included in the installer kernel as well.

** Affects: linux (Ubuntu)
 Importance: High
 Assignee: Canonical Kernel Team (canonical-kernel-team)
 Status: Triaged

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

Title:
  smartpqi driver needed in initram disk and installer

Status in linux package in Ubuntu:
  Triaged

Bug description:
  In 17.04 we included the smartPQI driver from Microsemi and this
  request is to include the driver into initram disk so that udeb can be
  created and included in the installer kernel as well.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1680156/+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 1604314] Re: [Xenial] iommu/amd: Fix unity mapping initialization race

2016-07-27 Thread Narinder Gupta 
i am facing the issue and i have updated the bug report. As per comment will 
you please check hpsa persion used for verification and also exact kernel 
patches which has the fixes. please update the bug once you find out the 
difference


(03:46:45 PM) narindergupta: also now seeing hpsa :03:00.0 board not ready, 
timed out

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

Title:
  [Xenial] iommu/amd: Fix unity mapping initialization race

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  == Xenial SRU Justification ==
  HP Gen8 servers were having kernel panics with the 4.2 and 4.4 kernel which 
is apparently resolved with the following commits.  HP would like to see these 
SRU'd for Xenial.

  commit 0caa7616a6aca449dd68b58cb29bd491d296c2d5
  Author: Aaron Campbell 
  Date:   Sat Jul 2 21:23:24 2016 -0300

  iommu/vt-d: Fix infinite loop in free_all_cpu_cached_iovas

  commit 522e5cb76d0663c88f96b6a8301451c8efa37207
  Author: Joerg Roedel 
  Date:   Fri Jul 1 16:42:55 2016 +0200

  iommu/amd: Fix unity mapping initialization race

  == Testing ==
  HP confirms their testing shows these patches resolves the issue on several 
test machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1604314/+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 1604314] Re: [Xenial] iommu/amd: Fix unity mapping initialization race

2016-07-27 Thread Narinder Gupta 
i ma facing the same problem where disk was not find after the update of
this kernel. Will this patch might impact the uuid of the disk?

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

Title:
  [Xenial] iommu/amd: Fix unity mapping initialization race

Status in linux package in Ubuntu:
  Triaged
Status in linux source package in Xenial:
  Triaged

Bug description:
  == Xenial SRU Justification ==
  HP Gen8 servers were having kernel panics with the 4.2 and 4.4 kernel which 
is apparently resolved with the following commits.  HP would like to see these 
SRU'd for Xenial.

  commit 0caa7616a6aca449dd68b58cb29bd491d296c2d5
  Author: Aaron Campbell 
  Date:   Sat Jul 2 21:23:24 2016 -0300

  iommu/vt-d: Fix infinite loop in free_all_cpu_cached_iovas

  commit 522e5cb76d0663c88f96b6a8301451c8efa37207
  Author: Joerg Roedel 
  Date:   Fri Jul 1 16:42:55 2016 +0200

  iommu/amd: Fix unity mapping initialization race

  == Testing ==
  HP confirms their testing shows these patches resolves the issue on several 
test machines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1604314/+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 1550481] Re: hpsa driver causing kernel panics on HP ProLiant DL385p Gen8

2016-07-07 Thread Narinder Gupta 
there is a IOMMU bug HP is debugging and for now you can disable IOMMU
and it should boot as well as should work fine. Once HP will identify
fix and release it we will integrate into Ubuntu 16.04.

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

Title:
  hpsa driver causing kernel panics on HP ProLiant DL385p Gen8

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Doing regression testing on Ubuntu 14.04.4, we've found a big one: An
  HP ProLiant DL385p Gen8 kernel panics on startup with the default
  kernel for that version (4.2.0-27-generic). The server's display (see
  screen shot taken via its BMC's remote KVM) shows a kernel panic that
  seems to implicate the hpsa driver. This server boots and installs
  every Trusty release through 14.04.3 (with a 3.19.0-25 kernel) just
  fine.

  I'm attaching log files from a 14.04.1 installation so that you can
  have some hardware information, and a screen shot of the kernel panic
  in 14.04.4.

  We (the server certification team) have access to the server for a
  limited period. Normally it's in OIL.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1550481/+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 1438853] Re: Ubuntu 15.04: Kernel panic seen during installation

2015-04-02 Thread Narinder Gupta 
** Summary changed:

- [Anders-2]Ubuntu 15.04: Kernel panic seen during installation
+ Ubuntu 15.04: Kernel panic seen during installation

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

Title:
  Ubuntu 15.04: Kernel panic seen during installation

Status in linux package in Ubuntu:
  In Progress
Status in maas package in Ubuntu:
  New
Status in linux source package in Vivid:
  In Progress
Status in maas source package in Vivid:
  New

Bug description:
  Ubuntu 15.04 fails with Kernel Panic.

  Installer used is latest dated 24-March 2015

  http://archive.ubuntu.com/ubuntu/dists/vivid/main/installer-
  amd64/current/images/netboot/ubuntu-installer/amd64/

  Below is the kernel panic message seen during the installation.

    ┌───┤ Configuring apt ├───┐
    │ │
    │ 35% │
    │ │
    │ Scanning local repositories... │
    │ │
    │ [ 529.902606] Kernel panic - not syncing: Timeout synchronizing machine 
check over CPUs │
  [ 531.075045] Shutting down cpus with NMI──┘
  [ 531.131326] Kernel Offset: 0x0 from 0x8100 (relocation range: 
0x8000-0xbfff)
  [ 531.305965] Rebooting in 30 seconds..
  [ 561.537340] ACPI MEMORY or I/O RESET_REG.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1438853/+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 1392432] Re: On Mellanox adapter, reboot under Bond mode loses interface

2014-11-20 Thread Narinder Gupta 
it seems after upgrading the packages to latest issue is not
reproducible so marking this issue as invalid.

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

Title:
  On Mellanox adapter, reboot under Bond mode loses interface

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  This is reported at HP in their bug tracker as: QXCR1001386573

  Symptom: Every time reboot under bonding mode in ubuntu14.04, the
  interface eth0/eth2 disappeared, and only bond0 showed up. The
  Mellanox driver needs to reload. Then the interfaces will appeared and
  the bonding function is working fine.

  HP CSI confirmed that the issue can be seen on Anders (m710) with two
  Mellanox Firmware Version: 2.32.1092 and 2.32.5210. Also another
  Cartridge - McDivitt (m400) has similar issue. Other Cartridge with
  Intel NIC solution does not have this problem when doing bonding. Is
  it possible that the issue is about Ubuntu  Mellanox compatibility
  problem?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1392432/+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 1370716] [NEW] port 1 of bl460c Gen9 can not get IP

2014-09-17 Thread Narinder Gupta 
Public bug reported:

SRU Justification:

Impact:

BL460Gen9 does not get IP addresses on both the NIC ports with Ubuntu 
14.04/14.04.1
The NIC card in the blade is Broadcom Corporation BCM57840 NetXtreme II 
10/20-Gigabit Ethernet.
The NIC port 1 does not get an IP address both during install and after install.
I have attached the dmesg and lspci logs captured from the installer.

Steps to reproduce:
start installation process but kernel does not get IP address on port1 but 
port2 works fine.
Looks like Broadcom ethernet driver issue.

It seems upstream has this fix and below patch was suggested by Broadcom team 
which fixes this issue.
Below is the patch that Qlogic has provided, that fixes the issue.
http://patchwork.ozlabs.org/patch/358990/

Fix:
apply upstream commit: dad91ee478c7f39e04a33272732147b8c274bb58

Test:
Boot the system and see if we get both nics working.

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

** Affects: linux (Ubuntu Trusty)
 Importance: Undecided
 Status: Triaged

** Attachment added: attaching the logs
   
https://bugs.launchpad.net/bugs/1370716/+attachment/4206752/+files/BL460Gen9.zip

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

Title:
  port 1 of bl460c Gen9 can not get IP

Status in “linux” package in Ubuntu:
  Invalid
Status in “linux” source package in Trusty:
  Triaged

Bug description:
  SRU Justification:

  Impact:

  BL460Gen9 does not get IP addresses on both the NIC ports with Ubuntu 
14.04/14.04.1
  The NIC card in the blade is Broadcom Corporation BCM57840 NetXtreme II 
10/20-Gigabit Ethernet.
  The NIC port 1 does not get an IP address both during install and after 
install.
  I have attached the dmesg and lspci logs captured from the installer.

  Steps to reproduce:
  start installation process but kernel does not get IP address on port1 but 
port2 works fine.
  Looks like Broadcom ethernet driver issue.

  It seems upstream has this fix and below patch was suggested by Broadcom team 
which fixes this issue.
  Below is the patch that Qlogic has provided, that fixes the issue.
  http://patchwork.ozlabs.org/patch/358990/

  Fix:
  apply upstream commit: dad91ee478c7f39e04a33272732147b8c274bb58

  Test:
  Boot the system and see if we get both nics working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1370716/+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 1248621] Re: Medium Errors when running cpufreq test in fwts

2013-11-06 Thread Narinder Gupta 
attaching the acpidump.log

** Attachment added: acpidump.log
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248621/+attachment/3901810/+files/acpidump.log

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

Title:
  Medium Errors when running cpufreq test in fwts

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  While running the cpufreq test on a server, we encountered the
  following (Here's the full log)

  Results generated by fwts: Version V13.09.01 (2013-09-17 07:41:02).

  Some of this work - Copyright (c) 1999 - 2010, Intel Corp. All rights 
reserved.
  Some of this work - Copyright (c) 2010 - 2013, Canonical.

  This test run on 05/11/13 at 16:05:51 on host Linux ubuntuc1n1 
3.11.0-12-generic
  #19-Ubuntu SMP Wed Oct 9 16:20:46 UTC 2013 x86_64.

  Command: fwts -q --stdout-summary -r /root/.checkbox/scaling_test.log 
cpufreq.
  Running tests: cpufreq.

  cpufreq: CPU frequency scaling tests.
  

  Test 1 of 1: CPU P-State Checks.
  For each processor in the system, this test steps through the various 
frequency
  states (P-states) that the BIOS advertises for the processor. For each 
processor
  /frequency combination, a quick performance value is measured. The test then
  validates that:
1. Each processor has the same number of frequency states.
2. Higher advertised frequencies have a higher performance.
3. No duplicate frequency values are reported by the BIOS.
4. BIOS doing Sw_All P-state coordination across cores.
5. BIOS doing Sw_Any P-state coordination across cores.

  CPU 0: 14 CPU frequency steps supported.
   Frequency | Relative Speed | Bogo loops
  ---++---
2.45 GHz | 100.0 %|155783
2.45 GHz |  92.3 %|143795
2.35 GHz |  92.3 %|143798
2.25 GHz |  92.3 %|143796
2.15 GHz |  92.3 %|143797
2.05 GHz |  92.3 %|143794
1.95 GHz |  92.3 %|143815
1.85 GHz |  92.3 %|143710
1.75 GHz |  92.3 %|143789
1.65 GHz |  92.3 %|143795
1500 MHz |  92.3 %|143798
1400 MHz |  92.3 %|143799
1300 MHz |  92.3 %|143796
1200 MHz |  92.3 %|143797

  FAILED [MEDIUM] CPUFreqSlowerOnCPU: Test 1, Supposedly higher frequency 1300 
MHz
  is slower (143796 bogo loops) than frequency 1300 MHz (143797 bogo loops) on 
CPU
  0.
  FAILED [MEDIUM] CPUFreqSlowerOnCPU: Test 1, Supposedly higher frequency 1500 
MHz
  is slower (143798 bogo loops) than frequency 1500 MHz (143799 bogo loops) on 
CPU
  0.
  FAILED [MEDIUM] CPUFreqSlowerOnCPU: Test 1, Supposedly higher frequency 1.65 
GHz
  is slower (143795 bogo loops) than frequency 1.65 GHz (143798 bogo loops) on 
CPU
  0.
  FAILED [MEDIUM] CPUFreqSlowerOnCPU: Test 1, Supposedly higher frequency 1.75 
GHz
  is slower (143789 bogo loops) than frequency 1.75 GHz (143795 bogo loops) on 
CPU
  0.
  FAILED [MEDIUM] CPUFreqSlowerOnCPU: Test 1, Supposedly higher frequency 1.85 
GHz
  is slower (143710 bogo loops) than frequency 1.85 GHz (143789 bogo loops) on 
CPU
  0.
  FAILED [MEDIUM] CPUFreqSlowerOnCPU: Test 1, Supposedly higher frequency 2.05 
GHz
  is slower (143794 bogo loops) than frequency 2.05 GHz (143815 bogo loops) on 
CPU
  0.
  FAILED [MEDIUM] CPUFreqSlowerOnCPU: Test 1, Supposedly higher frequency 2.25 
GHz
  is slower (143796 bogo loops) than frequency 2.25 GHz (143797 bogo loops) on 
CPU
  0.
  FAILED [MEDIUM] CPUFreqSlowerOnCPU: Test 1, Supposedly higher frequency 2.45 
GHz
  is slower (143795 bogo loops) than frequency 2.45 GHz (143798 bogo loops) on 
CPU
  0.
  Frequency scaling not supported.

  

  0 passed, 8 failed, 0 warnings, 0 aborted, 0 skipped, 0 info only.
  


  
  0 passed, 8 failed, 0 warnings, 0 aborted, 0 skipped, 0 info only.

  Test Failure Summary
  


  Critical failures: NONE

  High failures: NONE

  Medium failures: 8
   cpufreq: Supposedly higher frequency   1300 MHz is slower (143796 bogo 
loops) than frequency   1300 MHz (143797 bogo loops) on CPU 0.
   cpufreq: Supposedly higher frequency   1500 MHz is slower (143798 bogo 
loops) than frequency   1500 MHz (143799 bogo loops) on CPU 0.
   cpufreq: Supposedly higher frequency   1.65 GHz is slower (143795 bogo 
loops) than frequency   1.65 GHz (143798 bogo loops) on CPU 0.
   cpufreq: Supposedly higher frequency   1.75 GHz is slower (143789 bogo 
loops) than frequency   1.75 GHz (143795 bogo loops) on CPU 0.
   cpufreq: Supposedly higher frequency   1.85 GHz is slower

Re: [Kernel-packages] [Bug 1090002] Re: biosdevname gives name of device as rename7 in Quantal

2013-09-27 Thread Narinder Gupta 
Yeah we ran this issue with biosdevname developer and after close 
examination he told thats the issue with the BIOS firmware where SMBIOS 
entry were not proper. When we tried to run this on later HP FW system 
we do not see the bug anymore.

Will you please let me know you server configuraiton include the 
firmware version?

On 09/27/2013 10:43 AM, Paul Boven wrote:
 Hi Narinder,

 Well, that's exactly the problem - sometime during the boot, apparently
 biosdev thought it was p2p1, and the OS tried to assign the name p2p1 to
 it, which it had already given out. When I run biosdev now, it shows up
 as being p2p2 allright - but the interface doesn't get assigned the name
 p2p2 during boot anymore, and instead I have an unexpected interface
 name 'rename3' show up in my ifconfig. Which breaks things quite badly.



-- 
Thanks and Regards,
Narinder Gupta (PMP)   narinder.gu...@canonical.com
Technical Account Manager
Canonical, Ltd.narindergupta [irc.freenode.net]
+1.281.736.5150narindergupta2007[skype]

Ubuntu- Linux for human beings | www.ubuntu.com | www.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/1090002

Title:
  biosdevname gives name of device as rename7 in Quantal

Status in “linux” package in Ubuntu:
  Confirmed
Status in “udev” package in Ubuntu:
  Confirmed
Status in “linux” source package in Quantal:
  Confirmed
Status in “udev” source package in Quantal:
  Confirmed
Status in “linux” source package in Raring:
  Confirmed
Status in “udev” source package in Raring:
  Confirmed

Bug description:
  In Quantal kernel biosdevname feature is not working as it suppose to
  be. On hardware we are seeing an issue where few of the network
  interface names are named as rename7 etc.. while biosdevname -d
  utility provides the correct biosname while kernel name have been
  messed up. There are total 16 network interfaces on the server which
  are ALOMs for Emulex card connected to system.

  It seems this issue is a race condition and will get fixed in Fedora
  18. But having fix in Quantal will help also.

  https://bugzilla.redhat.com/show_bug.cgi?id=782145

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1090002/+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 1196597] Re: nic-modules udeb does not contain the qlcnic driver for Qlogic

2013-08-02 Thread Narinder Gupta 
Downloaded the latest nic-modules and I can see the qlcnic driver is
there in latest version.

** Tags removed: verification-needed-raring
** Tags added: verification-verfied-raring

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

Title:
  nic-modules udeb does not contain the qlcnic driver for Qlogic

Status in “linux” package in Ubuntu:
  Fix Released
Status in “linux” source package in Raring:
  Fix Committed
Status in “linux” source package in Saucy:
  Fix Released

Bug description:
  SRU Justification

  Impact:

  I am trying to do install on DL360p Gen8 with qlogic card which needs
  qlcnic driver. But installer gives error stating that no network
  controller found. As by default server comes with intel nic but it has
  option to use either intel or Qlogic ALOM. After testing with Qlogic
  ALOM found out that nic-modules udeb does not contains the qlcnic
  driver. When we do not select the nic and keep continue the
  installation no issue kernel comes up file with nic driver installed
  and we need to configure it manually.

  Testing:

  Try to netboot, it either works or it doesn't

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