headers
Peter Much | 1 Apr 2008 01:20

Re: kern/122126: [ed] [panic] panic when using WD-8013 with ed(4)

The following reply was made to PR kern/122126; it has been noted by GNATS.

From: Peter Much <pmc <at> citylink.dinoex.sub.org>
To: bug-followup <at> FreeBSD.org
Cc: Volker Werth <vwe <at> FreeBSD.org>
Subject: Re: kern/122126: [ed] [panic] panic when using WD-8013 with ed(4)
Date: Tue, 1 Apr 2008 01:00:23 +0200

 I tried to find out some more:

 1. The panic happens only when pinging to an existing station on the
    BNC network.
    Pinging to a non-existent address will give the correct "host is
    down" message.

 2. I tried to add 
    > makeoptions DEBUG=-g
    to my kernel config and rebuilt. 
    But when running this kernel, it gives the same behaviour as
    the GENERIC kernel: it shows multiple panics scrolling off the
    screen and then freezes. It does not try to dump.

 3. I did boot without acpi. No difference.
_______________________________________________
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 | 0 comments |
headers
Sean Farley | 1 Apr 2008 01:33
Picon
Favicon

kern/122318: Segmentation fault when running Linux cmake


>Number:         122318
>Category:       kern
>Synopsis:       Segmentation fault when running Linux cmake
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Mon Mar 31 23:40:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Sean Farley
>Release:        FreeBSD 7.0-STABLE i386
>Organization:
>Environment:
System: FreeBSD thor.farley.org 7.0-STABLE FreeBSD 7.0-STABLE #0: Sat Mar 29 15:00:16 CDT 2008
sean <at> thor.farley.org:/usr/FreeBSD/RELENG_7/obj/usr/FreeBSD/RELENG_7/src/sys/THOR i386

>Description:
I have a build chroot based upon FC2--please do not shoot me--that had
worked in the past with RELENG_6 on an i386 box.  I moved to RELENG_7 on
an amd64 box.  For some reason, running cmake core dumps regardless if
it is my FC2 chroot or linux_base-fc{4,6}.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Simas Kvilius | 1 Apr 2008 01:52
Picon

kern/122319: [wi] imposible to enable ad-hoc demo mode with Orinoco Gold PC card


>Number:         122319
>Category:       kern
>Synopsis:       [wi] imposible to enable ad-hoc demo mode with Orinoco Gold PC card
>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:   Tue Apr 01 00:00:03 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Simas Kvilius
>Release:        7.0
>Organization:
Home
>Environment:
>Description:
I'm using old Lucent orinoco wireless card in ad-hoc demo mode.
It seems someone forgot to implement ad-hoc demo mode in the newest wi
driver (driver which comes with RELENG7). I added  following statement
to if_wi.c line 407 to indicate, that my card supports ad-hoc demo
mode (someone definitely forgot to include this):

ic->ic_caps |= IEEE80211_C_AHDEMO;
(Continue reading)

Permalink | Reply | 0 comments |
headers
Simas Kvilius | 1 Apr 2008 01:59
Picon

[wi] Lucent Orinoco gold card ad-hoc demo mode

I'm using old Lucent orinoco wireless card in ad-hoc demo mode.
It seems someone forgot to implement ad-hoc demo mode in the newest wi
driver (driver which comes with RELENG7). I added  following statement
to if_wi.c line 407 to indicate, that my card supports ad-hoc demo
mode (someone definitely forgot to include this):

ic->ic_caps |= IEEE80211_C_AHDEMO;

Now I can enable ad-hoc demo mode using ifconfig utility (with command
ifconfig wi0 mode 11b media DS/11Mbps mediaopt adhoc mediaopt flag0),
but it seems there is another bug. Now I cannot change radio channel
(nic is always stuck in channel 3, i think this channel is hardcoded
as default ibss channel inside my nic).
System accepts ifconfig wi0 channel 13 command, but ifconfig wi0 shows
no changes in channel configuration.

Could anyone fix this bug with channels (I tried to figure out where
problem is, but it seems I'm to lame to do kernel hacking of this
level by myself). My card was working fine with FreeBSD 5.1 (both with
ifconfig and wicontrol tools) and Linux.

Regards,
Simas
_______________________________________________
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 | 0 comments |
headers
Paul Hoffman | 1 Apr 2008 03:42
Gravatar

misc/122320: Need to use ipv6_enable="YES" even when it is obvious


>Number:         122320
>Category:       misc
>Synopsis:       Need to use ipv6_enable="YES" even when it is obvious
>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:   Tue Apr 01 01:50:01 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     Paul Hoffman
>Release:        7.0-RELEASE
>Organization:
self
>Environment:
FreeBSD justv6.proper.com 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Sun Feb 24 19:59:52 UTC 2008    
root <at> logan.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386
>Description:
/etc/rc.conf has:
ipv6_network_interfaces="sis0"
ifconfig_sis0="inet6 2001:470:8095::2 prefixlen 48"
ipv6_defaultrouter="2001:470:8095::1"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Marcin Cieslak | 1 Apr 2008 03:53
Picon

