[Prev][Next][Index][Thread]

Re: Quantom 2.5G Hard-Disk problem.



There is no trace for the error in /var/log/messages. Probably the
disk was made inaccessible and error could not be written.

I know the many changes required for the 2.x kernel but anyway, after
this problem become unbarable, I tried using the very stable, 1.2.13
kernel. The system (RedHat 4.0) with 1.2.13 kernel, including X and
many applications are up and running, excluding xterm. I can not open
xterm window and the reported error is "no pty's". (This is of course
not the problem for my 2.x kernel and another thing, I compiled the
2.0.27 kernel as embeded one with out loading modules and comment out
starting load module deamon, so it probably makes less problem for 1.2.13).

Any clue ? 

Thanks,
Shlomo.

> From benavrhm@tcltek.co.il  Tue Jan 21 16:40:53 1997
> Date: Tue, 21 Jan 1997 16:37:44 +0200 (IST)
> From: Jonathan Ben-Avraham <benavrhm@tcltek.co.il>
> X-Sender: benavrhm@banjo
> To: Shlomo Reches <shlomor@msil.sps.mot.com>
> Cc: linux-il@linux.org.il
> Subject: Re: Quantom 2.5G Hard-Disk problem.
> Mime-Version: 1.0
> Content-Type> : > TEXT/PLAIN> ; > charset=US-ASCII> 
> Content-Length: 3507
> 
> On Tue, 21 Jan 1997, Shlomo Reches wrote:
> 
> > Hi,
> > 
> > I have a disk problem, which cause the machine to halt (It sometimes
> > happand few minutes after I start Linux).
> > 
> > I used to think it is the kernel (2.0.18), but it was upgraded since
> > (2.0.27) and the problem is still there.
> > 
> > I would like to ask if anyone has the same disk as mine and weather
> > the same problem was experienced.
> > 
> > More info
> > ---------
> > - P/133, soyo HX (Triton III) mother board with a Quantum IDE 2.5G hard disk.
> > 
> > - It is definitly hardware problem, because after hardware reset, a disk
> >   failure error (20) is reported. Only turning off, than on again, makes the
> >   disk operational. I suspect the disk than the motherboard's (soyo hx) chipsets
> >   or settings and last the on-board IDE controller.
> > 
> > - It happands only under Linux, which let me believe, it uses some advanced
> >   feature of the disk, not used by Windogs. This puts the disk in a certain
> >   state, which is not reset due to a bug.
> > 
> > - The error has something to do with the swap space. The error can occur when
> >   running any program. In some, I get a more detailed error, which point to
> >   the swap.
> > 
> > Thanks,
> > Shlomo.
> > 
> I have seen similar problems with various 2.X kernels. Please send 
> /var/log/messages output. When this happened to me I got:
> 
> Jan  5 21:52:32 tango kernel: Unable to handle kernel paging request 
> at virtual address 000d7661
> Jan  5 21:52:32 tango kernel: current->tss.cr3 = 00101000, $r3 = 00101000
> Jan  5 21:52:32 tango kernel: *pde = 00000000
> Jan  5 21:52:32 tango kernel: Oops: 0000
> Jan  5 21:52:32 tango kernel: CPU:    0
> Jan  5 21:52:32 tango kernel: EIP:    0010:[<c0111ed0>]
> Jan  5 21:52:32 tango kernel: EFLAGS: 00010203
> Jan  5 21:52:32 tango kernel: eax: c0bf1e34   ebx: 000d7661   ecx: 
> c0bf1e34  
>  edx: c379989c
> Jan  5 21:52:32 tango kernel: esi: c3799900   edi: c0bf1e30   ebp: 
> c01ec270  
>  esp: c01ec264
> Jan  5 21:52:32 tango kernel: ds: 0018   es: 0018   ss: 0018
> Jan  5 21:52:32 tango kernel: Process swapper (pid: 0, process nr: 0, 
> stackpage=c01ea40c)
> Jan  5 21:52:32 tango kernel: Stack: c3799810 c3799900 00000000 
> ad2e0799 c015
> 37d8 c0bf1e34 c3799810 c014a5b1 
> Jan  5 21:52:32 tango kernel:        c3799810 00000000 c3799810 
> c3b56164 0000
> 0014 c014a9d2 c3b56164 c3799810 
> Jan  5 21:52:32 tango kernel:        00000014 c3799810 c3b56164 
> c3b56148 0000
> 7100 ad2de799 00000001 c0140014 
> Jan  5 21:52:32 tango kernel: Call Trace: [<c01537d8>] [<c014a5b1>] 
> [<c014a9d
> 2>] [<c0140014>] [<c014e4d3>] [<c01437d6>] [<c01439b1>] 
> Jan  5 21:52:32 tango kernel:        [<c013c318>] [<c011861f>] 
> [<c010a7bb>] [
> <c0109674>] [<c010a818>] [<c010935c>] [<c01091c3>] [<c01cf909>] 
> Jan  5 21:52:32 tango kernel:        [<c0117ca0>] [<c0111d44>] 
> Jan  5 21:52:32 tango kernel: Code: 8b 13 8b 5b 04 85 d2 74 65 8b 02 
> 83 f8 01
>  75 5e 9c 5e fa c7 
> Jan  5 21:52:32 tango kernel: Aiee, killing interrupt handler
>                               ~~~~
> The above sequence repeats itself until at some point something gets
> trashed and the kernel halts. Usually there is file system damage as 
> a result. This is how we lost ftp.linux.org.il about 10 days ago. I 
> solved this problem by moving to 2.1.20 - which doesn't support IP 
> aliasing correctly BTW. Again - give us more info.
> 
>  - yba
> 
>    EE 77 7F 30 4A 64 2E C5  83 5F E7 49 A6 82 29 BA    ~. .~   TclTek Ltd.
>  =}-------------------------------------------------ooO--U--Ooo-----------{=
>   - benavrhm@tcltek.co.il - tel: +972.52.670.353, http://www.tcltek.co.il -
> 


Follow-Ups: