similar to: CentOS 7: BUG: unable to handle kernel NULL pointer dereference

Displaying 20 results from an estimated 2000 matches similar to: "CentOS 7: BUG: unable to handle kernel NULL pointer dereference"

2017 Jan 10
0
CentOS 7: BUG: unable to handle kernel NULL pointer dereference
Am 10.01.2017 um 19:51 schrieb m.roth at 5-cent.us: > We've just started seeing this. Anyone else? > > reason: BUG: unable to handle kernel NULL pointer dereference at > 00000000000000b8 > component: kernel > count: 1 > analyzer: vmcore > architecture: x86_64 > event_log: > kernel: 3.10.0-327.18.2.el7.x86_64 >
2016 Aug 31
8
[PATCH 0/2] supermin: use /etc/os-release
Hi, let's make supermin use /etc/os-release as primary source instead of the various release files in /etc; apparently distros (e.g. openSUSE) are starting removing them. Thanks, Pino Toscano (2): Add simple handling of /etc/os-release Use os-release to detect the distro src/Makefile.am | 3 +++ src/dpkg.ml | 3 ++- src/os_release.ml | 78
2018 Oct 02
1
[supermin PATCH] rpm: generalize openSUSE support
It seems that all the newer versions of openSUSE have an 'opensuse-' prefix in their distro ID; hence, check for that prefix at once, keeping compatibility for the old "opensuse" ID. Followup of commit 0668b2d64abef0724219480a3d7fc16b8dd1e68f. --- src/ph_rpm.ml | 3 ++- tests/test-harder.sh | 2 +- 2 files changed, 3 insertions(+), 2 deletions(-) diff --git
2018 Oct 01
2
[supermin PATCH] rpm: support openSUSE Leap 15
openSUSE Leap 15 has "opensuse-leap" as ID in os-release, so add it both in the detection code of the RPM handler, and in test-harder.sh. --- src/ph_rpm.ml | 2 +- tests/test-harder.sh | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/ph_rpm.ml b/src/ph_rpm.ml index b0a5eb2..3caa38e 100644 --- a/src/ph_rpm.ml +++ b/src/ph_rpm.ml @@ -40,7 +40,7 @@ let
2006 Mar 27
2
How to disable event_log?
Hi, how can I disable event_log in order to reduce hard disk activity? I can't find any hints in conf files. Must I hack the source code or even use brutal methods like creating a dir called event_log in the log dir, in order to prevent asterisk from creating an event_log file? (Just chmod a-w event_log does not work, unfortunately.) Thanks for any hints! Roger.
2017 Sep 01
0
[supermin][PATCH] os-release: use ID_LIKE as a fallback for SUSE detection
SUSE distros all have in common suse in ID_LIKE field. The ID field could be varying and is even set to 'Dummy' when building the packages. If the usual values for openSUSE/SLE can't be found in ID, try with ID_LIKE. --- src/os_release.ml | 10 +++++++++- src/os_release.mli | 7 +++++++ src/ph_rpm.ml | 1 + 3 files changed, 17 insertions(+), 1 deletion(-) diff --git
2017 Sep 01
0
[supermin][PATCH v2] os-release: use ID_LIKE as a fallback for SUSE detection
SUSE distros all have in common suse in ID_LIKE field. The ID field could be varying and is even set to 'Dummy' when building the packages. If the usual values for openSUSE/SLE can't be found in ID, try with ID_LIKE. --- Diff with v1: * Use Utils.string_split rather than too recent String.split_on_char src/os_release.ml | 10 +++++++++- src/os_release.mli | 7 +++++++
2003 Nov 05
2
asterisk nightmare from hell!
Ok for those of you all up in a tizzy over my subject line, please don't take it literally because I'm certainly not saying that asterisk is the problem here. I just got a little nightmare problem that I need a bit of help figuring out. I installed an asterisk system a few months ago for a client, it has run almost flawlessly with the exception of a few small glitches. However, I got a
2014 Nov 28
2
SEtroubleshootd Crashing
When running Node.js through Phusion Passenger on Centos 6.5 ( Linux 2.6.32-431.23.3.el6.x86_64 #1 SMP Thu Jul 31 17:20:51 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux), with SELinux enabled in permissive mode we receive a large number of entries in the audit.log and setroubleshootd randomly crashes with the following error, We have resolved the selinux alerts by following the troubleshooting steps
2012 Jan 17
1
Errors in /var/spool/mail/root
CentOS Experts, I am receiving the following in /var/spool/mail/root. I cleaned out the file and then rebooted and the same errors came back. Is it possible to analyze the data and advise if there is an issue with my system? This is a completely fresh install. From user at localhost.srv.net Tue Jan 17 08:11:56 2012 Return-Path: <user at localhost.srv.net> X-Original-To: root at
2016 Aug 31
0
[PATCH 2/2] Use os-release to detect the distro
Check the ID field in /etc/os-release on the current system, before checking for the other old-style release-/version-like files in /etc. Some distributions (openSUSE Thumbleweed) are starting to remove them, breaking the supermin detection. --- src/dpkg.ml | 3 ++- src/pacman.ml | 5 +++-- src/rpm.ml | 15 +++++++++------ 3 files changed, 14 insertions(+), 9 deletions(-) diff --git
2006 Jun 09
3
Trouble getting SMS working
Hi, I have been trying to get my asterisk box to send SMS's to my Panasonic dect phone via a Linksys pap2. I believe I have the message centers setup correctly between * and the phone. The pap2 is configured to only use G711a. The Asterisk version is 1.0.7. In my /etc/asterisk/extensions.conf I have [smsphone] exten = 199,1,Goto(smsmorx,${CALLERIDNUM},1) [smsmorx] exten =
2017 Jan 09
1
Validated BCM4321 chip on CentOS 7.3
Hey All! I've validated the Broadcom chipset 4321 on 7.3 with the latest 64-bit Broadcom driver(6_30_223_271) if someone with edit capability can update the table please: https://wiki.centos.org/HowTos/Laptops/Wireless/Broadcom https://wiki.centos .org/HowTos/Laptops/Wireless/Broadcom#head-5b5da35ce5cedf2cddd2e815739a64758e341ab8 Table entry: Chip: BCM4321 EL version: CentOS 7.3 Kernel:
2007 Mar 27
1
Erased log files
People, I've erased the *messages* and *full *files in /var/log/asterisk/. I've already created other files and changed the owner, etc, and permissions: *-rw-r--r-- 1 asterisk asterisk 0 Mar 2 16:01 event_log -rw-r--r-- 1 asterisk asterisk 1514385 Mar 27 18:15 full -rw-r--r-- 1 asterisk asterisk 396170 Mar 27 18:20 messages -rw-r--r-- 1 asterisk asterisk 1102 Mar 3 18:08
2018 Jan 12
3
[Bug 104609] New: [G96, 9500 GT] Removing nouveau module results in BUG: unable to handle kernel NULL pointer dereference at 00000000000000b8
https://bugs.freedesktop.org/show_bug.cgi?id=104609 Bug ID: 104609 Summary: [G96, 9500 GT] Removing nouveau module results in BUG: unable to handle kernel NULL pointer dereference at 00000000000000b8 Product: Mesa Version: unspecified Hardware: All OS: All Status: NEW
2014 Dec 01
2
SEtroubleshootd Crashing
Thanks Could you please clarify, which version libxml is broken and has there been a newer version released that will fix it. -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of Daniel J Walsh Sent: 01 December 2014 14:58 To: CentOS mailing list Subject: Re: [CentOS] SEtroubleshootd Crashing This seems to be a problem with an updated
2004 Dec 02
2
Asterisk with SMS
Hi all, I am trying to setup the SMS of Asterisk. I have a Siemens SMS enable fixed phone which connects to my Asterisk through PSTN. Currently, I can use my fixed phone to edit and send messages to the Asterisk. However, I cannot make my Asterisk to send messages to the fixed phone. The SMS command displays TX and RX records, hang for a while and then stops with non-zero exits. I read
2010 Feb 10
1
asterisk sudden restart - 1.4.18.1
Hi, Asterisk got stopped this morning after 20 minutes and phones went to 'No Service' and then got started automatically after 20 min, as I could see in the full log that asterisk got started at so and so time: [Feb 10 08:29:31] VERBOSE[31013] logger.c: Asterisk Event Logger Started /var/log/asterisk/event_log [Feb 10 08:29:31] VERBOSE[31013] logger.c: Asterisk Dynamic Loader Starting:
2009 Feb 27
1
Realtime mapping for 'queue_log' found to engine 'odbc', but the engine is not available
Hi, I am trying to log queue_log to odbc (MS SQL) I have res_odbc.conf configured and modules.conf have preload => res_odbc.so preload => res_config_odbc.so extconfig.conf has queue_log => odbc,asterisk. When I start asterisk I get the following messages. The important one being: Realtime mapping for 'queue_log' found to engine 'odbc', but the engine is not available
2009 Jan 12
1
problem with dahdi and meetme
Hi to all. I'm trying to use meetme on asterisk 1.4.22.1. On a debian i've compiled (as i need h323 support) openh323_v1_18_0 pwlib_v1_10_0 dahdi-linux-2.1.0.3 dahdi-tools-2.1.0.2 asterisk-1.4.22.1 All works fine, dahdi status is: asterik:/data/programmi# /etc/init.d/dahdi status ### Span 1: DAHDI_DUMMY/1 "DAHDI_DUMMY/1 (source: RTC) 1" (MASTER) asterik:/data/programmi#