On Sunday 15 June 2003 12:19 pm, Tom Brinkman wrote:
> One more thought, tho I think the suggestions you've gotten to
> check the filesystem are probly better ... take a look at
> /etc/updatedb.conf and see if it isn't corrupted or incomplete.
Looks identical here Thanks for the suggesti
On Sunday June 15 2003 07:52 am, Ronald J. Hall wrote:
> On Sunday 15 June 2003 07:58 am, Tom Brinkman wrote:
> > 'locate -u' == 'updatedb'Sorry I must'a missed the part
> > where you've had this problem even after a fresh install. You
> > could try 'bonnie++' to see if your drive(s) are b
On Sunday 15 June 2003 07:58 am, Tom Brinkman wrote:
> 'locate -u' == 'updatedb'Sorry I must'a missed the part
> where you've had this problem even after a fresh install. You
> could try 'bonnie++' to see if your drive(s) are behaving up to
> par. Should be on your CD's.
No problem - I
On Saturday 14 June 2003 06:39 pm, James Sparenberg wrote:
> pulling at straws here. if you do ulimit... what does it say?
>
> James
James, that was a good thought there, but for root and my normal user it
reports "unlimited". :-)
--
/\
On Saturday June 14 2003 10:59 am, Ronald J. Hall wrote:
> On Saturday 14 June 2003 09:43 am, Tom Brinkman wrote:
> > That means you've got no problems with cpu/cache/ram and
> > that your cooling is adequate under extreme load. I suspect
> > your problem involves some files or such that got c
On Sat, 2003-06-14 at 12:38, Ronald J. Hall wrote:
> On Saturday 14 June 2003 01:31 pm, Luca Olivetti wrote:
>
> > Try without it (either boot to runlevel 3 or use the nv driver instead)
> > to see if it makes a difference.
> >
> > Bye
>
> Oh, I had already tried it in single-user mode - made no
On Saturday 14 June 2003 02:31 pm, Lorne wrote:
> I just went back and tried expert and it isn't like i remember the older
> versions either. ?
Yes, its different now.
> hdparm -d /dev/hda
> /dev/hda:
> using_dma= 0 (off)
>
> Will give info on if you are using DMA, I believe someone asked
On Saturday 14 June 2003 02:15 pm, Lorne wrote:
> Would it be out of the question to load 9.0 on it again fresh and see if
> the problem goes away? Even if you put it on another hard drive. Although
> it would be better to use the same HD if possible. I've been watching the
> thread and even thoug
On Saturday 14 June 2003 01:31 pm, Luca Olivetti wrote:
> Try without it (either boot to runlevel 3 or use the nv driver instead)
> to see if it makes a difference.
>
> Bye
Oh, I had already tried it in single-user mode - made no difference. I also
routinely boot to 3, then "startx". I tried it
On Sat, 2003-06-14 at 09:06, Ronald J. Hall wrote:
> On Saturday 14 June 2003 10:27 am, Damian Gatabria wrote:
>
> > OK, so i'm pretty much convinced it's not a bad drive.. you probably
> > already tried, but did you fsck / ? (the one at boot doesn't count as
> > AFAIK it's run with certain para
You should have the pgm 'reiserfsck' installed ..usage is 'reiserfsck
/dev/partition-to-check' . The partition should not be mounted.
I haven't had a problem with a reiser partition in some time but about a
year ago used reiserfsck to recover a damaged fs where it worked
perfectly.
See 'man reise
On Sat, 2003-06-14 at 14:15, Lorne wrote:
>
> Would it be out of the question to load 9.0 on it again fresh and see if the
> problem goes away? Even if you put it on another hard drive. Although it
> would be better to use the same HD if possible. I've been watching the thread
> and even thoug
On Friday 13 June 2003 09:15 pm, Ronald J. Hall wrote:
> On Friday 13 June 2003 07:51 pm, Lorne wrote:
> > I wonder if it is a bad hard drive, and or controller. No errors during
> > install? For it to die like that it just seems/smells hardware based. Are
> > you running hdparm and doing anything
On Friday 13 June 2003 09:12 pm, Ronald J. Hall wrote:
> On Friday 13 June 2003 07:51 pm, Lorne wrote:
> > I wonder if it is a bad hard drive, and or controller. No errors during
> > install? For it to die like that it just seems/smells hardware based. Are
> > you running hdparm and doing anything
En/na Ronald J. Hall ha escrit:
On Saturday 14 June 2003 08:38 am, Luca Olivetti wrote:
By chanche, are you using the nvidia driver?
I had similar problems (kernel oopses with high load, normally while
doing an updatedb) if I used the nvidia driver, but only with previous
versions (8.2, 9.0). Neve
On Saturday 14 June 2003 13:06, Ronald J. Hall wrote:
> On Saturday 14 June 2003 10:27 am, Damian Gatabria wrote:
> > OK, so i'm pretty much convinced it's not a bad drive.. you probably
> > already tried, but did you fsck / ? (the one at boot doesn't count as
> > AFAIK it's run with certain para
On Saturday 14 June 2003 10:27 am, Damian Gatabria wrote:
> OK, so i'm pretty much convinced it's not a bad drive.. you probably
> already tried, but did you fsck / ? (the one at boot doesn't count as
> AFAIK it's run with certain parameters not to check/fix some aspects of the
> file system)
>
On Saturday 14 June 2003 10:25 am, Lyvim Xaphir wrote:
> The logic of this says to me that if your system is installed off the
> cd's just like everybody else's is, then you should be getting the
> results that everyone else is getting. Since we know your hardware is
> pristine, and since you are
On Saturday 14 June 2003 09:43 am, Tom Brinkman wrote:
> That means you've got no problems with cpu/cache/ram and that
> your cooling is adequate under extreme load. I suspect your
> problem involves some files or such that got corrupted by all these
> hard lockups and resets you've had. Tho
On Saturday 14 June 2003 08:38 am, Luca Olivetti wrote:
>
> By chanche, are you using the nvidia driver?
> I had similar problems (kernel oopses with high load, normally while
> doing an updatedb) if I used the nvidia driver, but only with previous
> versions (8.2, 9.0). Never had a problem (crossi
On Saturday 14 June 2003 01:15, Ronald J. Hall wrote:
> On Friday 13 June 2003 07:51 pm, Lorne wrote:
> > I wonder if it is a bad hard drive, and or controller. No errors during
> > install? For it to die like that it just seems/smells hardware based. Are
> > you running hdparm and doing anything t
On Sat, 2003-06-14 at 00:26, Ronald J. Hall wrote:
> Okay, a bit of an update. I deleted the slocate.db.tmp file in
> /var/lib/slocate, and reran updatedb. Crash - spont. reboot.
>
> I did a urpme slocate, then a urpmi slocate. Reran updatedb.
> Crash - spont. reboot.
>
> I turned DMA off to /de
On Friday June 13 2003 11:09 pm, Ronald J. Hall wrote:
> On Thursday 12 June 2003 06:39 pm, Miark wrote:
> > Sounds like a hardware problem that manifests itself with a lot
> > of heat. Is there some other CPU-intensive stuff you could try
> > to test that theory, like rendering some video?
> >
> >
En/na Ronald J. Hall ha escrit:
Let me thank everyone who's tried to help so far. I guess I ought to mention
that under v9.0 of Mandrake, this same hardware setup did not have this
problem at all.
By chanche, are you using the nvidia driver?
I had similar problems (kernel oopses with high load,
On Saturday 14 June 2003 01:04 am, James Sparenberg wrote:
> Wait a sec... had an epiphany...(or gas, not sure) ... doesn't slocate
> use the sleep cat dbs? aka db1 db2 etc etc. If these are bad maybe
> that's the problem. A script the other day was submitted that might
> find out if anything i
On Fri, 2003-06-13 at 21:38, Ronald J. Hall wrote:
> Argh. Forgot about anacron. I always install it. At a few minutes after 12,
> just now, it ran. For a very short while. Guess what happened? :-(
>
> BTW, is there any chance someone can look at their /var/lib/slocate.db.tmp
> file and see if t
Ronald J. Hall wrote:
Argh. Forgot about anacron. I always install it. At a few minutes after 12,
just now, it ran. For a very short while. Guess what happened? :-(
BTW, is there any chance someone can look at their /var/lib/slocate.db.tmp
file and see if they can read it? Are you supposed to be
> action it might help in finding the common thread. If it doesn't die...
> I'd go back to urpme urpmi
sounds like a cool sig (and it even rhymes)
> James
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
Argh. Forgot about anacron. I always install it. At a few minutes after 12,
just now, it ran. For a very short while. Guess what happened? :-(
BTW, is there any chance someone can look at their /var/lib/slocate.db.tmp
file and see if they can read it? Are you supposed to be able to? Mine looks
Okay, a bit of an update. I deleted the slocate.db.tmp file in
/var/lib/slocate, and reran updatedb. Crash - spont. reboot.
I did a urpme slocate, then a urpmi slocate. Reran updatedb.
Crash - spont. reboot.
I turned DMA off to /dev/hda, then reran updatedb. Crash -spont. reboot.
Thank goodne
On Friday 13 June 2003 10:11 pm, Damian Gatabria wrote:
> Sorry for butting in -- have you tried disabling DMA?
>
> hdparm -d0 /dev/hdX && updatedb ..
>
>
> HTH
>
> Damian
Damian, by all means butt away!
Seriously though, I've not tried disabling DMA. I've always used DMA with
previous versi
On Friday 13 June 2003 07:51 pm, Lorne wrote:
> I wonder if it is a bad hard drive, and or controller. No errors during
> install? For it to die like that it just seems/smells hardware based. Are
> you running hdparm and doing anything to soup up to UDMA or anything? What
> about when you install.
On Friday 13 June 2003 07:51 pm, Lorne wrote:
> I wonder if it is a bad hard drive, and or controller. No errors during
> install? For it to die like that it just seems/smells hardware based. Are
> you running hdparm and doing anything to soup up to UDMA or anything? What
> about when you install.
On Thursday 12 June 2003 06:39 pm, Miark wrote:
> Sounds like a hardware problem that manifests itself with a lot of heat.
> Is there some other CPU-intensive stuff you could try to test that
> theory, like rendering some video?
>
> Miark
Just ran cpuburn for about 20 mins with no problems.
--
On Friday 13 June 2003 05:55 pm, Jack Coates wrote:
> slocate crashing would be a segfault. The whole box going down is either
> a kernel bug or hardware failure.
>
> try doing something else disk & cpu intensive, like compiling a kernel.
Okay, I just ran cpuburn for about 20 mins, with nary a hi
> >
> > I wonder if it is a bad hard drive, and or controller. No errors during
> > install? For it to die like that it just seems/smells hardware based. Are
> > you running hdparm and doing anything to soup up to UDMA or anything?
> > What about when you install. regular or expert install? Do you
On Fri, 2003-06-13 at 16:51, Lorne wrote:
> On Friday 13 June 2003 01:17 pm, Ronald J. Hall wrote:
> > On Friday 13 June 2003 04:09 pm, Ronald J. Hall wrote:
> > > slocate.db.tmp, size 1.6mb. I renamed it, will run the command again.
> > > Wish me luck! :-)
> >
> > Well, (hate replying to myself -
On Friday 13 June 2003 01:17 pm, Ronald J. Hall wrote:
> On Friday 13 June 2003 04:09 pm, Ronald J. Hall wrote:
> > slocate.db.tmp, size 1.6mb. I renamed it, will run the command again.
> > Wish me luck! :-)
>
> Well, (hate replying to myself - sound psycho) but...
>
> Ran updatedb as root (single
Sounds like a hardware problem that manifests itself with a lot of heat.
Is there some other CPU-intensive stuff you could try to test that
theory, like rendering some video?
Miark
On Fri, 13 Jun 2003 16:17:33 -0400
"Ronald J. Hall" <[EMAIL PROTECTED]> wrote:
> Well, (hate replying to myself -
On Fri, 2003-06-13 at 13:28, James Sparenberg wrote:
> On Fri, 2003-06-13 at 13:09, Ronald J. Hall wrote:
> > On Friday 13 June 2003 01:31 pm, James Sparenberg wrote:
> >
> > > Dark,
> > >
> > >Sounds like somehow slocate didn't install right. Are there any
> > > error messages in /var/log/me
On Fri, 2003-06-13 at 13:17, Ronald J. Hall wrote:
> On Friday 13 June 2003 04:09 pm, Ronald J. Hall wrote:
>
> > slocate.db.tmp, size 1.6mb. I renamed it, will run the command again. Wish
> > me luck! :-)
>
> Well, (hate replying to myself - sound psycho) but...
>
> Ran updatedb as root (single
On Fri, 2003-06-13 at 13:09, Ronald J. Hall wrote:
> On Friday 13 June 2003 01:31 pm, James Sparenberg wrote:
>
> > Dark,
> >
> >Sounds like somehow slocate didn't install right. Are there any
> > error messages in /var/log/messages or possibly but less likely
> > /var/log/kernel/errors left
On Friday 13 June 2003 04:09 pm, Ronald J. Hall wrote:
> slocate.db.tmp, size 1.6mb. I renamed it, will run the command again. Wish
> me luck! :-)
Well, (hate replying to myself - sound psycho) but...
Ran updatedb as root (single user mode), and it recreated that file, made it
as far as 1.8 meg
On Friday 13 June 2003 01:31 pm, James Sparenberg wrote:
> Dark,
>
>Sounds like somehow slocate didn't install right. Are there any
> error messages in /var/log/messages or possibly but less likely
> /var/log/kernel/errors left behind. Also what is in /var/lib/slocate?
> you may need to remo
On Friday, 13 June 2003 19:31, James Sparenberg wrote:
> On Fri, 2003-06-13 at 07:06, Ronald J. Hall wrote:
> > Why?
> >
> > I've never had this behavior before out of a Mandrake setup.
> >
> > As root, I can type in "updatedb" at a shell, and it will run for 2-3
> > mins, as per usual, then sudden
On Fri, 2003-06-13 at 07:06, Ronald J. Hall wrote:
> Why?
>
> I've never had this behavior before out of a Mandrake setup.
>
> As root, I can type in "updatedb" at a shell, and it will run for 2-3 mins, as
> per usual, then suddenly, monitor goes black, and machine spontaneously
> reboots.
>
>
Why?
I've never had this behavior before out of a Mandrake setup.
As root, I can type in "updatedb" at a shell, and it will run for 2-3 mins, as
per usual, then suddenly, monitor goes black, and machine spontaneously
reboots.
I have an 80 gig HD.
and usually...some kind of damage is done.
Thi
47 matches
Mail list logo
