Re: Sockets stuck in FIN_WAIT_1
On Fri, 30 May 2008, Peter Jeremy wrote:
As a work-around, you could write a cronjob that scans netstat and
temporarily creates an ipfw 'reset' rule that matches each FIN_WAIT_1
socket
In the past, I've used something like this:
netstat -an | grep FIN_WAIT_1 |
perl -pe 's/.*\s((?:\d+\.){3}\d+)\.(\d+)\s*((?:\d+\.){3}\d+)\.(\d+).*/tcpdrop
$1 $2 $3 $4/' |
sh -x
This relies on tcpdrop, included as /usr/sbin/tcpdrop on FreeBSD 6.x; you
may need to install it from a port on FreeBSD 4.x.
--
Tod McQuillin
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Odd file in /lost+found after softupdate inconsistency in fsck
Hi all, My server froze up tonight after a 2 month uptime running 6.3-PRERELEASE from Dec 28 2007. I had to fsck /home by hand because of an inconsistency fsck couldn't repair automatically -- something to do with an unexpected softupdate inconsistency. After that, I ended up with some files in /home/lost+found, one of which is quite interesting: /home/lost+found# ls -lksh total 24432 24432 -r 1 root operator40G Mar 5 20:12 #005 It is 40G in size but only occupies 24432k on disk, so it is a sparse file. I'm not aware of any sparse files of quite that size on my system (or relative sparseness) but it's possible i might overlook one. But the thing that's interesting to me is the inode number (inode 5) and the fact that rm doesn't want me to remove it: /home/lost+found# rm \#005 override r root/operator snapshot for #005? n Is there a magic shapshot flag on the file? Have I somehow damaged my ufs2+softupdates filesystem by losing its inode #5 containing snapshot data? Any insights appreciated, -- Tod McQuillin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Odd file in /lost+found after softupdate inconsistency in fsck
On Thu, 6 Mar 2008, Peter Jeremy wrote: On Wed, Mar 05, 2008 at 09:43:15PM +0900, Tod McQuillin wrote: /home/lost+found# ls -lksh total 24432 24432 -r 1 root operator40G Mar 5 20:12 #005 It is 40G in size but only occupies 24432k on disk, so it is a sparse file. The file permissions and sparseness matches a snapshot. If your FS is 40GB then it is a snapshot. Thanks Peter. So, it's a shapshot -- is it still usable? Is it safe to delete it? snapinfo doesn't know about it: # snapinfo -v /home /dev/ad4s2e mounted on /home no snapshots found I'm not in the habit of making snapshots ... but it might have come from a dump -L. Anyway, I think the conclusion is that it's a snapshot, of mysterious origin, and it's probably not useful. Thanks again, -- Tod MCQuillin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Laptop recommendations for 6.x
On Tue, 20 Feb 2007, Nik Clayton wrote: I'm using an IBM/Lenovo T42 at the moment, but that's shortly going back, so: Things I don't like: * Battery life isn't great Did you try powerd? * No WiFi WiFi works fine on my T42 with the iwi driver. -- Tod McQuillin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Strange error
On Sun, 12 Jun 2005, Peter Jeremy wrote: On Fri, 2005-Jun-10 22:41:36 +0200, Jack Raats wrote: This day I've a very strange error when trying to connect to my FreeBSD machine (4.11-STABLE) I got the following error: ssh_exchange_identification: Connection closed by remote host Can anyone give me any clue what's wrong? I missed the start of this thread but this sounds like tcpwrappers closing the connection. Check your /etc/hosts.allow and look in /var/log/messages for a message like: May 31 12:18:36 hostname sshd[1594]: warning: /etc/hosts.allow, line 32: can't verify hostname: getaddrinfo(1.2.3.4.example.com, AF_INET) failed May 31 12:18:37 hostname sshd[1594]: refused connect from 1.2.3.4 (1.2.3.4) If you see something like that you can change the entry in your /etc/hosts.allow to allow ssh connections from that specific IP or netmask. see hosts_options(5) for details. -- Tod McQuillin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Poor network performance: a lot of timeouts
On Mon, 30 May 2005, Kris Kennaway wrote: On Mon, May 30, 2005 at 10:56:22PM +0200, Sebastian Ahndorf wrote: Kris Kennaway wrote: Both sides must have same config, autosense should work if there is no config possibility in other end. autosense may in fact not work, especially on low-quality NICs like rl. I don't agree to that. I had similar problems with my network using a cheap switch with some realtek nics. I had the nics running 100baseTX Full Duplex. Changing this to autosense made the problems gone. Your one example does not disprove the statement. I've seen this problem myself, and so have many others. I found this document extremely helpful in understanding ethernet autonegotiation, especially the table on page 7: https://myvision.flukenetworks.com/edocs/efile.asp?oid=2040882 Good luck, -- Tod ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: wi0 is always status: no carrier
On Thu, 12 May 2005, Kirk Strauser wrote: I've finally coerced FreeBSD 5.4 to see my PCMCIA WLAN card (with many thanks to Warner), but it always reports status: no carrier. I'm attempting to connect to an open WAP that broadcasts it's SSID, so my understanding is that it should be as simple as ifconfig wi0 ad.dr.es.s netmask 255.255.255.0 or dhclient wi0, but neither of those work. Be sure to set the ssid: ifconfig wi0 ssid whatever -- Tod McQuillin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
ACPI errors with 5-stable, zzz
With 5-stable as of last night (5.4-PRERELEASE #0: Thu Mar 3 21:41:55 JST 2005), on an IBM ThinkPad X20, running 'zzz' produces the following messages on the console: ACPI-0501: *** Error: Handler for [EmbeddedControl] returned AE_NO_HARDWARE_RESPONSE ACPI-1304: *** Error: Method execution failed [\\_SB_.PCI0.ISA_.EC__.SYSL] (Node 0xc16d8040), AE_NO_HARDWARE_RESPONSE ACPI-1304: *** Error: Method execution failed [\\_SI_._SST] (Node 0xc16dd480), AE_NO_HARDWARE_RESPONSE ACPI-0306: *** Error: Method _SST failed, AE_NO_HARDWARE_RESPONSE The system then appears to sleep (however, characters are still visible on the display under bright light (though the backlight is off) and the sleeping moon indicator light does not light as it did with 4-stable). The system wakes up and continues operating with no trouble, so perhaps this is no cause for concern, but if anyone can explain the messages, I'd appreciate it. dmesg is attached. -- Tod McQuillin Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...2 2 1 1 1 1 1 0 0 done No buffers busy after final sync Uptime: 11m35s Shutting down ACPI Rebooting... Copyright (c) 1992-2005 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.4-PRERELEASE #0: Thu Mar 3 21:41:55 JST 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/REIZOUKO Timecounter i8254 frequency 1193182 Hz quality 0 CPU: Intel Pentium III (597.41-MHz 686-class CPU) Origin = GenuineIntel Id = 0x686 Stepping = 6 Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE real memory = 335478784 (319 MB) avail memory = 318652416 (303 MB) npx0: [FAST] npx0: math processor on motherboard npx0: INT 16 interface acpi0: PTLTD RSDT on motherboard acpi0: [MPSAFE] acpi0: Power Button (fixed) acpi_ec0: Embedded Controller: GPE 0x9, GLK port 0x66,0x62 on acpi0 Timecounter ACPI-safe frequency 3579545 Hz quality 1000 acpi_timer0: 24-bit timer at 3.579545MHz port 0x1008-0x100b on acpi0 cpu0: ACPI CPU (3 Cx states) on acpi0 acpi_throttle0: ACPI CPU Throttling on cpu0 acpi_lid0: Control Method Lid Switch on acpi0 acpi_button0: Sleep Button on acpi0 pcib0: ACPI Host-PCI bridge port 0xcf8-0xcff on acpi0 pci0: ACPI PCI bus on pcib0 agp0: Intel 82443BX (440 BX) host to PCI bridge mem 0xf800-0xfbff at device 0.0 on pci0 pcib1: ACPI PCI-PCI bridge at device 1.0 on pci0 pci1: ACPI PCI bus on pcib1 pci1: display, VGA at device 0.0 (no driver attached) isab0: PCI-ISA bridge at device 7.0 on pci0 isa0: ISA bus on isab0 atapci0: Intel PIIX4 UDMA33 controller port 0x1800-0x180f,0x376,0x170-0x177,0x3f6,0x1f0-0x1f7 at device 7.1 on pci0 ata0: channel #0 on atapci0 ata0: [MPSAFE] ata1: channel #1 on atapci0 ata1: [MPSAFE] uhci0: Intel 82371AB/EB (PIIX4) USB controller port 0x1820-0x183f irq 11 at device 7.2 on pci0 uhci0: [GIANT-LOCKED] usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: bridge, PCI-unknown at device 7.3 (no driver attached) cbb0: RF5C476 PCI-CardBus Bridge mem 0x5000-0x5fff irq 11 at device 8.0 on pci0 cardbus0: CardBus bus on cbb0 pccard0: 16-bit PCCard bus on cbb0 cbb0: [MPSAFE] cbb1: RF5C476 PCI-CardBus Bridge mem 0x5010-0x50100fff irq 11 at device 8.1 on pci0 cardbus1: CardBus bus on cbb1 pccard1: 16-bit PCCard bus on cbb1 cbb1: [MPSAFE] xl0: 3Com 3c556B Fast Etherlink XL port 0x2000-0x20ff mem 0xf4011000-0xf401107f,0xf4011400-0xf401147f irq 11 at device 10.0 on pci0 miibus0: MII bus on xl0 acphy0: AC101 10/100 media interface on miibus0 acphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto xl0: Ethernet address: 00:04:76:5f:45:1f xl0: [MPSAFE] pci0: simple comms at device 10.1 (no driver attached) pcm0: Crystal Semiconductor CS4281 mem 0xf400-0xf400,0xf401-0xf4010fff irq 11 at device 11.0 on pci0 pcm0: [GIANT-LOCKED] pcm0: Cirrus Logic CS4297A AC97 Codec acpi_tz0: Thermal Zone on acpi0 atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: [GIANT-LOCKED] psm0: model Generic PS/2 mouse, device ID 0 fdc0: floppy drive controller (FDE) port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on acpi0 fdc0: [MPSAFE] fdc0: [FAST] fd0: 1440-KB 3.5 drive on fdc0 drive 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0: port may not be enabled sio0: 16550A-compatible COM port port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sio0: type 8250 or not responding ppc0: Standard parallel printer port port 0x3bc-0x3bf irq 7 on acpi0 ppc0: Generic chipset (NIBBLE-only
Help me understand netstat output
On a 5.3-STABLE system (and actually for the past few years on FreeBSD 4.x and 5.x), 'netstat -in' has show numbers like this: NameMtu Network Address Ipkts IerrsOpkts Oerrs Coll xl01500 Link#1 00:04:76:5f:45:1f 622543 0 621123 0 0 xl01500 192.168.7 192.168.7.28622208 - 2110040 - - lo0 16384 Link#3 169 0 169 0 0 lo0 16384 127 127.0.0.1 169 - 169 - - wi0* 1500 Link#4 00:02:2d:29:28:7f0 00 0 0 Why does the second line for xl0 show so many more outgoing packets than the first line? It seems to me the first line (Link#1) should count all packets at OSI layer 2, and the second should count layer 3 (IP) packets. I can see the layer 2 count being bigger than layer 3 count (lots of arp or other ether-only traffic) but not the other way around. Anyone know the explanation for this? -- Tod McQuillin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Bug in nfsd, or did I just read the manpage wrong ?
On Wed, 9 Feb 2005, Pete French wrote:
I have a machine with three interfaces on it, two onto
internal networks, one ointo the outside world. I only want
NFS to be accessible on the two internal interfaces so I have this line
in my /etc/rc.conf:
nfs_server_flags=-u -t -n 4 -h 192.168.3.1 -h 192.168.4.1
That works - but it ony enables TCP on the second interface, the
first is UDP only. I have tried all sorts of combinations and
positioning for the -t flag, but the end result is the same. UDP
on both, TCP only on 192.168.4.1.
H... anybody got any ideas ? Puzzling the hell out of me!
Try the patch in http://www.freebsd.org/cgi/query-pr.cgi?pr=bin/25826
That worked for me. I've also attached the patch to this email.
--
tod McQuillin
Index: nfsd.c
===
RCS file: /usr/src/cvs-repo/src/sbin/nfsd/Attic/nfsd.c,v
retrieving revision 1.15.2.2
diff -u -r1.15.2.2 nfsd.c
--- nfsd.c 30 Mar 2004 20:25:33 - 1.15.2.2
+++ nfsd.c 10 May 2004 12:40:41 -
@@ -593,7 +593,8 @@
exit(1);
}
}
- if (tcpflag FD_ISSET(tcpsock, ready)) {
+ for (tcpsock = 0; tcpsock = maxsock; tcpsock++) {
+ if (tcpflag FD_ISSET(tcpsock, ready)) {
len = sizeof(inetpeer);
if ((msgsock = accept(tcpsock,
(struct sockaddr *)inetpeer, len)) 0) {
@@ -613,6 +614,7 @@
nfsdargs.namelen = sizeof(inetpeer);
nfssvc(NFSSVC_ADDSOCK, nfsdargs);
(void)close(msgsock);
+ }
}
#ifdef notyet
if (tp4flag FD_ISSET(tp4sock, ready)) {
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.11: sysctl hw.instruction_sse?
On Fri, 14 Jan 2005, Christian Weisgerber wrote: What's going on here? Add options CPU_ENABLE_SSE to your kernel config and rebuild the kernel. -- Tod McQuillin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: 4.11: sysctl hw.instruction_sse?
On Fri, 14 Jan 2005, Christian Weisgerber wrote: Tod McQuillin: Add options CPU_ENABLE_SSE to your kernel config and rebuild the kernel. But CPU_ENABLE_SSE is defined by default. Are you saying it isn't in RELENG_4? That's right. -- Tod ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: icc8 failed on 4.10: Illegal instruction
On Wed, 29 Dec 2004, Igor Sysoev wrote: (gdb) disassemble $eip ... 0x80b13d3 __intel_proc_init_ftzdaz+75:mov0x2c(%esp,1),%esi 0x80b13d7 __intel_proc_init_ftzdaz+79:stmxcsr (%esp,1) 0x80b13db __intel_proc_init_ftzdaz+83:mov(%esp,1),%eax ... (gdb) Strange, the code in __intel_proc_init_ftzdaz looks like the right code. Right now I can not say from what extention stmxcsr come from. Here is the features from dmesg: Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,C MOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE Google seems to indicate it's an SSE instruction. Do you have 'options CPU_ENABLE_SSE' in your kernel config? -- Tod McQuillin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Logging out the user
On Thu, 16 Dec 2004, [ISO-8859-2] Kov$Ba(Bcs P$Bi(Bter wrote: Sorry for this newbie question, but I don't know how I can do this. When I type who at the command prompt I can see the active users. How can I kill a user from that list? The second column in the output from 'who' shows the tty the user is logged in from, for example, 'ttyp1'. You can find the processes attached to that tty with 'ps tp1' Then you can kill those processes (start with SIGHUP) ... 'kill -HUP ' There are some users whos process has stuck. How can I kill those as well? ps -Uusername then kill as above. -- Tod McQuillin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Just locked up a file system ... but not the system ...
On Thu, 12 Aug 2004, Marc G. Fournier wrote: I have a tech going down to reboot the machine, since I can't leave it down long ... is there something else that I should have looked at on this? Since there is no KVM/keyboard attached to this, and it wasn't booted with one in it, I don't have any way of getting to the DDB and trying to get a core :( Can't you use reboot -d for this? or maybe reboot -qd. Never tried it, but it seems like it makes sense in this situation. -- Tod McQuillin ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Hardware RAID vs vinum
On Mon, 27 May 2002, Miguel Mendez wrote: On Mon, May 27, 2002 at 06:02:23AM -0700, Cy Schubert - CITS Open Systems Group wrote: Did we see a difference in CPU utilization? No. However ODS and VxVM run below the kernel and cannot be measured by vmstat or sar, which is different to how vinum works because it is part of the kernel. I feel curious about this. Both ODS and VxVM are just kernel modules that sit between hardware and the VFS layer if I'm not mistaken. What makes them different than vinum? I don't have experience with vinum, but we also experienced terrible performance with Sun's ODS and software RAID-5. We didn't notice similar problams with Veritas volume manager. I'm beginning to think it's peculiar to ODS, and that other software RAID-5 implementations probably work a lot better. -- Tod McQuillin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: Tar broken for large files?
On Thu, 16 May 2002, Jack L. Stone wrote: Install gtar from ports. I've incurred aborted backups with tar (+ gzip) lately too. What is superior about gtar...??? As it turns out, FreeBSD's tar is in fact GNU tar, albeit an older version. % tar --version GNU tar version 1.11.2 If you want to see all the changes in gtar from ports, then: # cd /usr/ports/archivers/gtar # make extract # less work/tar-1.13.25/NEWS # less work/tar-1.13.25/Changelog -- Tod McQuillin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: MFC of ATA driver from -current finished, please test..
On Mon, 18 Mar 2002, Søren Schmidt wrote: Please let me know asap if you encounter any (new) problems with the ATA driver after this commit. I have a Digital Celebris 6200 (PPro 200MHz) with an Orinoco isa-pcmcia bridge and an Orinoco 802.11b card. Using STABLE before the new ATA driver was committed the ata controller was probed like this: atapci0: Intel PIIX3 ATA controller port 0xecd0-0xecdf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0-master: DMA limited to UDMA33, non-ATA66 compliant cable ad0: 76319MB ST380021A [155061/16/63] at ata0-master WDMA2 acd0: CDROM TOSHIBA CD-ROM XM-5602B at ata0-slave using PIO3 Usinng the new driver it is probed like this: atapci0: Intel PIIX3 ATA controller port 0xecd0-0xecdf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ad0: 76319MB ST380021A [155061/16/63] at ata0-master WDMA2 acd0: CDROM TOSHIBA CD-ROM XM-5602B at ata0-slave PIO3 I have no devices on ata1 and before the new ata driver I was not even aware that it existed. Up until now I have been happily using irq 15 for wi0 (the Orinoco card). With the new driver probing ata1 at irq15, pccardd will not use the wi card, complaining Failed to allocate IRQ for Lucent Technologies. If I run atacontrol detach 1, then pccardd will allocate IRQ 15 for wi0 and everything works as before. Now I have added atacontrol detach 1 in /etc/rc.pccard right before the pccardc pccardmem command, and the system boots up with wi0 and everything works fine. My questions are, 1) Is this the way it's supposed to work? 2) Is there any way to disable probing of ata1 at boot time? (My bios setup did not seem to provide any explicit way of disabling it) 3) Does my workaround of running atacontrol detach 1 from rc.pccard seem like a reasonable workaround? 4) If the answer to 2 is no and the answer to 3 is yes, should this be made configurable via a variable in rc.conf? Thanks, -- Tod McQuillin To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: wi0 problems under latest STABLE
On Mon, 11 Mar 2002, Brooks Davis wrote:
At this point there isn't. I I'm going to have to rethink handling this
problem. It appears that WI_TIMEOUT is actually too long (it hangs the
machine for WI_TIMEOUT*WI_DELAY if the command doesn't return).
Additionaly, it appears that some cards are just broken and we need to
find a way to deal with them.
I made some changes to if_wi.c which completely cleared up the timeout in
wi_cmd messages and 500ms freezes which came up every minute on my laptop
and desktop machines.
The laptop is now completely back to the same behaviour as in cvs rev
1.18.2.14 and earlier of if_wi.c, though the desktop still logs these
messages at boot:
wi0: WaveLAN/IEEE 802.11 at port 0x240-0x27f irq 15 slot 0 on pccard0
wi0: 802.11 address: 00:02:2d:2b:ab:06
wi0: using Lucent chip or unknown chip
wi0: timeout in wi_cmd 2; event status 8080
wi0: timeout in wi_cmd 0; event status 8080
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: wi_cmd: busy bit won't clear.
wi0: init failed
Probably some changes are still needed at attach time.
Here is the patch:
Index: if_wi.c
===
RCS file: /usr/src/cvs-repo/src/sys/i386/isa/Attic/if_wi.c,v
retrieving revision 1.18.2.16
diff -c -r1.18.2.16 if_wi.c
*** if_wi.c 4 Mar 2002 20:03:57 - 1.18.2.16
--- if_wi.c 14 Mar 2002 12:55:54 -
***
*** 453,459
--- 453,461
struct wi_ltv_gen gen;
struct ifnet*ifp;
int error;
+ int s;
+ s = splimp();
sc = device_get_softc(dev);
ifp = sc-arpcom.ac_if;
***
*** 463,468
--- 465,471
if (error) {
device_printf(dev, bus_setup_intr() failed! (%d)\n, error);
wi_free(dev);
+ splx(s);
return (error);
}
***
*** 481,486
--- 484,490
if ((error = wi_read_record(sc, (struct wi_ltv_gen *)mac)) != 0) {
device_printf(dev, mac read failed %d\n, error);
wi_free(dev);
+ splx(s);
return (error);
}
bcopy((char *)mac.wi_mac_addr,
***
*** 584,589
--- 588,594
ether_ifattach(ifp, ETHER_BPF_SUPPORTED);
callout_handle_init(sc-wi_stat_ch);
+ splx(s);
return(0);
}
***
*** 799,804
--- 804,810
{
struct wi_softc *sc;
struct ifnet*ifp;
+ int s;
sc = xsc;
ifp = sc-arpcom.ac_if;
***
*** 809,815
--- 815,823
if (ifp-if_flags IFF_OACTIVE)
return;
+ s = splimp();
wi_cmd(sc, WI_CMD_INQUIRE, WI_INFO_COUNTERS);
+ splx(s);
return;
}
--
Tod McQuillin
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-stable in the body of the message
