Fatal trap 12 with recent current (notebook with network pc-card)
I have Mitac 7020 notebook with Apollo 10/100M Fast Ethernet PC Card. Today i cvsuped recent current and now kernel panics ufter card insertion with the folowing message: pccard: card inserted, slot 0 date time mobile pccardd[186]: Card Dual Speed(10/100 PC Card) [1.0] [ ] matched Dual Speed (/10/100( Port Attached)? PC Card/) [(null)] [(null)] Fatal trap 12: page fault while in kernel mode fault virtual address = 0x3c fault core = supervisor write, page not present instruction pointer = 0x8:0xc01cceb1 stack pointer = 0x10:0xc698ab00 frame pointer = 0x10:0xc698ab00 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 = 186 (pccardd) kernel: type 12 trap, code=0 Stopped at device_set_flags+0x9: movl%eax,0x3c(%edx) kernel config is: # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # #http://www.FreeBSD.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the NOTES configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in NOTES. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.313 2001/07/02 21:01:48 brooks Exp $ machine i386 cpu I686_CPU ident NOTEBOOK maxusers32 #optionsVISUAL_USERCONFIG #visual boot -c editor #To statically compile in device wiring instead of /boot/device.hints #hints GENERIC.hints #Default places to look for devices. makeoptions DEBUG=-g#Build kernel with gdb(1) debug symbols #optionsMATH_EMULATE#Support for x87 emulation options INET#InterNETworking options INET6 #IPv6 communications protocols options FFS #Berkeley Fast Filesystem options SOFTUPDATES #Enable FFS soft updates support #optionsMD_ROOT #MD is a potential root device options NFSCLIENT #Network Filesystem Client options NFSSERVER #Network Filesystem Server #optionsNFS_ROOT#NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000#Delay (in ms) before probing SCSI options UCONSOLE#Allow users to grab the console #optionsUSERCONFIG #boot -c editor #optionsVISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B#Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options KBD_INSTALL_CDEV# install a CDEV entry in /dev # Debugging for use in -current options DDB options INVARIANTS options INVARIANT_SUPPORT options WITNESS # To make an SMP kernel, the next two are needed #optionsSMP # Symmetric MultiProcessor Kernel #optionsAPIC_IO # Symmetric (APIC) I/O device isa #device eisa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc 1 # At keyboard controller device atkbd # at keyboard device psm # psm mouse device vga # VGA screen # splash screen/screen saver device splash # syscons is the default console driver, resembling an SCO console device sc 1 # Enable this for the pcvt (VT220 compatible) console driver #device vt #optionsXSERVER # support for X
No Subject
? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
kernel panic in getnewvnode
The filesystem with the kernel that had debugging symbols was fried. All I have is below, but I can try to crash the system tonight, if needed, with a (new) debuggable kernel. -- Steve (kgdb) bt #0 0xc017fd9e in dumpsys () #1 0xc017fb8b in boot () #2 0xc017ffbd in panic () #3 0xc01ac62b in bdwrite () #4 0xc01df3a5 in ffs_update () #5 0xc01ebd06 in ffs_fsync () #6 0xc01ea506 in ffs_sync () #7 0xc01b7f2d in sync () #8 0xc017f828 in boot () #9 0xc017ffbd in panic () #10 0xc0179332 in free () #11 0xc01af803 in cache_zap () #12 0xc01afd0b in cache_purge () #13 0xc01b43cc in getnewvnode () #14 0xc01ea816 in ffs_vget () #15 0xc01ed0e1 in ufs_lookup () #16 0xc01f1d15 in ufs_vnoperate () #17 0xc01b0026 in vfs_cache_lookup () #18 0xc01f1d15 in ufs_vnoperate () #19 0xc01b3671 in lookup () #20 0xc01b316c in namei () #21 0xc01b9d35 in lstat () #22 0xc02235df in syscall () #23 0xc0217c9d in syscall_with_err_pushed () #24 0x280a753d in ?? () #25 0x280a6dde in ?? () #26 0x804972e in ?? () #27 0x804b728 in ?? () #28 0x80493c1 in ?? () To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
RE: Fatal trap 12 with recent current (notebook with network pc-
On 31-Oct-01 Ilmar S. Habibulin wrote: I have Mitac 7020 notebook with Apollo 10/100M Fast Ethernet PC Card. Today i cvsuped recent current and now kernel panics ufter card insertion with the folowing message: pccard: card inserted, slot 0 date time mobile pccardd[186]: Card Dual Speed(10/100 PC Card) [1.0] [ ] matched Dual Speed (/10/100( Port Attached)? PC Card/) [(null)] [(null)] Fatal trap 12: page fault while in kernel mode fault virtual address = 0x3c fault core = supervisor write, page not present instruction pointer = 0x8:0xc01cceb1 stack pointer = 0x10:0xc698ab00 frame pointer = 0x10:0xc698ab00 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 = 186 (pccardd) kernel: type 12 trap, code=0 Stopped at device_set_flags+0x9: movl%eax,0x3c(%edx) kernel config is: Please provide a backtrace. (trace in ddb should do the trick) -- John Baldwin [EMAIL PROTECTED] -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc Power Users Use the Power to Serve! - http://www.FreeBSD.org/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
weird -current gdb/gcc(?) problem
Hackers,
first of all i want to apologize for posting this in -current.
this should probably go into -questions.
i have some weird problem. i have cvsup'ed and installed -current
yesterday. i have attached script(1) output. quick search came up
with nothing.
did i miss anything?
thanks
max
Script started on Wed Oct 31 09:49:56 2001
beetle% uname -a
FreeBSD beetle 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Oct 30 13:23:19 PST 2001
root@beetle:/usr/obj/usr/src/sys/BEETLE i386
beetle%
beetle%
beetle% cat c2.sh
#!/bin/sh -x
gcc -v
ld -v
ar -V
rm a.out libtest.a lib.o
cat lib.c
cat prog1.c
gcc -Wall -g -c -o lib.o lib.c
ar cr libtest.a lib.o
gcc -Wall -g prog1.c -L. -ltest
./a.out
gdb a.out
beetle%
beetle%
beetle% ./c2.sh
+ gcc -v
Using builtin specs.
gcc version 2.95.3 20010315 (release)
+ ld -v
GNU ld version 2.11.2 20010719 [FreeBSD] (with BFD 2.11.2 20010719 [FreeBSD])
+ ar -V
GNU ar 2.11.2 20010719 [FreeBSD]
Copyright 1997, 98, 99, 2000, 2001 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License. This program has absolutely no warranty.
+ rm a.out libtest.a lib.o
rm: libtest.a: No such file or directory
rm: lib.o: No such file or directory
+ cat lib.c
#include stdio.h
int
foo(int i, short s, char c, char *str)
{
printf(%d, %d, %d, %s\n, i, s, c, str);
return (0);
}
+ cat prog1.c
#include stdio.h
int foo (int, short, char, char *);
int
main(void)
{
return (foo(1, 2, '3', test));
}
int
foo(int i, short s, char c, char *str)
{
printf(%d, %d, %d, %s\n, i, s, c, str);
return (0);
}
+ gcc -Wall -g -c -o lib.o lib.c
+ ar cr libtest.a lib.o
+ gcc -Wall -g prog1.c -L. -ltest
+ ./a.out
1, 2, 51, test
+ gdb a.out
GNU gdb 4.18
Copyright 1998 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-unknown-freebsd...
(gdb) b main
Breakpoint 1 at 0x80484c6: file prog1.c, line 8.
(gdb) run
Starting program: /usr/home/max/test/a.out
Breakpoint 1, main () at prog1.c:8
8 return (foo(1, 2, '3', test));
(gdb) s
foo (i=1, s=10244, c=-54 'Ê', str=0x804855b test) at prog1.c:13
13 {
(gdb) q
The program is running. Exit anyway? (y or n) y
beetle%
beetle%
beetle%
beetle% cat c1.sh
#!/bin/sh -x
gcc -v
ld -v
rm a.out
cat prog1.c
gcc -Wall -g prog1.c
./a.out
gdb a.out
beetle%
beetle%
beetle% ./c1.sh
+ gcc -v
Using builtin specs.
gcc version 2.95.3 20010315 (release)
+ ld -v
GNU ld version 2.11.2 20010719 [FreeBSD] (with BFD 2.11.2 20010719 [FreeBSD])
+ rm a.out
+ cat prog1.c
#include stdio.h
int foo (int, short, char, char *);
int
main(void)
{
return (foo(1, 2, '3', test));
}
int
foo(int i, short s, char c, char *str)
{
printf(%d, %d, %d, %s\n, i, s, c, str);
return (0);
}
+ gcc -Wall -g prog1.c
+ ./a.out
1, 2, 51, test
+ gdb a.out
GNU gdb 4.18
Copyright 1998 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-unknown-freebsd...
(gdb) b main
Breakpoint 1 at 0x80484c6: file prog1.c, line 8.
(gdb) run
Starting program: /usr/home/max/test/a.out
Breakpoint 1, main () at prog1.c:8
8 return (foo(1, 2, '3', test));
(gdb) s
foo (i=1, s=10244, c=-54 'Ê', str=0x804855b test) at prog1.c:13
13 {
(gdb) q
The program is running. Exit anyway? (y or n) y
beetle% exit
Script done on Wed Oct 31 09:50:49 2001
Repeatable make_dev() crash during periodic daily run
Fyi: my system at home has crashed twice now at 3:01am during the periodic daily run with: WARNING: Driver mistake: repeat make_dev(da0a) I can crash it at will (did so this morning) by running periodic daily. -- Jos Backus _/ _/_/_/Santa Clara, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/_/ [EMAIL PROTECTED] _/_/ _/_/_/use Std::Disclaimer; To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Repeatable make_dev() crash during periodic daily run
Hi Poul-Henning, On Wed, Oct 31, 2001 at 07:38:56PM +0100, Poul-Henning Kamp wrote: Make sure you have rev 1.46 of sys/kern/subr_disk.c and 1.100 of sys/kern/kern_conf.c In other words: the latest. I know, and I do. lizzy:/sys/kern% uname -a FreeBSD lizzy.bugworks.com 5.0-CURRENT FreeBSD 5.0-CURRENT #4: Tue Oct 30 21:38:06 PST 2001 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/LIZZY i386 lizzy:/sys/kern% ident subr_disk.c kern_conf.c subr_disk.c: $FreeBSD: src/sys/kern/subr_disk.c,v 1.46 2001/10/28 09:39:28 phk Exp $ kern_conf.c: $FreeBSD: src/sys/kern/kern_conf.c,v 1.100 2001/10/28 09:39:28 phk Exp $ lizzy:/sys/kern% ls -l subr_disk.c kern_conf.c -rw-r--r-- 1 root wheel 9672 Oct 28 09:23 kern_conf.c -rw-r--r-- 1 root wheel 9672 Oct 28 09:23 subr_disk.c -- Jos Backus _/ _/_/_/Santa Clara, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/_/ [EMAIL PROTECTED] _/_/ _/_/_/use Std::Disclaimer; To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Repeatable make_dev() crash during periodic daily run
In message [EMAIL PROTECTED], Jos Backus writes: Hi Poul-Henning, On Wed, Oct 31, 2001 at 07:38:56PM +0100, Poul-Henning Kamp wrote: Make sure you have rev 1.46 of sys/kern/subr_disk.c and 1.100 of sys/kern/kern_conf.c In other words: the latest. I know, and I do. OK, so far so good. Try to find the /dev catalog which does this and if possible send me a ls -l from it. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 [EMAIL PROTECTED] | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
where did smp_started go?
Kernels no build smp_started hath vanisheddeclaring it an extern volatile int smp_started; in smp.h doesn't really help. Did you intend for the actual storage to be in $ARCH/$ARCH/mp_machdep.c? -matt To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: where did smp_started go?
On Wed, Oct 31, 2001 at 12:09:10PM -0800, Matthew Jacob wrote: Kernels no build smp_started hath vanisheddeclaring it an extern volatile int smp_started; in smp.h doesn't really help. Did you intend for the actual storage to be in $ARCH/$ARCH/mp_machdep.c? No. It was a typical braino when you want to fix something too late at night too quickly :-( I reverted to change to subr_smp.c -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: where did smp_started go?
oops. can you revert i386/mp_machdep.c then? On Wed, 31 Oct 2001, Marcel Moolenaar wrote: On Wed, Oct 31, 2001 at 12:09:10PM -0800, Matthew Jacob wrote: Kernels no build smp_started hath vanisheddeclaring it an extern volatile int smp_started; in smp.h doesn't really help. Did you intend for the actual storage to be in $ARCH/$ARCH/mp_machdep.c? No. It was a typical braino when you want to fix something too late at night too quickly :-( I reverted to change to subr_smp.c -- Marcel Moolenaar USPA: A-39004 [EMAIL PROTECTED] 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
[Fwd: weird -current gdb/gcc(?) problem]
Alexander N. Kabaev wrote: What is the problem exactly? It is hard to guess that from the information you posted. foo (i=1, s=10244, c=-54 'J', str=0x804855b test) at prog1.c:13 Is that what bothers you? It happens because your code is compiled with no optimization, and that causes gcc to allocate temporary backing storage for all parameters in the function foo. When you type an 's' command to step into the foo function from main, gcc stops immediately after function stack frame has been initialized but before parameters have been copied into their respective temporary locations. yes, but i posted wrong output :( try to do the same but use -ggdb instead of -g switch. even if you step info function some funny things happen. you can try to do both -O2 -ggdb vs. -ggdb only. thanks, max
Re: weird -current gdb/gcc(?) problem
Maksim Yevmenkin [EMAIL PROTECTED] wrote: i have some weird problem. Well, it would have been nice if you had told what you deemed to be the problem. ;-) I can't find any problem at all... Breakpoint 1, main () at prog1.c:8 8 return (foo(1, 2, '3', test)); (gdb) s foo (i=1, s=10244, c=-54 'Ê', str=0x804855b test) at prog1.c:13 If you mean it should look like: foo (i=1, s=2, c=51 '3', str=0x804855b test) at prog1.c:13 here, erm, no. Your breakpoint simply hit before the function stack frame initialization was complete, so gdb displays the wrong values at that point. Just type a single `s', followed by a `where', and you'll see it will eventually get the argument list right then. -- cheers, Jorg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: weird -current gdb/gcc(?) problem
Joerg,
i have some weird problem.
Well, it would have been nice if you had told what you deemed to
be the problem. ;-) I can't find any problem at all...
Breakpoint 1, main () at prog1.c:8
8 return (foo(1, 2, '3', test));
(gdb) s
foo (i=1, s=10244, c=-54 'Ê', str=0x804855b test) at prog1.c:13
If you mean it should look like:
foo (i=1, s=2, c=51 '3', str=0x804855b test) at prog1.c:13
here, erm, no. Your breakpoint simply hit before the function stack
frame initialization was complete, so gdb displays the wrong values at
that point. Just type a single `s', followed by a `where', and you'll
see it will eventually get the argument list right then.
first of all i want to apoligize. i sent the wrong output. yes, it
does the right thing if you use -g switch, however it does not
work for me if i use -ggdb switch.
thanks,
max
Script started on Wed Oct 31 13:46:09 2001
beetle% uname -a
FreeBSD beetle 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Tue Oct 30 13:23:19 PST 2001
root@beetle:/usr/obj/usr/src/sys/BEETLE i386
beetle% cat c1.sh
#!/bin/sh -x
gcc -v
ld -v
rm a.out
cat prog1.c
gcc -Wall -ggdb prog1.c
./a.out
gdb a.out
beetle% ./c1.sh
+ gcc -v
Using builtin specs.
gcc version 2.95.3 20010315 (release)
+ ld -v
GNU ld version 2.11.2 20010719 [FreeBSD] (with BFD 2.11.2 20010719 [FreeBSD])
+ rm a.out
+ cat prog1.c
#include stdio.h
int foo (int, short, char, char *);
int
main(void)
{
return (foo(1, 2, '3', test));
}
int
foo(int i, short s, char c, char *str)
{
printf(%d, %d, %d, %s\n, i, s, c, str);
return (0);
}
+ gcc -Wall -ggdb prog1.c
+ ./a.out
1, 2, 51, test
+ gdb a.out
GNU gdb 4.18
Copyright 1998 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-unknown-freebsd...
(gdb) b main
Breakpoint 1 at 0x80484c6: file prog1.c, line 8.
(gdb) run
Starting program: /usr/home/max/test/a.out
Breakpoint 1, main () at prog1.c:8
8 return (foo(1, 2, '3', test));
(gdb) s
foo (i=671494208, s=10246, c=16 '\020', str=0x2804ca2b \203~T) at prog1.c:13
13 {
(gdb) s
14 printf(%d, %d, %d, %s\n, i, s, c, str);
(gdb) where
#0 foo (i=671494208, s=10246, c=16 '\020',
str=0x2332b Error reading address 0x2332b: Bad address) at prog1.c:14
#1 0x80484d6 in main () at prog1.c:8
(gdb) p i
$1 = 671494208
(gdb) p s
$2 = 10246
(gdb) p c
$3 = 16 '\020'
(gdb) p str
$4 = 0x2332b Error reading address 0x2332b: Bad address
(gdb) q
The program is running. Exit anyway? (y or n) y
beetle% exit
Script done on Wed Oct 31 13:46:46 2001
Re: WARNING: Driver mistake: destroy_dev on 154/0
In message [EMAIL PROTECTED] Nick Hibma writes: : Yes. I have no idea why phk has not done this. Because the asr driver maintainer has asserted a strong lock in the past and phk doesn't have an asr card. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Revert awk to one that works
Can someone revert awk to one that actually works? === usr.bin/kdump sh /usr/src/usr.bin/kdump/mkioctls /usr/obj/usr/src/i386/usr/include ioctl.c awk: newline in string #include cam/scsi/s... at source line 1 awk: newline in string #include cam/scsi/s... at source line 1 awk: newline in string #include cam/scsi/s... at source line 1 In file included from :72: /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redef ined /usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:115: warning: this is the lo cation of the previous definition cpp0: output pipe has been closed *** Error code 2 -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Revert awk to one that works
On Wed, Oct 31, 2001 at 03:16:37PM -0800, Steve Kargl wrote: Can someone revert awk to one that actually works? Why don't we look at fixing the mkioctls script instead?? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Revert awk to one that works
On Wed, Oct 31, 2001 at 04:45:58PM -0800, David O'Brien wrote: On Wed, Oct 31, 2001 at 03:16:37PM -0800, Steve Kargl wrote: Can someone revert awk to one that actually works? Why don't we look at fixing the mkioctls script instead?? That's fine. But, before pulling the switch on a major utility, it would be nice if the committer would actually test the new utility. -- Steve To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Revert awk to one that works
On Wed, Oct 31, 2001 at 04:56:18PM -0800, Steve Kargl wrote: On Wed, Oct 31, 2001 at 04:45:58PM -0800, David O'Brien wrote: On Wed, Oct 31, 2001 at 03:16:37PM -0800, Steve Kargl wrote: Can someone revert awk to one that actually works? Why don't we look at fixing the mkioctls script instead?? That's fine. But, before pulling the switch on a major utility, it would be nice if the committer would actually test the new utility. I *DID* test it with a full `make world'. By chance is this your second `make world' after the change? It seems we are using the host awk instead of the one we built. Requiring someone to do two back-to-back `make world's before a commit has never been a requirement. Some things we just find out after a commit. There isn't much we can do about that with our current practices. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Revert awk to one that works
On Wed, Oct 31, 2001 at 04:45:58PM -0800, David O'Brien wrote:
Why don't we look at fixing the mkioctls script instead??
What about this patch?
--- mkioctls.orig Wed Oct 31 17:08:33 2001
+++ mkioctlsWed Oct 31 17:13:07 2001
@@ -19,50 +19,48 @@
# Build a list of headers that have ioctls in them.
# XXX should we use an ANSI cpp?
# XXX netipx conflicts with netns (leave out netns).
-ioctl_includes=`
- cd $1
- find -s * -name '*.h' -follow |
- egrep -v '^(netns)/' |
- xargs egrep -l \
-'^#[ ]*define[ ]+[A-Za-z_][A-Za-z0-9_]*[ ]+_IO[^a-z0-9_]' |
- sed -e 's/^/#include /' -e s'/$//'
-`
-echo $ioctl_includes |
+cat 'EOT'
+/* XXX obnoxious prerequisites. */
+#define COMPAT_43
+#include sys/param.h
+#include sys/devicestat.h
+#include sys/disklabel.h
+#include sys/socket.h
+#include sys/time.h
+#include sys/tty.h
+#include net/ethernet.h
+#include net/if.h
+#include net/if_var.h
+#include net/route.h
+#include netatm/atm.h
+#include netatm/atm_if.h
+#include netatm/atm_sap.h
+#include netatm/atm_sys.h
+#include netinet/in.h
+#include netinet/ip_compat.h
+#include netinet/ip_fil.h
+#include netinet/ip_auth.h
+#include netinet/ip_nat.h
+#include netinet/ip_frag.h
+#include netinet/ip_state.h
+#include netinet/ip_mroute.h
+#include netinet6/in6_var.h
+#include netinet6/nd6.h
+#include netinet6/ip6_mroute.h
+#include stdio.h
+#include cam/cam.h
+EOT
+
+cd $1
+find -s * -name '*.h' -follow |
+ egrep -v '^(netns)/' |
+ xargs egrep -l \
+'^#[ ]*define[ ]+[A-Za-z_][A-Za-z0-9_]*[ ]+_IO[^a-z0-9_]' |
+ sed -e 's/^/#include /' -e s'/$//' |
gcc -E -I$1 -dM - |
- awk -v ioctl_includes=$ioctl_includes -v use_switch=$use_switch '
+ awk -v use_switch=$use_switch '
BEGIN {
- print /* XXX obnoxious prerequisites. */
- print #define COMPAT_43
- print #include sys/param.h
- print #include sys/devicestat.h
- print #include sys/disklabel.h
- print #include sys/socket.h
- print #include sys/time.h
- print #include sys/tty.h
- print #include net/ethernet.h
- print #include net/if.h
- print #include net/if_var.h
- print #include net/route.h
- print #include netatm/atm.h
- print #include netatm/atm_if.h
- print #include netatm/atm_sap.h
- print #include netatm/atm_sys.h
- print #include netinet/in.h
- print #include netinet/ip_compat.h
- print #include netinet/ip_fil.h
- print #include netinet/ip_auth.h
- print #include netinet/ip_nat.h
- print #include netinet/ip_frag.h
- print #include netinet/ip_state.h
- print #include netinet/ip_mroute.h
- print #include netinet6/in6_var.h
- print #include netinet6/nd6.h
- print #include netinet6/ip6_mroute.h
- print #include stdio.h
- print #include cam/cam.h
- print
- print ioctl_includes
print
print char *
print ioctlname(register_t val)
--
Jos Backus _/ _/_/_/Santa Clara, CA
_/ _/ _/
_/ _/_/_/
_/ _/ _/_/
[EMAIL PROTECTED] _/_/ _/_/_/use Std::Disclaimer;
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: Revert awk to one that works
On Wed, Oct 31, 2001 at 05:14:34PM -0800, Jos Backus wrote: On Wed, Oct 31, 2001 at 04:45:58PM -0800, David O'Brien wrote: Why don't we look at fixing the mkioctls script instead?? What about this patch? It does not work. +cat 'EOT' +/* XXX obnoxious prerequisites. */ ^^^ what should this be terminating? Or where is it's terminating ? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Revert awk to one that works
On Wed, Oct 31, 2001 at 06:12:07PM -0800, David O'Brien wrote: It does not work. Bummer. I'll look at it when I get back from dinner. +cat 'EOT' +/* XXX obnoxious prerequisites. */ ^^^ what should this be terminating? Or where is it's terminating ? Typo. Does it work better when you remove it? -- Jos Backus _/ _/_/_/Santa Clara, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/_/ [EMAIL PROTECTED] _/_/ _/_/_/use Std::Disclaimer; To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Revert awk to one that works
On Wed, 31 Oct 2001, David O'Brien wrote: On Wed, Oct 31, 2001 at 04:56:18PM -0800, Steve Kargl wrote: On Wed, Oct 31, 2001 at 04:45:58PM -0800, David O'Brien wrote: On Wed, Oct 31, 2001 at 03:16:37PM -0800, Steve Kargl wrote: Can someone revert awk to one that actually works? Why don't we look at fixing the mkioctls script instead?? That's fine. But, before pulling the switch on a major utility, it would be nice if the committer would actually test the new utility. I *DID* test it with a full `make world'. By chance is this your second `make world' after the change? It seems we are using the host awk instead of the one we built. Requiring someone to do two back-to-back `make world's before a commit has never been a requirement. Some things we just find out after a commit. Required isn't really the question. It seems like common sense to me when discussing such a frequently used build tool. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
kernel build fails in atomic.c
I got the following eariler, and thinking I was out of sync, I cvsupped everything from scratch, and still got it. --- cc -c -g -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -f format-extensions -ansi -nostdinc -I- -I. -I../../.. -I../../../dev -I../../../contrib/dev/acpica -I../../../contrib/ipfilter -I../../../ ../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 -fomit-frame-pointer ../../../i386/i386/atomic.c In file included from ../../../i386/i386/atomic.c:48: machine/atomic.h: In function `atomic_set_char': machine/atomic.h:214: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_char': machine/atomic.h:215: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_char': machine/atomic.h:216: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_char': machine/atomic.h:217: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_set_short': machine/atomic.h:219: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_short': machine/atomic.h:220: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_short': machine/atomic.h:221: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_short': machine/atomic.h:222: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_set_int': machine/atomic.h:224: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_int': machine/atomic.h:225: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_int': machine/atomic.h:226: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_int': machine/atomic.h:227: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_set_long': machine/atomic.h:229: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_clear_long': machine/atomic.h:230: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_add_long': machine/atomic.h:231: inconsistent operand constraints in an `asm' machine/atomic.h: In function `atomic_subtract_long': machine/atomic.h:232: inconsistent operand constraints in an `asm' *** Error code 1 Stop in /usr/src/sys/i386/compile/WAHOO. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! - POWER TO THE PEOPLE! - Religious fundamentalism is the biggest threat to international security that exists today. United Nations Secretary General B.B.Ghali, 1995 _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Revert awk to one that works
Doug Barton [EMAIL PROTECTED] writes: On Wed, 31 Oct 2001, David O'Brien wrote: I *DID* test it with a full `make world'. By chance is this your second `make world' after the change? It seems we are using the host awk instead of the one we built. Requiring someone to do two back-to-back `make world's before a commit has never been a requirement. Some things we just find out after a commit. Required isn't really the question. It seems like common sense to me when discussing such a frequently used build tool. I'm sure there's better things you could be doing besides lecturing David about testing his changes before committing. Not every bug can be found before committing, which is why we have a little thing called -CURRENT. Best regards, Mike Barcroft To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Revert awk to one that works
(Sigh. In my mkioctls patch I tried to get rid of the need to pass in $ioctl_includes to awk but I can't think of any way to make that work. Oh well. Glad it works now.) -- Jos Backus _/ _/_/_/Santa Clara, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/_/ [EMAIL PROTECTED] _/_/ _/_/_/use Std::Disclaimer; To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Revert awk to one that works
On Wed, 31 Oct 2001, Mike Barcroft wrote: Doug Barton [EMAIL PROTECTED] writes: On Wed, 31 Oct 2001, David O'Brien wrote: I *DID* test it with a full `make world'. By chance is this your second `make world' after the change? It seems we are using the host awk instead of the one we built. Requiring someone to do two back-to-back `make world's before a commit has never been a requirement. Some things we just find out after a commit. Required isn't really the question. It seems like common sense to me when discussing such a frequently used build tool. I'm sure there's better things you could be doing besides lecturing David about testing his changes before committing. Not every bug can be found before committing, which is why we have a little thing called -CURRENT. A) Two sentences isn't a lecture. B) We have a little thing called -current to shake out the non-obvious bugs that still exist after all reasonable testing has already occurred. If you're not familiar with the arguments about how much valuable developer time is wasted due to insufficiently tested changes, check the archives. My only purpose in replying was to state my objection to the sufficency of David's argument. There are a lot of things that aren't required, but are a good idea none the less. -- We will not tire, we will not falter, and we will not fail. - George W. Bush, President of the United States September 20, 2001 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Revert awk to one that works
On Wed, Oct 31, 2001 at 10:12:43PM -0800, Doug Barton wrote: My only purpose in replying was to state my objection to the sufficency of David's argument. There are a lot of things that aren't required, but are a good idea none the less. All I'll say is just about every large change I make, goes thru a `make buildworld' before committing. Only about 15% of committers seems to do this much. -- -- David ([EMAIL PROTECTED]) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: weird -current gdb/gcc(?) problem
As Maksim Yevmenkin wrote: first of all i want to apoligize. i sent the wrong output. yes, it does the right thing if you use -g switch, however it does not work for me if i use -ggdb switch. Indeed, the output generated with -ggdb looks weird. But then, it never occurred to me to use -ggdb at all. Why would one want to do this? If i get around, i'll try it on another OS and/or architecture. -- cheers, Jorg .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Revert awk to one that works
On Wed, 31 Oct 2001, David O'Brien wrote: On Wed, Oct 31, 2001 at 10:12:43PM -0800, Doug Barton wrote: My only purpose in replying was to state my objection to the sufficency of David's argument. There are a lot of things that aren't required, but are a good idea none the less. All I'll say is just about every large change I make, goes thru a `make buildworld' before committing. Only about 15% of committers seems to do this much. Also a good point. I almost felt bad about picking on you about this. :) -- We will not tire, we will not falter, and we will not fail. - George W. Bush, President of the United States September 20, 2001 Do YOU Yahoo!? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: buildworld breakage during make depend at usr.bin/kdump
Date: Wed, 31 Oct 2001 08:34:16 -0800 (PST) From: David Wolfskill [EMAIL PROTECTED] mkdep -f .depend -a-I/usr/obj/usr/src/i386/usr/include /usr/src/usr.bin/jot/jot.c cd /usr/src/usr.bin/jot; make _EXTRADEPEND echo jot: /usr/obj/usr/src/i386/usr/lib/libc.a .depend === usr.bin/kdump sh /usr/src/usr.bin/kdump/mkioctls /usr/obj/usr/src/i386/usr/include ioctl.c awk: newline in string #include cam/scsi/s... at source line 1 ... Stop in /usr/src/usr.bin/kdump. *** Error code 1 However, in reviewing that log, I didn't see the awk complaints (awk: newline in string #include cam/scsi/s... at source line 1). Yup; that is the error message that accompanies awk's termination (from within the src/usr.bin/kdump/mkioctls script) with status 2. At this stage, I'll welcome pointers/suggestions while I do some research on my own. By breaking down the parts of the pipeline in src/usr.bin/kdump/mkioctls, it looks as if the problem is that the (shell) variable ioctl_includes is being set to a list of #include directives, one per line, such as: #include cam/scsi/scsi_pass.h #include cam/scsi/scsi_ses.h #include cam/scsi/scsi_targetio.h #include dev/ppbus/lptio.h #include dev/ppbus/ppi.h ... That shell variable is being used to set the value of a similarly-named awk variable: awk -v ioctl_includes=$ioctl_includes -v use_switch=$use_switch ' And awk does *not* seem to like having embedded newline characters in there. By generating the output to a separate file, the replacing each real newline with a C/awk/Perl representation thereof (i.e., \n), I was able to get the awk part of the pipeline to terminate with a status of 0, while generating what looks like reasonable output (though I'm hardly an expert on that). If there is a way to tell awk to quit whining and *like* the newlines, that would seem to be ideal. Failing that, I can work up some way to transmogrify the #include list so awk will like it better Am I really the only one who has seen this? 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
buildworld breakage during make depend at usr.bin/kdump
=== usr.bin/jot rm -f .depend mkdep -f .depend -a-I/usr/obj/usr/src/i386/usr/include /usr/src/usr.bin/jot/jot.c cd /usr/src/usr.bin/jot; make _EXTRADEPEND echo jot: /usr/obj/usr/src/i386/usr/lib/libc.a .depend === usr.bin/kdump sh /usr/src/usr.bin/kdump/mkioctls /usr/obj/usr/src/i386/usr/include ioctl.c awk: newline in string #include cam/scsi/s... at source line 1 awk: newline in string #include cam/scsi/s... at source line 1 awk: newline in string #include cam/scsi/s... at source line 1 In file included from :72: /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:115: warning: this is the location of the previous definition cpp0: output pipe has been closed *** Error code 2 Stop in /usr/src/usr.bin/kdump. *** Error code 1 Stop in /usr/src/usr.bin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Recent CVSup history: CVSup begin from cvsup14.freebsd.org at Sat Oct 27 03:47:00 PDT 2001 CVSup ended from cvsup14.freebsd.org at Sat Oct 27 03:53:43 PDT 2001 CVSup begin from cvsup14.freebsd.org at Sun Oct 28 03:47:00 PST 2001 CVSup ended from cvsup14.freebsd.org at Sun Oct 28 03:52:52 PST 2001 CVSup begin from cvsup14.freebsd.org at Mon Oct 29 03:47:00 PST 2001 CVSup ended from cvsup14.freebsd.org at Mon Oct 29 03:53:47 PST 2001 CVSup begin from cvsup14.freebsd.org at Tue Oct 30 03:47:00 PST 2001 CVSup ended from cvsup14.freebsd.org at Tue Oct 30 03:53:02 PST 2001 CVSup begin from cvsup14.freebsd.org at Wed Oct 31 03:47:01 PST 2001 CVSup ended from cvsup14.freebsd.org at Wed Oct 31 03:53:25 PST 2001 The whine about duplicate definitions for MDF_ACTIVE is old news -- it was certainly present in yesterday's build, which completed normally (for me), and the most recent change to either was back around 28 July (and the last change to the other was near the end of 1999). However, in reviewing that log, I didn't see the awk complaints (awk: newline in string #include cam/scsi/s... at source line 1). Changing directories to src/usr.bin/kdump manually issuing make depend re-creates the symptoms, with an additional whine about /usr/include/sys/wormio.h:102 /usr/include/sys/cdrio.h:77 each having definitions of CDRIOCBLANK. As I recall, the fact that this was noticed in usr.bin/kdump is something that isn't likely of much material value: rather, that's an area that happens to be fairly sensitive, and one of the first to get hit when something goes weird elsewhere. At this stage, I'll welcome pointers/suggestions while I do some research on my own. Thanks, 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: Clock Drift
On Tuesday 30 October 2001 06:17 pm, Dreamtime.net Inc. wrote: A while back I read a thread regarding clock drift. We are now having the same problem. Does anyone know what the remedy is for this? Thanks. Sincerely, Stephen H. Kapit I had the same problem a couple of months ago. Try adding the follwing to your kernel config: options CLK_USE_I8254_CALIBRATION options CLK_USE_TSC_CALIBRATION worked for me. Beech -- Micro$oft: Where can we make you go today? --- Beech Rintoul - IT Manager - Instructor - [EMAIL PROTECTED] /\ ASCII Ribbon Campaign | Anchorage Gospel Rescue Mission \ / - NO HTML/RTF in e-mail | P.O. Box 230510 X - NO Word docs in e-mail | Anchorage, AK 99523-0510 / \ - To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: cvs commit: src/sys/kern subr_smp.c src/sys/sys smp.h
In article [EMAIL PROTECTED] Marcel Moolenaar [EMAIL PROTECTED] wrote: marcel 2001/10/31 01:03:05 PST Modified files: sys/kern subr_smp.c sys/sys smp.h Log: Make smp_started volatile in sys/smp.h and remove the volatile declaration in subr_smp.c. This solves a compile problem with gcc 3.0.1 (ia64 cross-build). Reviewed: jhb Revision ChangesPath 1.159 +1 -2 src/sys/kern/subr_smp.c 1.69 +2 -2 src/sys/sys/smp.h This patch totally remove THE definition(?) of smp_started from subr_smp.c and thus make the kernel unbuildable. N.Dudorov P.S. The fix is obvious - return smp_started definition minus 'volatile' to the subr_smp.c To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ouch -- the second controller on Promise-66 is not detected!
I just commit the fix using new devclass_find_free_unit() interface function. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
