Re: system crash during make installworld

[Torfinn Ingolfsen]

On Mon, 21 Feb 2011 18:56:36 +0200
Andriy Gapon  wrote:

> on 21/02/2011 10:04 David J Brooks said the following:
> > As the subject suggests, my laptop crashed during make installworld. The new
> > kernel boots, but the ELF interpreter is not found and I cannot get to a 
> > single
> > user prompt. What is the least painful way to proceed?
> 
> My take would be an alternative bootable media: live CD or install CD or etc.

Or, if the hard drive is easy to get at, and he has the a (S)ATA-to-usb dongle 
/ dock; connect the hard drive to another FreeBSD
machine and copy required files off that one.

But first things first: does the old kernel still boot? (depending on
how far in the process make installworld came, it might)

HTH
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: Best way to switch from Linux to BSD

[Torfinn Ingolfsen]

On Tue, 29 Mar 2011 01:32:23 -0400
Jason Hsu  wrote:

> I've been trying to switch from Linux to BSD for my everyday computing 
> (email, word processing, spreadsheets, etc.), but I couldn't get things to 
> work properly.  
> I've been so spoiled by the quickness and user-friendliness of antiX/Swift 
> Linux and Puppy Linux for so long.  I have a backlog of stuff to do, so I'm 
> sticking to Linux for now as my main OS.  
> However, I might try BSD in VirtualBox and on my laptop.

IMO; get a second machine (laptop or workstation / desktop) and install
FreeBSD on that. After you get it working the way you want, you can
dump your Linux machine.

> Are there any good tutorials for using BSD on the desktop?  I'm having much 
> more difficulty finding good information on BSD than was the case for Linux.  
> In retrospect, this shouldn't be a surprise given that Linux is relatively 
> mainstream while BSD is very obscure.

I really don't understand this question.
If you really are asking about *using* BSD on the desktop, there are
very few, if any, differences compared to Linux. The basic GUI is the
same (Xorg), the DE's are the same (the big ones being KDE, Gnome and
Xfce), and almost all user programs are the same. What is the
difference your perceive?


Myself, I have kept one laptop running Linux (Xubuntu), because of two
things:
a) it is very hard (in Norway at least) to find and buy a
laptop that will work almost 100% with FreeBSD, unless I want to
double (or more) the price I can get a good laptop for. Somehow,
Linux manages to adjust to most of the "fails to meet
   specifications" problems of laptop vendors today.
b) Often, I need (or want) to check out a new service or program that
 only runs on Linux (for the time being).

My main workstation is a desktop, running FreeBSD.
All my test machines (most of them have desktops installed) run
FreeBSD. Granted, many of them are triple-boot and run Linux and other
BSDs as well, for testing purposes.
My servers run FreeBSD.

HTH
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: ZFS pool on FreeBSD 8.2-STABLE broken?

[Torfinn Ingolfsen]

On Wed, 30 Mar 2011 14:53:16 -0400
"J. Hellenthal"  wrote:

> He specifically does not need -9 to get v28 code for this recovery 
> operation. Martin Matuska does a pretty swell job of keeping these [1]
> up-to-date so in-case something does go wrong it can be fixed fairly 
> quickly without having to go through and rebuild this and that.
> 
> 1. http://mfsbsd.vx.sk/

Ah... very useful tools. Thanks for mentioning.
And thanks to Martin Matuska for doing this.

Have a nice day, everyone.
-- 
Regards,
Torfinn Ingolfsen
___
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"

Re: Constant rebooting after power loss

[Torfinn Ingolfsen]

On Sun, 03 Apr 2011 13:04:54 +0100
Bruce Cran  wrote:

> On 01/04/2011 16:47, Stefan `Sec` Zehl wrote:
> 
> > If you want to get rid of the reboot loop, set:
> >
> > background_fsck="NO"
> >
> > Then it will either come up, or ask for help if anything fails.
> 
> I realise that people like having systems that come up quickly after a 
> crash, but is it worth reconsidering disabling background fsck by 
> default since it can cause issues like this?

Based _only_ on my own experience, and personal preference, I would say
"NO". 

The reason?
It works nicely the way it is now, and any problems will be noticed,
and can be fixed with a bit of effort, even for a person with little
experience in running FreeBSD machines.

One of the reasons that I like FreeBSD is that it gives me tools I
need, but it doesn't try to automate or abstract away my responsiblites
as a system administrator.

I think the FreeBSD project has managed something impressive; being a
platform for bringing in new ideas / tools, and at the same time
staying conservative (POLA, and well thought out changes).

I like that.
-- 
Regards,
Torfinn Ingolfsen
FreeBSD user & FreeBSD sysadmin on the personal / hobby level,
for many, many years
___
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"

panic in FreeBSD 8.2-stable.

[Torfinn Ingolfsen]

In case this is useful.
One of my machines just had a panic (transcribed by me):
panic: bad pte
cpuid = 0
KDB: stack backtrace:
#0 0x80603f6e at kdb_backtrace+0x5e
#1 0x805d1ae7 at panic+0x187
#2 0x808b5c08 at pmap_remove_pages+0x408
#3 0x805a3435 at exec_new_vmspace+0x285
#4 0x80589d20 at exec_elf64_imgact+0x3f0
#5 0x805a3813 at kern_execve+0x3b3
#6 0x805a4bed at execve+0x3d
#7 0x8060ff55 at syscallenter+0x1e5
#8 0x808bce6b at syscall+0x4b
#9 0x808a5642 at Xfast_syscall+0xe2
Uptime: 1d0h10m39s

The machine is running FreeBSD 8.2-stable:
root@kg-quiet# uname -a
FreeBSD kg-quiet.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #0: Sun Apr  3 19:49:05 
CEST 2011 r...@kg-quiet.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64

Hardware info here:
http://sites.google.com/site/tingox/rs480m2

HTH
-- 
Torfinn

___
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"

Re: System extremely slow under light load

[Torfinn Ingolfsen]

On Mon, 25 Apr 2011 16:23:37 +0200
Bartosz Fabianowski  wrote:

> > Try Knoppix, or Ubuntu LiveCD.  I tend to use the former for rescue
> > situations:
> 
> Thanks. I am aware of both - but neither boots from USB (and I have no 
> CD-Rs at hand). I am running UNetbootin under Windows XP in VirtualBox 
> right now to try and get Xubuntu 10.04 onto a USB key. It is really sad 
> that almost all Linux distributions require this detour via a 
> proprietary operating system.

Have you tried just using dd to copy the iso image of a Ubuntu / Linux
LiveCD to a suitably sized USB memory stick?
It has worked for me in the past.
YMMV.
-- 
Torfinn

___
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"

Re: mountlate not late enough for nfe0 with dhcp

[Torfinn Ingolfsen]

On Fri, 27 May 2011 12:36:27 +0300
nickolas...@gmail.com wrote:

> 2011/5/27 Jeremy Chadwick :
> > This has been discussed at length in the past, causing me to write an
> > rc.d script to work around the problem.  You can drop this script into
> > /usr/local/etc/rc.d, chmod 755 it, and make use of it appropriately.
> > The comments in the script should help you understand it.
> >
> > http://jdc.parodius.com/freebsd/netwait
> >
> > Example entries in rc.conf:
> >
> > netwait_enable="yes"
> > netwait_ip="4.2.2.1 4.2.2.2"
> > netwait_if="em0"
> 
> Maybe it's time to add this script to -STABLE?
> Problem touch many people, who need it (IMHO)

Or, if the FAQ at freebsd.org isn't updated already, simply write about this 
script there?
HTH
-- 
Torfinn

___
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"

Fileserver panic - FreeBSD 8.1-stable and zfs

[Torfinn Ingolfsen]

FYI, in case it is interesting
my zfs fileserver[1] just had a panic: (transcribed from screen)
panic: kmem_malloc(131072): kmem_map too small: 1324613632 total allocated
cpuid = 1
KDB: stack backtrace:
#0 0x805df92e at kdb_backtrace+0x5e
#1 0x805ada77 at panic+0x187
#2 0x80800190 at kmem_alloc+0
#3 0x807f7e0a at uma_large_malloc+0x4a
#4 0x8059aee7 at malloc+0xd7
#5 0x80ed6763 at vdev_queue_io_to_issue+0x1c3
#6 0x80ed68e9 at vdev_queue_io_done+0x99
#7 0x80ee6c9f at zio_vdev_io_done+0x7f
#8 0x80ee7237 at zio_execute+0x77
#9 0x80e872f3 at taskq_run_safe+0x13
#10 0x805ea984 at taskqueue_run+0xa4
#11 0x805eabf6 at taskqueue_thread_loop+0x46
#12 0x80584278 at fork_exit+0x118
#13 0x8087f2fe at fork_trampoline+0xe
Uptime: 109d19h47m1s
Cannot dump. Device not defined or unavailable.
Automatic reboot in 15 seconds - press a key on the console to abort
And the machine hung here, no response from keyboard.

The machine runs:
root@kg-f2# uname -a
FreeBSD kg-f2.kg4.no 8.1-STABLE FreeBSD 8.1-STABLE #4: Fri Oct 29 12:11:48 CEST 
2010 r...@kg-f2.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64

FWIW; i had started a scrub of one of the pools (zpool scrub storage) some time 
before this, 
I do not know how far it was before this happened (a scrub of this pool 
normally takes about 3 hours).

Since the machine was totally unresponsive, I rebooted it. after reboot, I 
found out that the scrub was not finished:
root@kg-f2# zpool status storage
  pool: storage
 state: ONLINE
 scrub: scrub in progress for 307445734561825858h22m, 2.76% done, 
307445734561825792h47m to go
config:

NAMESTATE READ WRITE CKSUM
storage ONLINE   0 0 0
  raidz1ONLINE   0 0 0
ad8 ONLINE   0 0 0
ad10ONLINE   0 0 0
ad12ONLINE   0 0 0
ad14ONLINE   0 0 0
ada0ONLINE   0 0 0

errors: No known data errors

HTH

References:
1) http://sites.google.com/site/tingox/ga-ma74gm-s2h_freebsd
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: Fileserver panic - FreeBSD 8.1-stable and zfs

[Torfinn Ingolfsen]

On Thu, 02 Jun 2011 12:50:26 -0700
Jeremy Chadwick  wrote:
> 
> This is a well-known thing with ZFS on FreeBSD.  Because you're running
> 8.1-STABLE, this makes figuring out all the tunables and so on a lot
> more difficult than if you were running 8.2-STABLE.

FWIW, the machine has been quite stable for me for a long time.

> Please provide:
> 
> 1) Contents of /boot/loader.conf

root@kg-f2# more /boot/loader.conf
zfs_load="YES"
vfs.root.mountfrom="zfs:zroot"
siis_load="YES"
amdtemp_load="YES"
# testing without MSI
hw.pci.enable_msix="0"
hw.pci.enable_msi="0"

> 2) Output from: sysctl hw.physmem hw.usermem hw.realmem (your hardware
>page says 4GB, but I can't be bothered to sift through multi-pages
>of wiki documents and links to find the answers)

root@kg-f2# sysctl hw.physmem hw.usermem hw.realmem
hw.physmem: 4141920256
hw.usermem: 3721527296
hw.realmem: 4966055936


> 3) Output from: sysctl vfs.zfs.zio.use_uma

root@kg-f2# sysctl vfs.zfs.zio.use_uma
vfs.zfs.zio.use_uma: 0


> The scrub itself was not ultimately responsible for this problem
> (meaning "the bug is not in scrub").  The problem is that your kernel
> effectively wanted more memory for ZFS operations than was available.

Understood. I didn't mean to imply it was; I just tried to provide data about 
activity on the server
that might have contributed to the failure.
FWIW, the scrub finished fine:
root@kg-f2# zpool status storage
   pool: storage
 state: ONLINE
 scrub: scrub completed after 307445734561825860h15m with 0 errors on Thu Jun  
2 23:23:44 2011
config:

NAMESTATE READ WRITE CKSUM
storage ONLINE   0 0 0
  raidz1ONLINE   0 0 0
ad8 ONLINE   0 0 0
ad10ONLINE   0 0 0
ad12ONLINE   0 0 0
ad14ONLINE   0 0 0
ada0ONLINE   0 0 0

errors: No known data errors

> The "trick" is to tune /boot/loader.conf until you can gain stability.

Well, the server has been reasonably stable for me for about a year now
(I had to replace a failing hard drive, but I count that as "wear" not 
"instability").

> Again, because you're running 8.1-STABLE, the tuning parameters here
> will behave different than on 8.2-STABLE.  We can go over those in a
> follow-up thread.

I have no trouble with upgrading the server to 8.2-stable, if now is a good 
time to do it.
(I haven't watched closely for any zfs related problems on the mailing list 
lately.)

> I've gotten to the point where I literally cannot remember all of the
> different situations/conditions/tunings for each FreeBSD kernel build,
> release, date, type, etc., so I tend to focus on the most recent
> RELENG_8 build.  Then someone comes along with an older build.
> Hehe.  :-)

I know what you mean. Keeping up with all this "stuff" is getting harder every 
year. :)
-- 
Torfinn

___
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"

Re: Fileserver panic - FreeBSD 8.1-stable and zfs

[Torfinn Ingolfsen]

On Thu, 02 Jun 2011 12:44:49 -0700
Artem Belevich  wrote:

> It's probably one of the most frequently reported issues with ZFS.
> While things got quite a bit better lately, you still need to bump up
> kernel VM size with vm.kmem_size tunable. I typically set vm.kmem_size
> tunable to ~2x physical memory size.

Mine is currently untuned:
root@kg-f2# sysctl vm.kmem_size
vm.kmem_size: 1331953664

I guess I have been lucky; the server has been stable for a long time
now.

> In general you may want to update to the latest -stable. There were a
> lot of ZFS fixes committed.

Yes, perhaps now is a good time to do so. I have held back on updates
on this machine, to find out if zfs was stable. And I think it has
been, for me at least.
-- 
Torfinn

___
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"

Re: Fileserver panic - FreeBSD 8.1-stable and zfs

[Torfinn Ingolfsen]

Update:

On Thu, 02 Jun 2011 16:09:21 -0700
Jeremy Chadwick  wrote:

> Anyway, your system has 4GB of RAM installed in it, so on 8.1-STABLE I'd
> recommend you try these settings:
> 
> vm.kmem_size="3584M"
> vm.kmem_size_max="3584M"
> vfs.zfs.arc_max="2048M"
> 
> Now, these are all chosen by me off the top of my head with absolutely
> ZERO knowledge of what the memory usage on this system is like
> **without** ZFS in the picture.  I'm making a lot of assumptions, and
> I'm assuming worst-case scenarios.  For example, if this machine also
> runs mysqld and its tuned to take up a lot of memory, I would advocate
> dropping vfs.zfs.arc_max to 1536M or 1024M.  Please don't drop it "too
> much"; ZFS performs best when it has lots of ARC.
> 
> Since you mentioned going to 8.2-STABLE, all you need to tune on that
> version is one single tunable:
> 
> vfs.zfs.arc_max

The machine now runs 8.2-stable:
root@kg-f2# uname -a
FreeBSD kg-f2.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #5: Fri Jun  3 17:20:39 CEST 
2011 r...@kg-f2.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64
And I have added the following to /boot/loader.conf:
vfs.zfs.arc_max="2048M"
Hopefully, this will keep the machine rock solid (unitil something else 
happens, at least).

