Panic during kernel booting on HP Proliant DL180G6 and latest STABLE

2011-05-08 Thread Bartosz Stec

Hi list!

I moved my 8-STABLE system from cheap AMD64 machine to Proliant DL180G6 
(full ZFS send -> receive) yesterday.
Operation was succesfull, system booted and everything worked fine. 
Still, I wanted to perform full world + kernel rebuild with updated 
sources and CPUTYPE (core2 instead of athlon64) and removed unused NIC 
drivers from kernel.


New kernel panicked during boot. I rebuilt kernel again, without any 
CPUTYPE in make.conf, but panic was still there. Old kernel (built at 
8.04.2011) is booting fine.

First panic line says:

   panic: m_getzone: m_getjcl: invalid cluster type.


I made a por quality photo of screen with stack backtrace and it's 
available here: http://www.picamatic.com/view/7544359_IMAG0029/


Now the funny thing:

Igb driver is compiled into the kernel. If I add igb driver to 
loader.conf kernel complains of course:


   module_register: module pci/igb already exists!
   Module pci/igb failed to register: 17


but there's no panic!

When I remove 'if_igb_load="YES"' from loader.conf, I experience panic 
visible above.


Kernel config: http://pastebin.com/G7K0vfuJ


--
Bartosz Stec


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


test

2011-05-08 Thread Jason Hellenthal

hackers,

Test

-- 

 Regards, (jhell)
 Jason Hellenthal

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: test

2011-05-08 Thread Jason Hellenthal

hackers,

On Sun, May 08, 2011 at 01:54:18PM -0400, Jason Hellenthal wrote:
> 
> hackers,
> 
> Test
> 

My appologies. this message was never supposed to leave the outbox. 
Instead of hitting one key I hit another. Please disregard.


Thanks.

-- 

 Regards, (jhell)
 Jason Hellenthal

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: Panic during kernel booting on HP Proliant DL180G6 and latest STABLE

2011-05-08 Thread Bartosz Stec

W dniu 2011-05-08 16:02, Bartosz Stec pisze:

Hi list!

I moved my 8-STABLE system from cheap AMD64 machine to Proliant 
DL180G6 (full ZFS send -> receive) yesterday.
Operation was succesfull, system booted and everything worked fine. 
Still, I wanted to perform full world + kernel rebuild with updated 
sources and CPUTYPE (core2 instead of athlon64) and removed unused NIC 
drivers from kernel.


New kernel panicked during boot. I rebuilt kernel again, without any 
CPUTYPE in make.conf, but panic was still there. Old kernel (built at 
8.04.2011) is booting fine.

First panic line says:

   panic: m_getzone: m_getjcl: invalid cluster type.


I made a por quality photo of screen with stack backtrace and it's 
available here: http://www.picamatic.com/view/7544359_IMAG0029/


Now the funny thing:

Igb driver is compiled into the kernel. If I add igb driver to 
loader.conf kernel complains of course:


   module_register: module pci/igb already exists!
   Module pci/igb failed to register: 17


but there's no panic!

When I remove 'if_igb_load="YES"' from loader.conf, I experience panic 
visible above.


Kernel config: http://pastebin.com/G7K0vfuJ


Picamatic seems offline now, so here's another link to backtrace photo: 
http://i51.tinypic.com/nyuux3.jpg


