Newbie Sempron/ISO question

2007-02-01 Thread Thomas Roberts
I need help deciding which ISO to install on my machine, which is a Compaq Presario SR1620NX. The FreeBSD/amd64 Project web page says the Sempron uses the AMD64 architecture so I installed the amd64 6.2-RELEASE ISO. Since I want to stay with STABLE I started reading on how to do it and am now con

Re: Loader hang

2007-02-01 Thread Stanislav Sedov
On Thu, 1 Feb 2007 13:45:33 +1030 "Daniel O'Connor" <[EMAIL PROTECTED]> mentioned: > Hi *, > I recently installed 6.2 on a Supermicro P8SCT and I found that the loader > would hang after a few seconds unless I disabled the Adaptec 29160's BIOS. > > It also has a 3ware 8006-2LP (which I am booting

Re: ath0: ath_reset: unable to reset hardware; hal status 3

2007-02-01 Thread Kai Lockwood
Hello, I am having the same type of trouble with a Dynex card. I mearly receive 'ath0: Device timeout' on the main console screen. > I take it you tried ifconfig'ing the interface down and up? I have. The card does not appear to reset itself. While the card is up, it just rotates across the cha

Re: portupgrade -arR errors

2007-02-01 Thread Brian
Ilya Vishnyakov wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please help me to find out why portupgrade -arR gives me errors such as: missing key: categories: Cannot read the portsdb! /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:548:in `open_db': database file error (PortsDB::DBError)

portupgrade -arR errors

2007-02-01 Thread Ilya Vishnyakov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please help me to find out why portupgrade -arR gives me errors such as: missing key: categories: Cannot read the portsdb! /usr/local/lib/ruby/site_ruby/1.8/portsdb.rb:548:in `open_db': database file error (PortsDB::DBError) from /usr/local/l

Security Officer-supported branches update

2007-02-01 Thread FreeBSD Security Officer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello Everyone, The branches supported by the FreeBSD Security Officer have been updated to reflect recent EoL (end-of-life) events. The new list is below and at http://security.freebsd.org/ >. FreeBSD 4.11 and FreeBSD 6.0 have `expired' and are no

Re: Filesystem hang on 3ware 6.2 system

2007-02-01 Thread Craig Rodrigues
On Thu, Feb 01, 2007 at 02:24:54PM -0500, Michael R. Wayne wrote: > As I read the "kernel deadlock debugging chapter", I see that it > operates on core dumps. Once the machine enters this state, my You didn't read properly: http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kern

Re: Filesystem hang on 3ware 6.2 system

2007-02-01 Thread Kris Kennaway
On Thu, Feb 01, 2007 at 02:24:54PM -0500, Michael R. Wayne wrote: > On Wed, Jan 31, 2007 at 11:28:16AM +0200, Kostik Belousov wrote: > > On Wed, Jan 31, 2007 at 02:24:35AM -0500, Michael R. Wayne wrote: > > > We have a nubmer of similar machines that were initiallly formated > > > with 6.2 before i

Re: Filesystem hang on 3ware 6.2 system

2007-02-01 Thread Michael R. Wayne
On Wed, Jan 31, 2007 at 11:28:16AM +0200, Kostik Belousov wrote: > On Wed, Jan 31, 2007 at 02:24:35AM -0500, Michael R. Wayne wrote: > > We have a nubmer of similar machines that were initiallly formated > > with 6.2 before it was released and have subsequently been upgraded > > to 6.2-RELEASE with

Re: 6.2 amd64 panic: lockmgr: thread 0xffffff009f9fd000, not exclusive lock holder 0xffffff003961c000 unlocking

2007-02-01 Thread Kostik Belousov
On Thu, Feb 01, 2007 at 10:55:18AM -0600, Guy Helmer wrote: > Kostik Belousov wrote: > >On Thu, Feb 01, 2007 at 06:38:26PM +0200, Kostik Belousov wrote: > > > >Index: fs/procfs/procfs.c > >=== > >RCS file: /usr/local/arch/ncvs/src/sys/

Re: 6.2 amd64 panic: lockmgr: thread 0xffffff009f9fd000, not exclusive lock holder 0xffffff003961c000 unlocking

2007-02-01 Thread Guy Helmer
Kostik Belousov wrote: On Thu, Feb 01, 2007 at 06:38:26PM +0200, Kostik Belousov wrote: On Thu, Feb 01, 2007 at 10:02:08AM -0600, Guy Helmer wrote: vn_lock with LK_EXCLUSIVE|LK_RETRY flags combination shall not fail. It should return even dead vnodes locked. I suspect that in fact this is ra

Re: 6.2 amd64 panic: lockmgr: thread 0xffffff009f9fd000, not exclusive lock holder 0xffffff003961c000 unlocking

2007-02-01 Thread Kostik Belousov
On Thu, Feb 01, 2007 at 06:38:26PM +0200, Kostik Belousov wrote: > On Thu, Feb 01, 2007 at 10:02:08AM -0600, Guy Helmer wrote: > vn_lock with LK_EXCLUSIVE|LK_RETRY flags combination shall not fail. It should > return even dead vnodes locked. > > I suspect that in fact this is race with exec(). Cou

Re: 6.2 amd64 panic: lockmgr: thread 0xffffff009f9fd000, not exclusive lock holder 0xffffff003961c000 unlocking

