Compile a kernel with UMASS_DEBUG (or load the module compile with
CFLAGS+=-DUMASS_DEBUG) and send me the output of an attach. It should be
possible to make it work.
The fact that it reboots without reason is very very strange indeed. If
that is the case, check that your machine is grounded
Then a panic reboot. I guess it's better than before -
previously I got no message whatsoever; the OS just froze
rebooted. At the same time I'd think a panic/reboot is Very
Very Bad; at least if something is wrong shouldn't the OS
just say no?
Well, perhaps you could consider a panic an
On Thursday, 11 April 2002 at 10:43:46 +0400, Eugene Mitrofanov wrote:
Hi
I have 2 raid0 volumes on my server. Some time ago one hard disk died
and I removed it from the server. Now the system reboots suddenly every
1..5 days. I recompiled kernel with debuging info and located the place of
It seems Mike Tancsa wrote:
Yet, when I go to do a rebuild,
raidtest3# atacontrol rebuild ar0
atacontrol: ioctl(ATARAIDREBUILD): Operation not supported by device
raidtest3#
I guess there needs to be some way to tell the controller to use ad6 as
part of the rebuild no ?
You need to do
Hi,
At 01:55 11/04/02 +0100, Ian Dowse wrote:
In message [EMAIL PROTECTED], Vladislav V. Zhuk writes:
After attempt to write data to write-protected floppy
(or diskette with bad blocks) FreeBSD die.
It's VERY VERY annoying... :(
Who can fix this bug??
Unfortunately, this is believed to
I received lots of positive feedback about the DHCP 3.0.1 tarball,
so I've gone ahead with the MFC. DHCP 3.x has been in -CURRENT for a
couple of months without incident and it fixes a number of known
issues. Please let me know if you experience any problems.
Thanks,
-
Thus spake Ian Dowse [EMAIL PROTECTED]:
In message [EMAIL PROTECTED], Vladislav V. Zhuk writes:
After attempt to write data to write-protected floppy
(or diskette with bad blocks) FreeBSD die.
It's VERY VERY annoying... :(
Who can fix this bug??
Unfortunately, this is believed to be
On Wed, 10 Apr 2002, Eric S wrote:
According to the manual, if I'm NFS mounting /usr/src and /usr/obj, using
one machine to build everything, and installing across NFS on all the
other FreeBSD boxes on our net, I need to set KERNCONF to all of the
kernel names, with the build box first.
At 10:57 AM 4/11/2002 +0200, Søren Schmidt wrote:
It seems Mike Tancsa wrote:
Yet, when I go to do a rebuild,
raidtest3# atacontrol rebuild ar0
atacontrol: ioctl(ATARAIDREBUILD): Operation not supported by device
raidtest3#
I guess there needs to be some way to tell the controller
It seems Mike Tancsa wrote:
I guess there needs to be some way to tell the controller to use ad6 as
part of the rebuild no ?
You need to do a atacontrol detach on the failed device, then an
atacontrol attach on the new disk. BTW you dont need to boot
inbetween :)
atacontrol:
Hi hi.
A while back my freebsd4.5-release-p2 has started to give these
errors when working with nfs (client):
Apr 11 11:32:18 flash /kernel: m_clalloc failed, consider increase NMBCLUSTERS value
Apr 11 11:32:18 flash /kernel: fxp0: cluster allocation failed, packet dropped!
Apr 11 11:32:19
Geez, calm down. You catch more flies with honey than with vinegar.
Also, isn't the warning pretty self-explanatory?
man ioctl shows that sys/ioctl.h is expected to be used in userland.
And, unlike userland, it's not like the kernel has any obligation to be the
same across Unices, so I'm
Ok, why on earth is there a #warning for including sys/ioctl.h for
kernel stuff ?
By definition, /usr/include/sys _IS_ kernel include files.
Has some crack monkey been playing with include files again ?
If the current sys/ioctl.h isn't for use in the kernel, will someone
please replace it
13 matches
Mail list logo
