This will not fix the problem. I even removed rev 1.57-1.58 and it
still causes gdb to lockup the system.
Szilveszter Adam ([EMAIL PROTECTED]) wrote:
Hello everybody!
ps 2000/12/29 16:44:44 PST
Modified files:
sys/kern sys_process.c
Log:
Pass me the
On Fri, Dec 29, 2000 at 10:57:10PM +0100, Szilveszter Adam wrote:
Hi!
Maybe this is related, maybe not... I upgraded to the latest CURRENT
available this morning and now I also see occasional (albeit short) hangs
sometimes, although the machine seems to be responsive otherwise.
But, not
On Fri, Dec 29, 2000 at 04:19:38PM -0800, Alfred Perlstein wrote:
I'd appreciate it if those who are having issues with gdb were to
try this patch and let me know if it fixes things.
Sorry, but gdb keeps hanging my box after this patch.
In fact, the behaviour didn't changed.
Index:
This gives an almost -current kernel without the hangs:
setenv TZ PST8PDT
cvs -q update -P -d -D "2000-12-26 10:00"
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never
panic: lockable mtx_enter() of lockmgr interlock when not legal @
../../kern/kern_lock.c: 247
which is
mtx_enter(lkp-lk_interlock, MTX_DEF);
my system is an i386 UP with two dc cards and a kernel configured as
follows:
machine i386
cpu I586_CPU
cpu I686_CPU
Please respond directly to [EMAIL PROTECTED] as I am not on this mailing
list..
I am hoping that this is not something I am doing wrong ... the procedur
ei followed was cvsup src and ports... using supfile in handbook for
going to current.. from there i did /usr/src make buildworld then make
On Sat, Dec 30, 2000 at 09:41:08AM -0600, Michael Harnois wrote:
panic: lockable mtx_enter() of lockmgr interlock when not legal @
../../kern/kern_lock.c: 247
Hello!
OK, so since nobody has done it before me, I just decided to investigate a
bit. Remember, that I am not a kernel hacker, so I
My isp's router is sending me IGMP queries.
18:25:07.850008 212.242.151.2 224.0.0.1: 212.242.151.2 224.0.0.1: igmp
v2 query [intvl 10]igmp query [ttl 1]
I think it keeps my user-ppp connection open, even if I have this rule in my
firewall:
$fwcmd add 65432 deny ip from 212.242.151.2 to any
On Sat, Dec 30, 2000 at 11:58:05AM -0500, Raymond Hicks wrote:
Please respond directly to [EMAIL PROTECTED] as I am not on this mailing
list..
I am hoping that this is not something I am doing wrong ... the procedur
ei followed was cvsup src and ports... using supfile in handbook for
POSIX says that getlogin_r should return an int, not a char *. Our
implementation is also broken; it will only work the first time.
Since we've already bumped libc version number, anyone mind if I
fix it?
--
Dan Eischen
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe
A checkin was just made that fixed a mutex that was being held incorrectly
in psignal, which features in your stack trace.
It's possible that this has been fixed in the last 24 hours.
Szilveszter Adam wrote:
On Sat, Dec 30, 2000 at 09:41:08AM -0600, Michael Harnois wrote:
panic: lockable
On 30-Dec-00 Paul Saab wrote:
This will not fix the problem. I even removed rev 1.57-1.58 and it
still causes gdb to lockup the system.
Try backing out the proctree lock.
--
John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/
PGP Key: http://www.Baldwin.cx/~john/pgpkey.asc
On 30-Dec-00 Michael Harnois wrote:
panic: lockable mtx_enter() of lockmgr interlock when not legal @
../../kern/kern_lock.c: 247
which is
mtx_enter(lkp-lk_interlock, MTX_DEF);
We need to know where interrupts were disabled (since that is what makes the
blockable mtx_enter() not legal).
On Sat, Dec 30, 2000 at 11:46:15AM -0800, Julian Elischer wrote:
A checkin was just made that fixed a mutex that was being held incorrectly
in psignal, which features in your stack trace.
It's possible that this has been fixed in the last 24 hours.
Hello Julian!
If you are referring to the
On Sat, Dec 30, 2000 at 12:08:48PM -0800, John Baldwin wrote:
On 30-Dec-00 Michael Harnois wrote:
panic: lockable mtx_enter() of lockmgr interlock when not legal @
../../kern/kern_lock.c: 247
which is
mtx_enter(lkp-lk_interlock, MTX_DEF);
We need to know where interrupts were
On Sat, Dec 30, 2000 at 12:23:58PM -0800, John Baldwin wrote:
On 30-Dec-00 Szilveszter Adam wrote:
On Sat, Dec 30, 2000 at 12:08:48PM -0800, John Baldwin wrote:
On 30-Dec-00 Michael Harnois wrote:
panic: lockable mtx_enter() of lockmgr interlock when not legal @
On 30-Dec-00 Szilveszter Adam wrote:
On Sat, Dec 30, 2000 at 12:23:58PM -0800, John Baldwin wrote:
On 30-Dec-00 Szilveszter Adam wrote:
On Sat, Dec 30, 2000 at 12:08:48PM -0800, John Baldwin wrote:
On 30-Dec-00 Michael Harnois wrote:
panic: lockable mtx_enter() of lockmgr interlock
On Sat, Dec 30, 2000 at 12:36:36PM -0800, John Baldwin wrote:
That's ok. I seem to have goofed up in kern_sig.c. Please try the (untested)
patch at http://www.FreeBSD.org/~jhb/patches/kern_sig.patch.
OK, trying it right now... it applied cleanly, but it will take sometime
until the compile
On Sat, Dec 30, 2000 at 12:36:36PM -0800, John Baldwin wrote:
That's ok. I seem to have goofed up in kern_sig.c. Please try the (untested)
patch at http://www.FreeBSD.org/~jhb/patches/kern_sig.patch.
Well, the kernel is ready and the patch appears to work. Ie I can run a
large dirlisting on
A bug in specfs's fsync dating back to Kirk's original softupdates work
( which required a similar mark/scan fix to the FFS fsync ) appears to
have been exposed by recent pageout peformance commits I made.
I've committed a mark/scan fix to specfs's fsync, which appears
to
On Sat, Dec 30, 2000 at 18:32 +0100, Leif Neland wrote:
My isp's router is sending me IGMP queries.
18:25:07.850008 212.242.151.2 224.0.0.1: 212.242.151.2
224.0.0.1: igmp v2 query [intvl 10]igmp query [ttl 1]
Ask your provider to not do it. :) Do you run any multicast
enabled
Hello!
I just wanted to tell you quickly that you can scrap the vague reports I
made about network problems yesterday... (including ssh and ftp hangs...)
*Sigh...* I thought I was quite sure it was a FreeBSD problem, processes
really appeared to be hung. And besides, never thought that packet
22 matches
Mail list logo