In article <[EMAIL PROTECTED]>,
Brian Fundakowski Feldman  <[EMAIL PROTECTED]> wrote:
> If this is a problem with sbsize, this should take care of any possibility
> ever of there being a problem...

I tried your patch, but it panics reliably on start-up:

Automatic boot in progress...
/dev/da0s1a: clean, 335363 free (8667 frags, 40837 blocks, 1.1% fragmentation)
/dev/da0s1e: clean, 1966150 free (46222 frags, 239991 blocks, 1.0% fragmentation)
Doing initial network setup: hostname.
panic: reducing sbsize: lost count, uid = 0
Stopped at      Debugger+0x34:  movb    $0,in_Debugger.390
db> trace
Debugger(c0280363) at Debugger+0x34
panic(c027fc80,0,2400,0,c7c20f74) at panic+0x70
chgsbsize(0,c7c20f78,2400,ffffffff,7fffffff) at chgsbsize+0x33
sbreserve(c7c20f74,2400,c7c20f00,c77ee440) at sbreserve+0x6a
soreserve(c7c20f00,2400,a280,c7c20f00,c02bb368) at soreserve+0x1c
udp_attach(c7c20f00,0,c77ee440,0,c86f6f80) at udp_attach+0x2a
socreate(2,c86f6f20,2,0,c77ee440) at socreate+0xe8
socket(c77ee440,c86f6f80,8085098,bfbffda0,3) at socket+0x3e
syscall2(2f,2f,2f,3,bfbffda0) at syscall2+0x1f1
Xint0x80_syscall() at Xint0x80_syscall+0x25

The value of *hiwat in chgsbsize() is 0:

db> x/ul 0xc7c20f78
0xc7c20f78:     0

I can't get it to generate a core dump that it will recognize on
reboot, and I'm not set up for remote gdb on this machine.  But I can
check anything you'd like with ddb.

  John Polstra                                               [EMAIL PROTECTED]
  John D. Polstra & Co., Inc.                        Seattle, Washington USA
  "Disappointment is a good sign of basic intelligence."  -- Chögyam Trungpa

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

Reply via email to