ACPI kills my current-box frequently.

[NAKAJI Hiroyuki]

Hi,

I updated the kernel on my current-box yesterday evening.

$ uname -a
FreeBSD boggy.acest.tutrp.tut.ac.jp 5.0-CURRENT FreeBSD 5.0-CURRENT #12:
Sat Sep  8 16:56:16 JST 2001
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/NAKAJI  i386

Just after rebooting with this kernel and installworld, this host reboots
frequently, about every 10 minutes. /var/log/messages shows that

$ zgrep 'Copyright .*FreeBSD Project' /var/log/messages.1.gz  
Sep  8 17:10:36 boggy /boot/kernel/kernel: Copyright (c) 1992-2001 The FreeBSD Project.
Sep  8 17:28:57 boggy /boot/kernel/kernel: Copyright (c) 1992-2001 The FreeBSD Project.
Sep  8 17:49:55 boggy /boot/kernel/kernel: Copyright (c) 1992-2001 The FreeBSD Project.
Sep  8 18:32:36 boggy /boot/kernel/kernel: Copyright (c) 1992-2001 The FreeBSD Project.
Sep  8 18:42:08 boggy /boot/kernel/kernel: Copyright (c) 1992-2001 The FreeBSD Project.
Sep  8 18:58:45 boggy /boot/kernel/kernel: Copyright (c) 1992-2001 The FreeBSD Project.
Sep  8 19:21:52 boggy /boot/kernel/kernel: Copyright (c) 1992-2001 The FreeBSD Project.
Sep  8 19:35:39 boggy /boot/kernel/kernel: Copyright (c) 1992-2001 The FreeBSD Project.
$ zgrep 'Copyright .*FreeBSD Project' /var/log/messages.0.gz 
Sep  8 21:01:17 boggy /boot/kernel/kernel: Copyright (c) 1992-2001 The FreeBSD Project.
Sep  8 21:21:28 boggy /boot/kernel/kernel: Copyright (c) 1992-2001 The FreeBSD Project.
Sep  8 22:23:55 boggy /boot/kernel/kernel: Copyright (c) 1992-2001 The FreeBSD Project.
Sep  8 22:39:09 boggy /boot/kernel/kernel: Copyright (c) 1992-2001 The FreeBSD Project.
Sep  8 23:13:55 boggy /boot/kernel/kernel: Copyright (c) 1992-2001 The FreeBSD Project.
Sep  8 23:22:30 boggy /boot/kernel/kernel: Copyright (c) 1992-2001 The FreeBSD Project.
Sep  8 23:31:25 boggy /boot/kernel/kernel: Copyright (c) 1992-2001 The FreeBSD Project.
Sep  8 23:39:39 boggy /boot/kernel/kernel: Copyright (c) 1992-2001 The FreeBSD Project.

Finally I found this evening this host stopping after the failure of fsck,
prompting

Enter full pathname of shell or RETURN for /bin/sh:

The solution was 'unset acpi_load'. :(
-- 
NAKAJI Hiroyuki

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Recent -current breaks console probing on dell notebook?

[Robert Watson]

On Mon, 3 Sep 2001, Kazutaka YOKOTA wrote:

 Until yesterday, I was running -CURRENT from around July 4th on my
 notebook, given that I was travelling and unwilling to break my means of
 giving presentations on my trip :-).  Yesterday, I decided to upgrade, and
 built kernel/world.  The userland stuff appears to work fine, but
 interestingly, my kernel seems not to probe the console, and instead, use
 the serial console.  The boot loader does not have this problem, and sees
 the console fine.  The symptoms are that as the kernel loads (spin spin) 
 after the boot loader, it ceases spinning, the cursor changes to a block,
 
 This means that the video card is initialized Ok...

Although eventually the display will turn itself off due to lack of
keyboard activity.

 and after a delay for hardware probes (tc), the login prompt comes up but
 
 syscons is working and providing /dev/ttyv%d...

Now that I'm back in my office, I can actually log into the machine
remotely fine, and cat to /dev/ttyv0 to generate output on the display.
/dev/console does not generate output on the display, however.

 without the ability to type.  
 
 Umm, the keyboard is not available...

dmesg on the box over the network demonstrates that while sc0 is probed
with a vga display, the keyboard is not probed:

