Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)

2006-04-03 Thread Scott Long

Matthew Jacob wrote:


I must have missed something here. What's the problem that causes
contigmalloc to be called here? If this is to do with  4GB of memory, that
was fixed in -CURRENT over a month ago.



He's using 6.0-RELEASE.

Scott

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)

2006-04-03 Thread Ganbold

Kris Kennaway wrote:

On Mon, Apr 03, 2006 at 02:27:31PM +0900, Ganbold wrote:
  

Kris Kennaway wrote:


On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote:
 
  

Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE.
Boot takes 3-4 minutes after da0: 140014MB (286749488 512 byte sectors: 
255H 63S/T 17849C) line and continues.
I will try to upgrade again to 6.1-PRERELEASE later today. I did before 
and the problem still was there.
   


The mpt driver calls contigmalloc in a way that takes ages to run
because it was poorly rewritten some time ago.  Scottl partially fixed
it on 7.0 (after the problem became much worse there - it was taking
over 40 minutes instead of 4) but the change is not complete enough to
back-port yet.
 
  

I see. Yes, it eventually becomes up after 3-4 minutes.
However what annoying is every time I reboot/restart the server
I have to manually press Enter key. How can I resolve this issue?



Please explain what you mean: why do you have to manually press Enter?
  
It is not booting, - appears on screen and waits forever. When I press 
Enter

key on keyboard it starts booting.

Ganbold


Kris

  


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)

2006-04-03 Thread Kris Kennaway
On Mon, Apr 03, 2006 at 03:15:54PM +0900, Ganbold wrote:
 Kris Kennaway wrote:
 On Mon, Apr 03, 2006 at 02:27:31PM +0900, Ganbold wrote:
   
 Kris Kennaway wrote:
 
 On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote:
  
   
 Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE.
 Boot takes 3-4 minutes after da0: 140014MB (286749488 512 byte 
 sectors: 255H 63S/T 17849C) line and continues.
 I will try to upgrade again to 6.1-PRERELEASE later today. I did before 
 and the problem still was there.

 
 The mpt driver calls contigmalloc in a way that takes ages to run
 because it was poorly rewritten some time ago.  Scottl partially fixed
 it on 7.0 (after the problem became much worse there - it was taking
 over 40 minutes instead of 4) but the change is not complete enough to
 back-port yet.
  
   
 I see. Yes, it eventually becomes up after 3-4 minutes.
 However what annoying is every time I reboot/restart the server
 I have to manually press Enter key. How can I resolve this issue?
 
 
 Please explain what you mean: why do you have to manually press Enter?
   
 It is not booting, - appears on screen and waits forever. When I press 
 Enter
 key on keyboard it starts booting.

That's a completely separate issue.  I don't know why it's happening
though.

Kris


pgpAcJlxDBp7s.pgp
Description: PGP signature


Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)

2006-04-03 Thread Matthew Jacob



On Mon, 3 Apr 2006, Scott Long wrote:


Matthew Jacob wrote:


I must have missed something here. What's the problem that causes
contigmalloc to be called here? If this is to do with  4GB of memory, that
was fixed in -CURRENT over a month ago.



He's using 6.0-RELEASE.



A reason to allow an MFC ? :-)

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)

2006-04-03 Thread Scott Long

Matthew Jacob wrote:




On Mon, 3 Apr 2006, Scott Long wrote:


Matthew Jacob wrote:


I must have missed something here. What's the problem that causes
contigmalloc to be called here? If this is to do with  4GB of 
memory, that

was fixed in -CURRENT over a month ago.



He's using 6.0-RELEASE.



A reason to allow an MFC ? :-)



I'm fully intending for it to get MFC'd, I just want a chance to test
it in our FC environment first so that any problems don't become
emergencies.

Scott

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)

2006-04-03 Thread Ganbold

Kris Kennaway wrote:

On Mon, Apr 03, 2006 at 03:15:54PM +0900, Ganbold wrote:
  

Kris Kennaway wrote:


On Mon, Apr 03, 2006 at 02:27:31PM +0900, Ganbold wrote:
 
  

Kris Kennaway wrote:
   


On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote:

 
  

Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE.
Boot takes 3-4 minutes after da0: 140014MB (286749488 512 byte 
sectors: 255H 63S/T 17849C) line and continues.
I will try to upgrade again to 6.1-PRERELEASE later today. I did before 
and the problem still was there.
  
   


