Oops in 2.2.17
Using 2.2.17 kernel that is standard other than the bridging firewall patch, this Oops happened while setting up tripwire - it was scanning the disk and then locked up. As its purely a remote machine, I am only able to go off of the logs in syslogd. Below is the ksymoops report. If im leaving anything out, please let me know. While its somewhat relevant, it will also oops when doing a shutdown -h but I added the option for buggy chipsets, but havnt tested it, as its a server and shouldnt really be shutdown anyhow. Ksymoops report: ksymoops 2.3.4 on i586 2.2.17. Options used -v /usr/src/linux/vmlinux (specified) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.17/ (default) -m /usr/src/linux/System.map (default) Jan 20 13:14:59 Venus kernel: current->tss.cr3 = 00101000, %%cr3 = 00101000 Jan 20 13:14:59 Venus kernel: *pde = Jan 20 13:14:59 Venus kernel: Oops: Jan 20 13:14:59 Venus kernel: CPU:0 Jan 20 13:14:59 Venus kernel: EIP:0010:[show_registers+653/704] Jan 20 13:14:59 Venus kernel: EFLAGS: 00010046 Jan 20 13:14:59 Venus kernel: eax: ebx: ecx: e86e2fe2 edx: c1c78000 Jan 20 13:14:59 Venus kernel: esi: 28181f68 edi: c1fb ebp: c280 esp: c1faff2c Jan 20 13:14:59 Venus kernel: ds: 0018 es: 0018 ss: 0018 Jan 20 13:14:59 Venus kernel: Process kswapd (pid: 5, process nr: 5, stackpage=c1faf000) Jan 20 13:14:59 Venus kernel: Stack: e86e2fe2 0e00 c0206d2e c01bee9a c1fae1c1 0e00 c1faffd4 c1fae000 Jan 20 13:14:59 Venus kernel:c021961c c021961c e86e2fe2 00010286 e86e2fe3 c300 c0108d58 c1faffb0 Jan 20 13:14:59 Venus kernel:c01bb776 c01bd16e c010dfc0 c01bd16e c1faffb0 Jan 20 13:15:00 Venus kernel: Call Trace: [tvecs+7194/13344] [] [die+48/56] [error_table+2646/9568] [error_table+9294/9568] [do_page_fault+708/944] [error_table+9294/9568] Jan 20 13:15:00 Venus kernel: Code: 8a 04 0b 89 44 24 38 50 68 6e b7 1b c0 e8 91 9d 00 00 83 c4 Using defaults from ksymoops -t elf32-i386 -a i386 Code; Before first symbol <_EIP>: Code; Before first symbol 0: 8a 04 0b mov(%ebx,%ecx,1),%al Code; 0003 Before first symbol 3: 89 44 24 38 mov%eax,0x38(%esp,1) Code; 0007 Before first symbol 7: 50push %eax Code; 0008 Before first symbol 8: 68 6e b7 1b c0push $0xc01bb76e Code; 000d Before first symbol d: e8 91 9d 00 00call 9da3 <_EIP+0x9da3> 9da3 Before first symbol Code; 0012 Before first symbol 12: 83 c4 00 add$0x0,%esp System information: [syonic@Venus syonic]$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 5 model : 2 model name : Pentium 75 - 200 stepping : 5 cpu MHz : 100.230 fdiv_bug : no hlt_bug : no sep_bug : no f00f_bug : yes coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr mce cx8 bogomips : 199.88 Its a SOYO 5ED board with ETEQ 82C662X chipset (the manual is available at http://www.soyousa.com/manuals/586new/m5ed20f.pdf if your really interested in every part of the board) The machine is serving as a firewall for my internal network. Its only been running for a few days so far with no problems. If any other information is needed at all, please let me know. I am unable to reproduce it when using tripwire again, So im not sure how to reproduce this, but I'm open to any suggestions. Also, the bridging firewall patch (which I would like to see in 2.4) is available at http://ac2i.tzo.com/bridge_filter/linux_brfw_2.2.17.diff in case your wondering what I've done to my kernel, but I dont think its too relevant, but im not a kernel developer. Again, let me know if theres anything I can do to further trace this. -- James Brents [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Oops in 2.2.17
Using 2.2.17 kernel that is standard other than the bridging firewall patch, this Oops happened while setting up tripwire - it was scanning the disk and then locked up. As its purely a remote machine, I am only able to go off of the logs in syslogd. Below is the ksymoops report. If im leaving anything out, please let me know. While its somewhat relevant, it will also oops when doing a shutdown -h but I added the option for buggy chipsets, but havnt tested it, as its a server and shouldnt really be shutdown anyhow. Ksymoops report: ksymoops 2.3.4 on i586 2.2.17. Options used -v /usr/src/linux/vmlinux (specified) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.17/ (default) -m /usr/src/linux/System.map (default) Jan 20 13:14:59 Venus kernel: current-tss.cr3 = 00101000, %%cr3 = 00101000 Jan 20 13:14:59 Venus kernel: *pde = Jan 20 13:14:59 Venus kernel: Oops: Jan 20 13:14:59 Venus kernel: CPU:0 Jan 20 13:14:59 Venus kernel: EIP:0010:[show_registers+653/704] Jan 20 13:14:59 Venus kernel: EFLAGS: 00010046 Jan 20 13:14:59 Venus kernel: eax: ebx: ecx: e86e2fe2 edx: c1c78000 Jan 20 13:14:59 Venus kernel: esi: 28181f68 edi: c1fb ebp: c280 esp: c1faff2c Jan 20 13:14:59 Venus kernel: ds: 0018 es: 0018 ss: 0018 Jan 20 13:14:59 Venus kernel: Process kswapd (pid: 5, process nr: 5, stackpage=c1faf000) Jan 20 13:14:59 Venus kernel: Stack: e86e2fe2 0e00 c0206d2e c01bee9a c1fae1c1 0e00 c1faffd4 c1fae000 Jan 20 13:14:59 Venus kernel:c021961c c021961c e86e2fe2 00010286 e86e2fe3 c300 c0108d58 c1faffb0 Jan 20 13:14:59 Venus kernel:c01bb776 c01bd16e c010dfc0 c01bd16e c1faffb0 Jan 20 13:15:00 Venus kernel: Call Trace: [tvecs+7194/13344] [c300] [die+48/56] [error_table+2646/9568] [error_table+9294/9568] [do_page_fault+708/944] [error_table+9294/9568] Jan 20 13:15:00 Venus kernel: Code: 8a 04 0b 89 44 24 38 50 68 6e b7 1b c0 e8 91 9d 00 00 83 c4 Using defaults from ksymoops -t elf32-i386 -a i386 Code; Before first symbol _EIP: Code; Before first symbol 0: 8a 04 0b mov(%ebx,%ecx,1),%al Code; 0003 Before first symbol 3: 89 44 24 38 mov%eax,0x38(%esp,1) Code; 0007 Before first symbol 7: 50push %eax Code; 0008 Before first symbol 8: 68 6e b7 1b c0push $0xc01bb76e Code; 000d Before first symbol d: e8 91 9d 00 00call 9da3 _EIP+0x9da3 9da3 Before first symbol Code; 0012 Before first symbol 12: 83 c4 00 add$0x0,%esp System information: [syonic@Venus syonic]$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 5 model : 2 model name : Pentium 75 - 200 stepping : 5 cpu MHz : 100.230 fdiv_bug : no hlt_bug : no sep_bug : no f00f_bug : yes coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr mce cx8 bogomips : 199.88 Its a SOYO 5ED board with ETEQ 82C662X chipset (the manual is available at http://www.soyousa.com/manuals/586new/m5ed20f.pdf if your really interested in every part of the board) The machine is serving as a firewall for my internal network. Its only been running for a few days so far with no problems. If any other information is needed at all, please let me know. I am unable to reproduce it when using tripwire again, So im not sure how to reproduce this, but I'm open to any suggestions. Also, the bridging firewall patch (which I would like to see in 2.4) is available at http://ac2i.tzo.com/bridge_filter/linux_brfw_2.2.17.diff in case your wondering what I've done to my kernel, but I dont think its too relevant, but im not a kernel developer. Again, let me know if theres anything I can do to further trace this. -- James Brents [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Difficult to diagnose oops in 2.2.17, details at www.aeinet.com/oops
(Please cc: me directly if you so choose, I am not subscribed to l-k at the moment. Thanks. Otherwise, I'll follow the thread in a l-k archive.) All, I'd like to enlist your help in diagnosing a series of oopsen over the last eight weeks. I didn't start tracking the problem in detail until a week ago, but you can now find the log files, ksymoops output, SysRq dumps, and other files at: http://www.aeinet.com/oops Basically, the system is a stock Debian 2.2 (potato) install on an Intel system, with a custom compiled kernel. The motherboard is a dual-cpu Intel N440BX server board with single PIII (katmai) 500 cpu, 256 MB RAM, and is very lightly loaded most of the time. It had been stable for approximately nine months on 2.2.14, then began to exhibit a variety of strange oops and crashes about eight weeks ago. Generally, the oops would result in a hard system lock up, where only a reset would return the box to normal. Some of these oops made it into /var/log/messages, and ksymoops was run on that. The output is one of the links at the URL above. The average uptime at this point was about an hour or two, though sometimes it was only five minutes. My first guess was hardware, specifically memory. Running memcheck86 on the system found serious faults, so the memory was replaced with a new module that passed memcheck86 with flying colors. The result was that the system would stay up approximately one or two days at a time, but the oops and lockups were still occurring. Since it was taking about 15 minutes to reboot, I installed and converted to reiserfs (3.5.57), and upgraded to 2.2.17 at the same time. The kernel is now 2.2.17 + crypto (10) + reiserfs (3.5.57) + badram (3.3). No change in the symptoms happened, and I was resetting the system manually every day or so. Fast forward to about a week ago, when I decided that I should seek community help. As an incentive, I'll ship one six-pack of beer anywhere in the world to the first person who solves this problem permanently. Brand of beer is negotiable--but I only have access to cheap American beer :) See the web log for the (unsuccessful) efforts taken so far suggested by the helpful people at #linpeople and #kernelnewbies on irc.debian.org. I still suspect it's hardware, though I have no idea what it might be now. Christmas break brings a new system to replace it, so it will be moot by then, but I'm still determined to get to the bottom of it anyway. Thanks for your time. Johnathan Corgan Atlas Enterprises Internet - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Difficult to diagnose oops in 2.2.17, details at www.aeinet.com/oops
(Please cc: me directly if you so choose, I am not subscribed to l-k at the moment. Thanks. Otherwise, I'll follow the thread in a l-k archive.) All, I'd like to enlist your help in diagnosing a series of oopsen over the last eight weeks. I didn't start tracking the problem in detail until a week ago, but you can now find the log files, ksymoops output, SysRq dumps, and other files at: http://www.aeinet.com/oops Basically, the system is a stock Debian 2.2 (potato) install on an Intel system, with a custom compiled kernel. The motherboard is a dual-cpu Intel N440BX server board with single PIII (katmai) 500 cpu, 256 MB RAM, and is very lightly loaded most of the time. It had been stable for approximately nine months on 2.2.14, then began to exhibit a variety of strange oops and crashes about eight weeks ago. Generally, the oops would result in a hard system lock up, where only a reset would return the box to normal. Some of these oops made it into /var/log/messages, and ksymoops was run on that. The output is one of the links at the URL above. The average uptime at this point was about an hour or two, though sometimes it was only five minutes. My first guess was hardware, specifically memory. Running memcheck86 on the system found serious faults, so the memory was replaced with a new module that passed memcheck86 with flying colors. The result was that the system would stay up approximately one or two days at a time, but the oops and lockups were still occurring. Since it was taking about 15 minutes to reboot, I installed and converted to reiserfs (3.5.57), and upgraded to 2.2.17 at the same time. The kernel is now 2.2.17 + crypto (10) + reiserfs (3.5.57) + badram (3.3). No change in the symptoms happened, and I was resetting the system manually every day or so. Fast forward to about a week ago, when I decided that I should seek community help. As an incentive, I'll ship one six-pack of beer anywhere in the world to the first person who solves this problem permanently. Brand of beer is negotiable--but I only have access to cheap American beer :) See the web log for the (unsuccessful) efforts taken so far suggested by the helpful people at #linpeople and #kernelnewbies on irc.debian.org. I still suspect it's hardware, though I have no idea what it might be now. Christmas break brings a new system to replace it, so it will be moot by then, but I'm still determined to get to the bottom of it anyway. Thanks for your time. Johnathan Corgan Atlas Enterprises Internet - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Reproducable oops in 2.2.17 and 2.2.18pre21
On Fri, 17 Nov 2000 14:49:38 Rasmus Andersen wrote: > Hi. > > I get an oops reproducably with 2.2.17 and 2.2.18pre21 on a stock RH 6.2 > system. I cannot trigger it with the RH supplied kernel (2.2.14-5.0). > I also got it with 2.2.17pre10 which prompted me to upgrade the kernel. > I initially suspected bad RAM but have exchanged the RAM with memtest86'ed > RAM for no improvement. > > What I do: I try to back the system up with tar zcvf /var/backup.tar.gz > -X exclude /lib /sbin /var /bin /etc /boot /home /root /usr > (the exclude file contains the path of the file itself, i.e., > /var/ backup.tar.gz). > Exclude /dev and /proc also, /lost+found if you have it, and /mnt if you only want that drive. Perhaps things like /proc/kcore make trouble... -- Juan Antonio Magallon Lacarta #> cd /pub mailto:[EMAIL PROTECTED] #> more beer - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Reproducable oops in 2.2.17 and 2.2.18pre21
On Fri, 17 Nov 2000, Rasmus Andersen wrote: > Hi. > > I get an oops reproducably with 2.2.17 and 2.2.18pre21 on a stock RH 6.2 > system. I cannot trigger it with the RH supplied kernel (2.2.14-5.0). > I also got it with 2.2.17pre10 which prompted me to upgrade the kernel. > I initially suspected bad RAM but have exchanged the RAM with memtest86'ed > RAM for no improvement. > Code; c0121b43 <__get_free_pages+1eb/2b8> > <_EIP>: > Code; c0121b43 <__get_free_pages+1eb/2b8> <= >0: 89 70 04 mov%esi,0x4(%eax) <= > Code; c0121b46 <__get_free_pages+1ee/2b8> >3: 89 e8 mov%ebp,%eax > Code; c0121b48 <__get_free_pages+1f0/2b8> >5: 2b 05 ec da 1d c0 sub0xc01ddaec,%eax > Code; c0121b4e <__get_free_pages+1f6/2b8> >b: 8d 04 40 lea(%eax,%eax,2),%eax > Code; c0121b51 <__get_free_pages+1f9/2b8> >e: 89 c2 mov%eax,%edx > Code; c0121b53 <__get_free_pages+1fb/2b8> > 10: c1 e2 04 shl$0x4,%edx > Code; c0121b56 <__get_free_pages+1fe/2b8> > 13: 01 00 add%eax,(%eax) Which compiler are you using? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Reproducable oops in 2.2.17 and 2.2.18pre21
Hi. I get an oops reproducably with 2.2.17 and 2.2.18pre21 on a stock RH 6.2 system. I cannot trigger it with the RH supplied kernel (2.2.14-5.0). I also got it with 2.2.17pre10 which prompted me to upgrade the kernel. I initially suspected bad RAM but have exchanged the RAM with memtest86'ed RAM for no improvement. What I do: I try to back the system up with tar zcvf /var/backup.tar.gz -X exclude /lib /sbin /var /bin /etc /boot /home /root /usr (the exclude file contains the path of the file itself, i.e., /var/ backup.tar.gz). Running 2.2.17 I got the following oops during the backup, i.e., tar had not finished yet (the exact place in the backup process varies): ksymoops 0.7c on i586 2.2.17. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.17/ (default) -m /boot/System.map (specified) Warning (compare_maps): ksyms_base symbol module_list_R__ver_module_list not found in System.map. Ignoring ksyms_base entry Nov 13 18:15:05 firewall kernel: Unable to handle kernel NULL pointer dereference at virtual address 0004 Nov 13 18:15:05 firewall kernel: current->tss.cr3 = 07259000, %cr3 = 07259000 Nov 13 18:15:05 firewall kernel: *pde = Nov 13 18:15:05 firewall kernel: Oops: 0002 Nov 13 18:15:05 firewall kernel: CPU:0 Nov 13 18:15:05 firewall kernel: EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 Nov 13 18:15:05 firewall kernel: EFLAGS: 00010087 Nov 13 18:15:05 firewall kernel: eax: ebx: 0001 ecx: edx: Nov 13 18:15:05 firewall kernel: esi: c02009f0 edi: 1000 ebp: c022a790 esp: c725bd4c Nov 13 18:15:05 firewall kernel: ds: 0018 es: 0018 ss: 0018 Nov 13 18:15:05 firewall kernel: Process bzip2 (pid: 1327, process nr: 23, stackpage=c725b000) Nov 13 18:15:05 firewall kernel: Stack: 1000 0306 0001 000a 0202 0306 16cf Nov 13 18:15:05 firewall kernel:1000 c0126ff4 0003 1000 0306 0002 c10fd3c0 Nov 13 18:15:05 firewall kernel:c06c1000 c01261e8 1000 16cf 1000 0306 0002 c10fd3c0 Nov 13 18:15:05 firewall kernel: Call Trace: [] [] [] [] [] [] [] Nov 13 18:15:05 firewall kernel:[] [] [] [] [] [] [] [] Nov 13 18:15:05 firewall kernel:[] [] [] Nov 13 18:15:05 firewall kernel: Code: 89 70 04 89 e8 2b 05 ec da 1d c0 8d 04 40 89 c2 c1 e2 04 01 >>EIP; c0121b43 <__get_free_pages+1eb/2b8> <= Trace; c0126ff4 Trace; c01261e8 Trace; c01263c5 Trace; c0125f01 Trace; c013f74c Trace; c013fdc2 Trace; c014011b Trace; c01264ff <__brelse+13/64> Trace; c013e23e Trace; c011130e Trace; c011ae20 Trace; c011157e Trace; c0111573 Trace; c010a103 Trace; c01249cf Trace; c012483c Trace; c010923d Trace; c0109104 Code; c0121b43 <__get_free_pages+1eb/2b8> <_EIP>: Code; c0121b43 <__get_free_pages+1eb/2b8> <= 0: 89 70 04 mov%esi,0x4(%eax) <= Code; c0121b46 <__get_free_pages+1ee/2b8> 3: 89 e8 mov%ebp,%eax Code; c0121b48 <__get_free_pages+1f0/2b8> 5: 2b 05 ec da 1d c0 sub0xc01ddaec,%eax Code; c0121b4e <__get_free_pages+1f6/2b8> b: 8d 04 40 lea(%eax,%eax,2),%eax Code; c0121b51 <__get_free_pages+1f9/2b8> e: 89 c2 mov%eax,%edx Code; c0121b53 <__get_free_pages+1fb/2b8> 10: c1 e2 04 shl$0x4,%edx Code; c0121b56 <__get_free_pages+1fe/2b8> 13: 01 00 add%eax,(%eax) 1 warning issued. Results may not be reliable. Running 2.2.18pre21 I get the following during the scp I do afterwards to get the data off of the machine (sometimes it lock up here, other times it doesn't): ksymoops 0.7c on i586 2.2.18pre21. Options used -V (specified) -K (specified) -L (specified) -O (specified) -m /boot/System.map (specified) Unable to handle kernel NULL pointer dereference at virtual address 0014 current->tss.cr3 = 00101000, %cr3 = 00101000 *pde = Oops: 0002 CPU:0 EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010202 eax: ebx: c02d12e0 ecx: c02d12e0 edx: 0010 esi: 0400 edi: ebp: 0030 esp: c7fe1fac ds: 0018 es: 0018 ss: 0018 Process kswapd (pid: 5, process nr: 5, stackpage=c7fe1000) Stack: c7fe 001e 0006 0001 0001 c0121007 0006 0030 c7fe c01b615a c7fe01c5 0e00 c01210ef 0030 0f00 c7ff9fc0 c0106000 c0107c63 0f00 c01ebfd8 Call Trace: [] [] [] [] [] Code: 89 42 04 8b 51 04 85 d2 74 04 8b 01 89 02 c7 01 00 00 00 00 >>EIP; c011be86<= Trace; c0121007 Trace; c01b615a Trace; c01210ef Trace; c0106000 Trace; c0107c63 Code; c011be
Reproducable oops in 2.2.17 and 2.2.18pre21
Hi. I get an oops reproducably with 2.2.17 and 2.2.18pre21 on a stock RH 6.2 system. I cannot trigger it with the RH supplied kernel (2.2.14-5.0). I also got it with 2.2.17pre10 which prompted me to upgrade the kernel. I initially suspected bad RAM but have exchanged the RAM with memtest86'ed RAM for no improvement. What I do: I try to back the system up with tar zcvf /var/backup.tar.gz -X exclude /lib /sbin /var /bin /etc /boot /home /root /usr (the exclude file contains the path of the file itself, i.e., /var/ backup.tar.gz). Running 2.2.17 I got the following oops during the backup, i.e., tar had not finished yet (the exact place in the backup process varies): ksymoops 0.7c on i586 2.2.17. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.17/ (default) -m /boot/System.map (specified) Warning (compare_maps): ksyms_base symbol module_list_R__ver_module_list not found in System.map. Ignoring ksyms_base entry Nov 13 18:15:05 firewall kernel: Unable to handle kernel NULL pointer dereference at virtual address 0004 Nov 13 18:15:05 firewall kernel: current-tss.cr3 = 07259000, %cr3 = 07259000 Nov 13 18:15:05 firewall kernel: *pde = Nov 13 18:15:05 firewall kernel: Oops: 0002 Nov 13 18:15:05 firewall kernel: CPU:0 Nov 13 18:15:05 firewall kernel: EIP:0010:[c0121b43] Using defaults from ksymoops -t elf32-i386 -a i386 Nov 13 18:15:05 firewall kernel: EFLAGS: 00010087 Nov 13 18:15:05 firewall kernel: eax: ebx: 0001 ecx: edx: Nov 13 18:15:05 firewall kernel: esi: c02009f0 edi: 1000 ebp: c022a790 esp: c725bd4c Nov 13 18:15:05 firewall kernel: ds: 0018 es: 0018 ss: 0018 Nov 13 18:15:05 firewall kernel: Process bzip2 (pid: 1327, process nr: 23, stackpage=c725b000) Nov 13 18:15:05 firewall kernel: Stack: 1000 0306 0001 000a 0202 0306 16cf Nov 13 18:15:05 firewall kernel:1000 c0126ff4 0003 1000 0306 0002 c10fd3c0 Nov 13 18:15:05 firewall kernel:c06c1000 c01261e8 1000 16cf 1000 0306 0002 c10fd3c0 Nov 13 18:15:05 firewall kernel: Call Trace: [c0126ff4] [c01261e8] [c01263c5] [c0125f01] [c013f74c] [c013fdc2] [c014011b] Nov 13 18:15:05 firewall kernel:[c01264ff] [c013e23e] [c011130e] [c011ae20] [c011157e] [c0111573] [c010a103] [c01249cf] Nov 13 18:15:05 firewall kernel:[c012483c] [c010923d] [c0109104] Nov 13 18:15:05 firewall kernel: Code: 89 70 04 89 e8 2b 05 ec da 1d c0 8d 04 40 89 c2 c1 e2 04 01 EIP; c0121b43 __get_free_pages+1eb/2b8 = Trace; c0126ff4 grow_buffers+40/f8 Trace; c01261e8 refill_freelist+10/44 Trace; c01263c5 getblk+139/164 Trace; c0125f01 get_hash_table+1d/2c Trace; c013f74c ext2_alloc_block+74/178 Trace; c013fdc2 block_getblk+156/2a0 Trace; c014011b ext2_getblk+20f/21c Trace; c01264ff __brelse+13/64 Trace; c013e23e ext2_file_write+226/5bc Trace; c011130e update_wall_time+12/48 Trace; c011ae20 handle_mm_fault+c8/13c Trace; c011157e timer_bh+d2/3a0 Trace; c0111573 timer_bh+c7/3a0 Trace; c010a103 do_8259A_IRQ+8f/9c Trace; c01249cf sys_write+c3/e8 Trace; c012483c sys_read+0/d0 Trace; c010923d error_code+2d/40 Trace; c0109104 system_call+34/40 Code; c0121b43 __get_free_pages+1eb/2b8 _EIP: Code; c0121b43 __get_free_pages+1eb/2b8 = 0: 89 70 04 mov%esi,0x4(%eax) = Code; c0121b46 __get_free_pages+1ee/2b8 3: 89 e8 mov%ebp,%eax Code; c0121b48 __get_free_pages+1f0/2b8 5: 2b 05 ec da 1d c0 sub0xc01ddaec,%eax Code; c0121b4e __get_free_pages+1f6/2b8 b: 8d 04 40 lea(%eax,%eax,2),%eax Code; c0121b51 __get_free_pages+1f9/2b8 e: 89 c2 mov%eax,%edx Code; c0121b53 __get_free_pages+1fb/2b8 10: c1 e2 04 shl$0x4,%edx Code; c0121b56 __get_free_pages+1fe/2b8 13: 01 00 add%eax,(%eax) 1 warning issued. Results may not be reliable. Running 2.2.18pre21 I get the following during the scp I do afterwards to get the data off of the machine (sometimes it lock up here, other times it doesn't): ksymoops 0.7c on i586 2.2.18pre21. Options used -V (specified) -K (specified) -L (specified) -O (specified) -m /boot/System.map (specified) Unable to handle kernel NULL pointer dereference at virtual address 0014 current-tss.cr3 = 00101000, %cr3 = 00101000 *pde = Oops: 0002 CPU:0 EIP:0010:[c011be86] Using defaults from ksymoops -t elf32-i386 -a i386 EFLAGS: 00010202 eax: ebx: c02d12e0 ecx: c02d12e0 edx: 0010 esi: 0400 edi: ebp: 0030 esp: c7fe1fac ds: 0018 es: 0018 ss: 0018 Process kswapd (pid: 5, process nr: 5, stackpage=c7fe1000) Stack: c7fe 001e 0006 0001 0001 c0121007 0006 0030 c7fe c01b615a c7fe01c5
Re: Reproducable oops in 2.2.17 and 2.2.18pre21
On Fri, 17 Nov 2000, Rasmus Andersen wrote: Hi. I get an oops reproducably with 2.2.17 and 2.2.18pre21 on a stock RH 6.2 system. I cannot trigger it with the RH supplied kernel (2.2.14-5.0). I also got it with 2.2.17pre10 which prompted me to upgrade the kernel. I initially suspected bad RAM but have exchanged the RAM with memtest86'ed RAM for no improvement. snip Code; c0121b43 __get_free_pages+1eb/2b8 _EIP: Code; c0121b43 __get_free_pages+1eb/2b8 = 0: 89 70 04 mov%esi,0x4(%eax) = Code; c0121b46 __get_free_pages+1ee/2b8 3: 89 e8 mov%ebp,%eax Code; c0121b48 __get_free_pages+1f0/2b8 5: 2b 05 ec da 1d c0 sub0xc01ddaec,%eax Code; c0121b4e __get_free_pages+1f6/2b8 b: 8d 04 40 lea(%eax,%eax,2),%eax Code; c0121b51 __get_free_pages+1f9/2b8 e: 89 c2 mov%eax,%edx Code; c0121b53 __get_free_pages+1fb/2b8 10: c1 e2 04 shl$0x4,%edx Code; c0121b56 __get_free_pages+1fe/2b8 13: 01 00 add%eax,(%eax) Which compiler are you using? - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Reproducable oops in 2.2.17 and 2.2.18pre21
On Fri, 17 Nov 2000 14:49:38 Rasmus Andersen wrote: Hi. I get an oops reproducably with 2.2.17 and 2.2.18pre21 on a stock RH 6.2 system. I cannot trigger it with the RH supplied kernel (2.2.14-5.0). I also got it with 2.2.17pre10 which prompted me to upgrade the kernel. I initially suspected bad RAM but have exchanged the RAM with memtest86'ed RAM for no improvement. What I do: I try to back the system up with tar zcvf /var/backup.tar.gz -X exclude /lib /sbin /var /bin /etc /boot /home /root /usr (the exclude file contains the path of the file itself, i.e., /var/ backup.tar.gz). Exclude /dev and /proc also, /lost+found if you have it, and /mnt if you only want that drive. Perhaps things like /proc/kcore make trouble... -- Juan Antonio Magallon Lacarta # cd /pub mailto:[EMAIL PROTECTED] # more beer - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: oops in 2.2.17, not in 2.2.14-5
> > OK, I tried with 2.2.16 and 2.2.18pre21 compiled with egcs-2.91.66 > (the kernels reported yesterday were compiled with 2.95.2). > > 2.2.16 oopsed faithfully (I could not get hold of the oops as several > scrolled by and none made it to the log). 2.2.18pre21 does not oops. > Bzip2 core dumps, but gzip makes it through. So it seems that my > problem has been solved already and proactively :) > Eeek. Apparently I was a bit too early with the champagne... I was away for an hour or so and when I came back it (2.2.18pre21) had oopsed with multiple oops (i.e. the first offscreen) and hardlocked. I'm now running 2.2.14-5 again, doing the exact same stuff and it seems to hold up... (knock wood). Barring someine suggestin a better solution I'll try to compile a kernel with serial console and capture an oops that way. Regards Rasmus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: oops in 2.2.17, not in 2.2.14-5
> I get this also with 2.2.17pre10 (which was what I was running before > encountering this) but not with the stock RH 6.2 kernel (2.2.14-5.0). > Unless I get other suggestions I'm going to try with the latest 2.2.18pre > and 2.2.16 tomorrow. > OK, I tried with 2.2.16 and 2.2.18pre21 compiled with egcs-2.91.66 (the kernels reported yesterday were compiled with 2.95.2). 2.2.16 oopsed faithfully (I could not get hold of the oops as several scrolled by and none made it to the log). 2.2.18pre21 does not oops. Bzip2 core dumps, but gzip makes it through. So it seems that my problem has been solved already and proactively :) Regards, Rasmus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Oops on 2.2.17 [klogd bonus question]
On Mon, Nov 13, 2000 at 11:10:08PM -0600, Peter Samuelson wrote: > > [Rasmus Andersen] > > I'm getting oopses on a linux 2.2.17 box when I try to do > > tar cvIf -X /. Reproducably. > > Are you excluding /proc? Trying to back up all of /proc is definitely > asking for trouble, although the oops still indicates a kernel bug. Good suggestion. But I exclude /proc and anyways it crashes before I get to that part of the fs. Regards, Rasmus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Oops on 2.2.17 [klogd bonus question]
On Mon, Nov 13, 2000 at 11:10:08PM -0600, Peter Samuelson wrote: [Rasmus Andersen] I'm getting oopses on a linux 2.2.17 box when I try to do tar cvIf file -Xfile /. Reproducably. Are you excluding /proc? Trying to back up all of /proc is definitely asking for trouble, although the oops still indicates a kernel bug. Good suggestion. But I exclude /proc and anyways it crashes before I get to that part of the fs. Regards, Rasmus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: oops in 2.2.17, not in 2.2.14-5
I get this also with 2.2.17pre10 (which was what I was running before encountering this) but not with the stock RH 6.2 kernel (2.2.14-5.0). Unless I get other suggestions I'm going to try with the latest 2.2.18pre and 2.2.16 tomorrow. OK, I tried with 2.2.16 and 2.2.18pre21 compiled with egcs-2.91.66 (the kernels reported yesterday were compiled with 2.95.2). 2.2.16 oopsed faithfully (I could not get hold of the oops as several scrolled by and none made it to the log). 2.2.18pre21 does not oops. Bzip2 core dumps, but gzip makes it through. So it seems that my problem has been solved already and proactively :) Regards, Rasmus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: oops in 2.2.17, not in 2.2.14-5
OK, I tried with 2.2.16 and 2.2.18pre21 compiled with egcs-2.91.66 (the kernels reported yesterday were compiled with 2.95.2). 2.2.16 oopsed faithfully (I could not get hold of the oops as several scrolled by and none made it to the log). 2.2.18pre21 does not oops. Bzip2 core dumps, but gzip makes it through. So it seems that my problem has been solved already and proactively :) Eeek. Apparently I was a bit too early with the champagne... I was away for an hour or so and when I came back it (2.2.18pre21) had oopsed with multiple oops (i.e. the first offscreen) and hardlocked. I'm now running 2.2.14-5 again, doing the exact same stuff and it seems to hold up... (knock wood). Barring someine suggestin a better solution I'll try to compile a kernel with serial console and capture an oops that way. Regards Rasmus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Oops on 2.2.17 [klogd bonus question]
[Rasmus Andersen] > I'm getting oopses on a linux 2.2.17 box when I try to do > tar cvIf -X /. Reproducably. Are you excluding /proc? Trying to back up all of /proc is definitely asking for trouble, although the oops still indicates a kernel bug. Peter - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Oops on 2.2.17 [klogd bonus question]
On Mon, 13 Nov 2000, Rasmus Andersen wrote: > Hi. > > I'm getting oopses on a linux 2.2.17 box when I try to do > tar cvIf -X /. Reproducably. This works fine > for the std. RH 6.2 kernel (2.2.14-5). The resulting file > is about 20MB. > > I would submit the oops, but it is run through klogd and > I seem to remember people expressing dissatisfaction > with klogd. So what do I do now to get a usable oops > to submit? I dont know anything wrong with klogd. Anyway, kill klogd so you'll get a non decoded oops on your screen and then you can decoded it with ksymoops. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
oops in 2.2.17, not in 2.2.14-5
Hi. When running 'tar cvIf /' or 'tar cvzf /' (but sometimes not with 'plain' tar, i.e., without compression) I get an oops after some time. This is reproducible. The oops below is from a 'tar cvIf' run. I get this also with 2.2.17pre10 (which was what I was running before encountering this) but not with the stock RH 6.2 kernel (2.2.14-5.0). Unless I get other suggestions I'm going to try with the latest 2.2.18pre and 2.2.16 tomorrow. Since I had just experienced RAM problems on another machine I put in some new RAM after testing it with memtest86, but that did not solve the problem (neither did the old RAM show any errors when I memtested it afterwards). I'm not sure about the warning. Is it fatal? And what should I do to get rid of it? Comments appreciated and info willingly given :) ksymoops 0.7c on i586 2.2.17. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.17/ (default) -m /boot/System.map (specified) Warning (compare_maps): ksyms_base symbol module_list_R__ver_module_list not found in System.map. Ignoring ksyms_base entry Nov 13 18:15:05 firewall kernel: Unable to handle kernel NULL pointer dereference at virtual address 0004 Nov 13 18:15:05 firewall kernel: current->tss.cr3 = 07259000, %cr3 = 07259000 Nov 13 18:15:05 firewall kernel: *pde = Nov 13 18:15:05 firewall kernel: Oops: 0002 Nov 13 18:15:05 firewall kernel: CPU:0 Nov 13 18:15:05 firewall kernel: EIP:0010:[] Using defaults from ksymoops -t elf32-i386 -a i386 Nov 13 18:15:05 firewall kernel: EFLAGS: 00010087 Nov 13 18:15:05 firewall kernel: eax: ebx: 0001 ecx: edx: Nov 13 18:15:05 firewall kernel: esi: c02009f0 edi: 1000 ebp: c022a790 esp: c725bd4c Nov 13 18:15:05 firewall kernel: ds: 0018 es: 0018 ss: 0018 Nov 13 18:15:05 firewall kernel: Process bzip2 (pid: 1327, process nr: 23, stackpage=c725b000) Nov 13 18:15:05 firewall kernel: Stack: 1000 0306 0001 000a 0202 0306 16cf Nov 13 18:15:05 firewall kernel:1000 c0126ff4 0003 1000 0306 0002 c10fd3c0 Nov 13 18:15:05 firewall kernel:c06c1000 c01261e8 1000 16cf 1000 0306 0002 c10fd3c0 Nov 13 18:15:05 firewall kernel: Call Trace: [] [] [] [] [] [] [] Nov 13 18:15:05 firewall kernel:[] [] [] [] [] [] [] [] Nov 13 18:15:05 firewall kernel:[] [] [] Nov 13 18:15:05 firewall kernel: Code: 89 70 04 89 e8 2b 05 ec da 1d c0 8d 04 40 89 c2 c1 e2 04 01 >>EIP; c0121b43 <__get_free_pages+1eb/2b8> <= Trace; c0126ff4 Trace; c01261e8 Trace; c01263c5 Trace; c0125f01 Trace; c013f74c Trace; c013fdc2 Trace; c014011b Trace; c01264ff <__brelse+13/64> Trace; c013e23e Trace; c011130e Trace; c011ae20 Trace; c011157e Trace; c0111573 Trace; c010a103 Trace; c01249cf Trace; c012483c Trace; c010923d Trace; c0109104 Code; c0121b43 <__get_free_pages+1eb/2b8> <_EIP>: Code; c0121b43 <__get_free_pages+1eb/2b8> <= 0: 89 70 04 mov%esi,0x4(%eax) <= Code; c0121b46 <__get_free_pages+1ee/2b8> 3: 89 e8 mov%ebp,%eax Code; c0121b48 <__get_free_pages+1f0/2b8> 5: 2b 05 ec da 1d c0 sub0xc01ddaec,%eax Code; c0121b4e <__get_free_pages+1f6/2b8> b: 8d 04 40 lea(%eax,%eax,2),%eax Code; c0121b51 <__get_free_pages+1f9/2b8> e: 89 c2 mov%eax,%edx Code; c0121b53 <__get_free_pages+1fb/2b8> 10: c1 e2 04 shl$0x4,%edx Code; c0121b56 <__get_free_pages+1fe/2b8> 13: 01 00 add%eax,(%eax) 1 warning issued. Results may not be reliable. -- Regards, Rasmus([EMAIL PROTECTED]) Without censorship, things can get terribly confused in the public mind. -General William Westmoreland, during the war in Viet Nam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Oops on 2.2.17 [klogd bonus question]
Hi. I'm getting oopses on a linux 2.2.17 box when I try to do tar cvIf -X /. Reproducably. This works fine for the std. RH 6.2 kernel (2.2.14-5). The resulting file is about 20MB. I would submit the oops, but it is run through klogd and I seem to remember people expressing dissatisfaction with klogd. So what do I do now to get a usable oops to submit? Regards, Rasmus - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
oops in 2.2.17, not in 2.2.14-5
Hi. When running 'tar cvIf file /' or 'tar cvzf file /' (but sometimes not with 'plain' tar, i.e., without compression) I get an oops after some time. This is reproducible. The oops below is from a 'tar cvIf' run. I get this also with 2.2.17pre10 (which was what I was running before encountering this) but not with the stock RH 6.2 kernel (2.2.14-5.0). Unless I get other suggestions I'm going to try with the latest 2.2.18pre and 2.2.16 tomorrow. Since I had just experienced RAM problems on another machine I put in some new RAM after testing it with memtest86, but that did not solve the problem (neither did the old RAM show any errors when I memtested it afterwards). I'm not sure about the warning. Is it fatal? And what should I do to get rid of it? Comments appreciated and info willingly given :) ksymoops 0.7c on i586 2.2.17. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.17/ (default) -m /boot/System.map (specified) Warning (compare_maps): ksyms_base symbol module_list_R__ver_module_list not found in System.map. Ignoring ksyms_base entry Nov 13 18:15:05 firewall kernel: Unable to handle kernel NULL pointer dereference at virtual address 0004 Nov 13 18:15:05 firewall kernel: current-tss.cr3 = 07259000, %cr3 = 07259000 Nov 13 18:15:05 firewall kernel: *pde = Nov 13 18:15:05 firewall kernel: Oops: 0002 Nov 13 18:15:05 firewall kernel: CPU:0 Nov 13 18:15:05 firewall kernel: EIP:0010:[c0121b43] Using defaults from ksymoops -t elf32-i386 -a i386 Nov 13 18:15:05 firewall kernel: EFLAGS: 00010087 Nov 13 18:15:05 firewall kernel: eax: ebx: 0001 ecx: edx: Nov 13 18:15:05 firewall kernel: esi: c02009f0 edi: 1000 ebp: c022a790 esp: c725bd4c Nov 13 18:15:05 firewall kernel: ds: 0018 es: 0018 ss: 0018 Nov 13 18:15:05 firewall kernel: Process bzip2 (pid: 1327, process nr: 23, stackpage=c725b000) Nov 13 18:15:05 firewall kernel: Stack: 1000 0306 0001 000a 0202 0306 16cf Nov 13 18:15:05 firewall kernel:1000 c0126ff4 0003 1000 0306 0002 c10fd3c0 Nov 13 18:15:05 firewall kernel:c06c1000 c01261e8 1000 16cf 1000 0306 0002 c10fd3c0 Nov 13 18:15:05 firewall kernel: Call Trace: [c0126ff4] [c01261e8] [c01263c5] [c0125f01] [c013f74c] [c013fdc2] [c014011b] Nov 13 18:15:05 firewall kernel:[c01264ff] [c013e23e] [c011130e] [c011ae20] [c011157e] [c0111573] [c010a103] [c01249cf] Nov 13 18:15:05 firewall kernel:[c012483c] [c010923d] [c0109104] Nov 13 18:15:05 firewall kernel: Code: 89 70 04 89 e8 2b 05 ec da 1d c0 8d 04 40 89 c2 c1 e2 04 01 EIP; c0121b43 __get_free_pages+1eb/2b8 = Trace; c0126ff4 grow_buffers+40/f8 Trace; c01261e8 refill_freelist+10/44 Trace; c01263c5 getblk+139/164 Trace; c0125f01 get_hash_table+1d/2c Trace; c013f74c ext2_alloc_block+74/178 Trace; c013fdc2 block_getblk+156/2a0 Trace; c014011b ext2_getblk+20f/21c Trace; c01264ff __brelse+13/64 Trace; c013e23e ext2_file_write+226/5bc Trace; c011130e update_wall_time+12/48 Trace; c011ae20 handle_mm_fault+c8/13c Trace; c011157e timer_bh+d2/3a0 Trace; c0111573 timer_bh+c7/3a0 Trace; c010a103 do_8259A_IRQ+8f/9c Trace; c01249cf sys_write+c3/e8 Trace; c012483c sys_read+0/d0 Trace; c010923d error_code+2d/40 Trace; c0109104 system_call+34/40 Code; c0121b43 __get_free_pages+1eb/2b8 _EIP: Code; c0121b43 __get_free_pages+1eb/2b8 = 0: 89 70 04 mov%esi,0x4(%eax) = Code; c0121b46 __get_free_pages+1ee/2b8 3: 89 e8 mov%ebp,%eax Code; c0121b48 __get_free_pages+1f0/2b8 5: 2b 05 ec da 1d c0 sub0xc01ddaec,%eax Code; c0121b4e __get_free_pages+1f6/2b8 b: 8d 04 40 lea(%eax,%eax,2),%eax Code; c0121b51 __get_free_pages+1f9/2b8 e: 89 c2 mov%eax,%edx Code; c0121b53 __get_free_pages+1fb/2b8 10: c1 e2 04 shl$0x4,%edx Code; c0121b56 __get_free_pages+1fe/2b8 13: 01 00 add%eax,(%eax) 1 warning issued. Results may not be reliable. -- Regards, Rasmus([EMAIL PROTECTED]) Without censorship, things can get terribly confused in the public mind. -General William Westmoreland, during the war in Viet Nam - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Oops on 2.2.17 [klogd bonus question]
On Mon, 13 Nov 2000, Rasmus Andersen wrote: Hi. I'm getting oopses on a linux 2.2.17 box when I try to do tar cvIf file -Xfile /. Reproducably. This works fine for the std. RH 6.2 kernel (2.2.14-5). The resulting file is about 20MB. I would submit the oops, but it is run through klogd and I seem to remember people expressing dissatisfaction with klogd. So what do I do now to get a usable oops to submit? I dont know anything wrong with klogd. Anyway, kill klogd so you'll get a non decoded oops on your screen and then you can decoded it with ksymoops. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Oops on 2.2.17 [klogd bonus question]
[Rasmus Andersen] I'm getting oopses on a linux 2.2.17 box when I try to do tar cvIf file -Xfile /. Reproducably. Are you excluding /proc? Trying to back up all of /proc is definitely asking for trouble, although the oops still indicates a kernel bug. Peter - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Oops on 2.2.17 (and 2.2.18pre20)
Hello i got me several nasty oopses on my heavily loaded webserver. [1.] One line summary of the problem: I get a oops that seems to generate more oops. My logs are full of them bastards. I hate them. GRRR. [2.] Full description of the problem/report: I recently upgraded my box to 1GB of mem, and upgraded to 2.2.18pre20 + andreas VM-Global patch. The only thing i changed was to turn on (ip) firewall. I then got a oops. Thinking nothing of it i reverted to 2.2.17 (turned on firewalling there too) thinking it was a pre20 or VM-Global problem. Then i got this never ending oops loop. Some parts of the system still worked (especially the part mailing me all the oopses = 300MB of logs :)). I wonder if has something to do with the memory? How do i check for bad ram? Does 1GB break something? [3.] Keywords (i.e., modules, networking, kernel): eepro100,firewalling,2.2.17,2.2.18pre20,SMP,1GB [4.] Kernel version (from /proc/version): Linux version 2.2.17 ([EMAIL PROTECTED]) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #4 SMP Thu Nov 9 07:21:07 CET 2000 [5.] Output of Oops.. I have several megs of oops if anyone wants them. Ksymoops complained about: /usr/bin/nm: /lib/modules/2.2.17/build/arch/i386/boot/bbootsect.o: File format not recognized /usr/src/linux/scripts/ksymoops/ksymoops: read_nm_symbols pclose failed 0x100 and alot about stuff like this: Warning: ksyms_base symbol EISA_bus_Rsmp_7413793a not found in System.map. Ignoring ksyms_base entry Warning: ksyms_base symbol MCA_bus_Rsmp_f48a2c4c not found in System.map. Ignoring ksyms_base entry The Oopses: Nov 10 09:05:48 gimme kernel: current->tss.cr3 = 31f25000, %%cr3 = 31f25000 Nov 10 09:05:48 gimme kernel: *pde = 32556067 Nov 10 09:05:48 gimme kernel: Oops: Nov 10 09:05:48 gimme kernel: CPU:1 Nov 10 09:05:48 gimme kernel: EIP:0010:[do_follow_link+39/408] Nov 10 09:05:48 gimme kernel: EFLAGS: 00010206 Nov 10 09:05:48 gimme kernel: eax: c9dd3e60 ebx: c9dd3e60 ecx: 000c0024 edx: eb374c00 Nov 10 09:05:48 gimme kernel: esi: c71387a0 edi: c9dd3e60 ebp: 0001 esp: f2bcff20 Nov 10 09:05:48 gimme kernel: ds: 0018 es: 0018 ss: 0018 Nov 10 09:05:48 gimme kernel: Process postmaster (pid: 23613, process nr: 192, stackpage=f2bcf000) Nov 10 09:05:48 gimme kernel: Stack: c60b0035 0001 c012ff5b c71387a0 c9dd3e60 0001 e4f362a0 ffe9 Nov 10 09:05:48 gimme kernel:c60b 0003 c60b001f 0016 8bc1bd82 c01300ae c60b c71387a0 Nov 10 09:05:48 gimme kernel:0001 e4f362a0 ffe9 c60b 0028 f2bce000 1000 002e Nov 10 09:05:48 gimme kernel: Call Trace: [lookup_dentry+351/488] [open_namei+114/1248] [filp_open+68/240] [sys_open+82/172] [system_call+52/56] Nov 10 09:05:48 gimme kernel: Code: 8b 41 64 85 c0 0f 84 54 01 00 00 83 78 2c 00 0f 84 4a 01 00 Warning: trailing garbage ignored on Code: line Text: 'Code: 8b 41 64 85 c0 0f 84 54 01 00 00 83 78 2c 00 0f 84 4a 01 00 ' Garbage: ' ' Code: Before first symbol <_IP>: <=== Code: Before first symbol 0:8b 41 64 movl 0x64(%ecx),%eax <=== Code: 0003 Before first symbol 3:85 c0 testl %eax,%eax Code: 0005 Before first symbol 5:0f 84 54 01 00 00 je 015f Before first symbol Code: 000b Before first symbol b:83 78 2c 00 cmpl $0x0,0x2c(%eax) Code: 000f Before first symbol f:0f 84 4a 01 00 00 je 015f Before first symbol Nov 10 09:05:48 gimme kernel: Unable to handle kernel paging request at virtual address 000c0088 Nov 10 09:05:48 gimme kernel: current->tss.cr3 = 324ea000, %%cr3 = 324ea000 Nov 10 09:05:48 gimme kernel: *pde = 2f89c067 Nov 10 09:05:48 gimme kernel: Oops: Nov 10 09:05:48 gimme kernel: CPU:0 Nov 10 09:05:48 gimme kernel: EIP:0010:[do_follow_link+39/408] Nov 10 09:05:48 gimme kernel: EFLAGS: 00010206 Nov 10 09:05:48 gimme kernel: eax: c9dd3e60 ebx: c9dd3e60 ecx: 000c0024 edx: eb374c00 Nov 10 09:05:48 gimme kernel: esi: c71387a0 edi: c9dd3e60 ebp: 0001 esp: f2bcff20 Nov 10 09:05:48 gimme kernel: ds: 0018 es: 0018 ss: 0018 Nov 10 09:05:48 gimme kernel: Process postmaster (pid: 23615, process nr: 192, stackpage=f2bcf000) Nov 10 09:05:48 gimme kernel: Stack: c77d7035 0001 c012ff5b c71387a0 c9dd3e60 0001 c329d1e0 ffe9 Nov 10 09:05:48 gimme kernel:c77d7000 0003 c77d701f 0016 8bc1bd82 c01300ae c77d7000 c71387a0 Nov 10 09:05:48 gimme kernel:0001 c329d1e0 ffe9 c77d7000 0028 f2bce000 1000 002e Nov 10 09:05:48 gimme kernel: Call Trace: [lookup_dentry+351/488] [open_namei+114/1248] [filp_open+68/240] [sys_open+82/172] [system_call+52/56] Nov 10 09:05:48 gimme kernel: Code: 8b 41 64 85 c0 0f 84 54 01 00 00 83 78 2c 00 0f 84 4a 01 00 Warning: trailing garbage ignored on Code: line Text: 'Code: 8b 41 64 85 c0 0f 84 54 01 00 00 83 78 2c 00 0f 84 4a 01 00 ' Garbage: ' ' Code:
Oops in 2.2.17
Today I've found the following in my /var/log/messages: Oct 28 20:14:36 some_host kernel: kmem_free: Bad obj addr (objp=c2b381e0, name=size-64) Oct 28 20:14:36 some_host kernel: Unable to handle kernel NULL pointer dereference at virtual address Oct 28 20:14:36 some_host kernel: current->tss.cr3 = 00101000, %cr3 = 00101000 Oct 28 20:14:36 some_host kernel: *pde = Oct 28 20:14:36 some_host kernel: Oops: 0002 Oct 28 20:14:36 some_host kernel: CPU:0 Oct 28 20:14:36 some_host kernel: EIP:0010:[kfree+377/424] Oct 28 20:14:36 some_host kernel: EFLAGS: 00010202 Oct 28 20:14:36 some_host kernel: eax: 0039 ebx: c2fff0e0 ecx: edx: 003b Oct 28 20:14:36 some_host kernel: esi: c2b381e0 edi: 0202 ebp: 0825d1fc esp: c2fc3f80 Oct 28 20:14:36 some_host kernel: ds: 0018 es: 0018 ss: 0018 Oct 28 20:14:36 some_host kernel: Process kswapd (pid: 5, process nr: 5, stackpage=c2fc3000) Oct 28 20:14:36 some_host kernel: Stack: c2b3823c c1d8ebc0 c012e6f8 c2b381e0 0015 Oct 28 20:14:36 some_host kernel:0006 0001 0030 c012e9ef 0019 Oct 28 20:14:36 some_host kernel:c011fb79 0006 0030 c2fc2000 c01ac29a c2fc21c1 0e00 c011fc0b Oct 28 20:14:36 some_host kernel: Call Trace: [prune_dcache+220/300] [shrink_dcache_memory+35/40] [do_try_to_free_pages+137/184] [tvecs+7290/13632] [kswapd+99/152] [get_options+0/116] [kernel_thread+35/48] Oct 28 20:14:36 some_host kernel: Code: c7 05 00 00 00 00 00 00 00 00 eb 1b 8d 76 00 56 68 22 c1 1a Here is some info: [gosha@gosha gosha]$ uname -a Linux gosha 2.2.17 #1 Tue Sep 5 00:25:20 EDT 2000 i586 unknown [gosha@gosha gosha]$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 5 model : 4 model name : Pentium MMX stepping: 3 cpu MHz : 224.538 fdiv_bug: no hlt_bug : no sep_bug : no f00f_bug: yes coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr mce cx8 mmx bogomips: 447.28 [gosha@gosha gosha]$ cat /proc/meminfo total:used: free: shared: buffers: cached: Mem: 48250880 45023232 3227648 25837568 1007616 18173952 Swap: 101113856 67829760 33284096 MemTotal: 47120 kB MemFree:3152 kB MemShared: 25232 kB Buffers:984 kB Cached: 17748 kB SwapTotal: 98744 kB SwapFree: 32504 kB # # Automatically generated by make menuconfig: don't edit # # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set CONFIG_M586TSC=y # CONFIG_M686 is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_TSC=y CONFIG_1GB=y # CONFIG_2GB is not set # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set # CONFIG_SMP is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # General setup # CONFIG_NET=y CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_QUIRKS=y # CONFIG_PCI_OPTIMIZE is not set CONFIG_PCI_OLD_PROC=y # CONFIG_MCA is not set # CONFIG_VISWS is not set CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y # CONFIG_BINFMT_JAVA is not set # CONFIG_PARPORT is not set # CONFIG_APM is not set # CONFIG_TOSHIBA is not set # # Plug and Play support # CONFIG_PNP=y # # Block devices # CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_IDE=y # CONFIG_BLK_DEV_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y CONFIG_BLK_DEV_IDECD=y # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_BLK_DEV_IDESCSI is not set # CONFIG_BLK_DEV_CMD640 is not set # CONFIG_BLK_DEV_RZ1000 is not set CONFIG_BLK_DEV_IDEPCI=y CONFIG_BLK_DEV_IDEDMA=y # CONFIG_BLK_DEV_OFFBOARD is not set CONFIG_IDEDMA_AUTO=y # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_TRM290 is not set # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_VIA82C586 is not set # CONFIG_BLK_DEV_CMD646 is not set # CONFIG_BLK_DEV_CS5530 is not set # CONFIG_IDE_CHIPSETS is not set CONFIG_BLK_DEV_LOOP=y # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_MD is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y # CONFIG_BLK_DEV_XD is not set # CONFIG_BLK_DEV_DAC960 is not set CONFIG_PARIDE_PARPORT=y # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_DEV_HD is not set # # Networking options # CONFIG_PACKET=y CONFIG_NETLINK=y # CONFIG_RTNETLINK is not set CONFIG_NETLINK_DEV=y # CONFIG_FIREWALL is not set # CONFIG_FILTER is not set CONFIG_UNIX=y CONFIG_INET=y # CONFIG_IP_MULTICAST is not set # CONFIG_IP_ADVANCED_ROUTER
Oops in 2.2.17
Today I've found the following in my /var/log/messages: Oct 28 20:14:36 some_host kernel: kmem_free: Bad obj addr (objp=c2b381e0, name=size-64) Oct 28 20:14:36 some_host kernel: Unable to handle kernel NULL pointer dereference at virtual address Oct 28 20:14:36 some_host kernel: current-tss.cr3 = 00101000, %cr3 = 00101000 Oct 28 20:14:36 some_host kernel: *pde = Oct 28 20:14:36 some_host kernel: Oops: 0002 Oct 28 20:14:36 some_host kernel: CPU:0 Oct 28 20:14:36 some_host kernel: EIP:0010:[kfree+377/424] Oct 28 20:14:36 some_host kernel: EFLAGS: 00010202 Oct 28 20:14:36 some_host kernel: eax: 0039 ebx: c2fff0e0 ecx: edx: 003b Oct 28 20:14:36 some_host kernel: esi: c2b381e0 edi: 0202 ebp: 0825d1fc esp: c2fc3f80 Oct 28 20:14:36 some_host kernel: ds: 0018 es: 0018 ss: 0018 Oct 28 20:14:36 some_host kernel: Process kswapd (pid: 5, process nr: 5, stackpage=c2fc3000) Oct 28 20:14:36 some_host kernel: Stack: c2b3823c c1d8ebc0 c012e6f8 c2b381e0 0015 Oct 28 20:14:36 some_host kernel:0006 0001 0030 c012e9ef 0019 Oct 28 20:14:36 some_host kernel:c011fb79 0006 0030 c2fc2000 c01ac29a c2fc21c1 0e00 c011fc0b Oct 28 20:14:36 some_host kernel: Call Trace: [prune_dcache+220/300] [shrink_dcache_memory+35/40] [do_try_to_free_pages+137/184] [tvecs+7290/13632] [kswapd+99/152] [get_options+0/116] [kernel_thread+35/48] Oct 28 20:14:36 some_host kernel: Code: c7 05 00 00 00 00 00 00 00 00 eb 1b 8d 76 00 56 68 22 c1 1a Here is some info: [gosha@gosha gosha]$ uname -a Linux gosha 2.2.17 #1 Tue Sep 5 00:25:20 EDT 2000 i586 unknown [gosha@gosha gosha]$ cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 5 model : 4 model name : Pentium MMX stepping: 3 cpu MHz : 224.538 fdiv_bug: no hlt_bug : no sep_bug : no f00f_bug: yes coma_bug: no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr mce cx8 mmx bogomips: 447.28 [gosha@gosha gosha]$ cat /proc/meminfo total:used: free: shared: buffers: cached: Mem: 48250880 45023232 3227648 25837568 1007616 18173952 Swap: 101113856 67829760 33284096 MemTotal: 47120 kB MemFree:3152 kB MemShared: 25232 kB Buffers:984 kB Cached: 17748 kB SwapTotal: 98744 kB SwapFree: 32504 kB # # Automatically generated by make menuconfig: don't edit # # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set CONFIG_M586TSC=y # CONFIG_M686 is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_TSC=y CONFIG_1GB=y # CONFIG_2GB is not set # CONFIG_MATH_EMULATION is not set # CONFIG_MTRR is not set # CONFIG_SMP is not set # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # General setup # CONFIG_NET=y CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_QUIRKS=y # CONFIG_PCI_OPTIMIZE is not set CONFIG_PCI_OLD_PROC=y # CONFIG_MCA is not set # CONFIG_VISWS is not set CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y # CONFIG_BINFMT_JAVA is not set # CONFIG_PARPORT is not set # CONFIG_APM is not set # CONFIG_TOSHIBA is not set # # Plug and Play support # CONFIG_PNP=y # # Block devices # CONFIG_BLK_DEV_FD=y CONFIG_BLK_DEV_IDE=y # CONFIG_BLK_DEV_HD_IDE is not set CONFIG_BLK_DEV_IDEDISK=y CONFIG_BLK_DEV_IDECD=y # CONFIG_BLK_DEV_IDETAPE is not set # CONFIG_BLK_DEV_IDEFLOPPY is not set # CONFIG_BLK_DEV_IDESCSI is not set # CONFIG_BLK_DEV_CMD640 is not set # CONFIG_BLK_DEV_RZ1000 is not set CONFIG_BLK_DEV_IDEPCI=y CONFIG_BLK_DEV_IDEDMA=y # CONFIG_BLK_DEV_OFFBOARD is not set CONFIG_IDEDMA_AUTO=y # CONFIG_BLK_DEV_OPTI621 is not set # CONFIG_BLK_DEV_TRM290 is not set # CONFIG_BLK_DEV_NS87415 is not set # CONFIG_BLK_DEV_VIA82C586 is not set # CONFIG_BLK_DEV_CMD646 is not set # CONFIG_BLK_DEV_CS5530 is not set # CONFIG_IDE_CHIPSETS is not set CONFIG_BLK_DEV_LOOP=y # CONFIG_BLK_DEV_NBD is not set # CONFIG_BLK_DEV_MD is not set CONFIG_BLK_DEV_RAM=y CONFIG_BLK_DEV_RAM_SIZE=4096 CONFIG_BLK_DEV_INITRD=y # CONFIG_BLK_DEV_XD is not set # CONFIG_BLK_DEV_DAC960 is not set CONFIG_PARIDE_PARPORT=y # CONFIG_PARIDE is not set # CONFIG_BLK_CPQ_DA is not set # CONFIG_BLK_DEV_HD is not set # # Networking options # CONFIG_PACKET=y CONFIG_NETLINK=y # CONFIG_RTNETLINK is not set CONFIG_NETLINK_DEV=y # CONFIG_FIREWALL is not set # CONFIG_FILTER is not set CONFIG_UNIX=y CONFIG_INET=y # CONFIG_IP_MULTICAST is not set # CONFIG_IP_ADVANCED_ROUTER is
[OOPS] with 2.2.17+ide+ext3
Casually browsing through my system logs, I came upon this two oopses that happened together (logged as same second). I don't really remember what situation was surrounding, or even if any interruption was experienced. The system did totally freeze just under 30 minutes later, however, with no oops logged at that time. Neither SysRq nor Ctrl+Alt+Del responded; I had to hit the reset button on the case. Attached are the two recorded oopses as processed by ksymoops. If it makes much difference, the oops wasn't run through ksymoops until after a reboot. ksymoops 2.3.4 on i586 2.2.17ext3. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.17ext3/ (default) -m /boot/System.map-2.2.17ext3 (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Warning (compare_maps): mismatch on symbol V32U96eyeLocation , pctel says c410b5b0, /lib/modules/2.2.17ext3/misc/pctel.o says c41284d4. Ignoring /lib/modules/2.2.17ext3/misc/pctel.o entry Oops: CPU:0 EIP:0010:[sock_poll+26/48] EFLAGS: 00013293 eax: 9d129dbe ebx: c12da8c0 ecx: c1f87000 edx: c12da8c0 esi: edi: 0400 ebp: 000a esp: c2241ee8 ds: 0018 es: 0018 ss: 0018 Process X (pid: 288, process nr: 28, stackpage=c2241000) Stack: 0040 0020 c2c43540 c012fa5a c12da8c0 c1f87000 1000 0008 0020 c2c43540 Call Trace: [do_select+274/512] [sys_select+881/1176] [sys_gettimeofday+32/148] [system_call+52/56] Code: 8b 50 08 51 50 53 8b 42 20 ff d0 83 c4 10 5b 83 c4 18 c3 8d Using defaults from ksymoops -t elf32-i386 -a i386 Code; Before first symbol <_EIP>: Code; Before first symbol 0: 8b 50 08 mov0x8(%eax),%edx Code; 0003 Before first symbol 3: 51push %ecx Code; 0004 Before first symbol 4: 50push %eax Code; 0005 Before first symbol 5: 53push %ebx Code; 0006 Before first symbol 6: 8b 42 20 mov0x20(%edx),%eax Code; 0009 Before first symbol 9: ff d0 call *%eax Code; 000b Before first symbol b: 83 c4 10 add$0x10,%esp Code; 000e Before first symbol e: 5bpop%ebx Code; 000f Before first symbol f: 83 c4 18 add$0x18,%esp Code; 0012 Before first symbol 12: c3ret Code; 0013 Before first symbol 13: 8d 00 lea(%eax),%eax Oops: CPU:0 EIP:0010:[locks_remove_posix+32/148] EFLAGS: 00013286 eax: 9d129d12 ebx: c12da8c0 ecx: 9d129d12 edx: c12da8c0 esi: c0024e00 edi: ebp: 9d129d82 esp: c2241d6c ds: 0018 es: 0018 ss: 0018 Process X (pid: 288, process nr: 28, stackpage=c2241000) Stack: 0001 9d129d12 0300 c0126a68 c07753e0 9d129dc6 c32f7af8 c0126a8e c07753e0 c0221da4 c0221da3 3246 c2b37660 c0221da3 c0221da4 c01133d3 c3def6e0 c32f7ae0 c2242000 c012596b c12da8c0 c2263400 Call Trace: [fput+32/84] [fput+70/84] [mmput+63/72] [filp_close+83/108] [mm_release+16/52] [do_exit+320/672] [do_exit+201/672] Oct 22 23:29:42 hapablap kernel:[die+71/72] [error_table+9294/9568] [error_table+9216/9568] [do_page_fault+729/992] [error_table+9294/9568] [error_code+45/52] [sock_poll+26/48] [alloc_wait+23/152] Code: 8b 71 70 85 f6 74 62 90 f6 46 24 01 74 52 8b 44 24 64 39 46 Code; Before first symbol <_EIP>: Code; Before first symbol 0: 8b 71 70 mov0x70(%ecx),%esi Code; 0003 Before first symbol 3: 85 f6 test %esi,%esi Code; 0005 Before first symbol 5: 74 62 je 69 <_EIP+0x69> 0069 Before first symbol Code; 0007 Before first symbol 7: 90nop Code; 0008 Before first symbol 8: f6 46 24 01 testb $0x1,0x24(%esi) Code; 000c Before first symbol c: 74 52 je 60 <_EIP+0x60> 0060 Before first symbol Code; 000e Before first symbol e: 8b 44 24 64 mov0x64(%esp,1),%eax Code; 0012 Before first symbol 12: 39 46 00 cmp%eax,0x0(%esi) 2 warnings issued. Results may not be reliable.
[OOPS] with 2.2.17+ide+ext3
Casually browsing through my system logs, I came upon this two oopses that happened together (logged as same second). I don't really remember what situation was surrounding, or even if any interruption was experienced. The system did totally freeze just under 30 minutes later, however, with no oops logged at that time. Neither SysRq nor Ctrl+Alt+Del responded; I had to hit the reset button on the case. Attached are the two recorded oopses as processed by ksymoops. If it makes much difference, the oops wasn't run through ksymoops until after a reboot. ksymoops 2.3.4 on i586 2.2.17ext3. Options used -V (default) -k /proc/ksyms (default) -l /proc/modules (default) -o /lib/modules/2.2.17ext3/ (default) -m /boot/System.map-2.2.17ext3 (default) Warning: You did not tell me where to find symbol information. I will assume that the log matches the kernel and modules that are running right now and I'll use the default options above for symbol resolution. If the current kernel and/or modules do not match the log, you can get more accurate output by telling me the kernel version and where to find map, modules, ksyms etc. ksymoops -h explains the options. Warning (compare_maps): mismatch on symbol V32U96eyeLocation , pctel says c410b5b0, /lib/modules/2.2.17ext3/misc/pctel.o says c41284d4. Ignoring /lib/modules/2.2.17ext3/misc/pctel.o entry Oops: CPU:0 EIP:0010:[sock_poll+26/48] EFLAGS: 00013293 eax: 9d129dbe ebx: c12da8c0 ecx: c1f87000 edx: c12da8c0 esi: edi: 0400 ebp: 000a esp: c2241ee8 ds: 0018 es: 0018 ss: 0018 Process X (pid: 288, process nr: 28, stackpage=c2241000) Stack: 0040 0020 c2c43540 c012fa5a c12da8c0 c1f87000 1000 0008 0020 c2c43540 Call Trace: [do_select+274/512] [sys_select+881/1176] [sys_gettimeofday+32/148] [system_call+52/56] Code: 8b 50 08 51 50 53 8b 42 20 ff d0 83 c4 10 5b 83 c4 18 c3 8d Using defaults from ksymoops -t elf32-i386 -a i386 Code; Before first symbol _EIP: Code; Before first symbol 0: 8b 50 08 mov0x8(%eax),%edx Code; 0003 Before first symbol 3: 51push %ecx Code; 0004 Before first symbol 4: 50push %eax Code; 0005 Before first symbol 5: 53push %ebx Code; 0006 Before first symbol 6: 8b 42 20 mov0x20(%edx),%eax Code; 0009 Before first symbol 9: ff d0 call *%eax Code; 000b Before first symbol b: 83 c4 10 add$0x10,%esp Code; 000e Before first symbol e: 5bpop%ebx Code; 000f Before first symbol f: 83 c4 18 add$0x18,%esp Code; 0012 Before first symbol 12: c3ret Code; 0013 Before first symbol 13: 8d 00 lea(%eax),%eax Oops: CPU:0 EIP:0010:[locks_remove_posix+32/148] EFLAGS: 00013286 eax: 9d129d12 ebx: c12da8c0 ecx: 9d129d12 edx: c12da8c0 esi: c0024e00 edi: ebp: 9d129d82 esp: c2241d6c ds: 0018 es: 0018 ss: 0018 Process X (pid: 288, process nr: 28, stackpage=c2241000) Stack: 0001 9d129d12 0300 c0126a68 c07753e0 9d129dc6 c32f7af8 c0126a8e c07753e0 c0221da4 c0221da3 3246 c2b37660 c0221da3 c0221da4 c01133d3 c3def6e0 c32f7ae0 c2242000 c012596b c12da8c0 c2263400 Call Trace: [fput+32/84] [fput+70/84] [mmput+63/72] [filp_close+83/108] [mm_release+16/52] [do_exit+320/672] [do_exit+201/672] Oct 22 23:29:42 hapablap kernel:[die+71/72] [error_table+9294/9568] [error_table+9216/9568] [do_page_fault+729/992] [error_table+9294/9568] [error_code+45/52] [sock_poll+26/48] [alloc_wait+23/152] Code: 8b 71 70 85 f6 74 62 90 f6 46 24 01 74 52 8b 44 24 64 39 46 Code; Before first symbol _EIP: Code; Before first symbol 0: 8b 71 70 mov0x70(%ecx),%esi Code; 0003 Before first symbol 3: 85 f6 test %esi,%esi Code; 0005 Before first symbol 5: 74 62 je 69 _EIP+0x69 0069 Before first symbol Code; 0007 Before first symbol 7: 90nop Code; 0008 Before first symbol 8: f6 46 24 01 testb $0x1,0x24(%esi) Code; 000c Before first symbol c: 74 52 je 60 _EIP+0x60 0060 Before first symbol Code; 000e Before first symbol e: 8b 44 24 64 mov0x64(%esp,1),%eax Code; 0012 Before first symbol 12: 39 46 00 cmp%eax,0x0(%esi) 2 warnings issued. Results may not be reliable.
Oops in 2.2.17
I'm running 2.2.17 on Dual SMP system. This appeared on syslog last night: Oct 18 03:28:39 trane kernel: Unable to handle kernel paging request at virtual address 2d4d524d Oct 18 03:28:39 trane kernel: current->tss.cr3 = 00101000, %cr3 = 00101000 Oct 18 03:28:39 trane kernel: *pde = Oct 18 03:28:39 trane kernel: Oops: Oct 18 03:28:39 trane kernel: CPU:1 Oct 18 03:28:39 trane kernel: EIP:0010:[exit_mmap+86/264] Oct 18 03:28:39 trane kernel: EFLAGS: 00010202 Oct 18 03:28:39 trane kernel: eax: 2d4d5245 ebx: dd21e380 ecx: edx: cbe97da0 Oct 18 03:28:39 trane kernel: esi: edi: cbe97da0 ebp: esp: df4ffee0 Oct 18 03:28:39 trane kernel: ds: 0018 es: 0018 ss: 0018 Oct 18 03:28:39 trane kernel: Process sendmail (pid: 5802, process nr: 149, stackpage=df4ff000) Oct 18 03:28:39 trane kernel: Stack: df4fe000 000b c0114e74 cbe97da0 cbe97da0 cbe97da0 c0119cca Oct 18 03:28:39 trane kernel:cbe97da0 df4fe000 000b df4fe000 000b df4fe000 df4fe000 c010913c Oct 18 03:28:39 trane kernel:000b df4fe000 08122ed0 bfff7c88 df4fff40 df4fe4a4 df4fffc4 Oct 18 03:28:39 trane kernel: Call Trace: [mmput+28/52] [do_exit+250/744] [do_signal+568/724] [free_pgtables+127/136] [force_sig_info+168/180] [force_ sig+17/24] [do_page_fault+416/960] Oct 18 03:28:40 trane kernel:[sys_munmap+61/100] [error_code+45/52] [signal_return+20/24] Oct 18 03:28:40 trane kernel: Code: 8b 50 08 85 d2 74 0b 55 56 53 ff d2 83 c4 0c 8b 43 28 8b 40 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Oops in 2.2.17
I'm running 2.2.17 on Dual SMP system. This appeared on syslog last night: Oct 18 03:28:39 trane kernel: Unable to handle kernel paging request at virtual address 2d4d524d Oct 18 03:28:39 trane kernel: current-tss.cr3 = 00101000, %cr3 = 00101000 Oct 18 03:28:39 trane kernel: *pde = Oct 18 03:28:39 trane kernel: Oops: Oct 18 03:28:39 trane kernel: CPU:1 Oct 18 03:28:39 trane kernel: EIP:0010:[exit_mmap+86/264] Oct 18 03:28:39 trane kernel: EFLAGS: 00010202 Oct 18 03:28:39 trane kernel: eax: 2d4d5245 ebx: dd21e380 ecx: edx: cbe97da0 Oct 18 03:28:39 trane kernel: esi: edi: cbe97da0 ebp: esp: df4ffee0 Oct 18 03:28:39 trane kernel: ds: 0018 es: 0018 ss: 0018 Oct 18 03:28:39 trane kernel: Process sendmail (pid: 5802, process nr: 149, stackpage=df4ff000) Oct 18 03:28:39 trane kernel: Stack: df4fe000 000b c0114e74 cbe97da0 cbe97da0 cbe97da0 c0119cca Oct 18 03:28:39 trane kernel:cbe97da0 df4fe000 000b df4fe000 000b df4fe000 df4fe000 c010913c Oct 18 03:28:39 trane kernel:000b df4fe000 08122ed0 bfff7c88 df4fff40 df4fe4a4 df4fffc4 Oct 18 03:28:39 trane kernel: Call Trace: [mmput+28/52] [do_exit+250/744] [do_signal+568/724] [free_pgtables+127/136] [force_sig_info+168/180] [force_ sig+17/24] [do_page_fault+416/960] Oct 18 03:28:40 trane kernel:[sys_munmap+61/100] [error_code+45/52] [signal_return+20/24] Oct 18 03:28:40 trane kernel: Code: 8b 50 08 85 d2 74 0b 55 56 53 ff d2 83 c4 0c 8b 43 28 8b 40 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: OOPS on 2.2.17
On Fri, 29 Sep 2000 23:48:34 -0500 (CDT), Erik McKee <[EMAIL PROTECTED]> wrote: >I recieved this oops on boot up. ksymoops claims that the module is from >2.2.16, but I haven't touched any of the modules after make >modules_install. >Warning (compare_Version): Version mismatch. 3c507 says 2.2.17, bsd_comp says >2.2.16. Expect lots of address mismatches. You have a mixture of 2.2.16 and 2.2.17 modules in your system. Erase all of /lib/modules/`uname -r` and do a fresh make modules_install, but see below first. >Warning (compare_maps): ksyms_base symbol module_list_R__ver_module_list not found in >System.map. Ignoring ksyms_base entry You have been caught by the broken symbol versioning in the Makefiles. mv .config .. make mrproper mv ../.config . make oldconfig make dep clean bzImage modules rm -rf /lib/modules/ make install modules_install reboot - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
OOPS on 2.2.17
Hello!
I recieved this oops on boot up. ksymoops claims that the module is from
2.2.16, but I haven't touched any of the modules after make
modules_install. Also, with 2.2.17 my networking freezes up more
frequently then before. I only use ethernet and not ppp, so I don't now
why this module would be useful at all anyway.
TIA
Erik
ksymoops 2.3.4 on i586 2.2.17. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.2.17/ (default)
-m /usr/src/linux/System.map (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
Warning (compare_Version): Version mismatch. 3c507 says 2.2.17, bsd_comp says 2.2.16.
Expect lots of address mismatches.
Warning (compare_maps): ksyms_base symbol module_list_R__ver_module_list not found in
System.map. Ignoring ksyms_base entry
Unable to handle kernel paging request at virtual address 85005922
current->tss.cr3 = 01d08000, %cr3 = 01d08000
*pde =
Oops: 0002
CPU:0
EIP:0010:[]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010282
eax: c2802c91 ebx: c2802000 ecx: c023c9e0 edx: c023c9e0
esi: edi: c2802051 ebp: c2802048 esp: c1cc7ef8
ds: 0018 es: 0018 ss: 0018
Process modprobe (pid: 39, process nr: 9, stackpage=c1cc7000)
Stack: 08066248 c1cc7f4c c023c9e0 c2802000 c03b9009 c2802051 c0120867 c2802048
080653b8 0f60 c011421f c1cc6000 08065370 08062628 bfffe04c
c1cc7f4c 0008 ffea c03b9000 c03bb000 0048
Call Trace: [] [] [] [] []
[] []
[] [] []
Code: 00 0c 00 01 00 2e 00 00 00 08 79 03 00 0c 00 02 00 2e 2e 00
>>EIP; c1109003 <_end+ea7f2f/25a0f2c> <=
Trace; c2802000 <[bsd_comp]__module_kernel_version+0/16>
Trace; c2802051 <[bsd_comp]bsd_clear+5/30>
Trace; c0120867
Trace; c2802048 <[bsd_comp]__module_using_checksums+32/36>
Trace; c011421f
Trace; c2802048 <[bsd_comp]__module_using_checksums+32/36>
Trace; c2802000 <[bsd_comp]__module_kernel_version+0/16>
Trace; c0108e19
Trace; c0107b75
Trace; c0107a64
Code; c1109003 <_end+ea7f2f/25a0f2c>
<_EIP>:
Code; c1109003 <_end+ea7f2f/25a0f2c> <=
0: 00 0c 00 addb %cl,(%eax,%eax,1) <=
Code; c1109006 <_end+ea7f32/25a0f2c>
3: 01 00 addl %eax,(%eax)
Code; c1109008 <_end+ea7f34/25a0f2c>
5: 2e 00 00 addb %al,%cs:(%eax)
Code; c110900b <_end+ea7f37/25a0f2c>
8: 00 08 addb %cl,(%eax)
Code; c110900d <_end+ea7f39/25a0f2c>
a: 79 03 jnsf <_EIP+0xf> c1109012 <_end+ea7f3e/25a0f2c>
Code; c110900f <_end+ea7f3b/25a0f2c>
c: 00 0c 00 addb %cl,(%eax,%eax,1)
Code; c1109012 <_end+ea7f3e/25a0f2c>
f: 02 00 addb (%eax),%al
Code; c1109014 <_end+ea7f40/25a0f2c>
11: 2e 2e 00 00 addb %al,%cs:(%eax)
3 warnings issued. Results may not be reliable.
OOPS on 2.2.17
Hello!
I recieved this oops on boot up. ksymoops claims that the module is from
2.2.16, but I haven't touched any of the modules after make
modules_install. Also, with 2.2.17 my networking freezes up more
frequently then before. I only use ethernet and not ppp, so I don't now
why this module would be useful at all anyway.
TIA
Erik
ksymoops 2.3.4 on i586 2.2.17. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.2.17/ (default)
-m /usr/src/linux/System.map (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
Warning (compare_Version): Version mismatch. 3c507 says 2.2.17, bsd_comp says 2.2.16.
Expect lots of address mismatches.
Warning (compare_maps): ksyms_base symbol module_list_R__ver_module_list not found in
System.map. Ignoring ksyms_base entry
Unable to handle kernel paging request at virtual address 85005922
current-tss.cr3 = 01d08000, %cr3 = 01d08000
*pde =
Oops: 0002
CPU:0
EIP:0010:[c1109003]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010282
eax: c2802c91 ebx: c2802000 ecx: c023c9e0 edx: c023c9e0
esi: edi: c2802051 ebp: c2802048 esp: c1cc7ef8
ds: 0018 es: 0018 ss: 0018
Process modprobe (pid: 39, process nr: 9, stackpage=c1cc7000)
Stack: 08066248 c1cc7f4c c023c9e0 c2802000 c03b9009 c2802051 c0120867 c2802048
080653b8 0f60 c011421f c1cc6000 08065370 08062628 bfffe04c
c1cc7f4c 0008 ffea c03b9000 c03bb000 0048
Call Trace: [c2802000] [c2802051] [c0120867] [c2802048] [c011421f]
[c2802048] [c2802000]
[c0108e19] [c0107b75] [c0107a64]
Code: 00 0c 00 01 00 2e 00 00 00 08 79 03 00 0c 00 02 00 2e 2e 00
EIP; c1109003 _end+ea7f2f/25a0f2c =
Trace; c2802000 [bsd_comp]__module_kernel_version+0/16
Trace; c2802051 [bsd_comp]bsd_clear+5/30
Trace; c0120867 free_pages+27/2c
Trace; c2802048 [bsd_comp]__module_using_checksums+32/36
Trace; c011421f sys_init_module+44f/4c4
Trace; c2802048 [bsd_comp]__module_using_checksums+32/36
Trace; c2802000 [bsd_comp]__module_kernel_version+0/16
Trace; c0108e19 do_IRQ+41/48
Trace; c0107b75 error_code+2d/34
Trace; c0107a64 system_call+34/38
Code; c1109003 _end+ea7f2f/25a0f2c
_EIP:
Code; c1109003 _end+ea7f2f/25a0f2c =
0: 00 0c 00 addb %cl,(%eax,%eax,1) =
Code; c1109006 _end+ea7f32/25a0f2c
3: 01 00 addl %eax,(%eax)
Code; c1109008 _end+ea7f34/25a0f2c
5: 2e 00 00 addb %al,%cs:(%eax)
Code; c110900b _end+ea7f37/25a0f2c
8: 00 08 addb %cl,(%eax)
Code; c110900d _end+ea7f39/25a0f2c
a: 79 03 jnsf _EIP+0xf c1109012 _end+ea7f3e/25a0f2c
Code; c110900f _end+ea7f3b/25a0f2c
c: 00 0c 00 addb %cl,(%eax,%eax,1)
Code; c1109012 _end+ea7f3e/25a0f2c
f: 02 00 addb (%eax),%al
Code; c1109014 _end+ea7f40/25a0f2c
11: 2e 2e 00 00 addb %al,%cs:(%eax)
3 warnings issued. Results may not be reliable.
