lshw hangs on "PCI (sysfs)"

[enigma_0Z]

Binary package hint: lshw

I'm running on a Core 2 Duo system, specifically a Dell Vostro 1400 notebook. lshw worked with Gutsy, but "sudo lshw" hangs at "PCI (sysfs)" in hardy. It sits here forever as far as I can tell. I believe it has been this way ever since I upgraded to hardy.

lshw-gtk has the same issue.

[enigma_0Z (enigma-0za)]

Someone on the ubuntu IRC channel has the same issue:

http://irclogs.ubuntu.com/2008/03/27/%23ubuntu+1.txt

Someone who is reporting another bug also experienced this:

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

Seems like a pretty bad issue to me...

[Darik Horn (dajhorn)]

Does this patch fix the lshw hang?

The lshw program can loop forever if it does not recognize a PCI capability, or if it gets garbage from sysfs.

[enigma_0Z (enigma-0za)]

pardon my ignorance... I do know how to apply patches, but how do I do this inside a debian system... and what source is this meant to be patched against? Ubuntu's source repo?

Thanks.

[enigma_0Z (enigma-0za)]

nevermind. Google is my friend. Compiling now.

[enigma_0Z (enigma-0za)]

Ok. Tried it. It works.

Was this a regression from Gutsy, or what's going on? It still waits for a while (perhaps approx 30 seconds) on PCI, but AFAIK that's somewhat normal.

Thanks... Can we get this into Hardy?

[Darik Horn (dajhorn)]

> Was this a regression from Gutsy, or what's going on?

No, this bug exists in Gutsy too, but it may not express on your hardware.

> It still waits for a while (perhaps approx 30 seconds) on PCI

This is normal.

> Thanks... Can we get this into Hardy?

Hardy could be released next week, so probably not.

[enigma_0Z (enigma-0za)]

Well, thanks. Perhaps we could get it into a backport for hardy considering it's a LTS release?

AFAIK, lshw did not hang like this on gutsy, does this indicate an issue with my hardware, or is it nothing to be worried about?

And... thanks again. This one's been really bugging me.

[Darik Horn (dajhorn)]

> Perhaps we could get it into a backport for hardy considering it's a LTS release?

Ensure that it gets fixed early in the hardy+1 development so that it can be a backport candidate.

Upstream may already have a fix for this bug here:

  http://www.ezix.org/project/ticket/340

> does this indicate an issue with my hardware, or is it nothing to be worried about?

This is not a hardware problem, so don't worry about it.

[earthmeLon (earthmelon)]

Seems that I was experiencing the same issue. I realized that the program needs to LOAD the information. Try giving the program a few additional seconds and see if it gives you any output.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Jaewon Chang (jaewonac)]

Hello?

Is this bug fixed? I'm using ubuntu 16.04 and experiencing same bug.