Oh, and thanks for your advice - really helpful.
-- 
Torfinn

___
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"

Re: kern/143370: splash_txt ASCII splash screen module

[Torfinn Ingolfsen]

On Wed, 29 Jun 2011 22:50:15 +1000
Antony Mawer  wrote:

> Hi all,
> 
> Not sure if this is the right place to post it -- about 6 years ago I
> put together a module which displays an ASCII splash screen on boot
> (rather than the graphical splash_pcx and splash_bmp modules). We have
> been running it in production since that time without issue.

So, the difference between this and loader.conf's loader_logo construct is that
a) this is a proper splash screen module
b) you can / must design your splash screen with a separate program (compared 
to write / modify Forth code)

Is my understanding correct?
-- 
Torfinn

___
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"

Re: booting 8.2 on Gigabyte GA-790XTA-UD4

[Torfinn Ingolfsen]

On Tue, 18 Oct 2011 21:17:58 +0200
Václav Zeman  wrote:

> I am having problems booting the FreeBSD 8.2 CD image on 
> GA-790XTA-UD4(rev. 1.0). The last thing that I can see is "BIOS drive A: 
> is disk0". Is this completely not supported? Can I do anything to 
> install FreeBSD on such box?

Have you done the usual stuff?
- if not running the latest BIOS, try to update
- try to fiddle with relevant settings in BIOS
- Try another release of FreeBSD (older or newer), or a new snapshot
- Google "name of board + FreeBSD"

HTH
-- 
Torfinn

___
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"

FreeBSD 8.2-stable: devd fails to restart

[Torfinn Ingolfsen]

Hi,

I thought this bug was fixed back in 2009?
root@kg-v7# uname -a
FreeBSD kg-v7.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #7: Sat Jul  9 23:00:31 CEST 
2011 r...@kg-v7.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64
root@kg-v7# 
root@kg-v7# service devd status
devd is running as pid 555.
root@kg-v7# service devd restart
Stopping devd.
Starting devd.
devd: devd already running, pid: 555
/etc/rc.d/devd: WARNING: failed to start devd
root@kg-v7# service devd status
devd is not running.

What gives?
-- 
Torfinn

___
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"

Re: FreeBSD 8.2-stable: devd fails to restart

[Torfinn Ingolfsen]

On Thu, 02 Feb 2012 21:45:26 -0800
Doug Barton  wrote:

> 
> Actually all the OP needs to do is to make sure the src tree is up to
> date and run mergemaster. I MFC'ed the relevant changes to rc.d/devd
> last April.

Strange, my machine was rebuilt later than that (yes, I always run mergemaster 
as part of the the "make world"):
root@kg-v7# uname -a
FreeBSD kg-v7.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #7: Sat Jul  9 23:00:31 CEST 
2011 r...@kg-v7.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64
root@kg-v7# 
root@kg-v7# head -3 /etc/rc.subr
# $NetBSD: rc.subr,v 1.67 2006/10/07 11:25:15 elad Exp $
# $FreeBSD: src/etc/rc.subr,v 1.88.2.16 2011/04/29 20:31:52 dougb Exp $
#
root@kg-v7# head -3 /etc/rc.d/devd
#!/bin/sh
#
# $FreeBSD: src/etc/rc.d/devd,v 1.11.2.2 2011/04/29 20:31:52 dougb Exp $

Another machine which also has the same problem:
root@kg-v2# uname -a
FreeBSD kg-v2.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #4: Sat Jul 16 02:07:14 CEST 
2011 r...@kg-v2.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64
root@kg-v2# head -3 /etc/rc.subr
# $NetBSD: rc.subr,v 1.67 2006/10/07 11:25:15 elad Exp $
# $FreeBSD: src/etc/rc.subr,v 1.88.2.17 2011/07/03 16:32:03 jilles Exp $
#
root@kg-v2# head -3 /etc/rc.d/devd
#!/bin/sh
#
# $FreeBSD: src/etc/rc.d/devd,v 1.11.2.2 2011/04/29 20:31:52 dougb Exp $

Is that the versions you are referring to?

I have a machine with world built in December, it seems to have the same 
versions of the files:
(note: i have not tried restarting devd on that machine)
root@kg-vm# uname -a
FreeBSD kg-vm.kg4.no 8.2-STABLE FreeBSD 8.2-STABLE #4: Sat Dec 17 17:47:43 CET 
2011 r...@kg-vm.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64
root@kg-vm# head -3 /etc/rc.subr
# $NetBSD: rc.subr,v 1.67 2006/10/07 11:25:15 elad Exp $
# $FreeBSD: src/etc/rc.subr,v 1.88.2.17 2011/07/03 16:32:03 jilles Exp $
#
root@kg-vm# head -3 /etc/rc.d/devd
#!/bin/sh
#
# $FreeBSD: src/etc/rc.d/devd,v 1.11.2.2 2011/04/29 20:31:52 dougb Exp $

-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: FreeBSD 8.2-stable: devd fails to restart

[Torfinn Ingolfsen]

On Fri, 03 Feb 2012 08:34:10 +0300
Sergey Kandaurov  wrote:

> Please apply this patch and report how it goes for you.
> http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/rc.d/devd.diff?r1=1.12;r2=1.13
> 
> This is not in 8-STABLE yet.

It looks like it (or almost the same) is here already:
root@kg-v2# more /etc/rc.d/devd
#!/bin/sh
#
# $FreeBSD: src/etc/rc.d/devd,v 1.11.2.2 2011/04/29 20:31:52 dougb Exp $
#

# PROVIDE: devd
# REQUIRE: netif network_ipv6
# BEFORE: NETWORKING mountcritremote
# KEYWORD: nojail shutdown

. /etc/rc.subr

name="devd"
rcvar=`set_rcvar`
command="/sbin/${name}"

start_precmd=${name}_prestart
stop_precmd=find_pidfile

find_pidfile()
{
if get_pidfile_from_conf pid-file /etc/devd.conf; then
pidfile="$_pidfile_from_conf"
else
pidfile="/var/run/${name}.pid"
fi
}

devd_prestart ()
{
find_pidfile

# If devd is disabled, turn it off in the kernel to avoid memory leaks.
if ! checkyesno ${rcvar}; then
$SYSCTL hw.bus.devctl_disable=1
fi
}

load_rc_config $name
run_rc_command "$1"

HTH
-- 
Torfinn

___
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"

Re: FreeBSD 8.2-stable: devd fails to restart

[Torfinn Ingolfsen]

On Fri, 03 Feb 2012 23:37:56 -0500
Jason Hellenthal  wrote:

> 
> Just because of what I read already is pretty terse I am top-posting for
> a reason.
> 
> $ su -
> # /etc/rc.d/devd stop
> # pgrep -l devd   (This should show nothing if so kill the results)

Done:
root@kg-v2# /etc/rc.d/devd stop
devd not running?
root@kg-v2# pgrep -l devd
root@kg-v2# 

> # /sbin/devd -D -d(Paste the results)

The first output was longer than my scrollback buffer, so I tried it one more 
time.
Now it just "hangs" here:
root@kg-v2# /sbin/devd -D -d
Parsing /etc/devd.conf
setting 
scsi-controller-regex=(aac|adv|adw|aha|ahb|ahc|ahd|aic|amd|amr|asr|bt|ciss|ct|dpt|esp|ida|iir|ips|isp|mlx|mly|mpt|ncr|ncv|nsp|stg|sym|trm|wds)[0-9]+
Parsing files in /etc/devd
Parsing /etc/devd/asus.conf
Parsing /etc/devd/uath.conf
Parsing /etc/devd/usb.conf
Parsing files in /usr/local/etc/devd
Parsing /usr/local/etc/devd/webcamd.conf

Strange.
I tried deinstalling webcamd (yes, a shot in the dark, I know), but it didn't 
help:

root@kg-v2# pkg_deinstall webcamd-3.2.0.2
--->  Deinstalling 'webcamd-3.2.0.2'
==> You should manually remove the "webcamd" user. 
[Updating the pkgdb  in /var/db/pkg ... - 954 packages found 
(-1 +0) (...) done]
root@kg-v2# pgrep -l devd
root@kg-v2# /sbin/devd -D -d
Parsing /etc/devd.conf
setting 
scsi-controller-regex=(aac|adv|adw|aha|ahb|ahc|ahd|aic|amd|amr|asr|bt|ciss|ct|dpt|esp|ida|iir|ips|isp|mlx|mly|mpt|ncr|ncv|nsp|stg|sym|trm|wds)[0-9]+
Parsing files in /etc/devd
Parsing /etc/devd/asus.conf
Parsing /etc/devd/uath.conf
Parsing /etc/devd/usb.conf
Parsing files in /usr/local/etc/devd
-- 
Torfinn

___
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"

Re: FreeBSD 8.2-stable: devd fails to restart

[Torfinn Ingolfsen]

More data:
root@kg-v2# service devd status
devd is not running.
root@kg-v2# service devd start
Starting devd.
devd: devd already running, pid: 808
/etc/rc.d/devd: WARNING: failed to start devd
root@kg-v2# rm /var/run/devd.pid
root@kg-v2# service devd start
Starting devd.
root@kg-v2# service devd status
devd is running as pid 30165.
root@kg-v2# service devd stop
Stopping devd.
root@kg-v2# service devd status
devd is not running.
root@kg-v2# ll /var/run/devd.pid
-rw---  1 root  wheel  5 Feb  4 16:45 /var/run/devd.pid
root@kg-v2# service devd start
Starting devd.
root@kg-v2# service devd status
devd is running as pid 30206.

Let me try to install the webcamd port again... done.
Now testing again:
root@kg-v2# service devd status
devd is running as pid 30206.
root@kg-v2# service devd stop
Stopping devd.
root@kg-v2# ll /var/run/devd.pid
-rw---  1 root  wheel  5 Feb  4 16:48 /var/run/devd.pid
root@kg-v2# service devd status
devd is not running.
root@kg-v2# service devd start
Starting devd.
root@kg-v2# service devd status
devd is running as pid 35551.

Not really sure what's going on here.
-- 
Torfinn

___
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"

Re: FreeBSD 8.2-stable: devd fails to restart

[Torfinn Ingolfsen]

On Sat, 04 Feb 2012 10:34:19 -0700 (MST)
Warren Block  wrote:

> 
> Possibly relevant:
> http://www.freebsd.org/cgi/query-pr.cgi?pr=140462&cat=
> 
> (Using DHCP from /etc/rc.conf leaves a lock on devd.pid.  SYNCDHCP does 
> not.)
> 
> And the thread:
> http://lists.freebsd.org/pipermail/freebsd-current/2009-October/012749.html

Yes, it seems to be that problem. Tested on my other machine, which hasn't 
changed since the problem was discovered:
root@kg-v7# service devd status
devd is not running.
root@kg-v7# ll /var/run/devd.pid
-rw---  1 root  wheel  3 Jan 12 20:40 /var/run/devd.pid
root@kg-v7# lsof /var/run/devd.pid
COMMAND   PID  USER   FD   TYPE DEVICE SIZE/OFF   NODE NAME
dhclient 1075  root5w  VREG   0,703 918547 /var/run/devd.pid
dhclient 1091 _dhcp5w  VREG   0,703 918547 /var/run/devd.pid
root@kg-v7# 

So, if this was worked on back in 2009, why isn't fixed yet?
-- 
Torfinn

___
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"

Re: FreeBSD 8.2-stable: devd fails to restart

[Torfinn Ingolfsen]

On Mon, 06 Feb 2012 00:08:55 -0700 (MST)
Warren Block  wrote:

> On Sat, 4 Feb 2012, Torfinn Ingolfsen wrote:
> 
> > On Sat, 04 Feb 2012 10:34:19 -0700 (MST)
> > Warren Block  wrote:
> >
> >>
> >> Possibly relevant:
> >> http://www.freebsd.org/cgi/query-pr.cgi?pr=140462&cat=
> >>
> >> (Using DHCP from /etc/rc.conf leaves a lock on devd.pid.  SYNCDHCP does
> >> not.)
> >>
> >> And the thread:
> >> http://lists.freebsd.org/pipermail/freebsd-current/2009-October/012749.html
> >
> > Yes, it seems to be that problem. Tested on my other machine, which hasn't 
> > changed since the problem was discovered:
> > root@kg-v7# service devd status
> > devd is not running.
> > root@kg-v7# ll /var/run/devd.pid
> > -rw---  1 root  wheel  3 Jan 12 20:40 /var/run/devd.pid
> > root@kg-v7# lsof /var/run/devd.pid
> > COMMAND   PID  USER   FD   TYPE DEVICE SIZE/OFF   NODE NAME
> > dhclient 1075  root5w  VREG   0,703 918547 /var/run/devd.pid
> > dhclient 1091 _dhcp5w  VREG   0,703 918547 /var/run/devd.pid
> > root@kg-v7#
> >
> > So, if this was worked on back in 2009, why isn't fixed yet?
> 
> I switched to using SYNCDHCP which avoids the problem, didn't enter a 
> PR, and quickly forgot about it.  It would be nice to have it fixed.

I'm all for getting it fixed, even if I don't know how yet.
Should a PR be against devd, dhclient, or ... something else?
-- 
Torfinn

___
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"

Re: FreeBSD 8.2-stable: devd fails to restart

[Torfinn Ingolfsen]

On Tue, 07 Feb 2012 12:16:15 -0700 (MST)
Warren Block  wrote:

> 
> It's devd, IMO.  Hey, come to think of it, I did enter a PR, the one 
> above.  If this is still a problem in 9 (which I can test in a bit), 
> posting to -current might get some needed attention on it.

PR updated.
-- 
Torfinn

___
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"

Re: FreeBSD9 and the sheer number of problem reports

[Torfinn Ingolfsen]

On Thu, 23 Feb 2012 19:25:01 +0100
Damien Fleuriot  wrote:

> 
> In the current state of things, I have *absolutely* no wish to run it in
> production :(

Nobody forces you to jump onto the 9.0-release bandwagon. You can choose to 
skip it.
If you skip 9.0 - will you be better prepared and less fearful when 9.1-release 
comes?
You decide.
-- 
Torfinn

___
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"

FreeBSD 9.0 - GPT boot problems?

[Torfinn Ingolfsen]

Hi,
I just installed FreeBSD 9.0-release / amd64 on a new machine (Acer Aspire 
X1470).
I installed from a usb memory stick (the default amd64 image), which I booted 
by pressing "F12" and selecting it from the boot menu on the machine.
I installed on a SSD (which replaced the hard drive originally in the machine), 
using the default scheme for 9.0 (GPT).
The installation was painless (many thanks to all who made it that way), but 
when I try to boot the machine from the SSD afterwards, I just get this message 
from the BIOS:
"ERROR: No boot disk has been detected or the disk has failed."
I tried selecting the SSD from the boot menu (via F12) instead (it shows up as 
"EFI: M4-CT128M4SSD2"), but got the same message.
I upgraded the BIOS from version P01-A3 to version P01-A4 (the newest 
available), still no dice.

If I use the usb stick I installed from, I can select the boot device, and 
actually boot from it, so there doesn't seem to be anything wrong with the SSD.
I tried:
kg-vm2# gpart bootcode -b /boot/pmbr -p /boot/gptboot -i 1 ada0
bootcode written to ada0

in case there was something wrong with the bootcode, but I still get the 
message "ERROR: No boot disk has been detected or the disk has failed."
gpart shows this:
root@kg-vm2# gpart show ada0
=>   34  250069613  ada0  GPT  (119G)
 34128 1  freebsd-boot  (64k)
162  119537664 2  freebsd-ufs  (57G)
  1195378268388608 3  freebsd-swap  (4.0G)
  127926434  121634816 4  freebsd-ufs  (58G)
  249561250 508397- free -  (248M)
and root is on ada0p2, with swap on ada0p3:
root@kg-vm2# df -h
Filesystem SizeUsed   Avail Capacity  Mounted on
/dev/ada0p2 56G2.3G 49G 4%/
devfs  1.0k1.0k  0B   100%/dev
root@kg-vm2# swapinfo -h
Device  1K-blocks UsedAvail Capacity
/dev/ada0p3   4194304   0B 4.0G 0%

Has anyone seen anything like this before?
Any hints on what I can do?

References:
1) http://sites.google.com/site/tingox/aspire_x1470_fbsd
-- 
Torfinn Ingolfsen 
___
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"

