Re: /dev permissions after reboot (and panic)

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:Content-Type: text/plain; charset=us-ascii
:Content-Disposition: inline
:
:So every time I reboot, I get a panic (I believe someone else may
:be having this problem too).  I've included a capture of the ddb
:session at the bottom.  Unfortunately, I can't get a core dump.
:But, what really sucks, is if I did a 'MAKEDEV all', permissions
:in /dev get hosed when the machine comes back up.  MAKEDEV is doing
:the right thing, because I've checked to make sure the devices
:have the correct permissions.  When the machine comes back up,
:things like null, zero, tty, lose their write permissions, which
:hoses things up.
:
:A copy of the kernel can be found on leaf:~pavalos/public/kernel.0713
:or at:
:
:http://www.theshell.com/~pavalos/crash/kernel.0713
:
:Here's the ddb session (hand-typed):

    Are you rebooting just after doing the MAKEDEV or are the permissions
    hosed after you run MAKEDEV and check them, before rebooting? 

    If the permissions are getting hosed after the reboot see if a few
    'sync' commands and a pause before 'reboot' works around that problem.
    I will try to reproduce the MAKEDEV issue on my test box.

    Which patch set is this with?  The m_nextpkt != NULL is a warning
    rather a panic, but the patch set I sent today should have fixed that.
    The actual panic is occuring due to the buffers not being flushable, 
    which sounds like a softupdates issue so if the sync commands don't
    fix the problem (or even if they do).  See if turning off softupdates 
    fixes the problem (which will tell me where to look).

						-Matt

:giving up on 7 buffers
:Debugger("Busy buffer problem")
:
:CPU1 stopping CPUs: 0x00000001
: stopped
:Stopped at      Debugger+0x44:  movb    $0,in_Debugger.0
:db> panic
:panic: from debugger
:mp_lock = 00000001; cpuid = 1; lapic.id = 06000000
:Trace beginning at frame 0xded829f0
:panic(c02c65b1,6000000,c02c2de4,ded82a20,0) at panic+0xd9
:panic(c02c2de4,ded82aec,c01394b2,c028e0e7,0) at panic+0xd9
:db_command_loop(c028e0e7,0,ffffffff,ded82a50,ded82a4c) at db_command_loop
:db_command(c03132b0,c02ef5e0,c02ea1d4,c02ea1ec,ded82b20) at db_command+0x2b1
:db_command_loop(c028e0e7,c0367d40,c0317880,1,0) at db_command_loop+0x75
:db_trap(3,0,1,1,ded82b6c) at db_trap+0xc8
:kdb_trap(3,0,ded82b74,0,0) at kdb_trap+0x17b
:trap(18,10,ded80010,0,c3f35ea0) at trap+0x55e
:calltrap() at calltrap+0xc
:--- trap 0x3, eip = 0xc028e0e7, esp = 0xded82bb4, ebp = 0xded82bbc ---
:Debugger(c02c64bc,7,0,7,7) at Debugger+0x44
:boot(0,ded82d40,c02a63ce,ded82c24,ded82d10) at boot+0x2dc
:reboot(ded82c24,ded82d10,4,deb82500,1) at reboot+0x2c
:syscall2(2f,2f,2f,0,0) at syscall2+0x28a
:Xint0x80_syscall() at Xint0x80_syscall+0x2a
:boot() called on cpu#1
:Uptime: 5m46s
:LWKT_WAIT_IPIQ WARNING! 1 wait 0 (-1)
:panic: LWKT_WAIT_IPIQ
:mp_lock = 00000001; cpuid = 1; lapic.id = 06000000
:boot() called on cpu#1
:Uptime: 5m46s
:LWKT_WAIT_IPIQ WARNING! 1 wait 0 (-2)
:panic: LWKT_WAIT_IPIQ
:mp_lock = 00000001; cpuid = 1; lapic.id = 06000000
:boot() called on cpu#1
:Uptime: 5m46s
:LWKT_WAIT_IPIQ WARNING! 1 wait 0 (-3)
:panic: LWKT_WAIT_IPIQ
:mp_lock = 00000001; cpuid = 1; lapic.id = 06000000
:boot() called on cpu#1
:Uptime: 5m46s
:
:At this point, I just power-cycled the machine...
:
:--fdj2RfSjLxBAspz7
:Content-Type: application/pgp-signature
:Content-Disposition: inline
:
:-----BEGIN PGP SIGNATURE-----
:Version: GnuPG v1.4.1 (DragonFly)
:
:iD4DBQFC2aZqKjaxugguz8URAo9iAJjSVptf65Y44yOGT4/9zQYOlkuqAKCMox24
:9dDS4m3wsNhMdksKM2mSDg==
:=pHtG
:-----END PGP SIGNATURE-----
:
:--fdj2RfSjLxBAspz7--
:

					Matthew Dillon 
					<dillon@xxxxxxxxxxxxx>