Messages in this thread | | | Date | Fri, 2 May 2008 12:44:06 -0300 | From | "Carlos R. Mafra" <> | Subject | Re: RFC: starting a kernel-testers group for newbies |
| |
On Fri 2.May'08 at 7:58:25 -0700, Linus Torvalds wrote: > > > On Fri, 2 May 2008, Adrian Bunk wrote: > > > > But for users this is a recent regression since 2.6.24 worked > > and 2.6.25 does not. > > Totally and utterly immaterial. > > If it's a timing-related bug, as far as developers are concerned, nothing > they did introduced the problem. > > So anybody who think s that "process" should have caught it is just being > stupid.
So I would like to ask you what an user should do when facing what is probably a timing-related bug, as it appears I have the bad luck of hitting one.
See for example my comments after this one http://bugzilla.kernel.org/show_bug.cgi?id=10117#c11
This same problem is still present with yesterday's git, and sometimes it hangs without hpet=disable and sometimes it doesn't. (And never with hpet=disable in the boot command line)
And when it hangs I can see only _one_ "Switched to high resolution mode on CPU x" message before the hang point, and when it boots fine there is always the two of them in sequence:
Switched to high resolution mode on CPU 1 Switched to high resolution mode on CPU 0
And using vga=6 or vga=0x0364 makes a difference in the probability of hanging.
I am just waiting -rc1 to be released to send an email with my problem again, as I am unable to debug this myself. I think this is ok from my part, right?
| |