On Tue, 2007-05-01 at 11:41 +0200, Gregoire Favre wrote:
> Hello again,
>
> just forgot this :
>
> ksymoops 2.4.11 on x86_64 2.6.21. Options used
> -V (default)
> -k /proc/ksyms (default)
> -l /proc/modules (default)
> -o /lib/modules/2.6.21/ (default)
> -m
On Tue, 2007-05-01 at 11:41 +0200, Gregoire Favre wrote:
Hello again,
just forgot this :
ksymoops 2.4.11 on x86_64 2.6.21. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.6.21/ (default)
-m
On Mon, 2007-04-30 at 18:52 +0200, Gregoire Favre wrote:
> On Sat, Apr 28, 2007 at 09:14:37PM +0100, Jon Burgess wrote:
>
> > While the above patch works, it seems the underlying causes is that
> > vmalloc_32() is providing memory above 4Gb on x86-64 which is not what
>
On Mon, 2007-04-30 at 18:52 +0200, Gregoire Favre wrote:
On Sat, Apr 28, 2007 at 09:14:37PM +0100, Jon Burgess wrote:
While the above patch works, it seems the underlying causes is that
vmalloc_32() is providing memory above 4Gb on x86-64 which is not what
the driver expects. This same
On Sat, 2007-04-28 at 18:17 +0100, Jon Burgess wrote:
> On Fri, 2007-04-27 at 18:06 -0400, Lee Revell wrote:
> > On 4/27/07, Jon Burgess <[EMAIL PROTECTED]> wrote:
> > > Interesting - I see similar symptoms after upgrading my PC:
> > > * old PC was AMD Athlo
On Fri, 2007-04-27 at 18:06 -0400, Lee Revell wrote:
> On 4/27/07, Jon Burgess <[EMAIL PROTECTED]> wrote:
> > Interesting - I see similar symptoms after upgrading my PC:
> > * old PC was AMD Athlon 64 3000 w/ 2GB of RAM which had no issues
> > * new PC is a Intel Core 2
On Fri, 2007-04-27 at 18:06 -0400, Lee Revell wrote:
On 4/27/07, Jon Burgess [EMAIL PROTECTED] wrote:
Interesting - I see similar symptoms after upgrading my PC:
* old PC was AMD Athlon 64 3000 w/ 2GB of RAM which had no issues
* new PC is a Intel Core 2 Duo w/ 4GB of RAM and fails
On Sat, 2007-04-28 at 18:17 +0100, Jon Burgess wrote:
On Fri, 2007-04-27 at 18:06 -0400, Lee Revell wrote:
On 4/27/07, Jon Burgess [EMAIL PROTECTED] wrote:
Interesting - I see similar symptoms after upgrading my PC:
* old PC was AMD Athlon 64 3000 w/ 2GB of RAM which had no issues
On Fri, 2007-04-27 at 18:06 -0400, Lee Revell wrote:
> On 4/27/07, Jon Burgess <[EMAIL PROTECTED]> wrote:
> > Interesting - I see similar symptoms after upgrading my PC:
> > * old PC was AMD Athlon 64 3000 w/ 2GB of RAM which had no issues
> > * new PC is a Intel Core 2
On Fri, 2007-04-27 at 22:46 +0200, Markus Rechberger wrote:
> just for the completeness, what does dmesg show up?
> You forgot to mention what device you have too...
>
> Markus
>
> On 4/27/07, Gregoire Favre <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > I have a computer (mother Asus Commando)
On Fri, 2007-04-27 at 22:46 +0200, Markus Rechberger wrote:
just for the completeness, what does dmesg show up?
You forgot to mention what device you have too...
Markus
On 4/27/07, Gregoire Favre [EMAIL PROTECTED] wrote:
Hello,
I have a computer (mother Asus Commando) with 4x1Gb Ram.
On Fri, 2007-04-27 at 18:06 -0400, Lee Revell wrote:
On 4/27/07, Jon Burgess [EMAIL PROTECTED] wrote:
Interesting - I see similar symptoms after upgrading my PC:
* old PC was AMD Athlon 64 3000 w/ 2GB of RAM which had no issues
* new PC is a Intel Core 2 Duo w/ 4GB of RAM and fails
I have never tried it myself but it looks like it might do what you want:
http://oss.sgi.com/projects/fam/
fam and imon FAQ
===
What is fam?
fam, the File Alteration Monitor, provides an API which applications can use to
be notified when specific files or directories are
I have never tried it myself but it looks like it might do what you want:
http://oss.sgi.com/projects/fam/
fam and imon FAQ
===
What is fam?
fam, the File Alteration Monitor, provides an API which applications can use to
be notified when specific files or directories are
>> Before 2.2.18. Now I've tested with both
>> 2.4.1-pre12 and 2.4.1. 2.4 kernel klogd is
>> always using 99% cpu. What gives?
>>
> Can you try 2.4.0? Are you using the 3c59x ethernet driver? I've got the
> same problem on one of my machines, (see message with subject "2.4.1-pre10
> ->
What is the output of 'lspci -v'? If it says that the chip revision is '78' then
this is one of the new 3C905CX (note the CX) NIC's or ASIC on the motherboard.
I've seen a problem with the 3c59x.c driver and this chip, it can send packets
but not receive any. The 3Com 3c90x-1.0.0i.tgz driver at
What is the output of 'lspci -v'? If it says that the chip revision is '78' then
this is one of the new 3C905CX (note the CX) NIC's or ASIC on the motherboard.
I've seen a problem with the 3c59x.c driver and this chip, it can send packets
but not receive any. The 3Com 3c90x-1.0.0i.tgz driver at
Yes it could be a modem on the line, so my comment about DCD is wrong, a comms
program must be able to send AT commands to the modem when DCD is not asserted
before the call is setup. I was being confused by the login getty which we run
on the same serial port. This drops back to the login
tput is dumped to /dev/null if DCD is not asserted no
matter what the flow control says. Perhaps there are some hardware differences
in the configuration of the control signal pull-up/downs.
Jon Burgess
PLANET PROJECT will connect millions of people worldwide through the combined
technology
hat the flow control says. Perhaps there are some hardware differences
in the configuration of the control signal pull-up/downs.
Jon Burgess
PLANET PROJECT will connect millions of people worldwide through the combined
technology of 3Com and the Internet. Find out more and
>The last message I see is "Calibrating delay loop"
>(I see this thaks to the Jtag debugger for Elan520 because
>I haven't configured the VGA board yet).
I've seen this on a board with a BIOS problem. I think it is caused because the
Kernel is in a loop waiting for a timer interrupt to
The last message I see is "Calibrating delay loop"
(I see this thaks to the Jtag debugger for Elan520 because
I haven't configured the VGA board yet).
I've seen this on a board with a BIOS problem. I think it is caused because the
Kernel is in a loop waiting for a timer interrupt to occur.
When using Linux-2.2.17 + ide.2.2.17.all.2904.patch on a board with the
CS5530, doing the following generates a kernel NULL dereference:
pb-3com# cat /proc/ide/cs5530
Unable to handle kernel NULL pointer dereference at virtual address 003c
...
This is caused because the 'bmide_dev' in
When using Linux-2.2.17 + ide.2.2.17.all.2904.patch on a board with the
CS5530, doing the following generates a kernel NULL dereference:
pb-3com# cat /proc/ide/cs5530
Unable to handle kernel NULL pointer dereference at virtual address 003c
...
This is caused because the 'bmide_dev' in
> When trying to compile SimGear-0.0.12 under 2.2.16, with gcc-2.95.2,
> I could (quite reproducibly) cause an unbounded number of:
>
> VM: do_try_to_free_pages failed for x
>
>where x was cc1plus, kswapd, syslogd, etc.
>
>Under 2.2.17pre20, this still start to happen, but shortly thereafter
When trying to compile SimGear-0.0.12 under 2.2.16, with gcc-2.95.2,
I could (quite reproducibly) cause an unbounded number of:
VM: do_try_to_free_pages failed for x
where x was cc1plus, kswapd, syslogd, etc.
Under 2.2.17pre20, this still start to happen, but shortly thereafter
the
26 matches
Mail list logo