Re: Entropy harvesting? Grim reaper is more like it...

2001-03-12 Thread Matthew Jacob


Wait a minute. isn't this all old mail being resent? What's going on?


> > I did a buildworld/installworld on an alpha yesterday, and now I'm left with:
> > 
> > start_init: trying /sbin/init
> > Entropy harvesting: interrupts ethernet.
> > 
> > 
> > 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...

2001-03-12 Thread Matthew Jacob

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.

John- both you && David have seen this. Both Doug && I have working 4100s.

It's not the same issue, I believe.


>  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.

I don't believe it's this issue.



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...

2001-03-12 Thread Matthew Jacob

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.

Again, as per previous, that didn't show anything.

WHen I have a tad more time today or tomorrow, I'll try and narrow it further.



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...

2001-03-12 Thread Matthew Jacob



> > 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.

That did not fix the problem. Only disabling interrupt harvesting fixed it.

> 
> 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: Entropy harvesting? Grim reaper is more like it...

2001-03-11 Thread Doug Rabson

On Sat, 10 Mar 2001, David O'Brien wrote:

> On Fri, Mar 09, 2001 at 01:39:58PM -0800, Matthew Jacob wrote:
> > > Erm, just so you know.  The 4100 here at WC doesn't even make it past
> > > the SCSI probe due to interrupt issues.
> >
> > Hmm. Well, it *was* working a couple of days ago :-)
>
> Uh, actually _your_ 4100 is the only I've ever known to work on
> post-SMPng.  The WC 4100 has *never* worked on post SMPng.  I don't
> believe I've heard that DFR's runs SMPng either.
>
> I guess I should get a `dd' of your system disk, or get you a console on
> the WC box.

My 4100 was working after the last set of mcpcia fixes. I haven't updated
it for about a week so it may be broken again I guess.

-- 
Doug Rabson Mail:  [EMAIL PROTECTED]
Phone: +44 20 8348 6160



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...

2001-03-10 Thread Matthew Jacob




> On Fri, Mar 09, 2001 at 01:39:58PM -0800, Matthew Jacob wrote:
> > > Erm, just so you know.  The 4100 here at WC doesn't even make it past
> > > the SCSI probe due to interrupt issues.
> >
> > Hmm. Well, it *was* working a couple of days ago :-)
> 
> Uh, actually _your_ 4100 is the only I've ever known to work on
> post-SMPng.  The WC 4100 has *never* worked on post SMPng.  I don't
> believe I've heard that DFR's runs SMPng either.

That's strange. After each time I've gotten this working again (and it now
works on the 4100 here *AND* the ones at NASA/Ames) I've sent mail saying "Try
yours again" to you! I thougt you *were* working again.

> I guess I should get a `dd' of your system disk, or get you a console on
> the WC box.

Well, since I have *two* working systems- one of which is a four hose
configuration, I don't know quite what to say... :-) I should just bring
one of my disks by. urrmm.. Actually, one system has a DDS tape drive so
I'll dd you a root disk image- it'll be da2 so you'll have to shove disks
ahead of it or DTRT.

-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...

2001-03-10 Thread David O'Brien

On Fri, Mar 09, 2001 at 01:39:58PM -0800, Matthew Jacob wrote:
> > Erm, just so you know.  The 4100 here at WC doesn't even make it past
> > the SCSI probe due to interrupt issues.
>
> Hmm. Well, it *was* working a couple of days ago :-)

Uh, actually _your_ 4100 is the only I've ever known to work on
post-SMPng.  The WC 4100 has *never* worked on post SMPng.  I don't
believe I've heard that DFR's runs SMPng either.

I guess I should get a `dd' of your system disk, or get you a console on
the WC box.
 
-- 
-- David  ([EMAIL PROTECTED])
  GNU is Not Unix / Linux Is Not UniX

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...

2001-03-09 Thread Matthew Jacob

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



Re: Entropy harvesting? Grim reaper is more like it...

2001-03-09 Thread John Baldwin


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...

2001-03-09 Thread Matthew Jacob


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...

2001-03-09 Thread Matthew Jacob

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...

2001-03-09 Thread Matthew Jacob

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: Entropy harvesting? Grim reaper is more like it...

2001-03-09 Thread Matthew Jacob

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...

2001-03-09 Thread Mark Murray

> 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...

2001-03-09 Thread Kris Kennaway

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...

2001-03-09 Thread Matthew Jacob


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.
> > 
> > 
> > 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...

2001-03-09 Thread Mark Murray

> I did a buildworld/installworld on an alpha yesterday, and now I'm left with:
> 
> start_init: trying /sbin/init
> Entropy harvesting: interrupts ethernet.
> 
> 
> 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
-- 
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