headers
hunreal | 1 Sep 2006 05:35
Picon

kern/102737: Panic at SMP kernel


>Number:         102737
>Category:       kern
>Synopsis:       Panic at SMP kernel
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Sep 01 03:40:16 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     hunreal
>Release:        6.1-STABLE
>Organization:
>Environment:
FreeBSD work 6.1-STABLE FreeBSD 6.1-STABLE #0: Fri Sep  1 09:25:15 CST 2006    
root <at> work:/usr/src/sys/i386/compile/SMP  i386

>Description:
OS panic while running SMP kernel, but work fine while non-SMP kernel.
It is a Web Server with Apache 2.2.3 worker MPM, PHP 5.1.6.
I have been tried 6.1-RELEASE, 6.1-STABLE, both are the same problem.
Attached kernel coredump backtrace,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Dan Burzynski | 1 Sep 2006 11:19
Favicon

kern/102741: Multiple outbound connect() calls produce 'Network is unreachable'


>Number:         102741
>Category:       kern
>Synopsis:       Multiple outbound connect() calls produce 'Network is unreachable'
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Sep 01 09:20:26 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Dan Burzynski
>Release:        6.1
>Organization:
Moo
>Environment:
FreeBSD hendrix.moocards.com 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May  7 04:42:56 UTC 2006    
root <at> opus.cse.buffalo.edu:/usr/obj/usr/src/sys/SMP  i386
>Description:
When doing multiple (but not nessesarlity concurrent) outbound socket connections (such as using HTTP)
we're seeing the error message 'Network is unreachable' after a random amount. It then persists for a
while and then we're back to it working for a little while.

I've run a tcpdump and it seems that the point at which it complains that the network is unreachable, it's not
(Continue reading)

Permalink | Reply | 0 comments |
headers
Lapo Luchini | 1 Sep 2006 12:02
Picon
Favicon
Gravatar

bin/102745: "mount -o snapshot" removes any existing "-o" option from the mount


>Number:         102745
>Category:       bin
>Synopsis:       "mount -o snapshot" removes any existing "-o" option from the mount
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Sep 01 10:10:22 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Lapo Luchini
>Release:        FreeBSD 6.1-STABLE i386
>Organization:
>Environment:
System: FreeBSD cyberx.home.lapo.it 6.1-STABLE FreeBSD 6.1-STABLE #59: Thu Jun 8 22:17:18 CEST 2006
root <at> cyberx.home.lapo.it:/usr/obj/usr/src/sys/CYBERX i386

>Description:

(edited for shortness, showing only relevant lines)

% mount                           
/dev/ad0s1f on /usr (ufs, local, soft-updates, acls)
(Continue reading)

Permalink | Reply | 0 comments |
headers
Sergey Zaharchenko | 1 Sep 2006 13:02
Picon
Favicon

bin/102747: ppp timer subsystem stops under certain circumstances


>Number:         102747
>Category:       bin
>Synopsis:       ppp timer subsystem stops under certain circumstances
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Sep 01 11:10:21 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Sergey Zaharchenko
>Release:        FreeBSD 7.0-CURRENT i386
>Organization:
Volgograd State Technical University
>Environment:
System: FreeBSD shark.localdomain 7.0-CURRENT FreeBSD 7.0-CURRENT #1:
Mon Aug 28 15:41:24 UTC 2006
root <at> shark.localdomain:/var/obj/src/usr.src/sys/GENERIC i386
>Description:
There are certain situations which cause the ppp timer subsystem to stop
(that is, there are timers in the list, but none of them ever get
triggered). This is caused by calling setitimer() with a zero it_value
in timer_InitService(). Killing ppp with SIGALRM triggers the first
(Continue reading)

Permalink | Reply | 0 comments |
headers
Václav Haisman | 1 Sep 2006 17:34
Picon
Picon
Gravatar

kern/102752: malloc(M_WAITOK) of "g_bio", forcing M_NOWAIT with non-sleepable locks held


>Number:         102752
>Category:       kern
>Synopsis:       malloc(M_WAITOK) of "g_bio", forcing M_NOWAIT with non-sleepable locks held
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Sep 01 15:40:20 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Václav Haisman
>Release:        6.1
>Organization:
SU SH
>Environment:
FreeBSD logout.sh.cvut.cz 6.1-STABLE FreeBSD 6.1-STABLE #0: Thu Aug 10 00:33:03 CEST 2006    
root <at> logout.sh.cvut.cz:/usr/obj/usr/src/sys/LOGOUT  i386
>Description:
+malloc(M_WAITOK) of "g_bio", forcing M_NOWAIT with the following non-sleepable locks held:
+exclusive sleep mutex inp (tcpinp) r = 0 (0xc50c5d38) locked  <at>  /usr/src/sys/netinet/tcp_usrreq.c:1029
+KDB: stack backtrace:
+kdb_backtrace(c08eef84,e78be89c,1,c45752c0,c1035380) at kdb_backtrace+0x2f
+witness_warn(5,0,c0819ce0,c07fc905,c05eaca1) at witness_warn+0x1ac
(Continue reading)

