home *** CD-ROM | disk | FTP | other *** search
-
- [...]
- >> As far as the _scsi_no_dma here is the error messages I get if I
- >> don't do that.
- >>
- >> bpf: lo0 attached < normal
- >> dmanext at end!!!
- >> trap type 1, code = a24d, v = 426748e7
- >> pid = 1310, pc = 0005A9FC, ps = 2200, sfc = 0001, dfc = 0001
- >> registers
- >> [blah blah blah]
- >> kernel stack
- >> [blah blah blah]
- >>
- >> Any other Ideas?
- >
- >"dmanext at end!!!" is an error message, that should never ever be
- >printed.. What happend, if it is printed, is that the chip has been
- >walked thru the whole data transfer of a running scsi command, and,
- >after having transmitted everything there is to transmit, is interrupted
- >again to continue the transmission. Since there's no data left to
- >transmit, this is an illegal condition. Now, please don't ask me
- >WHY the @#$@ this ever happens...
-
- Just to let you know that he is not alone, I also get the same
- "dmanext at end!!!" message if I have SCSI dma enabled in the
- kernel. I also get a ton of "DMAINTR should never be entered"
- (or something to that effect) messages also. My machine is an
- A3000T. Could this be something linked to a proto chip?
-
- By the way, thanks to everyones for their help in getting my swap
- partition going. It turns out that the kernel would not recognize
- the swap partition unless it was on the same drive as the root
- partition. I have since moved them both onto the same drive, and
- rebuilt the "swapinfo" command, and everything seems to mount and
- work just great..
-
-
- Dave
-
- --
- Dave R. Madsen | Computer Science Department | Office: 107 Atanasoff
- Systems Support Group | Iowa State University | twisted@iastate.edu
- Project Vincent WGA | Ames, Iowa | madsen@cs.iastate.edu
-
-