Re: re(4) needs promisc to work properly
Hello Bill,
* Bill Paul [EMAIL PROTECTED] wrote:
I'm a little concerned about the fact that now SIOCSIFFLAGS can never
cause re_init_locked() to be called. There are some cases where it
does need to be called (like when the IFF_UP flag is first set to
turn the interface on).
I usually do it like in the vge(4) driver: if it's just the IFF_PROMISC
bit that's being toggled, then I only toggle the promisc mode bit in
the RX config register.
To avoid code duplication and to speed up IFF_BROADCAST as well, I
decided to keep the re_init_rxcfg() function. I took a look at vge(4)
and xl(4) and added `re_if_flags` to the softc to backup the original
ifp-if_flags.
Yours,
--
Ed Schouten [EMAIL PROTECTED]
WWW: http://g-rave.nl/
--- sys/dev/re/if_re.c Sat Dec 2 00:05:44 2006
+++ sys/dev/re/if_re.c Sat Dec 2 00:15:56 2006
@@ -249,6 +249,7 @@
static int re_ioctl(struct ifnet *, u_long, caddr_t);
static void re_init(void *);
static void re_init_locked (struct rl_softc *);
+static void re_init_rxcfg (struct rl_softc *);
static void re_stop(struct rl_softc *);
static void re_watchdog(struct ifnet *);
static int re_suspend (device_t);
@@ -2254,7 +2255,6 @@
{
struct ifnet*ifp = sc-rl_ifp;
struct mii_data *mii;
- u_int32_t rxcfg = 0;
union {
uint32_t align_dummy;
u_char eaddr[ETHER_ADDR_LEN];
@@ -2316,31 +2316,8 @@
} else
CSR_WRITE_4(sc, RL_TXCFG, RL_TXCFG_CONFIG);
CSR_WRITE_4(sc, RL_RXCFG, RL_RXCFG_CONFIG);
-
- /* Set the individual bit to receive frames for this host only. */
- rxcfg = CSR_READ_4(sc, RL_RXCFG);
- rxcfg |= RL_RXCFG_RX_INDIV;
-
- /* If we want promiscuous mode, set the allframes bit. */
- if (ifp-if_flags IFF_PROMISC)
- rxcfg |= RL_RXCFG_RX_ALLPHYS;
- else
- rxcfg = ~RL_RXCFG_RX_ALLPHYS;
- CSR_WRITE_4(sc, RL_RXCFG, rxcfg);
-
- /*
-* Set capture broadcast bit to capture broadcast frames.
-*/
- if (ifp-if_flags IFF_BROADCAST)
- rxcfg |= RL_RXCFG_RX_BROAD;
- else
- rxcfg = ~RL_RXCFG_RX_BROAD;
- CSR_WRITE_4(sc, RL_RXCFG, rxcfg);
-
- /*
-* Program the multicast filter, if necessary.
-*/
- re_setmulti(sc);
+
+ re_init_rxcfg(sc);
#ifdef DEVICE_POLLING
/*
@@ -2422,6 +2399,39 @@
callout_reset(sc-rl_stat_callout, hz, re_tick, sc);
}
+static void
+re_init_rxcfg(sc)
+ struct rl_softc *sc;
+{
+ u_int32_t rxcfg;
+ struct ifnet*ifp = sc-rl_ifp;
+
+ /* Set the individual bit to receive frames for this host only. */
+ rxcfg = CSR_READ_4(sc, RL_RXCFG);
+ rxcfg |= RL_RXCFG_RX_INDIV;
+
+ /* If we want promiscuous mode, set the allframes bit. */
+ if (ifp-if_flags IFF_PROMISC)
+ rxcfg |= RL_RXCFG_RX_ALLPHYS;
+ else
+ rxcfg = ~RL_RXCFG_RX_ALLPHYS;
+ CSR_WRITE_4(sc, RL_RXCFG, rxcfg);
+
+ /*
+* Set capture broadcast bit to capture broadcast frames.
+*/
+ if (ifp-if_flags IFF_BROADCAST)
+ rxcfg |= RL_RXCFG_RX_BROAD;
+ else
+ rxcfg = ~RL_RXCFG_RX_BROAD;
+ CSR_WRITE_4(sc, RL_RXCFG, rxcfg);
+
+ /*
+* Program the multicast filter, if necessary.
+*/
+ re_setmulti(sc);
+}
+
/*
* Set media options.
*/
@@ -2483,10 +2493,16 @@
break;
case SIOCSIFFLAGS:
RL_LOCK(sc);
- if (ifp-if_flags IFF_UP)
- re_init_locked(sc);
- else if (ifp-if_drv_flags IFF_DRV_RUNNING)
+ if (ifp-if_flags IFF_UP) {
+ if ((ifp-if_flags ^ sc-rl_if_flags)
+ (IFF_PROMISC | IFF_BROADCAST))
+ re_init_rxcfg(sc);
+ else
+ re_init_locked(sc);
+ } else if (ifp-if_drv_flags IFF_DRV_RUNNING) {
re_stop(sc);
+ }
+ sc-rl_if_flags = ifp-if_flags;
RL_UNLOCK(sc);
break;
case SIOCADDMULTI:
--- sys/pci/if_rlreg.h Sat Dec 2 00:07:27 2006
+++ sys/pci/if_rlreg.h Sat Dec 2 00:18:53 2006
@@ -737,6 +737,7 @@
struct mtx rl_intlock;
int rl_txstart;
int rl_link;
+ int rl_if_flags;
};
#defineRL_LOCK(_sc)mtx_lock((_sc)-rl_mtx)
pgpOSaoY8hkwl.pgp
Description: PGP signature
Re: sshd. UseDNS no ignored?
Hello! On Fri, 1 Dec 2006, Chuck Swiger wrote: On Nov 29, did you not say: I'm still wondering why OpenSSH is _so_ inferior to SSH.COM's ssh2 (which is also open-source)?...? Yes, I did. And no, I didn't say anything about either licensing or OSI Open Source. David Adam then asked Is it really open-source?; while you responded to this question, your answer was misleading. The commercial version of SSH publishes their source code, but that source code is not usable by many people because of the restriction against commercial use. Specifically, the answer to the question David asked is no: the F-Secure/SSH Communications version of SSH is not OSI Open Source, per OSD #6. David didn't mention OSI at all, you do. 2) We _aren't_ in @opensource.org mailing list hierarchy - it's FreeBSD maillist, and I hope I'm free to _not_ submit anything to opensource.org's consideration, and just to express my opinion instead. While you are free to have an opinion about factual issues [1], if you insist upon expressing an opinion which contradicts the facts (ie, such as claiming that the SSH.COM license is open-source), you can expect people to disagree with you by pointing out the relevant facts. I do insist on using the English word 'open' in it's vocabulary meaning (open == NOT closed; you _can_ see the sources for free), and yes, it's perfectly normal when people disagree with me ;) As for submitting anything to the OSI mailing list: if you refrain from claiming that a proprietary license is open source, then have no concern. On the other hand, the OSI board does contact sites which misuse the OSI Open Source trademark to claim their proprietary software complies with the Open I don't use, abuse or misuse the OSI Open Source trademark. You just can't restrict the use of the English word open, open-source etc, can you?! -Chuck [1]: Oddly enough, many people think so highly of their own opinions that they choose to ignore facts which contradict their opinions. I think my opinion deserves expressing here, and you have no facts that make me think otherwise. I think restricting the use of the phrase 'open-source' just to the OSI-blessed meaning looks the same as patenting mouse doubleclick by Microsoft ;) Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: [EMAIL PROTECTED] nic-hdl: LYNX-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
LSI 53C1030/mpt(4) problem
Hi, Recently I bought Intel Pentium D 945 (3.45GHz), Supermicro PDSME (Intel E7320), and LSI21320RB (PCI-X SCSI HBA using LSI 53C1030). I installed 6.2-RC1 to an old PATA HDD and attached it to the motherboard, and it worked fine. However, I installed 21320RB and made several SCSI HDDs attached, some strange problems occurred. First, 21320RB was recognized by the mpt(4) driver. When I tried it with no HDD it was recognized properly, so I turned off the box and connected an HDD to it and rebooted it. Then, mpt(4) recognized the HDD and it worked without problems. I thought it was okay, and connected more HDDs to the SCSI HBA. More specifically, 21320RB has two channels, so I connected two hardware RAID boxes which actually contain five HDDs each and are seen as one large HDD to each channel. When I rebooted the box after that, device probing at boot time stopped just before Waiting 5 seconds for SCSI devices to settle. Everything including keyboard does not work at that time, I turned off the box and disconnect the RAID boxes. After several trials, I found that 21320RB's behavior was somewhat strange: - with no HDD: Works fine basically, but after two or more HDDs recognized, it freezes during device probing (just before Waiting... message) even if the HDDs removed. Setting the card's configuration as factory default via BIOS setting seems to recover the state. - with one HDD: Works fine after it is recognized. - with two HDDs: Does not work if two HDDs are connected to each channel. BIOS message from the HBA is normal, but FreeBSD device probing keeps failing in the following two forms: a) Freeze just before Waiting... message. b) Freeze after Waiting... message. In b), mpt(4) seems to reset the buses and wait the responses, but I saw after displaying unretryable error it freeze when boot -v used. I tried booting the box with no SCSI HDD, connecting HDDs after the boot, and doing camcontrol rescan all. It recognizes the connected HDDs successfully, and it can be accessed fine even if it is more than one. However, simultaneous access causes solid freeze again. Then I tried a RAID box which has one ID and several LUN numbers corresponding to the HDDs. It recognized as normal, multiple HDDs at boot time, and can be accessed. Simultaneous access works, too. After that, I tried daisy-chaining two RAID boxes and connected the two to a channel of the SCSI HBA. These RAID boxes have ID=0 and ID=1. FreeBSD freezes after Waiting... message this time. In short, I could make this configuration work fine only when a RAID box (or SCSI HDD) is connected to the HBA, or multiple HDDs that have the same ID and different LUN number from each other are connected. I investigated the following: - 6.1R sometimes probes the two HDDs case, but accessing it makes the box freeze. - 2006 Nov 7-CURRENT snapshot probes the two HDDs case, but the HDDs are recognized as very slow devices such as 6MB/s, and accessing it makes the box freeze, too. - When the box freezes just before Waiting... message, boot -v does not display any detail messages there. In after Waiting.. case, several messages are displayed from mpt(4). - No panic in either case. In all cases, it silently freezes and does not respond to Ctrl-Alt-ESC. - When I use Intel D865GBF (motherboard with Intel 865 chipset), the same HBA, and the same RAID boxes, they work fine on 6.1-RC1. The HBA is connected to 33MHz PCI bus, not PCI-X, so it may make some differences. Any suggestions for what I should do for this problem? I can send more detail information from boot -v and/or dev.mpt.0.debug=5, but not sure which message is important for diagnosing. -- | Hiroki SATO pgpA2pXeWR7UN.pgp Description: PGP signature
Surround Sound
Hi Guys, is there any support for Surround Sound on Release 6.1? I would like to buy a new soundcard for my Media Station and would like to get to know if there are some cards supported by *BSD.. Greetz halfdan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Dell PE 1950 bce NICs revisited
On Wednesday 29 November 2006 11:33, Josh Paetzel wrote: On Wednesday 29 November 2006 10:43, Scott Long wrote: Josh Paetzel wrote: I've been using 6.1-R on a PE1950 for some time now. The stock bce driver doesn't work at all. I dug up a driver off the web (0.9.6) that worked fine with my workload (basically all TCP) but in talking to Scott I discovered that UDP traffic was a problem for this driver. Some time ago I upgraded to the driver in -STABLE. This driver also appears to work fine, but about once a day I get the following: Nov 29 01:16:47 server2 kernel: bce1: /usr/src/sys/dev/bce/if_bce.c(5000): Watch dog timeout occurred, resetting! Nov 29 01:16:47 server2 kernel: bce1: link state changed to DOWN Nov 29 01:16:48 server2 kernel: bce1: link state changed to UP Pretty minor complaint, as it doesn't really affect the operation of the box, but I suppose it's a sign that there's still some work to be done. $FreeBSD: src/sys/dev/bce/if_bce.c,v 1.2.2.6 2006/10/24 As I write this I see there has been some further work on the driver, so I think I'll upgrade it and see what happens. It's possible that rev 1.2.2.6 will fix what you're seeing. If not, then it might be the general issue with the watchdog framework being unreliable that we addressed with the em driver. If so, then it's mostly harmless. Scott The string I pasted is what I was using. Rebuilt using: /repoman/r/ncvs/src/sys/dev/bce/if_bce.c,v 1.2.2.6.2.1 this morning. I'll give it a few days and see how it's working. I think either way it's harmless. It happens about once a day, and strangely enough it's almost always in periods of very low load. Well, since the upgrade the NIC hasn't reset, so I'd say we have a winner. Thanks for all the work on this thing. :) -- Thanks, Josh Paetzel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: LSI 53C1030/mpt(4) problem
Hiroki Sato wrote: Hi, Recently I bought Intel Pentium D 945 (3.45GHz), Supermicro PDSME (Intel E7320), and LSI21320RB (PCI-X SCSI HBA using LSI 53C1030). I installed 6.2-RC1 to an old PATA HDD and attached it to the motherboard, and it worked fine. However, I installed 21320RB and made several SCSI HDDs attached, some strange problems occurred. [...] Any suggestions for what I should do for this problem? I can send more detail information from boot -v and/or dev.mpt.0.debug=5, but not sure which message is important for diagnosing. -- | Hiroki SATO Just for comparison, could you go back to FreeBSD 6.0 and see if the problems remain? Scott ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
witness_checkorder panic
Hello, I just got this on a box I'm testing before installation. It has clean RELENG_6 from about two weeks ago with only some small if_bge.c-patches Bruce Evans sent me for testing performance/hang problems. Since I doubt this panic is related to that, I just post it here in case someone is interested in more info : [sorry, no serial console attached ... just copy-paste from screen, but I will leave the box in the debugger for the WE ] struct mount mtx (struct mount mtx) @ /files/bsd/src6/sys/ufs/ufs/ufs_vnops.c:138 KDB: stack backtrace : witness_checkorder() _mtx_lock_flags() ufs_itimes() ufs_getattr() VOP_GETATTR_APV() filt_vfsread() knote() VOP_WRITE_APV() vn_write() dofilewrite() kern_writev() write() syscall() Xfast_syscall() --- syscall (4, FreeBSD ELF64, write), rip = 0x4363dc, rsp = 0X7fffdd78, rbp = 0x2f6 --- KDB: enter: witness_checkorder [thread pid 3987 tid 100133 ] Kernel config is stripped GENERIC + options AHC_ALLOW_MEMIO options TCP_DROP_SYNFIN options KDB options KDB_TRACE options DDB options KTRACE options INVARIANTS options INVARIANT_SUPPORT options DDB_NUMSYM options BREAK_TO_DEBUGGER options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_KDB options DEBUG_LOCKS options DEBUG_VFS_LOCKS options DIAGNOSTIC options MUTEX_PROFILING options MUTEX_DEBUG options SLEEPQUEUE_PROFILING options TURNSTILE_PROFILING options DEBUG_MEMGUARD The box was doing (/usr/src nfs-mounted): nohup time make -j 2 -DNO_CLEAN buildworld /tmp/bw_alone.log 21 It paniced shortly after I started 'tail -f /tmp/bw_alone.log' in another window, and /tmp is mfs. Arno -- Arno J. Klaassen SCITO S.A. 8 rue des Haies F-75020 Paris, France http://scito.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: pam.d/sshd
On Friday, 1 December 2006 at 21:02:45 +0100, Stefan Thurner wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Stefan. /etc/pam.d/sshd pam file is for sshd server not for ssh client. If you want to use ssh-agent whole the time your box is online you should start it right after login. In order to doing this add session optionalpam_ssh.so want_agent line into session facility of /etc/pam.d/system file (it's included into /etc/pam.d/login so don't worry). Hi Nikolay! Thats right and I have such a line in may pam.d/system file. But what I want is that ssh-agent is started on the remote host if I login on the remote host. Therefore I added the described lines in the pam.d/sshd file on the remote host. The password for ssh-key is requested if I login on the remote host (as it should) but no ssh-agent is started. I'm quite sure that it is a bug in pam_ssh.so. When bug reporting on the freebsd site is working again I will send in a problem report. Yes. You are right. Even with want_agent ssh-agent is started, but do not contain key decripted during the authentication phase. best regards - -Stefan - -- GPG-encrypted mail welcome! -- ID:E970FCBE -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFcIplxNmQVulw/L4RApPYAJ9C2frkDjE3AlKdQh/unv38E1YbjwCgtPaZ 6lio3DnQJBfjh+azcAyD9fA= =Rebv -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] -- == - Best regards, Nikolay Pavlov. --- == ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: witness_checkorder panic
On Sat, Dec 02, 2006 at 07:15:37PM +0100, Arno J. Klaassen wrote: Hello, I just got this on a box I'm testing before installation. It has clean RELENG_6 from about two weeks ago with only some small if_bge.c-patches Bruce Evans sent me for testing performance/hang problems. Since I doubt this panic is related to that, I just post it here in case someone is interested in more info : [sorry, no serial console attached ... just copy-paste from screen, but I will leave the box in the debugger for the WE ] struct mount mtx (struct mount mtx) @ /files/bsd/src6/sys/ufs/ufs/ufs_vnops.c:138 KDB: stack backtrace : witness_checkorder() _mtx_lock_flags() ufs_itimes() ufs_getattr() VOP_GETATTR_APV() filt_vfsread() knote() VOP_WRITE_APV() vn_write() dofilewrite() kern_writev() write() syscall() Xfast_syscall() --- syscall (4, FreeBSD ELF64, write), rip = 0x4363dc, rsp = 0X7fffdd78, rbp = 0x2f6 --- KDB: enter: witness_checkorder [thread pid 3987 tid 100133 ] Kernel config is stripped GENERIC + options AHC_ALLOW_MEMIO options TCP_DROP_SYNFIN options KDB options KDB_TRACE options DDB options KTRACE options INVARIANTS options INVARIANT_SUPPORT options DDB_NUMSYM options BREAK_TO_DEBUGGER options INVARIANTS options INVARIANT_SUPPORT options WITNESS options WITNESS_KDB options DEBUG_LOCKS options DEBUG_VFS_LOCKS options DIAGNOSTIC options MUTEX_PROFILING options MUTEX_DEBUG options SLEEPQUEUE_PROFILING options TURNSTILE_PROFILING options DEBUG_MEMGUARD The box was doing (/usr/src nfs-mounted): nohup time make -j 2 -DNO_CLEAN buildworld /tmp/bw_alone.log 21 It paniced shortly after I started 'tail -f /tmp/bw_alone.log' in another window, and /tmp is mfs. Please, try the patch at http://people.freebsd.org/~kib/kqueue-lor.1.patch [ I do not include it inline since spamfilter at freebsd.org notices the get.*fast pattern in the patch. I need to rename this somehow. ] pgptTIinYG46M.pgp Description: PGP signature
Gnome2 2.16 fails on Notification-daemon-0.3.6
Installing Gnome2 2.16 on FreeBSD 5.5 stable from /x11/gnome2 port. I have looked looked and the site is gone or down 100 % http://www.galago-project.org/ How can we fix this ? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sshd. UseDNS no ignored?
This thread has far exceeded whatever useful lifetime it may have had, and the freebsd-stable mailing list is not the place to discuss licensing issues. Please let this thread drop, and take any as yet unmade points to private e-mail. Thanks, Doug -- This .signature sanitized for your protection ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: sshd. UseDNS no ignored?
A troll is a troll, regardless of ML hierarchy ... or vocabulary. He's stated numerous times he has no intention of doing anything useful with his ideas, merely to pick at increasingly pedantic nits. Send him to Theo or Stallman if he wants to argue the fine points of word meanings. Tim ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: application hangs in STABLE from time to time
Hello! On Fri, 1 Dec 2006, Ganbold wrote: this. Next time use the -o wchan argument to ps to find out what state the process is blocked in. Ok, Here it is: 573 ?? Is 0:00.02 /usr/sbin/inetd -wW -C 60 78721 ?? I 0:00.01 /usr/local/Radiator-3.15/hooks/PSA ^ voiprad# ps -o wchan WCHAN ttyin It's more convenient to use -O here: [EMAIL PROTECTED] ps axO wchan PID WCHAN TT STAT TIME COMMAND 0 - ?? WLs0:00.00 [swapper] 1 wait?? ILs0:00.01 /sbin/init -- 2 - ?? DL 0:00.58 [g_event] 3 - ?? DL 0:11.72 [g_up] 4 - ?? DL 0:18.63 [g_down] 5 crypto ?? DL 0:00.00 [crypto] kgdb /dev/mem /boot/kernel/kernel.symbols I tried with with kernel.debug without success: voiprad# kgdb /dev/mem /usr/obj/usr/src/sys/VOIPRAD/kernel.debug kgdb: bad namelist Reverse the arguments: [EMAIL PROTECTED] kgdb /boot/kernel.debug/kernel.debug /dev/mem kgdb: kvm_nlist(_stopped_cpus): kgdb: kvm_nlist(_stoppcbs): [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol ps_pglobal_lookup] GNU gdb 6.1.1 [FreeBSD] ... (kgdb) info threads 111 Thread 100127 (PID=3196: kgdb) 0xc04aa6fb in sched_switch ( td=0xc6b31900, newtd=0xc35b2600, flags=1) at /usr/RELENG_6/src/sys/kern/sched_4bsd.c:973 110 Thread 100100 (PID=2734: more) 0xc04aa6fb in sched_switch ( td=0xc4dd3d80, newtd=0xc35b2600, flags=1) at /usr/RELENG_6/src/sys/kern/sched_4bsd.c:973 thanks, Ganbold Sincerely, Dmitry -- Atlantis ISP, System Administrator e-mail: [EMAIL PROTECTED] nic-hdl: LYNX-RIPE ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Surround Sound
On 12/2/06, Fabian Becker [EMAIL PROTECTED] wrote: Hi Guys, is there any support for Surround Sound on Release 6.1? I would like to buy a new soundcard for my Media Station and would like to get to know if there are some cards supported by *BSD.. What soundcard do you have? Greetz halfdan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: LSI 53C1030/mpt(4) problem
- 2006 Nov 7-CURRENT snapshot probes the two HDDs case, but the HDDs are recognized as very slow devices such as 6MB/s, and accessing it makes the box freeze, too. The 6MB/s thing I'm working on now. I have no clue about the other issues at this time. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
