Re: wierd build error with -current
On 30 Jun 2001 21:59:19 -0700, Matthew Jacob wrote:
I'm sure you're right. I guess I need to go fix the breakage.
It's supposed to work. Things get built in /usr/obj, not /usr/src.
Hrm, OK. That's something I didn't know. I'm assuming that you've tried
mounting /usr/src as read-write and tried compiling again?
- andrew
--
void signature () {
cout Andrew Reid -- [EMAIL PROTECTED] endl ;
cout Cell: +61 401 946 813 endl;
cout Quidquid latine dictum sit, altum viditur endl;
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
ipfilter+ipv6 - what am I missing?
Hi, On yesterdays -current I'm having some problems making ipfilter DTRT with ipv6 packets: bm# ipfstat -6io block out quick on xl0 from any to any block out quick on vx0 from any to any block in quick on xl0 from any to any block in quick on vx0 from any to any (passing ipv6 traffic) bm# ipfstat -6 IPv6 packets: in 0 out 0 Even with the above ruleset installed, ipfilter doesn't block any traffic at all, and counters for ipv6 packets remains at zero while successfully running various ipv6 sessions through the firewall, so what am I missing here? Feel free to flame me if I am missing the obvious :-) /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, TDC, IP-section. Hey, are any of you guys out there actually *using* RFC 2549? To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
can't build kernel: config doesn't work
Truly bizarre. Running config does nothing, although it generates the usual messages. I tried deleting my kernel object directory after an odd failure; ran config again, it didn't even recreate the directory. -- Michael D. Harnois[EMAIL PROTECTED] Redeemer Lutheran Church Washburn, Iowa Everyone thinks of changing the world, but no one thinks of changing himself. -- Leo Nikolaevich Tolstoy To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: can't build kernel: config doesn't work
The same here, but 'config -d /sys/compile/GENERIC GENERIC' did what it is supposed to do. Is this a new specification of 'config', or bug? From: Michael Harnois [EMAIL PROTECTED] Subject: can't build kernel: config doesn't work mdharnois Truly bizarre. Running config does nothing, although it generates the mdharnois usual messages. I tried deleting my kernel object directory after an mdharnois odd failure; ran config again, it didn't even recreate the directory. mdharnois To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
blockable sleep lock panic (and dumps still don't work)
microuptime() went backwards warning caused a blockable sleep lock panic on a June 25 kernel: panic: blockable sleep lock (sx) allproc @ ../../kern/kern_proc.c:146 Debugger(panic) Stopped at Debugger+0x44: pushl %ebx db trace Debugger(c02c7cfb) at Debugger+0x44 panic(c02cb140,c02c8500,c02c71a3,c02c7283,92) at panic+0x70 witness_lock(c038ad60,0,c02c7283,92) at witness_lock+0x22e _sx_slock(c038ad60,c02c7283,92,c2ad1604,c2ad1620) at _sx_slock+0x128 pfind(1ca,c2ad1600,c2ad1620,dc3aeda8,c01d94a7) at pfind+0x1c selwakeup(c2ad1604,c2ad1620,6d,dc3aeeb4,dc3aedb8) at selwakeup+0x35 ptcwakeup(c2ad1620,1,dc3aedc4,c01d68ac,c2ad1620) at ptcwakeup+0x23 ptsstart(c2ad1620,dc3aede0,c01d7fa5,c2ad1620,6d) at ptsstart+0x26 ttstart(c2ad1620,6d,c2ad1620,7,c2ad1620) at ttstart+0x18 tputchar(6d,c2ad1620) at tputchar+0x35 putchar(6d,dc3aeeb4) at putchar+0x4f kvprintf(c02c7701,c01c3624,dc3aeeb4,a,dc3aeecc) at kvprintf+0x8e printf(c02c7700,6949e,93dc1,6949e,d696a092) at printf+0x44 calcru(dc3abc80,dc3adb74,dc3adb7c,0) at calcru+0x12b getrusage(dc3abc80,dc3aef80,8332e78,84c4000,8505) at getrusage+0x112 syscall(2f,2f,2f,8505,84c4000) at syscall+0x8d5 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (117, FreeBSD ELF, getrusage), eip = 0x8247269, esp = 0x8517720, ebp = 0x8517730 --- db x/s 0xx02c7700 Bad character in number db x/s 0xc02c7700 pgrpdump_cmd+0x358: microuptime() went backwards (%ld.%06ld - %ld.%06ld)\012 db panic panic: from debugger Uptime: 4d23h47m42s dumping to dev ad1b, offset 7340064 dump ata1: resetting devices .. ad1: invalidating queued requests panic: mutex sched lock recursed at ../../kern/kern_synch.c:826 Uptime: 4d23h47m42s kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc fault code = supervisor read, page not present instruction pointer = 0x8:0xc01c7933 stack pointer = 0x10:0xdc3ae904 frame pointer = 0x10:0xdc3ae910 code segment= base 0x0, limit 0xf, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags= resume, IOPL = 0 current process = 68314 (cvsup) kernel: type 12 trap, code=0 Stopped at Debugger+0x44: pushl %ebx db trace Debugger(c02c7cfb) at Debugger+0x44 panic(c02cb140,c02c8500,c02c71a3,c02c7283,92) at panic+0x70 witness_lock(c038ad60,0,c02c7283,92) at witness_lock+0x22e _sx_slock(c038ad60,c02c7283,92,c2ad1604,c2ad1620) at _sx_slock+0x128 pfind(1ca,c2ad1600,c2ad1620,dc3aeda8,c01d94a7) at pfind+0x1c selwakeup(c2ad1604,c2ad1620,6d,dc3aeeb4,dc3aedb8) at selwakeup+0x35 ptcwakeup(c2ad1620,1,dc3aedc4,c01d68ac,c2ad1620) at ptcwakeup+0x23 ptsstart(c2ad1620,dc3aede0,c01d7fa5,c2ad1620,6d) at ptsstart+0x26 ttstart(c2ad1620,6d,c2ad1620,7,c2ad1620) at ttstart+0x18 tputchar(6d,c2ad1620) at tputchar+0x35 putchar(6d,dc3aeeb4) at putchar+0x4f kvprintf(c02c7701,c01c3624,dc3aeeb4,a,dc3aeecc) at kvprintf+0x8e printf(c02c7700,6949e,93dc1,6949e,d696a092) at printf+0x44 calcru(dc3abc80,dc3adb74,dc3adb7c,0) at calcru+0x12b getrusage(dc3abc80,dc3aef80,8332e78,84c4000,8505) at getrusage+0x112 syscall(2f,2f,2f,8505,84c4000) at syscall+0x8d5 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (117, FreeBSD ELF, getrusage), eip = 0x8247269, esp = 0x8517720, ebp = 0x8517730 --- db reboot No such command db call boot syncing disks... 34 34 panic: runq_add: proc 0xdc3abc80 (cvsup) not SRUN Uptime: 4d23h49m41s panic: lockmgr: locking against myself Uptime: 4d23h49m41s panic: lockmgr: locking against myself Uptime: 4d23h49m41s panic: lockmgr: locking against myself [ad nauseam] DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: can't build kernel: config doesn't work
It works for me ;) Remember that the new default is:
/sys/${MACHINEARCH}/compile/${KERNCONF}
On 01-Jul-2001 Takeshi Ken Yamada wrote:
|
| The same here, but 'config -d /sys/compile/GENERIC GENERIC'
| did what it is supposed to do.
|
| Is this a new specification of 'config', or bug?
|
| From: Michael Harnois [EMAIL PROTECTED]
| Subject: can't build kernel: config doesn't work
| mdharnois Truly bizarre. Running config does nothing, although it generates
| the
| mdharnois usual messages. I tried deleting my kernel object directory after
| an
| mdharnois odd failure; ran config again, it didn't even recreate the
| directory.
| mdharnois
|
| To Unsubscribe: send mail to [EMAIL PROTECTED]
| with unsubscribe freebsd-current in the body of the message
Mike
--
Mike Heffner mheffner@[acm.]vt.edu
Fredericksburg, VA [EMAIL PROTECTED]
PGP signature
Re: can't build kernel: config doesn't work
At 10:05 AM -0400 7/1/01, Mike Heffner wrote:
It works for me ;) Remember that the new default is:
/sys/${MACHINEARCH}/compile/${KERNCONF}
On 01-Jul-2001 Takeshi Ken Yamada wrote:
|
| The same here, but 'config -d /sys/compile/GENERIC GENERIC'
| did what it is supposed to do.
|
| Is this a new specification of 'config', or bug?
|
| From: Michael Harnois [EMAIL PROTECTED]
| Subject: can't build kernel: config doesn't work
| mdharnois Truly bizarre. Running config does nothing, although it generates
| the
| mdharnois usual messages. I tried deleting my kernel object directory after
| an
| mdharnois odd failure; ran config again, it didn't even recreate the
| directory.
| mdharnois
Right, there is a new compile directory. Perhaps this needs to be
added to UPDATING. Anyway, did you run cvs update -dP on your cvs
tree? Or just do mkdir on the new path mentioned above.
Mark
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: can't build kernel: config doesn't work
On Sun, Jul 01, 2001 at 08:09:14AM -0700, Mark Peek wrote:
Right, there is a new compile directory. Perhaps this needs to be
added to UPDATING. Anyway, did you run cvs update -dP on your cvs
tree? Or just do mkdir on the new path mentioned above.
It *IS* in UPDATING:
Updating Information for FreeBSD current users
This file is maintained and copyrighted by M. Warner Losh
[EMAIL PROTECTED]. Please send new entries directly to him. See end
of file for further details. For commonly done items, please see the
COMMON ITEMS: section later in the file.
20010628:
The kernel compile module has moved from src/sys/compile/FOO
to src/sys/${MACHINE}/compile/FOO.
- alex
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: can't build kernel: config doesn't work
OK, so it is my fault. Did I miss a HEADS UP on this? It certainly deserved one. -- Michael D. Harnois[EMAIL PROTECTED] Redeemer Lutheran Church Washburn, Iowa He who will not reason is a bigot; he who cannot is a fool; and he who dares not, is a slave. -- William Drummond To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: can't build kernel: config doesn't work
At 8:27 AM -0700 7/1/01, Alex Zepeda wrote:
On Sun, Jul 01, 2001 at 08:09:14AM -0700, Mark Peek wrote:
Right, there is a new compile directory. Perhaps this needs to be
added to UPDATING. Anyway, did you run cvs update -dP on your cvs
tree? Or just do mkdir on the new path mentioned above.
It *IS* in UPDATING:
Updating Information for FreeBSD current users
This file is maintained and copyrighted by M. Warner Losh
[EMAIL PROTECTED]. Please send new entries directly to him. See end
of file for further details. For commonly done items, please see the
COMMON ITEMS: section later in the file.
20010628:
The kernel compile module has moved from src/sys/compile/FOO
to src/sys/${MACHINE}/compile/FOO.
Silly me, of course Warner would make sure UPDATING is correct! :-) I
must have glossed over the cvs commit message for that change. I
stand corrected.
Mark
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Re: can't build kernel: config doesn't work
On 01-Jul-2001 Mark Peek wrote:
| At 10:05 AM -0400 7/1/01, Mike Heffner wrote:
|It works for me ;) Remember that the new default is:
|
| /sys/${MACHINEARCH}/compile/${KERNCONF}
|
|
| Right, there is a new compile directory. Perhaps this needs to be
| added to UPDATING. Anyway, did you run cvs update -dP on your cvs
| tree? Or just do mkdir on the new path mentioned above.
I just did a cvsup and ran config with no arguments, and it created the right
directory for me.
Mike
--
Mike Heffner mheffner@[acm.]vt.edu
Fredericksburg, VA [EMAIL PROTECTED]
PGP signature
Re: blockable sleep lock panic (and dumps still don't work)
On 1 Jul 2001, Dag-Erling Smorgrav wrote: microuptime() went backwards warning caused a blockable sleep lock panic on a June 25 kernel: panic: blockable sleep lock (sx) allproc @ ../../kern/kern_proc.c:146 Debugger(panic) Stopped at Debugger+0x44: pushl %ebx db trace ... tputchar(6d,c2ad1620) at tputchar+0x35 putchar(6d,dc3aeeb4) at putchar+0x4f kvprintf(c02c7701,c01c3624,dc3aeeb4,a,dc3aeecc) at kvprintf+0x8e printf(c02c7700,6949e,93dc1,6949e,d696a092) at printf+0x44 Debugger(c02c7cfb) at Debugger+0x44 panic(c02cb140,c02c8500,c02c71a3,c02c7283,92) at panic+0x70 witness_lock(c038ad60,0,c02c7283,92) at witness_lock+0x22e _sx_slock(c038ad60,c02c7283,92,c2ad1604,c2ad1620) at _sx_slock+0x128 pfind(1ca,c2ad1600,c2ad1620,dc3aeda8,c01d94a7) at pfind+0x1c selwakeup(c2ad1604,c2ad1620,6d,dc3aeeb4,dc3aedb8) at selwakeup+0x35 ptcwakeup(c2ad1620,1,dc3aedc4,c01d68ac,c2ad1620) at ptcwakeup+0x23 ptsstart(c2ad1620,dc3aede0,c01d7fa5,c2ad1620,6d) at ptsstart+0x26 ttstart(c2ad1620,6d,c2ad1620,7,c2ad1620) at ttstart+0x18 tputchar(6d,c2ad1620) at tputchar+0x35 This has something to do with the TIOCCONS ioctl. tputchar() is the output function for the TOTTY case, and the TOTTY flag is only set for kernel printfs if TIOCCONS has set constty to non-NULL. I'm not sure what uses TIOCCONS (I think it is intended for use with X, but it doesn't seem to be used on my systems). TIOCCONS is almost unimplementable (printing to a terminal is not reentrant enough to work in all contexts, and is supposed to be protected by spltty(), but kernel printfs must work in all contexts), so the correct fix may be to remove it. TIOCCONS is broken in all versions of FreeBSD. The brokenness is just more obvious now that there are more locks to trip over. The output function for the TOLOG case (i.e., msglogchar()) also seems to be broken in all versions of FreeBSD. It operates on the circular message buffer, but doesn't have any locking. The output function for the TOCONS case (i.e., cnputc()) is also problematic. Only the serial console output routine even attempts to be reentrant, and (per-cpu) reentrancy is not enough under SMP. Syscons' output routine was easy to panic by mixing kernel printfs with user-mode output the last time I checked. putchar(6d,dc3aeeb4) at putchar+0x4f kvprintf(c02c7701,c01c3624,dc3aeeb4,a,dc3aeecc) at kvprintf+0x8e printf(c02c7700,6949e,93dc1,6949e,d696a092) at printf+0x44 calcru(dc3abc80,dc3adb74,dc3adb7c,0) at calcru+0x12b getrusage(dc3abc80,dc3aef80,8332e78,84c4000,8505) at getrusage+0x112 syscall(2f,2f,2f,8505,84c4000) at syscall+0x8d5 syscall_with_err_pushed() at syscall_with_err_pushed+0x1b --- syscall (117, FreeBSD ELF, getrusage), eip = 0x8247269, esp = 0x8517720, ebp = 0x8517730 --- ... dumping to dev ad1b, offset 7340064 dump ata1: resetting devices .. ad1: invalidating queued requests panic: mutex sched lock recursed at ../../kern/kern_synch.c:826 Apparently addump() depends on too much infrastructure. A panic may occur at any time, so dump routines face much the same locking problems as console output routines. They can't go near normal locks like sched_lock, since they need to work when such locks are in any state. Bruce To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ipfilter+ipv6 - what am I missing?
I don't think ipf is complete in its ipv6 support yet.You can use ipfw instead. == WWW.XGFORCE.COM The Next Generation Load Balance and Fail Safe Server Clustering Software for the Internet. == - Original Message - From: Niels Chr. Bank-Pedersen [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, July 01, 2001 5:21 AM Subject: ipfilter+ipv6 - what am I missing? Hi, On yesterdays -current I'm having some problems making ipfilter DTRT with ipv6 packets: bm# ipfstat -6io block out quick on xl0 from any to any block out quick on vx0 from any to any block in quick on xl0 from any to any block in quick on vx0 from any to any (passing ipv6 traffic) bm# ipfstat -6 IPv6 packets: in 0 out 0 Even with the above ruleset installed, ipfilter doesn't block any traffic at all, and counters for ipv6 packets remains at zero while successfully running various ipv6 sessions through the firewall, so what am I missing here? Feel free to flame me if I am missing the obvious :-) /Niels Chr. -- Niels Christian Bank-Pedersen, NCB1-RIPE. Network Manager, TDC, IP-section. Hey, are any of you guys out there actually *using* RFC 2549? 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: fd0c mount(8) Race
Sat, Jun 30, 2001 at 00:16:53, cristjc (Crist J. Clark) wrote about fd0c mount(8) Race: mount: /dev/fd0c: No such file or directory That is, even though once I drop into single-user mode we see the symlink for /dev/fd0c, it does not seem like it was there when 'mount -a -t nonfs' is run in /etc/rc. I don't see it too. It appears if is created explicitly. Log follows (showing quite strange behavior): root@iv:~##ls -l /dev/fd0* crw-r- 1 root operator9, 0 Jul 1 15:01 /dev/fd0 root@iv:~##ls -l /dev/fd0c ls: /dev/fd0c: No such file or directory root@iv:~##mknod /dev/fd0c c 0 0 mknod: /dev/fd0c: File exists root@iv:~##ls -l /dev/fd0c lrw-rw-rw- 1 root wheel 4 Jul 1 19:31 /dev/fd0c - fd0 root@iv:~##rm /dev/fd0c root@iv:~##rm /dev/fd0c rm: /dev/fd0c: No such file or directory root@iv:~##ls -l /dev/fd0c ls: /dev/fd0c: No such file or directory root@iv:~##ls -l /dev/fd0c ls: /dev/fd0c: No such file or directory root@iv:~##mknod /dev/fd0c c 0 0 root@iv:~##ls -l /dev/fd0c lrw-rw-rw- 1 root wheel 4 Jul 1 19:31 /dev/fd0c - fd0 I'm surprised mainly that first mknod reported bogus failure. reproduce the problem? Or is it well known (I can't find it in the mail archive)? I think you can't - current devfs is too young. /netch To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Vinum + DEVFS ?
Alfred Perlstein [EMAIL PROTECTED] wrote: } * Patrick Hartling [EMAIL PROTECTED] [010630 14:04] wrote: } I just got two new hard drives, and I am preparing to set them up to do } RAID-1 with Vinum. A few weeks ago (around the time that use of DEVFS } became the default in -current), I saw a message saying that Vinum was } not yet ready for use with DEVFS. Is that still the case? } } I fixed that. :) Let me and Grog know if you have problems. Everything seems to be okay with the vinum device node creation, but I am having problems with my vinum configuration. I basically copied this from an example in the online documentation (which is also in the vinum(8) manpage); drive da3e device /dev/da3s1e drive da4e device /dev/da4s1e volume mirror plex org concat sd length 12g drive da3e plex org concat sd length 12g drive da4e When I do 'vinum create', I get the following: 1: drive da3e device /dev/da3s1e ** 1 : Invalid argument 2: drive da4e device /dev/da4s1e ** 2 : Invalid argument 3: volume mirror 4: plex org concat 5: sd length 12g drive da3e 6: plex org concat 7: sd length 12g drive da4e Which one is the invalid argument, and why is it invalid? Is there some caveat I have missed? -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Vinum + DEVFS ?
On Sunday, 1 July 2001 at 14:22:36 -0500, Patrick Hartling wrote: Alfred Perlstein [EMAIL PROTECTED] wrote: * Patrick Hartling [EMAIL PROTECTED] [010630 14:04] wrote: I just got two new hard drives, and I am preparing to set them up to do RAID-1 with Vinum. A few weeks ago (around the time that use of DEVFS became the default in -current), I saw a message saying that Vinum was not yet ready for use with DEVFS. Is that still the case? I fixed that. :) Let me and Grog know if you have problems. Everything seems to be okay with the vinum device node creation, but I am having problems with my vinum configuration. I basically copied this from an example in the online documentation (which is also in the vinum(8) manpage); drive da3e device /dev/da3s1e drive da4e device /dev/da4s1e volume mirror plex org concat sd length 12g drive da3e plex org concat sd length 12g drive da4e When I do 'vinum create', I get the following: 1: drive da3e device /dev/da3s1e ** 1 : Invalid argument 2: drive da4e device /dev/da4s1e ** 2 : Invalid argument 3: volume mirror 4: plex org concat 5: sd length 12g drive da3e 6: plex org concat 7: sd length 12g drive da4e Which one is the invalid argument, The name of the partition. and why is it invalid? I can't say for sure, since you don't supply the info asked for in the man page and the web page. But I'd be prepared to bet that your da3s1e and da4s1e partitions are not of type Vinum. Look for 'disklabel' in the man page. BTW, it's bad practice to name your drives after the partition on which they are currently resident. You can take those two drives and swap their SCSI IDs. Vinum will still find them and operate correctly, but your da3s1e partition will be drive da4e, and da4s1e will be drive da3e, which is completely confusing. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: Vinum + DEVFS ?
Greg Lehey [EMAIL PROTECTED] wrote: } On Sunday, 1 July 2001 at 14:22:36 -0500, Patrick Hartling wrote: } Alfred Perlstein [EMAIL PROTECTED] wrote: } } * Patrick Hartling [EMAIL PROTECTED] [010630 14:04] wrote: } I just got two new hard drives, and I am preparing to set them up to do } RAID-1 with Vinum. A few weeks ago (around the time that use of DEVFS } became the default in -current), I saw a message saying that Vinum was } not yet ready for use with DEVFS. Is that still the case? } } I fixed that. :) Let me and Grog know if you have problems. } } Everything seems to be okay with the vinum device node creation, but I } am having problems with my vinum configuration. I basically copied this } from an example in the online documentation (which is also in the } vinum(8) manpage); } } drive da3e device /dev/da3s1e } drive da4e device /dev/da4s1e } volume mirror }plex org concat } sd length 12g drive da3e }plex org concat } sd length 12g drive da4e } } When I do 'vinum create', I get the following: } } 1: drive da3e device /dev/da3s1e } ** 1 : Invalid argument } 2: drive da4e device /dev/da4s1e } ** 2 : Invalid argument } 3: volume mirror } 4: plex org concat } 5: sd length 12g drive da3e } 6: plex org concat } 7: sd length 12g drive da4e } } Which one is the invalid argument, } } The name of the partition. } } and why is it invalid? } } I can't say for sure, since you don't supply the info asked for in the } man page and the web page. Sorry, I'll be sure to include everything next time. } But I'd be prepared to bet that your } da3s1e and da4s1e partitions are not of type Vinum. Look for } 'disklabel' in the man page. That was it, thanks. I must have missed that point in reading the web pages yesterday (which are very helpful and readable, btw). } BTW, it's bad practice to name your drives after the partition on } which they are currently resident. You can take those two drives and } swap their SCSI IDs. Vinum will still find them and operate } correctly, but your da3s1e partition will be drive da4e, and da4s1e } will be drive da3e, which is completely confusing. Thanks for the tip. -Patrick Patrick L. Hartling | Research Assistant, VRAC [EMAIL PROTECTED] | 2624 Howe Hall -- (515)294-4916 http://www.137.org/patrick/ | http://www.vrac.iastate.edu/ To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: blockable sleep lock panic (and dumps still don't work)
This has something to do with the TIOCCONS ioctl. tputchar() is the output function for the TOTTY case, and the TOTTY flag is only set for kernel printfs if TIOCCONS has set constty to non-NULL. I'm not sure what uses TIOCCONS (I think it is intended for use with X, but it doesn't seem to be used on my systems). IIRC, xconsole uses this to capture console output. TIOCCONS is almost unimplementable (printing to a terminal is not reentrant enough to work in all contexts, and is supposed to be protected by spltty(), but kernel printfs must work in all contexts), so the correct fix may be to remove it. TIOCCONS is broken in all versions of FreeBSD. The brokenness is just more obvious now that there are more locks to trip over. The output function for the TOLOG case (i.e., msglogchar()) also seems to be broken in all versions of FreeBSD. It operates on the circular message buffer, but doesn't have any locking. I discussed this with jhb. We even had a test patch. Jhb told me that someone else was working on providing proper locking in kernel printf(). The output function for the TOCONS case (i.e., cnputc()) is also problematic. Only the serial console output routine even attempts to be reentrant, and (per-cpu) reentrancy is not enough under SMP. Syscons' output routine was easy to panic by mixing kernel printfs with user-mode output the last time I checked. Syscons' sccnputc() is not reentrant. I was trying to improbe this, but decided that I would wait until I see further development in tty locking and kernel printf() area by jhb. Kazu To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
IPV6 panic ?
Hi, I have had two of these since 6/30, which is when I last cvsup'ed and rebuilt everything. Fatal trap 12: page fault while in kernel mode fault virtual address = 0xdeadc0de fault code = supervisor read, page not present instruction pointer = 0x8:0xc02c3b10 stack pointer = 0x10:0xcbb4ff28 frame pointer = 0x10:0xcbb4ff3c 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 = 12 (swi6: tty:sio+) kernel: type 12 trap, code=0 Stopped at nd6_timer+_0x38: movl 0(%ebx),%eax db trace nd6_timer(0) at nd6_timer+0x38 softclock(0) at softclock_0x30e ithread_loop(c1207d00,cbb4ffa8) at ithread_loop+0x263 fork_exit(c0224b14,c1207d00,cbb4ffa8) at fork_exit+0xa0 fork_trampoline() at fork trampoline+0x8 db The kernel config is just GENERIC + IPSEC. IPV6 is configured and running. Thanks, skd To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: ipfilter+ipv6 - what am I missing?
On Sun, Jul 01, 2001 at 10:54 -0700, matt wrote: I don't think ipf is complete in its ipv6 support yet.You can use ipfw instead. Ipf has been supporting IPv6 for quite some time. It's just that one has to enable this support in the Makefile. $ grep INET6 contrib/ipfilter/Makefile #INET6=-DUSE_INET6 MFLAGS1='CFLAGS=$(CFLAGS) $(ARCHINC) $(SOLARIS2) $(INET6)' \ [ ... ] And ISTR that one has to add -6 to the ipf(8) invocation options (like, in /etc/rc.conf). When I extended ipf to invoke a preprocessor (PR bin/21989) I added some magic to not propose switches for unsupported features in the synopsis. Maybe this concern should be reraised? virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s get gpg key [EMAIL PROTECTED] -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
syslogd and -a
Hello - It seems the -a option for syslogd does not work 100%. I need to log from hosts from 192.168.1.1-.6 doing /usr/sbin/syslogd -a 192.168.1.1/29 does not work (nothing gets logged) but, if i do /usr/sbin/syslogd -a 192.168.1.1/32 -a 192.168.1.2/32, etc... that works can anyone try this out? Thanks - David To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: can't build kernel: config doesn't work
In message [EMAIL PROTECTED] Michael Harnois writes: : OK, so it is my fault. Did I miss a HEADS UP on this? It certainly : deserved one. I didn't send one. Maybe I should have. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: syslogd and -a
On Sun, Jul 01, 2001 at 11:41:25PM -0400, David Hill wrote: Hello - It seems the -a option for syslogd does not work 100%. I need to log from hosts from 192.168.1.1-.6 doing /usr/sbin/syslogd -a 192.168.1.1/29 does not work (nothing gets logged) but, if i do /usr/sbin/syslogd -a 192.168.1.1/32 -a 192.168.1.2/32, etc... that works can anyone try this out? Hmmm... Looks like, # syslogd -a 192.168.1.0/29 Will work and, # syslogd -a 192.168.1.1/29 Won't. I'll have a look. -- Crist J. Clark [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: syslogd and -a
On 02-Jul-01 (04:20:44/GMT) Crist J. Clark wrote: It seems the -a option for syslogd does not work 100%. Hmmm... Looks like, # syslogd -a 192.168.1.0/29 Will work and, # syslogd -a 192.168.1.1/29 Won't. Under 4.3-STABLE is the same. To capure log from router I added (in rc.conf) -a 192.168.22.254/32:* because with all log enabled I notice that with ..22.0/24 syslod refused to accept requests from network :-( Ciao, Riccardo. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
