Old Synopsis: iwn(4) causes page fault on interface up
New Synopsis: [iwn] iwn(4) causes page fault on interface up
Responsible-Changed-From-To: freebsd-bugs->freebsd-net
Responsible-Changed-By: linimon
Responsible-Changed-When: Tue Dec 8 02:57:52 UTC 2009
Responsible-Changed-Why:
Over to maintai
David Christensen wrote:
Can the bge driver use more than one MSI message? If
possible, what the advantage of this on a SMP system (better
CPU distribution on interrupts?)?
[...]
--
MSI is broken on this device (actually all PCI/PCI-X devices
in the 57XX family). The interrupt will be a
On 7 Dec 2009, at 13:21, Paul B Mahol wrote:
Patch attached to fix scan results.
Bug is obvious if you use -v flag:
ifconfig -v wlan0 list scan
It is interesting, that it never got noticed. I got hit with this one
when working on WPA instead of WPA2(RSN). In that case wpa_supplicant
would never
> Can the bge driver use more than one MSI message? If
> possible, what the advantage of this on a SMP system (better
> CPU distribution on interrupts?)?
>
> I have an Broadcom BCM5703X, with 8 MSI messages:
> --
> b...@pci0:1:2:0:class=0x02 card=0x00cb0e11
> chip=0x16a714e4 rev=0x02
>
Oups, everything is OK with route-to and reply-to in pf, my bad.
config for my situation must be like this
scrub in all fragment reassemble
pass in quick reply-to (em0 10.60.128.254) inet from any to
10.60.128.0/24 flags S/SA keep state
pass in quick reply-to (em0 10.70.128.254) inet from any to
1
Pyun YongHyeon wrote:
> On Mon, Dec 07, 2009 at 11:43:50AM -0800, Chris Cowart wrote:
>> Pyun YongHyeon wrote:
>>> On Sun, Dec 06, 2009 at 06:17:46PM -0800, Chris Cowart wrote:
On a related note, last night, when the system did boot, I would
also run into a problem where the following mes
On Mon, Dec 07, 2009 at 11:43:50AM -0800, Chris Cowart wrote:
> Pyun YongHyeon wrote:
> > On Sun, Dec 06, 2009 at 06:17:46PM -0800, Chris Cowart wrote:
> >> Having read the PR, I copied sys/dev/{msk,e1000} from HEAD into the
> >
> > I think the PR has nothing to do with this issue.
>
> You're rig
Pyun YongHyeon wrote:
> On Sun, Dec 06, 2009 at 06:17:46PM -0800, Chris Cowart wrote:
>> Having read the PR, I copied sys/dev/{msk,e1000} from HEAD into the
>
> I think the PR has nothing to do with this issue.
You're right. I found it when I was hunting for an explanation to the
hanging that see
On Friday 04 December 2009 09:47:37 Lytochkin Boris wrote:
> It seems that FreeBSD 8 has ipfw fwd and pf's route-to malfunctioning:
> 1) ipfw fwd
> a) net.inet.ip.forwarding = 0
> Packets altered by fwd rule are silently dropped somewhere
> between ip_output() checking forward tag and bpf (tcpdum
On Sun, Dec 06, 2009 at 06:17:46PM -0800, Chris Cowart wrote:
> Hello,
>
> I recently upgraded my home router box to 8.0. Since doing so, I've had
> some problems with the msk driver.
>
> On startup, I'm experiencing the behavior that seems to be documented in
> kern/139093. Specifically, during
The following reply was made to PR kern/106438; it has been noted by GNATS.
From: Pyun YongHyeon
To: Mark Abene
Cc: freebsd-net@freebsd.org, bug-follo...@freebsd.org, dar...@freebsd.org
Subject: Re: kern/106438: [ipf] ipfilter: keep state does not seem to allow
replies in on spar64 (and maybe o
On Mon, Dec 07, 2009 at 01:40:04AM +, Mark Abene wrote:
> The following reply was made to PR kern/106438; it has been noted by GNATS.
>
> From: Mark Abene
> To: bug-follo...@freebsd.org, m...@hinterbergen.de
> Cc:
> Subject: Re: kern/106438: [ipf] ipfilter: keep state does not seem to allow
Hi
After upgrade RELENG_8 -> 9-CURRENT following line in rc.con does not
work any more for me. (after boot no alias address on loop-back
interface).
ifconfig_lo0_alias0="127.0.0.2/32"
console output while is usual, without errors, but does not shows
required address:
---
Starting Network: lo0
On 12/7/09 2:48 PM, Bruce Simpson wrote:
> Andriy Syrovenko wrote:
>> Is it planned to be MFCed to STABLE?
>> Or, could you possibly point me into the right revision in HEAD, so I
>> could merge and test it locally?
>>
> Actually I did already MFC most of my changes to stable/8, just not
> relen
Andriy Syrovenko wrote:
Is it planned to be MFCed to STABLE?
Or, could you possibly point me into the right revision in HEAD, so I
could merge and test it locally?
Actually I did already MFC most of my changes to stable/8, just not
releng/8.0.
There were a few things to do with IGMP packet
Patch attached to fix scan results.
Bug is obvious if you use -v flag:
ifconfig -v wlan0 list scan
It is interesting, that it never got noticed. I got hit with this one
when working on WPA instead of WPA2(RSN). In that case wpa_supplicant
would never pick AP because it doesnt see WPA, it could see
Creation/destroying vlans with parent em interface leads to link flap:
root# date;ifconfig vlan4000 create vlan 4000 vlandev em1 10.0.0.1/30;sleep
5;tail -7 /var/log/kern.log
Mon Dec 7 15:18:38 MSK 2009
Dec 7 15:18:38 g kernel: vlan4000: bpf attached
Dec 7 15:18:38 g kernel: em1: Link is Do
Is it planned to be MFCed to STABLE?
Or, could you possibly point me into the right revision in HEAD, so I
could merge and test it locally?
2009/12/7 Bruce Simpson :
> I believe this *may* have been fixed in HEAD, but was one of the things
> which couldn't be MFCed due to the RC freeze...
>
__
Note: to view an individual PR, use:
http://www.freebsd.org/cgi/query-pr.cgi?pr=(number).
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including
experimental development code and obsolete releases.
S Tracker
I believe this *may* have been fixed in HEAD, but was one of the things
which couldn't be MFCed due to the RC freeze...
___
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "free
The following reply was made to PR kern/138666; it has been noted by GNATS.
From: Andriy Syrovenko
To: bug-follo...@freebsd.org, univers...@ukr.net
Cc:
Subject: Re: kern/138666: [multicast] [panic] not working multicast through
igmpproxy
Date: Mon, 7 Dec 2009 11:56:11 +0200
I'd like
21 matches
Mail list logo