sc0: System console on isa0
sc0: VGA 16 virtual consoles, flags=0x0
vga0: Generic ISA VGA at port 0x3c0-0x3df iomem 0xa-0xb on isa0
unknown: PNP0b00 can't assign resources

I've attached a diff between the dmesg's.  The old ones were pre-ACPI and
a number of other changes, so the diff may or may not be all that useful.

 Unfortunately, I don't have a box with me I
 can use as a serial console, so I can't attempt to see what it did or
 didn't probe successfully, just that things got that far.  When I get home
 tomorrow, I'll attempt to debug it, but was wondering if anyone else had
 experienced this, or could point me at any commits that might potentially
 impact this. 
 
 Can you login to your notebook via network? As the loader seems working,
 you can boot the machine with bootverbose set, and can get dmesg output
 if you are able to login via network.

Ok, diff attached.  I'm going on travel again, so am backing out to the
previous kernel again.  Interestingly, when I did the following:

  unload kernel
  load /boot/kernel.bad/kernel
  boot -s

it booted to multi-user mode.

I tried this with both my old device.hints from a while back, and a new
empty device.hints.

Robert N M Watson FreeBSD Core Team, TrustedBSD Project
[EMAIL PROTECTED]  NAI Labs, Safeport Network Services



--- /tmp/boot.1 Sun Sep  9 11:11:48 2001
+++ /tmp/boot.2 Sun Sep  9 11:12:04 2001
@@ -1,15 +1,15 @@
 Copyright (c) 1992-2001 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: Wed Jul  4 22:17:32 EDT 2001
-rwatson@paprika:/mnt/obj/usr/src/sys/GENERIC
+FreeBSD 5.0-CURRENT #0: Sun Sep  2 10:52:50 EDT 2001
+rwatson@paprika:/usr/obj/usr/src/sys/GENERIC
 Timecounter i8254  frequency 1193182 Hz
 CPU: Pentium III/Pentium III Xeon/Celeron (701.60-MHz 686-class CPU)
   Origin = GenuineIntel  Id = 0x68a  Stepping = 10
   
Features=0x383f9ffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE

 real memory  = 536788992 (524208K bytes)
-avail memory = 517382144 (505256K bytes)
-Preloaded elf kernel kernel at 0xc051.
+avail memory = 517279744 (505156K bytes)
+Preloaded elf kernel kernel at 0xc052e000.
 Pentium Pro MTRR support enabled
 WARNING: Driver mistake: destroy_dev on 154/0
 Using $PIR table, 9 entries at 0xc00fbd80
@@ -23,12 +23,10 @@
 pci1: PCI bus on pcib1
 pci1: display, VGA at 0.0 (no driver attached)
 pcic0: TI PCI-1420 PCI-CardBus Bridge irq 11 at device 3.0 on pci0
-pcic0: Memory mapped device, will work.
 pcic0: PCI Memory allocated: 0x4400
 pcic0: TI12XX PCI Config Reg: [ring enable][speaker enable][pci only]
 pccard0: PC Card bus (classic) on pcic0
 pcic1: TI PCI-1420 PCI-CardBus Bridge irq 11 at device 3.1 on pci0
-pcic1: Memory mapped device, will work.
 pcic1: PCI Memory allocated: 0x44001000
 pcic1: TI12XX PCI Config Reg: [ring enable][speaker enable][pci only]
 pccard1: PC Card bus (classic) on pcic1
@@ -51,48 +49,20 @@
 ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 pci0: simple comms at 16.1 (no driver attached)
 orm0: Option ROMs at iomem 
0xc-0xc,0xd-0xd07ff,0xd0800-0xd0fff,0xd1000-0xd17ff,0xd1800-0xd1fff,0xd2000-0xd27ff,0xd2800-0xd2fff,0xd3000-0xd37ff,0xd3800-0xd3fff
 on isa0
-fdc0: NEC 72065B or clone at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
-fdc0: FIFO enabled, 8 bytes threshold
-fd0: 1440-KB 3.5 drive on fdc0 drive 0
-atkbdc0: Keyboard controller (i8042) at port 0x60,0x64 on isa0
-atkbd0: AT Keyboard flags 0x1 irq 1 on atkbdc0
-kbd0 at atkbd0
-psm0: PS/2 

New ACPI dangerous false devices

[Andrey A. Chernov]

With new ACPI and my ASUS TUSL2-C I got following false devices
configured:

