Re: HPET regression in 2.6.26 versus 2.6.25 -- found another user with the same regression

[David Witbrodt]

Yinghai,

I finally found time to try to get some output using your patch for
resource.c on a kernel that hangs.

Some really good advice came in earlier today:  I can use "vga=1" to
get 80x50 mode during the early boot sequence.  I used that, and made
some alterations to the changes in your patch to squeeze more info
onto the screen.  I also changed KERN_DEBUG to KERN_ERR in your
printk's so that I could decrease the other output by using 
"loglevel=4".

While I cannot see the entire set of output from your debug printk's,
I can see the last 45+ lines that appear before the hang.  The results
were the same as when I used "hpet=disable":  the only difference 
between the working 2.6.25 kernel and the hanging 2.6.27 kernel was 
that the resource named "0000:00:14.0" (fed00000-fed003ff) switched
from "conflict=0" to "conflict=1".

The output from 'cat /proc/iomem' on a non-hanging kernel included
these two lines:

fed00000-fed003ff : HPET 0
  fed00000-fed003ff : 0000:00:14.0


None of this is really new information, since it matches with info
I've already posted.  I just wanted to let you know the results of
your patch on a kernel that hangs.

If I find a way to read the info from the 15-20 lines that scroll 
away on me, and if I find a difference, I'll post that as well.


DW
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/