LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Debian (https://www.linuxquestions.org/questions/debian-26/)
-   -   Oops & Kernel Panic on Debian Squeeze (https://www.linuxquestions.org/questions/debian-26/oops-and-kernel-panic-on-debian-squeeze-874840/)

Dudinin 04-13-2011 02:53 PM
Oops & Kernel Panic on Debian Squeeze
 
Hi everybody! Sory for my english :).
System: Debian Squeeze 2.6.32-5-686 (last stable in stable repo) without X-desktop

Last days I have an Oops & Kernel panic. Everything works well before I try to launch the EiskaltDC++. After some time before launching (using xvfb&x11vnc) I have an Oops such this:
Code:
Apr 11 21:44:10 Debi kernel: [177333.011830] BUG: unable to handle kernel NULL pointer dereference at 00000133
Apr 11 21:44:10 Debi kernel: [177333.011857] IP: [<c1238af6>] inet6_dump_addr+0x339/0x37e
Apr 11 21:44:10 Debi kernel: [177333.011873] *pde = 00000000
Apr 11 21:44:10 Debi kernel: [177333.011879] Oops: 0000 [#1] SMP
Apr 11 21:44:10 Debi kernel: [177333.011885] last sysfs file: /sys/devices/virtual/net/lo/operstate
Apr 11 21:44:10 Debi kernel: [177333.011893] Modules linked in: iptable_filter ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables tun binfmt_misc fuse loop snd_via82xx gameport snd_via82xx_modem snd_ac97_codec snd_mpu401_uart ac97_bus snd_rawmidi snd_pcm_oss snd_seq_device snd_mixer_oss snd_pcm snd_timer snd snd_page_alloc soundcore evdev processor button shpchp serio_raw i2c_viapro i2c_core pcspkr pci_hotplug ext4 mbcache jbd2 crc16 sd_mod crc_t10dif ata_generic pata_via sata_via uhci_hcd thermal via_rhine ehci_hcd thermal_sys libata mii usbcore nls_base scsi_mod tulip skge [last unloaded: scsi_wait_scan]
Apr 11 21:44:10 Debi kernel: [177333.011973]
Apr 11 21:44:10 Debi kernel: [177333.011979] Pid: 3681, comm: eiskaltdcpp-dae Not tainted (2.6.32-5-686 #1) System Name
Apr 11 21:44:10 Debi kernel: [177333.011987] EIP: 0060:[<c1238af6>] EFLAGS: 00210282 CPU: 0
Apr 11 21:44:10 Debi kernel: [177333.011994] EIP is at inet6_dump_addr+0x339/0x37e
Apr 11 21:44:10 Debi kernel: [177333.011999] EAX: cc122a89 EBX: 00000000 ECX: cc122a00 EDX: 000000ff
Apr 11 21:44:10 Debi kernel: [177333.012006] ESI: 000000c0 EDI: 00000030 EBP: cfb0a880 ESP: cc3b9cb0
Apr 11 21:44:10 Debi kernel: [177333.012009]  DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Apr 11 21:44:10 Debi kernel: [177333.012009] Process eiskaltdcpp-dae (pid: 3681, ti=cc3b8000 task=ce0c0880 task.ti=cc3b8000)
Apr 11 21:44:10 Debi kernel: [177333.012009] Stack:
Apr 11 21:44:10 Debi kernel: [177333.012009]  00000000 cfb0a880 ce49c6c0 cc122a84 c14c7a5c 00000003 00000000 00000000
Apr 11 21:44:10 Debi kernel: [177333.012009] <0> 00000000 cc130000 cc122a00 00000001 00000006 0000000a 00000002 00000030
Apr 11 21:44:10 Debi kernel: [177333.012009] <0> cfb0a880 c11e0f39 ce49c6c0 00000030 cfb0a894 ce49c6c0 cfb0a880 cf996600
Apr 11 21:44:10 Debi kernel: [177333.012009] Call Trace:
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c11e0f39>] ? rtnl_dump_all+0x79/0x94
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c11eedc2>] ? netlink_dump+0x47/0x143
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c11ef1a6>] ? netlink_recvmsg+0x170/0x26c
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c11efc0e>] ? netlink_unicast+0xda/0x10e
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c11ccc80>] ? __sock_recvmsg+0x50/0x58
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c11cd1b7>] ? sock_recvmsg+0x9d/0xb6
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c1043f56>] ? autoremove_wake_function+0x0/0x2d
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c1043f56>] ? autoremove_wake_function+0x0/0x2d
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c120ec88>] ? tcp_v4_do_rcv+0x15f/0x2cf
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c113b833>] ? copy_from_user+0x27/0x10e
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c11d46d1>] ? verify_iovec+0x3f/0x7a
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c11cdf9f>] ? sys_recvmsg+0x104/0x1a5
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c113b833>] ? copy_from_user+0x27/0x10e
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c11cdc90>] ? sys_sendto+0xfe/0x122
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c11cf364>] ? sock_init_data+0xa8/0x1c5
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c10c0f5c>] ? d_alloc+0x1b/0x154
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c10c0657>] ? __d_instantiate+0x44/0xa4
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c10d6fa1>] ? inotify_d_instantiate+0xf/0x30
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c11ccfcb>] ? sock_attach_fd+0x74/0x9e
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c10b175d>] ? fd_install+0x1e/0x3c
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c11cd03b>] ? sock_map_fd+0x46/0x50
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c11ce61c>] ? sys_socketcall+0x181/0x1aa
Apr 11 21:44:10 Debi kernel: [177333.012009]  [<c10030fb>] ? sysenter_do_call+0x12/0x28
Apr 11 21:44:10 Debi kernel: [177333.012009] Code: 18 ff 44 24 18 85 ed 0f 85 1d ff ff ff 8b 44 24 0c e8 2c 59 03 00 8b 44 24 28 e8 0b fc ff ff 85 f6 7e 2c 8b 54 24 24 ff 44 24 14 <8b> 42 34 83 e8 34 89 44 24 24 8b 54 24 24 8b 42 34 0f 18 00 90
Apr 11 21:44:10 Debi kernel: [177333.012009] EIP: [<c1238af6>] inet6_dump_addr+0x339/0x37e SS:ESP 0068:cc3b9cb0
Apr 11 21:44:10 Debi kernel: [177333.012009] CR2: 0000000000000133
Apr 11 21:44:10 Debi kernel: [177333.012452] ---[ end trace 814700765de41982 ]---
As I understand after talk with developers of eiskalt, it's not problem of eiskalt, but maybe drivers of netcard, hardware, or smth else.
When I try to launch eiskaltdcpp-daemon (without xvfb & x11vnc, without videocard or with), I have a similar Oops. Memory & Disks are in perfect condition (a few tests by MHDD & Memtest86+). Then I reconnect net cable to another netcard (from onboard to PCI). After launching eiskaltdcpp-daemon I had a kernel panic such this:
Code:
[18595.388251] CR2: 00000000ffffffb3
[some.digits ] ---[ end trace 814700765de41982 ]---
[some.digits ] Kernel Panic - not synching: Fatal exseption in interrupt
[some.digits ] Pid: 4716, comm: eiskaltdcpp-qt Tainted: G    D  2.6.32-5-686  #1
[some.digits ] Call Trace:
[some.digits ] [<c126c83a>] ? panic+0x38/0xe6
[some.digits ] **similar text**
[some.digits ] **similar text**
After that time after time I have had a kernel panic even if I use SSH! Sometimes I had exceptions using some programs as htop, aptitude.

How to solve this problem? Is it is software or hardware problem? If it's necessary, I can give more information.

Dudinin 04-24-2011 01:41 AM
Well, it seems to be a problem vith driver for chipset (or more exactly SATA-controller)VT8237. When I install my 1TB HDD and start eiskaltdcpp, after some time I have a kernel panic. Without this HDD I haven't. May be I should replace driver to another? Or this chipset can't work fine with 1TB SATA HDD with any drivers? I found this post:1TB WD Black Caviar + VT8237 working fine finally, but disk write cache?, it talk that IDE channel driver can solve any problem. How can I replace using driver to IDE?

P.S. Wow, when I connect my 1TB SATA HDD through Bi-directional IDE-SATA converter (using IDE slot), I also have the same kernel panic after using eiskaltdcpp...

Dudinin 05-16-2011 04:44 AM
Well... Thanks wery much for quick reply :). The decision of my problem is very fun: computer was overclocked! (probably by previous owner), and when I execute resource-intensive application, there is some memory errors (only 2nd test by memtester show errors!), I just put normal value..


All times are GMT -5. The time now is 02:39 PM.