On 2/1/07, Rao Shoaib <rao.shoaib at sun.com> wrote: > I am unable to get the bufctl's transaction history. > > > ::status > debugging crash dump vmcore.1 (64-bit) from punchin > operating system: 5.11 onnv-gate:2007-01-29 (i86pc) > panic message: > BAD TRAP: type=e (#pf Page fault) rp=ffffff000fdc2140 addr=ffffffff33a6f8ba > dump content: kernel pages only > > > $c > ip_wput_ire+0x1e7d(ffffffff12ddc3a0, fffffffee2fbe7a0, fffffffee9414a88, > fffffffee927d100, 2, 0) > ip_output_options+0x289d(fffffffee927d100, fffffffee2fbe6e0, > ffffffff12ddc3a0, 2 > , ffffffffc0012e60) > ip_output+0x24(fffffffee927d100, fffffffee2fbe6e0, ffffffff12ddc3a0, 2) > ip_wput+0x50(ffffffff12ddc3a0, fffffffee2fbe6e0) > putnext+0x2f1(ffffffff12dd9100, fffffffee2fbe6e0) > icmp_wput_hdrincl+0x2e1(ffffffff12dd9100, fffffffee2fbe6e0, fffffffed2c673e > <....> > > > > fffffffee2fbe7a0::whatis -b > fffffffee2fbe7a0 is fffffffee2fbe7a0+0, bufctl fffffffee315be98 > allocated from > streams_mblk
What is the output of: ::kmem_cache ! grep streams_mblk (i.e. are debugging flags enabled for the cache?) Generally, I wouldn't use the '-b' option to ::whatis; Since Solaris 10 (I believe), ::whatis will automatically print bufctl information if debugging is enabled. (for normal buffers, at least) > > fffffffee315be98::bufctl -v > ADDR BUFADDR TIMESTAMP THREAD > CACHE LASTLOG CONTENTS > fffffffee315be98 fffffffee2fbe7a0 92048f3a82 fffffffed2c9d8c0 > fffffffec0030c08 0 fffffffec813db50 This doesn't look like a bufctl_audit structure at all; it looks like a bufctl_t wrongly printed as a bufctl_audit_t. Once check would be to do: fffffffec0030c08::kmem_cache (i.e. is the cache pointer actually a valid kmem_cache?) Cheers, - jonathan