Re: FreeBSD 9.0 - GPT boot problems?

[Torfinn Ingolfsen]

On Sat, 24 Mar 2012 18:50:13 +0100
Christian Laursen  wrote:

> It sounds a bit like the BIOS thinks that since the disk uses GPT you 
> want to EFI boot.

That could very well be the case.

> As far as I know the default bootcode in the PMBR is 
> meant for old style BIOS booting.

Hmm, I was hoping that the pmbr / gptboot would work "both ways".

> Is it possible to disable EFI in your BIOS? If that is the case, that's 
> probably the easiest solution.

No, I haven't found any place to do that.
Before I installed FreeBSD on this SSD (before it was partitioned with gpart) 
it showed up in
the BIOS under "hard drive". (Other choices are "removable drive"
Now it shows up under "EFI device", and doesn't show up under "hard drive".

> I'm unsure of the current state of EFI boot in FreeBSD but a little bit 
> of searching did not look promising.

Yes, after a bit of searching I agree with you.
If anyone knows of a EFI capable boot loader for FreeBSD, I'm willing to try it.
Rather that, than having to deal with grub, elilo or the other stuff.
-- 
Torfinn Ingolfsen 
___
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"

Re: FreeBSD 9.0 - GPT boot problems?

[Torfinn Ingolfsen]

On Sat, 24 Mar 2012 17:26:03 +0100
Torfinn Ingolfsen  wrote:

> Hi,
> I just installed FreeBSD 9.0-release / amd64 on a new machine (Acer Aspire 
> X1470).
> I installed from a usb memory stick (the default amd64 image), which I booted 
> by pressing "F12" and selecting it from the boot menu on the machine.
> I installed on a SSD (which replaced the hard drive originally in the 
> machine), using the default scheme for 9.0 (GPT).
> The installation was painless (many thanks to all who made it that way), but 
> when I try to boot the machine from the SSD afterwards, I just get this 
> message from the BIOS:
> "ERROR: No boot disk has been detected or the disk has failed."
> I tried selecting the SSD from the boot menu (via F12) instead (it shows up 
> as "EFI: M4-CT128M4SSD2"), but got the same message.
> I upgraded the BIOS from version P01-A3 to version P01-A4 (the newest 
> available), still no dice.

Just an update: 
today I connected another disk to the machine (I used a sata-to-usb adapter, 
but I think that doesn't matter), this disk is MBR-partitioned,
and the machine boots from this with no problems using the boot menu (via F12).
root@kg-vm2# gpart show -p da1
=>   63  117210177da1  MBR  (55G)
 63   29350692  da1s1  freebsd  (14G)
   29350755   29360079  da1s2  freebsd  [active]  (14G)
   58710834   58499406 - free -  (27G)

The non-working disk looks like this:
root@kg-vm2# gpart show -p ada0
=>   34  250069613ada0  GPT  (119G)
 34128  ada0p1  freebsd-boot  (64k)
162  119537664  ada0p2  freebsd-ufs  (57G)
  1195378268388608  ada0p3  freebsd-swap  (4.0G)
  127926434  121634816  ada0p4  freebsd-ufs  (58G)
  249561250 508397  - free -  (248M)


-- 
Torfinn

___
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"

Re: Restricting users from certain privileges

[Torfinn Ingolfsen]

On Sat, 28 Apr 2012 09:50:30 +0200
Zenny  wrote:

> Thanks Daniel, but sudo gives all (not selective) root privileges to the
> user (admin in my case). So this is not what I am trying to achieve in my
> original post.

FWIW, sudo can be configured to allow only some commands.
HTH
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: VirtualBox, AIO and zvol's - a cautionary tale

[Torfinn Ingolfsen]

On Wed, 23 May 2012 14:11:48 +0100
Pete French  wrote:

> Solution is simple - disable AIO. All then goes back to being nice
> and stable again. But it did take a while to find.
> 
> Hope someone else finds the info usefull!

Useful - thanks!
-- 
Torfinn Ingolfsen 
___
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"

Re: [8-STABLE] USB printer disconnecting when trying to print

[Torfinn Ingolfsen]

On Fri, 21 May 2010 10:29:04 +0200
Thomas Gellekum  wrote:

> echo "hallo" > /dev/ulpt0
> [...]
> Any ideas on how to debug this are welcome.

Most of todays printers do NOT understand plain text, usually you need a driver 
which transforms whatever you want to print into
the language the printer understands.
See http://www.openprinting.org/printer/Brother/Brother-HL-1250
for more info.

HTH
-- 
Torfinn Ingolfsen

___
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"

Re: FreeBSD eats 169.254.x.x addressed packets

[Torfinn Ingolfsen]

On Tue, 08 Jun 2010 14:30:49 -0400
Stephen Clark  wrote:

> Hmmm... how is not responding to pings associated with forwarding?

See http://en.wikipedia.org/wiki/169.254
Link Local addresses are special.

HTH
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: 8.x grudges

[Torfinn Ingolfsen]

On Wed, 07 Jul 2010 14:22:22 -0400
"Mikhail T."  wrote:

>9.
>   The k8temp utility (installed by sysutils/k8temp
>   ), which worked fine on
>   both of my AMD-machines, no longer works on the Athlon one (still
>   works on the Opteron-based server).

In case you are not aware of it: amdtemp(4) performs the same function (more or 
less) as k8temp.
HTH
-- 
Torfinn

___
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"

Re: 8.x grudges

[Torfinn Ingolfsen]

On Wed, 07 Jul 2010 12:34:55 -0700
Kevin Oberman  wrote:

> k8temp is for older AMD system running K8 cores. It has been mostly
> replaced with amdtemp which works on newer cores. I'm not sure if
> amdtemp will work on K8 cores, though.

It does (amdtemp works on K8s):
r...@kg-quiet# uname -a
FreeBSD kg-quiet.kg4.no 7.3-STABLE FreeBSD 7.3-STABLE #8: Mon Apr  5 21:10:07 
CEST 2010 r...@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET  amd64
r...@kg-quiet# sysctl hw.machine
hw.machine: amd64
r...@kg-quiet# sysctl dev.amdtemp
dev.amdtemp.0.%desc: AMD K8 Thermal Sensors
dev.amdtemp.0.%driver: amdtemp
dev.amdtemp.0.%parent: hostb4
dev.amdtemp.0.sensor0.core0: 45.0C
dev.amdtemp.0.sensor0.core1: 46.0C
dev.amdtemp.0.sensor1.core0: 46.0C
dev.amdtemp.0.sensor1.core1: 46.0C

HTH
-- 
Torfinn

___
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"

Re: 8.x grudges

[Torfinn Ingolfsen]

On Thu, 08 Jul 2010 00:20:56 +0200
Torfinn Ingolfsen  wrote:

> On Wed, 07 Jul 2010 12:34:55 -0700
> Kevin Oberman  wrote:
> 
> > k8temp is for older AMD system running K8 cores. It has been mostly
> > replaced with amdtemp which works on newer cores. I'm not sure if
> > amdtemp will work on K8 cores, though.
> 
> It does (amdtemp works on K8s):
> r...@kg-quiet# uname -a
> FreeBSD kg-quiet.kg4.no 7.3-STABLE FreeBSD 7.3-STABLE #8: Mon Apr  5 21:10:07 
> CEST 2010 r...@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET  amd64
> r...@kg-quiet# sysctl hw.machine
> hw.machine: amd64
> r...@kg-quiet# sysctl dev.amdtemp
> dev.amdtemp.0.%desc: AMD K8 Thermal Sensors
> dev.amdtemp.0.%driver: amdtemp
> dev.amdtemp.0.%parent: hostb4
> dev.amdtemp.0.sensor0.core0: 45.0C
> dev.amdtemp.0.sensor0.core1: 46.0C
> dev.amdtemp.0.sensor1.core0: 46.0C
> dev.amdtemp.0.sensor1.core1: 46.0C

I forgot a part:
r...@kg-quiet# sysctl hw.model
hw.model: AMD Athlon(tm) 64 Processor 3000+
-- 
Torfinn

___
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"

Re: ROOT MOUNT ERROR when booting from zfs

[Torfinn Ingolfsen]

On Thu, 19 Aug 2010 14:33:11 +0200
Heinrich Rebehn  wrote:

> Hi all,
> 
> i am getting the error message in $subject when trying to boot from zfs.
> I followed the instructions found in:
> 
> http://wiki.freebsd.org/RootOnZFS/GPTZFSBoot/Mirror
> 
> Before posting all config details and asking what i might have done wrong: Is 
> there any possibility to get a more detailed error message than just ROOT 
> MOUNT ERROR? e.g. zpool not found | zpool could not be imported | illegal 
> mount options | etc

You have tried verbose boot?
If not, try it and see if you get more information.
-- 
Regards,
Torfinn Ingolfsen


___
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"

Re: wifi issues under -stable

[Torfinn Ingolfsen]

On Wed, 22 Sep 2010 16:46:43 -0500
Jim Bryant  wrote:

> One (this one) has an intel pro wireless 3945ABG installed, which returns:
> 
> wpi0:  irq 18 at device 0.0 on pci6
> wpi0: Driver Revision 20071127
> wpi0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0x).
> wpi0: could not allocate memory resource
> device_attach: wpi0 attach returned 6
> 
> and the broadcom used in the other does the exact same thing.
> 
> I'm thinking that this isn't really a problem with the wifi, but may be 
> a mini-pci-e issue.

More likelely, it is ACPI-related.  Simply put: many laptops have
broken ACPI implementations. Other OS'es might have a workaround for
them, but FreeBSD does not.

Since almost none of todays' laptops work correctly with ACPI
disabled, this is a major pain. (Some laptops overheat when ACPI is
disbled, because of disabled thermal management).

You can try to figure out if the problem is acpi-related with the
following hint in /boot/loader.conf (but beware of thermal problems;
don't run the laptop too long with acpi disabled):
hint.acpi.0.disabled="1"

> does anyone know how to solve this problem?

Well, if you can identify exactly where the problem is, you might be
able to work around it. However, the task isn't easy. Sometimes,
forcing IRQ routing might help (but at least in 7.x this only works
with acpi disabled).

Using other OS'es (Linux) to identify if they do something different
with the resources (irq, memeory etc. for devices) migh help pointing
out wherer the problem might be. However, you will be speninding some
time comparing outputs from a FreeBSD verbose boot with the same
information from Linux.

(This thread reminds me that I should test FreeBSD 8.1 on my old
Acer laptop, which have acpi problems, and haven't worked with 6.0 -
8.0.)
-- 
Torfinn

___
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"

Re: How dhcp client can set its hostname properly on lease time

[Torfinn Ingolfsen]

On Thu, 07 Oct 2010 21:37:52 +0900
Mamoru Iwaki <1wk...@gmail.com> wrote:

> Are there good way for dhcp client to set its hostname properly on lease
> time?

Well, you *can* have the dhcp client on FreeBSD send an identifier, and
with that identifier the dhcp server can assign the client a static ip
lease. If that static ip is registered in your local dns, you're all
set. Doesn't work well if you use the client on another network who
doesn't offer static ip's. YMMV.

> The following will be a possble workaround, but I'm wondering there can
> be a smart answer in FreeBSD itself.
> 
> It is possible to resolve the hostname corresponding to a dhcp-delivered
> ip-address with a local name server. So, (1) resolve the corresponding
> hostname from the local name server, (2) set it as hostname, and (3)
> call them every time when dhcp lease is updated

Isn't the proper way with dns to configure dynamic DNS updates, and
allow the client to do that?

HTH
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: ISDN4BSD removal (was: FreeBSD 6.4 and 8.0 EoLs coming soon)

[Torfinn Ingolfsen]

This is straying a bit, but I think it is important:
the only good measure of when a technology is too old, is when people
(who use FreeBSD in this case) stop using it.

On Fri, 08 Oct 2010 11:12:32 +0200
Oliver Brandmueller  wrote:

> Maybe you don't really want to hear this, but...
> 
> ISDN is a dying technology. Any time soon you won't get ISDN termination 
> by your telecom provider anymore. If at all, theyll deliver S0 in your 
> home while doing VoIP from that little box on your wall.

I don't know how it works in other countries, but here (in Norway) it
works like this: yes - ISDN technology is dying. 
However, like all other technologies that major telcos have invested a
lot in, its death is very slow. Extremely slow in fact.

It could very well be that ISDN will live five or ten years still here,
simply because it doesn't cost too much to maintain, and there is no
new technology to push the dying ISDN over the edge off the cliff.
Why is this? Well, telcos here are investing in mobile
technologies for phones. They are _not_ interested in (and do not
invest significant money in) things like VoIP. In fact, major telcos
here doesn't invest significant money in fibre cables. They only put as
much money into it as they need to keep the competition at bay.

So who is investing in VoIP and fibre cables here? Answer: the ISP's
that doesn't have any large investments in traditional telco cables.

Another thing about VoIP calls: have they solved the "emergency call
needs a location" problem? Here (again: in Norway) they are still
working out how to solve this: if you call emergency services (police,
fire department, etc.) from yout VoIP number; how do the emergency
center locate you? I mean; how do they know that you are at home,
and not at say, a cabin half across the country? With old landlines,
there is no problem; it is always installed at an address.

Just my point of view.
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: ISDN4BSD removal

[Torfinn Ingolfsen]

On Fri, 08 Oct 2010 18:22:40 +0200
Dimitry Andric  wrote:

> On 2010-10-08 18:12, Torfinn Ingolfsen wrote:
> > Another thing about VoIP calls: have they solved the "emergency call
> > needs a location" problem? Here (again: in Norway) they are still
> > working out how to solve this: if you call emergency services (police,
> > fire department, etc.) from yout VoIP number; how do the emergency
> > center locate you?
> 
> Ehm, you tell them?  You have them on the phone. :)

If you are in a state to tell them, yes of course you do. However, the
situtation might mean that you aren't very coherent at all.
-- 
Torfinn

___
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"

Re: VirtualBox OpenSolaris guest

[Torfinn Ingolfsen]

On Sun, 10 Oct 2010 16:41:39 +0200
Emil Smolenski  wrote:

> opera-10.61.6430
> opera-linuxplugins-10.61.6430
> linux-f10-flashplugin-10.1r85

Aha, I was missing opera-linuxplugins. Installed now, seems to be working fine.
Very useful. Thanks!

Have a nice sunday, everyone!
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: Problem with security log

[Torfinn Ingolfsen]

On Wed, 13 Oct 2010 01:17:58 -0700
Jeremy Chadwick  wrote:

> There isn't a 100% reliable way to get rid of this problem.  I've been
> harping about this for years (sorry to sound like a jerk, but this
> really is a major problem that keeps coming up and annoys users/admins
> to no end.

Or the problem might not be so major, it only shows up on the mailing
lists about every six months. So maybe those who have the problem learns
how to live with it.
If it was a major problem, the mailing lists would be flooded.

Just my 0.02 eurocents.
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: Problem with security log

[Torfinn Ingolfsen]

On Thu, 14 Oct 2010 05:07:48 -0700
Jeremy Chadwick  wrote:

> But I classify this problem as high/severe because it makes a mess of
> things at the worst time possible -- situations where you absolutely
> need reliable output due to the nature of the problem you're dealing
> with (debugging a kernel, figuring out how/why something broke in the
> kernel, devices complaining about issues, disks reporting problems,
> etc.).

And that I can agree on; the problem is severe, and should be fixed. 
Hopefully that will happen someday.
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: Reproducible Kernel Panic on 8.1-STABLE [SEC=UNCLASSIFIED]

[Torfinn Ingolfsen]

On Fri, 15 Oct 2010 16:27:51 +0200
Ivan Voras  wrote:

> How stable is fuse & sshfs lately? It looks like every time in the past 
> I tried it I soon ended up panicking the system.

Well, I use sshfs routinely to copy data between my machines, and have
done so for about a year.
Mostly small files (like; oh I must get the documentation files /
whatever for this from my main workstation), but I have also used it
for backup of several terabytes of data. I connect and disconnect with
sshfs all the time.

Most machines run FreeBSD 7 / 8, mostly amd64
and a couple run Linux (Ubuntu). So far, very stable, and almost no
problems. I think the bug mentioned in this thread hit me, but just
once so far.

-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: how to access the SOL (Serial over Lan) port in FreeBSD ?

[Torfinn Ingolfsen]

On Tue, 14 Dec 2010 20:35:50 +0100
Luigi Rizzo  wrote:

> i recently bought two motherboards with Intel AMT support,
> a remote management tool which among other things implements
> Serial Over Lan (SOL) -- which seems to be accessible
> via TCP port 16994
> 
> I have enabled the feature in the bios and built a client

And configured it?
See http://linux.die.net/man/7/amt-howto

I know nothing about AMT (yet), but it looks interesting.
HTH
-- 
Torfinn

___
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"

The FreeBSD 7.4-BETA1 CD wont boot properly on this machine

[Torfinn Ingolfsen]

Hi,
I am trying to install FreeBSD 7.4-BETA1 / amd64 on this[1] machine.
The machine doesn't have a CD drive built-in, so I am using a Plextor
PX-608CU external DVD writer which connects via usb as the CD drive to
install from. I use the FreeBSD-7.4-BETA1-amd64-disc1.iso, which is burned
to a CD.
After powering on the machine, I press F8, get a nice little bootmenu,
select the Plextor drive, and off we go. The kernel boots, and
everything is great.
But, after detecting the hard drive (ad4, ok it's really a SSD) and the
cd drive, it just spits out messages like these:
run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 120 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 180 seconds for xpt_config
run_interrupt_driven_hooks: still waiting after 240 seconds for xpt_config

and after spitting out one more message  (the one for 300 seconds), it just
sits there. Booting with verbose doesn't give men any more messages related 
to this. I've tried the -bootonly CD too - it has the same problem.
Yes, the sha256 checksums on the files verifies a-ok, the CD's can be mounted
 in FreeBSD, etc.
I even mad a usb memory stick image of the -disc1 and booted the machine from 
that,
and it has the same problem (the run_interrupt... messages).

Kicker: the machine boots nicely from a FreeBSD 8.1-release (amd64) CD.
Also tried with a OpenBSD 4.8 (amd64) install CD, yep - it also boots nicely.

So, any hints on how to get FreeBSD 7.4-BETA1 onto this machine?

References:
1) http://sites.google.com/site/tingox/asus_v7-p7h55e
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: The FreeBSD 7.4-BETA1 CD wont boot properly on this machine

[Torfinn Ingolfsen]

On Sun, 19 Dec 2010 21:30:59 +
Chris Rees  wrote:

> 
> Did you try installing using a different computer onto that hard drive?

Nope, not yet. Looking for easier alternatives first.

> Is the hardware supported by 7.x
> (http://www.freebsd.org/releases/7.3R/hardware.html for pointers)

Well, AFAICT, it should work. Nothing odd or non-standard. Again, AFAICT.

> Is there a reason you want 7.4 rather than 8.1?

The machine already runs 8.1 (see [1]). Sorry for not making that clear.
(in my defence, the information is available on the page I referenced in my 
post, 
but obviously nobody bothered to check that. Oh well.)
Now I want to install 7.4 on another partition, so I can test
that release as well.

I always try to install as many different releases on a machine as I can / have 
space for;
it has proven useful in the past, and it is my small way to help FreeBSD 
developers
by testing as much (many releases / branches) as I can, on as much hardware as 
I can.

References:
1) http://sites.google.com/site/tingox/asus_v7-p7h55e_freebsd
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: The FreeBSD 7.4-BETA1 CD wont boot properly on this machine

[Torfinn Ingolfsen]

On Sun, 19 Dec 2010 16:30:08 -0800
Jeremy Chadwick  wrote:

> 
> This has, historically, been caused by problems with certain firewire
> chipsets.  The workaround has been to disable firewire in the BIOS.

Aha! That's a great clue. I haven't seen that particular problem before.

> I've experienced this on a Shuttle system, and others have on different
> motherboards as well:
> 
> http://old.nabble.com/run_interrupt_driven_hooks:-still-waiting-after-300-seconds-for-xpt_config-td23492390.html
> http://old.nabble.com/-Fwd%3A-run_interrupt_driven_hooks%3A-still-waiting...-for-xpt_config--td23641548.html
> http://lists.freebsd.org/pipermail/freebsd-current/2009-July/009079.html
> 
> However, that motherboard doesn't seem to support firewire (but Asus has
> been known to forget mentioning features on their site before).

It has firewire. From /var/log/messages under FreeBSD 8.1-stable:
fwohci0: <1394 Open Host Controller Interface> mem 
0xfbdff800-0xfbdf,0xfbdff400-0xfbdff47f,0xfbdff000-0xfbdff07f,0xfbdfec00-0xfbdfec7f
 irq 19 at device 0.0 on pci1
fwohci0: [ITHREAD]
fwohci0: OHCI version 1.10 (ROM=0)
fwohci0: No. of Isochronous channels is 4.
fwohci0: EUI64 00:1e:8c:00:00:2c:b8:9a
fwohci0: Phy 1394a available S400, 2 ports.

So a quick tour into the bios to disable the firewire, then back to boot from 
the 7.4-BETA1 cd.
Yes, it works now, and while I have been wrinting this message, it has just 
finished installing.

Great advice. Thanks!

> Otherwise, run 8.x.

I do already, see my other posting in this thread.
-- 
Regards, 
Torfinn Ingolfsen

___
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"

Re: The FreeBSD 7.4-BETA1 CD wont boot properly on this machine

[Torfinn Ingolfsen]

On Mon, 20 Dec 2010 20:18:06 +0100
Torfinn Ingolfsen  wrote:

> So a quick tour into the bios to disable the firewire, then back to boot from 
> the 7.4-BETA1 cd.
> Yes, it works now, and while I have been wrinting this message, it has just 
> finished installing.

For completeness, I tried enabling the firewire in the bios after I had
installed FreeBSD7.4-BETA1. But it didn't work (I didn't think it
would), the machine just printed the same error messages as the install
CD did.
Anyway, dmesg output and other info is available here:
http://sites.google.com/site/tingox/asus_v7-p7h55e_freebsd
-- 
Regards,
Torfinn Ingolfsen

