Jiri -
For what it is worth, and understand that it is hard to prove a
negitive, on slack moments over the weekend I repeatedly booted my
system into single user (console) mode using a kernel with
CONFIG_GROUP_SCHED set to yes.
To date I have NOT been able to recreate the repeating key issue
Jiri -
For what it is worth, and understand that it is hard to prove a
negitive, on slack moments over the weekend I repeatedly booted my
system into single user (console) mode using a kernel with
CONFIG_GROUP_SCHED set to yes.
To date I have NOT been able to recreate the repeating key issue
at 10:37 +0100, Jiri Kosina wrote:
> On Sat, 16 Feb 2008, Chris Holvenstot wrote:
>
> > This is just to confirm that I have been running all day on a kernel
> > built with CONFIG_GROUP_SCHED turned 'off' and have not seen the problem
> > with my keyboard (I never noticed
at 10:37 +0100, Jiri Kosina wrote:
On Sat, 16 Feb 2008, Chris Holvenstot wrote:
This is just to confirm that I have been running all day on a kernel
built with CONFIG_GROUP_SCHED turned 'off' and have not seen the problem
with my keyboard (I never noticed a problem with the mouse
:
> [ Peter and Ingo added to CC, as this is apparently another instance of
> CONFIG_GROUP_SCHED causing mouse/keyboard misbehavior ]
>
> Thanks for testing, Chris.
>
> On Sat, 16 Feb 2008, Chris Holvenstot wrote:
>
> > Jiri -
> >
> >
> > Sorry for the
in a while
Chris
On Sat, 2008-02-16 at 12:03 +0100, Jiri Kosina wrote:
> On Fri, 15 Feb 2008, Chris Holvenstot wrote:
>
> > A number of corrispondents on this list offered troubleshooting
> > suggestions, most of which centered arund the high performance timer.
> > If you
in a while
Chris
On Sat, 2008-02-16 at 12:03 +0100, Jiri Kosina wrote:
On Fri, 15 Feb 2008, Chris Holvenstot wrote:
A number of corrispondents on this list offered troubleshooting
suggestions, most of which centered arund the high performance timer.
If you too feel that the issue you
:
[ Peter and Ingo added to CC, as this is apparently another instance of
CONFIG_GROUP_SCHED causing mouse/keyboard misbehavior ]
Thanks for testing, Chris.
On Sat, 16 Feb 2008, Chris Holvenstot wrote:
Jiri -
Sorry for the delay in getting this information back to you. I am now up
Frans & Pavel;
I too saw the random key repeats you are seeing with 2.6.25-rc1 -
however, I saw it (or something very much like the problem you are
reporting - I am not smart enough to determine if the root cause is the
same) with 2.6.25-git15
A number of corrispondents on this list offered
Per chance is 2.6.25-rc2 missing in action? I see the announcement from
about 3 and a half hours ago, but the latest patch that I see is
rc1-git4.
I even took the unheard of action of hitting refresh on my browser.
No joy
--
To unsubscribe from this list: send the line "unsubscribe
Per chance is 2.6.25-rc2 missing in action? I see the announcement from
about 3 and a half hours ago, but the latest patch that I see is
rc1-git4.
I even took the unheard of action of hitting refresh on my browser.
No joy
--
To unsubscribe from this list: send the line unsubscribe
Frans Pavel;
I too saw the random key repeats you are seeing with 2.6.25-rc1 -
however, I saw it (or something very much like the problem you are
reporting - I am not smart enough to determine if the root cause is the
same) with 2.6.25-git15
A number of corrispondents on this list offered
Thomas -
Attached is the output I believe you requested (standard boot - ommiting
the NOHPET directive)
Unless you want to try something else i will run in this configuration
today to try and verify that the problem is still with us.
Thanks for th good wishes - it is going to be a while - I
Thomas -
Attached is the output I believe you requested (standard boot - ommiting
the NOHPET directive)
Unless you want to try something else i will run in this configuration
today to try and verify that the problem is still with us.
Thanks for th good wishes - it is going to be a while - I
Thomas -
I believe that the following is the output you are looking for - sorry
for the delay - between doctors and grandkids I was ready for a few pain
pills and a long nap.
I suspect you often feel the same way after dealing with some who post
here.
Thank you for your support
Chris
[
am willing to do whatever I can to help isolate and or resolve this
issue, but to do so I need one of you experts to firmly grab hold of
some portion of my anatomy and guide me in the right direction.
Chris
On Thu, 2008-02-07 at 17:13 +0100, Thomas Gleixner wrote:
> On Thu, 7 Feb 2008, Ch
.
Please let me know if there are any other items you would like to do or
options you would like me to try.
Chris
On Thu, 2008-02-07 at 10:18 +0100, Jiri Kosina wrote:
> On Wed, 6 Feb 2008, Chris Holvenstot wrote:
>
> > I have several hours of running aith nohpet and X's affin
an willing to give it a shot.
Chris
On Thu, 2008-02-07 at 10:18 +0100, Jiri Kosina wrote:
> On Wed, 6 Feb 2008, Chris Holvenstot wrote:
>
> > I have several hours of running aith nohpet and X's affinity set to 2
> > instead of 3 and so far everything is running flawlessly.
&g
to give it a shot.
Chris
On Thu, 2008-02-07 at 10:18 +0100, Jiri Kosina wrote:
On Wed, 6 Feb 2008, Chris Holvenstot wrote:
I have several hours of running aith nohpet and X's affinity set to 2
instead of 3 and so far everything is running flawlessly.
Great, so this definitely is some kind
Thomas -
I believe that the following is the output you are looking for - sorry
for the delay - between doctors and grandkids I was ready for a few pain
pills and a long nap.
I suspect you often feel the same way after dealing with some who post
here.
Thank you for your support
Chris
[
thank you for your prompt (and effective) support on this
issue.
Chris
On Wed, 2008-02-06 at 14:54 +0100, Jiri Kosina wrote:
> On Wed, 6 Feb 2008, Chris Holvenstot wrote:
>
> > On this system I am using a PS2 Keyboard - and let me stress that it is
> > only occasionaly that i
should be able to out type a system
like this.
Chris
On Wed, 2008-02-06 at 14:28 +0100, Jiri Kosina wrote:
> On Wed, 6 Feb 2008, Chris Holvenstot wrote:
>
> > I built 2.6.24-git15 this morning and seem to have picked up a little
> > "funny" along the way - occasion
I built 2.6.24-git15 this morning and seem to have picked up a little
“funny” along the way – occasionally what should be a single key stroke
ends up spraying multiple characters on to my screen.
By this I mean I type “w” and get “w” or whatever.
This has happened a number of times
I built 2.6.24-git15 this morning and seem to have picked up a little
“funny” along the way – occasionally what should be a single key stroke
ends up spraying multiple characters on to my screen.
By this I mean I type “w” and get “w” or whatever.
This has happened a number of times
should be able to out type a system
like this.
Chris
On Wed, 2008-02-06 at 14:28 +0100, Jiri Kosina wrote:
On Wed, 6 Feb 2008, Chris Holvenstot wrote:
I built 2.6.24-git15 this morning and seem to have picked up a little
funny along the way - occasionally what should be a single key stroke
thank you for your prompt (and effective) support on this
issue.
Chris
On Wed, 2008-02-06 at 14:54 +0100, Jiri Kosina wrote:
On Wed, 6 Feb 2008, Chris Holvenstot wrote:
On this system I am using a PS2 Keyboard - and let me stress that it is
only occasionaly that it happens - I have had
For what it is worth - noted that 2.6.24-git8 now available - same error
as git7.
On Wed, 2008-01-30 at 19:36 +0100, Sam Ravnborg wrote:
> On Wed, Jan 30, 2008 at 11:57:31AM -0600, Chris Holvenstot wrote:
> > Please note that this does not appear to be just a issue with the
> >
Please note that this does not appear to be just a issue with the
powerpc build - I get the following failure whiole building a generic
x86 2.6.24-git7 kernel.
drivers/net/sis190.c:329: error: sis190_pci_tbl causes a section type
conflict
I suspect that you are ahead of me and alrealy knew this
Please note that this does not appear to be just a issue with the
powerpc build - I get the following failure whiole building a generic
x86 2.6.24-git7 kernel.
drivers/net/sis190.c:329: error: sis190_pci_tbl causes a section type
conflict
I suspect that you are ahead of me and alrealy knew this
For what it is worth - noted that 2.6.24-git8 now available - same error
as git7.
On Wed, 2008-01-30 at 19:36 +0100, Sam Ravnborg wrote:
On Wed, Jan 30, 2008 at 11:57:31AM -0600, Chris Holvenstot wrote:
Please note that this does not appear to be just a issue with the
powerpc build - I
cycles: out 1296, in 1243
cycles: out 1312, in 1245
cycles: out 1289, in 1239
cycles: out 1309, in 1245
cycles: out 1308, in 1244
cycles: out 1325, in 1239
cycles: out 1310, in 1245
cycles: out 1289, in 1239
cycles: out 1301, in 1252
cycles: out 1325, in 1249
cycles: out 1307, in 1249
cycles: out
cycles: out 1296, in 1243
cycles: out 1312, in 1245
cycles: out 1289, in 1239
cycles: out 1309, in 1245
cycles: out 1308, in 1244
cycles: out 1325, in 1239
cycles: out 1310, in 1245
cycles: out 1289, in 1239
cycles: out 1301, in 1252
cycles: out 1325, in 1249
cycles: out 1307, in 1249
cycles: out
On Mon, 2007-12-03 at 18:02 +0100, Rene Herman wrote:
> On 30-11-07 23:22, Rene Herman wrote:
>
> > On 30-11-07 14:14, Chris Holvenstot wrote:
> >
> >> For what it is worth I too have seen this problem this morning and it
> >> DOES appear to be ne
On Mon, 2007-12-03 at 18:02 +0100, Rene Herman wrote:
On 30-11-07 23:22, Rene Herman wrote:
On 30-11-07 14:14, Chris Holvenstot wrote:
For what it is worth I too have seen this problem this morning and it
DOES appear to be new (in contrast to a previous comment)
The message
For what it is worth I too have seen this problem this morning and it
DOES appear to be new (in contrast to a previous comment)
The message: pnpacpi: exceeded the max number of mem resources: 12
is displayed each time the system is booted with the 2.6.24-rc3-git5
kernel but is NOT displayed
For what it is worth I too have seen this problem this morning and it
DOES appear to be new (in contrast to a previous comment)
The message: pnpacpi: exceeded the max number of mem resources: 12
is displayed each time the system is booted with the 2.6.24-rc3-git5
kernel but is NOT displayed
ers (who will likely tell that they don't support those who build
and test development kernels)
Once again thanks
On Thu, 2007-11-01 at 18:51 +0100, Adrian Bunk wrote:
> On Thu, Nov 01, 2007 at 12:39:06PM -0500, Chris Holvenstot wrote:
> > Adrian Bunk <[EMAIL PROTECTED]>Adrian Bu
Although it may not be popular with the crowd here, I do have a valid
reason to run Windows - and I accomidate this using the VirtualBox
product.
Since I try to be slightly useful and build as many of the "test" kernel
images I can I end up rebuilding the VirtualBox kernel driver (open
source)
Although it may not be popular with the crowd here, I do have a valid
reason to run Windows - and I accomidate this using the VirtualBox
product.
Since I try to be slightly useful and build as many of the test kernel
images I can I end up rebuilding the VirtualBox kernel driver (open
source)
that they don't support those who build
and test development kernels)
Once again thanks
On Thu, 2007-11-01 at 18:51 +0100, Adrian Bunk wrote:
On Thu, Nov 01, 2007 at 12:39:06PM -0500, Chris Holvenstot wrote:
Adrian Bunk [EMAIL PROTECTED]Adrian Bunk [EMAIL PROTECTED]
Although it may
t;real data" back on them but I will
button up the case, bring the system back up, and come up withsome way
to flow "test data" between these two devices looking for another
failure.
Once again thanks for your time.
Chris
On Sat, 2007-10-27 at 13:47 +0100, Alan Cox wrote:
>
back up, and come up withsome way
to flow test data between these two devices looking for another
failure.
Once again thanks for your time.
Chris
On Sat, 2007-10-27 at 13:47 +0100, Alan Cox wrote:
On Fri, 26 Oct 2007 21:21:52 -0500
Chris Holvenstot [EMAIL PROTECTED] wrote:
My SATA
On Fri, 2007-10-19 at 12:28 -0400, Jeff Garzik wrote:
> Chris Holvenstot wrote:
> > I built 2.6.23-git14 this morning - when booted I can not access the
> > network via my Ethernet connection. Fallback to 2.6.23-git11 works OK.
> > One interesting message during boot:
I built 2.6.23-git14 this morning - when booted I can not access the
network via my Ethernet connection. Fallback to 2.6.23-git11 works OK.
One interesting message during boot:
sysctl table check failed: /net/token-ring .3.14 procname does not match
binary path procname
Complete dmesg output
I built 2.6.23-git14 this morning - when booted I can not access the
network via my Ethernet connection. Fallback to 2.6.23-git11 works OK.
One interesting message during boot:
sysctl table check failed: /net/token-ring .3.14 procname does not match
binary path procname
Complete dmesg output
On Fri, 2007-10-19 at 12:28 -0400, Jeff Garzik wrote:
Chris Holvenstot wrote:
I built 2.6.23-git14 this morning - when booted I can not access the
network via my Ethernet connection. Fallback to 2.6.23-git11 works OK.
One interesting message during boot:
[ 37.325760] forcedeth
Thank you, that worked great.
Chris
On Wed, 2007-10-17 at 05:06 +0200, Gabriel C wrote:
> Chris Holvenstot wrote:
> > Greetings -
>
> Hi,
>
> >
> > This is likely something I am doing wrong (or stupid) but I have run
> > through the build process a
Thank you, that worked great.
Chris
On Wed, 2007-10-17 at 05:06 +0200, Gabriel C wrote:
Chris Holvenstot wrote:
Greetings -
Hi,
This is likely something I am doing wrong (or stupid) but I have run
through the build process a couple of times with the same result.
When
I forgot to mention it in my initial post - although I am running an
AMD64 CPU - I am using the 32 bit version of the system
On Sun, 2007-09-30 at 08:41 -0500, Chris Holvenstot wrote:
> Good Morning -
>
> This morning I built the 2.6.23-rc8-git4 version of the kernel. After
>
Good Morning -
This morning I built the 2.6.23-rc8-git4 version of the kernel. After
rebooting I was unable to keep my mail client (evolution) up and running
for more than a few minutes at a time.
A look in the log shows the following message when evolution aborts:
kernel: [ 1716.971128]
Good Morning -
This morning I built the 2.6.23-rc8-git4 version of the kernel. After
rebooting I was unable to keep my mail client (evolution) up and running
for more than a few minutes at a time.
A look in the log shows the following message when evolution aborts:
kernel: [ 1716.971128]
I forgot to mention it in my initial post - although I am running an
AMD64 CPU - I am using the 32 bit version of the system
On Sun, 2007-09-30 at 08:41 -0500, Chris Holvenstot wrote:
Good Morning -
This morning I built the 2.6.23-rc8-git4 version of the kernel. After
rebooting I
On Mon, 2007-09-24 at 16:39 +0100, Mel Gorman wrote:
> On (19/09/07 17:57), Chris Holvenstot didst pronounce:
> > Still being a little new at this I am not sure if this is an issue at
> > all or not but I noted that while building the 2.6.23-rc6-git8 kernel
> > this
On Mon, 2007-09-24 at 16:39 +0100, Mel Gorman wrote:
On (19/09/07 17:57), Chris Holvenstot didst pronounce:
Still being a little new at this I am not sure if this is an issue at
all or not but I noted that while building the 2.6.23-rc6-git8 kernel
this afternoon I received the following
Still being a little new at this I am not sure if this is an issue at
all or not but I noted that while building the 2.6.23-rc6-git8 kernel
this afternoon I received the following error message:
Building modules, stage 2.
MODPOST 1670 modules
WARNING: Can't handle masks in
Still being a little new at this I am not sure if this is an issue at
all or not but I noted that while building the 2.6.23-rc6-git8 kernel
this afternoon I received the following error message:
Building modules, stage 2.
MODPOST 1670 modules
WARNING: Can't handle masks in
This morning I reported an issue which cause a failure of the
2.6.23-rc2-git4 kernel to boot on my system. The contents of my post
may be viewed here:
http://www.ussg.iu.edu/hypermail/linux/kernel/0708.1/1959.html
After 3 separate builds from "virgin sources" I still had the boot
failure with
Last night I built the 2.6.23-rc2-git4 kernel but could not get it to
boot. I rebuilt it this morning from scratch on the chance that I made
a finger-check the first time through and screwed the pooch.
After the second attempt to build this i still could not boot the
system. I received the
Last night I built the 2.6.23-rc2-git4 kernel but could not get it to
boot. I rebuilt it this morning from scratch on the chance that I made
a finger-check the first time through and screwed the pooch.
After the second attempt to build this i still could not boot the
system. I received the
This morning I reported an issue which cause a failure of the
2.6.23-rc2-git4 kernel to boot on my system. The contents of my post
may be viewed here:
http://www.ussg.iu.edu/hypermail/linux/kernel/0708.1/1959.html
After 3 separate builds from virgin sources I still had the boot
failure with the
On Thu, 2007-08-09 at 14:31 +0200, Benoit Boissinot wrote:
> On 8/9/07, Chris Holvenstot <[EMAIL PROTECTED]> wrote:
> > > Chris Snook wrote:
> > >
> > >The problem here is that your clock is wrong either at mount (boot)
> > >time or unmount (shutdown) t
> Chris Snook wrote:
>
>The problem here is that your clock is wrong either at mount (boot)
>time or unmount (shutdown) time. There's nothing wrong with ext3,
>except that it happens to be noticing this condition.
Chris -
I appreciate the response but on the face of it I do not know if I
Chris Snook wrote:
The problem here is that your clock is wrong either at mount (boot)
time or unmount (shutdown) time. There's nothing wrong with ext3,
except that it happens to be noticing this condition.
Chris -
I appreciate the response but on the face of it I do not know if I
believe
:31 +0200, Benoit Boissinot wrote:
On 8/9/07, Chris Holvenstot [EMAIL PROTECTED] wrote:
Chris Snook wrote:
The problem here is that your clock is wrong either at mount (boot)
time or unmount (shutdown) time. There's nothing wrong with ext3,
except that it happens to be noticing
I think that I may have spotted a minor bug in the 2.6.23 kernel and its
relationship with the EXT3 file system. I apologize in advance if I am
mistaken, reporting a problem that is already known (I did not spot it
in Bugzilla) or if I am reporting it to the wrong forum. I made the
decision a
I think that I may have spotted a minor bug in the 2.6.23 kernel and its
relationship with the EXT3 file system. I apologize in advance if I am
mistaken, reporting a problem that is already known (I did not spot it
in Bugzilla) or if I am reporting it to the wrong forum. I made the
decision a
I am having a problem, likely caused by the vacuum between my ears, but
I thought that a few of you would find it recreational to tear up an
inexperienced user for doing dumb things.
I have what is quickly becoming a "un-ubuntu" 7.04 system - as time goes
on I seem to be replacing the standard
I am having a problem, likely caused by the vacuum between my ears, but
I thought that a few of you would find it recreational to tear up an
inexperienced user for doing dumb things.
I have what is quickly becoming a un-ubuntu 7.04 system - as time goes
on I seem to be replacing the standard
68 matches
Mail list logo
