Displaying 5 results from an estimated 5 matches for "c_links".
Did you mean:
c_link
2009 Jan 24
4
panic in callout_reset: bad link in callwheel
...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 a...
2001 May 14
2
openssh-2.9p1
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
2001 Jul 27
0
Updated ssh-keyscan patch for ssh2 support
In the past 2 months another change occurred in the CVS code that
broke my ssh-keyscan patch. Here's an updated version that tweaks the
changed name (in the Kex struct) and also causes an attempt to grab an
ssh2 key from an older server (without ssh2 support) to fail earlier
and without an error message (Stuart Pearlman emailed me some code for
this).
This patch is based on the BSD CVS
2012 Nov 24
0
ssh-keyscan continuity patch --
I apologize, this patch should have been sent awhile ago. Between a lot
of things that needed to be completed at work as a sysadmin for the
Research Computing group at Purdue University and retiring from work
after 38 years at the end of May (2012), I basically ignored it. This
patch is from a clone of my workstation that I just activated at home.
The patch was primarily written to fix the
2008 Oct 11
3
6.4-PRELEASE sporadically panicking with fatal trap 12
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