home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.linux
- Path: sparky!uunet!sun-barr!cs.utexas.edu!zaphod.mps.ohio-state.edu!rpi!batcomputer!theory.TC.Cornell.EDU!mdw
- From: mdw@theory.TC.Cornell.EDU (Matt Welsh)
- Subject: Re: Freeze-up after 'sock_init:...'
- Message-ID: <1992Sep11.001054.11085@tc.cornell.edu>
- Sender: news@tc.cornell.edu
- Nntp-Posting-Host: theory.tc.cornell.edu
- Organization: Cornell Theory Center
- References: <1992Sep10.210423.6701@tc.cornell.edu> <1992Sep10.214829.9832@lambda.msfc.nasa.gov>
- Date: Fri, 11 Sep 1992 00:10:54 GMT
- Lines: 27
-
- In article <1992Sep10.214829.9832@lambda.msfc.nasa.gov> davisdm@widget (Mat Davis) writes:
- >Matt Welsh (mdw@theory.TC.Cornell.EDU) wrote:
- >: In article <1992Sep10.162933.29988@lambda.msfc.nasa.gov> davisdm@widget (Mat Davis) writes:
- >: >I'm having trouble with Linux freezing after the 'sock_init:...' message.
- >:
- >: (and so on)
- >:
- >: This is a known problem with the SCSI drivers... if you don't have any
- >: SCSI devices then get the kernel code, dyke out the SCSI drivers, and
- >: recompile. Works like a charm. (I know; I posted the same problem just
- >: a few days ago).
- >:
- >If that's it, I've still got two questions:
- >
- >Why did it work so smoothly the first time and then *suddenly* start
- >having problems? The hardware wasn't touched.
-
- The problem is, at least for me, sporadic. If I ever get my kernel working
- again (after all my frivolous hacks on it...) I could send you mine,
- rdev-ed to the device of your choice. :)
-
- mdw
-
- --
- Matt Welsh mdw@tc.cornell.edu +1 607 253 2737
- Random Hacker, Cornell Engineering and Theory Center
- "People will say we're in love." --Hannibal Lecter
-