Re: Mounting devfs over to ZFS from fstab fails
On 3/28/08, Attila Nagy [EMAIL PROTECTED] wrote: Hello, I have some jails running on ZFS, so I have to mount devfs's into them. For this purpose, I have some similar lines in /etc/fstab: devfs /pool/jail/ldap/dev devfs rw 0 0 Where /pool is a ZFS filesystem. This has worked until today -when I upgraded from a previous 7-STABLE (FreeBSD 7.0-STABLE #16: Fri Mar 7 14:30:08 CET 2008) to today's STABLE- but not anymore. The boot process fails with something like WARNING: $true wasn't set, see man rc.conf (or something similar, I don't have the exact error message, but I can reproduce if it's needed), and the problem is that the rc scripts try to mount the devfs (and nullfs) stuff to the yet unmounted ZFS, so /pool/jail/ldap/dev doesn't exist. It would be helpfull to see what the error message is. For jails you don't need to place any devfs entries into /etc/fstab. The /etc/rc.d/jail script will automatically mount/umount the devfs for you. Just add the following to /etc/rc.conf: jail_jailname_devfs_enable=YES jail_jailname_devfs_ruleset=MyJailRule - this is optional You can also do the same thing with chroot, an example script is /etc/rc.d/named. Scot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Generic 2-port PCI Express Serial Card - how to get recognized?
To find the vendor/device IDs of your card use pciconf -lv, and look for entries similar to the following: [EMAIL PROTECTED]:0:20:0: class=0x0c0500 card=0x309b103c chip=0x43721002 rev=0x11 hdr=0x00 vendor = 'ATI Technologies Inc' device = 'IXP SB400 SMBus' class = serial bus subclass = SMBus Scot ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Generic 2-port PCI Express Serial Card - how to get recognized?
On 3/28/08, Karl Denninger [EMAIL PROTECTED] wrote: Hi folks; I have a generic PCI Express dumb (16550 allegedly) serial card that goes in a PCI Express slot. FreeBSD doesn't see it, which I assume has to do with the card's vendor ID not being in the table that FreeBSD reocognizes. How do I get the ID from the probe (and/or probe the bus when the machine is running?) - I assume I could add the vendor ID to the sio_pci.c module and it MIGHT work, yes? It doesn't have a specific brand and documentation is basically zilch; I figured it might work right out of the box, but so far, no joy. Thanks in advance! -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant Kids Rights Activist http://www.denninger.netMy home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.comMusings Of A Sentient Mind ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Missing manual pages (e.g. aio_fsync)
Hello, It seems that the manual page of aio_fsync is missing, at least in FreeBSD 7.0-STABLE. I have some questions regarding this: 1. Is there somebody working on a man page for aio_fsync? 2. Is there a list of missing manual pages? 3. What is the current status of POSIX and Unix Specification? Is there any agreement with IEEE or Open Group allowing to cut-and-paste from, say, http://www.opengroup.org/onlinepubs/009695399/functions/aio_fsync.html? -- Carlos A. M. dos Santos ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The Design and Implementation of the FreeBSD Operating System
Hi Unga, Is there a 2nd edition coming soon? Third iirc. ISBN 0201549794 was the first, although with a slightly different name. Regards, Robert PS: may I politely remind you of our mailinglist charters phrase: No posting should be made to more than 2 mailing lists (..) ? ;-) http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/eresources.html#ERESOURCES-MAIL ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: The Design and Implementation of the FreeBSD Operating System
In message [EMAIL PROTECTED], Robert Joosten ([EMAIL PROTECTED]) wrote: Hi Unga, Is there a 2nd edition coming soon? Third iirc. ISBN 0201549794 was the first, although with a slightly different name. You are forgetting ISBN 0201061961! Cheers, Nick. -- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Panic with usb serial
Hi all, Is it expected that removing a usb serial adapter while you have a connection (eg tip) using it will panic a -stable system? I know it is expected if you remove a mounted umass device so wanted to see if its known behavior for serial before I file a pr. (adapter is FTDI usb serial converter, class 0/0, rev 1.10/4.00, addr 3) -stable version as of the 25th march, (may have existed before but the first time I forgot to close tip before removing the device was on this version.) cheer, Vince ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Missing manual pages (e.g. aio_fsync)
Carlos A. M. dos Santos wrote: Hello, It seems that the manual page of aio_fsync is missing, at least in FreeBSD 7.0-STABLE. I have some questions regarding this: 1. Is there somebody working on a man page for aio_fsync? 2. Is there a list of missing manual pages? http://wiki.freebsd.org/MissingManpages no idea how complete that is though. 3. What is the current status of POSIX and Unix Specification? Is there any agreement with IEEE or Open Group allowing to cut-and-paste from, say, http://www.opengroup.org/onlinepubs/009695399/functions/aio_fsync.html? ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Panic with usb serial
On Sat, Mar 29, 2008 at 10:11:04PM +, Vince wrote: Is it expected that removing a usb serial adapter while you have a connection (eg tip) using it will panic a -stable system? I know it is expected if you remove a mounted umass device so wanted to see if its known behavior for serial before I file a pr. (adapter is FTDI usb serial converter, class 0/0, rev 1.10/4.00, addr 3) -stable version as of the 25th march, (may have existed before but the first time I forgot to close tip before removing the device was on this version.) I would expect that the problem is identical in the sense that with a connection established, you have an open file descriptor which is associated with a serial device that uses USB. So, yes, I would expect this behaviour based on the track record. Should it happen? The answer is no. File a PR? Also, I'd like to know what USB serial adapter you're using (brand, model, and a website of it if possible), for unrelated reasons. Thanks! -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
PCI add-in parallel port problem
Hi,
I'm trying to get a PCI-express add-in parallel port card working with
7.0-STABLE, and after trying the following, I'm unable to get it to
attach to the ppc bus. The card has a MosChip NM9805 chip. Motherboard
is an ASUS P5E64 WS. (which of course has no on-board parallel port).
The card seems to be recognised by the puc layer.
I've added
device puc
to the kernel config file, and added
{ 0x9710, 0x9805, 0x, 0,
MosChip NM9805 Dual 1284 Printer port,
0,
PUC_PORT_2P, 0x10, 8, 0,
},
to sys/dev/puc/pucdata.c and with verbose booting, get the following
extracts from dmesg: (full dmesg attached below)
pcib3: slot 0 INTB hardwired to IRQ 17
pcib4: slot 1 INTA is routed to irq 17
pcib5: slot 0 INTA is routed to irq 17
pcib6: slot 0 INTA is routed to irq 17
ppc0: Reserved 0x8 bytes for rid 0x10 type 4 at 0xdc00
ppc0: using extended I/O port range
puc0: MosChip NM9805 Dual 1284 Printer port port
0xdc00-0xdc07,0xd880-0xd887,0xd800-0xd807,0xd480-0xd487,0xd400-0xd407,0xd080-0xd08f
irq 17 at device 0.0 on pci10
pcib6: puc0 requested I/O range 0xdc00-0xdc07: in range
pcib5: puc0 requested I/O range 0xdc00-0xdc07: in range
pcib4: puc0 requested I/O range 0xdc00-0xdc07: in range
pcib3: puc0 requested I/O range 0xdc00-0xdc07: in range
puc0: Reserved 0x8 bytes for rid 0x18 type 4 at 0xd800
puc0: [FILTER]
ppc0: using extended I/O port range
ppc0: using extended I/O port range
[ and later ]
ppc0: parallel port not found.
ppc0: Parallel port failed to probe at irq 7 on isa0
Any suggestions would be appreciated.
--
Richard
Copyright (c) 1992-2008 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 is a registered trademark of The FreeBSD Foundation.
FreeBSD 7.0-STABLE #8: Sat Mar 29 16:40:32 EST 2008
[EMAIL PROTECTED]:/u3/obj/usr/src/sys/LOCAL
Preloaded elf kernel /boot/kernel/kernel at 0xc0ef1000.
Preloaded elf module /boot/kernel/snd_driver.ko at 0xc0ef1188.
Preloaded elf module /boot/kernel/snd_ad1816.ko at 0xc0ef1238.
Preloaded elf module /boot/kernel/sound.ko at 0xc0ef12e8.
Preloaded elf module /boot/kernel/snd_als4000.ko at 0xc0ef1394.
Preloaded elf module /boot/kernel/snd_atiixp.ko at 0xc0ef1444.
Preloaded elf module /boot/kernel/snd_cmi.ko at 0xc0ef14f4.
Preloaded elf module /boot/kernel/snd_cs4281.ko at 0xc0ef15a0.
Preloaded elf module /boot/kernel/snd_csa.ko at 0xc0ef1650.
Preloaded elf module /boot/kernel/snd_ds1.ko at 0xc0ef16fc.
Preloaded elf module /boot/kernel/snd_emu10kx.ko at 0xc0ef17a8.
Preloaded elf module /boot/kernel/snd_envy24.ko at 0xc0ef1858.
Preloaded elf module /boot/kernel/snd_spicds.ko at 0xc0ef1908.
Preloaded elf module /boot/kernel/snd_envy24ht.ko at 0xc0ef19b8.
Preloaded elf module /boot/kernel/snd_es137x.ko at 0xc0ef1a6c.
Preloaded elf module /boot/kernel/snd_ess.ko at 0xc0ef1b1c.
Preloaded elf module /boot/kernel/snd_sbc.ko at 0xc0ef1bc8.
Preloaded elf module /boot/kernel/snd_fm801.ko at 0xc0ef1c74.
Preloaded elf module /boot/kernel/snd_mss.ko at 0xc0ef1d24.
Preloaded elf module /boot/kernel/snd_hda.ko at 0xc0ef1dd0.
Preloaded elf module /boot/kernel/snd_ich.ko at 0xc0ef1e7c.
Preloaded elf module /boot/kernel/snd_maestro.ko at 0xc0ef1f28.
Preloaded elf module /boot/kernel/snd_maestro3.ko at 0xc0ef1fd8.
Preloaded elf module /boot/kernel/snd_neomagic.ko at 0xc0ef208c.
Preloaded elf module /boot/kernel/snd_sb16.ko at 0xc0ef2140.
Preloaded elf module /boot/kernel/snd_sb8.ko at 0xc0ef21f0.
Preloaded elf module /boot/kernel/snd_solo.ko at 0xc0ef229c.
Preloaded elf module /boot/kernel/snd_t4dwave.ko at 0xc0ef234c.
Preloaded elf module /boot/kernel/snd_via8233.ko at 0xc0ef23fc.
Preloaded elf module /boot/kernel/snd_via82c686.ko at 0xc0ef24ac.
Preloaded elf module /boot/kernel/snd_vibes.ko at 0xc0ef2560.
Preloaded elf module /boot/kernel/atapicam.ko at 0xc0ef2610.
Preloaded elf module /boot/kernel/acpi.ko at 0xc0ef26c0.
Calibrating clock(s) ... i8254 clock: 1193200 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter i8254 frequency 1193182 Hz quality 0
Calibrating TSC clock ... TSC clock: 2999672289 Hz
CPU: Intel(R) Core(TM)2 Duo CPU E6850 @ 3.00GHz (2999.67-MHz 686-class CPU)
Origin = GenuineIntel Id = 0x6fb Stepping = 11
Features=0xbfebfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE
Features2=0xe3fdSSE3,RSVD2,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,CX16,xTPR,PDCM
AMD Features=0x2010NX,LM
AMD Features2=0x1LAHF
Cores per package: 2
Instruction TLB: 4 KB Pages, 4-way set associative, 128 entries
1st-level instruction cache: 32 KB, 8-way set associative, 64 byte line size
1st-level data cache: 32 KB, 8-way set associative, 64 byte line size
L2 cache: 4096 kbytes, 16-way associative, 64 bytes/line
real memory = 2146697216 (2047 MB)
Physical memory chunk(s):
Re: Panic with usb serial
Jeremy Chadwick wrote: On Sat, Mar 29, 2008 at 10:11:04PM +, Vince wrote: Is it expected that removing a usb serial adapter while you have a connection (eg tip) using it will panic a -stable system? I know it is expected if you remove a mounted umass device so wanted to see if its known behavior for serial before I file a pr. (adapter is FTDI usb serial converter, class 0/0, rev 1.10/4.00, addr 3) -stable version as of the 25th march, (may have existed before but the first time I forgot to close tip before removing the device was on this version.) I would expect that the problem is identical in the sense that with a connection established, you have an open file descriptor which is associated with a serial device that uses USB. So, yes, I would expect this behaviour based on the track record. Should it happen? The answer is no. File a PR? Also, I'd like to know what USB serial adapter you're using (brand, model, and a website of it if possible), for unrelated reasons. Thanks! About what I was expecting but just thought I'd check. Will file a PR tomorrow when my wife isnt browsing facebook on that laptop :) Regarding the USB serial adapter, I was supplied it though work a while back. I believe from my rather fuzzy memory we got it though these guys http://www.usbnow.co.uk/Cables-USB_to_RS232_Cables/c1_23/index.html Although I wouldn't swear to it. I'll have an ask if anyone remembers on monday. Vince ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
USB-Serial converters [Was: Panic with usb serial]
On Sat, Mar 29, 2008 at 03:20:49PM -0700, Jeremy Chadwick wrote: Also, I'd like to know what USB serial adapter you're using (brand, model, and a website of it if possible), for unrelated reasons. Thanks! The Cables Unlimited USB-Serial adapter from TigerDirect[1] is based on the FTDI chipset and works really well. It supports up to 1MBps and can do non-standard rates (in -CURRENT). That said, we've got pretty comprehensive support for USB-serial converters. I've bought five or six different ones, with the Cables Unlimited one being the most expensive, and they're all supported. The cheaper ones I've tried either don't do arbitrary rates, support only up to 115200, or occasionally drop characters under continuous communication though. [1] http://www.tigerdirect.ca/applications/SearchTools/item-details.asp?EdpNo=1104139CatId=447 -Ed ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PCI add-in parallel port problem
On Sun, Mar 30, 2008 at 10:05:09AM +1100, Richard Perini wrote:
Hi,
I'm trying to get a PCI-express add-in parallel port card working with
7.0-STABLE, and after trying the following, I'm unable to get it to
attach to the ppc bus. The card has a MosChip NM9805 chip. Motherboard
is an ASUS P5E64 WS. (which of course has no on-board parallel port).
The card seems to be recognised by the puc layer.
I've added
device puc
to the kernel config file, and added
{ 0x9710, 0x9805, 0x, 0,
MosChip NM9805 Dual 1284 Printer port,
0,
PUC_PORT_2P, 0x10, 8, 0,
},
to sys/dev/puc/pucdata.c and with verbose booting, get the following
extracts from dmesg: (full dmesg attached below)
pcib3: slot 0 INTB hardwired to IRQ 17
pcib4: slot 1 INTA is routed to irq 17
pcib5: slot 0 INTA is routed to irq 17
pcib6: slot 0 INTA is routed to irq 17
ppc0: Reserved 0x8 bytes for rid 0x10 type 4 at 0xdc00
ppc0: using extended I/O port range
puc0: MosChip NM9805 Dual 1284 Printer port port
0xdc00-0xdc07,0xd880-0xd887,0xd800-0xd807,0xd480-0xd487,0xd400-0xd407,0xd080-0xd08f
irq 17 at device 0.0 on pci10
pcib6: puc0 requested I/O range 0xdc00-0xdc07: in range
pcib5: puc0 requested I/O range 0xdc00-0xdc07: in range
pcib4: puc0 requested I/O range 0xdc00-0xdc07: in range
pcib3: puc0 requested I/O range 0xdc00-0xdc07: in range
puc0: Reserved 0x8 bytes for rid 0x18 type 4 at 0xd800
puc0: [FILTER]
ppc0: using extended I/O port range
ppc0: using extended I/O port range
[ and later ]
ppc0: parallel port not found.
ppc0: Parallel port failed to probe at irq 7 on isa0
Any suggestions would be appreciated.
Take a look in /boot/device.hints
Do you have any lines in there referring to ppc0 ?
If so try commenting them out.
--
Insert your favourite quote here.
Erik Trulsson
[EMAIL PROTECTED]
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: PCI add-in parallel port problem
On Sun, Mar 30, 2008 at 12:56:31AM +0100, Erik Trulsson wrote:
On Sun, Mar 30, 2008 at 10:05:09AM +1100, Richard Perini wrote:
Hi,
I'm trying to get a PCI-express add-in parallel port card working with
7.0-STABLE, and after trying the following, I'm unable to get it to
attach to the ppc bus. The card has a MosChip NM9805 chip. Motherboard
is an ASUS P5E64 WS. (which of course has no on-board parallel port).
The card seems to be recognised by the puc layer.
I've added
device puc
to the kernel config file, and added
{ 0x9710, 0x9805, 0x, 0,
MosChip NM9805 Dual 1284 Printer port,
0,
PUC_PORT_2P, 0x10, 8, 0,
},
to sys/dev/puc/pucdata.c and with verbose booting, get the following
extracts from dmesg: (full dmesg attached below)
pcib3: slot 0 INTB hardwired to IRQ 17
pcib4: slot 1 INTA is routed to irq 17
pcib5: slot 0 INTA is routed to irq 17
pcib6: slot 0 INTA is routed to irq 17
ppc0: Reserved 0x8 bytes for rid 0x10 type 4 at 0xdc00
ppc0: using extended I/O port range
puc0: MosChip NM9805 Dual 1284 Printer port port
0xdc00-0xdc07,0xd880-0xd887,0xd800-0xd807,0xd480-0xd487,0xd400-0xd407,0xd080-0xd08f
irq 17 at device 0.0 on pci10
pcib6: puc0 requested I/O range 0xdc00-0xdc07: in range
pcib5: puc0 requested I/O range 0xdc00-0xdc07: in range
pcib4: puc0 requested I/O range 0xdc00-0xdc07: in range
pcib3: puc0 requested I/O range 0xdc00-0xdc07: in range
puc0: Reserved 0x8 bytes for rid 0x18 type 4 at 0xd800
puc0: [FILTER]
ppc0: using extended I/O port range
ppc0: using extended I/O port range
[ and later ]
ppc0: parallel port not found.
ppc0: Parallel port failed to probe at irq 7 on isa0
Any suggestions would be appreciated.
Take a look in /boot/device.hints
Do you have any lines in there referring to ppc0 ?
If so try commenting them out.
Thanks for the suggestion, Erik.
I commented out
hint.ppc.0.at=isa
hint.ppc.0.irq=7
from /boot/device.hints and that got rid of
ppc0: parallel port not found.
ppc0: Parallel port failed to probe at irq 7 on isa0
from dmesg, but unfortunately nothing else changed.
--
Richard Perini
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB-Serial converters [Was: Panic with usb serial]
On Sat, Mar 29, 2008 at 07:34:30PM -0400, Ed Maste wrote: On Sat, Mar 29, 2008 at 03:20:49PM -0700, Jeremy Chadwick wrote: Also, I'd like to know what USB serial adapter you're using (brand, model, and a website of it if possible), for unrelated reasons. Thanks! The Cables Unlimited USB-Serial adapter from TigerDirect[1] is based on the FTDI chipset and works really well. It supports up to 1MBps and can do non-standard rates (in -CURRENT). That said, we've got pretty comprehensive support for USB-serial converters. I've bought five or six different ones, with the Cables Unlimited one being the most expensive, and they're all supported. The cheaper ones I've tried either don't do arbitrary rates, support only up to 115200, or occasionally drop characters under continuous communication though. [1] http://www.tigerdirect.ca/applications/SearchTools/item-details.asp?EdpNo=1104139CatId=447 I was looking to pick up a few (one for my laptop which lacks a serial port, and another for around-the-house usage, as serial ports are becoming less and less common on motherboards) which did 9600, 19200, 38400, 57600, and (primarily) 115200 bps reliably and worked with FreeBSD. That adapter is exactly what I'm looking for! Thanks much! :-) -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Generic 2-port PCI Express Serial Card - how to get recognized?
On Sat, Mar 29, 2008 at 03:02:32PM +1030, Daniel O'Connor wrote: On Sat, 29 Mar 2008, Karl Denninger wrote: Hi folks; I have a generic PCI Express dumb (16550 allegedly) serial card that goes in a PCI Express slot. FreeBSD doesn't see it, which I assume has to do with the card's vendor ID not being in the table that FreeBSD reocognizes. How do I get the ID from the probe (and/or probe the bus when the machine is running?) - I assume I could add the vendor ID to the sio_pci.c module and it MIGHT work, yes? It doesn't have a specific brand and documentation is basically zilch; I figured it might work right out of the box, but so far, no joy. Have you tried loading puc? Unfortunately I think you will need to recompile your kernel because it is not in GENERIC and not available as a module. Look at /usr/src/sys/dev/puc/pucdata.c for a list of vendor/device IDs (and add yours if it isn't there). That did it - thanks! Works fine... -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant Kids Rights Activist http://www.denninger.netMy home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.comMusings Of A Sentient Mind ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Panic with usb serial
In message: [EMAIL PROTECTED] Jeremy Chadwick [EMAIL PROTECTED] writes: : On Sat, Mar 29, 2008 at 10:11:04PM +, Vince wrote: : Is it expected that removing a usb serial adapter while you have a : connection (eg tip) using it will panic a -stable system? I know it is : expected if you remove a mounted umass device so wanted to see if its known : behavior for serial before I file a pr. (adapter is FTDI usb serial : converter, class 0/0, rev 1.10/4.00, addr 3) : -stable version as of the 25th march, (may have existed before but the : first time I forgot to close tip before removing the device was on this : version.) : : I would expect that the problem is identical in the sense that with a : connection established, you have an open file descriptor which is : associated with a serial device that uses USB. : : So, yes, I would expect this behaviour based on the track record. : Should it happen? The answer is no. File a PR? : : Also, I'd like to know what USB serial adapter you're using (brand, : model, and a website of it if possible), for unrelated reasons. Thanks! That's odd, because I use an FTDI based serial device all the time for hacking on embedded systems. The problem that I have is 100% CPU usage on a tip process until I kill it. Warner ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_7 tinderbox] failure on i386/i386
TB --- 2008-03-30 00:27:28 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-03-30 00:27:28 - starting RELENG_7 tinderbox run for i386/i386 TB --- 2008-03-30 00:27:28 - cleaning the object tree TB --- 2008-03-30 00:27:49 - cvsupping the source tree TB --- 2008-03-30 00:27:49 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/i386/i386/supfile TB --- 2008-03-30 00:27:57 - building world (CFLAGS=-O2 -pipe) TB --- 2008-03-30 00:27:57 - cd /src TB --- 2008-03-30 00:27:57 - /usr/bin/make -B buildworld World build started on Sun Mar 30 00:27:59 UTC 2008 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Sun Mar 30 01:30:19 UTC 2008 TB --- 2008-03-30 01:30:19 - generating LINT kernel config TB --- 2008-03-30 01:30:19 - cd /src/sys/i386/conf TB --- 2008-03-30 01:30:19 - /usr/bin/make -B LINT TB --- 2008-03-30 01:30:19 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-03-30 01:30:19 - cd /src TB --- 2008-03-30 01:30:19 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Sun Mar 30 01:30:19 UTC 2008 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/fs/ntfs/ntfs_iconv.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/fs/ntfs/ntfs_ihash.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -Werror -pg -mprofiler-epilogue /src/sys/fs/ntfs/ntfs_subr.c /src/sys/fs/ntfs/ntfs_subr.c:468:66: error: macro lockmgr requires 4 arguments, but only 3 given /src/sys/fs/ntfs/ntfs_subr.c: In function 'ntfs_ntput': /src/sys/fs/ntfs/ntfs_subr.c:468: error: 'lockmgr' undeclared (first use in this function) /src/sys/fs/ntfs/ntfs_subr.c:468: error: (Each undeclared identifier is reported only once /src/sys/fs/ntfs/ntfs_subr.c:468: error: for each function it appears in.) *** Error code 1 Stop in /obj/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-03-30 01:38:48 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-03-30 01:38:48 - ERROR: failed to build lint kernel TB --- 2008-03-30 01:38:48 - tinderbox aborted TB --- 3638.72 user 375.27 system 4279.72 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-i386-i386.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_7 tinderbox] failure on i386/pc98
TB --- 2008-03-30 01:38:48 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-03-30 01:38:48 - starting RELENG_7 tinderbox run for i386/pc98 TB --- 2008-03-30 01:38:48 - cleaning the object tree TB --- 2008-03-30 01:39:05 - cvsupping the source tree TB --- 2008-03-30 01:39:05 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/i386/pc98/supfile TB --- 2008-03-30 01:39:12 - building world (CFLAGS=-O2 -pipe) TB --- 2008-03-30 01:39:12 - cd /src TB --- 2008-03-30 01:39:12 - /usr/bin/make -B buildworld World build started on Sun Mar 30 01:39:13 UTC 2008 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Sun Mar 30 02:41:20 UTC 2008 TB --- 2008-03-30 02:41:20 - generating LINT kernel config TB --- 2008-03-30 02:41:20 - cd /src/sys/pc98/conf TB --- 2008-03-30 02:41:20 - /usr/bin/make -B LINT TB --- 2008-03-30 02:41:20 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-03-30 02:41:20 - cd /src TB --- 2008-03-30 02:41:20 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Sun Mar 30 02:41:21 UTC 2008 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -pg -mprofiler-epilogue /src/sys/fs/ntfs/ntfs_iconv.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -pg -mprofiler-epilogue /src/sys/fs/ntfs/ntfs_ihash.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=8000 --param inline-unit-growth=100 --param large-function-growth=1000 -DGPROF -falign-functions=16 -DGPROF4 -DGUPROF -fno-builtin -mno-align-long-strings -mpreferred-stack-boundary=2 -mno-mmx -mno-3dnow -mno-sse -mno-sse2 -mno-sse3 -ffreestanding -pg -mprofiler-epilogue /src/sys/fs/ntfs/ntfs_subr.c /src/sys/fs/ntfs/ntfs_subr.c:468:66: error: macro lockmgr requires 4 arguments, but only 3 given /src/sys/fs/ntfs/ntfs_subr.c: In function 'ntfs_ntput': /src/sys/fs/ntfs/ntfs_subr.c:468: error: 'lockmgr' undeclared (first use in this function) /src/sys/fs/ntfs/ntfs_subr.c:468: error: (Each undeclared identifier is reported only once /src/sys/fs/ntfs/ntfs_subr.c:468: error: for each function it appears in.) *** Error code 1 Stop in /obj/pc98/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-03-30 02:48:21 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-03-30 02:48:21 - ERROR: failed to build lint kernel TB --- 2008-03-30 02:48:21 - tinderbox aborted TB --- 3510.82 user 375.17 system 4172.76 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-i386-pc98.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
gjournal....
Hi folks; Wondering about the various pros and cons of using the gjournal GEOM provider... and if you can promote and existing system using it, or whether you need to build something anew. The scenario is a fairly busy and large system with PostgreSQL database data on it. The data is currently on a 2-disk gmirror pair to provide data safety in the event of a disk failure. I am using softupdates right now. If I'm reading the docs correctly, I can't put gjournal in use on the existing filesystem, and need to effectively build a new disk structure then copy over the data onto it. Can you boot from a gjournal'd root? Ideas please, pros and cons of the various alternatives, etc. thanks! -- -- Karl Denninger ([EMAIL PROTECTED]) Internet Consultant Kids Rights Activist http://www.denninger.netMy home on the net - links to everything I do! http://scubaforum.org Your UNCENSORED place to talk about DIVING! http://genesis3.blogspot.comMusings Of A Sentient Mind ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
[releng_7 tinderbox] failure on ia64/ia64
TB --- 2008-03-30 01:44:31 - tinderbox 2.3 running on freebsd-stable.sentex.ca TB --- 2008-03-30 01:44:31 - starting RELENG_7 tinderbox run for ia64/ia64 TB --- 2008-03-30 01:44:31 - cleaning the object tree TB --- 2008-03-30 01:44:45 - cvsupping the source tree TB --- 2008-03-30 01:44:45 - /usr/bin/csup -r 3 -g -L 1 -h localhost -s /tinderbox/RELENG_7/ia64/ia64/supfile TB --- 2008-03-30 01:44:51 - building world (CFLAGS=-O2 -pipe) TB --- 2008-03-30 01:44:51 - cd /src TB --- 2008-03-30 01:44:51 - /usr/bin/make -B buildworld World build started on Sun Mar 30 01:44:52 UTC 2008 Rebuilding the temporary build tree stage 1.1: legacy release compatibility shims stage 1.2: bootstrap tools stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3: cross tools stage 4.1: building includes stage 4.2: building libraries stage 4.3: make dependencies stage 4.4: building everything World build completed on Sun Mar 30 03:08:02 UTC 2008 TB --- 2008-03-30 03:08:02 - generating LINT kernel config TB --- 2008-03-30 03:08:02 - cd /src/sys/ia64/conf TB --- 2008-03-30 03:08:02 - /usr/bin/make -B LINT TB --- 2008-03-30 03:08:02 - building LINT kernel (COPTFLAGS=-O2 -pipe) TB --- 2008-03-30 03:08:02 - cd /src TB --- 2008-03-30 03:08:02 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Sun Mar 30 03:08:03 UTC 2008 stage 1: configuring the kernel stage 2.1: cleaning up the object tree stage 2.2: rebuilding the object tree stage 2.3: build tools stage 3.1: making dependencies stage 3.2: building everything [...] cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/fs/ntfs/ntfs_iconv.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/fs/ntfs/ntfs_ihash.c cc -c -O2 -pipe -fno-strict-aliasing -std=c99 -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -Wundef -Wno-pointer-sign -fformat-extensions -nostdinc -I. -I/src/sys -I/src/sys/contrib/altq -I/src/sys/contrib/ia64/libuwx/src -D_KERNEL -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common -finline-limit=15000 --param inline-unit-growth=100 --param large-function-growth=1000 -fno-builtin -mconstant-gp -ffixed-r13 -mfixed-range=f32-f127 -fpic -ffreestanding -Werror /src/sys/fs/ntfs/ntfs_subr.c /src/sys/fs/ntfs/ntfs_subr.c:468:66: error: macro lockmgr requires 4 arguments, but only 3 given /src/sys/fs/ntfs/ntfs_subr.c: In function 'ntfs_ntput': /src/sys/fs/ntfs/ntfs_subr.c:468: error: 'lockmgr' undeclared (first use in this function) /src/sys/fs/ntfs/ntfs_subr.c:468: error: (Each undeclared identifier is reported only once /src/sys/fs/ntfs/ntfs_subr.c:468: error: for each function it appears in.) *** Error code 1 Stop in /obj/ia64/src/sys/LINT. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2008-03-30 03:17:29 - WARNING: /usr/bin/make returned exit code 1 TB --- 2008-03-30 03:17:29 - ERROR: failed to build lint kernel TB --- 2008-03-30 03:17:29 - tinderbox aborted TB --- 4897.02 user 379.75 system 5577.87 real http://tinderbox.des.no/tinderbox-releng_7-RELENG_7-ia64-ia64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Panic with usb serial
On Sat, Mar 29, 2008 at 10:11:04PM +, Vince wrote: Hi all, Is it expected that removing a usb serial adapter while you have a connection (eg tip) using it will panic a -stable system? I know it is expected if you remove a mounted umass device so wanted to see if its known behavior for serial before I file a pr. (adapter is FTDI usb serial converter, class 0/0, rev 1.10/4.00, addr 3) -stable version as of the 25th march, (may have existed before but the first time I forgot to close tip before removing the device was on this version.) What is the exact version number of your system ? There are two supported stable branch now. pgpLyLqVJwIJ4.pgp Description: PGP signature