The mpt driver calls contigmalloc in a way that takes ages to run
because it was poorly rewritten some time ago.  Scottl partially fixed
it on 7.0 (after the problem became much worse there - it was taking
over 40 minutes instead of 4) but the change is not complete enough to
back-port yet.

 
  

I see. Yes, it eventually becomes up after 3-4 minutes.
However what annoying is every time I reboot/restart the server
I have to manually press Enter key. How can I resolve this issue?
   


Please explain what you mean: why do you have to manually press Enter?
 
  
It is not booting, - appears on screen and waits forever. When I press 
Enter

key on keyboard it starts booting.



That's a completely separate issue.  I don't know why it's happening
though.
  


Same problem exists under FreeBSD-6.1-PRERELEASE, machine is not 
booting, - appears on screen and waits forever. When I press Enter 
key on keyboard it starts booting.
On CURRENT even worse, I tested yesterday's CURRENT, boot panics saying 
CPU class not configured.


Ganbold



Kris
  


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)

2006-04-02 Thread Ganbold

Kris Kennaway wrote:

On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote:
  

Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE.
Boot takes 3-4 minutes after da0: 140014MB (286749488 512 byte sectors: 
255H 63S/T 17849C) line and continues.
I will try to upgrade again to 6.1-PRERELEASE later today. I did before 
and the problem still was there.



The mpt driver calls contigmalloc in a way that takes ages to run
because it was poorly rewritten some time ago.  Scottl partially fixed
it on 7.0 (after the problem became much worse there - it was taking
over 40 minutes instead of 4) but the change is not complete enough to
back-port yet.
  

I see. Yes, it eventually becomes up after 3-4 minutes.
However what annoying is every time I reboot/restart the server
I have to manually press Enter key. How can I resolve this issue?
Is there any known solution?
In any case I will try first RELENG_6 then CURRENT on this machine.

thanks,

Ganbold

Kris


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)

2006-04-02 Thread Kris Kennaway
On Mon, Apr 03, 2006 at 02:27:31PM +0900, Ganbold wrote:
 Kris Kennaway wrote:
 On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote:
   
 Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE.
 Boot takes 3-4 minutes after da0: 140014MB (286749488 512 byte sectors: 
 255H 63S/T 17849C) line and continues.
 I will try to upgrade again to 6.1-PRERELEASE later today. I did before 
 and the problem still was there.
 
 
 The mpt driver calls contigmalloc in a way that takes ages to run
 because it was poorly rewritten some time ago.  Scottl partially fixed
 it on 7.0 (after the problem became much worse there - it was taking
 over 40 minutes instead of 4) but the change is not complete enough to
 back-port yet.
   
 I see. Yes, it eventually becomes up after 3-4 minutes.
 However what annoying is every time I reboot/restart the server
 I have to manually press Enter key. How can I resolve this issue?

Please explain what you mean: why do you have to manually press Enter?

Kris



pgpqSTt0JsDWE.pgp
Description: PGP signature


RE: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4)

2006-04-02 Thread Matthew Jacob
I must have missed something here. What's the problem that causes
contigmalloc to be called here? If this is to do with  4GB of memory, that
was fixed in -CURRENT over a month ago.

-Original Message-
From: Ganbold [mailto:[EMAIL PROTECTED] 
Sent: Sunday, April 02, 2006 10:28 PM
To: Kris Kennaway
Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED];
freebsd-stable@FreeBSD.org
Subject: Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370
G4)


Kris Kennaway wrote:
 On Mon, Apr 03, 2006 at 12:56:57PM +0900, Ganbold wrote:
   
 Here is dmes.boot and pciconf output on FreeBSD-6.0-RELEASE.
 Boot takes 3-4 minutes after da0: 140014MB (286749488 512 byte sectors: 
 255H 63S/T 17849C) line and continues.
 I will try to upgrade again to 6.1-PRERELEASE later today. I did before 
 and the problem still was there.
 

 The mpt driver calls contigmalloc in a way that takes ages to run
 because it was poorly rewritten some time ago.  Scottl partially fixed
 it on 7.0 (after the problem became much worse there - it was taking
 over 40 minutes instead of 4) but the change is not complete enough to
 back-port yet.
   
I see. Yes, it eventually becomes up after 3-4 minutes.
However what annoying is every time I reboot/restart the server
I have to manually press Enter key. How can I resolve this issue?
Is there any known solution?
In any case I will try first RELENG_6 then CURRENT on this machine.

thanks,

Ganbold
 Kris


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]