Re: port upgrade problem

2002-08-21 Thread Maxim M. Kazachek
Looks like nobody else expirienced this problem Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Wed, 21 Aug 2002, Maxim M. Kazachek wrote: portupgrade fails with reason (Makefile broken) on print/jadetex and x11-fonts/webfonts due to

sparc64 tinderbox failure

2002-08-21 Thread Dag-Erling Smorgrav
-- Rebuilding the temporary build tree -- stage 1: bootstrap tools -- stage 2: cleaning up the object tree

Re: port upgrade problem

2002-08-21 Thread Simon 'corecode' Schubert
On Wed, 21 Aug 2002 14:51:59 +0700 (NOVST) Maxim M. Kazachek wrote: Looks like nobody else expirienced this problem /usr/ports/Mk/bsd.port.mk, line 2580: warning: duplicate script for target patch-message ignored no, i got the same problem. some make issue i guess -- /\

Re: VM panic

2002-08-21 Thread Mark Murray
What kind of value do you use for N? It looks like lately the makefiles are too aggressive when using -j, so you end up with N * N * 2 processes running simultaneously. On my -current box with 128M RAM, I used -j13 for a long time, but that runs out of swap nowadays, so I'm using -j4 which

Re: current buildworld failure on Alpha?

2002-08-21 Thread Christian Weisgerber
Wilko Bulte [EMAIL PROTECTED] wrote: ds10#make Segmentation fault (core dumped) /usr/src/Makefile.inc1, line 140: warning: make -f /dev/null -m /usr/src/share/mk CPUTYPE=ev56 -V CPUTYPE returned non-zero status There was a time window when make -V ... was broken on 64-bit archs, i.e. it

Re: acpi prevents fdc to detect correctly

2002-08-21 Thread Mitsuru IWASAKI
my kernel can't detect fdc anymore when loading acpi. does anybody else have such issues? i know that it worked with a Aug 6 or a Aug 3 kernel, this was the last time i accessed my fd0. though reverting to a -D 08/06/2002 src/sys doesn't bring the desired effect (working fdc). Hmmm,

Solved: CURRENT and P-IV problems

2002-08-21 Thread Martin Blapp
Hi, As reported, Brian and I did see SIG4 and SIG11 during make buildworlds. I've replaced everything, two - three times, the problem persisted. I also tried three motherboards, but all from the same type: Intel BD843BG with DDR 266 Ram (2100). Just for interest, I've replaced this Mobo now

Re: port upgrade problem

2002-08-21 Thread John Angelmo
Maxim M. Kazachek wrote: Looks like nobody else expirienced this problem Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Wed, 21 Aug 2002, Maxim M. Kazachek wrote: portupgrade fails with reason (Makefile broken) on

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Mark Santcroos
On Wed, Aug 21, 2002 at 02:48:38PM +0200, Martin Blapp wrote: Hi, As reported, Brian and I did see SIG4 and SIG11 during make buildworlds. I've replaced everything, two - three times, the problem persisted. I also tried three motherboards, but all from the same type: Intel BD843BG

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Martin Blapp
Hi, I have a P4 mobile in my laptop and also had this behaviour for a certain -current window last week (the time I got the laptop). (Dell C640) Now it is gone. I'm sorry, I don't have an exact date/commit. Try to do some worlds in a row (5-10) and you will see if it survives. The problem

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Mark Santcroos
On Wed, Aug 21, 2002 at 03:32:44PM +0200, Martin Blapp wrote: I have a P4 mobile in my laptop and also had this behaviour for a certain -current window last week (the time I got the laptop). (Dell C640) Now it is gone. I'm sorry, I don't have an exact date/commit. Try to do some worlds

install crash on hp omnibook 6100

2002-08-21 Thread Tomas Hodan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hi all, i'm trying to install current from cd (i took 3 different builds) to my notebook hp omnibook 6100. by booting the kernel after few lines is the machine crashing. i'm not abte to see the reason, everything goes too fast. has anybody similar

Re: port upgrade problem

2002-08-21 Thread Christian Weisgerber
Maxim M. Kazachek [EMAIL PROTECTED] wrote: /usr/ports/Mk/bsd.port.mk, line 2580: warning: duplicate script for target patch-message ignored One of the recent changes in make (revision 1.38 of parse.c) causes it to emit this type of warning. This causes heaps of apparently harmless warnings

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Mark Santcroos
On Wed, Aug 21, 2002 at 04:07:14PM +0200, Mark Santcroos wrote: On Wed, Aug 21, 2002 at 03:32:44PM +0200, Martin Blapp wrote: I have a P4 mobile in my laptop and also had this behaviour for a certain -current window last week (the time I got the laptop). (Dell C640) Now it is gone. I'm

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Mark Santcroos
On Wed, Aug 21, 2002 at 04:45:54PM +0200, Mark Santcroos wrote: Can you try that ? Eek! First one already bailed out! Talking about bad luck! Signal 10 this time. The 2nd one fails at exactly the same point, that can't be coindedence. Also with a signal 10. (libutil) The 3rd

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Martin Blapp
Hi, The 2nd one fails at exactly the same point, that can't be coindedence. Also with a signal 10. (libutil) The 3rd ended somewhere else(games/rogue), but now with signal 4. Doing the 4rd now. Which ends with signal 11 in usr.sbin/devinfo/ ... Mark May this be the memory

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread KT Sin
Hi I believe this is caused by the pre-released version of gcc in the system. I started seeing this problem one week after I upgraded my hardware to Pentium 4 in May. Two weeks ago, I built the final release version of gcc 3.1.1 in the ports and used that to compile the kernel and userlands.

