I'm using the ide patch "ide.2.2.19.05042001" for 2.2.19. In 2.4.5 this cdr
wsa detected as a cdr. here it's detected as:
Vendor: CREATIVE Model: CD-RW RW8438ERev: FC03
Type: CD-ROM ANSI SCSI revision: 02
Cdrecord says this.
cdrecord: Invalid
I never got dma timeouts running 2.2.19 before installing my promise ata66
card and CDRW. Now i get them whenever disk usage is up and what ends up
happening is none of my drives running in dma mode. Is this some effect of
enabling the UDMA features of the promise card ? If i compiled the
I never got dma timeouts running 2.2.19 before installing my promise ata66
card and CDRW. Now i get them whenever disk usage is up and what ends up
happening is none of my drives running in dma mode. Is this some effect of
enabling the UDMA features of the promise card ? If i compiled the
I'm using the ide patch ide.2.2.19.05042001 for 2.2.19. In 2.4.5 this cdr
wsa detected as a cdr. here it's detected as:
Vendor: CREATIVE Model: CD-RW RW8438ERev: FC03
Type: CD-ROM ANSI SCSI revision: 02
Cdrecord says this.
cdrecord: Invalid argument.
I'm thinking that this is a kernel scsi emu problem rather than a CDR problem
due to the past scsi emulation mails i've seen about previous kernels. I've
been forced to move to 2.4.x because i want to use my promise ata66 ide
controller and the 2.2 promise drivers dont work for it. My CDR
I'm thinking that this is a kernel scsi emu problem rather than a CDR problem
due to the past scsi emulation mails i've seen about previous kernels. I've
been forced to move to 2.4.x because i want to use my promise ata66 ide
controller and the 2.2 promise drivers dont work for it. My CDR
this is just a general question about low latency patches on 2.2, I
remember hearing about low latency patches for 2.4 not playing well with X
4.x, is this true for 2.2 low latency patches as well?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
this is just a general question about low latency patches on 2.2, I
remember hearing about low latency patches for 2.4 not playing well with X
4.x, is this true for 2.2 low latency patches as well?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
Is there something generally wrong with how linux determines total cpu
usage (via procmeter3 and top) when dealing with applications that are
threaded? I routinely get 0% cpu usage when playing mpegs and mp3s and
some avi's even (Divx when using no software enhancement) ... Somehow i
doubt that
As a departure from just about every other post talking about something
wrong. I just want to say 2.2.19pre14 is working perfectly. I can't
say anything about latency because i haven't found much in the area of
timing patches for 2.2.19 yet, it is very responsive and fast and
handles quite well
As a departure from just about every other post talking about something
wrong. I just want to say 2.2.19pre14 is working perfectly. I can't
say anything about latency because i haven't found much in the area of
timing patches for 2.2.19 yet, it is very responsive and fast and
handles quite well
"Michael B. Allen" wrote:
> Hello,
>
> What's the nature of the VIA chipset problems? I want to get a new system
> this weekend but I read on kernel traffic that VIA has problems? I
> wan't to use Hendrick's ide patches on 2.2.18. What board should I
> get? Help, I've searched through usenet and
"Michael B. Allen" wrote:
Hello,
What's the nature of the VIA chipset problems? I want to get a new system
this weekend but I read on kernel traffic that VIA has problems? I
wan't to use Hendrick's ide patches on 2.2.18. What board should I
get? Help, I've searched through usenet and asked
I personally have no way of knowing if it's giving incorrect numbers for
cache and buffers and used and such .. but as for total memory,
something is wrong. lm sensors tells me i have 288MB of ram, the bootup
messages say i have 288MB of memory with 4MB being used by the kernel
and my bios says
I personally have no way of knowing if it's giving incorrect numbers for
cache and buffers and used and such .. but as for total memory,
something is wrong. lm sensors tells me i have 288MB of ram, the bootup
messages say i have 288MB of memory with 4MB being used by the kernel
and my bios says
Vojtech Pavlik wrote:
> On Thu, Feb 01, 2001 at 01:20:00PM -0500, Byron Stanoszek wrote:
>
> > > On Thu, Feb 01, 2001 at 11:46:08AM -0500, Byron Stanoszek wrote:
> > >
> > > > Yeah, by bios does the same thing too on the Abit KT7(a).
> > >
> > > Ok, I'll remember this. This is most likely the
Vojtech Pavlik wrote:
> On Wed, Jan 31, 2001 at 08:52:58PM -0500, safemode wrote:
>
> > My KA7 can go over 160Mhz FSB
> > Yes i know about memory speed limitions ..that's why you are able to choose
> > HW clock - PCI so at those high speeds it's actually say 120
Vojtech Pavlik wrote:
On Thu, Feb 01, 2001 at 01:20:00PM -0500, Byron Stanoszek wrote:
On Thu, Feb 01, 2001 at 11:46:08AM -0500, Byron Stanoszek wrote:
Yeah, by bios does the same thing too on the Abit KT7(a).
Ok, I'll remember this. This is most likely the cause of the
Byron Stanoszek wrote:
> On Wed, 31 Jan 2001, safemode wrote:
>
> > yea i know. . same mode i also had a big problem with DMA timeouts on
> > 2.4 so .. i dont know what's up with 2.4 and my motherboard ...2.2
> > hasn't shown a single irq or DMA er
Tobias Ringstrom wrote:
> On Wed, 31 Jan 2001, safemode wrote:
>
> > I'm wondering... Perhaps it's a problem motherboard specific. I'm
> > using the KA7 and saw pretty bad problems (extreme fs corruption)
> > and bad latency. Perhaps the K7V and the KT7's dont have this
Alan Cox wrote:
> > better than i ever got with 2.4 even when only one drive was on a channel.
> > Right now my k7-2 750 is at 849mhz with a FSB of 114Mhz and PCI at 34Mhz.
>
> Hint: people who overclock machines get suprising odd results and bad stuff
> happens. Please dont waste developers
Mark Hahn wrote:
> >From what I gather this chipset on 2.4.x is only stable if you cripple just about
>everything that makes
> > it worth having (udma, 2nd ide channel etc etc) ?does it even work when all
>that's done now or is
> > it fully functional?
>
> it seems to be fully functional
David Raufeisen wrote:
> On Wednesday, 31 January 2001, at 08:36:42 (+0100),
> Vojtech Pavlik wrote:
>
> > Hi!
> >
> > 1) You don't seem to have any drives on the VIA controller. If this is
> > true, I don't think this can be a VIA IDE driver problem.
> >
>
> Hi, Are you referring to Mark or me?
David Raufeisen wrote:
On Wednesday, 31 January 2001, at 08:36:42 (+0100),
Vojtech Pavlik wrote:
Hi!
1) You don't seem to have any drives on the VIA controller. If this is
true, I don't think this can be a VIA IDE driver problem.
Hi, Are you referring to Mark or me?
I have
Mark Hahn wrote:
From what I gather this chipset on 2.4.x is only stable if you cripple just about
everything that makes
it worth having (udma, 2nd ide channel etc etc) ?does it even work when all
that's done now or is
it fully functional?
it seems to be fully functional for some
Alan Cox wrote:
better than i ever got with 2.4 even when only one drive was on a channel.
Right now my k7-2 750 is at 849mhz with a FSB of 114Mhz and PCI at 34Mhz.
Hint: people who overclock machines get suprising odd results and bad stuff
happens. Please dont waste developers time
Tobias Ringstrom wrote:
On Wed, 31 Jan 2001, safemode wrote:
I'm wondering... Perhaps it's a problem motherboard specific. I'm
using the KA7 and saw pretty bad problems (extreme fs corruption)
and bad latency. Perhaps the K7V and the KT7's dont have this problem.
I dont see any
Byron Stanoszek wrote:
On Wed, 31 Jan 2001, safemode wrote:
yea i know. . same mode i also had a big problem with DMA timeouts on
2.4 so .. i dont know what's up with 2.4 and my motherboard ...2.2
hasn't shown a single irq or DMA error yet since going back to it.
currently
Adrian Cox wrote:
> Dylan Griffiths wrote:
> > The VIA KT133 chipset exhibits the following bugs under Linux 2.2.17 and
> > 2.4.0:
> > 1) PS/2 mouse cursor randomly jumps to upper right hand corner of screen and
> > locks for a bit
>
> This happens to me about once a month on a BX chipset PII
Adrian Cox wrote:
Dylan Griffiths wrote:
The VIA KT133 chipset exhibits the following bugs under Linux 2.2.17 and
2.4.0:
1) PS/2 mouse cursor randomly jumps to upper right hand corner of screen and
locks for a bit
This happens to me about once a month on a BX chipset PII machine here,
Linda Walsh wrote:
> Some oddities w/kapmd(2.4.0)... If I sit in X and do nothing other than run top or
> "vmstat 5", I get down to as low as 60% idle and 40% in system -- with kapmd getting
> 'charged' for the 40%.
>
> Then I go and run 'freeamp' and the CPU usage goes to 100% idle, presumably
Linda Walsh wrote:
Some oddities w/kapmd(2.4.0)... If I sit in X and do nothing other than run top or
"vmstat 5", I get down to as low as 60% idle and 40% in system -- with kapmd getting
'charged' for the 40%.
Then I go and run 'freeamp' and the CPU usage goes to 100% idle, presumably
Peter Horton wrote:
> On Thu, Jan 20, 2000 at 08:38:12AM +, Peter Horton wrote:
> >
> > I think I'm suffering the same thing on my new Asus A7V. Yesterday I got a
> > single "error in bitmap, remounting read only" type error, and today I got
> > some files in /tmp that returned I/O error
Peter Horton wrote:
On Thu, Jan 20, 2000 at 08:38:12AM +, Peter Horton wrote:
I think I'm suffering the same thing on my new Asus A7V. Yesterday I got a
single "error in bitmap, remounting read only" type error, and today I got
some files in /tmp that returned I/O error when
I'm sorry I can't be more descriptive than that, but there aren't any
errors ever displayed. What happened was after about a day of uptime, I
began seeing IO errors when trying to access files. I realized that the
IO errors occurred on any file I had created. I rebooted since the
computer
I'm sorry I can't be more descriptive than that, but there aren't any
errors ever displayed. What happened was after about a day of uptime, I
began seeing IO errors when trying to access files. I realized that the
IO errors occurred on any file I had created. I rebooted since the
computer
to me since i wouldn't be able to recode the client
anyway. I'm sure there are setiathome developers (at least one) paying
attention to this list. The client is broken.
safemode wrote:
It seems that for one reason or another, ip_conntrack
totally locks (not
removeable) after about 10 hours
It seems that for one reason or another, ip_conntrack totally locks (not
removeable) after about 10 hours of continued use. All i found were
these messages in my dmesg output
Jan 6 06:18:10 icebox kernel: reset_xmit_timer sk=c17fd040 1
when=0x5d9e, caller=c01a6bf1
Jan 6 06:18:10 icebox kernel:
It seems that for one reason or another, ip_conntrack totally locks (not
removeable) after about 10 hours of continued use. All i found were
these messages in my dmesg output
Jan 6 06:18:10 icebox kernel: reset_xmit_timer sk=c17fd040 1
when=0x5d9e, caller=c01a6bf1
Jan 6 06:18:10 icebox kernel:
since i wouldn't be able to recode the client
anyway. I'm sure there are setiathome developers (at least one) paying
attention to this list. The client is broken.
safemode wrote:
It seems that for one reason or another, ip_conntrack
totally locks (not
removeable) after about 10 hours of continued
"Grover, Andrew" wrote:
> > From: safemode [mailto:[EMAIL PROTECTED]]
>
> > Well, it seems the only way to look at sensor readings with
> > lmsensors is
> > to activate acpi in linux for my motherboard.
>
> Can you please send me the output from dm
"Grover, Andrew" wrote:
From: safemode [mailto:[EMAIL PROTECTED]]
Well, it seems the only way to look at sensor readings with
lmsensors is
to activate acpi in linux for my motherboard.
Can you please send me the output from dmesg, as well as /proc/interrupts? I
don't thin
Well, it seems the only way to look at sensor readings with lmsensors is
to activate acpi in linux for my motherboard. According to the docs, my
motherboard is supposed to be supported and is detected when linux
boots, the problem comes when i try to move the mouse (in console and
X). It
Well, it seems the only way to look at sensor readings with lmsensors is
to activate acpi in linux for my motherboard. According to the docs, my
motherboard is supposed to be supported and is detected when linux
boots, the problem comes when i try to move the mouse (in console and
X). It
Ruth Ivimey-Cook wrote:
>
> On IDE, you don't. IDE never supports hot-swap, RAID or no. If you want
> that, use SCSI.
That's not necessarily true. There is work in linux to support Tri-stating
the ide devices with the help of a custom card that will allow one to cut
power to a specific ide
Ruth Ivimey-Cook wrote:
On IDE, you don't. IDE never supports hot-swap, RAID or no. If you want
that, use SCSI.
That's not necessarily true. There is work in linux to support Tri-stating
the ide devices with the help of a custom card that will allow one to cut
power to a specific ide
Zdenek Kabelac wrote:
> Problem: When i am using my harddrive and cdrom,
my computer will freeze.
> It freezes in two different ways.. sometimes just the harddrive access
> will freeze (can still do things in X as long as they dont require
the
> harddrive), and then everything freezes within a
Zdenek Kabelac wrote:
> Problem: When i am using my harddrive and cdrom,
my computer will freeze.
> It freezes in two different ways.. sometimes just the harddrive access
> will freeze (can still do things in X as long as they dont require
the
> harddrive), and then everything freezes within a
All I can say right now is that enabling DMA on a 440LX chipset with
2.4.0-test12 or any other kernel I can remember has caused DMA timeout
and ide-reset problems. Disabling dma on the harddrives doesn't help
that much either, I still get ide resets. What I'm looking for right
now is some
All I can say right now is that enabling DMA on a 440LX chipset with
2.4.0-test12 or any other kernel I can remember has caused DMA timeout
and ide-reset problems. Disabling dma on the harddrives doesn't help
that much either, I still get ide resets. What I'm looking for right
now is some
On Wed, 29 Nov 2000 17:36:12 Marc Mutz wrote:
> kernel 2.2.17, '/' being a 1k blocksize ext2fs:
>
> root@adam:/ > dd if=/dev/zero of=holed.file bs=1000 seek=5000 count=1000
> 1000+0 records in
> 1000+0 records out
> root@adam:/ > ls -l holed.file
> -rw-r--r-- 1 root root 600 Nov
On Wed, 29 Nov 2000 17:36:12 Marc Mutz wrote:
kernel 2.2.17, '/' being a 1k blocksize ext2fs:
root@adam:/ dd if=/dev/zero of=holed.file bs=1000 seek=5000 count=1000
1000+0 records in
1000+0 records out
root@adam:/ ls -l holed.file
-rw-r--r-- 1 root root 600 Nov 29 23:33
On Wed, 15 Nov 2000 16:19:23 Guus Sliepen wrote:
> On Wed, Nov 15, 2000 at 03:46:03PM -0500, safemode wrote:
>
> > I was DDoS'd today while away and came home to find the firewall unable
> to
> > do anything network related (although my connection to irc was still
> &g
I was DDoS'd today while away and came home to find the firewall unable to
do anything network related (although my connection to irc was still
working oddly). a quick dmesg showed the problem.
ip_conntrack: maximum limit of 2048 entries exceeded
NET: 1 messages suppressed.
ip_conntrack: maximum
I was DDoS'd today while away and came home to find the firewall unable to
do anything network related (although my connection to irc was still
working oddly). a quick dmesg showed the problem.
ip_conntrack: maximum limit of 2048 entries exceeded
NET: 1 messages suppressed.
ip_conntrack: maximum
On Wed, 15 Nov 2000 16:19:23 Guus Sliepen wrote:
On Wed, Nov 15, 2000 at 03:46:03PM -0500, safemode wrote:
I was DDoS'd today while away and came home to find the firewall unable
to
do anything network related (although my connection to irc was still
working oddly). a quick dmesg
On Fri, 20 Oct 2000 15:34:04 Dmitry Pogosyan wrote:
> safemode wrote:
>
> > That's what i was thinking, but 30MB/s seems to be quite an
> exaggeration.
> > On my
> > Intel Corporation 82371AB PIIX4 IDE (rev 01), ide chipset my master
> (10.2GB
> > maxtor 72
That's what i was thinking, but 30MB/s seems to be quite an exaggeration.
On my
Intel Corporation 82371AB PIIX4 IDE (rev 01), ide chipset my master (10.2GB
maxtor 7200rpm UDMA66) drive i get ~15-16MB/s and on my slave (same
interface, 20.1GB maxtor 7200rpm UDMA66), i get ~13MB/s. This goes
That's what i was thinking, but 30MB/s seems to be quite an exaggeration.
On my
Intel Corporation 82371AB PIIX4 IDE (rev 01), ide chipset my master (10.2GB
maxtor 7200rpm UDMA66) drive i get ~15-16MB/s and on my slave (same
interface, 20.1GB maxtor 7200rpm UDMA66), i get ~13MB/s. This goes
On Fri, 20 Oct 2000 15:34:04 Dmitry Pogosyan wrote:
safemode wrote:
That's what i was thinking, but 30MB/s seems to be quite an
exaggeration.
On my
Intel Corporation 82371AB PIIX4 IDE (rev 01), ide chipset my master
(10.2GB
maxtor 7200rpm UDMA66) drive i get ~15-16MB/s and on my
I think my confusion came from the fact that i didn't need to reference a
specific device before the kernel upgrade. As for telling it to use
/dev/sg1 or sg0 ... I cant really tell anymore, i'm no longer using that
kernel. It probably was an incorrect usage of cdrecord, so i'm sorry for
the
Everything seems to be working great now... i'm using a patch Andre
Hedrick gave me and everything works like normal again. Thanks again for
everyone's help. Back to burning cds.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
Unfortunally i compile in all the scsi stuff and make ide-cd modular, so i
dont know what was compiled in anymore since that kernel tree is gone. I
did however recieve a patch to test10-pre3 which seems to be working, will
test the actual record part in a bit (and this kernel i know for a fact
this is cdrecord -v -debug -scanbus
note that i symlinked pg0 to scd0 since the device didn't exist anyway and
cdrecord insists that is the /dev equivilant to 0,0,0. well
dev: (NULL POINTER) speed: -1 fs: -1
Cdrecord 1.10a04 (i686-pc-linux-gnu) Copyright (C) 1995-2000 Jörg Schilling
TOC Type:
ead of the dev=/dev/ form?
> I'm
> told by the cdrecord maintainer that it's more reliable that way, and
> that
> the /dev/ format should not be used.
>
> What does cdrecord -scanbus show?
>
> Matt
>
> On Sun, Oct 15, 2000 at 01:57:24AM -0400, safemode wrote:
Oops on one thing, /dev/sr0 is merely a symlink to /dev/scd0, sorry it's
pretty late. these are the attributes of /dev/scd0
brw-rw1 root cdrom 11, 0 Sep 10 01:02 /dev/scd0
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Oops on one thing, /dev/sr0 is merely a symlink to /dev/scd0, sorry it's
pretty late. these are the attributes of /dev/scd0
brw-rw1 root cdrom 11, 0 Sep 10 01:02 /dev/scd0
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
=/dev/ form?
I'm
told by the cdrecord maintainer that it's more reliable that way, and
that
the /dev/ format should not be used.
What does cdrecord -scanbus show?
Matt
On Sun, Oct 15, 2000 at 01:57:24AM -0400, safemode wrote:
Alright, first off let me say that this cdrecord
I think my confusion came from the fact that i didn't need to reference a
specific device before the kernel upgrade. As for telling it to use
/dev/sg1 or sg0 ... I cant really tell anymore, i'm no longer using that
kernel. It probably was an incorrect usage of cdrecord, so i'm sorry for
the
Alright, first off let me say that this cdrecord was working fine with
2.4.0-test8. The recorder is on /dev/scd0 and also on /dev/sr0. maybe
this has something to do with it? i'm not sure, but cdrecord keeps saying
the stats for it are -2,-2,-2when it should be 0,0,0. Does anyone
know
ok. first this is what df -i gives me
FilesystemInodes IUsed IFree IUse% Mounted on
/dev/hda41822720 135002 16877188% /
so it's not the inode problem.
this is what tune2fs -l /dev/hda4 | grep ^Reserved gives me
tune2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b,
cvs server: cannot rewrite CVS/Entries.Backup: No space left on device
These are the sort of errors i'm getting from cvs but this is what df -m
tells me on the partition i'm downloading on
/dev/hda4 6865 4899 1610 76% /
I'm not sure how to test this on a diff program
I'm just wondering if I'm the only person who has had problems with
2.4.0-test9 recording on ide-scsi cdr's?
Nobody has posted anything about it and the test10-prex changefiles don't
mention it. cdrecord reports very weird results when scanning the scsi
bus whereas dmesg shows what one would
I'm just wondering if I'm the only person who has had problems with
2.4.0-test9 recording on ide-scsi cdr's?
Nobody has posted anything about it and the test10-prex changefiles don't
mention it. cdrecord reports very weird results when scanning the scsi
bus whereas dmesg shows what one would
The only reason I'm asking this is because nobody has mentioned it and it
seems to have gotten put on the back-burner .. i have heard a lot about
2.2.x ide-scsi fixes but nothing about 2.4.0 ... what's the status of this?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
The only reason I'm asking this is because nobody has mentioned it and it
seems to have gotten put on the back-burner .. i have heard a lot about
2.2.x ide-scsi fixes but nothing about 2.4.0 ... what's the status of this?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
On Sun, 08 Oct 2000 16:37:03 safemode wrote:
> I know this passed by the list before but i missed it. How do you get
> ide
> - scsi cdrecording to work again? or is this a cdrecord incompatibility
> issue now? This worked a couple sub-versions ago in test8. anyone
> k
I know this passed by the list before but i missed it. How do you get ide
- scsi cdrecording to work again? or is this a cdrecord incompatibility
issue now? This worked a couple sub-versions ago in test8. anyone know?
-
To unsubscribe from this list: send the line "unsubscribe
I know this passed by the list before but i missed it. How do you get ide
- scsi cdrecording to work again? or is this a cdrecord incompatibility
issue now? This worked a couple sub-versions ago in test8. anyone know?
-
To unsubscribe from this list: send the line "unsubscribe
Keith Packard wrote:
> > Odd, Isn't 777 insecure for shared memory segments?
>
> Yes; Enlightenment does have it's own little set of features...
>
> [EMAIL PROTECTED]XFree86 Core Team SuSE, Inc.
>
I recieved a bunch and bunch of these messages when i run out of shm
Keith Packard wrote:
Odd, Isn't 777 insecure for shared memory segments?
Yes; Enlightenment does have it's own little set of features...
[EMAIL PROTECTED]XFree86 Core Team SuSE, Inc.
I recieved a bunch and bunch of these messages when i run out of shm
segments. The
safemode wrote:
> Mark Hahn wrote:
>
>> this has nothing to do with the linux kernel.
>> X itself does not use shm for anything. apps may use
>> an X extension (XSHM) which uses shm segments to exchange
>> image data without copying through a socket, but that's
Mark Hahn wrote:
this has nothing to do with the linux kernel.
X itself does not use shm for anything. apps may use
an X extension (XSHM) which uses shm segments to exchange
image data without copying through a socket, but that's
an extension, not inherent to X.
> Ok, compiling using a cvs of X
Alan Cox wrote:
> I have about 16 after 2 days. Thats a fairly typical desktop (gnome
panel,
> gfm and everything else is a terminal window)
Whoa now?! 16 shm segments?if that's true something is terribly
wrong with either X or the kernel's handling of shm that's scary.
this
is
safemode wrote:
> Ok, compiling using a cvs of X i got a couple hours ago, I'm just
> wondering what the average segment number is for SHM on an X session
> that has been up for a while i'll get back with any sort of info
> on if the SHM problem has been solved with thi
Ok, compiling using a cvs of X i got a couple hours ago, I'm just
wondering what the average segment number is for SHM on an X session
that has been up for a while i'll get back with any sort of info
on if the SHM problem has been solved with this latest CVS or if it
continues to look like
David Ford wrote:
> safemode wrote:
>
> > i'll get back about the latest xfree86 in about 2 hours .. but if anyone has any
>other ideas
> > or info i can give ...it's not problem. test8 seems stable enough to keep itself
>up until
> > i'm ready to reboot.
>
David Ford wrote:
> safemode wrote:
>
> > One more little complaint.. why doesn't vger replace the FROM to
> > [EMAIL PROTECTED] like any other sane mailing list ... i
> > keep going to Reply and not sending to the list. At least add a
> > reply-to tag like the p
2.4.0-test8-vm3 seems quite stable with this CVS of X
After running xawtv and gqmpeg ...which would quickly die due to shm
being maxed .. it still works and shows ~ 839 segments ..not really
moving from it
And after 20 min with all the apps i had open before, still not in
swap. Which on test9,
David Ford wrote:
> safemode wrote:
>
> > It seems to me that test8-vm3 handles this fine. in test9 upon loading X i was
> > already using swap and down to 10MB ... here i have netscape loaded and some other
> > stuff along with gaim and i've got 36MB free still.
t and post your comments there. There is another
> gentlemen with a similar problem. I'm changing pace here, I believe the kernel is
> fine and it is an X issue as it occurs on 2.2 as well. Visit the tail of:
> http://www.xfree86.org/pipermail/xpert/2000-September/thread.html.
>
> -d
.
David Ford wrote:
> I think it's time to get Christoph on the line and see what he has to say. The
> 4096 number is a limit to the system, you can have a max of 4096 shared memory
> segments systemwide. Do you know offhand which programs are using(abusing)
> shm?
>
> -d
David Ford wrote:
> No, those two are often empty. Does the total of the first group's bytes
> column match the used column of df?
>
> -d
The sum of the Bytes used in the 4096 entries ipcs shows is WAY off from the
bytes used in df if that's what you wanted to know.df shows 109K in
use...
David Ford wrote:
> safemode wrote:
>
> > xawtv will still work but gqmpeg cannot run. shget returns no memory
> > available on any app trying to access it. Well, hope that tells
> > someone something because i'm stumped .. something in shm seems
> > br
David Ford wrote:
> safemode wrote:
>
> > xawtv will still work but gqmpeg cannot run. shget returns no memory
> > available on any app trying to access it. Well, hope that tells
> > someone something because i'm stumped .. something in shm seems
> > br
In running xawtv i stumbled upon a very interesting message
shmget: No space left on device
yet df -m shows
shm 8192 108 8084 2% /var/shm
I'm not sure what's going on here, /var/shm shows a BUNCH of files in
it.. and none of my partitions are even close to
I'd like to start out by saying Rik's latest patch to test8 was working
GREAT except that deadlock problem which after 7 days of uptime in X
finally occurred. So, I thought, updating to the latest normal kernel
should have that and it fixed. Obviously I was wrong. The kernel is
displaying
I'd like to start out by saying Rik's latest patch to test8 was working
GREAT except that deadlock problem which after 7 days of uptime in X
finally occurred. So, I thought, updating to the latest normal kernel
should have that and it fixed. Obviously I was wrong. The kernel is
displaying
In running xawtv i stumbled upon a very interesting message
shmget: No space left on device
yet df -m shows
shm 8192 108 8084 2% /var/shm
I'm not sure what's going on here, /var/shm shows a BUNCH of files in
it.. and none of my partitions are even close to
David Ford wrote:
safemode wrote:
xawtv will still work but gqmpeg cannot run. shget returns no memory
available on any app trying to access it. Well, hope that tells
someone something because i'm stumped .. something in shm seems
broken.. or the vm is.
what does 'ipcs
1 - 100 of 121 matches
Mail list logo
