search for: panics

Hi all. I've been trying to build some new systems, and no matter what I do, if I load the zaptel and tor2 drivers, the system panics within an hour, even with no traffic. These systems are using dual Athlon MP 2800 chips with one, two, or three T400P boards and 2 GB of system memory. I'm currently using Fedora Core 1, but I also went back to our old reliable Red Hat 7.3 and the systems still panic()ed. If I don't star...

I'm running 9.2-RC4 on a handful of desktop and server machines (both i386 and amd64). I have seen three panics (all vm_page_unwire) on one of those systems only (amd64 server) during the past week. The first two panics were triggered when shutting down the ntpd daemon (a recent development snapshot version of ntpd: 4.2.7p387). Exiting a later release (p388) has not triggered the panic. The system panicke...

I am writing a small documentation on reason(s) : why kernel panic happen !! and possible (crisp) solution(s) googling out this error throws me very hazy solutions .. if some one could suggest the possible reasons and crispy solution it would be of great documentation help to many . one great link i found was this (

rsync -Ha --link-dest=/media/4tb/bak/panic-2012-01-01 /media/2tb/bak/panic-2012-02-01 /media/4tb/bak/ root at dancer:/media/4tb/bak# ls -l panic*/home/darxus/0000_latest.jpg -rw------- 15 darxus darxus 100772 1999-09-14 21:19 panic-2011-12-20/home/darxus/0000_latest.jpg -rw------- 15 darxus darxus 100772 1999-09-14 21:19 panic-2012-01-01/home/darxus/0000_latest.jpg -rw------- 1 darxus darxus

Dear list, I have Debian Etch with Samba Version 3.0.24 configured as a PDC. Every day I get exactly 9 emails with panic action: > The Samba 'panic action' script, /usr/share/samba/panic-action, > was called for PID 4170 (). > > This means there was a problem with the program, such as a segfault. > However, the executable could not be found for process 4170. > It

...o some snags. While the installation from CD went fine, after configuring and enabling my ed0 NIC, bad things start to happen. FWIW, this machine is an ancient (hardware circa 1991, BIOS circa 1994) dual-Pentium 133 MHz machine, with EISA/PCI and onboard SCSI. So far I can reliably reproduce two panics, one appears to be a ed driver bug (based on reports of similar panics with different NICs, notably nge) and one is a filesystem corruption problem. Here's the process that I go through to reliably reproduce both problems. 1) Boot machine in multi-user mode 2) After ifconfig ed0, machine panic...

There are a couple of instances when sshd will send a message to syslog saying "Don't panic" if you are logging auth.info. I change this on my site because Big Brother monitors the logs and freaks out when it sees the word panic. Do you think it is worth submitting a bug report to change the wording to use a word other than panic? -- Mark Keisler "Blessed is he who

Hi, all Those days, we spent some efforts to check severe error handling (panic, BUG_ON, BUG, ASSERT) in XEN. We have several round internal discussions as well as several mail threads with Keir. Below is the discussion writeup. If agreed, after review, we want to place it in XEN document folder or XEN wiki since we think it might be helpful to developers. Thanks a lot for your help! Regards,

On 03/12/2015 13:33, Jonathan Billings wrote: > On Thu, Dec 03, 2015 at 09:29:21AM +0000, Duncan Brown wrote: >> Hi All >> >> After upgrading to 7.2, I'm getting an immediate kernel panic on boot >> >> Dropping back to 3.10.0-229.20.1.el7.x86_64 and the system boots fine >> >> How can I go about diagnosing the problem here? > It'd probably

Working on the Dell R420 today, got most of it working, even the broadcom ethernet cards! However, I get the following when I reboot the system: Syncing disks, vnodes remaining...4 Sleeping thread (tid 100107, pid 9) owns a non-sleepable lock KDB: stack backtrace of thread 100107: sched_switch() at sched_switch+0x19f mi_switch() at mi_switch+0x208 sleepq_switch() at sleepq_switch+0xfc

Hi, I'm experiencing "frequent" kernel panics on a system with Asterisk 1.4.26.3. There is no core dump, "just" a kernel panic. This is the only data I could copy from the screen: EIP: 0060: [<f8e248b4>] Tainted: P VLI EFLAGS: 00210297 (2.6.23-gentoo-r8 #1) eax: 00000130 ebx: 00000000 ecx: 00220028 edx: 00000978 esi: 346e5802...

On 03/12/2015 13:54, Jonathan Billings wrote: > On Thu, Dec 03, 2015 at 01:44:47PM +0000, Duncan Brown wrote: >> The last message before it is "switching to clocksource hpet" >> >> Then the panic scrolls by >> >> I've no idea if that counts as later or not > It's unlikely to be a panic related to your hardware clock (HPET = > High Precision

---- I have a bunch of these in my log... Was wondering if anyone had seen them before and what the cause might be? Thanks... Oct 1 03:25:15 Ishtar smbd[23925]: [2011/10/01 03:25:15, 0] lib/util.c:1468(smb_panic) Oct 1 03:25:15 Ishtar smbd[23925]: PANIC (pid 23925): internal error Oct 1 03:25:15 Ishtar smbd[23925]: #1 /usr/sbin/smbd(smb_panic+0x55) [0x7f7120093134] Oct 1 03:25:15

...booting, or short after a boot, while trying to cvsup the ports-tree). Also tried a few 4.7-Stable snapshots, but also had the same problem. It was not until 4.7-Release that it worked without any problem. But when I tried to upgrade to 4.8-Stable and build the GENERIC and my own kernel, the kernel panics returned. Anyone got any ideas? I already checked my memory and harddisks and they seem fine. (and also 4.7-Release hasn't got any problems -> could even cvsup the complete sources and build world) Thanks in advance for any help Fatal trap 12: page fault while in kernel mode fault virtua...

This may or may not be ext3 related but I am trying to find any pointers which might help me. I got a number of HP Proliant DL380 g5 with a P400 controller and also two qla2400 cards. The OS is RedHat EL4 U5 x86_64. Every time during reboot these systems panic after the last umount and I believe before the cciss driver is getting unloaded. The last messages I am able to see are: md: stopping

Box with fresh RELENG_7 panic under heavy network load (more than 50k connections). This panics seems to be senfile(2) related, because when sendfile disabled in nginx, I can't reproduce the problem. Backtrace in all cases like this: # kgdb kernel /spool/crash/vmcore.1 GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General...

> -----Original Message----- > From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On > Behalf Of Johnny Hughes > Sent: den 26 maj 2016 14:30 > To: centos at centos.org > Subject: Re: [CentOS] Kernel panic on 6.8 release with kernel-2.6.32- > 642.el6.x86_64 > > If lockd is failling to start: > > https://bugs.centos.org/view.php?id=10927

...#39;s to ask for help in figuring out a kernel panic I am running into. The machine in question has run fine without problem for quite some time, running as a database/web server. It has an identical (hardware) twin that performs essentially the same functions, but which has not had any kernel panics. The only recent change I've made of note before the kernel panics started, is to set up an NFS share on both of those machines, each of which is mounted by three other machines. It seems like whenever there is any more than a negligible amount of activity over those NFS shares, that one m...

This is probably unreproducible, but I just got a panic whilst scrubbing a simple mirrored pool on scxe snv124. Evidently on of the disks went offline for some reason and shortly thereafter the panic happened. I have the dump and the /var/adm/messages containing the trace. Is there any point in submitting a bug report? The panic starts with: Jan 19 13:27:13 host6

My system (a laptop with ZFS root and boot, SNV 64A) on which I was trying Opensolaris now has the zpool-related kernel panic reboot loop. Booting into failsafe mode or another solaris installation and attempting: ''zpool import -F rootpool'' results in a kernel panic and reboot. A search shows this type of kernel panic has been discussed on this forum over the last year.