[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Broken kernel at AMD64/EM64T



Norbert Tretkowski wrote:
* Bogdan wrote:
Yesterday I try to install linux-image-2.6.17-2-amd64. After reboot,
all serveices works well, but ssh which fails during connect:

Anyone with an AMD64 system who's able to reproduce this? Last time I
worked on such a system was with 2.6.15, which didn't had the problem.

                Norbert


I notice that ipac-ng also cause such problem for me:

strace:
~skip~
fcntl(3, F_SETFD, FD_CLOEXEC)           = 0
read(3, "1\n- 1154376000\n* 1157054400\n+ 11"..., 4096) = 41
--- SIGCHLD (Child exited) @ 0 (0) ---
read(3, "", 4096)                       = 0
close(3)                                = 0
rt_sigaction(SIGHUP, {SIG_IGN}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGINT, {SIG_IGN}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGQUIT, {SIG_IGN}, {SIG_DFL}, 8) = 0
wait4(13768, [{WIFEXITED(s) && WEXITSTATUS(s) == 0}], 0, NULL) = 13768
rt_sigaction(SIGHUP, {SIG_DFL}, NULL, 8) = 0
rt_sigaction(SIGINT, {SIG_DFL}, NULL, 8) = 0
rt_sigaction(SIGQUIT, {SIG_DFL}, NULL, 8) = 0
socketpair(PF_FILE, SOCK_STREAM, 0 <unfinished ...>
+++ killed by SIGKILL +++

dmesg:

Call Trace: <ffffffff80247f85>{tracesys+209}

Code: 48 8b 3c 23 89 c5 e8 c2 97 ff ff 85 c0 89 c3 78 2e 89 c6 4c
RIP <ffffffff80241bf9>{sys_socketpair+107} RSP <ffff81006f5d9f48>
CR2: 0000000000000003
 <1>Unable to handle kernel NULL pointer dereference at 0000000000000003 RIP:
<ffffffff80241bf9>{sys_socketpair+107}
PGD e25a067 PUD 73575067 PMD 0
Oops: 0000 [43] SMP
CPU 3
Modules linked in: iptable_filter ipt_REDIRECT xt_tcpudp iptable_nat ip_nat ip_conntrack nfnetlink ip_tables x_tables ipv6 sg sr_mod pcspkr shpchp pci_hotplug e752x_edac edac_mc ehci_hcd uhci_hcd tg3 eeprom i2c_isa i2c_i801 i2c_core psmouse ide_generic ide_disk ide_cd cdrom reiserfs sd_mod generic ide_core ata_piix libata scsi_mod evdev
Pid: 13767, comm: ipacsum Not tainted 2.6.17-2-amd64 #1
RIP: 0010:[<ffffffff80241bf9>] <ffffffff80241bf9>{sys_socketpair+107}
RSP: 0018:ffff810020dadf48  EFLAGS: 00010206
RAX: 0000000000000003 RBX: 0000000000000003 RCX: 0000000000000003
RDX: ffff810071bc4690 RSI: ffff81006a928980 RDI: ffff810071bc4700
RBP: 0000000000000000 R08: 00000000fffffff6 R09: ffff81006a928980
R10: 0000000000000000 R11: 0000000000000000 R12: 0000000000000001
R13: 0000000000000001 R14: 00007fff63069a50 R15: 00000000008878a0
FS:  00002b3e48494520(0000) GS:ffff8100024e37c0(0000) knlGS:0000000000000000
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000003 CR3: 000000007ef97000 CR4: 00000000000006e0
Process ipacsum (pid: 13767, threadinfo ffff810020dac000, task ffff810017d756a0)
Stack: ffff81004a1bec80 ffff81004a1be680 0000000000887880 00000000006bbe00
       0000000000503010 0000000000887830 00000000008878c0 ffffffff80247f85
       0000000000000202 00007fff63069a50
Call Trace: <ffffffff80247f85>{tracesys+209}

Code: 48 8b 3c 23 89 c5 e8 c2 97 ff ff 85 c0 89 c3 78 2e 89 c6 4c
RIP <ffffffff80241bf9>{sys_socketpair+107} RSP <ffff810020dadf48>
CR2: 0000000000000003

Reply to: