Yeah, I'd have to agree here, not on a mainframe (it would have been identified by the hardware), but also, SIGBUS can happen when you get an invalid address as well as a SEGV, especially on architectures where there are whole chunks of memory you're not allowed to execute, for example. I've seen lots of SIGBUSes in my day, but never bad Ram that wasn't already identified.
Eric, I'll start up my s390x now and try it out. ---------------------------- Jim McDonough IBM Linux Technology Center Samba Team 6 Minuteman Drive Scarborough, ME 04074 USA [EMAIL PROTECTED] [EMAIL PROTECTED] Phone: (207) 885-5565 IBM tie-line: 776-9984 "Eric Wilson" <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 05/25/04 03:57 PM Please respond to ewilson To "Gerald (Jerry) Carter" <[EMAIL PROTECTED]> cc [EMAIL PROTECTED] Subject Re: [Samba] nmbd crash on z/800 64 bit RHEL v 3.0 Jerry; No updates were available via up2date. Bad RAM? On a mainframe? The RAM is virtual, and shared between 9 instances. Wouldn't it be unlikley only nmbd on this particular instance of nine would see bad RAM. Cheers; E! ----------------- Eric Wilson "There is nothing more frightful than ignorance in action." -Johann von Goethe, German Playwright 1749-1832 > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Eric Wilson wrote: > | Ping 2 - Any chance anyone may have seen this before? > | > |>[2004/05/17 15:58:16, 0] lib/fault.c:fault_report(36) > |> =============================================================== > |>[2004/05/17 15:58:16, 0] lib/fault.c:fault_report(37) > |> INTERNAL ERROR: Signal 7 in pid 6745 (3.0.2-6.3E) > ~ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > SIGBUS is normall an indication of bad ram. However, > I would check with RH for an update since 3.0.2 is > pretty old now just to be safe. > > |> Please read the appendix Bugs of the Samba HOWTO collection > |>[2004/05/17 15:58:16, 0] lib/fault.c:fault_report(39) > |> =============================================================== > |>[2004/05/17 15:58:16, 0] lib/util.c:smb_panic(1422) > |> PANIC: internal error > |>[2004/05/17 15:58:16, 0] lib/util.c:smb_panic(1430) > |> BACKTRACE: 14 stack frames: > |> #0 nmbd [0x155555ef642] > |> #1 nmbd [0x155555ef71e] > |> #2 [0x1ffffffe750] > > > > > > cheers, jerry > - ---------------------------------------------------------------------- > Hewlett-Packard ------------------------- http://www.hp.com > SAMBA Team ---------------------- http://www.samba.org > GnuPG Key ---- http://www.plainjoe.org/gpg_public.asc > "...a hundred billion castaways looking for a home." ----------- Sting > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.4 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFAs6LNIR7qMdg1EfYRAjEYAJ9lKP8KHPHfUseT+pNPChCAGIYAcACfQXad > ZuwbnNMWzN4gKBVx1+Gn+RU= > =zWrq > -----END PGP SIGNATURE----- > -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba -- To unsubscribe from this list go to the following URL and read the instructions: http://lists.samba.org/mailman/listinfo/samba