sio1: configured irq 3 not in bitmap of probed irqs 0
sio1 port 0-0x7 irq 3 on acpi0
sio1: type 8250

(I disable sio1 in BIOS, it must not assign irq 3 here)

sc1: System console on isa0
sc1: MDA 16 virtual consoles, flags=0x0

(I have no sc1 or MDA)

sio1 maked by ACPI is dangerous ineed because when try to write something
to /dev/cuaa1 I got system lockup. Please do something with it. 

Also I got lots of:

fdc1: cannot reserve I/O port range (6 ports)
ppc1: cannot reserve I/O port range

I don't think they are dangerous because no devices created.

-- 
Andrey A. Chernov
http://ache.pp.ru/

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: boot() called on cpu #1 - hang

[Michael Class]

Hello Tor,

thank you for your quick response, unfortunately your patch did
not fix the problem.

I have now tested a little bit more with the following sequence:

  boot machine to single-user
  reboot

I did this more then 10 times. It now got stuck every time
Approx. 8 time with

  boot() called on cpu #1
  W

And 3 times with

  boot() called on cpu #0
  Wa

or

  boot() called on cpu #0
  Waiting (max

It looks to me that the kernel-printf gets somehow stuck.

Michael


On Sun, 9 Sep 2001 [EMAIL PROTECTED] wrote:

  Hello,
 
  on a 5.0-current i386-SMP system of today I am still getting on about
  every second reboot the message:
 
  boot() called on cpu #1
  W

 Try applying the enclosed patch.

 - Tor Egge




-
michael class, viktor-renner str. 39, 72074 tuebingen, frg
E-Mail: [EMAIL PROTECTED]
 Phone: +49 7031 14-3707 (work) +49 7071 81950 (private)
-


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

problems with libkvm and sysctl

[chrisw]

CONTEXT:

I'm writing a clone of pgrep(1) (part of Solaris) for FreeBSD 
5.0-CURRENT.  Similar to FreeBSD's killall, pgrep matches a pattern 
against either the executable associated with each process or each 
process's command line arguments.  I have tried using both sysctl and 
kvm to do this and have run into problems with each:

The snippet below works, except that for each non-zero kp[n].ki_args I 
find that
ki_args is an invalid pointer and that dereferencing it to access 
arguments to
process n results in a bus error.

   size_t len;
   int mib[3] = { CTL_KERN, KERN_PROC, KERN_PROC_ALL };

   if( sysctl( mib, 3, NULL, len, NULL, 0 )  0 )
 {
   perror( sysctl failed );
   return( -1 );
 }

   assert( kp = malloc( len ) );

   if( sysctl( mib, 3, kp, len, NULL, 0 )  0 )
 {
   perror( sysctl failed );
   return( -1 );
 }

That failing, I fell back on libkvm using this snippet:

   if( ( kern = kvm_open( NULL, NULL, NULL, O_RDONLY,
  kvm_open failed ) ) == NULL )
 {
   exit( 1 );
 }

and found that the resulting executable fails on kvm_open:

$ pgrep foo
kvm_open failed: /dev/mem: Invalid argument

The same open works on 4.1.1-STABLE with the same device file /dev/mem 
present.

Am I doing something obviously wrong, or are these known limitations of 
the proc info interfaces at this time?

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

acpi.ko

[Dag-Erling Smorgrav]

Why does the boot loader automatically load acpi.ko at boot time, even
though I have no loader.conf, and do not have device acpica in my
kernel?  The ACPI driver causes the clock to run at double rate, so I
there is absolutely no way I will run it on this machine if I can help
it.

DES
-- 
Dag-Erling Smorgrav - [EMAIL PROTECTED]

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

cp in INSTALLTMP?

[Christian Weisgerber]

I don't know why nobody else seems to be seeing this, but cp is
used several times during installworld, which consequently fails
for me unless cp is added to INSTALLTMP.

...
=== gnu/lib/libreadline/history
install -c -o root -g wheel -m 444   libhistory.a /usr/lib
install -c -o root -g wheel -m 444   libhistory_p.a /usr/lib
install -c -s -o root -g wheel -m 444 libhistory.so.4 /usr/lib
ln -sf libhistory.so.4 /usr/lib/libhistory.so
cp /usr/src/gnu/lib/libreadline/history/../../../../contrib/libreadline/doc/history.3 
rlhistory.3
install -c -o root -g wheel -m 444 rlhistory.3.gz  /usr/share/man/man3
...
=== gnu/usr.bin/cvs/contrib
...
cp /usr/src/gnu/usr.bin/cvs/contrib/../../../../contrib/cvs/contrib/rcs2log.sh rcs2log
install -c -o root  -g wheel -m 555   rcs2log /usr/share/examples/cvs/contrib/rcs2log
...
=== gnu/usr.bin/perl/library/re
rm -f re_exec.c
cp ../../regexec.c re_exec.c
cc -c  -fno-strict-aliasing -DAPPLLIB_EXP=/usr/libdata/perl/BSDPAN 
-DVERSION=\0.02\  -DXS_VERSION=\0.02\ -DPIC -fpic 
-I/home/obj/usr/src/gnu/usr.bin/perl/library/re -I/usr/obj/usr/src/alpha/usr/include 
re_exec.c
rm -f re_comp.c
cp ../../regcomp.c re_comp.c
cc -c  -fno-strict-aliasing -DAPPLLIB_EXP=/usr/libdata/perl/BSDPAN 
-DVERSION=\0.02\  -DXS_VERSION=\0.02\ -DPIC -fpic -I/home/obj/usr/src/gnu/usr.bin 
/perl/library/re -I/usr/obj/usr/src/alpha/usr/include re_comp.c
...
=== gnu/usr.bin/perl/pod/pod2man
install -c  -o root -g wheel -m 555   pod2man /usr/bin
cp -p 
/usr/src/gnu/usr.bin/perl/pod/pod2man/../../../../../contrib/perl5/pod/pod2man.PL 
pod2man.PL
...

-- 
Christian naddy Weisgerber  [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: Awright, who's the funny bunny?

[Bruce Evans]

[wrong mailing list [EMAIL PROTECTED] changed to [EMAIL PROTECTED]]

On 9 Sep 2001, Dag-Erling Smorgrav wrote:

 Nice smiley face, but try to align it better next time.  Looks like
 the Linuxulator is a goner again, btw:

 panic: recurse

 syncing disks... \\|/  \\|/
 @'/ .. \\`@
 /_| \\__/ |_\\
\\__U_/

Recursive panics don't work right.  boot() normally prints a newline after
syncing disks..., but not if sync() panics recursively.

 panic: bremfree: bp 0xcd04f5a0 not locked
 Uptime: 5h25m26s

 dumping to dev ad1b, offset 7340064
 dump ata1: resetting devices .. done
 511 510 509 508 507 506 505 504 503 502 501 500 499 498 497 496 495 494 493 492 491 
490 489 488 487 486 485 484 483 482 481 480 479 478 477 476 475 474 473 472 471 470 
469 468 467 466 465 464 463 462 461 460 459 458 457 456 455 454 453 452 451 450 449 
448 447 446 445 444 443 442 441 440 439 438 437 436 435 434 433 432 431 430 429 428 
427 426 425 424 423 422 421 420 419 418 417 416 415 414 413 412 411 410 409 408 407 
406 405 404 403 402 401 400 399 398 397 396 395 394 393 392 391 390 389 388 387 386 
385 384 383 382 381 380 379 378 377 376 375 374 373 372 371 370 369 368 367 366 365 
364 363 [CTRL-C to abort] 362 361 360 359 358 357 [CTRL-C to abort] 356 355 354 353 
352 351 350 349 348 347 346 345 344 343 342 341 340 339 338 337 336 335 334 333 332 
331 330 329 328 327 326 325 324 323 322 321 320 319 318 317 316 315 314 313 312 311 
310 309 308 307 306 305 304 303 302 301 300 299 298 297 296 295 294 293 292 291 290 
289 288 287 286 285 284 283 282 281 280 279 278 277 276 275 274 2!
!
  73 272 271 270 269 268 267 266 265 264 263 262 261 260 259 258 257 256 255 254 253 
252 251 250 249 248 247 246 245 244 243 242 241 240 239 238 237 236 235 234 233 232 
231 230 229 228 227 226 225 224 223 222 221 220 219 218 217 216 215 214 213 212 211 
210 209 208 207 206 205 204 203 202 201 200 199 198 197 196 195 194 193 192 191 190 
189 188 187 186 185 184 183 182 181 180 179 178 177 176 175 174 173 172 171 170 169 
168 167 166 165 164 163 162 161 160 159 158 157 156 155 154 153 152 151 150 149 148 
147 146 145 144 143 142 141 140 139 138 137 136 135 134 133 132 131 130 129 128 127 
126 125 124 123 122 121 120 119 [CTRL-C to abort] 118 [CTRL-C to abort] 117 116 115 
114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 [CTRL-C to abort] 99 98 
97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 
69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 
41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20!
!
   19 18 17 16 15 14 13 12 11 10 9 8 [CTRL-C to abort] 7 6 5 [CTRL-C to
 abort] 4 [CTRL-C to abort] 3 2 [CTRL-C to abort] 1 0 [CTRL-C to abort]

Did you want to abort?  I really hate the change that stopped the space
bar aborting.

 ---
 ...
 #8  0xc01a529d in panic (fmt=0xc02a9e88 recurse)
 at ../../../kern/kern_shutdown.c:657
 #9  0xc01c55c8 in witness_lock (lock=0xda11373c, flags=8,
 file=0xc02c3380 ../../../i386/linux/linux_sysvec.c, line=387)
 at ../../../kern/subr_witness.c:543
 #10 0xc02807b0 in linux_sendsig (catcher=0x286f2e10, sig=32, mask={
   sigmask_l_ = optimized out or zero length, sigmask = 0xda14ff1c,
   sigmask_r_ = 0xda14fef8 }, code=0)
 at ../../../i386/linux/linux_sysvec.c:387
 #11 0xc01aaaea in postsig (sig=32) at ../../../kern/kern_sig.c:1694

