[lkml]   [1997]   [Aug]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: Keyboard stopped after 2 day uptime!
    On Fri, 22 Aug 1997, Jeffrey Hundstad wrote:

    >I had the same thing happen to me on pre-2.0.31-7 after a couple of
    >hours of uptime...
    >I was using the full text search engine called `Isearch' to re-index the
    >Linux kernel tree. I allowed it to use 20 megabytes of ram from my 32
    >meg machine. It apparently got MORE greedy than that and caused heavy
    >swapping. I switched virtual consoles to see a `ps' to see how much ram
    >that is was taking and the getty on the NEW VC said `re-spawning too fast
    >waiting for 10 minutes.' or something to that effect... I then killed
    >the re-index process. Everything appeared to be working just fine. I
    >then `startx' and went on doing other work. ...after about 10 minutes
    >rxvt quit receiving keystrokes and tkRat (my mailer) didn't receive
    >keystrokes. I managed to kill all of my sessions (with the mouse) and
    >stopped fvwm. I used control-alt-delete successfully to reboot the

    I unfortunately was unsuccessful with c-a-d, the keyboard was totally
    unusable, I had X, pine (in an xterm), prompt that had just finished
    compiling and netscape open, and I also didn't have telnet going at that
    stage, and was able to exit to the console, closing everything correctly.

    >BTW: This happened to me before on 2.0.30.
    >BTW^2: telnetting into the machine worked JUST FINE.

    >> I am runing kernel pre-2.0.31-7, and after 2 days uptime I got this
    >> message:
    >> Aug 23 00:14:57 mabs kernel: hdg: media changed
    >> Aug 23 00:44:28 mabs kernel: hda: status timeout: status=0xd0 { Busy }
    >> Aug 23 00:44:28 mabs kernel: hda: disabled DMA
    >> Aug 23 00:44:28 mabs kernel: hda: drive not ready for command
    >> Aug 23 00:44:28 mabs kernel: ide0: reset: success
    >> Aug 23 00:48:40 mabs kernel: hdg: media changed
    >> And from there on my keyboard stopped working.
    >> Below is my HDD bootup info if anyone is interested:
    >> Aug 23 01:00:18 mabs kernel: ide: i82371 PIIX (Triton) on PCI bus 0 function 57
    >> Aug 23 01:00:18 mabs kernel: ide0: BM-DMA at 0x3000-0x3007
    >> Aug 23 01:00:18 mabs kernel: ide1: BM-DMA at 0x3008-0x300f
    >> Aug 23 01:00:18 mabs kernel: hda: QUANTUM FIREBALL_TM1280A, 1222MB w/76kB Cache, CHS=621/64/63, DMA
    >> Aug 23 01:00:18 mabs kernel: hdc: st3144AT, 124MB w/32kB Cache, CHS=1001/15/17
    >> I have:
    >> iP200
    >> 24Mb RAM, 98Mb Swap
    >> Giga-byte GA-586ATM/P M/B
    >> sda is a 1GB SCSI HDD
    >> P.S. This may have been a spike, but my computer is _very_ spike
    >> protected, but if beyond resonable doubt, it probably will be...


     \ /
      Last update: 2005-03-22 13:40    [W:0.045 / U:43.296 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site