Re: 4.8-PRE upgrade to FreeBSD 5 errors
Sounds as if the new boot loader wasn't installed. I had problems much like this back when I upgraded to 5-current. -- Scott - Original Message - From: "David Schultz" <[EMAIL PROTECTED]> To: "Axel Gruner" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, March 06, 2003 8:02 PM Subject: Re: 4.8-PRE upgrade to FreeBSD 5 errors > Thus spake Axel Gruner <[EMAIL PROTECTED]>: > > > > link_elf: symbol lminor undefined > > > > link_elf: symbol splhigh undefined > > > You seem to be trying to load outdated modules. > > > > Hmm, well, so what to do here? I switched of any module in loader.conf. > > THe location of modules moved between 4.x and 5.0, so you may have > to clear out the old ones (/modules). However, I haven't had any > problems with the kernel finding the wrong ones myself, so maybe > this has something to do with the other failures you experienced. > > > Yes, in single user mode, no problem. > > I did a second run there. Buildworld, buildkernel, installkernel, > > mergemaster, installworld... Same result. Same errors. > [...] > > Yes, it worked that time. > > The problem is, if i try to run /usr/sbin/mergemaster after the > > installworld, i get an error: cant cd to /usr/src/etc > > Well, then mergemaster didn't work, and that explains why you're > still getting errors. ;-) Make sure you actually have a > /usr/src/etc. > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Unable to shutdown cleanly
Hello, I'm unable to shutdown cleanly. What happens is I get the message the following message and the system freezes. I've used GENERIC as well as a custom kernel. If I shutdown to single user then umount everything but / I still get the same problems. The system runs a background fsck after rebooting. Last message I see : Waiting (max 60 seconds) for system process `vnlru' to stop...stopped To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Pentium 4 optimization status
Is it still unsafe to build everything with p4 optimizations? -- Scott To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: dnet causes Hard Lock on SMP kernel? ( was 'Why is my -current system Hard Locking?' )
On 07-Nov-2002, Joel M. Baldwin wrote: > --On Friday, November 08, 2002 8:45 AM +0900 Jun Kuriyama > <[EMAIL PROTECTED]> wrote: > > >At Thu, 7 Nov 2002 22:55:56 + (UTC), > >Joel M. Baldwin <[EMAIL PROTECTED]> wrote: > >>I'm still pursuing the cause of the Hard Locks on my system. > >> > >>1.) I have a serial console hooked up. Nothing appears on > >>the console when a Hard Lock happens. No panic. > >>2.) Shorting IOCHK to ground on the ISA connector doesn't work > >>on a ABIT BP6, so I can't force myself into ddb. > >> > >>The BIG thing is that I now have a sure fire way of forcing > >>a Hard Lock. Every time I run the distributed.net client > >>'dnet' the system hard locks. BUT ONLY ON A SMP KERNEL! > >>I have a non SMP kernel running and things so far > >>seem stable. Running the system with only 1 CPU is slow, > >>so it'll take a while for me to be sure. > > > >I got same result on my box. Only solution I have is deinstall > >dnetc. :-) > > > >-- > >Jun Kuriyama <[EMAIL PROTECTED]> // IMG SRC, Inc. > > What motherboard/CPU is this on? > Have you tried a nonSMP kernel? I noticed my machine started locking up almost a month ago and ended up removing all services on startup. Starting dnetc back up and the machine locks hard. Sorry for lack of info, but this appears to be just over a month old. The info I wrote down previously pointed to kern_fork.c and proctree function call. -- Scott DodsonPGP KEY id 0x5F9A9E5E [EMAIL PROTECTED] [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
5-current crashing when booting SMP
Over the past few weeks I've had continuous problems booting
my 5-current system with an SMP kernel. Immediately after
the system has booted and the login screen displays the machine
panics. The motherboard is an Abit BP6. Below is the information
provided when it locks up. Based on the kernel panic FAQ I
was able to determine that the suspect function is proctree but I
wasn't able to get it to dump and investigate further. My knowledge
of debugging is almost non existant, any help on the matter would
be appreciated. This has been happening since I updated around
the first week of October.
1st 0xc297f068 process lock (processlock) @ kern_fork.c:571
2nd 0xc0578d00 proctree (proctree) @ kern_fork.c:596
recursed on non-recursive lock (sleepmutex) process lock
kern_fork.c:599 first acquired @ kern_fork.c:571
panic : recurse
cpuid =1 lapic.id=0100
Debugger("panic")
Stopped at Debugger + 0x55:xchg %ebx,in_Debugger.0
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: if_dc: ethernet address now reported as 00:00:00:00:00:00
I have the same problem using a Linksys LNE100TX which uses the dc driver. I also started having problems crashing when using an SMP kernel with the same cvsup. I'm not sure if they're in anyway related. -- scott - Original Message - From: "Robert Watson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, October 21, 2002 11:11 PM Subject: if_dc: ethernet address now reported as 00:00:00:00:00:00 > > I upgraded one of my older boxes with a Linksys ethernet card this > evening, and was a bit surprised to see this in dmesg: > > dc0: port 0xe800-0xe8ff mem > 0xfebfff00-0xfebf irq 9 at device 19.0 on pci0 > dc0: Ethernet address: 00:00:00:00:00:00 > miibus0: on dc0 > dcphy0: on miibus0 > dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > This wasn't the case a month or two ago when the box was last upgraded. > I'm going to look into backing out some of the recent commits to if_dc and > see if that helps, but I have to say this result isn't thrilling :-). > Interestingly, IP works, although it's probably making a mess of the CPU > load on the surrounding machines: > > curry:~> arp -a > ... > ? (192.168.11.227) at 00:00:00:00:00:00 on xl0 [ethernet] > > Another problem I've had with this card for years is that it can't > properly negotiation 100mbps, although around 3.0-current, it could. No > time to track that down either. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > [EMAIL PROTECTED] Network Associates Laboratories > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: if_dc: ethernet address now reported as 00:00:00:00:00:00
I have the same problem using a Linksys LNE100TX which uses the dc driver. I also started having problems crashing when using an SMP kernel with the same cvsup. I'm not sure if they're in anyway related. -- scott - Original Message - From: "Robert Watson" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, October 21, 2002 11:11 PM Subject: if_dc: ethernet address now reported as 00:00:00:00:00:00 > > I upgraded one of my older boxes with a Linksys ethernet card this > evening, and was a bit surprised to see this in dmesg: > > dc0: port 0xe800-0xe8ff mem > 0xfebfff00-0xfebf irq 9 at device 19.0 on pci0 > dc0: Ethernet address: 00:00:00:00:00:00 > miibus0: on dc0 > dcphy0: on miibus0 > dcphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > This wasn't the case a month or two ago when the box was last upgraded. > I'm going to look into backing out some of the recent commits to if_dc and > see if that helps, but I have to say this result isn't thrilling :-). > Interestingly, IP works, although it's probably making a mess of the CPU > load on the surrounding machines: > > curry:~> arp -a > ... > ? (192.168.11.227) at 00:00:00:00:00:00 on xl0 [ethernet] > > Another problem I've had with this card for years is that it can't > properly negotiation 100mbps, although around 3.0-current, it could. No > time to track that down either. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > [EMAIL PROTECTED] Network Associates Laboratories > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Journaled filesystem in CURRENT
I've been having loads of problems with the bg-fsck. After recovering from a crash/power failure my machine will boot and start the check. If there's moderate activity during the time its checking it will panic and reboot, getting stuck in a loop most of the time. I've not seen anyone mention this on the list, but I was wondering if anyone's experienced this? This has been ongoing across many cvsups and buildworlds. Thanks, Scott >>> Alexander Leidinger<[EMAIL PROTECTED]> 09/26/02 12:23PM >>> On Thu, 26 Sep 2002 10:52:18 -0500 Dan Nelson <[EMAIL PROTECTED]> wrote: > > We have something better than those. SoftUpdates. Much faster than > > jfs in metadata intensive operations. > > If you can stand the 20 minutes of severly degraded performance while > the background fsck runs after a crash, and the loss of any files Sometimes it's better to have 20 minutes (or how long it takes to do the bg-fsck on your FS) degraded performance, than no performance at all (you can have this too, just configure the system to make an fg-fsck instead of a bg-fsck)... (how long does it take to check the journal and to do some appropriate actions depending on the journal?) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