This seems to be because:

  1.85  +3 -3  src/sys/i386/linux/linux_sysvec.c

missed changing linux_sendsig().  It only changed linux_rt_sendsig().

Bruce


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

How can I turn off acpi 100%?

[Edwin Culp]

I hadn't rebooted my laptop since Aug 28 although I have been building world
and a new kernel daily.  I thought today would be a good day to see how acpi
was comming.  Mistake.  It comes up fine, I think because all I can see are:

acpi_cmbat0: bif size changed 0 

at what looks like several per second.  In single user I am getting:

acpi-ec0: evaluation of CPE query method _Q3F failed - AE_NOT_FOUND

at the rate of one every 10 seconds more or less.  So basically my laptop
is useless right now.  

It is a Compaq 1700 PIII 850Mhz, 256MB, 30GB.  I haven't had a problem since
July.  

How can I turn all this off?  Can I send any info that might help someone else?

Thanks,

ed




---

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: How can I turn off acpi 100%?

[Edwin Culp]

I just realized that booting an old kernel doesn't stop the errors.  It that
the case or am I now doing something totally stupid in addition to having
decided to reboot my laptop today?  :-)

Thanks,

ed

Quoting Edwin Culp [EMAIL PROTECTED]:

| 
| I hadn't rebooted my laptop since Aug 28 although I have been building
| world
| and a new kernel daily.  I thought today would be a good day to see how
| acpi
| was comming.  Mistake.  It comes up fine, I think because all I can see
| are:
| 
| acpi_cmbat0: bif size changed 0 
| 
| at what looks like several per second.  In single user I am getting:
| 
| acpi-ec0: evaluation of CPE query method _Q3F failed - AE_NOT_FOUND
| 
| at the rate of one every 10 seconds more or less.  So basically my laptop
| is useless right now.  
| 
| It is a Compaq 1700 PIII 850Mhz, 256MB, 30GB.  I haven't had a problem
| since
| July.  
| 
| How can I turn all this off?  Can I send any info that might help someone
| else?
| 
| Thanks,
| 
| ed
| 
| 
| 
| 
| ---
| 
| 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: How can I turn off acpi 100%?

