search for: ksymoop

Hi all, Can anyone point to some documentation on the recommended way to capture and process ksymoops for Centos 4.3? Many thanks Daveh

Hello! I got oops after about 3 hours of uptime. Load was about 1,5. This is output of ksymoops after forced reboot if it helps someone. :-) ksymoops 2.4.0 on i686 2.4.14-pre8. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.14-pre8/ (default) -m /boot/System.map-2.4.14-pre8 (default) Warning (compare_maps): mismat...

...s under quite decent loads, and they are occassionally crashing. I've been logging console messages recently in an effort to find the cause, and some appear to be related to I perused your lists and found the message I'm replying to. If you don't mind, I've included messages and ksymoops from two crashes that I had recently. Both were different. I'm not sure if you have fixes for them in the new kernel, so I'll be upgrading a few machines tonight. I'm running 2.6.10 with the "data=journal" mount option. Is that the best / safest option for running with MyS...

Hello, Over the last month or so, I've noticed the following error showing up repeatedly in my system logs under kernel 2.4.18-ac3 and more recently under 2.4.19-rc1: EXT3-fs error (device ide0(3,3)) in ext3_new_inode: error 28 I've now been able to capture the following Oops before the system went down entirely: Assertion failure in do_get_write_access() at transaction.c:611:

...this.. The system was usuable, but not very. If I tried to access the ext3 volume, it would hang. Reboot hung too, complaining about too many open files. Any ideas? I have no idea what triggered it; this is a big file/web/mail server, with all of that on the ext3 volume. And I've never run ksymoops before, but I think I did it right. - Josh Assertion failure in do_get_write_access() at transaction.c:609: "!(((jh2bh(jh)) ->b_state & (1UL << BH_Lock)) != 0)" invalid operand: 0000 CPU: 1 EIP: 0010:[<e094e941>] Not tainted EFLAGS: 00010286 eax: 00000078...

...nother oops, which looks suspiciously similiar to the one i posted some days ago (https://listman.redhat.com/pipermail/ext3-users/2002-May/003587.html). Jun 11 12:11:30 castor kernel: Assertion failure in journal_write_metadata_buffer() at journal.c:406: "buffer_jdirty(jh2bh(jh_in))" ksymoops 0.7c on i686 2.4.18-4custom. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.18-4custom/ (default) -m /boot/System.map-2.4.18-4 (specified) Warning (compare_maps): ksyms_base symbol dev_getbyhwaddr_R__ver_dev_getbyhwaddr...

...db find command, but I also had some oops crashing my box completely (it even stopped answering echo request packets!). I didn't figgure out yet how to catch those oops to a floppy or something, so if one of you knows, tell me please, so I can provide some more information. Anyway, here is one ksymoops output: ************************************ ksymoops 2.4.3 on i686 2.4.10. Options used -v /boot/vmlinuz (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.10/ (default) -m /boot/System.map (default) Warning: You did not tell me where to...

...w=1, want=1912610820, limit=4192192 Sep 25 10:46:51 gw kernel: attempt to access beyond end of device Sep 25 10:46:51 gw kernel: 09:03: rw=1, want=536870916, limit=4192192 Sep 25 10:46:51 gw kernel: Assertion failure in __journal_remove_journal_head() at journal.c:1730: "buffer_jbd(bh)" ksymoops: Error (expand_objects): cannot stat(/lib/ext3.o) for ext3 ksymoops: No such file or directory Error (expand_objects): cannot stat(/lib/jbd.o) for jbd ksymoops: No such file or directory Warning (compare_maps): mismatch on symbol partition_name , ksyms_base says c01e0cf0, System.map says c014f3e...

...copy-user-reschedule.patch dac960-enclosure-quiet.patch dma-livelock-fix.patch e100-1.5.5.tar.gz e1000-3.0.7.tar.gz eepro100-speedo-1.patch emu10k1-tone.patch exports-cleanup.patch ext3-2.4.patch finerflush.patch ide-450nx-nodma-2 ide-probe-irq-silent ipmi-kcs-2.0.patch iput-free.patch kernel.spec ksymoops-2.3.4.tar.gz linux-2.4.5.tar.gz linux-ksymoops-2.3.4-install.patch linux-ksymoops-2.3.4-nobfddep.patch ncr53c8xx-quiet.patch net-exports.patch pagecache-ac18.patch per-cpu-pages.patch pid-profiling.patch print-64gb-oops.patch ptrace-thread-signal.patch rh-changeloop.patch rpcalias.patch scsi-error...

...ut. This results in "ext3_free_inode: bit already cleared for inode XXXX" messages or the following assertion. FYI, this does not occur when using ext2. Nor does it occur when I perform the 'rm' operation across NFS rather than on the local filesystem behind nfs' back. The ksymoops output for the assertion is below. I'm gonna look into it further, just wondering if this rings any bells with any others. :) Thanks. ------ Message from syslogd@slippey at Thu Aug 2 15:19:37 2001 ... slippey kernel: Assertion failure in journal_revoke() at revoke.c line 278: "!test_an...

