lkml.org 
[lkml]   [1998]   [Apr]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
Subject2.1.96+ stuck in lock_kernel() ??
>Woohoo...
>I ran the following
>dd if=/dev/hda of=/dev/null
>dd if=/dev/hdc of=/dev/null
>make -j for linux-2.1.96 (plus your patches)
>cp -R on medium sized (20Mb) development tree
>
>The first three ran fine for about 3 min. Within 20s of doing the
>cp -R I got a hard lock. I did the Ctrl-Numlock thing and got
>
>EIP: 0010: [<c01d0f93>] EFLAGS: 00000286
>EAX: c05e6000 EBX: c05e6000 ECX: 00000001 EDX: 00000001
>ESI: c0094000 EDI: fffffc18 EBP: c05e7ef8 DS: 0018 ES: 0018
>
>System.map is attached.
>
>kernel 2.1.96 (your [IDE] patches), compiled with pgcc 1.02 with
>-O2 -mpentium -mcpu=pentium -march=pentium

c01d0f70 T __up_wakeup
c01d0f80 T __lock_kernel <--- c01d0f93
c01d0fbc T __delay
c01d0fc4 T __udelay

The IDE driver never calls lock_kernel(),
but I do see a call in scsi_error,
along with a matching unlock_kernel().

Curiously, md.c also invokes lock_kernel(),
but *never* invokes unlock_kernel().

Can anybody explain this?

--
mlord@pobox.com
The Linux IDE guy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu

\
 
 \ /
  Last update: 2005-03-22 13:42    [W:0.031 / U:0.048 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site