Re: question about ipl.ko

2002-08-21 Thread Sergey Mokryshev
Hello, Crist! You wrote to Sergey Mokryshev [EMAIL PROTECTED] on Tue, 20 Aug 2002 11:15:20 -0700: [skipped] $ grep PFIL /usr/src/sys/i386/conf/AMBER options PFIL_HOOKS You need to include options PFIL_HOOKS in your kernel configuration to be able to use ipfilter as a loadable module.

Re: question about ipl.ko

2002-08-21 Thread David W. Chapman Jr.
Another point - you can upgrade ipfilter stuff without rebooting, it is useful in situations where minimum downtime is possible. PFIL_HOOKS does not add much functionality to the kernel and I always turn this on on every box. I think you are missing his point though. Some people kldload

Re: port upgrade problem

2002-08-21 Thread Beech Rintoul
On Tuesday 20 August 2002 11:51 pm, Maxim M. Kazachek wrote: Looks like nobody else expirienced this problem Sincerely, Maxim M. Kazachek mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] On Wed, 21 Aug 2002, Maxim M. Kazachek wrote: portupgrade fails with reason

subscribe

2002-08-21 Thread Benjamin Polidore
To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message

Re: Proliferating quirk table entries

2002-08-21 Thread Chris Dillon
On Tue, 20 Aug 2002, Terry Lambert wrote: I think everyone in this thread needs to read the last instance of this same thread, the first time it came up. I believe the general consensus was to send the 6, and if it failed, retry with the 10, and set a flag so that subsequent requests were

Re: question about ipl.ko

2002-08-21 Thread Sergey Mokryshev
(removed questions@ from Cc) Hello, David! You wrote to Sergey Mokryshev [EMAIL PROTECTED] on Wed, 21 Aug 2002 11:26:32 -0500: Another point - you can upgrade ipfilter stuff without rebooting, it is useful in situations where minimum downtime is possible. PFIL_HOOKS does not add much

Re: question about ipl.ko

2002-08-21 Thread David W. Chapman Jr.
No, ipl.ko is not broken. It depends on pfil(9). Shouldn't we try to make a pfil.ko that ipl.ko depends on then? -- David W. Chapman Jr. [EMAIL PROTECTED] Raintree Network Services, Inc. www.inethouston.net [EMAIL PROTECTED] FreeBSD Committer www.FreeBSD.org To Unsubscribe: send mail

Re: question about ipl.ko

2002-08-21 Thread Sergey Mokryshev
Hello, David! You wrote to Sergey Mokryshev [EMAIL PROTECTED] on Wed, 21 Aug 2002 12:07:43 -0500: No, ipl.ko is not broken. It depends on pfil(9). DWC Shouldn't we try to make a pfil.ko that ipl.ko depends on then? I make a brief look into code (I am not a kernel hacker nor a programmer).

Re: question about ipl.ko

2002-08-21 Thread David W. Chapman Jr.
There are a few files with PFIL_HOOKS-dependant #ifdefs, but it is strongly tied with the code. /sys/net/bridge.c /sys/netinet/ip_input.c /sys/netinet/ip_output.c /sys/netinet6/ip6_forward.c /sys/netinet6/ip6_input.c /sys/netinet6/ip6_output.c Darren Reed has some pieces of code on

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Alexander Leidinger
On Wed, 21 Aug 2002 14:48:38 +0200 (CEST) Martin Blapp [EMAIL PROTECTED] wrote: As reported, Brian and I did see SIG4 and SIG11 during make buildworlds. I've replaced everything, two - three times, the problem persisted. I also tried three motherboards, but all from the same type: Intel

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Mark Santcroos
On Wed, Aug 21, 2002 at 11:38:20PM +0800, KT Sin wrote: Hi I believe this is caused by the pre-released version of gcc in the system. I started seeing this problem one week after I upgraded my hardware to Pentium 4 in May. Two weeks ago, I built the final release version of gcc 3.1.1 in

Re: acpi prevents fdc to detect correctly

2002-08-21 Thread Joerg Wunsch
As Simon 'corecode' Schubert wrote: my kernel can't detect fdc anymore when loading acpi. does anybody else have such issues? Hmm, not here. However, my fdc driver is modloaded, too (from the bootloader). I just tried to unload it, then load acpi (which yields module_register_init:

Re: install crash on hp omnibook 6100

2002-08-21 Thread Terry Lambert
Tomas Hodan wrote: i'm trying to install current from cd (i took 3 different builds) to my notebook hp omnibook 6100. by booting the kernel after few lines is the machine crashing. i'm not abte to see the reason, everything goes too fast. has anybody similar situation? any ideas why? 4.6

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Mark Santcroos
On Wed, Aug 21, 2002 at 08:05:17PM +0200, Mark Santcroos wrote: On Wed, Aug 21, 2002 at 11:38:20PM +0800, KT Sin wrote: Hi I believe this is caused by the pre-released version of gcc in the system. I started seeing this problem one week after I upgraded my hardware to Pentium 4 in

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Martin Blapp
Hi, Try to compile the entire system on another box, install it then on the CURRENT target box, and try again ! Bye the way, after 6 rounds, I see now SIG4 and SIG11 too :-/ To bad - so it's definitly data corruption in CURRENT. Asus Board P4B533-V, P-IV 2,26Ghz, 1GB DDR 2100 Ram. Martin

Re: install crash on hp omnibook 6100

2002-08-21 Thread Andy Sparrow
i'm trying to install current from cd (i took 3 different builds) to my notebook hp omnibook 6100. by booting the kernel after few lines is the machine crashing. i'm not abte to see the reason, everything goes too fast. has anybody similar situation? any ideas why? 4.6 works fine. Hi

Re: fd0 sometime not configured....

2002-08-21 Thread Joerg Wunsch
[EMAIL PROTECTED] (Jan Stocker) wrote: I cant mount my floppy from time to time. twoflower# mount -t msdosfs /dev/fd0 /home/jstocker/floppy/ msdosfs: /dev/fd0: Device not configured ENXIO is something of a `catch-all' error code in the kernel. It could mean that there's no such driver

Re: BAD psmintr: [Re: psm problem]

2002-08-21 Thread Anselm Garbe
Hi Nate, here's my dmesg: Copyright (c) 1992-2002 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 5.0-CURRENT #0: Mon Aug 19 22:50:47 CEST 2002 [EMAIL

Re: install crash on hp omnibook 6100

2002-08-21 Thread Georg-W. Koltermann
Am Mi, 2002-08-21 um 21.52 schrieb Andy Sparrow: i'm trying to install current from cd (i took 3 different builds) to my notebook hp omnibook 6100. by booting the kernel after few lines is the machine crashing. i'm not abte to see the reason, everything goes too fast. has anybody

Re: install crash on hp omnibook 6100

2002-08-21 Thread Doug White
On Wed, 21 Aug 2002, Andy Sparrow wrote: At least one person with a 6100 persevered further with this, maybe someone else can help you with the current status or better advice? There is an issue with the HP laptop DSDT and our ACPI code. They initialize some child devices before initializing

Re: BAD psmintr: [Re: psm problem]

2002-08-21 Thread Anselm Garbe
On Tue, Aug 20, 2002 at 04:05:44PM -0700, Nate Lawson wrote: BTW, just a hunch: try reverting sys/dev/pci/pci.c to 1.194 and see if that helps. Looks like the current version of psm.c is requesting a shared interrupt (RF_SHAREABLE). I've done that and compiled a new kernel (currently

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread KT Sin
Hi Please try to continue from where it broke by repeating make. Otherwise, please get a precompiled port package. kt On Wed, Aug 21, 2002 at 10:26:37PM +0200, Mark Santcroos wrote: On Wed, Aug 21, 2002 at 08:05:17PM +0200, Mark Santcroos wrote: On Wed, Aug 21, 2002 at 11:38:20PM +0800, KT

Re: BAD psmintr: [Re: psm problem]

2002-08-21 Thread Terry Lambert
Anselm Garbe wrote: atkbdc0: Keyboard controller (i8042) port 0x64,0x60 irq 1 on acpi0 atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: PS/2 Mouse irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 Mine (which works) says: atkbdc0: Keyboard controller (i8042) at

Re: Solved: CURRENT and P-IV problems

2002-08-21 Thread Don Lewis
On 21 Aug, Martin Blapp wrote: Hi, Try to compile the entire system on another box, install it then on the CURRENT target box, and try again ! Bye the way, after 6 rounds, I see now SIG4 and SIG11 too :-/ To bad - so it's definitly data corruption in CURRENT. Asus Board P4B533-V,

Re: BAD psmintr: [Re: psm problem]

2002-08-21 Thread Anselm Garbe
On Wed, Aug 21, 2002 at 05:34:36PM -0700, Terry Lambert wrote: On a hunch, I will guess that the special case code for ISA sharing for the keyboard and mouse on the same PS/2 controller is not present in the ACPI. Try not loading ACPI, and see if it fixes it for you (this seems to be the