Maybe make.conf will be useful too:

   CPUTYPE?=core2
   KERNCONF=PROLIANT
   #MAKEOPTS=-j3
   #WITH_DEBUG=yes
   #DEBUG_FLAGS=-g

   # default build settings for ports collection
   .if ${.CURDIR:M*/ports/*} && !defined(NOCCACHE)
   CFLAGS=-O2 -pipe
   #CXXFLAGS= -O2 -fno-strict-aliasing -pipe -funroll-loops
   BUILD_OPTIMIZED=YES
   WITH_OPENSSL=YES
   WITH_XCHARSET=all
   WITH_CHARSET=utf8
   WITH_COLLATION=utf8_general_ci
   .endif

   # default build settings for base system
   .if ${.CURDIR:M*/usr/src/*} || ${.CURDIR:M*/usr/obj/*} &&
   !defined(NOCCACHE)

   CFLAGS=-O2 -pipe
   COPTFLAGS=-O2 -pipe

   CC:=${CC:C,^cc,/usr/local/libexec/ccache/world/cc,1}
   CXX:=${CXX:C,^c\+\+,/usr/local/libexec/ccache/world/c++,1}

   .endif

   # added by use.perl 2011-05-08 17:13:51
   PERL_VERSION=5.10.1



--
Bartosz Stec


___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


[RFC][Change-Request] Create usefulness in rc.subr etc/rc.conf.d/*.conf namespace.

2011-05-08 Thread Jason Hellenthal

List, - Please reply-to freebsd...@freebsd.org

Recently I have been going over some changes in the configurations that 
are possible with the rc subsystem and to my dismay I have found some 
inconsistencies with in particular the way rc.conf.d directory is 
processed and the arguments that are supplied to load_rc_config so I have 
patched it up...

Let me explain:  As determined by rc.subr load_rc_config, config's from 
rc.conf.d are loaded by the scripts $name as an argument to load_rc_config 
and thus only the name being parsed is is available to be used in the 
rc.conf.d directory. Why is this bad ? Its not! but it is inconvenient as 
the user has no direct way to know that a variable used by nfsd is also 
needed by mountd or the same for various other scripts in the rc.d 
directory. At this time these config's are explained to be available for 
the user to utilize by rc.conf(5) but yet without much knowledge of the 
inner workings of the rc subsystem it would be quite the feat to do.


The attachment[1] keeps this functionality the same while introducing a 
more convenient approach for the user to modularize their configuration 
however they see fit within a couple constraints that work very well. 


What does it do ?: As stated above, current functionality is undisturbed 
while allowing the user to create config's by any name they so desire as 
long as it has an extension of ".conf", also introducing the ability to 
turn a configuration file off by using chmod(1). You can turn nfsc1.conf
off/on by simply chmod [-/+]x etc/rc.conf.d/nfs1.conf


Why ? Simple. How many times have you been bitten by disabling something 
in the rc.conf file and left to discover what you just disabled was also 
used by another daemon but that daemon is now not starting ? This is a way 
to virtualize your configuration allowing you to add multiple _enable= 
lines to different configurations for different roles. For instance 
rpcbind is used by both samba and nfs*. With this you can add 
rpcbind_enable to both a configuration for samba and nfs and when you 
disable one service you know that you have not disabled a dependent for 
another.


This is a small addition that fixes currently broken undesirable aspects 
of the configuration system that deals with the rc.conf.d directory with a 
SysV style init approach that is just as flexible. This should apply 
cleanly to current and stable/8 & 8.2-RELEASE systems. Once more feedback 
has been received Ill update the manual page with any suggestions 
regenerate the patch to accommodate and file a PR.


1). http://patches.jhell.googlecode.com/hg/rc.subr_modular_conf.patch


Thanks

-- 

 Regards, (jhell)
 Jason Hellenthal



pgp2JDj2HJ4jZ.pgp
Description: PGP signature


Re: test

2011-05-08 Thread Chip Camden
Quoth Jason Hellenthal on Sunday, 08 May 2011:
> hackers,
> 
> On Sun, May 08, 2011 at 01:54:18PM -0400, Jason Hellenthal wrote:
> > 
> > hackers,
> > 
> > Test
> > 
> 
> My appologies. this message was never supposed to leave the outbox. 
> Instead of hitting one key I hit another. Please disregard.
> 

Nevertheless, it's good advice.

-- 
.O. | Sterling (Chip) Camden  | http://camdensoftware.com
..O | sterl...@camdensoftware.com | http://chipsquips.com
OOO | 2048R/D6DBAF91  | http://chipstips.com


pgpLkvPQPChSO.pgp
Description: PGP signature