[vox-tech] kernel oops resulting in hung processes.

Ryan Castellucci vox-tech@lists.lugod.org
Wed, 12 Feb 2003 11:09:11 -0800


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 12 February 2003 10:51 am, Peter Jay Salzman wrote:
> begin Ryan Castellucci <ryan+lugod@cal.net>
>
> > This is not the first time this has happened, but it's really startin=
g to
> > bug me.
> >
> > I got this last night when my nightly security checks were running.
> >
> > Feb 12 04:22:44 windy kernel: Device not ready.  Make sure there is a
> > disc in the drive. Feb 12 04:22:44 windy kernel: sda : READ CAPACITY
> > failed.
> > Feb 12 04:22:44 windy kernel: sda : status =3D 1, message =3D 00, hos=
t =3D 0,
> > driver =3D 08 Feb 12 04:22:44 windy kernel: Info fld=3D0xa00 (nonstd)=
,
> > Current sd00:00: sense key Not Ready Feb 12 04:22:44 windy kernel: sd=
a :
> > block size assumed to be 512 bytes, disk size 1GB. Feb 12 04:22:44 wi=
ndy
> > kernel:  /dev/scsi/host1/bus0/target0/lun0: I/O error: dev 08:00, sec=
tor
> > 0 Feb 12 04:22:44 windy kernel:  I/O error: dev 08:00, sector 0
> > Feb 12 04:22:44 windy kernel: Unable to handle kernel paging request =
at
> > virtual address 3a2061a8 Feb 12 04:22:44 windy kernel:  printing eip:
> > Feb 12 04:22:44 windy kernel: c0160783
> > Feb 12 04:22:44 windy kernel: *pde =3D 00000000
> > Feb 12 04:22:44 windy kernel: Oops: 0000
> > Feb 12 04:22:45 windy kernel: CPU:    0
> > Feb 12 04:22:45 windy kernel: EIP:    0010:[scan_dir_for_removable+19=
/64]
> >    Tainted: PF Feb 12 04:22:45 windy kernel: EIP:    0010:[<c0160783>=
]  =20
> > Tainted: PF Feb 12 04:22:45 windy kernel: EFLAGS: 00010202
> > Feb 12 04:22:45 windy kernel: eax: df761b60   ebx: 3a206164   ecx:
> > 00000000   edx: df761b60 Feb 12 04:22:45 windy kernel: esi: c9ff6be0 =
=20
> > edi: c6d6a360   ebp: df687540   esp: cb567f28 Feb 12 04:22:45 windy
> > kernel: ds: 0018   es: 0018   ss: 0018
> > Feb 12 04:22:45 windy kernel: Process find (pid: 13919,
> > stackpage=3Dcb567000) Feb 12 04:22:45 windy kernel: Stack: c9ff6be0
> > c0160c16 c6d6a360 c02661e0 00000000 c9ff6be0 c9ff6c60 c9ff6c4c Feb 12
> > 04:22:45 windy kernel:        df687540 c0141690 df687540 cb567fa0
> > c0141b90 df687540 fffffff7 00000004 Feb 12 04:22:45 windy kernel:    =
  =20
> > bfffeee8 c0141d3f df687540 c0141b90 cb567fa0 00000778 dffcb360 41ed00=
07
> > Feb 12 04:22:45 windy kernel: Call Trace: [devfs_readdir+86/448]
> > [vfs_readdir+96/144] [filldir64+0/352] [sys_getdents64+79/185]
> > [filldir64+0/352] Feb 12 04:22:45 windy kernel: Call Trace: [<c0160c1=
6>]
> > [<c0141690>] [<c0141b90>] [<c0141d3f>] [<c0141b90>] Feb 12 04:22:45 w=
indy
> > kernel:    [sys_swapoff+321/640] [system_call+51/64] Feb 12 04:22:45
> > windy kernel:    [<c0130001>] [<c0106f23>]
> > Feb 12 04:22:45 windy kernel:
> > Feb 12 04:22:45 windy kernel: Code: 66 8b 43 44 25 00 f0 00 00 66 3d =
00
> > 60 75 0d f6 43 10 04 74
> >
> > sda is sometimes a USB device, was not plugged in at the time.
> >
> > Anyone know where things went wrong here?
> >
> > This error resulted in processes getting hung in the 'D' state (as
> > reported by top)
> >
> > I ended up having to reboot. Any ideas?
>
> why not disable devfs and see if this happens again?

I can try that, but it will take a while. this problem tends to crop up e=
very=20
few weeks without warning.

> also, see:
>
> /usr/src/linux-2.4.20/Documentation/oops-tracing.txt
>
> and why did you reboot?  because of a few processes in the D state?

New processes were hanging as I attempted to use the system. It quickly=20
became unusable.

- --=20
PGP/GPG Fingerprint: 3B30 C6BE B1C6 9526 7A90  34E7 11DF 44F3 7217 7BC7
On pgp.mit.edu, import with `gpg --keyserver pgp.mit.edu --recv-key 72177=
BC7`
Also available at http://www.cal.net/~ryan/ryan_at_mother_dot_com.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+SpvXEd9E83IXe8cRAnDRAKCecw65AfeDMpgsc/dvL/xKRImb5wCff2db
IRLgbkCHRhIajvOfs759/FQ=3D
=3Dba1l
-----END PGP SIGNATURE-----