ocess 5450
(XF86_SVGA.ati1
2).
...
This is a stock kerne 2.4.4 .
ishikawa@duron$ uname -a
Linux duron 2.4.4 #20 Tue May 1 13:45:38 JST 2001 i686 unknown
ishikawa@duron$
My question again: Can OOM process killer be taught NOT to kill X11
server
(and kill its client first) ?
Well, having X11 run c
ocess 5450
(XF86_SVGA.ati1
2).
...
This is a stock kerne 2.4.4 .
ishikawa@duron$ uname -a
Linux duron 2.4.4 #20 Tue May 1 13:45:38 JST 2001 i686 unknown
ishikawa@duron$
My question again: Can OOM process killer be taught NOT to kill X11
server
(and kill its client first) ?
Well, having X11 run c
>On Sun, May 06, 2001 at 01:51:59PM +0100, Alan Cox wrote:
>
>> > There really needs to be a hardware fix... this doesn't stop some
>> > application having it's owne optimised code from breaking on some
>> > hardware (think games and similation software perhaps).
>>
>> prefetch is virtually
On Sun, May 06, 2001 at 01:51:59PM +0100, Alan Cox wrote:
There really needs to be a hardware fix... this doesn't stop some
application having it's owne optimised code from breaking on some
hardware (think games and similation software perhaps).
prefetch is virtually addresses. An
For comparison purposes,
I use stock kernel 2.4.4.
Use scsi tape support as module.
Tape drive is HP c1539 (aka 1533a) dds-2.
This drive is on the scsi chain of Tekram dc390, tmscsim driver
(used as module).
Hardware compression is enabled.
Under this setup,
tar cvbf 20 /dev/st0
For comparison purposes,
I use stock kernel 2.4.4.
Use scsi tape support as module.
Tape drive is HP c1539 (aka 1533a) dds-2.
This drive is on the scsi chain of Tekram dc390, tmscsim driver
(used as module).
Hardware compression is enabled.
Under this setup,
tar cvbf 20 /dev/st0
J. A. Magallon wrote:
>I'm not so sure it's only a 'rule of thumb'. Do not know the state of
>paging in just released 2.4.4, but in previuos kernel, a page that was
>paged-out, reserves its place in swap even if it is paged-in again, so
>once you have paged-out all your ram at least once, you
J. A. Magallon wrote:
I'm not so sure it's only a 'rule of thumb'. Do not know the state of
paging in just released 2.4.4, but in previuos kernel, a page that was
paged-out, reserves its place in swap even if it is paged-in again, so
once you have paged-out all your ram at least once, you can't
AMD Duron 750Mhz. 256MB memory, 80MB swap.
ishikawa@duron$ !ksy
ksymoops < oops-2001-04-24-b.txt
ksymoops 2.3.7 on i686 2.4.4-pre4. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.4-pre4/ (default)
-m /boot/System.map-2.
AMD Duron 750Mhz. 256MB memory, 80MB swap.
ishikawa@duron$ !ksy
ksymoops oops-2001-04-24-b.txt
ksymoops 2.3.7 on i686 2.4.4-pre4. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.4-pre4/ (default)
-m /boot/System.map-2.4.4
ve
core was created. (I only began tracing after the
web page was loaded and searching of a string is performed once.)
I used "strace -o X.trace.out -p pid-of-X-server".
ishikawa@duron$ grep map X.trace.out
08:33:49 old_mmap(NULL, 163840, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP
ted. (I only began tracing after the
web page was loaded and searching of a string is performed once.)
I used "strace -o X.trace.out -p pid-of-X-server".
ishikawa@duron$ grep map X.trace.out
08:33:49 old_mmap(NULL, 163840, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOU
Hi,
On my athlong K7 optimized kernel prints "unknown" fir oricessir type.
(I have not realized what this "unknown" stood for until today.)
#uname -p
unknown
#uname -a
Linux duron 2.4.3 #2 Fri Apr 6 04:38:35 JST 2001 i686 unknown
It would be nice to have the processor name printed.
Is this
On 10 Apr 2001, Richard Russon wrote:
> VM: Undead swap entry 000bb300
> VM: Undead swap entry 00abb300
> VM: Undead swap entry 016fb300
I have seen similar mysterious crashes of X server
when I began accessing large web page using Netscape
navigator. It was reproducible the first few times I
On 10 Apr 2001, Richard Russon wrote:
VM: Undead swap entry 000bb300
VM: Undead swap entry 00abb300
VM: Undead swap entry 016fb300
I have seen similar mysterious crashes of X server
when I began accessing large web page using Netscape
navigator. It was reproducible the first few times I
Hi,
On my athlong K7 optimized kernel prints "unknown" fir oricessir type.
(I have not realized what this "unknown" stood for until today.)
#uname -p
unknown
#uname -a
Linux duron 2.4.3 #2 Fri Apr 6 04:38:35 JST 2001 i686 unknown
It would be nice to have the processor name printed.
Is this
.)
Kurt Garloff wrote:
> On Thu, Mar 22, 2001 at 02:24:56AM +0900, Chiaki Ishikawa wrote:
> > --- begin quote ---
> > > enclosed are 163 potential bugs in 2.4.1 where blocking functions are
> > > called with either interrupts disabled or a spin lock held. The
> > &
Hi,
I suppose that many SCSI maintainers do read the linux-kernel
mailing list. However, just in case, I am quoting one of the
very interesting postings that come from people at Stanford.
They seem to be doing mechanical verification / checking of
linux source code to hunt for potentical bugs. In
Hi,
I suppose that many SCSI maintainers do read the linux-kernel
mailing list. However, just in case, I am quoting one of the
very interesting postings that come from people at Stanford.
They seem to be doing mechanical verification / checking of
linux source code to hunt for potentical bugs. In
hese devices seem to report all LUN's as available even
if the media is not in the drive.
The driver, tmscsim.o, is compiled as module and is inserted during boot
(using Debian's /etc/module mechanism).
Eg.
Device config.
ishikawa@duron$ cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 0
Hi,
I have an "old" Nakamichi CD changer.
("old" might be important consideration here. )
Should I test the patch submitted and report what I found ?
(Or maybe I don't have to bother at this stage at all
and simply wait for the 2.5 development and debugging cycle?)
-
To unsubscribe from
to report all LUN's as available even
if the media is not in the drive.
The driver, tmscsim.o, is compiled as module and is inserted during boot
(using Debian's /etc/module mechanism).
Eg.
Device config.
ishikawa@duron$ cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 04 Lun: 00
e elapsed time of SCSI case is TWICE as long if
we let the previous output of the test program stay before
running the second test? (I suspect fdatasync
takes time proportional to the (then current) file size, but
still why SCSI case is so long is beyond me.)
Eg.
ishikawa@duron$ ls -l /tmp/t.out
time of SCSI case is TWICE as long if
we let the previous output of the test program stay before
running the second test? (I suspect fdatasync
takes time proportional to the (then current) file size, but
still why SCSI case is so long is beyond me.)
Eg.
ishikawa@duron$ ls -l /tmp/t.out
ls: /tmp
ion
especially about the last two entries.
Why are they loaded at all? I could not figure
out why until today. These are also listed
in /etc/modules, and "auto" is not given.
So kerneld is not started at boot time...
FYO, just to show what the lsmod output looks like after
mounting a CD in nakami
ion
especially about the last two entries.
Why are they loaded at all? I could not figure
out why until today. These are also listed
in /etc/modules, and "auto" is not given.
So kerneld is not started at boot time...
FYO, just to show what the lsmod output looks like after
mounting a CD in nakamichi
Robert Read wrote:
> I have used 128k and larger buffer sizes, and I just noticed this
> fragment in the RedHat Tux Webserver patch. It creates a 2MB buffer:
>
>
I am encouraged to try a large buffer then.
Thank you.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
some problems hitting
memory size limit during loading, etc.)
Has anyone tried 128K buffer size in kernel/printk.c
and still have the kernel boot (without
hard to notice memory corruption problems and other subtle bugs)?
Any hints and tips will be appreciated.
Happy Hacking,
Chiaki Ishikawa
PS:
Robert Read wrote:
I have used 128k and larger buffer sizes, and I just noticed this
fragment in the RedHat Tux Webserver patch. It creates a 2MB buffer:
I am encouraged to try a large buffer then.
Thank you.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
ory size limit during loading, etc.)
Has anyone tried 128K buffer size in kernel/printk.c
and still have the kernel boot (without
hard to notice memory corruption problems and other subtle bugs)?
Any hints and tips will be appreciated.
Happy Hacking,
Chiaki Ishikawa
PS: FYI, I am quoting my in
m other
faster devices.)
BTW, I was pleasantly surprised to see the nicely formatted
dump of registers and such. It seems that kdb is really
useful for the type of analysis at hand!
Happy Hacking,
Chiaki Ishikawa
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
and such. It seems that kdb is really
useful for the type of analysis at hand!
Happy Hacking,
Chiaki Ishikawa
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
he name changes that took place last year.
SCSI device names and others are not quite up to date and
don't agree with what we see on the real system.
(I am assuming that this is generally true and
not Debian-specific.)
Attached is my first cut to update the of the docu
e real system.
(I am assuming that this is generally true and
not Debian-specific.)
Attached is my first cut to update the of the document.
I would appreciate it if the README document is updated
to reflect the current implemntation.
I would be glad to help by typing the first r
ure where to report this.
> (It might as well be the scsi system problem...)
> Help will be appreciated where to send the bug reports, etc..
> (Forwarding will be fine.)
>
> Happy Hacking,
>
> Chiaki
>
> ---
> I use Debian GNU/Linux, kernel 2.4.1.
> ishikawa@duron$ uname
(It might as well be the scsi system problem...)
Help will be appreciated where to send the bug reports, etc..
(Forwarding will be fine.)
Happy Hacking,
Chiaki
---
I use Debian GNU/Linux, kernel 2.4.1.
ishikawa@duron$ uname -a
Linux duron 2.4.1 #18 Fri Feb 9 02:18:50 JST 2001 i686
Peter Samuelson wrote:
> [Ishikawa]
> > I just noticed that running
> >
> > . /usr/src/linux/script/ver_linux
> >
> > prints out strange libc version
> [...]
> > I found that if the command "ls" is aliased to "ls -aF"
Peter Samuelson wrote:
[Ishikawa]
I just noticed that running
. /usr/src/linux/script/ver_linux
prints out strange libc version
[...]
I found that if the command "ls" is aliased to "ls -aF"
So ... don't use '.' to execute scripts. If there is
I just noticed that running
. /usr/src/linux/script/ver_linux
prints out strange libc version when I run it
as a normal user. It prints out expected output if
I run it as superuser.
Output Example: Incorrect and correct examples.
Binutils 2.10.0.26
! Linux C Library
I just noticed that running
. /usr/src/linux/script/ver_linux
prints out strange libc version when I run it
as a normal user. It prints out expected output if
I run it as superuser.
Output Example: Incorrect and correct examples.
Binutils 2.10.0.26
! Linux C Library
"J . A . Magallon" wrote:
>
>
> Average users you are targetting with that automagical
> card detection even do not know there are SCSI and IDE disks. They just
> want a 30Gb ide disk to install linux and play. If they involve with SCSI
> and ID numbers and multiple cards and so on they can read
"J . A . Magallon" wrote:
Average users you are targetting with that automagical
card detection even do not know there are SCSI and IDE disks. They just
want a 30Gb ide disk to install linux and play. If they involve with SCSI
and ID numbers and multiple cards and so on they can read some
I sent out a longish response a few minutes ago which explained
the my problem was solved somehow!
One thing I missed explaining in my original post is
the AMI BIOS on the GA-7IXE4 motherboard
has a very spartan set of options.
For the geometry translation of ATA disk, only
On/Off choice was
Guest section DW wrote:
> On Sat, Dec 23, 2000 at 12:11:41AM +0900, Ishikawa wrote:
>
> > I have to think more deeply then what the best measure would be.
>
> I suppose you can get all systems involved to agree on 255 heads
> if you select LBA in the BIOS.
>
&
Guest section DW wrote:
On Sat, Dec 23, 2000 at 12:11:41AM +0900, Ishikawa wrote:
I have to think more deeply then what the best measure would be.
I suppose you can get all systems involved to agree on 255 heads
if you select LBA in the BIOS.
Andries
Hi,
I think I misunderstood one
I sent out a longish response a few minutes ago which explained
the my problem was solved somehow!
One thing I missed explaining in my original post is
the AMI BIOS on the GA-7IXE4 motherboard
has a very spartan set of options.
For the geometry translation of ATA disk, only
On/Off choice was
Thank you for your tips.
Guest section DW wrote:
> First a few warnings - probably you know already, but just to be sure:
>
>
> (i) The geometry you get is mostly determined by the BIOS settings
> (Normal / Large / LBA / PartitionTable).
>
>
> (ii) The 2.2.14+ and 2.4 behaviours are both
Thank you for your tips.
Guest section DW wrote:
First a few warnings - probably you know already, but just to be sure:
(i) The geometry you get is mostly determined by the BIOS settings
(Normal / Large / LBA / PartitionTable).
(ii) The 2.2.14+ and 2.4 behaviours are both correct,
IDE woes.
Sorry for this lengthy post, I read ide.txt, large-disk-howto.txt and
experimented with fdisk (DOS/WIN), dd, and a few other tricks,
but can't seem to be able to solve a question.
Big Question - 1:
I have a 20GB seagate ATA disk.
My Board BIOS recognizes the CHS geometry when it
IDE woes.
Sorry for this lengthy post, I read ide.txt, large-disk-howto.txt and
experimented with fdisk (DOS/WIN), dd, and a few other tricks,
but can't seem to be able to solve a question.
Big Question - 1:
I have a 20GB seagate ATA disk.
My Board BIOS recognizes the CHS geometry when it
config from some early test-1x series
compilation.)
ishikawa@standard$ diff -C1 -cibw ~/config-saved /usr/src/linux/.config
*** /home/ishikawa/config-saved Fri Nov 24 13:44:30 2000
--- /usr/src/linux/.config Sat Nov 25 09:29:17 2000
***
*** 31,34
# CONFIG_MPENTIUM4 is not set
config from some early test-1x series
compilation.)
ishikawa@standard$ diff -C1 -cibw ~/config-saved /usr/src/linux/.config
*** /home/ishikawa/config-saved Fri Nov 24 13:44:30 2000
--- /usr/src/linux/.config Sat Nov 25 09:29:17 2000
***
*** 31,34
# CONFIG_MPENTIUM4 is not set
rks with test-9 on my PC.)
I would like to thank Kurt for continueing to maintain
the old tmscsim driver for the new kernel.
Happy Hacking,
Chiaki Ishikawa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please
would like to thank Kurt for continueing to maintain
the old tmscsim driver for the new kernel.
Happy Hacking,
Chiaki Ishikawa
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org/lkml/
54 matches
Mail list logo
