Project

General

Profile

Bug #4400

kernel panic

Added by Reginald Beardsley over 5 years ago. Updated over 5 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Start date:
2013-12-13
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage

Description

I think this includes everything requested in the wiki. If not please let me know. I've saved the contents of /var/crash if that is desired. System is a dual core Atom w/ nVidia chipset running oi_151a8.

root@openindiana:~# fmdump -Vp -u ad5528d9-9507-42d8-8892-e38a3d3e0b02
TIME                           UUID                                 SUNW-MSG-ID
Dec 12 2013 16:10:48.061641000 ad5528d9-9507-42d8-8892-e38a3d3e0b02 SUNOS-8000-KL

  TIME                 CLASS                                 ENA
  Dec 12 16:10:47.9390 ireport.os.sunos.panic.dump_available 0x0000000000000000
  Dec 12 16:09:40.2242 ireport.os.sunos.panic.dump_pending_on_device 0x0000000000000000

nvlist version: 0
    version = 0x0
    class = list.suspect
    uuid = ad5528d9-9507-42d8-8892-e38a3d3e0b02
    code = SUNOS-8000-KL
    diag-time = 1386886247 968517
    de = fmd:///module/software-diagnosis
    fault-list-sz = 0x1
    fault-list = (array of embedded nvlists)
    (start fault-list[0])
    nvlist version: 0
        version = 0x0
        class = defect.sunos.kernel.panic
        certainty = 0x64
        asru = sw:///:path=/var/crash/openindiana/.ad5528d9-9507-42d8-8892-e38a3d3e0b02
        resource = sw:///:path=/var/crash/openindiana/.ad5528d9-9507-42d8-8892-e38a3d3e0b02
        savecore-succcess = 1
        dump-dir = /var/crash/openindiana
        dump-files = vmdump.0
        os-instance-uuid = ad5528d9-9507-42d8-8892-e38a3d3e0b02
        panicstr = BAD TRAP: type=e (#pf Page fault) rp=ffffff0003cfba30 addr=0 occurred in module "genunix" due to a NULL pointer dereference
        panicstack = unix:die+dd () | unix:trap+17db () | unix:cmntrap+e6 () | genunix:taskq_thread_wait+84 () | genunix:taskq_thread+308 () | unix:thread_start+8 () | 
        crashtime = 1386886048
        panic-time = December 12, 2013 04:07:28 PM CST CST
    (end fault-list[0])

    fault-status = 0x1
    severity = Major
    __ttl = 0x1
    __tod = 0x52aa3468 0x3ac9128

oot@openindiana:/var/crash/openindiana# echo '::panicinfo\\\\n::cpuinfo -v\\\\n::threadlist -v 10\\\\n::msgbuf\\\\n*panic_thread::findstack -v\\\\n::stacks' | mdb 0 > ~/crash.0
mdb: failed to read thread at ffffff0003f34c40: no mapping for address
mdb: failed to read thread at ffffff0003f34c40: no mapping for address
mdb: failed to read thread at ffffff0003f34c40: no mapping for address
root@openindiana:/var/crash/openindiana# 

root@openindiana:~/panic# ls -l
total 2230613
-rw-r--r--   1 root     root           2 Dec 12 16:10 bounds
-rw-r--r--   1 root     root      134282 Dec 13 07:58 crash.0
-rw-r--r--   1 root     root           0 Dec 13 07:57 panic.0
-rw-r--r--   1 root     root     2879905 Dec 13 07:57 unix.0
-rw-r--r--   1 root     root     858304512 Dec 13 07:58 vmcore.0
-rw-r--r--   1 root     root     285212672 Dec 12 16:10 vmdump.0
root@openindiana:~/panic# 

Files

crash.0 (131 KB) crash.0 Reginald Beardsley, 2013-12-13 05:12 PM

History

#1

Updated by Marcel Telka over 5 years ago

Please make the crash dump file (vmdump.0) available. Thanks.

#2

Updated by Piotr Jasiukajtis over 5 years ago

Reginald Beardsley wrote:

I think this includes everything requested in the wiki. If not please let me know. I've saved the contents of /var/crash if that is desired. System is a dual core Atom w/ nVidia chipset running oi_151a8.

[...]

Could you upload crash.0 file to this BUG report?

#3

Updated by Reginald Beardsley over 5 years ago

I'm not running any external services so I don't have a convenient mechanism at the moment. I'll look into finding a way when I have more time. I have moved all the files to the root home directory (/root on my system) so they won't get lost and I can transfer them by ftp at any time.

Dropbox, Thoth or similar will take some study as I'm not familiar w/ any of them or their dependencies.

#4

Updated by Reginald Beardsley over 5 years ago

I attempted to upload crash.0 when I created the report. Maybe it will get there this time

#5

Updated by Garrett D'Amore over 5 years ago

Do you have any further details about what you were doing when this occurred? I see lots of what look like keyboard hot plug events in the log. Unfortunately, debugging from just what you have here is not going to be very easy without the actual kernel crash, because the stack backtrace just includes a generic taskq which is... unfortunate.

#6

Updated by Reginald Beardsley over 5 years ago

Keyboard hotplug events are because I'm using a 4 port KVM switch to access the system. I've got the coredump if you've got someplace for me to put it.

Here's what I have saved:

rw-r--r- 1 root root 285212672 Dec 12 16:10 vmdump.0
rw-r--r- 1 root root 2 Dec 12 16:10 bounds
rw-r--r- 1 root root 0 Dec 13 07:57 panic.0
rw-r--r- 1 root root 2879905 Dec 13 07:57 unix.0
rw-r--r- 1 root root 858304512 Dec 13 07:58 vmcore.0
rw-r--r- 1 root root 134282 Dec 13 07:58 crash.0

Also available in: Atom PDF