Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 17 Nov 2016 07:25:58 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-bugs@FreeBSD.org
Subject:   [Bug 214598] head -r308247: dump from ddb unsuccessful on a powerpc64 PowerMac G5f. . .
Message-ID:  <bug-214598-8@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214598

            Bug ID: 214598
           Summary: head -r308247: dump from ddb unsuccessful on a
                    powerpc64 PowerMac G5f. . .
           Product: Base System
           Version: CURRENT
          Hardware: powerpc
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: kern
          Assignee: freebsd-bugs@FreeBSD.org
          Reporter: markmi@dsl-only.net

[This was on a PowerMac11,3 (PowerMac G5 "Quad Core" --dual socket-each dual
core actually).]

head -r308247: As close to a successful dump from ddb as I've ever had on a
powerpc64 PowerMac G5. . . but it still fails. . .

Transcribed from a camera picture of the screen. . .
(I will drop off various leading zeros and some formatting will be differen=
t.)

KDB: enter: manual escape to debugger
[ thread pid 12 tid 10018 ]
Stopped at       .kdb_enter+0x70:       ori r0, r0, 0x0
db> dump
Dumping 9 MB (3 chunks)
  chunk 0: 10MB (2510 pages) ... ok
  chunk 1: 1MB (24 pages) ... ok
  chunk 2: 1MB (2 pages)panic: vm_fault: fault on nofault entry, addr:
c000000000022000
cpuid =3D 1
KDB: stack backtrace:
0xf93cd0: at .kdb_backtrace+0x6c
0xf93df0: at .vpanic+0x178
0xf93eb0: at .panic+0x34
0xf93f30: at .vm_fault_hold+0x1ac
0xf94120: at .vm_fault+0x98
0xf941c0: at .trap_pfault+0xe8
0xf94240: at .trap+0x1e44
0xf944b0: at .powerpc_interrupt+0x1e0
0xf94550: at kernel DSI read trap 0 0xc000000000022ff8
          by .memcpy+0x144:
          ssr1=3D0x9000000000001032
          r1  =3D  0xf94800
          cr  =3D0x40000424
          xer =3D0x20000000
          ctr =3D     0x200
          r2  =3D 0x10de000
          sr  =3D0x40000000
0xf94800: at .moea64_kextract+0x124
0xf94840: at tmpstk+0x297c
0xf948c0: at ._bus_dmamap_sync+0x124
0xf94960: at .ata_dmaload+0x1e8
0xf94a00: at .ata_begin_transaction+0x240
0xf94aa0: at .ataaction+0x4e0
0xf94b50: at .xpt_run_devq+0x934
0xf94c40: at .xpt_action_default+0x3a8
0xf94cf0: at .ata_action+0x3c8
0xf94d80: at .xpt_actino+0x44
0xf94e00: at .xpt_polled_action+0x60c
0xf94ec0: at .adadump+0x33c
0xf954e0: at .dump_write+0x88
0xf954e0: at .dump_sys_cb_dumpdata+0x124
0xf955c0: at .dumpsys_foreach_chunk+0x68
0xf95660: at .dumpsys_generic+0x26c
0xf95770: at .doadump+0xbc
0xf95800: at .db_dump+0x44
0xf95880: at .db_command+0x3f4

(I omit the rest going back to blocked_loop+0x38.)



Historical note:

I probably last tried this under some 10.x vintage and did just reported th=
at
the DMA request size was too large and stopped.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-214598-8>