search for: c_link

...264 (kgdb) fr 6 #6 0xc05623aa in callout_reset (c=0xc3a8552c, to_ticks=19, ftn=0xc0561940 <realitexpire>, arg=0xc3a852b8) at /usr/src/sys/kern/kern_timeout.c:471 471 /usr/src/sys/kern/kern_timeout.c: No such file or directory. in /usr/src/sys/kern/kern_timeout.c (kgdb) p *c $1 = {c_links = {sle = {sle_next = 0x0}, tqe = {tqe_next = 0x0, tqe_prev = 0xd2006ad0}}, c_time = 2974104, c_arg = 0xc3a852b8, c_func = 0xc0561940 <realitexpire>, c_mtx = 0x0, c_flags = 22} (kgdb) p c->c_links.tqe.tqe_prev $2 = (struct callout **) 0xd2006ad0 (kgdb) p *c->c_links.tqe.tqe_prev Cannot...

Hi, 1. I think you should apply the attached patch to openssh-2.9p1, otherwise ssh-keyscan on linux boxes with glibc-2.1 will experience enormous timeout delays. 2. Is there a program like ssh-keyscan for the Version2 (dsa and rsa) keys?? regards Peter Breitenlohner <peb at mppmu.mpg.de> -------------- next part -------------- diff -ur openssh-2.9p1.orig/ssh-keyscan.c

...; /* Pointer to other possible addresses */ char *c_output_name; /* Hostname of connection for output */ char *c_data; /* Data read from this fd */ + Kex *c_kex; /* The key-exchange struct for ssh2 */ struct timeval c_tv; /* Time at which connection gets aborted */ TAILQ_ENTRY(Connection) c_link; /* List of connections in timeout order. */ } con; @@ -242,8 +264,8 @@ return (tok); } -static void -keyprint(char *host, char *output_name, char *kd, int len) +static Key * +keygrab_ssh1(con *c) { static Key *rsa; static Buffer msg; @@ -252,12 +274,12 @@ buffer_init(&msg); rs...

...+ */ + if (s == i) + break; +/* + * Save fd of first "touch"ed entry. If we encounter it again, we'll + * know that we've cycled through all of the original queue. + */ + contouch(s); /* a fresh timeout for fdcon[s] */ + if (i < 0) + i = s; + + c = TAILQ_NEXT(c, c_link); + } + + conntimedout = 0; + + return; + } + +/* + * If we have the "connclosed" condition, the read failed because the + * remote server closed the connection before sending the key. All hosts + * that currently have a viable "fdcon[s]" entry will be recycled below + * to n...

Hello, I'm running 6.4-PRELEASE, last built on 2008-10-05 with /usr/src updated on the same day. I had a panic that looks to me very similiar to the one described here (hence the subject): http://lists.freebsd.org/pipermail/freebsd-stable/2008-September/045405.html What caught my curiosity is the message: Unread portion of the kernel message buffer: acd0: WARNING - TEST_UNIT_READY read