Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-18 Thread Alan Stern
On Sun, 18 Mar 2007, Jiri Slaby wrote: > Alan Stern napsal(a): > > On Sun, 18 Mar 2007, Jiri Slaby wrote: > > > >> Alan Stern napsal(a): > >>> In drivers/usb/host/uhci-q.c, near the start is a function named > >>> uhci_fsbr_on(). Put a "return" statement right at its beginning so that > >>> the

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-18 Thread Jiri Slaby
Alan Stern napsal(a): On Sun, 18 Mar 2007, Jiri Slaby wrote: Alan Stern napsal(a): In drivers/usb/host/uhci-q.c, near the start is a function named uhci_fsbr_on(). Put a "return" statement right at its beginning so that the function doesn't do anything. Does that make any difference? Yes,

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-18 Thread Alan Stern
On Sun, 18 Mar 2007, Jiri Slaby wrote: > Alan Stern napsal(a): > > In drivers/usb/host/uhci-q.c, near the start is a function named > > uhci_fsbr_on(). Put a "return" statement right at its beginning so that > > the function doesn't do anything. Does that make any difference? > > Yes, it

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-18 Thread Jiri Slaby
Alan Stern napsal(a): In drivers/usb/host/uhci-q.c, near the start is a function named uhci_fsbr_on(). Put a "return" statement right at its beginning so that the function doesn't do anything. Does that make any difference? Yes, it works. regards, -- http://www.fi.muni.cz/~xslaby/

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-18 Thread Alan Stern
On Sun, 18 Mar 2007, Jiri Slaby wrote: > Alan Stern napsal(a): > > Nothing in the log stands out. Can you collect an equivalent log using a > > version of uhci-hcd with the "eliminate skeleton QHs" patch reverted? > > Perhaps there will be a significant difference. Although I doubt it... ...

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-18 Thread Jiri Slaby
Alan Stern napsal(a): Nothing in the log stands out. Can you collect an equivalent log using a version of uhci-hcd with the "eliminate skeleton QHs" patch reverted? Perhaps there will be a significant difference. Although I doubt it... f74d8f40 3949330898 C Ii:001:01 0 1 = 04 f74d8f40

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-18 Thread Jiri Slaby
Alan Stern napsal(a): Nothing in the log stands out. Can you collect an equivalent log using a version of uhci-hcd with the eliminate skeleton QHs patch reverted? Perhaps there will be a significant difference. Although I doubt it... f74d8f40 3949330898 C Ii:001:01 0 1 = 04 f74d8f40

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-18 Thread Alan Stern
On Sun, 18 Mar 2007, Jiri Slaby wrote: Alan Stern napsal(a): Nothing in the log stands out. Can you collect an equivalent log using a version of uhci-hcd with the eliminate skeleton QHs patch reverted? Perhaps there will be a significant difference. Although I doubt it... ... The

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-18 Thread Jiri Slaby
Alan Stern napsal(a): In drivers/usb/host/uhci-q.c, near the start is a function named uhci_fsbr_on(). Put a return statement right at its beginning so that the function doesn't do anything. Does that make any difference? Yes, it works. regards, -- http://www.fi.muni.cz/~xslaby/

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-18 Thread Alan Stern
On Sun, 18 Mar 2007, Jiri Slaby wrote: Alan Stern napsal(a): In drivers/usb/host/uhci-q.c, near the start is a function named uhci_fsbr_on(). Put a return statement right at its beginning so that the function doesn't do anything. Does that make any difference? Yes, it works. Okay.

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-18 Thread Jiri Slaby
Alan Stern napsal(a): On Sun, 18 Mar 2007, Jiri Slaby wrote: Alan Stern napsal(a): In drivers/usb/host/uhci-q.c, near the start is a function named uhci_fsbr_on(). Put a return statement right at its beginning so that the function doesn't do anything. Does that make any difference? Yes, it

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-18 Thread Alan Stern
On Sun, 18 Mar 2007, Jiri Slaby wrote: Alan Stern napsal(a): On Sun, 18 Mar 2007, Jiri Slaby wrote: Alan Stern napsal(a): In drivers/usb/host/uhci-q.c, near the start is a function named uhci_fsbr_on(). Put a return statement right at its beginning so that the function doesn't do

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-17 Thread Alan Stern
On Sat, 17 Mar 2007, Jiri Slaby wrote: > Alan Stern napsal(a): > > On Tue, 13 Mar 2007, Jiri Slaby wrote: > > > >> So, do you mean rmmod uhci_hcd, unplug the keyboard, modprobe > >> uhci_hcd, start usbmon, plug the keyboard, press numlock, stop usbmon, > >> post it? > > Here you are: ... >

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-17 Thread Jiri Slaby
Alan Stern napsal(a): On Tue, 13 Mar 2007, Jiri Slaby wrote: So, do you mean rmmod uhci_hcd, unplug the keyboard, modprobe uhci_hcd, start usbmon, plug the keyboard, press numlock, stop usbmon, post it? Here you are: f78666c0 1992239699 C Ii:001:01 -2 0 f74d7b40 1996231756 S Ci:001:00 s 80

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-17 Thread Jiri Slaby
Alan Stern napsal(a): On Tue, 13 Mar 2007, Jiri Slaby wrote: So, do you mean rmmod uhci_hcd, unplug the keyboard, modprobe uhci_hcd, start usbmon, plug the keyboard, press numlock, stop usbmon, post it? Here you are: f78666c0 1992239699 C Ii:001:01 -2 0 f74d7b40 1996231756 S Ci:001:00 s 80

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-17 Thread Alan Stern
On Sat, 17 Mar 2007, Jiri Slaby wrote: Alan Stern napsal(a): On Tue, 13 Mar 2007, Jiri Slaby wrote: So, do you mean rmmod uhci_hcd, unplug the keyboard, modprobe uhci_hcd, start usbmon, plug the keyboard, press numlock, stop usbmon, post it? Here you are: ... (Remind: there is a

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-16 Thread Jiri Slaby
On 3/15/07, Alan Stern <[EMAIL PROTECTED]> wrote: By the way, what happens if you press CapsLock rather than NumLock? It should behave pretty the same, sending a command to the keyboard to change an LED setting. Does the keyboard then stop working in the same way? Yes, and hence the *lock in

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-16 Thread Jiri Slaby
On 3/15/07, Alan Stern [EMAIL PROTECTED] wrote: By the way, what happens if you press CapsLock rather than NumLock? It should behave pretty the same, sending a command to the keyboard to change an LED setting. Does the keyboard then stop working in the same way? Yes, and hence the *lock in

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-15 Thread Alan Stern
On Tue, 13 Mar 2007, Jiri Slaby wrote: > So, do you mean rmmod uhci_hcd, unplug the keyboard, modprobe > uhci_hcd, start usbmon, plug the keyboard, press numlock, stop usbmon, > post it? By the way, what happens if you press CapsLock rather than NumLock? It should behave pretty the same,

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-15 Thread Alan Stern
On Tue, 13 Mar 2007, Jiri Slaby wrote: So, do you mean rmmod uhci_hcd, unplug the keyboard, modprobe uhci_hcd, start usbmon, plug the keyboard, press numlock, stop usbmon, post it? By the way, what happens if you press CapsLock rather than NumLock? It should behave pretty the same, sending

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-13 Thread Alan Stern
On Tue, 13 Mar 2007, Jiri Slaby wrote: > On 3/13/07, Alan Stern <[EMAIL PROTECTED]> wrote: > > I don't see anything in the UHCI snapshots to explain the difference in > > behavior. One thing that stands out is the other, low-speed device (a > > mouse?) -- in the bad kernel dump its driver was

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-13 Thread Jiri Slaby
On 3/13/07, Alan Stern <[EMAIL PROTECTED]> wrote: I don't see anything in the UHCI snapshots to explain the difference in behavior. One thing that stands out is the other, low-speed device (a mouse?) -- in the bad kernel dump its driver was running and in the good kernel dump its driver wasn't.

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-13 Thread Alan Stern
On Mon, 12 Mar 2007, Jiri Slaby wrote: > Alan, sorry for the previous bad post, I mismatched 2 files. This is > hopefully correct. > > > thanks. Could you also please redo the test with the offending uhci patch > > reverted and send the output of a working situation? > > - BAD kernel: > >

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-13 Thread Alan Stern
On Mon, 12 Mar 2007, Jiri Slaby wrote: Alan, sorry for the previous bad post, I mismatched 2 files. This is hopefully correct. thanks. Could you also please redo the test with the offending uhci patch reverted and send the output of a working situation? - BAD kernel: USBMON

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-13 Thread Jiri Slaby
On 3/13/07, Alan Stern [EMAIL PROTECTED] wrote: I don't see anything in the UHCI snapshots to explain the difference in behavior. One thing that stands out is the other, low-speed device (a mouse?) -- in the bad kernel dump its driver was running and in the good kernel dump its driver wasn't.

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-13 Thread Alan Stern
On Tue, 13 Mar 2007, Jiri Slaby wrote: On 3/13/07, Alan Stern [EMAIL PROTECTED] wrote: I don't see anything in the UHCI snapshots to explain the difference in behavior. One thing that stands out is the other, low-speed device (a mouse?) -- in the bad kernel dump its driver was running and

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-12 Thread Jiri Slaby
Jiri Kosina napsal(a): (trimmed CC list a bit) On Mon, 12 Mar 2007, Jiri Slaby wrote: UHCI: Eliminate asynchronous skeleton Queue Headers Post it along with the usbmon log, and I'll try to figure out what happened. Here it comes: USBMON: f7525b40 1832950485 C Ii:004:01 0 8 = 5300

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-12 Thread Jiri Kosina
(trimmed CC list a bit) On Mon, 12 Mar 2007, Jiri Slaby wrote: > > > UHCI: Eliminate asynchronous skeleton Queue Headers > > Post it along with the usbmon log, and I'll try to figure out what happened. > Here it comes: > USBMON: > f7525b40 1832950485 C Ii:004:01 0 8 = 5300 >

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-12 Thread Alan Stern
On Mon, 12 Mar 2007, Jiri Slaby wrote: > Alan Stern napsal(a): > > On Mon, 12 Mar 2007, Jiri Slaby wrote: > > > >> Bisecting figured out the culprit: > >> Commit: 17230acdc71137622ca7dfd789b3944c75d39404 > >> Author: Alan Stern <[EMAIL PROTECTED]> Mon, 19 Feb 2007 15:52:45 -0500 > >> > >>

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-12 Thread Jiri Slaby
Alan Stern napsal(a): On Mon, 12 Mar 2007, Jiri Slaby wrote: Bisecting figured out the culprit: Commit: 17230acdc71137622ca7dfd789b3944c75d39404 Author: Alan Stern <[EMAIL PROTECTED]> Mon, 19 Feb 2007 15:52:45 -0500 UHCI: Eliminate asynchronous skeleton Queue Headers [...] Post it along

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-12 Thread Alan Stern
On Mon, 12 Mar 2007, Jiri Slaby wrote: > Bisecting figured out the culprit: > Commit: 17230acdc71137622ca7dfd789b3944c75d39404 > Author: Alan Stern <[EMAIL PROTECTED]> Mon, 19 Feb 2007 15:52:45 -0500 > > UHCI: Eliminate asynchronous skeleton Queue Headers > > This patch (as856)

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-12 Thread Jiri Slaby
Jiri Kosina napsal(a): On Sun, 11 Mar 2007, Jiri Slaby wrote: - /* make sure the unused bits in the last byte are zeros */ - if (count > 0 && size > 0) - data[(offset+count*size-1)/8] = 0; - No, this doesn't help -- -rc3-mm2 minus this behaves exactly the same.

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-12 Thread Jiri Slaby
Jiri Kosina napsal(a): On Sun, 11 Mar 2007, Jiri Slaby wrote: - /* make sure the unused bits in the last byte are zeros */ - if (count 0 size 0) - data[(offset+count*size-1)/8] = 0; - No, this doesn't help -- -rc3-mm2 minus this behaves exactly the same. [...]

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-12 Thread Alan Stern
On Mon, 12 Mar 2007, Jiri Slaby wrote: Bisecting figured out the culprit: Commit: 17230acdc71137622ca7dfd789b3944c75d39404 Author: Alan Stern [EMAIL PROTECTED] Mon, 19 Feb 2007 15:52:45 -0500 UHCI: Eliminate asynchronous skeleton Queue Headers This patch (as856) attempts to

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-12 Thread Jiri Slaby
Alan Stern napsal(a): On Mon, 12 Mar 2007, Jiri Slaby wrote: Bisecting figured out the culprit: Commit: 17230acdc71137622ca7dfd789b3944c75d39404 Author: Alan Stern [EMAIL PROTECTED] Mon, 19 Feb 2007 15:52:45 -0500 UHCI: Eliminate asynchronous skeleton Queue Headers [...] Post it along

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-12 Thread Alan Stern
On Mon, 12 Mar 2007, Jiri Slaby wrote: Alan Stern napsal(a): On Mon, 12 Mar 2007, Jiri Slaby wrote: Bisecting figured out the culprit: Commit: 17230acdc71137622ca7dfd789b3944c75d39404 Author: Alan Stern [EMAIL PROTECTED] Mon, 19 Feb 2007 15:52:45 -0500 UHCI: Eliminate

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-12 Thread Jiri Kosina
(trimmed CC list a bit) On Mon, 12 Mar 2007, Jiri Slaby wrote: UHCI: Eliminate asynchronous skeleton Queue Headers Post it along with the usbmon log, and I'll try to figure out what happened. Here it comes: USBMON: f7525b40 1832950485 C Ii:004:01 0 8 = 5300 f7525b40

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-12 Thread Jiri Slaby
Jiri Kosina napsal(a): (trimmed CC list a bit) On Mon, 12 Mar 2007, Jiri Slaby wrote: UHCI: Eliminate asynchronous skeleton Queue Headers Post it along with the usbmon log, and I'll try to figure out what happened. Here it comes: USBMON: f7525b40 1832950485 C Ii:004:01 0 8 = 5300

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-11 Thread Jiri Slaby
Jiri Slaby napsal(a): Jiri Kosina napsal(a): Hmm, strange, I did bet that this would have solved the problem, as the code is for sure bogus and could be causing these kinds of problems (I Hmm, so I'll check this out again to eliminate human factor. verified. --

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-11 Thread Jiri Slaby
Jiri Kosina napsal(a): On Sun, 11 Mar 2007, Jiri Slaby wrote: - /* make sure the unused bits in the last byte are zeros */ - if (count > 0 && size > 0) - data[(offset+count*size-1)/8] = 0; - No, this doesn't help -- -rc3-mm2 minus this behaves exactly the same. -rc3

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-11 Thread Jiri Kosina
On Sun, 11 Mar 2007, Jiri Slaby wrote: > > - /* make sure the unused bits in the last byte are zeros */ > > - if (count > 0 && size > 0) > > - data[(offset+count*size-1)/8] = 0; > > - > No, this doesn't help -- -rc3-mm2 minus this behaves exactly the same. > -rc3 without this patch

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-11 Thread Jiri Slaby
Jiri Kosina napsal(a): On Fri, 9 Mar 2007, Jiri Kosina wrote: If this is present also in vanilla and not only in -mm, could you please try reverting commits 4237081e573b99a48991aa71364b0682c444651c and d4ae650a904612ffb7edd3f28b69b022988d2466 and let me know if the situation gets any better?

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-11 Thread Jiri Slaby
Jiri Kosina napsal(a): On Fri, 9 Mar 2007, Jiri Kosina wrote: If this is present also in vanilla and not only in -mm, could you please try reverting commits 4237081e573b99a48991aa71364b0682c444651c and d4ae650a904612ffb7edd3f28b69b022988d2466 and let me know if the situation gets any better?

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-11 Thread Jiri Kosina
On Sun, 11 Mar 2007, Jiri Slaby wrote: - /* make sure the unused bits in the last byte are zeros */ - if (count 0 size 0) - data[(offset+count*size-1)/8] = 0; - No, this doesn't help -- -rc3-mm2 minus this behaves exactly the same. -rc3 without this patch too. Going

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-11 Thread Jiri Slaby
Jiri Kosina napsal(a): On Sun, 11 Mar 2007, Jiri Slaby wrote: - /* make sure the unused bits in the last byte are zeros */ - if (count 0 size 0) - data[(offset+count*size-1)/8] = 0; - No, this doesn't help -- -rc3-mm2 minus this behaves exactly the same. -rc3

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-11 Thread Jiri Slaby
Jiri Slaby napsal(a): Jiri Kosina napsal(a): Hmm, strange, I did bet that this would have solved the problem, as the code is for sure bogus and could be causing these kinds of problems (I Hmm, so I'll check this out again to eliminate human factor. verified. --

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-09 Thread Jiri Slaby
On 3/9/07, Jiri Slaby <[EMAIL PROTECTED]> wrote: I don't know if this is related, but my notebook keyboard doesn't emit numbers with numlock (not even directly Fn+blue number) anymore with -rc3 (note that LED is flashing when numlock is on). I think -rc2 worked fine (I'm going to check this

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-09 Thread Jiri Slaby
On 3/9/07, Jiri Kosina <[EMAIL PROTECTED]> wrote: On Fri, 9 Mar 2007, Jiri Kosina wrote: > If this is present also in vanilla and not only in -mm, could you please > try reverting commits 4237081e573b99a48991aa71364b0682c444651c and > d4ae650a904612ffb7edd3f28b69b022988d2466 and let me know if

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-09 Thread Jiri Kosina
On Fri, 9 Mar 2007, Jiri Kosina wrote: > If this is present also in vanilla and not only in -mm, could you please > try reverting commits 4237081e573b99a48991aa71364b0682c444651c and > d4ae650a904612ffb7edd3f28b69b022988d2466 and let me know if the > situation gets any better? Hi Jiri, or

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-09 Thread Jiri Kosina
On Fri, 9 Mar 2007, Dmitry Torokhov wrote: > > > > > (II) evdev brain: Rescanning devices (12). > > > > > (II) evdev brain: Rescanning devices (13). > > > > > (II) evdev brain: Rescanning devices (14). > > > > > in this kernel, but I don't know if this is relevant. > > > > > After booting back to

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-09 Thread Dmitry Torokhov
On 3/9/07, Jiri Slaby <[EMAIL PROTECTED]> wrote: Andrew Morton napsal(a): > On Sat, 03 Mar 2007 16:54:45 +0100 Jiri Slaby <[EMAIL PROTECTED]> wrote: > >> >> Jiri Slaby napsal(a): >>> Andrew Morton napsal(a): >>>> Temporarily at >>

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-09 Thread Jiri Slaby
Andrew Morton napsal(a): On Sat, 03 Mar 2007 16:54:45 +0100 Jiri Slaby <[EMAIL PROTECTED]> wrote: Jiri Slaby napsal(a): Andrew Morton napsal(a): Temporarily at http://userweb.kernel.org/~akpm/2.6.21-rc2-mm1/ Weird behaviour of numlock and capslock on USB keyboard in X. After Hmm

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-09 Thread Jiri Slaby
Andrew Morton napsal(a): On Sat, 03 Mar 2007 16:54:45 +0100 Jiri Slaby [EMAIL PROTECTED] wrote: Jiri Slaby napsal(a): Andrew Morton napsal(a): Temporarily at http://userweb.kernel.org/~akpm/2.6.21-rc2-mm1/ Weird behaviour of numlock and capslock on USB keyboard in X. After Hmm, it's

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-09 Thread Dmitry Torokhov
On 3/9/07, Jiri Slaby [EMAIL PROTECTED] wrote: Andrew Morton napsal(a): On Sat, 03 Mar 2007 16:54:45 +0100 Jiri Slaby [EMAIL PROTECTED] wrote: Jiri Slaby napsal(a): Andrew Morton napsal(a): Temporarily at http://userweb.kernel.org/~akpm/2.6.21-rc2-mm1/ Weird behaviour of numlock

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-09 Thread Jiri Kosina
On Fri, 9 Mar 2007, Dmitry Torokhov wrote: (II) evdev brain: Rescanning devices (12). (II) evdev brain: Rescanning devices (13). (II) evdev brain: Rescanning devices (14). in this kernel, but I don't know if this is relevant. After booting back to .20-mm2 everything is

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-09 Thread Jiri Kosina
On Fri, 9 Mar 2007, Jiri Kosina wrote: If this is present also in vanilla and not only in -mm, could you please try reverting commits 4237081e573b99a48991aa71364b0682c444651c and d4ae650a904612ffb7edd3f28b69b022988d2466 and let me know if the situation gets any better? Hi Jiri, or even

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-09 Thread Jiri Slaby
On 3/9/07, Jiri Kosina [EMAIL PROTECTED] wrote: On Fri, 9 Mar 2007, Jiri Kosina wrote: If this is present also in vanilla and not only in -mm, could you please try reverting commits 4237081e573b99a48991aa71364b0682c444651c and d4ae650a904612ffb7edd3f28b69b022988d2466 and let me know if the

Re: Keyboard stops working after *lock [Was: 2.6.21-rc2-mm1]

2007-03-09 Thread Jiri Slaby
On 3/9/07, Jiri Slaby [EMAIL PROTECTED] wrote: I don't know if this is related, but my notebook keyboard doesn't emit numbers with numlock (not even directly Fn+blue number) anymore with -rc3 (note that LED is flashing when numlock is on). I think -rc2 worked fine (I'm going to check this too).

Re: i2c vs nVidia [Re: 2.6.21-rc2-mm1]

2007-03-06 Thread Jean Delvare
Hi All, On Tue, 6 Mar 2007 09:45:43 +0100, Jean Delvare wrote: > > > I guess we need to wait and see if someone hits the same problems > > > with an in-kernel driver. > > I just did, with i2c-nforce2. The key to trigger it seems to be to load > an i2c bus driver _after_ loading i2c-isa and a

Re: i2c vs nVidia [Re: 2.6.21-rc2-mm1]

2007-03-06 Thread Jean Delvare
Mar 2007 03:00:26 -0800, Andrew Morton <[EMAIL PROTECTED]> > > > wrote: > > > > > > > > > > > Temporarily at > > > > > > > > http://userweb.kernel.org/~akpm/2.6.21-rc2-mm1/ > > > > > > > > > > Mor

Re: i2c vs nVidia [Re: 2.6.21-rc2-mm1]

2007-03-06 Thread Jean Delvare
: Temporarily at http://userweb.kernel.org/~akpm/2.6.21-rc2-mm1/ More things... Yes, this is related to nVidia driver. First of all, I'm not asking for help for a broken closed-source driver. I just want Linux to be foolbullet-proof

Re: i2c vs nVidia [Re: 2.6.21-rc2-mm1]

2007-03-06 Thread Jean Delvare
Hi All, On Tue, 6 Mar 2007 09:45:43 +0100, Jean Delvare wrote: I guess we need to wait and see if someone hits the same problems with an in-kernel driver. I just did, with i2c-nforce2. The key to trigger it seems to be to load an i2c bus driver _after_ loading i2c-isa and a suitable

Re: i2c vs nVidia [Re: 2.6.21-rc2-mm1]

2007-03-05 Thread Greg KH
> > > > > Temporarily at > > > > > > http://userweb.kernel.org/~akpm/2.6.21-rc2-mm1/ > > > > > > > More things... > > > > Yes, this is related to nVidia driver. First of all, I'm not asking for help > > for a broken closed-source driver

Re: i2c vs nVidia [Re: 2.6.21-rc2-mm1]

2007-03-05 Thread Andrew Morton
On Tue, 6 Mar 2007 01:16:21 +0100 "J.A. Magall__n" <[EMAIL PROTECTED]> wrote: > On Fri, 2 Mar 2007 03:00:26 -0800, Andrew Morton <[EMAIL PROTECTED]> wrote: > > > > > Temporarily at > > > > http://userweb.kernel.org/~akpm/2.6.21-rc2-mm1

i2c vs nVidia [Re: 2.6.21-rc2-mm1]

2007-03-05 Thread J.A. Magallón
On Fri, 2 Mar 2007 03:00:26 -0800, Andrew Morton <[EMAIL PROTECTED]> wrote: > > Temporarily at > > http://userweb.kernel.org/~akpm/2.6.21-rc2-mm1/ > More things... Yes, this is related to nVidia driver. First of all, I'm not asking for help for a broken closed-sourc

Re: 2.6.21-rc2-mm1

2007-03-05 Thread Andrew Morton
On Mon, 5 Mar 2007 23:20:58 +0100 "J.A. Magall__n" <[EMAIL PROTECTED]> wrote: > On Fri, 2 Mar 2007 03:00:26 -0800, Andrew Morton <[EMAIL PROTECTED]> wrote: > > > > > Temporarily at > > > > http://userweb.kernel.org/~akpm/2.6.21-rc2-mm

Re: 2.6.21-rc2-mm1

2007-03-05 Thread J.A. Magallón
On Fri, 2 Mar 2007 03:00:26 -0800, Andrew Morton <[EMAIL PROTECTED]> wrote: > > Temporarily at > > http://userweb.kernel.org/~akpm/2.6.21-rc2-mm1/ > > Will appear later at > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc

Re: 2.6.21-rc2-mm1: drivers/usb/host/ohci-ssb.c doesn't compile

2007-03-05 Thread Michael Buesch
On Monday 05 March 2007 19:42, David Brownell wrote: > On Monday 05 March 2007 3:26 am, Michael Buesch wrote: > > > > Actually, it seems like I will run into other kinds of nasty problems > > > due to stupid design of the HCD code. The OHCI code #includes > > > the various drivers, which have a

Re: 2.6.21-rc2-mm1: drivers/usb/host/ohci-ssb.c doesn't compile

2007-03-05 Thread David Brownell
On Monday 05 March 2007 3:26 am, Michael Buesch wrote: > > Actually, it seems like I will run into other kinds of nasty problems > > due to stupid design of the HCD code. The OHCI code #includes > > the various drivers, which have a module_init each. So if you > > compile PCI and SSB support, you

Re: 2.6.21-rc2-mm1: drivers/usb/host/ohci-ssb.c doesn't compile

2007-03-05 Thread Adrian Bunk
> > > > > /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-hcd.c:931: > > > > > /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-ssb.c:47: > > > > > error: request for member 'hcd_priv_size' in somethi

Re: 2.6.21-rc2-mm1: drivers/usb/host/ohci-ssb.c doesn't compile

2007-03-05 Thread Greg KH
On Mon, Mar 05, 2007 at 12:26:45PM +0100, Michael Buesch wrote: > On Monday 05 March 2007 11:57, Michael Buesch wrote: > > > > CC drivers/usb/host/ohci-hcd.o > > > > In file included from > > > > /home/bunk/linux/kernel-2.6/linux-2.6.21-

Re: 2.6.21-rc2-mm1

2007-03-05 Thread Zan Lynx
encing. I have not been able to get my laptop to run 2.6.21-rc2-mm1 for more than 5 minutes. The last kernel I had working was 2.6.20-rc6-mm3. The problems may be multiple. Whenever I load the new bcm43xx drivers and do *anything* with iwconfig, it locks hard. No keyboard LEDs, and sysrq does n

Re: 2.6.21-rc2-mm1 -- WARNING: "pcmcia_access_configuration_register" [drivers/ssb/ssb.ko] undefined!

2007-03-05 Thread Randy Dunlap
On Mon, 5 Mar 2007 11:11:29 +0100 Michael Buesch wrote: > On Monday 05 March 2007 05:21, Miles Lane wrote: > > WARNING: "pcmcia_access_configuration_register" [drivers/ssb/ssb.ko] > > undefined! > > WARNING: "pccard_parse_tuple" > > [drivers/net/wireless/mac80211/bcm43xx/bcm43xx-mac80211.ko]

Re: 2.6.21-rc2-mm1

2007-03-05 Thread Bill Davidsen
Neil Brown wrote: On Sunday March 4, [EMAIL PROTECTED] wrote: On Mon, 5 Mar 2007 01:11:33 +0100 "J.A. Magallón" <[EMAIL PROTECTED]> wrote: On Fri, 2 Mar 2007 03:00:26 -0800, Andrew Morton <[EMAIL PROTECTED]> wrote: Temporarily at http://userweb.kernel.or

Re: 2.6.21-rc2-mm1: drivers/usb/host/ohci-ssb.c doesn't compile

2007-03-05 Thread Michael Buesch
On Monday 05 March 2007 11:57, Michael Buesch wrote: > > > CC drivers/usb/host/ohci-hcd.o > > > In file included from > > > /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-hcd.c:931: > > > /home/bunk/linux/kernel-2.6/linux-2.6.21

Re: 2.6.21-rc2-mm1: drivers/usb/host/ohci-ssb.c doesn't compile

2007-03-05 Thread Michael Buesch
git-wireless.patch > > >... > > > git trees > > >... > > > > <-- snip --> > > > > ... > > CC drivers/usb/host/ohci-hcd.o > > In file included from > > /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-hcd.c:

Re: 2.6.21-rc2-mm1: drivers/usb/host/ohci-ssb.c doesn't compile

2007-03-05 Thread Michael Buesch
gt; > ... > CC drivers/usb/host/ohci-hcd.o > In file included from > /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-hcd.c:931: > /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-ssb.c:47: > error: request for member 'hcd_priv_size'

Re: 2.6.21-rc2-mm1: drivers/net/wireless/ compile error

2007-03-05 Thread Michael Buesch
On Monday 05 March 2007 02:47, Adrian Bunk wrote: > On Fri, Mar 02, 2007 at 03:00:26AM -0800, Andrew Morton wrote: > >... > > Changes since 2.6.20-mm2: > >... > > git-wireless.patch > >... > > git trees > >... > > Multiple copies of the same drivers are a problem: > > <-- snip --> > > ... >

Re: 2.6.21-rc2-mm1

2007-03-05 Thread Antonino A. Daplas
On Mon, 2007-03-05 at 02:14 -0800, Andrew Morton wrote: > On Fri, 02 Mar 2007 16:56:42 +0100 Michal Piotrowski <[EMAIL PROTECTED]> > wrote: > > > Hi, > > > > Andrew Morton napisał(a): > > > Temporarily at > > > > > > http://userw

Re: 2.6.21-rc2-mm1

2007-03-05 Thread Andrew Morton
On Fri, 02 Mar 2007 16:56:42 +0100 Michal Piotrowski <[EMAIL PROTECTED]> wrote: > Hi, > > Andrew Morton napisał(a): > > Temporarily at > > > > http://userweb.kernel.org/~akpm/2.6.21-rc2-mm1/ > > > > Possible fix for > > nvidiafb-bring-bac

Re: 2.6.21-rc2-mm1 -- WARNING: "pcmcia_access_configuration_register" [drivers/ssb/ssb.ko] undefined!

2007-03-05 Thread Michael Buesch
On Monday 05 March 2007 05:21, Miles Lane wrote: > WARNING: "pcmcia_access_configuration_register" [drivers/ssb/ssb.ko] > undefined! > WARNING: "pccard_parse_tuple" > [drivers/net/wireless/mac80211/bcm43xx/bcm43xx-mac80211.ko] undefined! > WARNING: "pcmcia_register_driver" >

Re: 2.6.21-rc2-mm1 -- WARNING: pcmcia_access_configuration_register [drivers/ssb/ssb.ko] undefined!

2007-03-05 Thread Michael Buesch
On Monday 05 March 2007 05:21, Miles Lane wrote: WARNING: pcmcia_access_configuration_register [drivers/ssb/ssb.ko] undefined! WARNING: pccard_parse_tuple [drivers/net/wireless/mac80211/bcm43xx/bcm43xx-mac80211.ko] undefined! WARNING: pcmcia_register_driver

Re: 2.6.21-rc2-mm1

2007-03-05 Thread Andrew Morton
On Fri, 02 Mar 2007 16:56:42 +0100 Michal Piotrowski [EMAIL PROTECTED] wrote: Hi, Andrew Morton napisał(a): Temporarily at http://userweb.kernel.org/~akpm/2.6.21-rc2-mm1/ Possible fix for nvidiafb-bring-back-generic-ddc-reading.patch drivers/built-in.o: In function

Re: 2.6.21-rc2-mm1

2007-03-05 Thread Antonino A. Daplas
On Mon, 2007-03-05 at 02:14 -0800, Andrew Morton wrote: On Fri, 02 Mar 2007 16:56:42 +0100 Michal Piotrowski [EMAIL PROTECTED] wrote: Hi, Andrew Morton napisał(a): Temporarily at http://userweb.kernel.org/~akpm/2.6.21-rc2-mm1/ Possible fix for nvidiafb-bring

Re: 2.6.21-rc2-mm1: drivers/net/wireless/ compile error

2007-03-05 Thread Michael Buesch
On Monday 05 March 2007 02:47, Adrian Bunk wrote: On Fri, Mar 02, 2007 at 03:00:26AM -0800, Andrew Morton wrote: ... Changes since 2.6.20-mm2: ... git-wireless.patch ... git trees ... Multiple copies of the same drivers are a problem: -- snip -- ... LD

Re: 2.6.21-rc2-mm1: drivers/usb/host/ohci-ssb.c doesn't compile

2007-03-05 Thread Michael Buesch
/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-hcd.c:931: /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-ssb.c:47: error: request for member 'hcd_priv_size' in something not a structure or union Seems like there was a comma missing. There also seems to be some

Re: 2.6.21-rc2-mm1: drivers/usb/host/ohci-ssb.c doesn't compile

2007-03-05 Thread Michael Buesch
drivers/usb/host/ohci-hcd.o In file included from /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-hcd.c:931: /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-ssb.c:47: error: request for member 'hcd_priv_size' in something not a structure

Re: 2.6.21-rc2-mm1: drivers/usb/host/ohci-ssb.c doesn't compile

2007-03-05 Thread Michael Buesch
On Monday 05 March 2007 11:57, Michael Buesch wrote: CC drivers/usb/host/ohci-hcd.o In file included from /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-hcd.c:931: /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-ssb.c:47: error

Re: 2.6.21-rc2-mm1

2007-03-05 Thread Bill Davidsen
Neil Brown wrote: On Sunday March 4, [EMAIL PROTECTED] wrote: On Mon, 5 Mar 2007 01:11:33 +0100 J.A. Magallón [EMAIL PROTECTED] wrote: On Fri, 2 Mar 2007 03:00:26 -0800, Andrew Morton [EMAIL PROTECTED] wrote: Temporarily at http://userweb.kernel.org/~akpm/2.6.21-rc2-mm1/ Will appear

Re: 2.6.21-rc2-mm1 -- WARNING: pcmcia_access_configuration_register [drivers/ssb/ssb.ko] undefined!

2007-03-05 Thread Randy Dunlap
On Mon, 5 Mar 2007 11:11:29 +0100 Michael Buesch wrote: On Monday 05 March 2007 05:21, Miles Lane wrote: WARNING: pcmcia_access_configuration_register [drivers/ssb/ssb.ko] undefined! WARNING: pccard_parse_tuple [drivers/net/wireless/mac80211/bcm43xx/bcm43xx-mac80211.ko] undefined!

Re: 2.6.21-rc2-mm1

2007-03-05 Thread Zan Lynx
not been able to get my laptop to run 2.6.21-rc2-mm1 for more than 5 minutes. The last kernel I had working was 2.6.20-rc6-mm3. The problems may be multiple. Whenever I load the new bcm43xx drivers and do *anything* with iwconfig, it locks hard. No keyboard LEDs, and sysrq does not work. While I had

Re: 2.6.21-rc2-mm1

2007-03-05 Thread J.A. Magallón
On Fri, 2 Mar 2007 03:00:26 -0800, Andrew Morton [EMAIL PROTECTED] wrote: Temporarily at http://userweb.kernel.org/~akpm/2.6.21-rc2-mm1/ Will appear later at ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.21-rc2/2.6.21-rc2-mm1/ I'm also noticing very bad

Re: 2.6.21-rc2-mm1

2007-03-05 Thread Andrew Morton
On Mon, 5 Mar 2007 23:20:58 +0100 J.A. Magall__n [EMAIL PROTECTED] wrote: On Fri, 2 Mar 2007 03:00:26 -0800, Andrew Morton [EMAIL PROTECTED] wrote: Temporarily at http://userweb.kernel.org/~akpm/2.6.21-rc2-mm1/ Will appear later at ftp://ftp.kernel.org/pub/linux

i2c vs nVidia [Re: 2.6.21-rc2-mm1]

2007-03-05 Thread J.A. Magallón
On Fri, 2 Mar 2007 03:00:26 -0800, Andrew Morton [EMAIL PROTECTED] wrote: Temporarily at http://userweb.kernel.org/~akpm/2.6.21-rc2-mm1/ More things... Yes, this is related to nVidia driver. First of all, I'm not asking for help for a broken closed-source driver. I just want Linux

Re: i2c vs nVidia [Re: 2.6.21-rc2-mm1]

2007-03-05 Thread Andrew Morton
On Tue, 6 Mar 2007 01:16:21 +0100 J.A. Magall__n [EMAIL PROTECTED] wrote: On Fri, 2 Mar 2007 03:00:26 -0800, Andrew Morton [EMAIL PROTECTED] wrote: Temporarily at http://userweb.kernel.org/~akpm/2.6.21-rc2-mm1/ More things... Yes, this is related to nVidia driver. First

Re: i2c vs nVidia [Re: 2.6.21-rc2-mm1]

2007-03-05 Thread Greg KH
On Mon, Mar 05, 2007 at 04:33:20PM -0800, Andrew Morton wrote: On Tue, 6 Mar 2007 01:16:21 +0100 J.A. Magall__n [EMAIL PROTECTED] wrote: On Fri, 2 Mar 2007 03:00:26 -0800, Andrew Morton [EMAIL PROTECTED] wrote: Temporarily at http://userweb.kernel.org/~akpm/2.6.21-rc2-mm1

Re: 2.6.21-rc2-mm1: drivers/usb/host/ohci-ssb.c doesn't compile

2007-03-05 Thread Greg KH
On Mon, Mar 05, 2007 at 12:26:45PM +0100, Michael Buesch wrote: On Monday 05 March 2007 11:57, Michael Buesch wrote: CC drivers/usb/host/ohci-hcd.o In file included from /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-hcd.c:931: /home/bunk/linux

Re: 2.6.21-rc2-mm1: drivers/usb/host/ohci-ssb.c doesn't compile

2007-03-05 Thread Adrian Bunk
-mm1/drivers/usb/host/ohci-hcd.c:931: /home/bunk/linux/kernel-2.6/linux-2.6.21-rc2-mm1/drivers/usb/host/ohci-ssb.c:47: error: request for member 'hcd_priv_size' in something not a structure or union Seems like there was a comma missing. There also seems to be some

Re: 2.6.21-rc2-mm1: drivers/usb/host/ohci-ssb.c doesn't compile

2007-03-05 Thread David Brownell
On Monday 05 March 2007 3:26 am, Michael Buesch wrote: Actually, it seems like I will run into other kinds of nasty problems due to stupid design of the HCD code. The OHCI code #includes the various drivers, which have a module_init each. So if you compile PCI and SSB support, you have

Re: 2.6.21-rc2-mm1: drivers/usb/host/ohci-ssb.c doesn't compile

2007-03-05 Thread Michael Buesch
On Monday 05 March 2007 19:42, David Brownell wrote: On Monday 05 March 2007 3:26 am, Michael Buesch wrote: Actually, it seems like I will run into other kinds of nasty problems due to stupid design of the HCD code. The OHCI code #includes the various drivers, which have a module_init

  1   2   3   >