Bug 193380

Summary: [panic] firefox privileged instruction fault
Product: Base System Reporter: sasamotikomi
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Open ---    
Severity: Affects Only Me CC: adrian, arved, gecko, kipponi, sasamotikomi
Priority: --- Keywords: crash
Version: 9.2-STABLE   
Hardware: i386   
OS: Any   

Description sasamotikomi 2014-09-06 10:47:27 UTC
core.txt.34
FreeBSD 9.2-RELEASE
instruction pointer     = 0x20:0xc5ee0693
current process         = 3022 (firefox)

 nm -n /boot/kernel.old/kernel | grep 0x
c04b9630 t cam_compat_handle_0x17
c06a5600 T ed_probe_RTL80x9
c06a5880 t ed_rtl80x9_media_ioctl
c06a7750 t ed_pccard_dl100xx_mii_readbits
c06a7800 t ed_pccard_dl100xx_mii_writebits
c09a1110 t xl_txeof_90xB
c09a13a0 t xl_start_90xB_locked
c0f149a0 T ed_probe_WD80x3_generic
c0f15320 T ed_probe_WD80x3
c0f806d0 T Xint0x80_syscall
c0f8be80 t topo_probe_0x4
c136a5c8 d ed_probe_WD80x3.intr_vals
Comment 1 Tilman Keskinoz freebsd_committer freebsd_triage 2014-09-06 20:29:25 UTC
*** Bug 193372 has been marked as a duplicate of this bug. ***
Comment 2 Tilman Keskinoz freebsd_committer freebsd_triage 2014-09-06 20:29:46 UTC
*** Bug 193383 has been marked as a duplicate of this bug. ***
Comment 3 Tilman Keskinoz freebsd_committer freebsd_triage 2014-09-06 20:30:08 UTC
*** Bug 193377 has been marked as a duplicate of this bug. ***
Comment 4 Tilman Keskinoz freebsd_committer freebsd_triage 2014-09-06 20:30:42 UTC
*** Bug 193375 has been marked as a duplicate of this bug. ***
Comment 5 Tilman Keskinoz freebsd_committer freebsd_triage 2014-09-06 20:31:03 UTC
*** Bug 193387 has been marked as a duplicate of this bug. ***
Comment 6 Tilman Keskinoz freebsd_committer freebsd_triage 2014-09-06 20:31:21 UTC
*** Bug 193384 has been marked as a duplicate of this bug. ***
Comment 7 Tilman Keskinoz freebsd_committer freebsd_triage 2014-09-06 20:31:39 UTC
*** Bug 193379 has been marked as a duplicate of this bug. ***
Comment 8 Tilman Keskinoz freebsd_committer freebsd_triage 2014-09-06 20:31:55 UTC
*** Bug 193374 has been marked as a duplicate of this bug. ***
Comment 9 Tilman Keskinoz freebsd_committer freebsd_triage 2014-09-06 20:34:56 UTC
You have submitted 10 PRs with similar backtraces.

It looks like there is something wrong with your hardware.

Please verify it is not bad RAM etc by e.g. reproducing the issue on different hardware
Comment 10 sasamotikomi 2014-09-07 00:44:23 UTC
I already reproduce it on different hardware, I just mount my HDD on different PC with FreeBSD 10 (amd64) I try do some manipulation( of course I check my HDD nothing wrong with hardware)and got kernel panic, probably something wrong with two my folder (/usr/ports/ and /usr/src/) and one installed package(kdelibs4) when i try compilate/update/remove/rewrite it, I got Kernel panic, i do not know why here similar backtraces here is differents bug: 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193374 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193372
Look like old fuse panic bug.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193379
openjdk panic bug reprodure only when I use  java aplication
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193387
Panic only sometimes, more often just rebooting.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193377
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193380
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193383
Duplicate of that bug need just rename it properly( I really sorry, what post so much similar bug, not into one.) 
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193375
Comment 11 sasamotikomi 2014-09-07 00:59:13 UTC
Before I just like update my ports every 1-2 week and, look like one of realize somebody do one commit without installer folder PREFIX='' or WRKDIRPREFIX=''this is only a guess, it broke my system, when 10.1 is out I try new fresh reinstall, but "bug" still exit and I think need trap or verification, better "segmentation fault core dumped", than kernel panic and reboot.
Comment 12 Adrian Chadd freebsd_committer freebsd_triage 2014-09-07 02:19:40 UTC
You need to provide the full backtrace, not just the instruction pointer like that. The core.txt file provides a lot of useful information, can you please just attach it to the bug report?


-a
Comment 13 sasamotikomi 2014-09-11 06:17:44 UTC
(In reply to Adrian Chadd from comment #12)
> You need to provide the full backtrace, not just the instruction pointer
> like that. The core.txt file provides a lot of useful information, can you
> please just attach it to the bug report?
> 
> 
> -a

Probably, it's too much for attachments, here is link to core.txt.0-33:

https://mega.co.nz/#!h1IVibzQ!PZmIASjE4qCwThA8IOQiIQfhcUhSJCuLh6YmiVmkMzY

I can add it all as attachment, if it's requested, or need only 34?
Comment 14 Jan Beich freebsd_committer freebsd_triage 2014-09-11 11:01:08 UTC
After a quick look

core.txt.{21..33} are part of bug 193376 and *maybe* similar to bug 183417.
core.txt.{11,12,15,18} are part of bug 193367.
core.txt.{8,9,17} *maybe* similar to bug 146708.

core.txt.47 (bug 193377), core.txt.{37,55,58,59} (bug 193379), core.txt.{40..50} (bug 193384) are absent but *maybe* a part of bug 193376.

Firefox doesn't do a lot of unlink/rmdir calls so core.txt.34 *maybe* a part of bug 193367. Neither core.txt.34 nor "privileged instruction fault" string can be found in the archive to be sure.

comment 0 is useless as noted in bug 193374 comment 2.

(In reply to sasamotikomi from comment #13)
> Probably, it's too much for attachments, here is link to core.txt.0-33:

ZIP doesn't compress well but better attach to the relevant bugs.

$ du -Ah Core.txt.0-33_info.0-33.zip
1.4M    Core.txt.0-33_info.0-33.zip
$ tar cJf Core.txt.0-33_info.0-33.txz @Core.txt.0-33_info.0-33.zip
$ du -Ah Core.txt.0-33_info.0-33.txz
361K    Core.txt.0-33_info.0-33.txz
Comment 15 Eitan Adler freebsd_committer freebsd_triage 2018-05-20 23:53:40 UTC
For bugs matching the following conditions:
- Status == In Progress
- Assignee == "bugs@FreeBSD.org"
- Last Modified Year <= 2017

Do
- Set Status to "Open"
Comment 16 Graham Perrin freebsd_committer freebsd_triage 2022-10-17 12:17:17 UTC
Keyword: 

    crash

– in lieu of summary line prefix: 

    [panic]

* bulk change for the keyword
* summary lines may be edited manually (not in bulk). 

Keyword descriptions and search interface: 

    <https://bugs.freebsd.org/bugzilla/describekeywords.cgi>