memory_compare and get_make_and_model fails on Hitachi CB500 due to lshw issues

[Brian Fromme]

Checkbox certification fails, due to lshw problems.

[Brian Fromme (brianfromme)]

We need the output of 'lshw -json' so we can diagnose our checkbox tools.

Please run:

% lshw -json > lshw.json

and attach the lshw.json file to this bug report.

NOTE:
Canonical will examine the Checkbox memory_compare script.

[Brian Fromme (brianfromme)]

Please also include the output of the following commands:

% lshw -C system

% locale

NOTE: Both comment #1 and #2 should have commands run on the SUT (CB500 system under test).

[Jeff Lane  (bladernr)]

Briefly looked at this today. The text lshw output looks sane. memory_compare uses a json dump however, and get_make_and_model uses the output of lshw -C system

So when we get those we can run them through the parsers to see what the actual cause is.

For now, my initial guess is perhaps a locale setting putting some strange char in there, but that's not a very scientific guess, just a first impression.

[Leticia Fernandez (leticia-fernandez)]

==========================================================================================

Executed the following three commands suggested by Canonical.

1. lshw -json > lshw.json
2. lshw -C system
3. locale

Getting “Segmentation fault (core dumped)” error while running the “lshw” command. Output of above 3 commands is attached herewith as “usb_enable_lshw.json.txt” keeping this condition.

Note that the server blade have only one USB port. Two numbers of USB drives(1 x USB 2.0 and 1x USB 3.0) was connected to the server via an “USB HUB”.

If we disable the “USB” option and re-run the above commands then we are getting some useful output. Attached herewith the output of the 3 commands when ran successfully by disabling the “USB” option from server BIOS. File name as “usb_disable_lshw.json” attached in this email.

==============================================================================================

Please let me know if you face any problem in updating the Launchpad as I am facing.

Thanks in advance for your assistance.
Regards,
PK

[Jeff Lane  (bladernr)]

Hi Tish,

Can you get me the output of 'apt-cache policy lshw' ?

When PK says If we disable the “USB” option, what exactly does he mean? Unplug the Hub? or run using '-disable usb'

Please retry the following:

lshw -json

1: With the USB hub unplugged
2: With ONLY a USB3 stick plugged in

Sounds like the Hub may be the cause of the segfault.

[Jeff Lane  (bladernr)]

Also, if the USB port on that blade is only USB2, then for number 2 above, use a USB2 stick, not a USB3 stick.

[Leticia Fernandez (leticia-fernandez)]

Jeff,

Thanks for looking into this, I will have P answer your questions and get you
the information requested.

Thanks and Regards,

Leticia(Tish) Fernandez|Partner Programs|Mobile: [phone]
Solutions Engineering and Technical Operations (SETO)
HITACHI DATA SYSTEMS, 2845 Lafayette Street, Santa Clara, CA 95050
<email address hidden>

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of Jeff Lane
Sent: Tuesday, August 09, 2016 1:09 PM
To: Leticia Fernandez
Subject: [Bug 1610477] Re: memory_compare and get_make_and_model fails on Hitachi CB500 due to lshw issues

Hi Tish,

Can you get me the output of 'apt-cache policy lshw' ?

When PK says If we disable the “USB” option, what exactly does he mean?
Unplug the Hub? or run using '-disable usb'

Please retry the following:

lshw -json

1: With the USB hub unplugged
2: With ONLY a USB3 stick plugged in

Sounds like the Hub may be the cause of the segfault.

--
You received this bug notification because you are subscribed to the bug report.
https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.launchpad.net_bugs_1610477&d=CwIFaQ&c=DZ-EF4pZfxGSU6MfABwx0g&r=l9sXxKVqL9I8wjKmzWbSOG5sR5YJfjy9tpELdpheCMc&m=K9P22LA_BRCfJccJDeSIO6QtFMp87UI6w-BOUTJjeBI&s=vZX40Tf9-M-_yeF3s5zBBLnLml9AGO6m9_ILgzuCZ08&e=

