On Wed, Mar 28, 2018 at 03:11:50PM +0100, tech-lists wrote:
> On 28/03/2018 14:39, Gregory Byshenk wrote:
> > You can do this manually, or by adding a PORTS_MODULES line to
> > /etc/make.conf. This will rebuild the listed modules from ports
> > when you build a new kernel.
>
> Are you sure it's in
ng with the server. Based on the
error ("No such file or directory"), I would recommend
checking your amd config on the client.
--
greg byshenk - gbysh...@byshenk.net - Leiden, NL
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ecause the "limitations" don't necessarily have anything to do
with ZFS. That is, a situation in which one cannot recover, nor
even effectively troubleshoot, if there is a problem, will be a
"dire" one, regardless of what the problem might be or where its
source might
base system
sources", then 'freebsd-update' (from the base system)
will do the job.
Or am I missing/misunderstanding something?
--
greg byshenk - gbysh...@byshenk.net - Leiden, NL - Portland, OR USA
___
freebsd-stable@fre
find out why it crashed - if there
> was a power outage, hardware or software issue.
Another thing to do is look in the logs to see if background fsck
is failing for some reason. I've seen it happen in some cases that
background fsck fails and asks for a manual run, in which case th
s probably a bit on the cheap side (ALLNET FW9000).
Could it be a device problem? I've seen that type of error
(including a crash in the end) when a device can't handle DMA.
Disabling DMA solved the problem for me.
--
greg byshenk - gbysh...@byshenk.net - Leiden, NL - Portlan
^
if you want to try it.
It can be used with RELENG_9; check the NOTES file.
--
greg byshenk - gbysh...@byshenk.net - Leiden, NL
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsub
On Mon, Aug 22, 2011 at 11:59:11AM +0100, David Wood wrote:
> In message <20110822094756.gj92...@core.byshenk.net>, Greg Byshenk
> writes
> >It doesn't seem to matter; both cuau?.lock and cuau?.init produce the
> >error (for both ports), and cuau? itself remain
On Mon, Aug 22, 2011 at 10:23:14AM +0100, David Wood wrote:
> In message <20110822083336.gi92...@core.byshenk.net>, Greg Byshenk
> writes
> >On Mon, Aug 22, 2011 at 12:20:33AM +0200, Greg Byshenk wrote:
> >>puc0: mem
> >>0xf9dfc000-0xf9df,0xfa00-
On Mon, Aug 22, 2011 at 12:20:33AM +0200, Greg Byshenk wrote:
> On Sun, Aug 21, 2011 at 09:44:41PM +0100, David Wood wrote:
>
> > I wrote and contributed the support code for the OXPCIe95x serial chips
> > - and just happened to notice your report.
>
> Thanks for th
On Sun, Aug 21, 2011 at 09:44:41PM +0100, David Wood wrote:
> I wrote and contributed the support code for the OXPCIe95x serial chips
> - and just happened to notice your report.
Thanks for the response.
> In message <20110821154249.ge92...@core.byshenk.net>, Greg Byshenk
&
ld be much appreciated. The machine is still in
test phase, so I can mess around with it as necessary.
Thanks.
--
greg byshenk - free...@byshenk.net - Leiden, NL
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/l
Yue Wu wrote:
> > >> > Hello, sorry for poor English, I will try to explan clearer with my
> > >> > best.
> > >> >
> > >> > On Sat, Mar 05, 2011 at 04:48:17PM +0100, Greg Byshenk wrote:
> > >> >> On Sat, Mar 05, 2011 a
ll show you which of
your ports are out of date. Then 'portmaster -PP [...]' will force
package use for updates.
If you have an up-to-date ports tree, then I think that
portmaster -abPP
will update all of your ports, using packages, and save a backup copy
of the installed versi
ainc, it just asks
> for root mountpoint.
>
> And for shure I've got an 2.5" Hitachi HTS542516K9A300 160Gb SATA HDD
>
> If you need any aditional info I'll give it all, just ask.
If you change to SATA native mode, then your HD may
mber. For some reason,
the system was no longer seeing the main hard drive.
I solved the problem by setting 'SATA Native Mode' (or some such) in the
BIOS, which then led my (SATA) drive to be seen at '/dev/ad8'. After
booting from ad8 and modifying my 'fstab', ever
se as
a NAS system.
It may be that the ICC system can export the drives, but it seems like an
unnecessary complication.
--
greg byshenk - gbysh...@byshenk.net - Leiden, NL
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/l
ed perfectly fine with 7.1):
>
> /boot.config:
> -P
>
> /boot/loader.conf:
> kernel_options="-P"
> console="comconsole"
>
> /etc/ttys:
> ttyu0 "/usr/libexec/getty std.9600" vt100 off secure
Shouldn't this:
followup on this issue, I've updated the problem
machine to 8-STABLE (FreeBSD 8.1-STABLE #7: Mon Aug 23 13:01:15 CEST 2010)
and the problem seems to have gone away.
I had a journal overflow this morning, but that is a different problem,
and I think that it should be fixable via tuning a bi
On Mon, Aug 30, 2010 at 04:08:45AM -0700, Jeremy Chadwick wrote:
> Bcc:
> Subject: Re: igb related(?) panics on 7.3-STABLE
> Reply-To:
> In-Reply-To: <20100830094631.gd12...@core.byshenk.net>
>
> On Mon, Aug 30, 2010 at 11:46:31AM +0200, Greg Byshenk wrote:
> >
On Sun, Aug 29, 2010 at 08:16:59PM +0200, Greg Byshenk wrote:
> I've begun seeing problems on a machine running FreeBSD-7.3-STABLE, 64-bit,
> with two igb nics in use. Previously the machine was fine, running earlier
> versions of 7-STABLE, although the load on the network has incr
igb1: [ITHREAD]
igb1: [ITHREAD]
igb1: [ITHREAD]
igb1: [ITHREAD]
igb1: [ITHREAD]
igb1: [ITHREAD]
igb1: [ITHREAD]
igb1: [ITHREAD]
igb1: [ITHREAD]
igb1: [ITHREAD]
igb1: Ethernet address: 00:30:48:ca:cd:73
--
greg byshenk - gbysh...@byshenk.net - Leiden, NL
On Sat, Mar 13, 2010 at 09:33:50PM -0800, Doug Barton wrote:
> On 03/12/10 02:13, Greg Byshenk wrote:
> > I would put in a word for 'mergemaster -F' (or maybe '-iF') in such
> > cases.
> At this point the -U option is generally a safer bet. The only
r 'mergemaster -F' (or maybe '-iF') in such
cases.
It doesn't try to automate much, but it allows one to concentrate on
actual differences by automating the handling of those files where
only the VCS Id is different.
--
greg byshenk - gbysh...@byshenk.net - Leiden, NL
c/master.passwd,
> and the line `+:*::' has already put into /etc/group.
I may be completely wrong (I can't seem to find the source), and I
don't know if it is the source of your problem, but I recall it being
reported that 'passwd_compat' a
On Fri, Jan 22, 2010 at 10:01:02AM +0100, Greg Byshenk wrote:
> On Thu, Jan 21, 2010 at 08:23:23PM -0500, Dan Langille wrote:
> > First, see also my post: do I want ch0 or pass1?
> >
> > I have an external tape library and an external tape drive. They are
> > not
s0 target 0 lun 0 (pass0,ch2)
at scbus0 target 1 lun 0 (sa2,pass1)
at scbus0 target 2 lun 0 (pass2,ch1)
at scbus0 target 3 lun 0 (sa1,pass3)
#
(Currently the first changer is not powered up.)
So I think that what you want is something like
same as the others; it was similar, but
not identical. I changed the motherboard and all the problems went away,
never to reappear.
I don't know if it was a specific problem with that particular
motherboard, or something about that model, but for whatever reason, it
appears that the bu
ally wanted to use it).
When my company relocated to a new building, the entire network was
cabled at CAT6, but we still have some machines and switches that are
100baseTX, and they work fine.
--
greg byshenk - gbysh...@byshenk.net - Leiden, NL
_
# ifconfig em1
em1: flags=8843 metric 0 mtu 1500
options=db
ether 00:07:e9:1a:ae:dc
inet 192.168.1.62 netmask 0xf800 broadcast 192.168.7.255
media: Ethernet autoselect (1000baseLX )
status: active
Any ideas?
On Wed, May 13, 2009 at 06:44:38PM +0200, G
On Wed, May 13, 2009 at 06:42:07PM +0200, Greg Byshenk wrote:
> As a followup to my own previous message, I continue to have annoying
> problems with "em?: watchdog timeout" on one of my machines (now running
> 7.2-STABLE as of 2009-05-08).
>
> I have discontinued using
hine is running nfs and samba (3.2.10, from ports), and pretty
much nothing else.
Anyone have any ideas about this...? I'm going mad with this.
-greg byshenk
# pciconf -lvb
[...]
e...@pci0:7:1:0: class=0x02 card=0x10028086 chip=0x10118086 rev=0x01
hdr=0x00
vendor = &#
ux and
FreeBSD installs, so one thing I've done is to create a pxeboot rescue
image (using the mfsroot from the rescue CD). This means that, if there
is this sort of problem, we can boot into rescue mode from the network
(the BIOS is also redirected to the serial console) and not have to
worr
e, but if this fails, then you should be able to choose
single-user boot from the menu, which will then not try to run fsck or
mount / rw. From there you should be able to fsck and remount /, as well
as /home or anything else. This will fail if there is some
1 D2 D3 current D0
cap 05[50] = MSI supports 32 messages, 64 bit
cap 10[70] = PCI-Express 1 legacy endpoint
--
greg byshenk - gbysh...@byshenk.net - Leiden, NL
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
lags section. I was told in the ports list that you can add it
> to the ServerLayout section but I could never make that work.
I had the same problem yesterday after updating X.
For me, adding dbus_enable="YES" and hald_enable="YES" to rc.con
that its error messages are not particularly
informative).
You can also check to see if you can reach the server. Try a plain telnet
to port 22. You won't actually be able to establish a connection if you
aren't running ssh, but you should see something like:
Connected to .
Es
On Thu, Jan 08, 2009 at 11:47:42AM +0100, Oliver Fromme wrote:
> Greg Byshenk wrote:
> > Andrei Kolu wrote:
> > > NOTE: I do not reboot my system until everything is updated. Why it is
> > > necessary to boot new kernel and then upgrade world is beyound me..YMMW
is that, if something has gone horribly wrong, it is quite easy
to go back and boot kernel.old. If you don't realize that there is
something wrong until after you have installed everything (kernel and
userland), it can be much more difficult to recover.
--
greg byshenk - gbysh...@bys
On Mon, Nov 24, 2008 at 12:49:12PM +0100, Rink Springer wrote:
> Hi Greg,
>
> On Mon, Nov 24, 2008 at 12:42:49PM +0100, Greg Byshenk wrote:
> > backuphost# camcontrol devlist
> > at scbus0 target 0 lun 0 (pass0,ch3)
> >at scbus
0 15:01:16 backuphost kernel: ch: warning: could not map element source
address 30215d to a val
id element type
Nov 20 15:01:16 backuphost kernel: ch: warning: could not map element source
address 25603d to a val
id element type
Nov 20 15:01:16 backuphost kernel: ch: warning: could not map
On Thu, Nov 13, 2008 at 05:08:10PM +0100, Greg Byshenk wrote:
> On Wed, Nov 12, 2008 at 08:42:00PM -0800, Jeremy Chadwick wrote:
>
> > The rest of the below information is good -- but I'm confused about
> > something: is there anyone out there who can use mksnap_ffs on a
rt/spare
I can successfully mksnap_ffs the first (smaller) partition, but an
attempt to do so on any of the others causes a lock.
Note: this is a lockup, not a "slow". The system becomes unresponsive
to any input, and there is no hard drive activity, and this does not
change over a
e and says that something is wrong with
X (and particularly when my experience is that there is nothing wrong
with X), my first response is almost invariably: "what, specifically,
is wrong with X?"
--
greg byshenk - [EMAIL PROTECTED] - Leiden, NL
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
wed by a 'portupgrade -P' on the "clients" (building
packages on the build machine, and then installing via my own packages
on the others). Again, I can't say that it is "better", but it is
certainly faster and easier.
--
greg byshenk - [EMAIL PROTECTED] - Leid
re mouning.
http://lists.freebsd.org/pipermail/freebsd-current/2007-July/075001.html
--
greg byshenk - [EMAIL PROTECTED] - Leiden, NL
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Sat, May 03, 2008 at 11:42:14AM +0100, Doug Rabson wrote:
> On 1 May 2008, at 15:39, Michael Proto wrote:
> >Greg Byshenk wrote:
> >>[...] Basically my problem is that the current Samba3 (samba-3.0.28,1)
> >>won't build on a recent 6-STABLE system (I notic
-I/usr/local/include -DLDAP_DEPRECATED
-I/usr/ports/net/samba3/work/samba-3.0.28/source/lib -D_SAMBA_BUILD_=3 -fPIC
-DPIC -c smbd/oplock_linux.c -o smbd/oplock_linux.o
*** Error code 1
Stop in /usr/ports/net/samba3/work/samba-3.0.28/source.
*** Error code 1
Stop in /usr/ports/net/samba3.
*** Er
my
case I can't use serial.
I can also add that -- though I am not much of a progammer -- I will
happily test anything that anyone might suggest. My machine is not
in production (I built it to do some testing with FreeBSD7 and ZFS),
and I can break it without any real consequences.
mem.c
i386/src/sys/boot/i386/libi386/biossmap.c
...has broken booting on this machine.
Any advice gladly accepted.
--
greg byshenk - [EMAIL PROTECTED] - Leiden, NL
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/lis
On Sun, Jan 06, 2008 at 05:38:30PM +0100, Jose Garcia Juanino wrote:
> El domingo 06 de enero a las 15:41:21 CET, Greg Byshenk escribi?:
> > On Sat, Jan 05, 2008 at 11:28:31PM +0100, Jose Garcia Juanino wrote:
> >
> > > I have a 7.0-PRERELEASE i386 system with a nf
keymap
> keyrate
> font8x16
> font8x14
> font8x8
> blanktime
> .
> Starting sshd.
> Starting cron.
> Local package initialization:
> #
>
>
>
> Also, my /etc/src.conf used to build the world:
>
>
> #
> WITHOUT_ACPI=1
> WITHOUT_ASSERT_DEBUG=1
> WITHOUT_ATM=1
> WITHOUT_AUDIT=1
> WITHOUT_AUTHPF=1
> WITHOUT_BIND_DNSSEC=1
> WITHOUT_BIND_ETC=1
> WITHOUT_BIND_LIBS_LWRES=1
> WITHOUT_BIND_MTREE=1
> WITHOUT_BIND_NAMED=1
> WITHOUT_BLUETOOTH=1
> WITHOUT_I4B=1
> WITHOUT_IPFILTER=1
> WITHOUT_IPX=1
> WITHOUT_KERBEROS=1
> WITHOUT_LPR=1
> WITHOUT_NIS=1
> WITHOUT_PF=1
> WITHOUT_PROFILE=1
> WITHOUT_SENDMAIL=1
> WITHOUT_SHAREDOCS=1
> #
>
>
> The /etc/make.conf file:
>
> #
> CPUTYPE?=pentium3
> MODULES_OVERRIDE= linux if_tap sound/driver/emu10k1 syscons/green \
> linprocfs linsysfs smbfs ntfs ext2fs libiconv \
> libmchain aio if_bridge vesa \
> cd9660_iconv udf_iconv msdosfs_iconv ntfs_iconv \
> zfs bridgestp
> BOOT_COMCONSOLE_PORT= 0x3F8
> BOOT_COMCONSOLE_SPEED= 115200
> PERL_VER=5.8.8
> PERL_VERSION=5.8.8
> #
>
>
>
> Regards
--
greg byshenk - [EMAIL PROTECTED] - Leiden, NL
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
not ... has anyone seen this problem *with* i386?
Yes.
We run Nagios on an i386 machine (dual Athlon MP 1800+), and I first saw this
problem with a build of 6-STABLE as of 2007-10-04, and it continues (if I don't
use the libmap.conf settings) with the running system of 6.3-PRERLEASE as of
2007
sually isn't.
One process is:
[csup, etc.]
make buildworld
make buildkernel
make installkernel [reboot single user]
[mergemaster -p if necessary]
make installworld
mergemaster [reboo
e-to-be", then
you will have the opportunity to do the testing required to ensure that
there are no problems (in your situation) prior to rollout.
--
greg byshenk - [EMAIL PROTECTED] - Leiden, NL
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RST! My situation is not the same as yours,
and something that works fine in my environment may break horribly in yours.
--
greg byshenk - [EMAIL PROTECTED] - Leiden, NL
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
t "old style" behavior, what you want is something like:
passwd: compat
passwd_compat: nis
Alternatively, you can use something like:
passwd: files nis
# passwd_compat: nis
or even:
passwd: winbind nis files
# passwd_compat: nis
[Corrections welcome if I have t
e a serial console.
And what seems to be becoming common on servers is a BIOS that allows
you to fully redirect to serial, including BIOS configuration. The
servers that I have recently purchased have had a keyboard and monitor
plugged into them _once_ -- for the first BIOS setup -- and then never
ag
y used (one is the filestore for a CFD cluster, and the other
for a Maya/Muster rendering cluster), each having two em interfaces
and SMP -- and have not seen any watchdog issues (they are currently
running FreeBSD 6.2-PRERELEASE as of Oct 7 -- but no problems with
any earlier 6.1-STABLE versions
VM connected, and it works fine,
as well. No problems with video, no problems with network, no problems
with ssh login, etc.
-greg
FreeBSD xxx.xxx.com 6.2-PRERELEASE FreeBSD 6.2-PRERELEASE #21: Tue Sep 19
19:37:00 CEST 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sy
one would expect ... it
> shouldn't be so much that he *broke* -STABLE (shit happens, do you want
> your money back?), but it should be 'was he around to reverse his mistake
> in a reasonable amount of time?' ... ?
Exactly.
--
greg byshenk - [EMAIL PROTECTED] - Leiden
ng to lock the same NFS mounted file at
the same time. The result was over 1000 "Cannot allocate memory" errors
followed by rpc.lockd crashing.
I guess the server is telling me it wants an update...
--
greg byshenk - [EMAIL PROTECTED] - Leiden, NL
_
? Is 18Aug06 0:00.00 rpc.statd
[...]
> Well, how odd: as soon as I start the test process 515 on venus goes away.
> Now to wait for it to fail... (doesn't take too long):
[...]
> In conclusion: I agree with Greg Byshenk that the NFS server is bound to
> be the one at fault, BUT, is
I am using. Or there could be a problem with the
configuration of your server. Or there could be something else going
on (in the network...?).
But to see what exactly is happening in your case, you would probably
want to look at what exactly is happening on the client, the server, and
the ne
comments of others) were not meant to imply that one
should not rebuild ports after a major upgrade, but only that one need
not do so _before_ upgrading.
[...probably ... it worked for me ... YMMV ... if it is a critical
package, then it wouldn't hurt to rebuild it first ... usw
ouldn't be necessary to rebuild ports before the upgrade. If
there is something running that is critical, you might want to upgrade
it first, just be sure, but it probably isn't necessary. I upgraded a
workstation with 200+ ports installed, and saw no problems (I can't
fo
On Mon, Aug 21, 2006 at 04:03:47AM +0200, Konstantin Saurbier wrote:
> Am 20.08.2006 um 18:20 schrieb Greg Byshenk:
> >What is different is that this was with a 3Ware RAID controller --
> >which made removing/raconfiguring/rebuilding much easier -- but I was
> >seeing
On Sun, Aug 20, 2006 at 08:22:48PM +0200, Roland Smith wrote:
> On Sun, Aug 20, 2006 at 07:55:47PM +0200, Greg Byshenk wrote:
> > On Sun, Aug 20, 2006 at 07:38:28PM +0200, Roland Smith wrote:
> > > If FreeBSD supports the device, you should see an ar0 device.
> > >
On Sun, Aug 20, 2006 at 07:51:29PM +0200, Miroslav Lachman wrote:
> Greg Byshenk wrote:
[...]
> >This happened four times (with the same errors that have been discussed
> >here), running 6.1 STABLE as of June 22. Before attempting to RMA the
> >drives, I tried an updated
<http://www.gamepc.com/labs/view_content.asp?id=eoyraid&page=2&cookie%5Ftest=1>
is based upon the ICH4, and not Adaptec controller. And, unless I've
missed it, this controller is not supported.
What does dmesg output say about the drives and controller?
--
greg byshenk -
I was
seeing the exact same errors.
This happened four times (with the same errors that have been discussed
here), running 6.1 STABLE as of June 22. Before attempting to RMA the
drives, I tried an updated kernel, 6.1 STABLE as of July 19. Strangely
enough, the problems disappeared.
So, while I
as 74G, rather than the true 148G. I've double-checked all my BIOS
> > settings, and nothing seems out of order. Please help!
--
greg byshenk - [EMAIL PROTECTED] - Leiden, NL
___
freebsd-stable@freebsd.org mailing list
http://lists.freebs
72 matches
Mail list logo
