Re: New improved panic!
0xc0147290 is in random_kthread (../../dev/random/yarrow.c:97).
92 mtx_lock(Giant);
93 printf("OWNERSHIP Giant == %d sched_lock == %d\n",
94 mtx_owned(Giant), mtx_owned(sched_lock));
95 mtx_unlock(Giant);
96 #endif
97
98 for (pl = 0; pl 2; pl++)
99 yarrow_hash_init(random_state.pool[pl].hash, NULL, 0);
100
101 for (;;) {
Is DEBUG defined?
M
--
Mark Murray
Warning: this .sig is umop ap!sdn
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Panic mounting msdos fs
On 09-Mar-01 Andrea Campi wrote: Hi John, didn't have time to reply to your previous email (I was sleeping ;-)) before getting this. Do you still need the dump? No, jlemon and I figured it out on irc. I'm not sure why it's broken yet. On 08-Mar-01 Andrea Campi wrote: Yesterday -current: It seems modules are broken with witness right now. Before you were ok as long as you didn't unload the darn things, now they seem to be toast altogether, so you will want to use a static kernel for now until this is fixed. Doesn't it warrant a very big HEADSUP? Probably, they've already been partially broken, though the partial brokenness that I know how to fix will be fixed hopefully before too long. I'm not sure yet why sticking a mutex in a kld causes us to walk off a NULL pointer. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Unable to process your message
We are unable to process the message from [EMAIL PROTECTED] to [EMAIL PROTECTED]. The email address used to send your message is not subscribed to this group. If you are a member of this group, please be aware that you may only send messages and manage your subscription to this group using the email address(es) you have registered with Yahoo! Groups. Yahoo! Groups allows you to use the email address you originally used to register, or an alternate email address you specify in your personal settings. If you would like to subscribe to this group: 1. visit http://groups.yahoo.com/group/HipHopProductions/join -OR- 2. send email to [EMAIL PROTECTED] If you would like to specify an alternate email address: 1. visit http://groups.yahoo.com/myprefs?edit=2 2. type your alternate email address in the area labeled "Alternate posting addresses". 3. click the "Save Changes" button 4. wait approximately 10 minutes for the change to take effect After you follow these steps, you will be able to send messages to all your groups using this alternate email address. For further assistance, please email [EMAIL PROTECTED] or visit http://help.yahoo.com/help/us/groups DIE!!
PR bin/25110 - pthreads signal handling problem
I'm wondering if anyone has the time or inclination to take a look at a fix for PR bin/25110. We're having problems using a freshly-built 4.2-stable box (technically 4.3 rc at this point), and the bug is still present. I'm not sure how many people would see this problem (we see it because we have to compile Apache 1.x with the -pthread switch due to add-on modules that are threaded). Under 4.1-stable, everything was fine. At some point between 4.1-stable and 4.2-release, something changed, but my hunt through the CVS repository hasn't revealed anything obvious. In any case, it's a repeatable bug (the PR includes a code sample) and unless looked at, it will be a bug in 4.3-release. If there's any clarification needed, please let me know. TIA. -- j. James FitzGibbon [EMAIL PROTECTED] Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Entropy harvesting? Grim reaper is more like it...
I changed nothing from whatever the default is. It seems like a bit of POLA to freeze now. But I'll check this - if I can get that machine up again :-)... I did a buildworld/installworld on an alpha yesterday, and now I'm left with: start_init: trying /sbin/init Entropy harvesting: interrupts ethernet. hangs And this is even with booting from an older kernel. Umm... anyone gotta clue on this one? You have your entropy device set to block on boot? M To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Entropy harvesting? Grim reaper is more like it...
On Fri, Mar 09, 2001 at 09:32:29AM -0800, Matthew Jacob wrote: I changed nothing from whatever the default is. It seems like a bit of POLA to freeze now. But I'll check this - if I can get that machine up again :-)... Press ^T when it freezes and see if it's just blocked in rndslp or truly frozen. Kris PGP signature
Re: Entropy harvesting? Grim reaper is more like it...
I changed nothing from whatever the default is. It seems like a bit of POLA to freeze now. But I'll check this - if I can get that machine up again :-)... OK - if this is the entropy driver, then typing about 2 lines of shit will unlock it. Please put some echo's into the rc scripts to tie down where this is happening. M -- Mark Murray Warning: this .sig is umop ap!sdn To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Entropy harvesting? Grim reaper is more like it...
On Fri, 9 Mar 2001, Kris Kennaway wrote: On Fri, Mar 09, 2001 at 09:32:29AM -0800, Matthew Jacob wrote: I changed nothing from whatever the default is. It seems like a bit of POLA to freeze now. But I'll check this - if I can get that machine up again :-)... Press ^T when it freezes and see if it's just blocked in rndslp or truly frozen. Not being a csh/tcsh user, I of course didn't think of that! Thanks! To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Entropy harvesting? Grim reaper is more like it...
On Fri, 9 Mar 2001, Mark Murray wrote: I changed nothing from whatever the default is. It seems like a bit of POLA to freeze now. But I'll check this - if I can get that machine up again :-)... OK - if this is the entropy driver, then typing about 2 lines of shit will unlock it. I did try the typing trick... but that didn't help. lemme power this sucker on (it's the big 4100- I keep it off unless I'm working on it specifically- it sucks down lots of power and we're still supposedly in 'conserve' mode in California...) Please put some echo's into the rc scripts to tie down where this is happening. M To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PR bin/25110 - pthreads signal handling problem
On Fri, 9 Mar 2001, James FitzGibbon wrote:
I'm wondering if anyone has the time or inclination to take a look at a fix
for PR bin/25110. We're having problems using a freshly-built 4.2-stable
box (technically 4.3 rc at this point), and the bug is still present.
I'm not sure how many people would see this problem (we see it because we
have to compile Apache 1.x with the -pthread switch due to add-on modules
that are threaded). Under 4.1-stable, everything was fine. At some point
between 4.1-stable and 4.2-release, something changed, but my hunt through
the CVS repository hasn't revealed anything obvious.
In any case, it's a repeatable bug (the PR includes a code sample) and
unless looked at, it will be a bug in 4.3-release.
If there's any clarification needed, please let me know.
You can try the included patch.
--
Dan Eischen
Index: uthread_fork.c
===
RCS file: /opt/FreeBSD/cvs/src/lib/libc_r/uthread/uthread_fork.c,v
retrieving revision 1.21
diff -u -r1.21 uthread_fork.c
--- uthread_fork.c 2001/01/24 13:03:33 1.21
+++ uthread_fork.c 2001/03/09 17:53:37
@@ -32,6 +32,7 @@
* $FreeBSD: src/lib/libc_r/uthread/uthread_fork.c,v 1.21 2001/01/24
13:03:33 deischen Exp $
*/
#include errno.h
+#include signal.h
#include string.h
#include stdlib.h
#include unistd.h
@@ -110,7 +111,16 @@
else if (_pq_init(_readyq) != 0) {
/* Abort this application: */
PANIC("Cannot initialize priority ready queue.");
- } else {
+ } else if ((_thread_sigstack.ss_sp == NULL)
+ ((_thread_sigstack.ss_sp = malloc(SIGSTKSZ)) == NULL))
+ PANIC("Unable to allocate alternate signal stack");
+ else {
+ /* Install the alternate signal stack: */
+ _thread_sigstack.ss_size = SIGSTKSZ;
+ _thread_sigstack.ss_flags = 0;
+ if (__sys_sigaltstack(_thread_sigstack, NULL) != 0)
+ PANIC("Unable to install alternate signal stack");
+
/*
* Enter a loop to remove all threads other than
* the running thread from the thread list:
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: New improved panic!
Mark Murray [EMAIL PROTECTED] writes: Is DEBUG defined? Nope. DES -- Dag-Erling Smrgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Entropy harvesting? Grim reaper is more like it...
On Fri, 9 Mar 2001, Mark Murray wrote: I changed nothing from whatever the default is. It seems like a bit of POLA to freeze now. But I'll check this - if I can get that machine up again :-)... OK - if this is the entropy driver, then typing about 2 lines of shit will unlock it. Neither ^T or typing does anything. I'll have to do some surgery from another boot disk to find out what's what. Uk. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Entropy harvesting? Grim reaper is more like it...
I commented out all of the Entropy stuff at the front of rc and I was able to finish booting again. I'll do another buildworld/installworld and buildkernel/installkernel to see whether the problem re-appears. I'll leave the 'set -x' in my rc when I retest. I noticed the (re)appearance of a line which had caused problems in the past (the 'ps' generation foo). I'd really appreciate if the following would occur: 1. The entropy stuff gets it's own rc file. There's a lot of it. 2. You make it an option we can turn off sourcing it from rc. Also- we should really consider whether or not the breakage that has happened three or four times now is telling us something. This attempt to reseed entropy seems to be riskier than not having the entropy reseeded at all! :-) If this entropy stuff is all that important, maybe we should consider having this done entirely within the kernel as part of the config state tree (and not as a kmod or an option) so that a simple non-blocking sysctl early in RC can get you what you want. That is, by the time you call /sbin/init, you have gathered enough entropy. Or if you cannot do so (which I would imagine could actually be a true statement as all I/O results are *generally* pretty predictable until you turn on networking), can you do it *after* the system is almost all the way up? I guess I'm saying I don't want to have to get hung up like this any more. Please. -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Entropy harvesting? Grim reaper is more like it...
On 09-Mar-01 Matthew Jacob wrote: On Fri, 9 Mar 2001, Mark Murray wrote: I changed nothing from whatever the default is. It seems like a bit of POLA to freeze now. But I'll check this - if I can get that machine up again :-)... OK - if this is the entropy driver, then typing about 2 lines of shit will unlock it. Neither ^T or typing does anything. I'll have to do some surgery from another boot disk to find out what's what. Uk. Erm, just so you know. The 4100 here at WC doesn't even make it past the SCSI probe due to interrupt issues. If it's running really up to date current, try changing sys/alpha/include/mutex.h to define mtx_intr_enable() to nothing, which will hackishly run ithreads with a raised IPL and might solve the problem if its an interrupt storm you are seeing. -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Entropy harvesting? Grim reaper is more like it...
On Fri, 9 Mar 2001, John Baldwin wrote: On 09-Mar-01 Matthew Jacob wrote: On Fri, 9 Mar 2001, Mark Murray wrote: I changed nothing from whatever the default is. It seems like a bit of POLA to freeze now. But I'll check this - if I can get that machine up again :-)... OK - if this is the entropy driver, then typing about 2 lines of shit will unlock it. Neither ^T or typing does anything. I'll have to do some surgery from another boot disk to find out what's what. Uk. Erm, just so you know. The 4100 here at WC doesn't even make it past the SCSI probe due to interrupt issues. If it's running really up to date current, try changing sys/alpha/include/mutex.h to define mtx_intr_enable() to nothing, which will hackishly run ithreads with a raised IPL and might solve the problem if its an interrupt storm you are seeing. Hmm. Well, it *was* working a couple of days ago :-) -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