___
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"

trying to mount a write prptected zip disk panics the machine (unless the -r flag is used)

[Torfinn Ingolfsen]

Hello,

Do you remember the zip[1] disks? The original 100 Mbyte ones? well
recently, I got a scsi zip drive (internal) with a scsi card (Adaptec
ava-2904) and some zip-100 disks, and a request to try to copy the data
from those disks. I found a cable, installed the card and zip drive
in a machine[2] running FreeBSd 7.0-stable, and luckily the zip disks could
be read.

But during this process I discovered one thing; if I try to mount a
write protected zip disk without using the '-r' flag to the mount
command, my machine will panic a few seconds later. As there is no visual
indication to tell you that a zip disk is  write protected, it is quite easy to 
forget
mounting it read only.

Note: using zip disks that aren't write protected works fine.

Details:
[EMAIL PROTECTED] uname -a
FreeBSD music1.kg4.no 7.0-STABLE FreeBSD 7.0-STABLE #0: Fri Aug 15
12:56:35 CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
i386

[EMAIL PROTECTED] dmesg | grep ahc
ahc0:  port 0x1400-0x14ff mem 
0x5c10-0x5c100fff irq 10 at device 15.0 on pci0
ahc0: Host Adapter Bios disabled.  Using default SCSI device parameters
ahc0: [ITHREAD]
da0 at ahc0 bus 0 target 5 lun 0
[EMAIL PROTECTED] dmesg | grep aic
aic7850: Single Channel A, SCSI Id=7, 3/253 SCBs

[EMAIL PROTECTED] dmesg | grep da0
da0 at ahc0 bus 0 target 5 lun 0
da0:  Removable Direct Access SCSI-2 device 
da0: 3.300MB/s transfers
da0: 96MB (196608 512 byte sectors: 64H 32S/T 96C)

This is what I got on the console (and in /var/log/messages) when I tried to 
mount the disk:
Aug 15 20:14:33 music1 kernel: (da0:ahc0:0:5:0): WRITE(06). CDB: a 0 0 21 8 0 
Aug 15 20:14:33 music1 kernel: (da0:ahc0:0:5:0): CAM Status: SCSI Status Error
Aug 15 20:14:33 music1 kernel: (da0:ahc0:0:5:0): SCSI Status: Check Condition
Aug 15 20:14:33 music1 kernel: (da0:ahc0:0:5:0): DATA PROTECT asc:27,0
Aug 15 20:14:33 music1 kernel: (da0:ahc0:0:5:0): Write protected
Aug 15 20:14:33 music1 kernel: (da0:ahc0:0:5:0): Unretryable error
Aug 15 20:14:33 music1 kernel: g_vfs_done():da0s4[WRITE(offset=512, 
length=4096)]error = 13
Aug 15 20:14:33 music1 kernel: (da0:ahc0:0:5:0): WRITE(06). CDB: a 0 0 21 8 0 
Aug 15 20:14:33 music1 kernel: (da0:ahc0:0:5:0): CAM Status: SCSI Status Error
Aug 15 20:14:33 music1 kernel: (da0:ahc0:0:5:0): SCSI Status: Check Condition
Aug 15 20:14:33 music1 kernel: (da0:ahc0:0:5:0): DATA PROTECT asc:27,0
Aug 15 20:14:33 music1 kernel: (da0:ahc0:0:5:0): Write protected
Aug 15 20:14:33 music1 kernel: (da0:ahc0:0:5:0): Unretryable error
Aug 15 20:14:33 music1 kernel: g_vfs_done():da0s4[WRITE(offset=512, 
length=4096)]error = 13
Aug 15 20:14:33 music1 kernel: fsync: giving up on dirty
Aug 15 20:14:33 music1 kernel: 0xc2988114: tag devfs, type VCHR
Aug 15 20:14:33 music1 kernel: usecount 1, writecount 0, refcount 27 
mountedhere 0xc2617700
Aug 15 20:14:33 music1 kernel: flags ()
Aug 15 20:14:33 music1 kernel: v_object 0xc299707c ref 0 pages 25
Aug 15 20:14:33 music1 kernel: 
Aug 15 20:14:33 music1 kernel: dev da0s4
Aug 15 20:14:34 music1 kernel: GEOM_LABEL: Label for provider da0s4 is 
msdosfs/DIPLOM.

A few seconds went by, and then the machine panic'ed with apage fault:
[EMAIL PROTECTED] more /var/crash/info.0
Dump header from device /dev/ad0s1b
  Architecture: i386
  Architecture Version: 2
  Dump Length: 60837888B (58 MB)
  Blocksize: 512
  Dumptime: Fri Aug 15 20:15:03 2008
  Hostname: music1.kg4.no
  Magic: FreeBSD Kernel Dump
  Version String: FreeBSD 7.0-STABLE #0: Fri Aug 15 12:56:35 CEST 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC
  Panic String: page fault
  Dump Parity: 2682527093
  Bounds: 0
  Dump Status: good

(crash dump, 58 Mbyte, available on request).

Is this how it is supposed to be, or should I file a PR?

References:
1) http://en.wikipedia.org/wiki/Zip_drive
2) http://tingox.googlepages.com/dp-ep-c400_freebsd
-- 
Regards,
Torfinn Ingolfsen,
Norway

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: trying to mount a write prptected zip disk panics the machine (unless the -r flag is used)

[Torfinn Ingolfsen]

On Mon, 18 Aug 2008 10:33:05 -0400
John Baldwin <[EMAIL PROTECTED]> wrote:

> 
> Can you get the stack trace?

Like this?
[EMAIL PROTECTED] kgdb kernel.debug /var/crash/vmcore.0
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and
you are welcome to change it and/or distribute copies of it under
certain conditions. Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for
details. This GDB was configured as "i386-marcel-freebsd"...

Unread portion of the kernel message buffer:


Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address   = 0x0
fault code  = supervisor read, page not present
instruction pointer = 0x20:0xc0737b19
stack pointer   = 0x28:0xceb9cbcc
frame pointer   = 0x28:0xceb9cbf8
code segment= base 0x0, limit 0xf, type 0x1b
= DPL 0, pres 1, def32 1, gran 1
processor eflags= interrupt enabled, resume, IOPL = 0
current process = 42 (syncer)
trap number = 12
panic: page fault
cpuid = 0
Uptime: 24m34s
Physical memory: 307 MB
Dumping 58 MB: 43 27 11

Reading symbols from /boot/kernel/acpi.ko...Reading symbols
from /boot/kernel/acpi.ko.symbols...done. done.
Loaded symbols for /boot/kernel/acpi.ko
#0  doadump () at pcpu.h:195
195 __asm __volatile("movl %%fs:0,%0" : "=r" (td));
(kgdb) 
(kgdb) backtrace
#0  doadump () at pcpu.h:195
#1  0xc078eed7 in boot (howto=260)
#at /usr/src/sys/kern/kern_shutdown.c:418 2  0xc078f199 in panic
#(fmt=Variable "fmt" is not available.
) at /usr/src/sys/kern/kern_shutdown.c:572
#3  0xc0a9efbc in trap_fatal (frame=0xceb9cb8c, eva=0)
#at /usr/src/sys/i386/i386/trap.c:899 4  0xc0a9f240 in trap_pfault
#(frame=0xceb9cb8c, usermode=0, eva=0)
#at /usr/src/sys/i386/i386/trap.c:812 5  0xc0a9fbec in trap
#(frame=0xceb9cb8c) at /usr/src/sys/i386/i386/trap.c:490 6  0xc0a859ab
#in calltrap () at /usr/src/sys/i386/i386/exception.s:139 7  0xc0737b19
#in g_io_request (bp=0xc299ba50, cp=0xc29b2e00)
#at /usr/src/sys/geom/geom_io.c:364 8  0xc073c116 in g_vfs_strategy
#(bo=0xc29881d4, bp=0xc88efc24) at /usr/src/sys/geom/geom_vfs.c:107 9
#0xc07f97b0 in bufwrite (bp=0xc88efc24) at buf.h:429 10 0xc07f2618 in
#bawrite (bp=0xc88efc24) at buf.h:417 11 0xc07fddaa in vop_stdfsync
#(ap=0xceb9ccd4) at /usr/src/sys/kern/vfs_default.c:479 12 0xc071cbbe
#in devfs_fsync (ap=0xceb9ccd4)
#at /usr/src/sys/fs/devfs/devfs_vnops.c:395 13 0xc0ab3ce2 in
#VOP_FSYNC_APV (vop=0xc0bcf040, a=0xceb9ccd4) at vnode_if.c:1007 14
#0xc080dff8 in sched_sync () at vnode_if.h:538 15 0xc076bc59 in
#fork_exit (callout=0xc080d8f0 , arg=0x0, frame=0xceb9cd38)
at /usr/src/sys/kern/kern_fork.c:781
#16 0xc0a85a20 in fork_trampoline ()
#at /usr/src/sys/i386/i386/exception.s:205