...on failure in __journal_remove_journal_head() at journal.c:1634: "buffer_jbd(bh)" The filesystem in question is the root filesystem. The taint was caused by the openprom module, which was the only module loaded. Please let me know if you need any further data. Regards, Sean. ksymoops 2.4.3 on sparc64 2.4.13-pre6. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.13-pre6/ (default) -m /boot/System.map-2.4.13-pre6 (default) Warning: You did not tell me where to find symbol information. I will assume that...

...tches (0.0.7a) Intel BX chipset, SCSI Disks Symbios chipset - The crashing process is the master process of "postfix" an MTA. Just before the crash all processes on that machine started to segfault in nameserver resolution (remote dns server) and after 2-3 minutes this oops happened. ksymoops 2.3.4 on i686 2.2.19. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.19/ (default) -m /boot/System.map-2.2.19 (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches t...

On Monday 03 February 2003 00:38, Karl Heyes wrote: > On Sun, 2003-02-02 at 22:48, Marc Remijn wrote: > > The only module I know about that is 'tainted' is the philips webcam > > compression module pwcx, which I forced loaded with 'insmod -f'. But > > unloading that didn't change the problem. Anyway the 'tainted' issue has > > to do with no

....19-6.2.12 + 0.0.7a + https://listman.redhat.com/pipermail/ext3-users/2001-November/002258.html (not tuned in /proc yet) + journal 4MB on each fs + 6 ext3 fs on raid1 (hda+hdc) + 1 ext3 fs on another disk not on raid1 (hdd) While untarring (tar zxf) a file that was on a ext3/raid1 onto hdd I got: ksymoops 2.3.4 on i686 2.2.19-6.2.12.g1. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.19-6.2.12.g1/ (default) -m /boot/System.map-2.2.19-6.2.12.g1 (specified) Warning (compare_ksyms_lsmod): module iBCS is in lsmod but not in k...

Hi, i am seeing a crash in ext3_new_block quiet often today on 2.2.19 0.0.7a fsck 1.21 ksymoops 2.3.4 on i686 2.2.19. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.19/ (default) -m /boot/System.map-2.2.19 (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches t...

...ter.org Hello, I applied netfilter to my openmosix-2.4.20-kernel and now I got a kernel panic. I wonder whether the error is netfilter-based or not. I think it is because the kernel panic comes directly after the netfilter message on startup. Do you know anything about this? I'll attach the ksymoops and the applied patches. Thanks Georg Wild ksymoops 2.4.8 on i686 2.4.20-openmosix-1. Options used -V (default) -K (specified) -L (specified) -O (specified) -m /usr/src/linux/System.map (default) Unable to handle kernel NULL pointer dereference at virtual address 000...

...PowerPC 7410 based systems. I am getting reports of Oops happening either during removes (rm's), or coppies (cp's). Most reports state that issuing the same command once the system boots back up, does not cause it to crash. I guess its something else leading up to the crash. Here is the ksymoops output of one of the crashes. Any input/help would be appreciated.. This is the first time using ksymoops, so let me know if I should run it with different options. Btw: Could anyone tell me what the warning line below means? Thanks.. Oops: Exception in kernel mode, sig: 4 NIP: C00803F4 XER:...

...Linux version 2.4.18 (root@gere) (gcc version 2.95.2 20000220 (Debian GNU/Linux)) #2 man maj 6 15:05:32 CEST 2002 [5.] Output of Oops.. message (if applicable) with symbolic information resolved (see Documentation/oops-tracing.txt) Eh, this is quite embarrassing. I cannot decode the oops... Ksymoops 2.4.3 just leaves the oops intact without symbolic information. System.map is in place, smbfs is compiled in-kernel (not as a module): ksymoops 2.4.3 on i586 2.4.18. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.4.18/ (defau...

...ed kernel, latest stable is 2.4.20, although there are some interim patches which will become 2.4.21 eventually. If 2.4.20 also shows the same problem then you'll have to report it to the kernel mailing list or maintainer of the code in question. You'll need to decode the oops (above) with ksymoops to get a stack trace. You can try to isolate certain things, ices (in your case) mainly reads from dsp and writes on network sockets. The encoding part of ices is very unlikely to cause the panic but the ksymoops output is more likely to indicate the area of concern. If you need more help email...

VFS: brelse: Trying to free free buffer buffer layer error at fs/buffer.c:1182 Pass this trace through ksymoops for reporting Call Trace: [<c01468f0>] [<c0146aa9>] [<c0146b57>] [<c0146b84>] [<c0175a17>] [<c023cbfa>] [<c023d2f1>] [<c0175c90>] [<c01728e9>] [<c01ad7d6>] [<c014d215>] [<c0154c68>] [<c0154f79>] [<c015512...