Title:
  memory_compare and get_make_and_model fails on Hitachi CB500 due to
  lshw issues

Status in Checkbox Provider for PlainBox:
  Incomplete

Bug description:
  Checkbox certification fails, due to lshw problems.

To manage notifications about this bug go to:
https://urldefense.proofpoint.com/v2/url?u=https-3A__bugs.launchpad.net_plainbox-2Dprovider-2Dcheckbox_-2Bbug_1610477_-2Bsubscriptions&d=CwIFaQ&c=DZ-EF4pZfxGSU6MfABwx0g&r=l9sXxKVqL9I8wjKmzWbSOG5sR5YJfjy9tpELdpheCMc&m=K9P22LA_BRCfJccJDeSIO6QtFMp87UI6w-BOUTJjeBI&s=adEoKh3NUoERSBnrk5i1YVQ__wN-7ZUVUSmoEXtBeeE&e=

[Prasanta Kumar Nath (prasanta-nath)]

Here is the answers:

"When PK says If we disable the “USB” option, what exactly does he mean?
Unplug the Hub? or run using '-disable usb'"

From PK : USB option was disabled from server BIOS. Hence the USB drive was not detected by the server.

Logs have been collected for the conditions below and attached herewith -

1: With the USB hub unplugged
 Observation: lshw command executed successfully
2: With ONLY a USB3 stick plugged in
 Observation:gives Segmentation fault (core dumped) 3. : With ONLY a USB2 stick plugged in
 Observation: lshw command executed successfully

[Prasanta Kumar Nath (prasanta-nath)]

Here is the answers to your questions:

"When PK says If we disable the “USB” option, what exactly does he mean?
Unplug the Hub? or run using '-disable usb'"

PK: USB option was disabled in the server BIOS. Hence the USB drive was not detected by the server.

Requested logs were collected for the conditions below and posted herewith-

1: With the USB hub unplugged
 Observation: lshw command executed successfully
2: With ONLY a USB3 stick plugged in
 Observation:gives Segmentation fault (core dumped) 3. : With ONLY a USB2 stick plugged in
 Observation: lshw command executed successfully

[Jeff Lane  (bladernr)]

OK, this isn't a problem with the test tools... I'm not positive if this is a kernel issue, or a lshw issue, but thanks to PKs attachments, I've been able to manually and programmatically parse the outputs for 'lshw -json' and 'lshw -C system' and both parse correctly and both scripts work when modified to read the files PK provided.

So this is the issue:

When this system has a USB3.0 device plugged in, lshw segfaults.
When this system has a USB2.0 device plugged in, lshw does not segfault.

IIRC the USB hub initially used was a USB3.0 Hub with both a USB2.0 and USB3.0 thumbdrive plugged in.

I would suggest a couple things:

1: Re-install Trusty (specifically 14.04.5 if not already on that) and see if this is re-creatable.
2: Install 16.04.1 (Xenial) and see if it occurs there as well.

I've also mentioned all this to Brian.

So the net is I won't block a cert on this issue, as it's a corner case but I think it does need to be figured out and determined if it's a bigger issue than just lshw segfaulting (e.g. will more important things have problems if someone connects a USB3.0 device).

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1610477

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Prasanta Kumar Nath (prasanta-nath)]

We have re-run the failed tests after not plugging anything into the USB3.
Test log “Failed_test_rerun-08292016.zip” is attached herewith.

As requested, we also executed lshw command for Ubuntu 14.04.5 and Ubuntu 16.04.1 while USB 3.0 is plugged in. Observed that lshw is running without any issue for Ubuntu 16.04.1 and giving the same “Segmentation fault (core dumped)” issue for Ubuntu 14.04.5.

Output of lshw command in Ubuntu 14.04.5 and Ubuntu 16.04.1 OS as attached herewith as file name “lshw_output_for_Ubuntu14.04.5_Ubuntu16.04.1.txt”.