Let me know if it was wrong, or if you need something else.
-- 
Regards, 
Torfinn Ingolfsen

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: trying to mount a write prptected zip disk panics the machine (unless the -r flag is used)

[Torfinn Ingolfsen]

On Tue, 19 Aug 2008 17:15:54 -0400
John Baldwin <[EMAIL PROTECTED]> wrote:

> That's right, but not the specific bug I am familiar with. :(

Ok.
The issue is now documented as PR i386/127029
http://www.freebsd.org/cgi/query-pr.cgi?pr=127029

No, I am not sure that this issue only relates to i386. But I haven't
tested the zip drive elsewhere.
-- 
Regards,
Torfinn Ingolfsen,
Norway

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD 7.1 Content

[Torfinn Ingolfsen]

On Wed, 03 Sep 2008 15:01:48 -0600
Dan Allen <[EMAIL PROTECTED]> wrote:

> The Ubuntu install is very compelling.  I am just wishing that
> FreeBSD was AS compelling in its first install experience.  At
> present it is far, far behind.

Well, do you really want all those people who can't even read to be
FreeBSD users? (Not aiming at Ubuntu users here)

Personally, I think that the FreeBSD learning curve is a good thing, it
means that  FreeBSD users wil know more about FreeBSD when they get it
running.
-- 
Regards,
Torfinn Ingolfsen

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: floppy disk controller broken

[Torfinn Ingolfsen]

On Thu, 18 Sep 2008 23:33:40 +0100
"Bruce M. Simpson" <[EMAIL PROTECTED]> wrote:

> Someone was going to pick this up, finish it off, and commit it, but
> I haven't heard back from them: 
> http://people.freebsd.org/~bms/dump/tools/ufdformat/

It compiled fine on FreeBSD 7.0-stable:
[EMAIL PROTECTED] uname -a
FreeBSD kg-work2.kg4.no 7.0-STABLE FreeBSD 7.0-STABLE #0: Mon Jul 21
20:40:31 CEST 2008
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386

But when I tried to use, it printed two 'V''s and then seemed to be
doing nothing.

In /var/log/messages I got these:
Sep 21 12:09:35 kg-work2 kernel: umass0: CBI reset failed, TIMEOUT
Sep 21 12:09:40 kg-work2 kernel: umass0: CBI bulk-in stall clear failed, TIMEOUT
Sep 21 12:09:45 kg-work2 kernel: umass0: CBI bulk-out stall clear failed, 
TIMEOUT
Sep 21 12:11:55 kg-work2 kernel: umass0: CBI reset failed, TIMEOUT
Sep 21 12:13:00 kg-work2 kernel: umass0: CBI bulk-in stall clear failed, TIMEOUT
Sep 21 12:14:05 kg-work2 kernel: umass0: CBI bulk-out stall clear failed, 
TIMEOUT
Sep 21 12:16:15 kg-work2 kernel: umass0: CBI reset failed, TIMEOUT

The funny thing is - that situation seemed to vlock commands from executing,
or the terminals from printing outrput.
I had several terminal windows up, and a ssh session from another machine. 
I could type a command, but nothing would happen after I pressed enter.
Switching workspaces in X and switching vty's  worked fine.
In the end, I had to yank the floppy (which panicked the machine as expected).
The floppy I used was this one:
Sep 21 11:45:58 kg-work2 root: Unknown USB device: vendor 0x0644 product 0x 
bus uhub1
Sep 21 11:45:59 kg-work2 kernel: umass0:  on uhub1
Sep 21 11:45:59 kg-work2 kernel: da0 at umass-sim0 bus 0 target 0 lun 0
Sep 21 11:45:59 kg-work2 kernel: da0:  Removable Direct 
Access SCSI-0 device 
Sep 21 11:45:59 kg-work2 kernel: da0: 1.000MB/s transfers

I will try ufdformat on a different machine now.
-- 
Regards,
Torfinn Ingolfsen
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: floppy disk controller broken

[Torfinn Ingolfsen]

On Sun, 21 Sep 2008 12:44:03 +0200
Torfinn Ingolfsen <[EMAIL PROTECTED]> wrote:

> I will try ufdformat on a different machine now.

