Actions
Bug #7672
closedx86 trap trace is annoyingly unreadable in system log/mdb
Start date:
2016-12-16
Due date:
% Done:
100%
Estimated time:
Difficulty:
Bite-size
Tags:
needs-triage
Gerrit CR:
External Bug:
Description
example:
Oct 26 20:05:02 antares ^Mpanic[cpu5]/thread=ffffff03fd8e0840: Oct 26 20:05:02 antares genunix: [ID 335743 kern.notice] BAD TRAP: type=e (#pf Page fault) rp=ffffff0010919ab0 addr=0 occurred in module "<unknown>" due to a NULL pointer dereference Oct 26 20:05:02 antares unix: [ID 100000 kern.notice] Oct 26 20:05:02 antares unix: [ID 839527 kern.notice] mdb: Oct 26 20:05:02 antares unix: [ID 753105 kern.notice] #pf Page fault Oct 26 20:05:02 antares unix: [ID 532287 kern.notice] Bad kernel fault at addr=0x0 Oct 26 20:05:02 antares unix: [ID 243837 kern.notice] pid=100564, pc=0x0, sp=0xffffff0010919ba0, eflags=0x10002 Oct 26 20:05:02 antares unix: [ID 211416 kern.notice] cr0: 8005003b<pg,wp,ne,et,ts,mp,pe> cr4: 406b8<osxsav,xmme,fxsr,pge,pae,pse,de> Oct 26 20:05:02 antares unix: [ID 624947 kern.notice] cr2: 0 Oct 26 20:05:02 antares unix: [ID 625075 kern.notice] cr3: 238843000 Oct 26 20:05:02 antares unix: [ID 625715 kern.notice] cr8: 0 Oct 26 20:05:02 antares unix: [ID 100000 kern.notice] Oct 26 20:05:02 antares unix: [ID 592667 kern.notice] rdi: ffffff0407358000 rsi: 1000000 rdx: ffffffffffff0000 Oct 26 20:05:02 antares unix: [ID 592667 kern.notice] rcx: 0 r8: fffffffffb8010e9 r9: 0 Oct 26 20:05:02 antares unix: [ID 592667 kern.notice] rax: 202 rbx: 1400000 rbp: ffffff0010919ba0 Oct 26 20:05:02 antares unix: [ID 592667 kern.notice] r10: 0 r11: bd8e0840 r12: ffffff0406849800 Oct 26 20:05:02 antares unix: [ID 592667 kern.notice] r13: 1 r14: 0 r15: 2001 Oct 26 20:05:02 antares unix: [ID 592667 kern.notice] fsb: fffffd7fff152a40 gsb: ffffff03ee405580 ds: 0 Oct 26 20:05:02 antares unix: [ID 592667 kern.notice] es: 0 fs: 0 gs: 0 Oct 26 20:05:02 antares unix: [ID 592667 kern.notice] trp: e err: 10 rip: 0 Oct 26 20:05:02 antares unix: [ID 592667 kern.notice] cs: 30 rfl: 10002 rsp: ffffff0010919ba0 Oct 26 20:05:02 antares unix: [ID 266532 kern.notice] ss: 38 Oct 26 20:05:02 antares unix: [ID 359960 kern.notice] Oct 26 20:05:02 antares cpu address timestamp type vc handler pc Oct 26 20:05:02 antares unix: [ID 978388 kern.notice] 0 fffffffffbc1e998 1668f599e4 Oct 26 20:05:02 antares unix: [ID 856552 kern.notice] intr f1 Oct 26 20:05:02 antares unix: [ID 926436 kern.notice] unknown Oct 26 20:05:02 antares unix: [ID 851371 kern.notice] apic_send_ipi+79 Oct 26 20:05:02 antares unix: [ID 978388 kern.notice] 0 fffffffffbc1e820 1668f3945d Oct 26 20:05:02 antares unix: [ID 856552 kern.notice] intr f4 Oct 26 20:05:02 antares unix: [ID 926436 kern.notice] cbe_fire Oct 26 20:05:02 antares unix: [ID 851371 kern.notice] mach_cpu_idle+6 Oct 26 20:05:02 antares unix: [ID 978388 kern.notice] 0 fffffffffbc1e6a8 14fcd60453 Oct 26 20:05:02 antares unix: [ID 856552 kern.notice] intr f0 Oct 26 20:05:02 antares unix: [ID 926436 kern.notice] xc_serv Oct 26 20:05:02 antares unix: [ID 851371 kern.notice] mach_cpu_idle+6 Oct 26 20:05:02 antares unix: [ID 978388 kern.notice] 0 fffffffffbc1e530 14fbefb15b Oct 26 20:05:02 antares unix: [ID 856552 kern.notice] intr f4 Oct 26 20:05:02 antares unix: [ID 926436 kern.notice] cbe_fire Oct 26 20:05:02 antares unix: [ID 851371 kern.notice] mach_cpu_idle+6 Oct 26 20:05:02 antares unix: [ID 978388 kern.notice] 0 fffffffffbc1e3b8 14fb9420bc Oct 26 20:05:02 antares unix: [ID 856552 kern.notice] intr f0 Oct 26 20:05:02 antares unix: [ID 926436 kern.notice] xc_serv Oct 26 20:05:02 antares unix: [ID 851371 kern.notice] mach_cpu_idle+6 Oct 26 20:05:02 antares unix: [ID 978388 kern.notice] 0 fffffffffbc1e240 14fafc6a99 Oct 26 20:05:02 antares unix: [ID 856552 kern.notice] intr f0 Oct 26 20:05:02 antares unix: [ID 926436 kern.notice] xc_serv Oct 26 20:05:02 antares unix: [ID 851371 kern.notice] clock_tick_process+a1 Oct 26 20:05:02 antares unix: [ID 978388 kern.notice] 0 fffffffffbc1e0c8 14fafb836a Oct 26 20:05:02 antares unix: [ID 856552 kern.notice] intr f4 Oct 26 20:05:02 antares unix: [ID 926436 kern.notice] cbe_fire Oct 26 20:05:02 antares unix: [ID 851371 kern.notice] mach_cpu_idle+6 Oct 26 20:05:02 antares unix: [ID 978388 kern.notice] 0 fffffffffbc1df50 14fa075a14 Oct 26 20:05:02 antares unix: [ID 856552 kern.notice] intr f4 Oct 26 20:05:02 antares unix: [ID 926436 kern.notice] cbe_fire Oct 26 20:05:02 antares unix: [ID 851371 kern.notice] mach_cpu_idle+6 Oct 26 20:05:02 antares unix: [ID 978388 kern.notice] 0 fffffffffbc1ddd8 14f913327e Oct 26 20:05:02 antares unix: [ID 856552 kern.notice] intr f4 Oct 26 20:05:02 antares unix: [ID 926436 kern.notice] cbe_fire Oct 26 20:05:02 antares unix: [ID 851371 kern.notice] mach_cpu_idle+6
The problem seems to be that every printf() even without '\n' still makes a separate line in system log, so the trap trace is broken into several lines making it hard to read.
Updated by Electric Monk over 6 years ago
- Status changed from In Progress to Closed
- % Done changed from 50 to 100
git commit 905e0868667e1b82e8e339cd602d782b9fdc8e84
commit 905e0868667e1b82e8e339cd602d782b9fdc8e84 Author: Yuri Pankov <yuri.pankov@nexenta.com> Date: 2017-02-08T16:34:43.000Z 7672 x86 trap trace is annoyingly unreadable in system log/mdb Reviewed by: Robert Mustacchi <rm@joyent.com> Approved by: Richard Lowe <richlowe@richlowe.net>
Actions