.13 kernel and
ran the stress-ng and VM create/stop/restart testing like I did on the
previous version of this patch series. Tests successfully ran on qdf2400
platform, I did not observe any regressions on the Artful 4.13 kernel.
Tested-by: Manoj Iyer <manoj.i...@canonical.com>
--
==
tress-ng and VM create/stop/restart testing like I did on the
previous version of this patch series. Tests successfully ran on qdf2400
platform, I did not observe any regressions on the Artful 4.13 kernel.
Tested-by: Manoj Iyer
--
Manoj Iyer
Ubuntu/Canonical
ARM Servers - Cloud
On Fri, 10 Nov 2017, Manoj Iyer wrote:
On Thu, 9 Nov 2017, Manoj Iyer wrote:
James,
Looks like my VM test raised a false alarm. I retested stock Artful 4.13
kernel (No erratum 1041 patches applied).
James, an update on the crash (false alarm). We suspect this is a firmware
crash due
On Fri, 10 Nov 2017, Manoj Iyer wrote:
On Thu, 9 Nov 2017, Manoj Iyer wrote:
James,
Looks like my VM test raised a false alarm. I retested stock Artful 4.13
kernel (No erratum 1041 patches applied).
James, an update on the crash (false alarm). We suspect this is a firmware
crash due
On Thu, 9 Nov 2017, Manoj Iyer wrote:
James,
Looks like my VM test raised a false alarm. I retested stock Artful 4.13
kernel (No erratum 1041 patches applied).
James, an update on the crash (false alarm). We suspect this is a firmware
crash due to a possible fw bug. Once
On Thu, 9 Nov 2017, Manoj Iyer wrote:
James,
Looks like my VM test raised a false alarm. I retested stock Artful 4.13
kernel (No erratum 1041 patches applied).
James, an update on the crash (false alarm). We suspect this is a firmware
crash due to a possible fw bug. Once
failed. Status=0
[ 464.258973] ACPI CPPC: PCC check channel failed. Status=0
[ 465.283028] ACPI CPPC: PCC check channel failed. Status=0
SYS_DBG: Running SDI image (immediate mode)
SYS_DBG: Ram Dump Init
SYS_DBG: Failed to init SD card
SYS_DBG: Resetting system!
On Thu, 9 Nov 2017, Manoj Iyer
failed. Status=0
[ 464.258973] ACPI CPPC: PCC check channel failed. Status=0
[ 465.283028] ACPI CPPC: PCC check channel failed. Status=0
SYS_DBG: Running SDI image (immediate mode)
SYS_DBG: Ram Dump Init
SYS_DBG: Failed to init SD card
SYS_DBG: Resetting system!
On Thu, 9 Nov 2017, Manoj Iyer
On Thu, 9 Nov 2017, Manoj Iyer wrote:
James,
(sorry for top-posting)
Applied patch 3 patches to Ubuntu Artful Kernel ( 4.13.0-16-generic )
- Start 20 VMs one at a time
In a loop:
- Stop (virsh destroy) 20 VMs one at a time
- Start (virsh start) 20 VMs one at a time.
Fixing some
On Thu, 9 Nov 2017, Manoj Iyer wrote:
James,
(sorry for top-posting)
Applied patch 3 patches to Ubuntu Artful Kernel ( 4.13.0-16-generic )
- Start 20 VMs one at a time
In a loop:
- Stop (virsh destroy) 20 VMs one at a time
- Start (virsh start) 20 VMs one at a time.
Fixing some
] [Hardware Error]: 0030:
On Thu, 9 Nov 2017, James Morse wrote:
Hi Manoj,
On 08/11/17 19:05, Manoj Iyer wrote:
On Thu, 2 Nov 2017, Shanker Donthineni wrote:
The ARM architecture defines the memory locations that are permitted
to be accessed
] [Hardware Error]: 0030:
On Thu, 9 Nov 2017, James Morse wrote:
Hi Manoj,
On 08/11/17 19:05, Manoj Iyer wrote:
On Thu, 2 Nov 2017, Shanker Donthineni wrote:
The ARM architecture defines the memory locations that are permitted
to be accessed
ssions either. I ran the stress-ng tests for over 8hrs found the
system to be stable.
Tested-by: Manoj Iyer <manoj.i...@canonical.com>
Regards
--
Manoj Iyer
Ubuntu/Canonical
ARM Servers - Cloud
s-ng tests for over 8hrs found the
system to be stable.
Tested-by: Manoj Iyer
Regards
--
Manoj Iyer
Ubuntu/Canonical
ARM Servers - Cloud
grate: correct failure handling if
!hugepage_migration_support()")
Reported-by: Manoj Iyer <manoj.i...@canonical.com>
Signed-off-by: Punit Agrawal <punit.agra...@arm.com>
Cc: Joonsoo Kim <iamjoonsoo@lge.com>
Cc: Naoya Horiguchi <n-horigu...@ah.jp.nec.com>
Cc: Wanpeng
grate: correct failure handling if
!hugepage_migration_support()")
Reported-by: Manoj Iyer
Signed-off-by: Punit Agrawal
Cc: Joonsoo Kim
Cc: Naoya Horiguchi
Cc: Wanpeng Li
Cc: Christoph Lameter
---
Hi Andrew,
We ran into this bug when working towards enabling memory corruption
on arm64.
In linux-next struct device dev; was added to struct iommu_device
this breaks calls to iommu_put/get_resv_regions function because
these functions expect struct device * instead.
Please review and consider this patch to fix this.
Thanks
Manoj Iyer
In linux-next struct device dev; was added to struct iommu_device
this breaks calls to iommu_put/get_resv_regions function because
these functions expect struct device * instead.
Please review and consider this patch to fix this.
Thanks
Manoj Iyer
to struct iommu_device instead of
struct device * but the code in drivers/iommu/iommu.c was not refactored
to take this change into account.
Signed-off-by: Manoj Iyer <manoj.i...@canonical.com>
---
drivers/iommu/iommu.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers
to struct iommu_device instead of
struct device * but the code in drivers/iommu/iommu.c was not refactored
to take this change into account.
Signed-off-by: Manoj Iyer
---
drivers/iommu/iommu.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/iommu/iommu.c b/drivers/iommu/iom
Tested on Ubuntu 17.04 (Linux 4.10). I am able to boot the kernel on
QDF2400 platform without any panics.
Tested-by: Manoj Iyer <manoj.i...@canonical.com>
--
====
Manoj Iyer
Ubuntu/Canonical
ARM Servers - Cloud
On Wed, 22 Fe
Tested on Ubuntu 17.04 (Linux 4.10). I am able to boot the kernel on
QDF2400 platform without any panics.
Tested-by: Manoj Iyer
--
Manoj Iyer
Ubuntu/Canonical
ARM Servers - Cloud
On Wed, 22 Feb 2017, Shanker Donthineni wrote
From: Manoj Iyer
Signed-off-by: Manoj Iyer
Reported-by: Timo Aaltonen
Original-author: Timo Aaltonen
BugLink: http://bugs.launchpad.net/bugs/348861
---
drivers/usb/storage/unusual_devs.h |7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/usb/storage/unusual_devs.h
b
From: Manoj Iyer
This patch enables GE0301 3G modem as an interface, the patch has been
part of the Ubuntu kernel for a while but I forgot to upstream.
Test details can be found in the bug http://bugs.launchpad.net/bugs/348861
Please consider this patch for upstream.
Manoj Iyer (1):
USB
From: Manoj Iyer manoj.i...@canonical.com
This patch enables GE0301 3G modem as an interface, the patch has been
part of the Ubuntu kernel for a while but I forgot to upstream.
Test details can be found in the bug http://bugs.launchpad.net/bugs/348861
Please consider this patch for upstream
From: Manoj Iyer manoj.i...@canonical.com
Signed-off-by: Manoj Iyer manoj.i...@canonical.com
Reported-by: Timo Aaltonen tjaal...@ubuntu.com
Original-author: Timo Aaltonen tjaal...@ubuntu.com
BugLink: http://bugs.launchpad.net/bugs/348861
---
drivers/usb/storage/unusual_devs.h |7 +++
1
Chris,
Do you know what systems produce these errors? I can look and see if we
have those for testing your patch.
Cheers
Manoj
On Wed, 21 Nov 2012, Chris Ball wrote:
Hi Manoj, Matsumuro-san,
On Mon, Jul 18 2011, Manoj Iyer wrote:
Right, without the patch I get..
[ 52.526665] mmc0
Chris,
Do you know what systems produce these errors? I can look and see if we
have those for testing your patch.
Cheers
Manoj
On Wed, 21 Nov 2012, Chris Ball wrote:
Hi Manoj, Matsumuro-san,
On Mon, Jul 18 2011, Manoj Iyer wrote:
Right, without the patch I get..
[ 52.526665] mmc0
From: Manoj Iyer
The new B series BIOS has version string 43CN46WW. The driver
requires that 2nd and 3rd characters be 'E' and 'T' respectively,
where as the newer BIOS has 'C' and 'N' respectively. Failing to
load the module causes some of the hotkeys to not work.
Before the patch
From: Manoj Iyer
The new B series BIOS has version string 43CN46WW. The driver
requires that 2nd and 3rd characters be 'E' and 'T' respectively,
where as the newer BIOS has 'C' and 'N' respectively. Failing to
load the module causes some of the hotkeys to not work.
This was tested by me
From: Manoj Iyer manoj.i...@canonical.com
The new B series BIOS has version string 43CN46WW. The driver
requires that 2nd and 3rd characters be 'E' and 'T' respectively,
where as the newer BIOS has 'C' and 'N' respectively. Failing to
load the module causes some of the hotkeys to not work
From: Manoj Iyer manoj.i...@canonical.com
The new B series BIOS has version string 43CN46WW. The driver
requires that 2nd and 3rd characters be 'E' and 'T' respectively,
where as the newer BIOS has 'C' and 'N' respectively. Failing to
load the module causes some of the hotkeys to not work
From: Manoj Iyer
On Intel Panther Point chipset USB 3.0 devices show up as
high-speed devices on powerup, but after an s3 cycle they are
correctly recognized as SuperSpeed. At powerup switch the port
to xHCI so that USB 3.0 devices are correctly recognized.
BugLink: http://bugs.launchpad.net
From: Manoj Iyer
On Intel Panther Point chipset USB 3.0 devices show up as
high-speed devices on powerup, but after an s3 cycle they are
correctly recognized as SuperSpeed. At powerup switch the port
to xHCI so that USB 3.0 devices are correctly recognized.
This is a second attempt at fixing
will send out a new seperate
patch with the fix.
Thanks
Manoj
Thanks,
Andiry
On Tue, 21 Aug 2012, Andiry Xu wrote:
On Tue, Aug 21, 2012 at 12:06 PM, wrote:
From: Manoj Iyer
USB 3.0 devices show up as high-speed devices on powerup, after an
s3 cycle they are correctly recognized
will send out a new seperate
patch with the fix.
Thanks
Manoj
Thanks,
Andiry
On Tue, 21 Aug 2012, Andiry Xu wrote:
On Tue, Aug 21, 2012 at 12:06 PM, manoj.i...@canonical.com wrote:
From: Manoj Iyer manoj.i...@canonical.com
USB 3.0 devices show up as high-speed devices on powerup
From: Manoj Iyer manoj.i...@canonical.com
On Intel Panther Point chipset USB 3.0 devices show up as
high-speed devices on powerup, but after an s3 cycle they are
correctly recognized as SuperSpeed. At powerup switch the port
to xHCI so that USB 3.0 devices are correctly recognized
From: Manoj Iyer manoj.i...@canonical.com
On Intel Panther Point chipset USB 3.0 devices show up as
high-speed devices on powerup, but after an s3 cycle they are
correctly recognized as SuperSpeed. At powerup switch the port
to xHCI so that USB 3.0 devices are correctly recognized.
BugLink: http
as
well.
On Tue, 21 Aug 2012, Andiry Xu wrote:
On Tue, Aug 21, 2012 at 12:06 PM, wrote:
From: Manoj Iyer
USB 3.0 devices show up as high-speed devices on powerup, after an
s3 cycle they are correctly recognized as SuperSpeed. At powerup
unconditionally switch the port to xHCI like we do when
as
well.
On Tue, 21 Aug 2012, Andiry Xu wrote:
On Tue, Aug 21, 2012 at 12:06 PM, manoj.i...@canonical.com wrote:
From: Manoj Iyer manoj.i...@canonical.com
USB 3.0 devices show up as high-speed devices on powerup, after an
s3 cycle they are correctly recognized as SuperSpeed. At powerup
From: Manoj Iyer
USB 3.0 devices show up as high-speed devices on powerup, after an
s3 cycle they are correctly recognized as SuperSpeed. At powerup
unconditionally switch the port to xHCI like we do when we resume
from suspend.
BugLink: http://bugs.launchpad.net/bugs/1000424
Signed-off
From: Manoj Iyer
USB 3.0 devices show up as high-speed devices on powerup, after an
s3 cycle they are correctly recognized as SuperSpeed. At powerup
unconditionally switch the port to xHCI like we do when we resume
from suspend.
BugLink: http://bugs.launchpad.net/bugs/1000424
Test results
From: Manoj Iyer manoj.i...@canonical.com
USB 3.0 devices show up as high-speed devices on powerup, after an
s3 cycle they are correctly recognized as SuperSpeed. At powerup
unconditionally switch the port to xHCI like we do when we resume
from suspend.
BugLink: http://bugs.launchpad.net/bugs
From: Manoj Iyer manoj.i...@canonical.com
USB 3.0 devices show up as high-speed devices on powerup, after an
s3 cycle they are correctly recognized as SuperSpeed. At powerup
unconditionally switch the port to xHCI like we do when we resume
from suspend.
BugLink: http://bugs.launchpad.net/bugs
From: Manoj Iyer
In the latest V-series bios DMI_PRODUCT_VERSION does not contain
the string Lenovo or Thinkpad, but is set to the model number, this
causes the thinkpad_acpi module to fail to load. Recognize laptop
as Lenovo using DMI_BIOS_VENDOR instead, which is set to Lenovo.
Test on V490u
From: Manoj Iyer
In the latest V-series bios DMI_PRODUCT_VERSION does not contain
the string Lenovo or Thinkpad, but is set to the model number, this
causes the thinkpad_acpi module to fail to load. Recognize laptop
as Lenovo using DMI_BIOS_VENDOR instead, which is set to Lenovo.
Signed-off
From: Manoj Iyer
In the latest V-series bios DMI_PRODUCT_VERSION does not contain
the string Lenovo or Thinkpad, but is set to the model number, this
causes the thinkpad_acpi module to fail to load. Recognize laptop
as Lenovo using DMI_BIOS_VENDOR instead, which is set to Lenovo.
Signed-off
From: Manoj Iyer
Please consider this patch to thinkapd_acpi, it loads the module
on V-series systems that do not report with "Lenovo" or "ThinkPad"
prefix to DMI_PRODUCT_VERSION query, but only returns model name.
==
From: Manoj Iyer manoj.i...@canonical.com
Please consider this patch to thinkapd_acpi, it loads the module
on V-series systems that do not report with Lenovo or ThinkPad
prefix to DMI_PRODUCT_VERSION query, but only returns model name
From: Manoj Iyer manoj.i...@canonical.com
In the latest V-series bios DMI_PRODUCT_VERSION does not contain
the string Lenovo or Thinkpad, but is set to the model number, this
causes the thinkpad_acpi module to fail to load. Recognize laptop
as Lenovo using DMI_BIOS_VENDOR instead, which is set
From: Manoj Iyer manoj.i...@canonical.com
In the latest V-series bios DMI_PRODUCT_VERSION does not contain
the string Lenovo or Thinkpad, but is set to the model number, this
causes the thinkpad_acpi module to fail to load. Recognize laptop
as Lenovo using DMI_BIOS_VENDOR instead, which is set
From: Manoj Iyer manoj.i...@canonical.com
In the latest V-series bios DMI_PRODUCT_VERSION does not contain
the string Lenovo or Thinkpad, but is set to the model number, this
causes the thinkpad_acpi module to fail to load. Recognize laptop
as Lenovo using DMI_BIOS_VENDOR instead, which is set
Oops! This is embarrassing! my logic is flawed. Please ignore this patch,
I will resend it
NACK
On Thu, 2 Aug 2012, manoj.i...@canonical.com wrote:
From: Manoj Iyer
In the latest V-series bios DMI_PRODUCT_VERSION does not contain
the string Lenovo or Thinkpad, but is set to the model
From: Manoj Iyer
In the latest V-series bios DMI_PRODUCT_VERSION does not contain
the string Lenovo or Thinkpad, but is set to the model number, this
causes the thinkpad_acpi module to fail to load. Recognize laptop
as Lenovo using DMI_BIOS_VENDOR instead, which is set to Lenovo.
Signed-off
From: Manoj Iyer
In the latest V-series bios DMI_PRODUCT_VERSION does not contain
the string Lenovo or Thinkpad, but is set to the model number, this
causes the thinkpad_acpi module to fail to load. Recognize laptop
as Lenovo using DMI_BIOS_VENDOR instead, which is set to Lenovo.
BIOS
From: Manoj Iyer manoj.i...@canonical.com
In the latest V-series bios DMI_PRODUCT_VERSION does not contain
the string Lenovo or Thinkpad, but is set to the model number, this
causes the thinkpad_acpi module to fail to load. Recognize laptop
as Lenovo using DMI_BIOS_VENDOR instead, which is set
From: Manoj Iyer manoj.i...@canonical.com
In the latest V-series bios DMI_PRODUCT_VERSION does not contain
the string Lenovo or Thinkpad, but is set to the model number, this
causes the thinkpad_acpi module to fail to load. Recognize laptop
as Lenovo using DMI_BIOS_VENDOR instead, which is set
Oops! This is embarrassing! my logic is flawed. Please ignore this patch,
I will resend it
NACK
On Thu, 2 Aug 2012, manoj.i...@canonical.com wrote:
From: Manoj Iyer manoj.i...@canonical.com
In the latest V-series bios DMI_PRODUCT_VERSION does not contain
the string Lenovo or Thinkpad
From: Manoj Iyer
Patch adds support for BCM20702A0 device id (0a5c:21f4).
usb-devices after patch was applied:
T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0a5c ProdID=21f4 Rev=01.12
S: Manufacturer=Broadcom
From: Manoj Iyer manoj.i...@canonical.com
Patch adds support for BCM20702A0 device id (0a5c:21f4).
usb-devices after patch was applied:
T: Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0a5c ProdID=21f4 Rev=01.12
S
Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)
Hi Manoj,
* Manoj Iyer [2012-04-11 13:39:23 -0500]:
usb-devices:
T: Bus=01 Lev=02 Prnt=02 Port=03 Cnt=02 Dev#= 4
Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)
Hi Manoj,
* Manoj Iyer manoj.i...@canonical.com [2012-04-11 13:39:23 -0500]:
usb-devices:
T: Bus=01 Lev=02 Prnt=02
62 matches
Mail list logo
