Bug 25153

Summary: kdump does not finish displaying data
Product: Base System Reporter: Jim.Pirzyk <Jim.Pirzyk>
Component: binAssignee: Jim Pirzyk <pirzyk>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.2-RELEASE   
Hardware: Any   
OS: Any   

Description Jim.Pirzyk 2001-02-16 23:20:01 UTC 
	running kdump on this output file, it fails with Cannot allocate memory
	after accessing the last break call .  Here is the kdump on the kdump:

Jim.Pirzyk@snoopy:/usr/src/usr.bin/kdump
46>kdump | grep break
 56504 kdump    CALL  break(0x804e000)
 56504 kdump    RET   break 0
 56504 kdump    CALL  break(0x804f000)
 56504 kdump    RET   break 0
 56504 kdump    CALL  break(0x8051000)
 56504 kdump    RET   break 0
 56504 kdump    CALL  break(0x8052000)
 56504 kdump    RET   break 0
 56504 kdump    CALL  break(0x8054000)
 56504 kdump    RET   break 0
 56504 kdump    CALL  break(0x808b000)
 56504 kdump    RET   break 0
 56504 kdump    CALL  break(0x7d772000)
 56504 kdump    RET   break -1 errno 12 Cannot allocate memory

How-To-Repeat: 
	I can send the ktrace.out file, but compressed, it still is over 1MB.
Comment 1 Bruce Evans 2001-02-17 12:01:48 UTC 
On Fri, 16 Feb 2001 Jim.Pirzyk@disney.com wrote:

> >Description:
> 
> 	running kdump on this output file, it fails with Cannot allocate memory
> 	after accessing the last break call .  Here is the kdump on the kdump:

This may be caused by breakage of atomic writing of ktrace records in
rev.1.37 of kern_ktrace.c.  Perhaps there is only a problem when the
ktrace output file is on an nfs filesystem.  There must be multiple
processes writing to the same file to cause problems.

Bruce
Comment 2 Jim Pirzyk freebsd_committer freebsd_triage 2001-07-20 01:36:18 UTC 
Responsible Changed
From-To: freebsd-bugs->pirzyk

another PR of mine
Comment 3 Jim Pirzyk freebsd_committer freebsd_triage 2001-12-20 00:44:27 UTC 
State Changed
From-To: open->closed

Closed since now I should be using linux_kdump instead of just 
kdump.