[Edwin Culp]

David,

You are a life saver, as you so often are.  I am copying this to the 
developers so they can let me know what they need because this Compaq
seems to be a mess.

I'll add this to my hints and see what happens.

Thanks again,

ed

Quoting David Wolfskill [EMAIL PROTECTED]:

| Per Mike Smith's message of Wed, 29 Aug 2001 19:58:59 -0700:
| 
|  - Help! ACPI crashes my system.
| 
| You can disable ACPI by unsetting the 'acpi_load' variable in the
| loader (for temporary testing) or by setting
| 
| hint.acpi.0.disable=1
| 
| in /boot/device.hints.  If you find that you need to do this, please
| let the FreeBSD ACPI developers ([EMAIL PROTECTED]) know so that
| we can investigate the problem.
| 
| 
| Cheers,
| david
| -- 
| David H. Wolfskill[EMAIL PROTECTED]
| As a computing professional, I believe it would be unethical for me to
| advise, recommend, or support the use (save possibly for personal
| amusement) of any product that is or depends on any Microsoft product.
| 




---

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: cp in INSTALLTMP?

[Bruce Evans]

On Sun, 9 Sep 2001, Christian Weisgerber wrote:

 I don't know why nobody else seems to be seeing this, but cp is

This might be caused by having the sources and objects on different
machines with inconsistent clocks.

 used several times during installworld, which consequently fails
 for me unless cp is added to INSTALLTMP.

 ...
 === gnu/lib/libreadline/history
 install -c -o root -g wheel -m 444   libhistory.a /usr/lib
 install -c -o root -g wheel -m 444   libhistory_p.a /usr/lib
 install -c -s -o root -g wheel -m 444 libhistory.so.4 /usr/lib
 ln -sf libhistory.so.4 /usr/lib/libhistory.so
 cp 