2007-02-01 Thread Kostik Belousov
On Thu, Feb 01, 2007 at 10:02:08AM -0600, Guy Helmer wrote: > Guy Helmer wrote: > >Does this make sense to anyone (it doesn't to me - procfs_doprofile > >simply locks, calls vn_fullpath, and unlocks)? I was trying to track > >down a hang by running a system under stress, and instead got this >

Re: usb hard disk

2007-02-01 Thread Bruce Burden
On Thu, Feb 01, 2007 at 04:10:41PM +0100, Zoran Kolic wrote: > > Yup. I want my mbr on internal hdd and another grub on external > usb drive to boot linux. Simply, to let bios to choose from two > equal disks. Possible? > Mostly. :-) I have the original disk from my laptop in and USB/Fi

Re: 6.2 amd64 panic: lockmgr: thread 0xffffff009f9fd000, not exclusive lock holder 0xffffff003961c000 unlocking

2007-02-01 Thread Guy Helmer
Guy Helmer wrote: Does this make sense to anyone (it doesn't to me - procfs_doprofile simply locks, calls vn_fullpath, and unlocks)? I was trying to track down a hang by running a system under stress, and instead got this panic as a result of a process running a perl script that looks through

Re: usb hard disk

2007-02-01 Thread Zoran Kolic
> It works like this: > (usb hard drive connected to machine) > - you boot machine (on some machines you can press a special key to > bring up a bios boot menu) > - you select usb hard drive from bios boot menu > - bios loads boot loader (either Grub, Lilo, FreeBSD boot loader, > or whatever

Re: 6.2-RELEASE - Fatal trap 12 - nvidia driver ?

2007-02-01 Thread Kostik Belousov
On Thu, Feb 01, 2007 at 02:41:58PM +0100, Henri Hennebert wrote: > Kostik Belousov wrote: > >>Does the nvidia driver don't play right with devfs ? > >> > >>Thanks for your time, > > > >See PR/108078 > In my case hal is not installed. In PR/108078 the nvidia driver is there > too. So nvidia seems m

Re: 6.2-RELEASE - Fatal trap 12 - nvidia driver ?

2007-02-01 Thread Henri Hennebert
Kostik Belousov wrote: On Thu, Feb 01, 2007 at 11:39:33AM +0100, Henri Hennebert wrote: Hello, I experience Fatal trap 12 when I shutdown if I have run the X server (with nvidia driver 1.0.9746). This crash happen 4/5 of the time. It is in devfs_populate_loop() in devfs.c. I don't have the vm

Re: 6.2-RELEASE - Fatal trap 12 - nvidia driver ?

2007-02-01 Thread Kostik Belousov
On Thu, Feb 01, 2007 at 11:39:33AM +0100, Henri Hennebert wrote: > Hello, > > I experience Fatal trap 12 when I shutdown if I have run the X server > (with nvidia driver 1.0.9746). This crash happen 4/5 of the time. It is > in devfs_populate_loop() in devfs.c. I don't have the vmcore anymore :-/

6.2-RELEASE - Fatal trap 12 - nvidia driver ?

2007-02-01 Thread Henri Hennebert
Hello, I experience Fatal trap 12 when I shutdown if I have run the X server (with nvidia driver 1.0.9746). This crash happen 4/5 of the time. It is in devfs_populate_loop() in devfs.c. I don't have the vmcore anymore :-/. To look futher, I add options INVARIANTS (and INVARIANT_SUPPORT) and n

Re: portupgrade missing key: categories: Cannot read the portsdb!

2007-02-01 Thread Simon Dick
On Thu, 2007-02-01 at 11:42 +0200, Dominik Zalewski wrote: > Hi All, > > I've just updated my portstree and I'm trying to run portupgrade , which > gives > me following error: I had the same this morning, try upgrading to the latest portupgrade which got it working for me _

Re: portupgrade missing key: categories: Cannot read the portsdb!

2007-02-01 Thread Niclas Zeising
On 2/1/07, Dominik Zalewski <[EMAIL PROTECTED]> wrote: Hi All, I've just updated my portstree and I'm trying to run portupgrade , which gives me following error: [EMAIL PROTECTED] /usr/ports]# portupgrade -ai ---> Session started at: Thu, 01 Feb 2007 11:22:00 +0200 [missing key: categories] [U

Re: portupgrade missing key: categories: Cannot read the portsdb!

2007-02-01 Thread Yann Golanski
Quoth Dominik Zalewski on Thu, Feb 01, 2007 at 11:42:13 +0200 > I've just updated my portstree and I'm trying to run portupgrade , > which gives me following error: I've had the same problem last night. Sadly, the machine is at home and I at work so I cannot do much more than say "me too". Howev

Re: portupgrade missing key: categories: Cannot read the portsdb! - SOLVED

2007-02-01 Thread Dominik Zalewski
On Thursday 01 February 2007 11:46:21 am Niclas Zeising wrote: >>This has been reported several times already, and I think it's solved >>in a more recent portupgrade. >>Have a look at this thread: >>http://lists.freebsd.org/pipermail/freebsd-ports/2007-January/038395.html >>And this commit to portu

portupgrade missing key: categories: Cannot read the portsdb!

2007-02-01 Thread Dominik Zalewski
Hi All, I've just updated my portstree and I'm trying to run portupgrade , which gives me following error: [EMAIL PROTECTED] /usr/ports]# portupgrade -ai ---> Session started at: Thu, 01 Feb 2007 11:22:00 +0200 [missing key: categories] [Updating the portsdb in /usr/ports ... - 16413 port ent