Permalink | Reply | 0 comments |
headers
Robert Watson | 1 Sep 2006 18:28
Picon
Favicon

Re: kern/102752: malloc(M_WAITOK) of "g_bio", forcing M_NOWAIT with non-sleepable locks held

Synopsis: malloc(M_WAITOK) of "g_bio", forcing M_NOWAIT with non-sleepable locks held

Responsible-Changed-From-To: freebsd-bugs-≥rwatson
Responsible-Changed-By: rwatson
Responsible-Changed-When: Fri Sep 1 16:26:32 UTC 2006
Responsible-Changed-Why: 
Grab ownership of this PR, since it is of interest to me.  The fix here
is to drop the inpcb lock before going near copyin/copyout, but the
tricky bit is that the connection may change state while the lock is
dropped, so the path from the socket to the inpcb/tcpcb must be
re-evaluated, and the timewait state checked for.  In HEAD this is
easier since the inpcb can't go away, but in -STABLE we need to check
that so_pcb is still non-NULL also, as the connection could have been
reset.

I'll work on a patch for this in the near future.

http://www.freebsd.org/cgi/query-pr.cgi?pr=102752
_______________________________________________
freebsd-bugs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
Brooks Davis | 1 Sep 2006 18:34
Picon
Favicon

Re: misc/102724: rc.initdiskless does not copy hidden files

Synopsis: rc.initdiskless does not copy hidden files

State-Changed-From-To: open->patched
State-Changed-By: brooks
State-Changed-When: Fri Sep 1 16:33:47 UTC 2006
State-Changed-Why: 
Committed to HEAD.  Thanks!

Responsible-Changed-From-To: freebsd-bugs-≥brooks
Responsible-Changed-By: brooks
Responsible-Changed-When: Fri Sep 1 16:33:47 UTC 2006
Responsible-Changed-Why: 
Committed to HEAD.  Thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=102724
_______________________________________________
freebsd-bugs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe <at> freebsd.org"
Permalink | Reply | 1 comment |
headers
Stefan Bethke | 1 Sep 2006 18:56
Picon

Re: kern/102607: [if_bridge] don't generate random L2 address

Here's my suggestion for an addition to if_bridge(4):

--- if_bridge.4.orig    Sun Aug 13 20:44:18 2006
+++ if_bridge.4 Fri Sep  1 18:53:19 2006
 <at>  <at>  -107,6 +107,13  <at>  <at> 
in
.Xr rc.conf 5 .
.Pp
+The
+.Nm
+interface randomly chooses a link (MAC) address in the range  
reserved for
+locally adminstered addresses when it is created.
+The address can be changed by assigning the desired link address using
+.Xr ifconfig 8 .
+.Pp
The MTU of the first member interface to be added is used as the  
bridge MTU.
All additional members are required to have exactly the same value.
.Pp
 <at>  <at>  -231,6 +238,16  <at>  <at> 
      addm fxp6 stp fxp6 \e
      addm fxp7 stp fxp7 \e
      up
+.Ed
+.Pp
+The bridge can be used as a regular host interface at the same time as
+bridging between it's member ports. In this example, the bridge  
connects em0
+and em1, and will receive it's IP address through DHCP:
(Continue reading)

Permalink | Reply | 1001 comments |
headers
Eric Anholt | 1 Sep 2006 19:24
Picon
Favicon

kern/102760: iwi firmware load fails after significant uptime


>Number:         102760
>Category:       kern
>Synopsis:       iwi firmware load fails after significant uptime
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Sep 01 17:30:22 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator:     Eric Anholt
>Release:        FreeBSD 6.1-STABLE i386
>Organization:
>Environment:
System: FreeBSD vonnegut.anholt.net 6.1-STABLE FreeBSD 6.1-STABLE #4: Wed Jul 12 11:59:44 PDT 2006
root <at> vonnegut.anholt.net:/usr/obj/usr/src/6-stable/sys/MYKERNEL i386

	
>Description:
	My daily routine with my laptop involves using wireless networking at
	home, going to a coffeeshop on a different ssid, or going to work with
	wired ethernet, and coming home.  When I re-dhclient at a new location,
	or sometimes at just random times while using the wireless and
(Continue reading)

Permalink | Reply | 0 comments |
headers
Sam Leffler | 2 Sep 2006 00:20
Picon
Favicon

Re: kern/84861: [ipw] [patch] still can't get working ipw(4) with adhoc

Synopsis: [ipw] [patch] still can't get working ipw(4) with adhoc

Responsible-Changed-From-To: freebsd-bugs-≥sam
Responsible-Changed-By: sam
Responsible-Changed-When: Fri Sep 1 22:19:46 UTC 2006
Responsible-Changed-Why: 
I will deal with ipw issues

http://www.freebsd.org/cgi/query-pr.cgi?pr=84861
_______________________________________________
freebsd-bugs <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bugs
To unsubscribe, send any mail to "freebsd-bugs-unsubscribe <at> freebsd.org"
Permalink | Reply | 2 comments |

Gmane