Re: Is wi with problems in RELENG_4_5?

[Paulo Fragoso]

We have already found same problem caused by conflicts using an ISA
pccard adpter, but this problema was a bit different we couldn't start the
traffic anyway. Now all works fine by 8 until 30 hours for this problem to
happen.

We've changed pccard for one new Avaya Wireless without firmeware upgrade
and we found same problem.

Our dmesg and pccard log is:

/kernel: FreeBSD 4.5-RELEASE-p4 #0: Mon May  6 10:28:58 BRT 2002
/kernel: Timecounter "i8254"  frequency 1193182 Hz
/kernel: CPU: Pentium II/Pentium II Xeon/Celeron (334.09-MHz 686-class
CPU)
/kernel: Origin = "GenuineIntel"  Id = 0x660  Stepping = 0
/kernel:
Features=0x183f9ff
/kernel: real memory  = 67108864 (65536K bytes)
/kernel: avail memory = 60424192 (59008K bytes)
/kernel: Preloaded elf kernel "kernel" at 0xc046e000.
/kernel: Pentium Pro MTRR support enabled
/kernel: md0: Malloc disk
/kernel: Using $PIR table, 7 entries at 0xc00f8740
/kernel: npx0:  on motherboard
/kernel: npx0: INT 16 interface
/kernel: pcib0:  on motherboard
/kernel: pci0:  on pcib0
/kernel: pcib1:  at device
1.0 on pci0
/kernel: pci1:  on pcib1
/kernel: pci1:  at 0.0 irq 11
/kernel: isab0:  at device 7.0 on pci0
/kernel: isa0:  on isab0
/kernel: atapci0:  port 0xffa0-0xffaf at
device 7.1 on pci0
/kernel: ata0: at 0x1f0 irq 14 on atapci0
/kernel: uhci0:  port
0xef80-0xef9f irq 10 at device 7.2 on pci0
/kernel: usb0:  on uhci0
/kernel: usb0: USB revision 1.0
/kernel: uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
/kernel: uhub0: 2 ports with 2 removable, self powered
/kernel: chip1:  port
0x5f00-0x5f0f at device 7.3 on pci0
/kernel: rl0:  port 0xec00-0xecff mem
0xffafff00-0xffaf irq 11 at device 15.0 on pci0
/kernel: rl0: Ethernet address: 00:e0:4c:e2:14:76
/kernel: miibus0:  on rl0
/kernel: rlphy0:  on miibus0
/kernel: rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
/kernel: pci_cfgintr_search: linked (61) to configured irq 11 at 0:15:0
/kernel: pci_cfgintr: 0:16 INTA routed to irq 11
/kernel: pcic0:  irq 11 at device 16.0 on
pci0
/kernel: pcic0: PCI Memory allocated: 0x4400
/kernel: pcic0: TI12XX PCI Config Reg: [pwr save][CSC parallel isa irq]
/kernel: pccard0:  on pcic0
/kernel: orm0:  at iomem 0xc-0xc7fff on isa0
/kernel: fdc0:  at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2
on isa0
/kernel: fdc0: FIFO enabled, 8 bytes threshold
/kernel: atkbdc0:  at port 0x60,0x64 on isa0
/kernel: vga0:  at port 0x3c0-0x3df iomem 0xa-0xb
on isa0
/kernel: sc0:  at flags 0x100 on isa0
/kernel: sc0: VGA <16 virtual consoles, flags=0x300>
/kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
/kernel: sio0: type 16550A
/kernel: sio1: configured irq 3 not in bitmap of probed irqs 0
/kernel: ppc0: parallel port not found.
/kernel: DUMMYNET initialized (011031)
/kernel: IP packet filtering initialized, divert enabled, rule-based
forwarding enabled, default to accept, unlimited logging
/kernel: ad0: 4125MB  [8940/15/63] at ata0-master
UDMA33
/kernel: Mounting root from ufs:/dev/ad0s1a
/kernel: pccard: card inserted, slot 0
/kernel: pccard: card removed, slot 0
/kernel: pccard: card inserted, slot 0
pccardd[50]: Card "Avaya Communication"("Avaya Wireless PC Card") [Version
01.01] [] matched "Avaya Communication" ("Avaya Wireless PC Card")
[(null)] [(null)]
squid[324]: Squid Parent: child process 327 started
/kernel: wi0:  at port 0x240-0x27f irq 11 slot 0 on
pccard0
/kernel: wi0: Ethernet address: 00:02:2d:3f:82:77
pccardd[50]: wi0: Avaya Communication (Avaya Wireless PC Card) inserted.
pccard:wi0: Avaya Wireless PC Card inserted
pccardd[50]: pccardd started

Now in this router we are rebooting when it can't reach the wireless
network.

Thanks,
Paulo.

On Fri, 10 May 2002, Fred Clift wrote:

>
> I saw similar symptoms when I had either irq or io-range conflicts with a
> symbol card using the wi driver on my nortel emobility (rebadged Symbol
> la-3141) card.  There is a section in the netbsd handbook that tells of
> such conflicts with their version of the wi driver and some suggested ways
> of fixing it.
>
> Honestly, I ended up giving up on my problem.  (could get the symbol card
> to work fine by itself, but add a second pcmcia network card ed0 and
> neither would work right).  I eventually installed netbsd on the 'wirless
> router'...
>
> Fred
>
>
> On Fri, 10 May 2002, Paulo Fragoso wrote:
>
> > Hi,
> >
> > We have got some wireless routers using lucent cards (WaveLAN/IEEE
> ...
> >
> > /kernel: wi0: xmit failed
> > /kernel: wi0: watchdog timeout
> > /kernel: wi0: init failed
> > /kernel: wi0: failed to allocate 1594 bytes on NIC
> > /kernel: wi0: tx buffer allocation failed
> > /kernel: wi0: failed to allocate 1594 bytes on NIC
> > /kernel: wi0: mgmt. buffer allocation failed
> > /kernel: wi0: timeout in wi_seek to 0/0; last status 4000
> > /kernel: wi0: timeout in wi_seek to 0/44; last status 4044
> >
>
>
>
> --
> Fred Clift - [EMAIL PROTECTED] -- Remember: If brute
> force doesn't work, you're just not using enough.
>

-- 
   __O
 _-\<,_ Why d

Cluster allocation errors in messages

[Thomas Gravgaard]

I have been getting a massive amount of the following errors in my messages over the 
last couple of weeks :

> m_clalloc failed, consider increase NMBCLUSTERS value
> fxp0: cluster allocation failed, packet dropped!

As far as I can see from the archives, the value of NMBCLUSTERS is controlled by the 
maxusers, and since this value is 0 shouldn't the NMBCLUSTERS value autoscale?

I am running 4  .5-RELEASE-p4 on the machine which is a Compaq Prosignia 320. I have 
three identical machines with identical kernel configs that are having no problems. So 
I am quite baffled.

Can anybody give me some pointers?

+-+
| Thomas Gravgaard   | "The Scarlet Pimpernel is the most   (__)  |
| Software developer | overrated human being since Judas \\\'',)  |
| Infopaq A/S| Iscariot won the AD 31 best disciple\/  \ ^|
| [EMAIL PROTECTED]  | competition."  Black Adder  .\._/_)|
+-+
|FC København. Danske mestre 2000/2001!   |
+-+ 



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

Adduser broken??

[Odhiambo Washington]

Hello world,


In all the machines I've updated recently, even today, adduser seems to be broken,
unless I missed something. I've scanned the -stable list for this but can't find
a mention.


When you invoke it, it says:

Usernames must match regex (shortened):
[^[a-z0-9_][a-z0-9_-]*$]:

Then enter a username to add and it will continue to prompt you for username
till the cows come home ;-)

Any known fixes??

Thanks


-Wash

-- 
Odhiambo Washington  <[EMAIL PROTECTED]>"The box said 'Requires
Wananchi Online Ltd.  www.wananchi.com  Windows 95, NT, or better,'
Tel: 254 2 313985-9   Fax: 254 2 313922 so I installed FreeBSD."   
GSM: 254 72 743 223   GSM: 254 733 744 121  This sig is McQ!  :-)


Your analyst has you mixed up with another patient.  Don't believe a
thing he tells you.

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

Re: Adduser broken??

[Wade Majors]

Odhiambo Washington wrote:
> When you invoke it, it says:
> 
> Usernames must match regex (shortened):
> [^[a-z0-9_][a-z0-9_-]*$]:
> 
> Then enter a username to add and it will continue to prompt you for username
> till the cows come home ;-)

It is not prompting you for a username. it is prompting you for a regex 
pattern. The default is what is in []'s. This is the configuration 
stage. Just press enter for the prompts after that (must use passwords, 
default shell, etc) until you get to the prompt that says "Enter 
username [(regex from above)]:"

-Wade


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

Re: Cluster allocation errors in messages

[Bruce A. Mah]

If memory serves me right, "Thomas Gravgaard" wrote:
> I have been getting a massive amount of the following errors in my messages o
> ver the last couple of weeks :
> 
> > m_clalloc failed, consider increase NMBCLUSTERS value
> > fxp0: cluster allocation failed, packet dropped!
> 
> As far as I can see from the archives, the value of NMBCLUSTERS is controlled
>  by the maxusers, and since this value is 0 shouldn't the NMBCLUSTERS value a
> utoscale?

By default, yes.  However, you can force a particular number of cluster
mbufs by setting NMBCLUSTERS in the kernel configuration (see the LINT
configuration file) or by setting the kern.ipc.nmbclusters loader
tunable (see /boot/defaults/loader.conf).  See tuning(7) for more
details.

Bruce.



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

Re: conf/11376 still suspended

[Kris Kennaway]

On Sat, May 11, 2002 at 03:07:39AM +0200, Karsten W. Rohrbach wrote:
> Kris Kennaway([EMAIL PROTECTED])@2002.05.10 17:01:09 +:
> > There's also the important point that -stable is entirely the wrong
> > list to be asking on, because it's a technical support list and not a
> > development list.
> 
> one might note that there's the -qa mailing list which should hold
> discussion on issues pending a release, IIRC.
> 
> the question is, if -stable isn't a bad choice either.

I already said it's not, because it's a support list and not a
development list.  Patches should not be sent there, nor should there
be discussion of proposed changes to FreeBSD-current.

Kris



msg45138/pgp0.pgp
Description: PGP signature