/usr/src/gnu/lib/libreadline/history/../../../../contrib/libreadline/doc/history.3 
rlhistory.3

This is caused by a bug in bsd.man.mk.  It creates rlhistory.3 at
install time if certain files are out of date.  This also breaks
installing from read-only object trees.

 install -c -o root -g wheel -m 444 rlhistory.3.gz  /usr/share/man/man3

Note that it doesn't claim to rebuild rlhistory.3.gz from rlhistory.3.
I think it really doesn't create it.  This is correct -- the install should
just fail if rlhistory.3.gz doesn't exist.

 ...
 === gnu/usr.bin/perl/library/re
 rm -f re_exec.c
 cp ../../regexec.c re_exec.c
 cc -c  -fno-strict-aliasing -DAPPLLIB_EXP=/usr/libdata/perl/BSDPAN 
-DVERSION=\0.02\  -DXS_VERSION=\0.02\ -DPIC -fpic 
-I/home/obj/usr/src/gnu/usr.bin/perl/library/re -I/usr/obj/usr/src/alpha/usr/include 
re_exec.c
 rm -f re_comp.c
 cp ../../regcomp.c re_comp.c
 cc -c  -fno-strict-aliasing -DAPPLLIB_EXP=/usr/libdata/perl/BSDPAN 
-DVERSION=\0.02\  -DXS_VERSION=\0.02\ -DPIC -fpic -I/home/obj/usr/src/gnu/usr.bin 
/perl/library/re -I/usr/obj/usr/src/alpha/usr/include re_comp.c

Does all this happen at install time?  perl sometimes builds a lot at
install time, but I don't remember seeing it in this directory.

 ...
 === gnu/usr.bin/perl/pod/pod2man
 install -c  -o root -g wheel -m 555   pod2man /usr/bin
 cp -p 
/usr/src/gnu/usr.bin/perl/pod/pod2man/../../../../../contrib/perl5/pod/pod2man.PL 
pod2man.PL
 ...

This is clearly due to a bug in one of the perl Makefiles.

Bruce


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: cp in INSTALLTMP?

[Christian Weisgerber]

Bruce Evans [EMAIL PROTECTED] wrote:

  I don't know why nobody else seems to be seeing this, but cp is
 
 This might be caused by having the sources and objects on different
 machines with inconsistent clocks.

No, it's all local on a single machine.
FWIW, I'm on alpha.

  === gnu/usr.bin/perl/library/re
 [...]
 Does all this happen at install time?

Yes.  make installworld from yesterday.

-- 
Christian naddy Weisgerber  [EMAIL PROTECTED]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: acpi.ko

[Mike Smith]

 Why does the boot loader automatically load acpi.ko at boot time, even
 though I have no loader.conf, and do not have device acpica in my
 kernel?  The ACPI driver causes the clock to run at double rate, so I
 there is absolutely no way I will run it on this machine if I can help
 it.

Because your system claims ACPI support.

Your attitude is unproductive; a) the acpi(4) manpage tells you how to 
turn off the ACPI timecounter, and b) once I get some time to work on it, 
the timecounter will probably be fixed to deal (one way or another) with 
your board.

I am assuming you're using an ALi chipset of some sort?  Your bugreport 
dosn't seem to indicate that.  If all you're having trouble with is the 
timecounter, turn it off.