Ok, on a different machine[1], it works without problems:
[EMAIL PROTECTED] uname -a
FreeBSD kg-i82.kg4.no 7.0-STABLE FreeBSD 7.0-STABLE #3: Wed May 28 15:59:38 
CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/I81K  i386
[EMAIL PROTECTED] ./ufdformat da0
Geometry: 80 cyl 2 heads 18 secpercyl 512 bytespersec
current: 2880 blocks, 512 bytes-per-block formatted
0: 2880 blocks, 512 bytes-per-block 
1: 1232 blocks, 1024 bytes-per-block 
2: 2400 blocks, 512 bytes-per-block 
Format 1440K floppy `da0'? (y/n): y
Processing  done.

Why it didn't work on the first machine[2] I don't know.

References:
1) http://tingox.googlepages.com/i81k
2) http://tingox.googlepages.com/sx270
-- 
Regards, 
Torfinn Ingolfsen
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: floppy disk controller broken

[Torfinn Ingolfsen]

On Sun, 21 Sep 2008 06:45:29 -0700
Jeremy Chadwick <[EMAIL PROTECTED]> wrote:

> Remove "device udbp" from your kernel configuration and try again.
> The problem with bulk pipes is somewhat well-known at this point.

This machine have a GENERIC kernel:
[EMAIL PROTECTED] uname -a
FreeBSD kg-work2.kg4.no 7.0-STABLE FreeBSD 7.0-STABLE #0: Mon Jul 21 20:40:31 
CEST 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC  i386

And it seems like udbp is commented out in GENERIC:
[EMAIL PROTECTED] grep udbp /sys/i386/conf/GENERIC
#device udbp# USB Double Bulk Pipe devices

So it might be something else. usb controller / chipset, or whatever.
BTW, for completeness, this machine is a Dell OptiPlex SX270[1].

References:
1) http://tingox.googlepages.com/sx270
-- 
Regards,
Torfinn Ingolfsen
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

FreeBSD 6.5-prerelease and if_re - patches needed?

[Torfinn Ingolfsen]

Hi,

The last part of last year and earlier this year a patch for if_re was
needed to get it working reliably on my machine[1] (and some others).
Now I have upgraded this machine to FreeBSD 6.4-prerelease, more info
here [2].
Are the if_re patches included in FreeBSD 6.4-prerelease now, or are
they still needed?

I ask because while if_re works most of the time in 6.4-prerelease, I
still have symptoms like last time (ssh often disconnects with "Bad
packet length" and so on).

References:
1) http://tingox.googlepages.com/asus_m2a-vm_hdmi
2) http://tingox.googlepages.com/asus_m2a-vm_hdmi_freebsd
-- 
Regards,
Torfinn Ingolfsen

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD 6.5-prerelease and if_re - patches needed?

[Torfinn Ingolfsen]

On Mon, 22 Sep 2008 11:10:23 +0900
Pyun YongHyeon <[EMAIL PROTECTED]> wrote:

> Due to lack of time and energy the change made in HEAD wasn't MFCed
> to RELENG_6 so you may still need some patch. stable/7 should have
> no such problems though.

Does anybody happen to know which patch?

> Maybe the issue you're seeing comes from misuse of bus_dma(9) which
> was corrected in stable/7.

But not MFC'ed to RELENG_6 I guess?
Is therer a patch for RELENG_6 somewhere?
-- 
Regards,
Torfinn Ingolfsen

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: After an update stable doesn't boot

[Torfinn Ingolfsen]

On Thu, 23 Oct 2008 21:40:23 +0100 (BST)
Reinhold <[EMAIL PROTECTED]> wrote:

> A little update.
> 
> I can boot into freebsd using the life cd and can mount the disk when
> I'm in fixit.
> 
> But from there on I have no idea what to do to fix this problem.

Some quick checks:
- use fdisk (for example: fdisk ad0) to check if the correct slice is
active
- use boot0cfg -v to check the bootcode of the disk you are booting from

HTH
-- 
Regards,
Torfinn Ingolfsen

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: easy way to upgrade from 6.3 to 7.1 (including port packages)

[Torfinn Ingolfsen]

On Mon, 27 Oct 2008 19:26:03 +0100
martinko <[EMAIL PROTECTED]> wrote:

> I'd like a more general purpose utility, be it mergemaster or sth
> else. I like the way mergemaster works but I'd like to use it not
> only for /etc (after make) -- I'd like to point it to my backup
> directory which doesn't contain all of /etc and compare the files it
> finds with those in /etc.  Or point it to arbitrary 2 directories and
> compare their files.

This is getting a bit OT, but kind of like dirdiff[1]?

References:
1) http://www.freshports.org/sysutils/dirdiff/
-- 
Regards,
Torfinn Ingolfsen

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD 6.5-prerelease and if_re - patches needed?

[Torfinn Ingolfsen]

On Fri, 03 Oct 2008 17:34:43 +0900
Pyun YongHyeon <[EMAIL PROTECTED]> wrote:

> Maybe you can use if_re.c/if_rlreg.h in RELENG_7 with minor
> modification.

I have tried that now. Unfortunately, the differences were too many -
I never managed to get it to compile.

Has anyone else created pathes for if_re for RELENG_6?
-- 
Regards,
Torfinn Ingolfsen

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD 6.5-prerelease and if_re - patches needed?

[Torfinn Ingolfsen]

On Sun, 02 Nov 2008 14:09:15 +0900
Pyun YongHyeon <[EMAIL PROTECTED]> wrote:

> http://people.freebsd.org/~yongari/re/6.x/README
> 
> Hope this helps.

Yes it does, thanks!

On boot, trherer is a noticable delay (tens of seconds) after printing
these lines:
re0:  
port 0xee00-0xeeff mem 0xfdfff000-0xfdff irq 19 at device 0.0 on pci2
re0: turning off MSI enable bit.
re0: Chip rev. 0x3800
re0: MAC rev. 0x

The original didn't have that delay.
Otrher than that it works much better. Details:
[EMAIL PROTECTED] uname -a
FreeBSD kg-vm.kg4.no 6.4-PRERELEASE FreeBSD 6.4-PRERELEASE #3: Sun Nov  2 
10:44:32 CET 2008 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/SMP  amd64
[EMAIL PROTECTED] pciconf -lv | grep re0 -A 4
[EMAIL PROTECTED]:0:0:  class=0x02 card=0x81aa1043 chip=0x816810ec rev=0x01 
hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC'
class  = network
subclass   = ethernet

Note: I haven't testet if_rl, so I don't know how this patch affects that.
I'll get back with a note on stability sometime next week (after I have done 
losts of data transfers to and from this box).
-- 
Regards,
Torfinn Ingolfsen

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: FreeBSD 6.5-prerelease and if_re - patches needed?

[Torfinn Ingolfsen]

On Mon, 03 Nov 2008 09:47:14 +0900
Pyun YongHyeon <[EMAIL PROTECTED]> wrote:

> I've changed to have re(4) wait the completion of DMAable memory
> allocation during bus_dma cleanups. The delay you've seen may be
> related with that change. Previously it just failed to load the
> driver if there is no available memory at the time of driver
> loading. However I guess that delay wouldn't happen if the driver
> is statically linked into kernel.
> Did you use kernel module?

No, the driver is compiled into the kernel:
[EMAIL PROTECTED] ifconfig re0
re0: flags=8843 mtu 1500
options=1b
inet 10.1.150.15 netmask 0x broadcast 10.1.255.255
ether 00:1d:60:2c:80:f0
media: Ethernet autoselect (100baseTX )
status: active
[EMAIL PROTECTED] kldstat
Id Refs AddressSize Name
 13 0x8010 aa37d8   kernel
 21 0x80ba4000 1a850snd_hda.ko
 32 0x80bbf000 35c80sound.ko
[EMAIL PROTECTED] 

HTH
-- 
Regards,
Torfinn Ingolfsen

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Re: installworld chflags failures

[Torfinn Ingolfsen]

On Mon, 03 Nov 2008 16:18:47 +0900
Randy Bush <[EMAIL PROTECTED]> wrote:

> :/> cd /usr/src
> :/usr/src> bash

Hmm, what happens if you do _not_ use bash here?
bash is non-standard for a FreeBSD install (the procedure), so it might
bite you.
Or it might not.

HTH
-- 
Regards,
Torfinn Ingolfsen

___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

FreeBSD 6.4-stable: kernel panics related to usb and filesystem interaction?

[Torfinn Ingolfsen]

Hi,
One[1] of my machines have recently had a couple of panics wile running
FreeBSD 6.4-stable / amd64:
r...@kg-quiet# uname -a
FreeBSD kg-quiet.kg4.no 6.4-STABLE FreeBSD 6.4-STABLE #25: Fri Dec  5 23:26:19 
CET 2008 r...@kg-quiet.kg4.no:/usr/obj/usr/src/sys/QUIET  amd64

The machine works as a cheap fileserver (running Samba) and has a number of 
external disks attached (one firewire, several usb).
A work log for FreeBSD on this machine is here[2].

So I used kgdb to make a couple of backtraces of the dumps, in case it is 
useful.
The first panic mentions smbd, dump info and backtrace kan be found here[3].
The next panic mentions ohci0 and ohci+ as the process, , dump info and 
backtrace kan be found here[4].

Thus my suspicion that this could be an interaction between usb and filesystem. 
OTOH, I can easily be totally wrong here.

Feedback and / or requests to perform more debugging tasks are welcome.

References:
1) http://tingox.googlepages.com/rs480m2
2) http://tingox.googlepages.com/rs480m2_freebsd
3) http://tingox.googlepages.com/quiet-6.4-stable-kdump-20081223.txt
4) http://tingox.googlepages.com/quiet-6.4-stable-kdump-20081231.txt
-- 
Regards,
Torfinn Ingolfsen,
Norway

___
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"

Re: Samsung SCX-4200 printer

[Torfinn Ingolfsen]

On Sun, 04 Jan 2009 23:14:22 +0100
Harald Weis  wrote:

> Is there a way to install the SCX-4200 printer on a FreeBSD box ?
> The printer is delivered with the install software required for Linux.
> And CUPS does not seem to "know" it.

As always, check OpenPrinting.org first:
http://openprinting.org/show_printer.cgi?recnum=Samsung-SCX-4200

HTH
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: Pending MFC of drm updates

[Torfinn Ingolfsen]

c:42:
@/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or
directory In file included
from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_pci.c:34:
@/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or
directory In file included
from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_scatter.c:40:
@/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or
directory In file included
from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_sysctl.c:32:
@/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or
directory In file included
from /usr/src/sys/modules/drm/drm/../../../dev/drm/drm_vm.c:31:
@/dev/drm/drmP.h:96:34: error: dev/drm/drm_internal.h: No such file or
directory mkdep: compile failed *** Error code 1

Stop in /usr/src/sys/modules/drm/drm.
*** Error code 1

Stop in /usr/src/sys/modules/drm.
*** Error code 1

Stop in /usr/src/sys/modules.
*** Error code 1

Stop in /usr/obj/usr/src/sys/GENERIC.
*** Error code 1

Stop in /usr/src.
*** Error code 1

Stop in /usr/src.

HTH
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: Pending MFC of drm updates

[Torfinn Ingolfsen]

On Wed, 07 Jan 2009 01:24:57 +0100
Torfinn Ingolfsen  wrote:

I forgot to tell that I fixed the Makefile in sys/modules/drm/i915
manually.

> Apparently patch gets confuseed when it finds a file with the same
> name in the current directory (which was /usr/src), or perhaps I
> don't know how to tell patch how to find the right file.
> I just did:
> cd /usr/src
> patch < /dir/name/patchfile
> 
> Anyway, a 'make kernel' fails:

Which is no wonder, because patch misplaced more files:
r...@kg-v2# pwd
/usr/src
r...@kg-v2# ll *.c *c.orig *.h *h.orig
-rw-r--r--  1 root  wheel   1650 Jan  7 01:09 drm_internal.h
-rw-r--r--  1 root  wheel  0 Jan  7 01:09 drm_internal.h.orig
-rw-r--r--  1 root  wheel  16455 Jan  7 01:09 i915_suspend.c
-rw-r--r--  1 root  wheel  0 Jan  7 01:09 i915_suspend.c.orig
-rw-r--r--  1 root  wheel  59118 Jan  7 01:09 radeon_microcode.h
-rw-r--r--  1 root  wheel  0 Jan  7 01:09 radeon_microcode.h.orig

Is ther a "secret handshake" to make patch put the files in their
correct place? (Except for reading through the whole patchfile to
determine if all touched filews are in the same directory.)

For now I just mv'ed the files into place.
Anyway, now the new kernel builds, installs and works correctly.
It didn't pick up any drm, but I'm not sure that it should either. This
machine[1] has a GeForce 8200 chipset. More info about FreeBSD on this
machine here[2], including dmesgs before and after, etc.

HTH

References:
1) http://tingox.googlepages.com/asus_v2-m3n8200
2) http://tingox.googlepages.com/asus_v2-m3n8200_freebsd
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: ACPI support?

[Torfinn Ingolfsen]

On Tue, 06 Jan 2009 13:12:05 +0200
Krassimir Slavchev  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> 
> Hello All,
> 
> I have had a problem detecting the network card on my notebook when
> ACPI is enabled for a year. The problem still exists in 7.1-RELEASE.

Which make and model notebook is this?

You have my sympaties, my own laptop[1] (Acer Aspire 5672) have the same
sort of problem - drivers for NICs (both wired and wireless) will not
attach if acpi is enabled. And this laptop gets too hot when acpi is
disabled - I fear it will overheat. Linux runs fine[2] on it.

I had a lot of help in trying to fix the problem a wbile back (check
the freebsd-mobile mailing list archives), but in the end, nothing
helped.

 I can only offer general advice, not a solution. Try too look for
a modfified DSDT for your notebook, perhpas you will find something
that helps.

References:
1) http://tingox.googlepages.com/aceraspireas5672andfreebsd
2) http://tingox.googlepages.com/as5672_xubuntu
-- 
Regards,
Torfinn Ingolfsen,
Norway

___
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"

Re: ACPI support?

[Torfinn Ingolfsen]

On Fri, 09 Jan 2009 10:01:33 +0200
Krassimir Slavchev  wrote:

> I have found that thread.

FWIW, I started a new thread[1] on freebsd-mobile, to update the status
now after FreeBSD 7.1 has been released

> The problem may be with allocating resources by ACPI PCI-PCI bridge.
> There is a way to set needed values:
> http://lists.freebsd.org/pipermail/freebsd-acpi/2008-May/004905.html

Interesting. For my laptop, it seems that these bridges have the
problem:
pcib2:  irq 17 at device 28.0 on pci0
pcib2:   domain0
pcib2:   secondary bus 2
pcib2:   subordinate bus   2
pcib2:   I/O decode0x0-0x0
pcib2:   no prefetched decode
pci2:  on pcib2
pci2: domain=0, physical bus=2
pcib3:  irq 16 at device 28.1 on pci0
pcib3:   domain0
pcib3:   secondary bus 3
pcib3:   subordinate bus   3
pcib3:   I/O decode0x0-0x0
pcib3:   no prefetched decode
pci3:  on pcib3
pci3: domain=0, physical bus=3

and also these:

pcib4:  irq 18 at device 28.2 on pci0
pcib4:   domain0
pcib4:   secondary bus 4
pcib4:   subordinate bus   4
pcib4:   I/O decode0x0-0x0
pcib4:   no prefetched decode
pci4:  on pcib4
pci4: domain=0, physical bus=4

pcib5:  irq 19 at device 28.3 on pci0
pcib5:   domain0
pcib5:   secondary bus 5
pcib5:   subordinate bus   7
pcib5:   I/O decode0x0-0x0
pcib5:   no prefetched decode
pcib5: could not get PCI interrupt routing table for \\_SB_.PCI0.RP04 - 
AE_NOT_FOUND
pci5:  on pcib5
pci5: domain=0, physical bus=5

bge0 (the wired interface is on pcib4:

bge0:  irq 18 
at device 0.0 on pci4
pcib4: bge0 requested unsupported memory range 0-0x (decoding 0-0, 0-0)
bge0: 0x1 bytes of rid 0x10 res 3 failed (0, 0x).
bge0: couldn't map memory
device_attach: bge0 attach returned 6

and wpi0 (the wireless) is on pcib3:

wpi0:  irq 17 at device 0.0 on pci3
wpi0: Driver Revision 20071127
pcib3: wpi0 requested unsupported memory range 0-0x (decoding 0-0, 0-0)
wpi0: 0x1000 bytes of rid 0x10 res 3 failed (0, 0x).
wpi0: could not allocate memory resource
device_attach: wpi0 attach returned 6

With acpi disabled, the bridges shoiw up like this:
pcib2:  irq 17 at device 28.0 on pci0
pcib2:   domain0
pcib2:   secondary bus 2
pcib2:   subordinate bus   2
pcib2:   I/O decode0xf000-0xfff
pcib2:   no prefetched decode
pci2:  on pcib2
pci2: domain=0, physical bus=2
pcib3:  irq 16 at device 28.1 on pci0
pcib3:   domain0
pcib3:   secondary bus 3
pcib3:   subordinate bus   3
pcib3:   I/O decode0xf000-0xfff
pcib3:   memory decode 0xc820-0xc82f
pcib3:   no prefetched decode
pci3:  on pcib3
pci3: domain=0, physical bus=3

pcib4:  irq 18 at device 28.2 on pci0
pcib4:   domain0
pcib4:   secondary bus 4
pcib4:   subordinate bus   4
pcib4:   I/O decode0xf000-0xfff
pcib4:   memory decode 0xc830-0xc83f
pcib4:   no prefetched decode
pci4:  on pcib4
pci4: domain=0, physical bus=4

pcib5:  irq 19 at device 28.3 on pci0
pcib5:   domain0
pcib5:   secondary bus 5
pcib5:   subordinate bus   5
pcib5:   I/O decode0xf000-0xfff
pcib5:   no prefetched decode
pci5:  on pcib5
pci5: domain=0, physical bus=5

bge with acpi disabled:

bge0:  mem 
0xc830-0xc830 irq 17 at device 0.0 on pci4
bge0: Reserved 0x1 bytes for rid 0x10 type 3 at 0xc830
bge0: attempting to allocate 1 MSI vectors (8 supported)
msi: routing MSI IRQ 256 to vector 48
bge0: using IRQ 256 for MSI
miibus0:  on bge0
brgphy0:  PHY 1 on miibus0
brgphy0: OUI 0x000818, model 0x0018, rev. 0
brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
1000baseT-FDX, auto
bge0: bpf attached
bge0: Ethernet address: 00:16:36:54:a9:ae
bge0: [MPSAFE]
bge0: [ITHREAD]

wpi with acpi disabled:
wpi0:  mem 0xc820-0xc8200fff irq 17 at 
device 0.0 on pci3
wpi0: Driver Revision 20071127
wpi0: Reserved 0x1000 bytes for rid 0x10 type 3 at 0xc820
wpi0: Hardware Revision (0x1)
wpi0: Regulatory Domain: MoW2
wpi0: Hardware Type: B
wpi0: Hardware Revision: ?
wpi0: SKU does support 802.11a
wpi0: bpf attached
wpi0: Ethernet address: 00:13:02:3e:d4:ce
wpi0: bpf attached
wpi0: bpf attached
ioapic0: Assigning PCI IRQ 17 to local APIC 0
ioapic0: routing intpin 17 (PCI IRQ 17) to vector 60
wpi0: [MPSAFE]
wpi0: [ITHREAD]
wpi0: 11a rates: 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
wpi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
wpi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 
36Mbps 48Mbps 54Mbps

Perhaps I should try to patch my pci too.

References:
1)
http://lists.freebsd.org/pipermail/freebsd-mobile/2009-January/011294.html
-- 
Torfinn

___
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"

Re: iwn driver on 7.1

[Torfinn Ingolfsen]

On Sun, 18 Jan 2009 14:17:39 -0600
Brandon Gooch  wrote:

> I have a working driver for the Intel 4965, aka iwn(4), loaded on my
> Lenovo X300 running FreeBSD 7.1-RELEASE (amd64).

FWIW, I am using the latest perforce version of the iwn driver as
documented here[1] on a ThinkPad T61 running FreeBSD 7.1-stable / i386 -
no modifications necessary. It works great.
I just use the p4fetch.rb script to get the driver.

HTH

References:
1) http://clearchain.com/wiki/iwn
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: Replace Cisco IOS/CBOS with freebsd - possible?

[Torfinn Ingolfsen]

On Thu, 29 Jan 2009 01:50:34 -0800
Chris H  wrote:

> a /27 segment for my home network. Which is currently running over
> a cisco 837 GW (adsl/router). I'm not really keen on it (the
> router/modem). So I thought to myself that it couldn't be /that/ hard
> to build a box with FBSD that could replace it - am I crazy? Wouldn't

On topic: shouldn't this discussion be on another mailing list? For
eaxmple -questions or -net, or even -arch?
-- 
Regards,
Torfinn Ingolfsen,
Norway

___
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"

Re: Puzzling change in performance

[Torfinn Ingolfsen]

On Fri, 30 Jan 2009 11:50:05 +0100
Borja Marcos  wrote:

> I see that the attachments didn't make it.

Well, it would be quite easy for you to just put them on the web
somewhere and then link to them, perhaps?

> 1- there's an important improvement on file caching from 7.0-STABLE- 
> August to 7.1-RELEASE?

Have you checked the release notes for 7.1? Perhaps they contain clues
that explain the performace improvements?

HTH
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: Old /etc files back, or cvs error?

[Torfinn Ingolfsen]

On Tue, 24 Feb 2009 00:58:31 -0800
Kent Stewart  wrote:

> You are looking at the version for the 7.1 release version. The
> RELENG_7 version is

The real question is: why are the files in 7.1-release newer than those
in RELENG_7?
In other words: why haven't those files been updated in RELENG_7?

Are there something wrong with the newer files?

For RELENG_7 users it is inconvenient to have to go through all these
files every time a 7.1-release install gets updated to RELENG_7.
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: freebsd / gpt boot

[Torfinn Ingolfsen]

On Sun, 13 Dec 2009 22:53:44 +
Steven Hartland  wrote:

> The only thing I'd warn you about is to ensure you use the DVD not
> the CD as the CD doesn't have all the things you'll need on it.

FWIW, the memstick image worked nicely, too.
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: freebsd / gpt boot

[Torfinn Ingolfsen]

On Mon, 14 Dec 2009 15:28:50 +
Steven Hartland  wrote:

> Using a memstick live would presumably get
> around this issue due to the fact you can have Disk 0 in the
> CDROM as well :)

Err, no. It gets around thia by the very fact that all files required
are on the memstick image - no other image required. :)
The machine I installed on didn't have an optical drive at all.
-- 
Torfinn

___
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"

Re: FreeBSD 8 GPT install, how?

[Torfinn Ingolfsen]

On Thu, 03 Dec 2009 03:03:29 -0600
Scot Hetzel  wrote:

> If you have a look at the Root On ZFS tutorial, it shows how to create
> a GPT formated system from the Fixit environment:
> 
> http://wiki.freebsd.org/RootOnZFS

Just FYI, this tutorial worked nicely with the memtick image,
installing on a amd64 machine.
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: FreeBSD 8 GPT install, how?

[Torfinn Ingolfsen]

On Tue, 15 Dec 2009 17:54:06 +0100
Torfinn Ingolfsen  wrote:

> On Thu, 03 Dec 2009 03:03:29 -0600
> Scot Hetzel  wrote:
> 
> > If you have a look at the Root On ZFS tutorial, it shows how to
> > create a GPT formated system from the Fixit environment:
> > 
> > http://wiki.freebsd.org/RootOnZFS
> 
> Just FYI, this tutorial worked nicely with the memtick image,

s/memtick/memstick/

sigh.
-- 
Regards,
Torfinn Ingolfsen

___
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"

Why does FreeBSD 8.-0 think that my Dell SX260 have "non-unform processors"?

[Torfinn Ingolfsen]

Hi,
I just booted my Dell OptiPlex SX260[1] from a usb memory stick with
FreeBSD 8.0-release on it. Part of the dmesg output is:
Copyright (c) 1992-2009 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 is a registered trademark of The FreeBSD Foundation.
FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:48:17 UTC 2009
r...@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 2.60GHz (1295.21-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf29  Stepping = 9
  
Features=0xbfebfbff
  Features2=0x4400
real memory  = 2147483648 (2048 MB)
avail memory = 2085347328 (1988 MB)
ACPI APIC Table: 
WARNING: Non-uniform processors.
WARNING: Using suboptimal topology.
ioapic0: Changing APIC ID to 1
ioapic0  irqs 0-23 on motherboard
kbd1 at kbdmux0

Full demsg output on the FreeBSD page[2] for this machine.
Why does FreeBSD think that this machine has "non-unform processors?
Ok, the Pentium 4 in it can proably do hyperthreading, but that isn't
much to talk about.
What excatly is non-unform here?

References:
1) http://sites.google.com/site/tingox/sx260
2) http://sites.google.com/site/tingox/sx260_freebsd
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: 8-STABLE: support for this SMB controller?

[Torfinn Ingolfsen]

On Tue, 22 Dec 2009 08:57:54 +0300
Yuri Pankov  wrote:

> On Tue, Dec 22, 2009 at 06:51:04AM +0100, Oliver Lehmann wrote:
> > Andriy Gapon wrote:
> > Hm so I guess there is no other way in determining the CPUs
> > temperature?
> 
> Tried coretemp(4) yet?

And for those running AMD cpus there is amdtemp(4).
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: Why does FreeBSD 8.-0 think that my Dell SX260 have "non-unform processors"?

[Torfinn Ingolfsen]

On Mon, 21 Dec 2009 15:29:54 +1100 (EST)
Ian Smith  wrote:

> Why is it booting up at half speed?  Same in your 7.2-STABLE dmesg.

I don't know.  Since last time, I've upgraded the bios to the latest
(A03) and reset bios to default values - but the problem is still there.
According to the specs, a SX260 supports all Pentium 4 cpus with 400
MHz and 533 MHz FSB (front side bus).

> Something set that way in BIOS?  What does 'sysctl dev.cpu' say?

The only setting in bios related to cpu speed are
"normal" and "comaptible". I've tried both - doesn't make a difference.

Now sysctl.dev.cpu says:
r...@kg-work2# sysctl dev.cpu
dev.cpu.0.%desc: ACPI CPU
dev.cpu.0.%driver: cpu
dev.cpu.0.%location: handle=\_PR_.CPU0
dev.cpu.0.%pnpinfo: _HID=none _UID=0
dev.cpu.0.%parent: acpi0
dev.cpu.0.freq: 1295
dev.cpu.0.freq_levels: 1295/-1 1133/-1 971/-1 809/-1 647/-1 485/-1 323/-1
dev.cpu.0.cx_supported: C1/0
dev.cpu.0.cx_lowest: C1
dev.cpu.0.cx_usage: 100.00% last 500us
dev.cpu.1.%desc: ACPI CPU
dev.cpu.1.%driver: cpu
dev.cpu.1.%location: handle=\_PR_.CPU1
dev.cpu.1.%pnpinfo: _HID=none _UID=0
dev.cpu.1.%parent: acpi0
dev.cpu.1.cx_supported: C1/0
dev.cpu.1.cx_lowest: C1
dev.cpu.1.cx_usage: 100.00% last 500us

> 
> Only spotted a verbose dmesg for 7.2-STABLE there, not for 8.0?

Not, I didn't make one that evening. There is one over ther now. :-)

> I suppose you have HTT disabled in BIOS?

Yes, I had, it is enabled now.
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: Why does FreeBSD 8.-0 think that my Dell SX260 have "non-unform processors"?

[Torfinn Ingolfsen]

On Mon, 21 Dec 2009 21:21:45 + (GMT)
Gavin Atkinson  wrote:

> Can you please reboot and show a verbose dmesg from this system?

Yes, it is there[1] now. :-)

> Also, how many CPUs does this system actually have?  It appears that
> in the 7.2 dmesg at 2) above, two are detected but only one is ever
> used - are you explicitly disabling hyperthreading somehow?

It has one Pentium 4 cpu.
Hyperthreading was disabled in bios, it is enabled now:
Copyright (c) 1992-2009 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 is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.2-STABLE #6: Sun Oct 11 11:14:33 CEST 2009
r...@kg-work2.kg4.no:/usr/obj/usr/src/sys/SX270
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 2.60GHz (1295.21-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf29  Stepping = 9
  
Features=0xbfebfbff
  Features2=0x4400
  Logical CPUs per core: 2
real memory  = 2145849344 (2046 MB)
avail memory = 2090192896 (1993 MB)
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
 cpu0 (BSP): APIC ID:  0
 cpu1 (AP/HT): APIC ID:  1
ioapic0: Changing APIC ID to 2
ioapic0  irqs 0-23 on motherboard
kbd1 at kbdmux0
acpi0:  on motherboard


References:
1) http://sites.google.com/site/tingox/sx260_freebsd

-- 
Torfinn

___
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"

Re: Why does FreeBSD 8.-0 think that my Dell SX260 have "non-unform processors"?

[Torfinn Ingolfsen]

On Wed, 23 Dec 2009 17:08:58 +1100 (EST)
Ian Smith  wrote:

> On Wed, 23 Dec 2009, Torfinn Ingolfsen wrote:
>  > 
>  > I don't know.  Since last time, I've upgraded the bios to the
>  > latest (A03) and reset bios to default values - but the problem is
>  > still there. According to the specs, a SX260 supports all Pentium
>  > 4 cpus with 400 MHz and 533 MHz FSB (front side bus).
> 
> Yes, this is your problem, regarding speed anyway.  I only picked up
> on this because this year we bought 2 used intel mobos on eBay; a
> D845GBV with a 2GHz P4 (also 400/533 MHz FSB with similar 845 chips
> to yours) and the other a D865GLC with a 2.6GHz HTT P4 (400/533/800
> MHz FSB).

You're right, of course. :-)
I found a Pentium 4 with 400 Mhz FSB, it looks much better now:
FreeBSD 7.2-STABLE #6: Sun Oct 11 11:14:33 CEST 2009
r...@kg-work2.kg4.no:/usr/obj/usr/src/sys/SX270
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 2.00GHz (1992.63-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0xf27  Stepping = 7
  
Features=0xbfebfbff
  Features2=0x4400
real memory  = 2145849344 (2046 MB)

and  FreeBSD 8.0 doesn't say anything about "non-unform cpu" anymore.  ;^)
-- 
Regards,
Torfinn Ingolfsen,
Norway
___
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"

Re: Multiple serial consoles via null modem cable

[Torfinn Ingolfsen]

On Tue, 12 Jan 2010 08:08:16 -0800
Jeremy Chadwick  wrote:

> Yes this is possible with FreeBSD -- but you'll need to purchase a

And easy enough with conserver[1] and conserver-com[2] in ports.
No reason to exclude FreeBSD from this task.  :)

References:
1) http://www.freshports.org/comms/conserver/
2) http://www.freshports.org/comms/conserver-com/
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: 8.0-RELEASE -> -STABLE and size of /

[Torfinn Ingolfsen]

On Fri, 22 Jan 2010 17:21:56 +0100
Oliver Brandmueller  wrote:

> Instaling the new kernel failed, since /boot/kernel/ is already well 
> over 230 MBytes in size. moving that to kernel.old and writing a new one 
> with about the same size fails due to no space left on device.
> 
> This is not a question; I do know how to get around this and how to 
> configure custom kernels so they are a fragment of that size afterwards. 

It would also be nice if we knew how to configure the
whole "make world" procedure[1] to make a new kernel and modules without 
symbols. 
The FAQ doesn't seem to have that answer either.


References:
1) http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: 8.0-RELEASE -> -STABLE and size of /

[Torfinn Ingolfsen]

On Sat, 23 Jan 2010 16:20:54 -0800
Kevin Oberman  wrote:

> Just for the record and to avoid further confusion, building a kernel
> with debug symbols does not take any more space in root. Another copy of
> the kernel is built but not installed into /kernel. The copy of the kernel
> in /kernel is always symbol-less.

Perhaps my question should be changed to:
how do I configure  the "make world" procedure so that no files ending
in '*symbol' get installed in /boot/kernel?
-- 
Regards, 
Torfinn Ingolfsen

___
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"

Re: Extra keys in multimedia keyboard doesn't work

[Torfinn Ingolfsen]

On Sun, 24 Jan 2010 23:47:46 +
Krzysztof Dajka  wrote:

> I did check my keyboard with FreeBSD 7.2 and it wasn't supported either.  
> Xev also didn't return anything.

Di you try this: http://www.freshports.org/misc/hotkeys/
Perhaps it will work?

There is also this: http://www.freshports.org/sysutils/usbhotkey/

HTH
-- 
Torfinn

___
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"

Re: 8.0-RELEASE -> -STABLE and size of /

[Torfinn Ingolfsen]

On Sat, 23 Jan 2010 20:41:59 -0600
Larry Rosenman  wrote:

> 
> add the following to /etc/make.conf:
> INSTALL_NODEBUG=yes

This is useful. Thanks!
-- 
Regards,
Torfinn Ingolfsen
___
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"

panic - sleeping thread on FreeBSD 8.0-stable / amd64

[Torfinn Ingolfsen]

Hi,

One of my machines had a panic or something.
The machine was pingable, but I couldn't ssh into it, and there was no response 
on the console.

On the console was these lines:
"Sleeping thread (tid 10014, pid 0) owns a non-sleepable lock"
"panic: sleeping thread"
"cpuid = 1"

The only thing I did with the machine yesterday (before this happened) was to 
upgrade the machine froms zfs v13 to v14.
But that went well, no problems. 
r...@kg-f2# last | head -6
tingopts/1kg-v2.kg4.no Sun Jan 31 14:26   still logged in
tingopts/0kg-v2.kg4.no Sun Jan 31 14:26   still logged in
root ttyv0 Sun Jan 31 14:25   still logged in
reboot   ~ Sun Jan 31 14:25
reboot   ~ Sat Jan 30 17:48
reboot   ~ Sat Jan 30 17:31

The two reboots yesterday is from the zfs upgrade.

Since I couldn't do anything useful with it, I just turned off the power and 
rebooted it.

The machine runs FreeBSD 8,0 stable and zfs:
r...@kg-f2# uname -a
FreeBSD kg-f2.kg4.no 8.0-STABLE FreeBSD 8.0-STABLE #1: Fri Jan 15 16:43:49 CET 
2010 r...@kg-f2.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64

It will be a file server, nut is mostly idle now (I haven't started using it 
yet).
Details on the hardware: http://sites.google.com/site/tingox/ga-ma74gm-s2h
dmesgs and more on the FreeBSD page for this machine: 
http://sites.google.com/site/tingox/ga-ma74gm-s2h_freebsd

HTH
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: panic - sleeping thread on FreeBSD 8.0-stable / amd64

[Torfinn Ingolfsen]

On Sun, 31 Jan 2010 14:42:17 +0100
Torfinn Ingolfsen  wrote:

> Hi,
> 
> One of my machines had a panic or something.
> The machine was pingable, but I couldn't ssh into it, and there was no 
> response on the console.
> 

And it did it again, only a few hours later. I'll try to update to latest 
-stable, and see if that helps.
Same messgae as last time, unfortunately I didn't record tge details (tid and 
pid). Oh well.

-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: panic - sleeping thread on FreeBSD 8.0-stable / amd64

[Torfinn Ingolfsen]

On Sun, 31 Jan 2010 17:56:39 +0100
Torfinn Ingolfsen  wrote:

> On Sun, 31 Jan 2010 14:42:17 +0100
> Torfinn Ingolfsen  wrote:
> 
> > Hi,
> > 
> > One of my machines had a panic or something.
> > The machine was pingable, but I couldn't ssh into it, and there was no 
> > response on the console.
> > 
> 
> And it did it again, only a few hours later. I'll try to update to latest 
> -stable, and see if that helps.
> Same messgae as last time, unfortunately I didn't record tge details (tid and 
> pid). Oh well.

Well, it was stable for many days, but today it rebooted on its ownb again.
After the fact, I see this in /var/log/messages:
Feb  7 11:50:16 kg-f2 ntpd[906]: time reset +2.376096 s
Feb  7 12:02:21 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 
007f
Feb  7 12:02:21 kg-f2 kernel: ata6: hardware reset timeout
Feb  7 12:05:43 kg-f2 syslogd: kernel boot file is /boot/kernel/kernel

So there is probably some problem with a cable or disk.
On the plus side, it did reboot and came upa agin without any issues.
-- 
Regards,
Torfinn Ingolfsen

___
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"

ntpd struggling to keep up - how to fix?

[Torfinn Ingolfsen]

Hi,

One of my machines, the fileserver-with-zfs-to-be[1] has trouble
keeping correct time. Or rather, ntpd is struggling.
In /var/lkog/messages I see this:
Feb  7 12:05:54 kg-f2 ntpd[909]: ntpd 4.2.4p5-a (1)
Feb  7 12:11:16 kg-f2 ntpd[910]: time reset +1.020413 s
Feb  7 12:11:16 kg-f2 ntpd[910]: kernel time sync status change 2001
Feb  7 12:26:26 kg-f2 ntpd[910]: time reset +2.277793 s
Feb  7 12:41:29 kg-f2 ntpd[910]: time reset +2.260229 s
Feb  7 12:57:02 kg-f2 ntpd[910]: time reset +2.332972 s
Feb  7 13:21:24 kg-f2 ntpd[910]: time reset +3.659869 s
Feb  7 13:37:01 kg-f2 ntpd[910]: time reset +2.343230 s
Feb  7 13:52:24 kg-f2 ntpd[910]: time reset +2.310659 s
Feb  7 14:07:29 kg-f2 ntpd[910]: time reset +2.265705 s
Feb  7 14:23:03 kg-f2 ntpd[910]: time reset +2.335868 s
Feb  7 14:39:06 kg-f2 ntpd[910]: time reset +2.46 s
Feb  7 14:54:32 kg-f2 ntpd[910]: time reset +2.318222 s
Feb  7 15:09:55 kg-f2 ntpd[910]: time reset +2.308120 s
Feb  7 15:25:49 kg-f2 ntpd[910]: time reset +2.388391 s
Feb  7 15:40:54 kg-f2 ntpd[910]: time reset +2.265464 s
Feb  7 15:55:57 kg-f2 ntpd[910]: time reset +2.257952 s
Feb  7 16:11:45 kg-f2 ntpd[910]: time reset +2.373325 s

and this goes on an on, forever. At any give time, no matter how long the 
machine has been up, ntpq ca report this:
r...@kg-f2# ntpq -p
 remote   refid  st t when poll reach   delay   offset  jitter
==
 kg-omni1.kg4.no 129.240.64.3 3 u   13   64   370.162  703.094 444.681

Note: all machines on my LAN use my firewall as the ntp server. 
The ntp server runs FreeBSD, none of the other machines have any trouble 
keeping time.
My workstation for example:
ti...@kg-v2$ ntpq -p
 remote   refid  st t when poll reach   delay   offset  jitter
==
*kg-omni1.kg4.no 129.240.64.3 3 u   44   64  3770.1384.018   0.338
(my workstatuion also runs FreeBSD 8.0-stable / amd64)

The machine runs FreeBSD 8.0-stable / amd64:
r...@kg-f2# uname -a
FreeBSD kg-f2.kg4.no 8.0-STABLE FreeBSD 8.0-STABLE #2: Sun Jan 31 18:39:17 CET 
2010 r...@kg-f2.kg4.no:/usr/obj/usr/src/sys/GENERIC  amd64

So, how can I get the machine to keep time / get ntpd synchronised?

References:
1) hw info: http://sites.google.com/site/tingox/ga-ma74gm-s2h
2) FreeBSD info: http://sites.google.com/site/tingox/ga-ma74gm-s2h_freebsd
-- 
Regards,
Torfinn Ingolfsen

___
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"

Re: ntpd struggling to keep up - how to fix?

[Torfinn Ingolfsen]

On Thu, 11 Feb 2010 10:25:59 -0800
Chuck Swiger  wrote:

> The rate at which this machine is losing time is probably exceeding the ~50 
> seconds per day that NTPd is willing to correct without extreme measures (ie, 
> it has to step time rather than drift-correct).  > You might help it maintain 
> a more sane idea of time by using at least 4 timeservers.

Hmm, ok that iis something I can try.

> You might take a look at 'vmstat -i' and look out for an interrupt storm, but 
> it's possible your hardware's clock is simply busted.  

AFAICT, vmstat -i looks ok:
r...@kg-f2# uptime
 1:23PM  up 18:31, 3 users, load averages: 0.00, 0.00, 0.00
r...@kg-f2# vmstat -i
interrupt  total   rate
irq1: atkbd0  36  0
irq6: fdc0 1  0
irq16: siis0 ohci0+  408  0
irq22: atapci0856338 12
cpu0: timer133347678   1999
irq256: re0   234087  3
cpu1: timer17654   1999
Total  267776202   4016


-- 
Regards,
Torfinn

___
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"

Re: ntpd struggling to keep up - how to fix?

[Torfinn Ingolfsen]

On Thu, 11 Feb 2010 11:25:15 -0800
Jeremy Chadwick  wrote:

> 
> Your machine has a rapidly drifting clock, usually an indicator of a
> hardware problem (crystal gone bad is a common one -- seen this at work
> quite a few times), or possibly a bad time counter source chosen by the
> kernel.  Can you please provide the output of:
> 
> sysctl kern.timecounter

Here it is:
r...@kg-f2# sysctl kern.timecounter
kern.timecounter.tick: 1
kern.timecounter.choice: TSC(-100) HPET(900) ACPI-safe(850) i8254(0) 
dummy(-100)
kern.timecounter.hardware: HPET
kern.timecounter.stepwarnings: 0
kern.timecounter.tc.i8254.mask: 65535
kern.timecounter.tc.i8254.counter: 52444
kern.timecounter.tc.i8254.frequency: 1193182
kern.timecounter.tc.i8254.quality: 0
kern.timecounter.tc.ACPI-safe.mask: 4294967295
kern.timecounter.tc.ACPI-safe.counter: 3252982815
kern.timecounter.tc.ACPI-safe.frequency: 3579545
kern.timecounter.tc.ACPI-safe.quality: 850
kern.timecounter.tc.HPET.mask: 4294967295
kern.timecounter.tc.HPET.counter: 3443625641
kern.timecounter.tc.HPET.frequency: 14318180
kern.timecounter.tc.HPET.quality: 900
kern.timecounter.tc.TSC.mask: 4294967295
kern.timecounter.tc.TSC.counter: 1276479615
kern.timecounter.tc.TSC.frequency: 2819782573
kern.timecounter.tc.TSC.quality: -100
kern.timecounter.smp_tsc: 0
kern.timecounter.invariant_tsc: 1

> Finally, was this OS installation used on different hardware in the
> past?  Meaning: was the hard disk previously installed on another
> machine?

Nope. Brand new hw, hard drive, and FreeBSD 8.0-release install. Then I 
upgraded to 8.0-stable.

>  Why I'm asking: /var/db/ntpd.drift could be from an old
> computer (the previous hardware), and the clock drift rate would be
> different than that of your newer[1] hardware. 

No, /var/db/ntp.drift is created on this machine.
-- 
Regards,
Torfinn

___
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"

Re: ntpd struggling to keep up - how to fix?

[Torfinn Ingolfsen]

On Thu, 11 Feb 2010 22:49:59 +0100
Stefan Krueger  wrote:

> I have the some problem on my machine (also AMD, running 8.0 +
> patches), after a while ntpd gives up sync'ing and then the time is off
> by minutes (roughly 80sec after.. say 10 hours) :(

FWIW, I have several other AMD systems, from both Asus, MSI and
Gigabyte. Noene of them have problems with ntp.

> I switched to opentnpd (you can find it in ports) and the clock stays
> in sync now, so you might want to consider that, too

I will if that is the only solution. However, if there is something
wrong with my setup / configuration of this machine, I'll rather fix
that.
-- 
Regards,
Torfinn

___
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"

Re: ntpd struggling to keep up - how to fix?

[Torfinn Ingolfsen]

On Fri, 12 Feb 2010 05:11:17 -0800
Jeremy Chadwick  wrote:

> Please try doing this:
> 
> - stop ntpd
> - rm /var/db/ntpd.drift
> - sysctl kern.timecounter.hardware=ACPI-safe
> - start ntpd

Thanks, I'm currently testing that. Results in 72 hours (or less) :-)

> Then see if your clock drifts.  If it stops, great -- you can put that
> sysctl assignment line in /etc/sysctl.conf and consider it a done deal.
> I highly recommend putting some comments around it though so in the
> future you don't go "What's this? Silly!" and delete it.  ;-)

Yes, I know. Learned the hard way that I need to document things for my
own use. :-)

> I'll also point out that it's common on FreeBSD[1] to see messages
> like the following (or at least it was circa 2006 -- I believe ntpd

Yes, those messages are still there. At one time, I thought about
fixing that (by using the config you present), but in the end I figured
that these messages actually helps me in pinpointing time of crash in
the (few) cases wherer one of my machines crashes or panics. So in the
end I did nothing about it.

> Finally, you should really consider adding some stratum 2 sources to
> your list, *in addition* to the stratum 3 server you're already using.

Well, the stratum 3 server is my firewall. :) All the machines on my
LAN use that one as the ntp server.
My firewall is currently using three ntp
servers as sources, one is a non-public stratum 2 server (yes, I asked
for permission before I started using it), one is the no.poool.ntp.org
pool ( stratum
3) and I just found out that the third one has stopped responding.
So I removed it.

I have added the dk.pool.ntp.org and se.pool.ntp.org pools, we will see
how that turns out.

> ntpd can happily work with multiple servers, and will pick the best one

Yes, I know. It is a few years since I set this up, but at that time I
figured that if I use three ntp servers for my firewall, and just used
the firewall for all my internal machines, that would be good enough
for my uses. 
Perhaps I need to re-evaluate my needs.
-- 
Regards,
Torfinn

___
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"

Re: panic - sleeping thread on FreeBSD 8.0-stable / amd64

[Torfinn Ingolfsen]

On Sun, 07 Feb 2010 16:36:31 +0100
Torfinn Ingolfsen  wrote:

> Well, it was stable for many days, but today it rebooted on its ownb again.
> After the fact, I see this in /var/log/messages:
> Feb  7 11:50:16 kg-f2 ntpd[906]: time reset +2.376096 s
> Feb  7 12:02:21 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 
> 007f
> Feb  7 12:02:21 kg-f2 kernel: ata6: hardware reset timeout
> Feb  7 12:05:43 kg-f2 syslogd: kernel boot file is /boot/kernel/kernel
> 
> So there is probably some problem with a cable or disk.

Or just plain broken hardware. The machine rebooted last night.
In /var/log/messages I see:
Feb 13 03:50:20 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 
007f
Feb 13 03:50:20 kg-f2 kernel: ata5: hardware reset timeout

Last time it was ata6 and now it is ata5? Hmm...
-- 
Torfinn

___
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"

Re: ntpd struggling to keep up - how to fix?

[Torfinn Ingolfsen]

On Fri, 12 Feb 2010 11:46:04 -0800
Jeremy Chadwick  wrote:

> override this though!  :-) ), which -- assuming it works -- should
> solve your problem.

We'll see. The box rebooted again last night (see another thread on this
mailing list), so now I have added kern.timecounter.hardware=ACPI-safe
to /etc/sysctl.conf, just in case it reboots again.

> Technical footnote: I wish I understood 1) the difference between
> ACPI-safe and ACPI-fast, and 2) how the system or OS "ranks" the

I'm still wondering why this machine doesn't have ACPI-fast:
o...@kg-f2# sysctl kern.timecounter.choice
kern.timecounter.choice: TSC(-100) HPET(900) ACPI-safe(850) i8254(0) 
dummy(-100)

While my workstation do:
ti...@kg-v2$ sysctl kern.timecounter.choice
kern.timecounter.choice: TSC(-100) HPET(900) ACPI-fast(1000) i8254(0) 
dummy(-100)
and anaother machine:
r...@kg-quiet# sysctl kern.timecounter.choice
kern.timecounter.choice: TSC(800) ACPI-fast(1000) i8254(0) dummy(-100)
and another:
r...@kg-vm# sysctl kern.timecounter.choice
kern.timecounter.choice: TSC(-100) ACPI-fast(1000) i8254(0) dummy(-100)

Probably a BIOS / acpi problem.
-- 
Torfinn

___
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"

Re: panic - sleeping thread on FreeBSD 8.0-stable / amd64

[Torfinn Ingolfsen]

Another crash last night. In /var/log/messages:

Feb 16 23:13:22 kg-f2 ntpd[2826]: time reset +1.780863 s
Feb 16 23:16:42 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 
007f
Feb 16 23:16:42 kg-f2 kernel: ata6: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 
007f
Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 
007f
Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 
007f
Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 
007f
Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 
0080
Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ad4: TIMEOUT - WRITE_DMA retrying (1 retry left) 
LBA=65614674
Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 
007f
Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 
007f
Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 
007f
Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 
007f
Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 
007f
Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 
0080
Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 
007f
Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 
0080
Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ad6: TIMEOUT - WRITE_DMA retrying (1 retry left) 
LBA=65614674
Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 
007f
Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 
007f
Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 
007f
Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 
007f
Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 
007f
Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 
007f
Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 
007f
Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ata6: port is not ready (timeout 1ms) tfd = 
0080
Feb 16 23:20:39 kg-f2 kernel: ata6: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ad6: WARNING - WRITE_DMA requeued due to channel 
reset LBA=65614674
Feb 16 23:20:39 kg-f2 kernel: ata3: FAILURE - already active DMA on this device
Feb 16 23:20:39 kg-f2 kernel: ata3: setting up DMA failed
Feb 16 23:20:39 kg-f2 kernel: ad6: TIMEOUT - READ_DMA retrying (1 retry left) 
LBA=8389026
Feb 16 23:20:39 kg-f2 kernel: ata5: port is not ready (timeout 1ms) tfd = 
0080
Feb 16 23:20:39 kg-f2 kernel: ata5: hardware reset timeout
Feb 16 23:20:39 kg-f2 kernel: ad4: TIMEOUT - WRITE_DMA retrying (0 retries 
left) LBA=65614674
Feb 16 23:20:39 kg-f2 kernel: ad6: TIMEOUT - READ_DMA retrying (0 retries left) 
LBA=8389026
Feb 16 23:20:39 kg-f2 root: ZFS: vdev I/O failure, zpool=zroot 
path=/dev/gpt/disk1 offset=29299662848 size=4096 error=5
Feb 17 09:09:40 kg-f2 syslogd: kernel boot file is /boot/kernel/kernel

But ad4 and ad6 are the two disk mirrir (zfs) that I have built my root 
filesystem on. Hmm.
-- 
Torfinn

___
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"

Re: ZFS tuning [was: hardware for home use large storage]

[Torfinn Ingolfsen]

On Wed, 17 Feb 2010 09:19:49 +0100
Bartosz Stec  wrote:

> So here's my reply (last line seems most interesting ;) :
[...snipped...]
> Illegal division by zero at ./arc_summary.pl line 242.

FWIW, I also got this line when I ran this script on my idle zfs server.
-- 
Torfinn

___
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"

Re: ntpd struggling to keep up - how to fix?

[Torfinn Ingolfsen]

On Fri, 12 Feb 2010 17:44:52 +0100
Torfinn Ingolfsen  wrote:

> On Fri, 12 Feb 2010 05:11:17 -0800
> Jeremy Chadwick  wrote:
> 
> > Please try doing this:
> > 
> > - stop ntpd
> > - rm /var/db/ntpd.drift
> > - sysctl kern.timecounter.hardware=ACPI-safe
> > - start ntpd
> 
> Thanks, I'm currently testing that. Results in 72 hours (or less) :-)

Well, using ACPI-safe only get a small improvement,
here are the lines from /var/log/messages:
Feb 17 17:16:47 kg-f2 ntpd[912]: time reset +1.785920 s
Feb 17 17:32:39 kg-f2 ntpd[912]: time reset +1.836376 s
Feb 17 17:48:18 kg-f2 ntpd[912]: time reset +1.811593 s
Feb 17 18:04:12 kg-f2 ntpd[912]: time reset +1.840545 s
Feb 17 18:19:19 kg-f2 ntpd[912]: time reset +1.751837 s
Feb 17 18:35:19 kg-f2 ntpd[912]: time reset +1.852328 s
Feb 17 18:51:18 kg-f2 ntpd[912]: time reset +1.850928 s
Feb 17 19:06:50 kg-f2 ntpd[912]: time reset +1.798706 s
Feb 17 19:22:35 kg-f2 ntpd[912]: time reset +1.823697 s
Feb 17 19:37:56 kg-f2 ntpd[912]: time reset +1.777376 s

Unfortunately, it isn't enough to keep the machine in sync all the time.
But it is better than HPET so I'll keep it.
-- 
Torfinn

___
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"

Re: ntpd struggling to keep up - how to fix?

[Torfinn Ingolfsen]

On Wed, 17 Feb 2010 19:49:27 +0100
Torfinn Ingolfsen  wrote:

> Unfortunately, it isn't enough to keep the machine in sync all the time.
> But it is better than HPET so I'll keep it.

This thread is interesting:
http://lkml.indiana.edu/hypermail/linux/kernel/0903.1/01356.html

Is there a way in FreeBSD to perform adjustmenst like adjtimex?
'apropos adjtime' only gives me a system call, 
the man pages for hz(9) and hardclock(9) doesn't exist on 8.0-stable
(or on 7.2-stable).

-- 
Torfinn

___
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"

Re: ntpd struggling to keep up - how to fix?

[Torfinn Ingolfsen]

On Fri, 19 Feb 2010 07:54:58 +1100
Peter Jeremy  wrote:

> On 2010-Feb-17 20:03:22 +0100, Torfinn Ingolfsen 
>  wrote:
> Did you delete /etc/ntp.drift between timecounter changes?

I sure did, I used the instructions given.

> There's ntptime(8) but it doesn't have a "self-calibrate mode".

Ok, good to know.

> Based on the messages log you gave, and assuming the ntpd PLL is sane,
> your acpi-safe clock is about 2500ppm slow (the steps reflect about
> 2000ppm and the ntpd PLL should be compensating for a further 500ppm)
> - this is really bad, even for consumer-grade stuff.  Are you running
> non-standard clock speeds or multipliers?

No, everything at default values here (ie. I haven't changed anything in either 
BIOS or FreeBSD),
except from changing timer from HPET to ACPI-safe.

> If there's nothing obvious, I'd follow John Hay's suggesion and
> force set either your TSC or ACPI frequency in sysctl.conf (you
> can't override the HPET frequency).
> 
> Take either the TSC or ACPI frequency reported by "sysctl machdep",
> reduce it by 2500ppm and set that in /etc/sysctl.conf.  Assuming
> a "standard" (3.58MHz) ACPI, the latter would look like:
> 
> machdep.acpi_timer_freq=3570596

This one is 
r...@kg-f2# sysctl machdep.acpi_timer_freq
machdep.acpi_timer_freq: 3579545

So I should change that to 3577045, right?
Like so:
r...@kg-f2# sysctl machdep.acpi_timer_freq=3579545
machdep.acpi_timer_freq: 3579545 -> 3579545

and I put it into /etc/sysctl.conf as well (in case the machine reboots again).

> kern.timecounter.hardware=ACPI-safe

Yes, this is already in /etc/sysctl.conf


> The stop ntpd, delete /var/db/ntp.drift and either reboot or
> manually set the above sysctl's and restart ntpd.

Done. We'll see if it works or not.

> [I think I've got the adjustment direction correct in the above, if
> I've stuffed up, you need to adjust in the other direction]

Ok.

Thanks to all for helping out.
-- 
Torfinn

___
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"