make release stop at Creating ISO imagess
hi sirs, apologized me for disturbing this list but ireally have problem s. i make my own release by follwoing document in releng articles. here is my command cd /usr/src/release time make CHROOTDIR=/kaitag/KAITAG BUILDNAME=7.2-RELEASE \ CVSROOT=/var/ftp/pub/ncvs RELEASETAG=RELENG_7_2_0_RELEASE \ EXTSRCDIR=/usr/src EXTPORTSDIR=/usr/ports \ DOC_LANG=en_US.ISO8859-1 NODOC=NO NOPORTS=NO \ MAKE_DVD=YES MAKE_ISOS=YES CDROM=YES RELEASEDISTFILES=/var/ftp/pub/distfiles \ release the build process goes well but then fetching for cdrtools.tbz begin and stop. in my machine i have installed cdrtools and there is also mkisofs file so i wonder why the script /usr/src/release/i386/mkisofsimages.sh still fetching for cdrtools. and here is my uname of my machine wmc# uname -a FreeBSD wmc.tint.or.th 7.2-RELEASE FreeBSD KAITAG #0: Wed Oct 21 14:36:40 ICT 2009 r...@wmc.tint.or.th:/usr/obj/usr/src/sys/WMC i386 wmc# i set UNAME_r=7.2-RELEASE in /etc/make.conf though. many thanks in advance for any helps and hints. with best regards, psr -- มะไฟ ฅนเหลิงฟ้า มะขาม คินเดินดน http://makham.blogspot.com This message was sent using IMP, the Internet Messaging Program. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Help troubleshooting...
On Monday 26 October 2009 01:05:03 n...@ever.sanda.gr.jp wrote: M. Warner Losh wrote: I have a usb stick (8GB) on it. This stick has about 5GB of junk on it at this point. I tried to do 'cat * /dev/null' recently, to measure how fast it goes. It got about 1GB into the drive and then I got device missing messages. So devfs thinks the device went missing: Warner-san, maybe it is caused by the hardware problem on the USB flash memory. Some chip on the memory might have too much heat when you access the memory at fast rate. Then it stops working. What happens if you read from two USB disks at the same time? If the device went missing the USB HUB signalled that. This is maybe an indication that the USB firmware on the device crashed. Maybe this is due to heat, or unhandled race conditions when the load goes high. Try using dd and vary the block size from 512 to 65536 bytes. Does it stop working with all block sizes over time? --HPS ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: make release stop at Creating ISO imagess
Quoting Ruben de Groot mai...@bzerk.org: On Mon, Oct 26, 2009 at 02:36:39PM +0700, ??? ? typed: hi sirs, apologized me for disturbing this list but ireally have problem s. i make my own release by follwoing document in releng articles. here is my command cd /usr/src/release time make CHROOTDIR=/kaitag/KAITAG BUILDNAME=7.2-RELEASE \ CVSROOT=/var/ftp/pub/ncvs RELEASETAG=RELENG_7_2_0_RELEASE \ EXTSRCDIR=/usr/src EXTPORTSDIR=/usr/ports \ DOC_LANG=en_US.ISO8859-1 NODOC=NO NOPORTS=NO \ MAKE_DVD=YES MAKE_ISOS=YES CDROM=YES RELEASEDISTFILES=/var/ftp/pub/distfiles \ release the build process goes well but then fetching for cdrtools.tbz begin and stop. in my machine i have installed cdrtools and there is also mkisofs file so i wonder why the script /usr/src/release/i386/mkisofsimages.sh still fetching for cdrtools. Do you have the cdrtools.tbz package in /var/ftp/pub/distfiles ? thanks for your time but there is only cdrtools-2.01.tar.bz2 which is source files for making cdrtools. i keep all packages in a separate location, /usr/ports/packages/. Ruben with best regards, -- psr มะฃาม ฅินเดินดน มะไฟ ฅนเหลิงฟ้า http://makham.blogspot.com This message was sent using IMP, the Internet Messaging Program. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Help troubleshooting...
But there was no indication the device went missing on the console. And it wasn't until I unplugged it that da0 detached. Usually in the past when it has started throwing errors the console was chatty about why. Warner On Oct 26, 2009, at 2:59 AM, Hans Petter Selasky hsela...@c2i.net wrote: On Monday 26 October 2009 01:05:03 n...@ever.sanda.gr.jp wrote: M. Warner Losh wrote: I have a usb stick (8GB) on it. This stick has about 5GB of junk on it at this point. I tried to do 'cat * /dev/null' recently, to measure how fast it goes. It got about 1GB into the drive and then I got device missing messages. So devfs thinks the device went missing: Warner-san, maybe it is caused by the hardware problem on the USB flash memory. Some chip on the memory might have too much heat when you access the memory at fast rate. Then it stops working. What happens if you read from two USB disks at the same time? If the device went missing the USB HUB signalled that. This is maybe an indication that the USB firmware on the device crashed. Maybe this is due to heat, or unhandled race conditions when the load goes high. Try using dd and vary the block size from 512 to 65536 bytes. Does it stop working with all block sizes over time? --HPS ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: help needed to fix contrib/ee crash/exit when receiving SIGWINCH
Eygene Ryabinkin schrieb am 2009-10-24: Ed, good day. Fri, Oct 23, 2009 at 07:13:01PM +0200, Ed Schouten wrote: Have you sent it to Thomas Dickey as well? Sent the patch to bug-ncur...@gnu.org. Do you think that I should send it to Thomas directly as well? the patch got committed by thomas and is included in ncurses-5.7-20091024.patch.gz. i guess it will be included in our base version of ncurses once 5.8 gets released, but the patch should quickly make it into the port version of ncurses. alex ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: help needed to fix contrib/ee crash/exit when receiving SIGWINCH
Dag-Erling Smørgrav schrieb am 2009-10-25: Alexander Best alexbes...@math.uni-muenster.de writes: i just tried building ee under linux without using new_curse.c and linking the executable against ncurses. running the binary is showing the same problems with SIGWINCH. so if this is in fact caused by a ncurses bug the bug appears in linux ncurses too. No surprise, it's the same as ours. DES this was when we weren't sure if the problem was entirely ncurses-related. could have also been that linux was including the ncurses patches which get released by thomas dickey every now and then. i'm not entirely sure but i think the version in the base dir we use is the unpatched 5.7 release of ncurses. alex ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: make release stop at Creating ISO imagess
On Mon, Oct 26, 2009 at 02:36:39PM +0700, ??? ? typed: hi sirs, apologized me for disturbing this list but ireally have problem s. i make my own release by follwoing document in releng articles. here is my command cd /usr/src/release time make CHROOTDIR=/kaitag/KAITAG BUILDNAME=7.2-RELEASE \ CVSROOT=/var/ftp/pub/ncvs RELEASETAG=RELENG_7_2_0_RELEASE \ EXTSRCDIR=/usr/src EXTPORTSDIR=/usr/ports \ DOC_LANG=en_US.ISO8859-1 NODOC=NO NOPORTS=NO \ MAKE_DVD=YES MAKE_ISOS=YES CDROM=YES RELEASEDISTFILES=/var/ftp/pub/distfiles \ release the build process goes well but then fetching for cdrtools.tbz begin and stop. in my machine i have installed cdrtools and there is also mkisofs file so i wonder why the script /usr/src/release/i386/mkisofsimages.sh still fetching for cdrtools. Do you have the cdrtools.tbz package in /var/ftp/pub/distfiles ? Ruben ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Help troubleshooting...
In message: 200910260959.20772.hsela...@c2i.net Hans Petter Selasky hsela...@c2i.net writes: : On Monday 26 October 2009 01:05:03 n...@ever.sanda.gr.jp wrote: : M. Warner Losh wrote: : I have a usb stick (8GB) on it. This stick has about 5GB of junk on : it at this point. : : I tried to do 'cat * /dev/null' recently, to measure how fast it : goes. It got about 1GB into the drive and then I got device missing : messages. : : So devfs thinks the device went missing: : : Warner-san, maybe it is caused by the hardware problem on the USB flash : memory. Some chip on the memory might have too much heat when you access : the memory at fast rate. Then it stops working. : : : What happens if you read from two USB disks at the same time? I know that the august 25th version failed badly when I tried to burn DVDs from a USB drive to a USB attached DVD burner. This used to work flawlessly. : If the device went missing the USB HUB signalled that. This is maybe an : indication that the USB firmware on the device crashed. Maybe this is due to : heat, or unhandled race conditions when the load goes high. This same flash drive will do 20MB sustained on windows without a glitch using similar commands. : Try using dd and vary the block size from 512 to 65536 bytes. Does it stop : working with all block sizes over time? Once I get the message I posted, it is lights out for da0. No further access to the drive works at all. Warner ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Help troubleshooting...
On Monday 26 October 2009 12:48:16 M. Warner Losh wrote: I know that the august 25th version failed badly when I tried to burn DVDs from a USB drive to a USB attached DVD burner. This used to work flawlessly. Hi, There has been a recent fix to the EHCI driver, which might affect Mass Storage when short transfers are used. Also someone else has pointed out that certain VIA chipsets have an IRQ bug requiring the need for a software callout to restart the EHCI interrupt handler. This is not yet patched, hence I don't know if this is a real issue. http://svn.freebsd.org/viewvc/base?view=revisionrevision=197682 Is your code from after 1st of October? --HPS ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Help troubleshooting...
On Monday 26 October 2009 12:48:16 M. Warner Losh wrote: In message: 200910260959.20772.hsela...@c2i.net Hans Petter Selasky hsela...@c2i.net writes: : On Monday 26 October 2009 01:05:03 n...@ever.sanda.gr.jp wrote: : M. Warner Losh wrote: : I have a usb stick (8GB) on it. This stick has about 5GB of junk on : it at this point. : : I tried to do 'cat * /dev/null' recently, to measure how fast it : goes. It got about 1GB into the drive and then I got device missing : messages. : : So devfs thinks the device went missing: : : Warner-san, maybe it is caused by the hardware problem on the USB flash : memory. Some chip on the memory might have too much heat when you : access the memory at fast rate. Then it stops working. : : What happens if you read from two USB disks at the same time? I know that the august 25th version failed badly when I tried to burn DVDs from a USB drive to a USB attached DVD burner. This used to work flawlessly. : If the device went missing the USB HUB signalled that. This is maybe an : indication that the USB firmware on the device crashed. Maybe this is due : to heat, or unhandled race conditions when the load goes high. This same flash drive will do 20MB sustained on windows without a glitch using similar commands. : Try using dd and vary the block size from 512 to 65536 bytes. Does it : stop working with all block sizes over time? Once I get the message I posted, it is lights out for da0. No further access to the drive works at all. Make sure your driver has got sufficiently enough power, if powered over USB. --HPS ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: help needed to fix contrib/ee crash/exit when receiving SIGWINCH
On Mon, Oct 26, 2009 at 11:44:14AM +0100, Alexander Best wrote: Eygene Ryabinkin schrieb am 2009-10-24: Ed, good day. Fri, Oct 23, 2009 at 07:13:01PM +0200, Ed Schouten wrote: Have you sent it to Thomas Dickey as well? Sent the patch to bug-ncur...@gnu.org. Do you think that I should send it to Thomas directly as well? the patch got committed by thomas and is included in ncurses-5.7-20091024.patch.gz. i guess it will be included in our base version of ncurses once 5.8 gets released, but the patch should quickly make it into the port version of ncurses. devel/ncurses-devel will be updated this week. For base's ncurses, I'll check with Thomas Dickey to see if there will be 5.8 soon. If not, we can also import a recent snapshot. Thanks, Rong-En Fan pgp0ojXYkOoIt.pgp Description: PGP signature
Re: help needed to fix contrib/ee crash/exit when receiving SIGWINCH
Rong-En Fan ra...@freebsd.org writes: devel/ncurses-devel will be updated this week. For base's ncurses, I'll check with Thomas Dickey to see if there will be 5.8 soon. If not, we can also import a recent snapshot. There is no reason to wait, nor to import an entire snapshot. Se my earlier message to Alexander. DES -- Dag-Erling Smørgrav - d...@des.no ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Help troubleshooting...
In message: 200910261258.08135.hsela...@c2i.net Hans Petter Selasky hsela...@c2i.net writes: : On Monday 26 October 2009 12:48:16 M. Warner Losh wrote: : I know that the august 25th version failed badly when I tried to burn : DVDs from a USB drive to a USB attached DVD burner. This used to work : flawlessly. : : Hi, : : There has been a recent fix to the EHCI driver, which might affect Mass : Storage when short transfers are used. : : Also someone else has pointed out that certain VIA chipsets have an IRQ bug : requiring the need for a software callout to restart the EHCI interrupt : handler. This is not yet patched, hence I don't know if this is a real issue. : : http://svn.freebsd.org/viewvc/base?view=revisionrevision=197682 : : Is your code from after 1st of October? This code is from: FreeBSD lighthouse 9.0-CURRENT FreeBSD 9.0-CURRENT #41 r185338:198411M: Fri Oct 23 10:08:48 MDT 2009 i...@lighthouse:/cache/svn/head/sys/amd64/compile/LIGHTHOUSE amd64 so it would have r197682 baked in (the first number in my rev string is a mystery to me). Re another post: This is a 8GB flash, so I'm sure that there's enough power. Looking at the dmesg, this happend the second or third time I'd plugged in this flash drive. Here's a partial dmesg for usb things: CPU: AMD Turion(tm) 64 Mobile Technology ML-37 (1994.21-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x20f42 Stepping = 2 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2 Features2=0x1SSE3 AMD Features=0xe2500800SYSCALL,NX,MMX+,FFXSR,LM,3DNow!+,3DNow! AMD Features2=0x1LAHF real memory = 2147483648 (2048 MB) avail memory = 2059546624 (1964 MB) ACPI APIC Table: PTLTD APIC MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 2.1 irqs 0-23 on motherboard ... pcib2: ACPI PCI-PCI bridge at device 5.0 on pci0 pci2: ACPI PCI bus on pcib2 ohci0: ATI SB400 USB Controller mem 0xc000-0xcfff irq 19 at device 19.0 on pci0 Activate PA 0xc000 at VA 0xff00c000 ohci0: [ITHREAD] usbus0: ATI SB400 USB Controller on ohci0 ohci1: ATI SB400 USB Controller mem 0xc0001000-0xc0001fff irq 19 at device 19.1 on pci0 Activate PA 0xc0001000 at VA 0xff00c0001000 ohci1: [ITHREAD] usbus1: ATI SB400 USB Controller on ohci1 ehci0: ATI SB400 USB 2.0 controller mem 0xc0002000-0xc0002fff irq 19 at device 19.2 on pci0 Activate PA 0xc0002000 at VA 0xff00c0002000 ehci0: [ITHREAD] usbus2: EHCI version 1.0 usbus2: ATI SB400 USB 2.0 controller on ehci0 ... Timecounter TSC frequency 1994209008 Hz quality 800 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 480Mbps High Speed USB v2.0 Status is 0x3106 ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=80 wire Activate i/o 0x8014 Activate i/o 0x8015 ugen0.1: ATI at usbus0 uhub0: ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus0 ugen1.1: ATI at usbus1 uhub1: ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus1 ugen2.1: ATI at usbus2 uhub2: ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1 on usbus2 ad0: 114473MB FUJITSU MHV2120AT PL 008300A1 at ata0-master UDMA100 GEOM: ad0s2: geometry does not match label (255h,63s != 16h,63s). uhub0: 4 ports with 4 removable, self powered uhub1: 4 ports with 4 removable, self powered ... Root mount waiting for: usbus2 uhub2: 8 ports with 8 removable, self powered Root mount waiting for: usbus2 Trying to mount root from ufs:/dev/ad0s2a ugen0.2: Broadcom Corp at usbus0 ubt0: Broadcom Corp HP Integrated Module, class 224/1, rev 2.00/1.00, addr 2 on usbus0 usb_alloc_device:1635: getting device descriptor at addr 2 failed, USB_ERR_TIMEOUT! ugen2.2: HP at usbus2 umass0: HP v125w, class 0/0, rev 2.00/1.10, addr 2 on usbus2 umass0: SCSI over Bulk-Only; quirks = 0x umass0:2:0:-1: Attached to scbus2 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 da0: HP v125w PMAP Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 7660MB (15687680 512 byte sectors: 255H 63S/T 976C) ugen2.2: HP at usbus2 (disconnected) umass0: at uhub2, port 6, addr 2 (disconnected) (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): Invalidating pack g_vfs_done():da0s1[READ(offset=5298202624, length=65536)]error = 6 g_vfs_done():da0s1[READ(offset=5298268160, length=65536)]error = 6 g_vfs_done():da0s1[READ(offset=5298333696, length=65536)]error = 6 g_vfs_done():da0s1[WRITE(offset=1976320, length=32768)]error = 6 g_vfs_done():da0s1[READ(offset=5298137088, length=65536)]error = 6 (da0:umass-sim0:0:0:0):
Re: Help troubleshooting...
On Monday 26 October 2009 14:01:17 M. Warner Losh wrote: In message: 200910261258.08135.hsela...@c2i.net Hans Petter Selasky hsela...@c2i.net writes: : On Monday 26 October 2009 12:48:16 M. Warner Losh wrote: : I know that the august 25th version failed badly when I tried to burn : DVDs from a USB drive to a USB attached DVD burner. This used to work : flawlessly. : : Hi, : : There has been a recent fix to the EHCI driver, which might affect Mass : Storage when short transfers are used. : : Also someone else has pointed out that certain VIA chipsets have an IRQ : bug requiring the need for a software callout to restart the EHCI : interrupt handler. This is not yet patched, hence I don't know if this is : a real issue. : : http://svn.freebsd.org/viewvc/base?view=revisionrevision=197682 : : Is your code from after 1st of October? This code is from: FreeBSD lighthouse 9.0-CURRENT FreeBSD 9.0-CURRENT #41 r185338:198411M: Fri Oct 23 10:08:48 MDT 2009 i...@lighthouse:/cache/svn/head/sys/amd64/compile/LIGHTHOUSE amd64 so it would have r197682 baked in (the first number in my rev string is a mystery to me). Re another post: This is a 8GB flash, so I'm sure that there's enough power. Looking at the dmesg, this happend the second or third time I'd plugged in this flash drive. Here's a partial dmesg for usb things: CPU: AMD Turion(tm) 64 Mobile Technology ML-37 (1994.21-MHz K8-class CPU) Origin = AuthenticAMD Id = 0x20f42 Stepping = 2 Features=0x78bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA ,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2 Features2=0x1SSE3 AMD Features=0xe2500800SYSCALL,NX,MMX+,FFXSR,LM,3DNow!+,3DNow! AMD Features2=0x1LAHF real memory = 2147483648 (2048 MB) avail memory = 2059546624 (1964 MB) ACPI APIC Table: PTLTDAPIC MADT: Forcing active-low polarity and level trigger for SCI ioapic0 Version 2.1 irqs 0-23 on motherboard ... pcib2: ACPI PCI-PCI bridge at device 5.0 on pci0 pci2: ACPI PCI bus on pcib2 ohci0: ATI SB400 USB Controller mem 0xc000-0xcfff irq 19 at device 19.0 on pci0 Activate PA 0xc000 at VA 0xff00c000 ohci0: [ITHREAD] usbus0: ATI SB400 USB Controller on ohci0 ohci1: ATI SB400 USB Controller mem 0xc0001000-0xc0001fff irq 19 at device 19.1 on pci0 Activate PA 0xc0001000 at VA 0xff00c0001000 ohci1: [ITHREAD] usbus1: ATI SB400 USB Controller on ohci1 ehci0: ATI SB400 USB 2.0 controller mem 0xc0002000-0xc0002fff irq 19 at device 19.2 on pci0 Activate PA 0xc0002000 at VA 0xff00c0002000 ehci0: [ITHREAD] usbus2: EHCI version 1.0 usbus2: ATI SB400 USB 2.0 controller on ehci0 ... Timecounter TSC frequency 1994209008 Hz quality 800 Timecounters tick every 1.000 msec usbus0: 12Mbps Full Speed USB v1.0 usbus1: 12Mbps Full Speed USB v1.0 usbus2: 480Mbps High Speed USB v2.0 Status is 0x3106 ata0-master: pio=PIO4 wdma=WDMA2 udma=UDMA100 cable=80 wire Activate i/o 0x8014 Activate i/o 0x8015 ugen0.1: ATI at usbus0 uhub0: ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus0 ugen1.1: ATI at usbus1 uhub1: ATI OHCI root HUB, class 9/0, rev 1.00/1.00, addr 1 on usbus1 ugen2.1: ATI at usbus2 uhub2: ATI EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1 on usbus2 ad0: 114473MB FUJITSU MHV2120AT PL 008300A1 at ata0-master UDMA100 GEOM: ad0s2: geometry does not match label (255h,63s != 16h,63s). uhub0: 4 ports with 4 removable, self powered uhub1: 4 ports with 4 removable, self powered ... Root mount waiting for: usbus2 uhub2: 8 ports with 8 removable, self powered Root mount waiting for: usbus2 Trying to mount root from ufs:/dev/ad0s2a ugen0.2: Broadcom Corp at usbus0 ubt0: Broadcom Corp HP Integrated Module, class 224/1, rev 2.00/1.00, addr 2 on usbus0 usb_alloc_device:1635: getting device descriptor at addr 2 failed, USB_ERR_TIMEOUT! ugen2.2: HP at usbus2 umass0: HP v125w, class 0/0, rev 2.00/1.10, addr 2 on usbus2 umass0: SCSI over Bulk-Only; quirks = 0x umass0:2:0:-1: Attached to scbus2 (probe0:umass-sim0:0:0:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (probe0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (probe0:umass-sim0:0:0:0): SCSI Status: Check Condition (probe0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (probe0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (probe0:umass-sim0:0:0:0): Retrying Command (per Sense Data) da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 da0: HP v125w PMAP Removable Direct Access SCSI-0 device da0: 40.000MB/s transfers da0: 7660MB (15687680 512 byte sectors: 255H 63S/T 976C) ugen2.2: HP at usbus2 (disconnected) umass0: at uhub2, port 6, addr 2 (disconnected) (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): Invalidating pack g_vfs_done():da0s1[READ(offset=5298202624, length=65536)]error = 6 g_vfs_done():da0s1[READ(offset=5298268160, length=65536)]error = 6 g_vfs_done():da0s1[READ(offset=5298333696, length=65536)]error = 6
Re: Help troubleshooting...
M. Warner Losh i...@bsdimp.com writes: FreeBSD lighthouse 9.0-CURRENT FreeBSD 9.0-CURRENT #41 r185338:198411M: Fri Oct 23 10:08:48 MDT 2009 i...@lighthouse:/cache/svn/head/sys/amd64/compile/LIGHTHOUSE amd64 so it would have r197682 baked in (the first number in my rev string is a mystery to me). It means you have an inconsistent tree. The first number is the oldest revision in your tree, the second is the newest, and the M means you have local modifications. Re another post: This is a 8GB flash, so I'm sure that there's enough power. Non sequitur. Bigger chips draw more power. Is it plugged directly into the computer? If not, is it plugged into a powered hub? How many other devices are connected to the computer or hub? DES -- Dag-Erling Smørgrav - d...@des.no ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Help troubleshooting...
In message: 86skd6cmm8@ds4.des.no Dag-Erling_Smørgrav d...@des.no writes: : M. Warner Losh i...@bsdimp.com writes: : FreeBSD lighthouse 9.0-CURRENT FreeBSD 9.0-CURRENT #41 r185338:198411M: Fri Oct 23 10:08:48 MDT 2009 i...@lighthouse:/cache/svn/head/sys/amd64/compile/LIGHTHOUSE amd64 : : so it would have r197682 baked in (the first number in my rev string : is a mystery to me). : : It means you have an inconsistent tree. The first number is the oldest : revision in your tree, the second is the newest, and the M means you : have local modifications. Yes. Of course I have local modifications, but none in the usb stack. But I've also done a svn update from the top of the tree multiple times and this version number persists. : Re another post: This is a 8GB flash, so I'm sure that there's enough : power. : : Non sequitur. Bigger chips draw more power. Is it plugged directly : into the computer? If not, is it plugged into a powered hub? How many : other devices are connected to the computer or hub? Not entirely. This flash has worked in this computer in the past without issues (like a year ago when we were first integrating hpsusb into the tree). This flash is plugged directly into the computer. This behavior is consistent across multiple ports on the computer (so it isn't a bad port). While this doesn't prove it isn't a power issue, the odds are stacked against it being one. If there were a way to get the internal hub to tell me how much power it can deliver, and for me to query the flash to see maximum current draws, we could see if we're close to the edge or not... Warner ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Help troubleshooting...
M. Warner Losh i...@bsdimp.com writes: Yes. Of course I have local modifications, but none in the usb stack. But I've also done a svn update from the top of the tree multiple times and this version number persists. Weird. r185338 was a commit to the old USB stack. Try to run svnversion in sys/dev/usb, and in an unrelated directory such as sys/conf. If there's a difference, run svn stat in sys/dev/usb and see if anything unexpected shows up. DES -- Dag-Erling Smørgrav - d...@des.no ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Help troubleshooting...
On Monday 26 October 2009 14:37:59 M. Warner Losh wrote: In message: 86skd6cmm8@ds4.des.no Dag-Erling_Smørgrav d...@des.no writes: : M. Warner Losh i...@bsdimp.com writes: : FreeBSD lighthouse 9.0-CURRENT FreeBSD 9.0-CURRENT #41 r185338:198411M: : Fri Oct 23 10:08:48 MDT 2009 : i...@lighthouse:/cache/svn/head/sys/amd64/compile/LIGHTHOUSE amd64 : : so it would have r197682 baked in (the first number in my rev string : is a mystery to me). : : It means you have an inconsistent tree. The first number is the oldest : revision in your tree, the second is the newest, and the M means you : have local modifications. Yes. Of course I have local modifications, but none in the usb stack. But I've also done a svn update from the top of the tree multiple times and this version number persists. : Re another post: This is a 8GB flash, so I'm sure that there's enough : power. : : Non sequitur. Bigger chips draw more power. Is it plugged directly : into the computer? If not, is it plugged into a powered hub? How many : other devices are connected to the computer or hub? Hi, Not entirely. This flash has worked in this computer in the past without issues (like a year ago when we were first integrating hpsusb into the tree). Since then there has been at least one patch to improve performance in the EHCI driver. When the cat command stops, could you try to run: usbconfig -u XXX -a YYY dump_device_desc dump_curr_config_desc On that device. Is usbconfig able to extract the string descriptors in the device and config descriptor? Or do you get timeouts? Also check vmstat -i . This flash is plugged directly into the computer. This behavior is consistent across multiple ports on the computer (so it isn't a bad port). While this doesn't prove it isn't a power issue, the odds are stacked against it being one. If there were a way to get the internal hub to tell me how much power it can deliver, and for me to query the flash to see maximum current draws, we could see if we're close to the edge or not... Usually the maximum current is given by the device descriptor, but it might now be the actual value. See usbconfig dump_device_desc. --HPS ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: Help troubleshooting...
In message: 86aazecl00@ds4.des.no Dag-Erling_Smørgrav d...@des.no writes: : M. Warner Losh i...@bsdimp.com writes: : Yes. Of course I have local modifications, but none in the usb stack. : But I've also done a svn update from the top of the tree multiple : times and this version number persists. : : Weird. r185338 was a commit to the old USB stack. Try to run : svnversion in sys/dev/usb, and in an unrelated directory such as : sys/conf. If there's a difference, run svn stat in sys/dev/usb and see : if anything unexpected shows up. % cd sys/dev/usb % svnversion 198411M % cd ../../conf % svnversion 198411M Some more digging down this line shows that there was a dangling merge conflict in sys/i386/conf/GENERIC Warner ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
in_cksum.h for sparc64 missing ifdef KERNEL?
Hi, while trying to cleanup some WARNS issues under sbin/, I noticed that natd(8) fails to compile for sparc64 only, due to missing struct mbuf declaration in in_cksum.h. Comparing that header to other arch's headers leads me to believe an #ifdef is missing. See attached patch, but please note that I do not have the resources to run this through a make universe right now. Regards, Uli 1618[tip] 350410f79434 2009-10-26 21:02 +0100 uqs Put this under KERNEL just like all other arch do. diff -r 5558195fb93d -r 350410f79434 sys/sparc64/include/in_cksum.h --- a/sys/sparc64/include/in_cksum.h Mon Oct 26 19:57:23 2009 +0100 +++ b/sys/sparc64/include/in_cksum.h Mon Oct 26 21:02:06 2009 +0100 @@ -164,6 +164,8 @@ return (__ret); } +#ifdef _KERNEL u_short in_cksum_skip(struct mbuf *m, int len, int skip); +#endif #endif /* _MACHINE_IN_CKSUM_H_ */ ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
writing a FreeBSD C library
Hello all y'all Kernel Hackers,
Trying to get a deeper understanding of the FreeBSD kernel I am currently I
am studying C library files.
For this reason I wrote a very simple library, just to understand how it
works.
Below are my source codes for:
1. the header
2. the library file
3. a simple C program with which I intend to test my library function
## start of simple library header
#ifndef _s_lib_h_
#define _s_lib_h_
#define SOME_INT0x0001
/* prototype */
void myprnf(char *);
#endif /* _s_lib_h_ */
# end of header
# start of library file lb.c ##
#include stdio.h
#include slib.h
static void _myprf(char *);
void
myprnf(char *farg)
{
char *narg = farg;
_myprf(narg);
}
static void
_myprf(char *sarg)
{
char *pstr = sarg;
printf(%s\n, pstr);
}
## end of library file ###
start of source file
#include slib.h
int
main()
{
char *somestr = hello world;
myprnf(somestr);
return(1-1);
}
# end of source file ###
I compiled the library file in the following way.
% gcc -I../include -Wall -c lb.c
% ar rsv mylib.a lb.o
The compilation finished with no warnings so I assume that there are no
errors in the library itself.
Trying to compile my source file - let's call it source.c - I always get the
following error message:
% gcc -o testfile source.c
/var/tmp//ccQoff1S.o(.text+0x19): In function `main':
: undefined reference to `myprintf'
%
In other words, gcc doesn't seem to find my library. I tried to mv my
library file in /lib, /libexec
/usr/lib, /usr/libdata and /usr/libexec but none of the above directories
would directory would
let me compile my source file.
Now I am wondering where do I need to put mylib.a file to succeed?
Also, this is a static library. What do I need to do under FreeBSD to
compile this library into a dynamic
library and where would I put this file?
Lastly, most if not all the system calls can be found under /sys/kern/*.c.
When writing a FreeBSD C program
gcc makes use of the corresponding headers, e.g. unistd.h. and the standard
library libc. Is it possible
to peep a look at the source file for libc, i.e. is it included in the
source tree? Where?
Thanks
Oliver
There are many many more kernel related questions on my mind but I think
that this is enought for one
email.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: writing a FreeBSD C library
Hi, you have to link your executable to your library. The command-line option is -l. % gcc -o testfile -lmylib source.c Without it, your program doesn't know that this library exists (somewhere, /usr/lib, ...) Regards, Florian ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: writing a FreeBSD C library
Oliver Mahmoudi escribió: I compiled the library file in the following way. % gcc -I../include -Wall -c lb.c % ar rsv mylib.a lb.o You can study bsd.lib.mk and bsd.prog.mk in /usr/share/mk. With these two includes you can deal easily with your C programs/libraries. It will serve you very well later. The compilation finished with no warnings so I assume that there are no errors in the library itself. Trying to compile my source file - let's call it source.c - I always get the following error message: % gcc -o testfile source.c /var/tmp//ccQoff1S.o(.text+0x19): In function `main': : undefined reference to `myprintf' % That's easy, your library isn't linked to your program. First, compile the source file but _do not link_: gcc -c source.c This will result in a source.o file. Then link the object files (source.o and the static library) with ld: ld -o testfile source.o mylib.a In other words, gcc doesn't seem to find my library. I tried to mv my library file in /lib, /libexec /usr/lib, /usr/libdata and /usr/libexec but none of the above directories would directory would let me compile my source file. With static libraries you can just specify the full path when linking. Now I am wondering where do I need to put mylib.a file to succeed? Also, this is a static library. What do I need to do under FreeBSD to compile this library into a dynamic library and where would I put this file? Just using the proper parameters when compiling the library. It is a Linux article but you'll find some explications here: http://tldp.org/HOWTO/Program-Library-HOWTO/shared-libraries.html Again, the bsd.*.mk Makefile includes are pretty handful. Lastly, most if not all the system calls can be found under /sys/kern/*.c. When writing a FreeBSD C program gcc makes use of the corresponding headers, e.g. unistd.h. and the standard library libc. Is it possible to peep a look at the source file for libc, i.e. is it included in the source tree? Where? In /usr/src/lib/libc provided you have the source code installed in /usr/src. There are many many more kernel related questions on my mind but I think that this is enought for one email. I don't want to desperate you but these are very basic things. You should get a deeper knowledge of the basics first, before you try to do some kernel-related things. Otherwise, you will find it way too difficult and you won't enjoy. Anyway, the book of Marshall K. McKusick and George V. Neville-Neil is a good source of learning kernel stuff: http://www.amazon.com/Design-Implementation-FreeBSD-Operating-System/dp/0201702452 Regards, -- Gabor Kovesdan FreeBSD Volunteer EMAIL: ga...@freebsd.org .:|:. ga...@kovesdan.org WEB: http://people.FreeBSD.org/~gabor .:|:. http://kovesdan.org ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
MIPS: bus_dma(9) and cache problems
This problem haunts for a couple of days and I can't find a nice and clean solution so this email is actually a cry for help. The problem: There is a buffer loaded by bus_dmamap_load for use as a DMA buffer. Right before this buffer resides block of vital data structure. Consider following scenario: 1. code modifies data in block and this modification ends up in cache and is not written back to memory 2. right after this code calls bus_dmamap_sync for this buffer and as a result cache invalidation is performed 3. Cache function operates on cache line size-aligned addresses and the block in question happens to share the same cache line with the buffer. So modification made at step (1) is lost. If busdma code controls allocation (bus_dmamem_alloc) this situation can be avoided by forcing pointer alignment. But when address come from the outer space via bus_dmamap_load* there is not much to do. There are two solutions I've figured so far: - Create bounce page for not properly aligned memory. Which would reduce performance a lot. - Remap buffer's page(s) as uncached. I haven't succeeded with this one yet and not sure it's always possible. May be someone can suggest better way to clean this mess? Thanks! -- gonzo ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
Re: make release stop at Creating ISO imagess
Quoting Ruben de Groot mai...@bzerk.org: On Mon, Oct 26, 2009 at 02:36:39PM +0700, ??? ? typed: hi sirs, apologized me for disturbing this list but ireally have problem s. i make my own release by follwoing document in releng articles. here is my command cd /usr/src/release time make CHROOTDIR=/kaitag/KAITAG BUILDNAME=7.2-RELEASE \ CVSROOT=/var/ftp/pub/ncvs RELEASETAG=RELENG_7_2_0_RELEASE \ EXTSRCDIR=/usr/src EXTPORTSDIR=/usr/ports \ DOC_LANG=en_US.ISO8859-1 NODOC=NO NOPORTS=NO \ MAKE_DVD=YES MAKE_ISOS=YES CDROM=YES RELEASEDISTFILES=/var/ftp/pub/distfiles \ release the build process goes well but then fetching for cdrtools.tbz begin and stop. in my machine i have installed cdrtools and there is also mkisofs file so i wonder why the script /usr/src/release/i386/mkisofsimages.sh still fetching for cdrtools. Do you have the cdrtools.tbz package in /var/ftp/pub/distfiles ? Ruben i copy cdrtools.tbz to /var/ftp/pub/distfiles while answering your first mail and let the process ran overnight here is a result, from screen shot == begin of last page screen shot touch cdrom.1 Building CDROM disc1 filesystem image 0 blocks 0 blocks Building CDROM disc2 filesystem image Building CDROM disc3 filesystem image 0 blocks 0 blocks touch cdrom.2 Building bootonly CDROM filesystem image touch cdrom.3 Creating ISO images... The cdrtools port is not installed. Trying to get it now. Fetching ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7.2-release/Lates t/cdrtools.tbz...pkg_add: warning: error reading from server: Operation timed ou t ^CSignal 2 received, cleaning up.. Could not get it via pkg_add - please go install this from the ports collection and run this script again. 6240.165u 575.390s 20:45:53.90 9.1% -259+1079k 167010+14463io 87062pf+0w maifa [/usr/src/release] # == end of screen shot after interrupt the process i make ... rerelease once again and now it stuck at the same point == begin of screen shot + export RELEASETAG=RELENG_7_2_0_RELEASE + export RELNOTES_LANG=en_US.ISO8859-1 + export SEPARATE_LIVEFS= + export TARGET=i386 + export TARGET_ARCH=i386 + export RELEASEDIR=/R + export PATH=/bin:/usr/bin:/sbin:/usr/sbin:/usr/local/bin + export MANBUILDCAT=YES + umount /dev + true + mount -t devfs devfs /dev + [ ! -c /dev/null ] + [ -x /etc/rc.d/ldconfig ] + /etc/rc.d/ldconfig start ELF ldconfig path: /lib /usr/lib /usr/lib/compat a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout + [ ! -f /tmp/.world_done ] + [ ! -f /tmp/.skip_ports_index ] + cd /usr/src/release + make obj + make doRELEASE Creating ISO images... The cdrtools port is not installed. Trying to get it now. Fetching ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-7.2-release/Lates t/cdrtools.tbz... == end of screen shot, currently running process i do not know what happend to the sh script mention ealier. anyway thanks indeed for your time. with best regards -- psr มะฃาม ฅินเดินดน มะไฟ ฅนเหลิงฟ้า http://makham.blogspot.com This message was sent using IMP, the Internet Messaging Program. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to freebsd-hackers-unsubscr...@freebsd.org