Re: ports/121953: (workaround) openoffice.org-2.3.1 hangs with Glib errors

linimon <at> FreeBSD.org wrote:
> Synopsis: (workaround) openoffice.org-2.3.1 hangs with Glib errors
> 
> Responsible-Changed-From-To: freebsd-bugs-≥openoffice
> Responsible-Changed-By: linimon
> Responsible-Changed-When: Sat Mar 22 06:12:32 UTC 2008
> Responsible-Changed-Why: 
> Make this a ports PR and assign.

Can you try adding --with-system-zlib to your port Makefile
CONFIGURE_ARGS and recompile OpenOffice?

--- Makefile    28 Mar 2008 22:26:03 -0000      1.295
+++ Makefile    31 Mar 2008 23:34:46 -0000
 <at>  <at>  -140,7 +140,8  <at>  <at> 
 CONFIGURE_ARGS+=       --with-gnu-cp=${LOCALBASE}/bin/gcp              \
                        --with-gnu-patch=${LOCALBASE}/bin/gpatch        \
                        --enable-crashdump=yes                          \
-                       --enable-symbols=SMALL
+                       --enable-symbols=TRUE                           \
+                       --with-system-zlib
 .if ${ARCH} == amd64
 WITHOUT_MOZILLA=       yes
 LIB_DEPENDS+=          boost_regex:${PORTSDIR}/devel/boost

I think this is it:

http://lists.freebsd.org/pipermail/freebsd-openoffice/2007-December/003453.html

--Marcin
(Continue reading)

Permalink | Reply | 2 comments |
headers
David LeCount | 1 Apr 2008 03:52
Picon
Favicon

misc/122321: Hitachi SCSI drive can't be written to


>Number:         122321
>Category:       misc
>Synopsis:       Hitachi SCSI drive can't be written to
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Apr 01 02:00:05 UTC 2008
>Closed-Date:
>Last-Modified:
>Originator:     David LeCount
>Release:        FreeBSD 7 Stable I386
>Organization:
>Environment:
FreeBSD bahamut 7.0-STABLE FreeBSD 7.0-STABLE #0: Thu Feb 28 21:30:24 UTC 2008    
root <at> bahamut:/usr/obj/usr/src/sys/BAHAMUT_NEW  i386
>Description:
I have a Hitachi Ultrastar 15K147 SCSI hard drive connected to an LSILogic 1030 adapter running a recent
cvsup of FreeBSD 7 Stable I386. I am able to use fdisk to read the partition table, but any write I attempt
gives an input/output error, including simply using dd to zero the drive. Upon boot, I get a big list of
error messages, pasted below from dmesg. They don't occur if I simply unplug the drive with the adapter
still enabled.
(Continue reading)

Permalink | Reply | 0 comments |
headers
remko | 1 Apr 2008 08:40
Picon
Favicon

Re: kern/122319: [wi] imposible to enable ad-hoc demo mode with Orinoco Gold PC card

Synopsis: [wi] imposible to enable ad-hoc demo mode with Orinoco Gold PC card

Responsible-Changed-From-To: freebsd-bugs-≥freebsd-net
Responsible-Changed-By: remko
Responsible-Changed-When: Tue Apr 1 06:39:55 UTC 2008
Responsible-Changed-Why: 
reassign to networking team

http://www.freebsd.org/cgi/query-pr.cgi?pr=122319
_______________________________________________
freebsd-net <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe <at> freebsd.org"
Permalink | Reply | 752 comments |
headers
remko | 1 Apr 2008 08:40
Picon
Favicon

Re: kern/122318: [linux] [cmake]: Segmentation fault when running Linux cmake

Old Synopsis: Segmentation fault when running Linux cmake
New Synopsis: [linux] [cmake]: Segmentation fault when running Linux cmake

Responsible-Changed-From-To: freebsd-bugs-≥freebsd-emulation
Responsible-Changed-By: remko
Responsible-Changed-When: Tue Apr 1 06:40:26 UTC 2008
Responsible-Changed-Why: 
reassign to emulation team

http://www.freebsd.org/cgi/query-pr.cgi?pr=122318
_______________________________________________
freebsd-emulation <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-emulation
To unsubscribe, send any mail to "freebsd-emulation-unsubscribe <at> freebsd.org"
Permalink | Reply | 0 comments |
headers
remko | 1 Apr 2008 08:41
Picon
Favicon

Re: misc/122320: Need to use ipv6_enable="YES" even when it is obvious

Synopsis: Need to use ipv6_enable="YES" even when it is obvious

State-Changed-From-To: open->closed
State-Changed-By: remko
State-Changed-When: Tue Apr 1 06:41:46 UTC 2008
State-Changed-Why: 
This is not a problem record item, but something that might need
discussion. Though I think this was done on purpose to let people
explicitly enable IPv6 instead of letting it go loose on the internet
without additional configuration.

http://www.freebsd.org/cgi/query-pr.cgi?pr=122320
_______________________________________________
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 | 0 comments |

Gmane