Hi, We believe that this bug was fixed by a new kernel (2.6.35-21.30) released a couple of weeks ago. Please test that the
lshw
command completes on your machine without an oops, and comment here either way.
Dave
Hi,
We believe that this bug was fixed by a new kernel (2.6.35-21.30) released a couple of weeks ago. Please test that the
lshw
command completes on your machine without an oops, and comment here either way.
Dave