On Wed, 7 Mar 2007 23:49:14 +0000 Ash Milsted <thatistosayiseenem@xxxxxxxxx> wrote: > On Wed, 7 Mar 2007 21:25:34 +0000 > Ash Milsted <thatistosayiseenem@xxxxxxxxx> wrote: > > > On Wed, 7 Mar 2007 12:00:04 +0000 > > Ash Milsted <thatistosayiseenem@xxxxxxxxx> wrote: > > > > > On Sun, 4 Mar 2007 14:23:50 +0000 > > > Ash Milsted <thatistosayiseenem@xxxxxxxxx> wrote: > > > > > > > On Sat, 3 Mar 2007 15:14:24 +0000 > > > > Ash Milsted <thatistosayiseenem@xxxxxxxxx> wrote: > > > > > > > > > Hi, > > > > > With 2.6.21-rc2-git1 I have a problem with my ps/2 port keyboard - it only works > > > > > with one of the following on the command-line: > > > > > - nolapic > > > > > - irqfixup > > > > > - pci=noacpi > > > > > Otherwise it gets stuck with the numlock on. > > > > > The following options have no effect: > > > > > - nohz=off (who knows eh?) > > > > > - pci=nomsi > > > > > > > > snip > > > > > > > > > > Ash > > > > > > > > Just checked 2.6.21-rc2-mm1, still has the problem. > > > > Also, acpi=noirq fixes it too. > > > > To clarify, the problem is that my ps/2 port keyboard is completely frozen > > > > on boot - usually it gets activated when udev probes for hardware (my kernel > > > > config is highly modular). It worked fine with 2.6.20 and earlier with acpi > > > > taking care of interrupt routing. > > > > > > > > Ash > > > > > > Any thoughts on this? It still occurs with 2.6.21-rc3. Here's my config > > > in case that helps. You'll see that I have swap-prefetch patched in (I > > > also have RDSL and some VM changes in there), but I have confirmed that > > > the problem occurs with no extra patches. By the way, I tested mm1 with > > > a rather different config (I used my distro package) and still saw the > > > problem. > > > > > > Also, you should probably ignore that bit above where I suggest the > > > keyboard driver is being loaded as a module, because of course it > > > isn't.. Yet it does start responding (with pci=noacpi) at about that > > > time that udev does its thing. > > > > > schnip > > > > So, I tracked this down to 2.6.21-git7, the first snapshot that gives me > > this problem. Tellingly it does contain an input tree merge. I would git bisect > > but I don't have a local copy of the tree - I tried to get one, but it stopped > > halfway through the clone, probably because I had to use http... So, I hope that > > helps. > > > > Ash > > > > PS: I should have said I'm not subscribed, so please CC me on reply. > > PPS: That almost rhymes. Almost. > > Apologies for only replying to my own mails, but I need to be CC'd if > any alternative is to be convenient :) > > Linus, thanks for your detailed messages. I will try to get a bisect done, but > the university firewall is likely to put up a fight against rsync as much as it > does with the git protocol. We will see. And yeah, that 2.6.21-git7 business was > a typo, should've been 2.6.20-git7, natch. > ker-cut >Argh, I can't believe I forgot to get this into my tree. Could you >please tell me if the patch below fixes ytour issue? Yup, that patch really hit the spot. Now I don't have to bisect :) Thanks for your help (both of you), Ash - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