-- 
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also.  But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view.  [Dr. Fritz Todt]
   V I C T O R Y   N O T   V E N G E A N C E



To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

Re: cp in INSTALLTMP?

[Mike Barcroft]

Christian Weisgerber [EMAIL PROTECTED] writes:
 Bruce Evans [EMAIL PROTECTED] wrote:
 
   I don't know why nobody else seems to be seeing this, but cp is
  
  This might be caused by having the sources and objects on different
  machines with inconsistent clocks.
 
 No, it's all local on a single machine.
 FWIW, I'm on alpha.

I'm seeing this on my alpha as well.  I believe it started about a week
or two ago.

As a temporary solution I've been adding cp to
/usr/obj/usr/src/alpha/usr/bin and using chflags to set the schg flag.
This has to be done once a make world has started.

Best regards,
Mike Barcroft

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

LINT broken?

[Kris Kennaway]

Is anyone else seeing this?  This was build failure of a -current LINT
under RELENG_4.  As far as I can tell I'm up to date.

Kris

cc -c -O -pipe -march=pentium -march=pentiumpro -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline 
-Wcast-qual  -fformat-extensions -ansi  -nostdinc -I-  -I. -I../../.. -I../../../dev 
-I../../../contrib/dev/acpica -I../../../contrib/ipfilter -I../../../../include 
-DGPROF -DGPROF4 -DGUPROF -D_KERNEL -include opt_global.h -elf -malign-functions=4 
-fno-builtin -mpreferred-stack-boundary=2 -pg -mprofiler-epilogue 
../../../i386/linux/linux_sysvec.c
../../../i386/linux/linux_sysvec.c: In function `linux_rt_sendsig':
../../../i386/linux/linux_sysvec.c:223: `LINUX_SYS_linux_rt_sendsig' undeclared (first 
use in this function)
../../../i386/linux/linux_sysvec.c:223: (Each undeclared identifier is reported only 
once
../../../i386/linux/linux_sysvec.c:223: for each function it appears in.)
../../../i386/linux/linux_sysvec.c: In function `linux_sendsig':
../../../i386/linux/linux_sysvec.c:379: `LINUX_SYS_linux_sendsig' undeclared (first 
use in this function)
*** Error code 1


 PGP signature

Re: LINT broken?

[David W. Chapman Jr.]

On Sun, Sep 09, 2001 at 09:01:50PM -0700, Kris Kennaway wrote:
 Is anyone else seeing this?  This was build failure of a -current LINT
 under RELENG_4.  As far as I can tell I'm up to date.
 
 Kris
 
 cc -c -O -pipe -march=pentium -march=pentiumpro -Wall -Wredundant-decls 
-Wnested-externs -Wstrict-prototypes  -Wmissing-prototypes -Wpointer-arith -Winline 
-Wcast-qual  -fformat-extensions -ansi  -nostdinc -I-  -I. -I../../.. -I../../../dev 
-I../../../contrib/dev/acpica -I../../../contrib/ipfilter -I../../../../include 
-DGPROF -DGPROF4 -DGUPROF -D_KERNEL -include opt_global.h -elf -malign-functions=4 
-fno-builtin -mpreferred-stack-boundary=2 -pg -mprofiler-epilogue 
../../../i386/linux/linux_sysvec.c
 ../../../i386/linux/linux_sysvec.c: In function `linux_rt_sendsig':
 ../../../i386/linux/linux_sysvec.c:223: `LINUX_SYS_linux_rt_sendsig' undeclared 
(first use in this function)
 ../../../i386/linux/linux_sysvec.c:223: (Each undeclared identifier is reported only 
once
 ../../../i386/linux/linux_sysvec.c:223: for each function it appears in.)
 ../../../i386/linux/linux_sysvec.c: In function `linux_sendsig':
 ../../../i386/linux/linux_sysvec.c:379: `LINUX_SYS_linux_sendsig' undeclared (first 
use in this function)
 *** Error code 1
 
As you already know, I got this too, I think it was supposed to be 
fixed earlier today, but the cvsup problems of today might be hiding 
the update somewhere(just speculating).


-- 
David W. Chapman Jr.
[EMAIL PROTECTED]   Raintree Network Services, Inc. www.inethouston.net
[EMAIL PROTECTED]   FreeBSD Committer www.FreeBSD.org

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message