problems with the mfi
after rebooting I get very often: ... mfi0: COMMAND 0xff800132d990 TIMEOUT AFTER 659 SECONDS mfi0: COMMAND 0xff800132d990 TIMEOUT AFTER 689 SECONDS mfi0: COMMAND 0xff800132d990 TIMEOUT AFTER 719 SECONDS ... another reboot usualy fixes this. danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: So I whip out a FTDI-based multiport Serial USB Adapter....
Just an idea - do you use certified usb 2.0 cable ? I had some problems many times using non-standard cables.. Try using certified cable. Try using different keyboard/mouse, maybe they drain too much power from a single USB port that connects all those equipment... try to see how much power do they drain alone... it looks like a power problem.. but Im not an expert here and dont know the USB internals in FreeBSD sorry :-( -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Ports and WITH_LIBCPLUSPLUS
On Mon, Feb 4, 2013 at 2:40 PM, Volodymyr Kostyrko c.kw...@gmail.comwrote: 03.02.2013 15:28, Dimitry Andric: Thanks for trying this out. Is there also a list of ports that *do* compile (and hopefully run) successfully? :-) I already switched to libc++ on my unstable STABLE-9 machines. Currently I'm using this config: *: CXXFLAGS= -stdlib=libc++ -std=c++11 | LDFLAGS= -stdlib=libc++ audio/flac databases/db5 devel/binutils devel/doxygen devel/qt4-designer devel/qt4-qt3support devel/qt4-script devel/yasm graphics/libopenraw graphics/tesseract lang/gcc multimedia/phonon-gstreamer net-p2p/transmission-cli net-p2p/transmission-daemon sysutils/smartmontools textproc/hunspell www/qt4-webkit x11/nvidia-driver x11/qt4-opengl: !CXXFLAGS | !LDFLAGS databases/mariadb-client emulators/pearpc www/libxul x11-toolkits/qt4-gui: USE_GCC=4.6+ | !CXXFLAGS | !LDFLAGS www/squid32: USE_GCC=any | !CXXFLAGS | !LDFLAGS snip -- Sphinx of black quartz, judge my vow. Could you clarify where you have these settings? Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Ports and WITH_LIBCPLUSPLUS
05.02.2013 13:59, Andreas Nilsson: Thanks for trying this out. Is there also a list of ports that *do* compile (and hopefully run) successfully? :-) I already switched to libc++ on my unstable STABLE-9 machines. Currently I'm using this config: *: CXXFLAGS= -stdlib=libc++ -std=c++11 | LDFLAGS= -stdlib=libc++ audio/flac databases/db5 devel/binutils devel/doxygen devel/qt4-designer devel/qt4-qt3support devel/qt4-script devel/yasm graphics/libopenraw graphics/tesseract lang/gcc multimedia/phonon-gstreamer net-p2p/transmission-cli net-p2p/transmission-daemon sysutils/smartmontools textproc/hunspell www/qt4-webkit x11/nvidia-driver x11/qt4-opengl: !CXXFLAGS | !LDFLAGS databases/mariadb-client emulators/pearpc www/libxul x11-toolkits/qt4-gui: USE_GCC=4.6+ | !CXXFLAGS | !LDFLAGS www/squid32: USE_GCC=any | !CXXFLAGS | !LDFLAGS snip Could you clarify where you have these settings? This is my desktops that I use @home and @work. I'm not going that experimental on any production machine. -- Sphinx of black quartz, judge my vow. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Ports and WITH_LIBCPLUSPLUS
On Tue, Feb 5, 2013 at 1:06 PM, Volodymyr Kostyrko c.kw...@gmail.comwrote: 05.02.2013 13:59, Andreas Nilsson: Thanks for trying this out. Is there also a list of ports that *do* compile (and hopefully run) successfully? :-) I already switched to libc++ on my unstable STABLE-9 machines. Currently I'm using this config: *: CXXFLAGS= -stdlib=libc++ -std=c++11 | LDFLAGS= -stdlib=libc++ audio/flac databases/db5 devel/binutils devel/doxygen devel/qt4-designer devel/qt4-qt3support devel/qt4-script devel/yasm graphics/libopenraw graphics/tesseract lang/gcc multimedia/phonon-gstreamer net-p2p/transmission-cli net-p2p/transmission-daemon sysutils/smartmontools textproc/hunspell www/qt4-webkit x11/nvidia-driver x11/qt4-opengl: !CXXFLAGS | !LDFLAGS databases/mariadb-client emulators/pearpc www/libxul x11-toolkits/qt4-gui: USE_GCC=4.6+ | !CXXFLAGS | !LDFLAGS www/squid32: USE_GCC=any | !CXXFLAGS | !LDFLAGS snip Could you clarify where you have these settings? This is my desktops that I use @home and @work. I'm not going that experimental on any production machine. -- Sphinx of black quartz, judge my vow. Ah, sorry for being unclear. I meant which config files :) Best regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: re(4) problems with GA-H77N-WIFI
John-Mark Gurney wrote: Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 23:04 +0100: John-Mark Gurney wrote: Oliver Fromme wrote this message on Mon, Feb 04, 2013 at 19:15 +0100: I'm running a recent stable/9 (about 14 days old). What's the best way to debug this problem? At the moment I'm not even sure if it's the hardware, or if it's FreeBSD's fault (or my fault) ... Have you tried to disable msi and msix? hw.pci.enable_msix: 1 hw.pci.enable_msi: 1 I tried these entries in /boot/loader.conf, according to the re(4) manual page: hw.re.msi_disable=1 hw.re.msix_disable=1 Unfortunately it didn't make a difference. Did you try in loader.conf: hw.pci.enable_msix=0 hw.pci.enable_msi=0 To disable MSI for the whole system? No, I haven't ... Will do that ASAP. Best regards Oliver -- Oliver Fromme, secnetix GmbH Co. KG, Marktplatz 29, 85567 Grafing Handelsregister: Amtsgericht Muenchen, HRA 74606, Geschäftsfuehrung: secnetix Verwaltungsgesellsch. mbH, Handelsreg.: Amtsgericht München, HRB 125758, Geschäftsführer: Maik Bachmann, Olaf Erb, Ralf Gebhart FreeBSD-Dienstleistungen/-Produkte + mehr: http://www.secnetix.de/bsd Perl will consistently give you what you want, unless what you want is consistency. -- Larry Wall ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Ports and WITH_LIBCPLUSPLUS
05.02.2013 15:06, Andreas Nilsson: Ah, sorry for being unclear. I meant which config files :) I'm using ports-mgmt/portconf to keep track of all knobs. -- Sphinx of black quartz, judge my vow. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Ports and WITH_LIBCPLUSPLUS
On Tue, Feb 5, 2013 at 3:54 PM, Volodymyr Kostyrko c.kw...@gmail.comwrote: 05.02.2013 15:06, Andreas Nilsson: Ah, sorry for being unclear. I meant which config files :) I'm using ports-mgmt/portconf to keep track of all knobs. -- Sphinx of black quartz, judge my vow. Thanks. I'll look into that, and how it will fit in with poudriere. Regards Andreas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: So I whip out a FTDI-based multiport Serial USB Adapter....
On 2/4/2013 9:33 PM, Karl Denninger wrote: On 2/4/2013 9:02 PM, Karl Denninger wrote: On 2/4/2013 4:32 PM, Charles Sprickman wrote: On Feb 4, 2013, at 5:00 PM, Ian Lepore wrote: On Mon, 2013-02-04 at 16:31 -0500, Charles Sprickman wrote: On Feb 4, 2013, at 4:13 PM, Ian Lepore wrote: On Mon, 2013-02-04 at 14:58 -0600, Karl Denninger wrote: On 2/4/2013 2:06 PM, Ian Lepore wrote: On Mon, 2013-02-04 at 12:57 -0600, Karl Denninger wrote: ... and plug it into FreeBSD 9.1-Stable with the rev ID FreeBSD 9.1-STABLE #16 r244942 and it returns ugen4.4: vendor 0x0409 at usbus4 uhub6: vendor 0x0409 product 0x0050, class 9/0, rev 2.00/1.00, addr 4 on usbus4 uhub_attach: port 1 power on failed, USB_ERR_STALLED uhub_attach: port 2 power on failed, USB_ERR_STALLED uhub_attach: port 3 power on failed, USB_ERR_STALLED uhub_attach: port 4 power on failed, USB_ERR_STALLED uhub_attach: port 5 power on failed, USB_ERR_STALLED uhub_attach: port 6 power on failed, USB_ERR_STALLED uhub_attach: port 7 power on failed, USB_ERR_STALLED uhub6: 7 ports with 7 removable, self powered Yuck. The last time it was working was on a FreeBSD 7 box (yeah, I know, rather old) but I never had problems there. And it appears that all of the device declarations that I used to have to put in the kernel as non-standard stuff are now in GENERIC, so I would expect it to work. Ideas as to what may have gotten hosed up here? Those messages all seem to be related to a hub. Vendor ID 0x0409 is NEC. FTDI's vendor ID is 0x0403, and FTDI stuff works fine in FreeBSD 9 and 10; I use it all the time. Sometimes aftermarket vendors who use FTDI's parts program different vendor/product info and IDs have to be added to code to recognize them, that's the only trouble one usually encounters. -- Ian Well, that sorta kinda worked. Except that it still is identifying it as a hub too, and the two collide and crash the stack. But I can't find anything that is looking at the PID (0x0050) or the definition (HUB_0050) anywhere in the code. I'll go pull the NEC defs and set up something else instead of simply adding it to the FTDI probe list. It seems to me you have a problem with a hub (perhaps the root hub or a motherboard hub if you don't have an external one) and this has nothing to do with the ftdi device at all. I assume we're talking about a multi-port usb to serial adapter, correct? If so, they generally do have a hub included in the device. Example: ugen1.3: vendor 0x0409 at usbus1 uhub4: vendor 0x0409 product 0x0050, class 9/0, rev 2.00/1.00, addr 3 on usbus1 uhub4: 7 ports with 7 removable, self powered Then the individual ports look like this: ugen1.4: FTDI at usbus1 uftdi0: FT232R USB UART on usbus1 ugen1.5: FTDI at usbus1 uftdi1: FT232R USB UART on usbus1 (etc.) We use these for serial console ports, they're (relatively) cheap and have generally been well supported. The above info is from an 8.3 box. Just wanted to clarify that there is likely a hub in the serial box Karl is working with… Charles Oh, interesting. The biggest ftdi dongle I have is 4 ports, using the ftdi 4232 chip. I guess to get more ports than that, folks are now using an internal hub and multiple ftdi chips. These multiport things have been around for a long time. Someone at ISC recommended them when we were looking to replace some unsupported RocketPort cards. Not affiliated with this place, but it's the largest collection of USB to serial stuff I've ever seen (and they document for the most part what chips are involved): http://usbgear.com/USB-Serial.html Our first 16 ports are on one of these: http://usbgear.com/computer_cable_details.cfm?sku=USB-16COM-RMcats=199catid=493%2C494%2C474%2C199%2C461%2C106%2C1009%2C601 (the tx/rx blinky lights are handy in troubleshooting) Then the rest on this cheaper model: http://usbgear.com/computer_cable_details.cfm?sku=USBG-8COM-Mcats=199catid=494%2C199%2C474%2C2345%2C1009 So for some reason there's a problem with the hub, and that's probably preventing it from getting as far as seeing the ftdi parts that are downstream of that. My dmesg snippet is from the latter box. Note that the vendor and product ID are the same as Karl's. Perhaps there is a regression, as I am running 8.3 and have had no issues there (previously it was on a 4.11 box). Charles That's the EXACT box. I've used them for a VERY long time on FreeBSD and they have always worked perfectly well, but never on 9.x until now -- and it doesn't work on 9.x. Had to run out for a while -- continuing testing. OK, with the kernel back the way it was, this is what I got: I plug in and get: Feb 4 21:17:46 FS kernel: uhub6: vendor 0x0409 product 0x0050, class 9/0, rev 2.00/1.00, addr 4 on usbus4 Feb 4 21:17:46 FS kernel: uhub_attach: port 1 power on failed, USB_ERR_STALLED Feb 4 21:17:46 FS kernel: uhub_attach: port 2 power on failed,
Re: So I whip out a FTDI-based multiport Serial USB Adapter.... [SB QUAR: Tue Feb 5 10:15:47 2013]
On 2/5/2013 10:15 AM, Chris H wrote: On 2/4/2013 9:33 PM, Karl Denninger wrote: On 2/4/2013 9:02 PM, Karl Denninger wrote: On 2/4/2013 4:32 PM, Charles Sprickman wrote: These multiport things have been around for a long time. Someone at ISC recommended them when we were looking to replace some unsupported RocketPort cards. Not affiliated with this place, but it's the largest collection of USB to serial stuff I've ever seen (and they document for the most part what chips are involved): http://usbgear.com/USB-Serial.html Our first 16 ports are on one of these: http://usbgear.com/computer_cable_details.cfm?sku=USB-16COM-RMcats=199catid=493%2C494%2C474%2C199%2C461%2C106%2C1009%2C601 (the tx/rx blinky lights are handy in troubleshooting) Then the rest on this cheaper model: http://usbgear.com/computer_cable_details.cfm?sku=USBG-8COM-Mcats=199catid=494%2C199%2C474%2C2345%2C1009 So for some reason there's a problem with the hub, and that's probably preventing it from getting as far as seeing the ftdi parts that are downstream of that. My dmesg snippet is from the latter box. Note that the vendor and product ID are the same as Karl's. Perhaps there is a regression, as I am running 8.3 and have had no issues there (previously it was on a 4.11 box). Charles That's the EXACT box. I've used them for a VERY long time on FreeBSD and they have always worked perfectly well, but never on 9.x until now -- and it doesn't work on 9.x. Had to run out for a while -- continuing testing. OK, with the kernel back the way it was, this is what I got: I plug in and get: Feb 4 21:17:46 FS kernel: uhub6: vendor 0x0409 product 0x0050, class 9/0, rev 2.00/1.00, addr 4 on usbus4 Feb 4 21:17:46 FS kernel: uhub_attach: port 1 power on failed, USB_ERR_STALLED Feb 4 21:17:46 FS kernel: uhub_attach: port 2 power on failed, USB_ERR_STALLED Feb 4 21:17:46 FS kernel: uhub_attach: port 3 power on failed, USB_ERR_STALLED Feb 4 21:17:46 FS kernel: uhub_attach: port 4 power on failed, USB_ERR_STALLED Feb 4 21:17:46 FS kernel: uhub_attach: port 5 power on failed, USB_ERR_STALLED Feb 4 21:17:47 FS kernel: uhub_attach: port 6 power on failed, USB_ERR_STALLED Feb 4 21:17:47 FS kernel: uhub_attach: port 7 power on failed, USB_ERR_STALLED Feb 4 21:17:47 FS kernel: uhub6: 7 ports with 7 removable, self powered FS/karl:/disk/karl usbconfig -u 4 -a 4 dump_device_desc ugen4.4: product 0x0050 vendor 0x0409 at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0009 bDeviceSubClass = 0x bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x0409 idProduct = 0x0050 bcdDevice = 0x0100 iManufacturer = 0x no string iProduct = 0x no string iSerialNumber = 0x no string bNumConfigurations = 0x0001 I then issue and get: FS/karl:/disk/karl usbconfig -u 4 -a 4 power_on FS/karl:/disk/karl usbconfig -u 4 -a 4 dump_device_desc ugen4.4: product 0x0050 vendor 0x0409 at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0009 bDeviceSubClass = 0x bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x0409 idProduct = 0x0050 bcdDevice = 0x0100 iManufacturer = 0x no string iProduct = 0x no string iSerialNumber = 0x no string bNumConfigurations = 0x0001 And if I turn it off and back on (power_off then power_on) the cycle repeats. An attempt to reset is also futile, although the command is accepted. If I turn on hw.usb.uhub.debug I get a never-ending string of these: Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:13 FS kernel: usb_needs_explore: Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:13 FS kernel: usb_needs_explore: Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:13 FS kernel: usb_needs_explore: Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:13 FS kernel: usb_needs_explore: Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 Until the power is turned off on the device (with usbconfig -u 4 -a 4 power_off), when it settles down to this once in a while: Feb 4 21:29:26 FS kernel: usb_needs_explore: Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6429cf0 Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks
Re: So I whip out a FTDI-based multiport Serial USB Adapter.... [SB QUAR: Tue Feb 5 10:15:47 2013]
On 2/5/2013 10:15 AM, Chris H wrote: On 2/4/2013 9:33 PM, Karl Denninger wrote: On 2/4/2013 9:02 PM, Karl Denninger wrote: On 2/4/2013 4:32 PM, Charles Sprickman wrote: These multiport things have been around for a long time. Someone at ISC recommended them when we were looking to replace some unsupported RocketPort cards. Not affiliated with this place, but it's the largest collection of USB to serial stuff I've ever seen (and they document for the most part what chips are involved): http://usbgear.com/USB-Serial.html Our first 16 ports are on one of these: http://usbgear.com/computer_cable_details.cfm?sku=USB-16COM-RMcats=199catid=493%2C494%2C474%2C199%2C461%2C106%2C1009%2C601 (the tx/rx blinky lights are handy in troubleshooting) Then the rest on this cheaper model: http://usbgear.com/computer_cable_details.cfm?sku=USBG-8COM-Mcats=199catid=494%2C199%2C474%2C2345%2C1009 So for some reason there's a problem with the hub, and that's probably preventing it from getting as far as seeing the ftdi parts that are downstream of that. My dmesg snippet is from the latter box. Note that the vendor and product ID are the same as Karl's. Perhaps there is a regression, as I am running 8.3 and have had no issues there (previously it was on a 4.11 box). Charles That's the EXACT box. I've used them for a VERY long time on FreeBSD and they have always worked perfectly well, but never on 9.x until now -- and it doesn't work on 9.x. Had to run out for a while -- continuing testing. OK, with the kernel back the way it was, this is what I got: I plug in and get: Feb 4 21:17:46 FS kernel: uhub6: vendor 0x0409 product 0x0050, class 9/0, rev 2.00/1.00, addr 4 on usbus4 Feb 4 21:17:46 FS kernel: uhub_attach: port 1 power on failed, USB_ERR_STALLED Feb 4 21:17:46 FS kernel: uhub_attach: port 2 power on failed, USB_ERR_STALLED Feb 4 21:17:46 FS kernel: uhub_attach: port 3 power on failed, USB_ERR_STALLED Feb 4 21:17:46 FS kernel: uhub_attach: port 4 power on failed, USB_ERR_STALLED Feb 4 21:17:46 FS kernel: uhub_attach: port 5 power on failed, USB_ERR_STALLED Feb 4 21:17:47 FS kernel: uhub_attach: port 6 power on failed, USB_ERR_STALLED Feb 4 21:17:47 FS kernel: uhub_attach: port 7 power on failed, USB_ERR_STALLED Feb 4 21:17:47 FS kernel: uhub6: 7 ports with 7 removable, self powered FS/karl:/disk/karl usbconfig -u 4 -a 4 dump_device_desc ugen4.4: product 0x0050 vendor 0x0409 at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0009 bDeviceSubClass = 0x bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x0409 idProduct = 0x0050 bcdDevice = 0x0100 iManufacturer = 0x no string iProduct = 0x no string iSerialNumber = 0x no string bNumConfigurations = 0x0001 I then issue and get: FS/karl:/disk/karl usbconfig -u 4 -a 4 power_on FS/karl:/disk/karl usbconfig -u 4 -a 4 dump_device_desc ugen4.4: product 0x0050 vendor 0x0409 at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0009 bDeviceSubClass = 0x bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x0409 idProduct = 0x0050 bcdDevice = 0x0100 iManufacturer = 0x no string iProduct = 0x no string iSerialNumber = 0x no string bNumConfigurations = 0x0001 And if I turn it off and back on (power_off then power_on) the cycle repeats. An attempt to reset is also futile, although the command is accepted. If I turn on hw.usb.uhub.debug I get a never-ending string of these: Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:13 FS kernel: usb_needs_explore: Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:13 FS kernel: usb_needs_explore: Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:13 FS kernel: usb_needs_explore: Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:13 FS kernel: usb_needs_explore: Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 Until the power is turned off on the device (with usbconfig -u 4 -a 4 power_off), when it settles down to this once in a while: Feb 4 21:29:26 FS kernel: usb_needs_explore: Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6429cf0 Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks
Re: So I whip out a FTDI-based multiport Serial USB Adapter.... [SB QUAR: Tue Feb 5 10:15:47 2013]
On 2/5/2013 10:15 AM, Chris H wrote: On 2/4/2013 9:33 PM, Karl Denninger wrote: On 2/4/2013 9:02 PM, Karl Denninger wrote: On 2/4/2013 4:32 PM, Charles Sprickman wrote: These multiport things have been around for a long time. Someone at ISC recommended them when we were looking to replace some unsupported RocketPort cards. Not affiliated with this place, but it's the largest collection of USB to serial stuff I've ever seen (and they document for the most part what chips are involved): http://usbgear.com/USB-Serial.html Our first 16 ports are on one of these: http://usbgear.com/computer_cable_details.cfm?sku=USB-16COM-RMcats=199catid=493%2C494%2C474%2C199%2C461%2C106%2C1009%2C601 (the tx/rx blinky lights are handy in troubleshooting) Then the rest on this cheaper model: http://usbgear.com/computer_cable_details.cfm?sku=USBG-8COM-Mcats=199catid=494%2C199%2C474%2C2345%2C1009 So for some reason there's a problem with the hub, and that's probably preventing it from getting as far as seeing the ftdi parts that are downstream of that. My dmesg snippet is from the latter box. Note that the vendor and product ID are the same as Karl's. Perhaps there is a regression, as I am running 8.3 and have had no issues there (previously it was on a 4.11 box). Charles That's the EXACT box. I've used them for a VERY long time on FreeBSD and they have always worked perfectly well, but never on 9.x until now -- and it doesn't work on 9.x. Had to run out for a while -- continuing testing. OK, with the kernel back the way it was, this is what I got: I plug in and get: Feb 4 21:17:46 FS kernel: uhub6: vendor 0x0409 product 0x0050, class 9/0, rev 2.00/1.00, addr 4 on usbus4 Feb 4 21:17:46 FS kernel: uhub_attach: port 1 power on failed, USB_ERR_STALLED Feb 4 21:17:46 FS kernel: uhub_attach: port 2 power on failed, USB_ERR_STALLED Feb 4 21:17:46 FS kernel: uhub_attach: port 3 power on failed, USB_ERR_STALLED Feb 4 21:17:46 FS kernel: uhub_attach: port 4 power on failed, USB_ERR_STALLED Feb 4 21:17:46 FS kernel: uhub_attach: port 5 power on failed, USB_ERR_STALLED Feb 4 21:17:47 FS kernel: uhub_attach: port 6 power on failed, USB_ERR_STALLED Feb 4 21:17:47 FS kernel: uhub_attach: port 7 power on failed, USB_ERR_STALLED Feb 4 21:17:47 FS kernel: uhub6: 7 ports with 7 removable, self powered FS/karl:/disk/karl usbconfig -u 4 -a 4 dump_device_desc ugen4.4: product 0x0050 vendor 0x0409 at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0009 bDeviceSubClass = 0x bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x0409 idProduct = 0x0050 bcdDevice = 0x0100 iManufacturer = 0x no string iProduct = 0x no string iSerialNumber = 0x no string bNumConfigurations = 0x0001 I then issue and get: FS/karl:/disk/karl usbconfig -u 4 -a 4 power_on FS/karl:/disk/karl usbconfig -u 4 -a 4 dump_device_desc ugen4.4: product 0x0050 vendor 0x0409 at usbus4, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0009 bDeviceSubClass = 0x bDeviceProtocol = 0x0001 bMaxPacketSize0 = 0x0040 idVendor = 0x0409 idProduct = 0x0050 bcdDevice = 0x0100 iManufacturer = 0x no string iProduct = 0x no string iSerialNumber = 0x no string bNumConfigurations = 0x0001 And if I turn it off and back on (power_off then power_on) the cycle repeats. An attempt to reset is also futile, although the command is accepted. If I turn on hw.usb.uhub.debug I get a never-ending string of these: Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:12 FS kernel: usb_needs_explore: Feb 4 21:29:12 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:13 FS kernel: usb_needs_explore: Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:13 FS kernel: usb_needs_explore: Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:13 FS kernel: usb_needs_explore: Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 Feb 4 21:29:13 FS kernel: usb_needs_explore: Feb 4 21:29:13 FS kernel: usb_bus_powerd: bus=0xc646ac78 Until the power is turned off on the device (with usbconfig -u 4 -a 4 power_off), when it settles down to this once in a while: Feb 4 21:29:26 FS kernel: usb_needs_explore: Feb 4 21:29:26 FS kernel: usb_bus_powerd: bus=0xc6429cf0 Feb 4 21:29:26 FS kernel: usb_bus_powerd: Recomputing power masks
Re: So I whip out a FTDI-based multiport Serial USB Adapter.... [SB QUAR: Tue Feb 5 10:15:47 2013]
On Tue, Feb 5, 2013 at 5:27 PM, chr...@ultimatedns.net wrote: Understood. I was referring to the _computers_ power supply. :) Still it may be caused by some issued on the USB bus power management. Normally an USB port can supply 500mA of current. Above that port should be disabled by the host if I remember correctly. If there is a hub inside the serial port adapter it would be good to know it it is powered directly from the USB port or does it have its own power supply... There could be too much power drain from the USB port by external devices attached to the hub/adapter. But this would be rather obvious. There may be some misunderstanding between USB Host and the self powered USB device, so they cannot agree on the power supply level, which seems more probable :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: So I whip out a FTDI-based multiport Serial USB Adapter.... [SB QUAR: Tue Feb 5 10:15:47 2013]
On 2/5/2013 10:44 AM, CeDeROM wrote: On Tue, Feb 5, 2013 at 5:27 PM, chr...@ultimatedns.net wrote: Understood. I was referring to the _computers_ power supply. :) Still it may be caused by some issued on the USB bus power management. Normally an USB port can supply 500mA of current. Above that port should be disabled by the host if I remember correctly. If there is a hub inside the serial port adapter it would be good to know it it is powered directly from the USB port or does it have its own power supply... There could be too much power drain from the USB port by external devices attached to the hub/adapter. But this would be rather obvious. There may be some misunderstanding between USB Host and the self powered USB device, so they cannot agree on the power supply level, which seems more probable :-) The FTDI adapter has the provision for an external power supply (+5V) but it does not require it unless you're running off an unpowered bus, which is not normally the case. 500ma is quite a bit of available energy. I suspect the issue is found in the KVM, which attaches as a low speed device; I'm going to see if I have the same issue with other USB devices connected while the KVM is on the box. -- -- Karl Denninger /The Market Ticker ®/ http://market-ticker.org Cuda Systems LLC ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: problems with the mfi
On Tuesday, February 05, 2013 3:48:28 am Daniel Braniss wrote: after rebooting I get very often: ... mfi0: COMMAND 0xff800132d990 TIMEOUT AFTER 659 SECONDS mfi0: COMMAND 0xff800132d990 TIMEOUT AFTER 689 SECONDS mfi0: COMMAND 0xff800132d990 TIMEOUT AFTER 719 SECONDS ... another reboot usualy fixes this. Does it have the latest firmware? -- John Baldwin ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: So I whip out a FTDI-based multiport Serial USB Adapter.... [SB QUAR: Tue Feb 5 10:15:47 2013]
On Tue, Feb 5, 2013 at 6:09 PM, Karl Denninger k...@denninger.net wrote: The FTDI adapter has the provision for an external power supply (+5V) but it does not require it unless you're running off an unpowered bus, which is not normally the case. 500ma is quite a bit of available energy. Karl, can you please use external power supply to power up the adapter - with and without the additional devices step by step - this way we will eliminate one of the possible causes :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: stable/9 r245439 breaks security/pam_ssh_agent_auth on stable/9 (WAS: CLANG 3.2 breaks security/pam_ssh_agent_auth on stable/9)
On Tue, Feb 5, 2013 at 12:36 AM, Kimmo Paasiala kpaas...@gmail.com wrote: On Sun, Feb 3, 2013 at 7:22 PM, Chris Rees cr...@freebsd.org wrote: On 3 February 2013 17:15, Stefan Bethke s...@lassitu.de wrote: Am 03.02.2013 um 10:57 schrieb Chris Rees cr...@freebsd.org: On 3 February 2013 03:55, Kimmo Paasiala kpaas...@gmail.com wrote: There is no PR yet with my fix and therefor no commit to ports tree that would fix the problem. I'll file a PR soon (TM). The problem was in base, and is fixed there. Huh? With -current r246283, I still get a segfault from sudo unless I have Kimmo's patch. Is there some confusion about which problem is addressed by Kimmo's patch? Hm, perhaps it might be necessary then. Kimmo, please would you submit the patch you had as a PR? I'm sure Wesley would appreciate the hint. Chris I'll file a PR when I have recovered from a nasty flu. Right now I'm not fit for thinking... I changed the title of this thread to a better one. -Kimmo It looks like the port was updated just recently to a new version that has its own problems that are no longer related strnvis(3). I'll have to give up for now. (freebsd-ports added to cc:) -Kimmo ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: About kern.ipc.somaxconn and netstat
Hello. Sorry for the very late answer. That is a very good command, thank you for your recommendation. All the time that I have executed it it shows 0 listen queue overflows so I guess our configuration is working. Thank you so much. -Mensaje original- From: Kubilay Kocak Sent: Thursday, January 31, 2013 6:39 AM To: Efraín Déctor Cc: freebsd-stable@freebsd.org Subject: Re: About kern.ipc.somaxconn and netstat On 31/01/2013 4:54 AM, Efraín Déctor wrote: -Mensaje original- From: Kubilay Kocak Sent: Wednesday, January 30, 2013 3:25 AM To: Efraín Déctor Cc: freebsd-stable@freebsd.org Subject: Re: About kern.ipc.somaxconn and netstat On 30/01/2013 12:26 PM, Efraín Déctor wrote: Hello. We have a webserver using FreeBSD, we read about tunning kern.ipc.somaxconn (http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/configtuning-kernel-limits.html) so the OS can handle all the connections. Is there a way to know how many connections are established in a certain moment?. I know about netstat(1) but is there any other command that we can use to know the exact amount of how many connections are established?. This one might help: kern.ipc.numopensockets: Number of open sockets It's usefulness will depend on the granularity you require (in only, out only, established only, etc) but it's always represented system-wide resource consumption very well (matching observed workloads - some baseline value) Thank you, it is very helpfull, using kern.ipc.numopensockets with sockstat(1) and netstat(1) will give me a clue to tune kern.ipc.somaxconn Thank you all. Also, if you haven't already come across this one in your netstat travels, this one directly reports listen queue overflows: netstat -s -p tcp |grep listen -- Ta, Koobs ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Lançamento - Ferramentas ETramontina
Confira em nosso site! http://www.tubaraoeletrico.com.br/ ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Test network capabilities
Hello. Is there a way to test the network capabilities of FreeBSD?, currently we are tunning our server to achieve the best performance for the socket connections. Using this http://rerepi.wordpress.com/2008/04/19/tuning-freebsd-sysoev-rit/ and this https://calomel.org/freebsd_network_tuning.html guides we see that we are on the right path, however we want to conduct a test to see if what we have configured meets our needs. Is there a way to send connections to a opened port of FreeBSD? Something like Apache Bench but for a socket server based on Apache Mina? Thanks in advance. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
[releng_9 tinderbox] failure on ia64/ia64
TB --- 2013-02-05 19:29:45 - tinderbox 2.10 running on freebsd-stable.sentex.ca TB --- 2013-02-05 19:29:45 - FreeBSD freebsd-stable.sentex.ca 8.3-STABLE FreeBSD 8.3-STABLE #0: Tue Oct 16 17:37:58 UTC 2012 mdtan...@freebsd-stable.sentex.ca:/usr/obj/usr/src/sys/server amd64 TB --- 2013-02-05 19:29:45 - starting RELENG_9 tinderbox run for ia64/ia64 TB --- 2013-02-05 19:29:45 - cleaning the object tree TB --- 2013-02-05 19:30:12 - checking out /src from svn://svn.freebsd.org/base/stable/9 TB --- 2013-02-05 19:30:12 - cd /tinderbox/RELENG_9/ia64/ia64 TB --- 2013-02-05 19:30:12 - /usr/local/bin/svn cleanup /src TB --- 2013-02-05 19:31:29 - /usr/local/bin/svn update /src TB --- 2013-02-05 19:31:38 - building world TB --- 2013-02-05 19:31:38 - CROSS_BUILD_TESTING=YES TB --- 2013-02-05 19:31:38 - MAKEOBJDIRPREFIX=/obj TB --- 2013-02-05 19:31:38 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-02-05 19:31:38 - SRCCONF=/dev/null TB --- 2013-02-05 19:31:38 - TARGET=ia64 TB --- 2013-02-05 19:31:38 - TARGET_ARCH=ia64 TB --- 2013-02-05 19:31:38 - TZ=UTC TB --- 2013-02-05 19:31:38 - __MAKE_CONF=/dev/null TB --- 2013-02-05 19:31:38 - cd /src TB --- 2013-02-05 19:31:38 - /usr/bin/make -B buildworld World build started on Tue Feb 5 19:31:39 UTC 2013 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 Tue Feb 5 21:24:13 UTC 2013 TB --- 2013-02-05 21:24:13 - generating LINT kernel config TB --- 2013-02-05 21:24:13 - cd /src/sys/ia64/conf TB --- 2013-02-05 21:24:13 - /usr/bin/make -B LINT TB --- 2013-02-05 21:24:13 - cd /src/sys/ia64/conf TB --- 2013-02-05 21:24:13 - /usr/sbin/config -m LINT TB --- 2013-02-05 21:24:13 - building LINT kernel TB --- 2013-02-05 21:24:13 - CROSS_BUILD_TESTING=YES TB --- 2013-02-05 21:24:13 - MAKEOBJDIRPREFIX=/obj TB --- 2013-02-05 21:24:13 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-02-05 21:24:13 - SRCCONF=/dev/null TB --- 2013-02-05 21:24:13 - TARGET=ia64 TB --- 2013-02-05 21:24:13 - TARGET_ARCH=ia64 TB --- 2013-02-05 21:24:13 - TZ=UTC TB --- 2013-02-05 21:24:13 - __MAKE_CONF=/dev/null TB --- 2013-02-05 21:24:13 - cd /src TB --- 2013-02-05 21:24:13 - /usr/bin/make -B buildkernel KERNCONF=LINT Kernel build for LINT started on Tue Feb 5 21:24:14 UTC 2013 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 Kernel build for LINT completed on Tue Feb 5 22:08:11 UTC 2013 TB --- 2013-02-05 22:08:11 - cd /src/sys/ia64/conf TB --- 2013-02-05 22:08:11 - /usr/sbin/config -m GENERIC TB --- 2013-02-05 22:08:11 - building GENERIC kernel TB --- 2013-02-05 22:08:11 - CROSS_BUILD_TESTING=YES TB --- 2013-02-05 22:08:11 - MAKEOBJDIRPREFIX=/obj TB --- 2013-02-05 22:08:11 - PATH=/usr/bin:/usr/sbin:/bin:/sbin TB --- 2013-02-05 22:08:11 - SRCCONF=/dev/null TB --- 2013-02-05 22:08:11 - TARGET=ia64 TB --- 2013-02-05 22:08:11 - TARGET_ARCH=ia64 TB --- 2013-02-05 22:08:11 - TZ=UTC TB --- 2013-02-05 22:08:11 - __MAKE_CONF=/dev/null TB --- 2013-02-05 22:08:11 - cd /src TB --- 2013-02-05 22:08:11 - /usr/bin/make -B buildkernel KERNCONF=GENERIC Kernel build for GENERIC started on Tue Feb 5 22:08:11 UTC 2013 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 [...] /src/sys/dev/firewire/if_fwip.c:499: undefined reference to `crom_add_simple_text' /src/sys/dev/firewire/if_fwip.c:500: undefined reference to `crom_add_entry' /src/sys/dev/firewire/if_fwip.c:501: undefined reference to `crom_add_simple_text' if_fwip.o: In function `fwip_stream_input': /src/sys/dev/firewire/if_fwip.c:840: undefined reference to `fw_noderesolve_nodeid' if_fwip.o: In function `fwip_unicast_input': /src/sys/dev/firewire/if_fwip.c:939: undefined reference to `fw_noderesolve_nodeid' if_fwip.o:(.data.rel+0x80): undefined reference to `sysctl__hw_firewire_children' *** Error code 1 Stop in /obj/ia64.ia64/src/sys/GENERIC. *** Error code 1 Stop in /src. *** Error code 1 Stop in /src. TB --- 2013-02-05 22:18:17 - WARNING: /usr/bin/make returned exit code 1 TB --- 2013-02-05 22:18:17 - ERROR: failed to build GENERIC kernel TB --- 2013-02-05 22:18:17 - 7184.44 user 859.13 system 10111.94 real http://tinderbox.freebsd.org/tinderbox-releng_9-RELENG_9-ia64-ia64.full ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
csh/tcsh: odd %~ prompt variable behaviour
(Please keep me CC'd as I'm not subscribed to the list) System is base/stable/9, r245697. tcsh version is 6.18.01: $ sudo -i root@icarus:~ # sfdjsdj sfdjsdj: Command not found. root@icarus:~ # cd ~root root@icarus:~ # dsjfdsfdsf dsjfdsfdsf: Command not found. root@icarus:~ # cd ~jdc root@icarus:~jdc # sdjfdjkfjdsk sdjfdjkfjdsk: Command not found. root@icarus:/home/jdc # notice sudden prompt change root@icarus:/home/jdc # cd ~root root@icarus:~ # dsfjjdskdfs dsfjjdskdfs: Command not found. root@icarus:~ # logout This only happens when an invalid command is issued (e.g. had I used ls instead of blah the prompt would not have changed). $prompt is the standard /root/.cshrc (r244005) value: set prompt = %N@%m:%~ %# I cannot reproduce this problem on Debian 6.0.1 with tcsh 6.17.02: $ ssh jdc@192.168.1.161 Linux debian 2.6.32-5-686 #1 SMP Sun Sep 23 09:49:36 UTC 2012 i686 Last login: Tue Feb 3 19:22:19 2013 from icarus.home.lan jdc@debian:~$ sudo -i root@debian:~# /bin/tcsh debian:~# set prompt = %N@%m:%~ %# root@debian:~ # sdfsdf sdfsdf: Command not found. root@debian:~ # cd ~jdc root@debian:~jdc # sdfssgsgjsj sdfssgsgjsj: Command not found. root@debian:~jdc # exit root@debian:~# logout The number of changes between 6.17.02 and 6.18.01 seem quite large (looking at src/contrib/tcsh/Fixes). Does anyone have a non-FreeBSD system with tcsh 6.18.01 available to determine if this is a FreeBSD-centric issue or an actual issue with tcsh that needs to be reported upstream? Thanks. -- | Jeremy Chadwick j...@koitsu.org | | UNIX Systems Administratorhttp://jdc.koitsu.org/ | | Mountain View, CA, US| | 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 freebsd-stable-unsubscr...@freebsd.org
FreeBSD-9.1 would not boot on pentium3 laptop
Hello! I have an old Dell Latitude C800 laptop (with Pentium3 CPU in it). FreeBSD 6.3-STABLE was running fine on it, but I decided to update the machine to 9.1-STABLE. Well, neither my own custom kernel, nor even the official 9.1-RELEASE CD1 would boot... In both cases the boot process runs up to detecting uhub0, then either hangs forever or shuts off after a short while. Again, I thought I screwed-up the build, but the official CD would not boot either, so here I am. Flipping through the old CDs I have, the 7.3 hangs at boot similarly (after reporting loading the memory image and warning me about dangerously low battery). The 3.2-STABLE (September 1999) boots fine -- and goes into sysinstall. Freesbie-2.0.1 (which is based on FreeBSD-6.2) booted too. What happened between 6.x and 7.x? Any ideas? Thanks! -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD-9.1 would not boot on pentium3 laptop
Hi, On Tue, 05 Feb 2013 23:38:28 -0500 Mikhail T. mi+t...@aldan.algebra.com wrote: Hello! I have an old Dell Latitude C800 laptop (with Pentium3 CPU in it). FreeBSD 6.3-STABLE was running fine on it, but I decided to update the machine to 9.1-STABLE. Well, neither my own custom kernel, nor even the official 9.1-RELEASE CD1 would boot... In both cases the boot process runs up to detecting uhub0, then either hangs forever or shuts off after a short while. USB? I have had a Fujitsu LifeBook which I only could use with 7.x out for the same reason. Erich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD-9.1 would not boot on pentium3 laptop
On 05.02.2013 23:50, Erich Dollansky wrote: USB? That would be a shame -- I'm dressing up this old machine to be used with a couple of USB-devices. I have had a Fujitsu LifeBook which I only could use with 7.x out for the same reason. Is there a PR? Thanks, -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: re(4) problems with GA-H77N-WIFI
On Mon, Feb 04, 2013 at 07:15:51PM +0100, Oliver Fromme wrote: Hello, I need some advice how to debug this issue ... Recently I got a new mainboard for a router, it's a Gigabyte GA-H77N-WIFI with two onboard re(4) NICs. The problem is that re0 works fine and re1 doesn't: It doesn't receive any packets. Tcpdump displays all outgoing packets, but no incoming ones on re1. Can you see the packets sent from re1 on other box? If not, it probably indicates GMAC is in weird state which in turn indicates initialization was not complete for the controller. Ifconfig shows the link correctly (100 or 1000 Mbit, depending on where I plug the cable in). I also swapped cables just to be sure, but it made no difference. If you cold-boot the box with UTP cable plugged in to re1 does it make any difference? I'm running a recent stable/9 (about 14 days old). What's the best way to debug this problem? At the I would check whether GMAC is active when driver detects a valid link. Add a code like the following to re_miibus_statchg() to get the status of RL_COMMAND register. You would get the status whenever a link is established with link partner. Index: if_re.c === --- if_re.c (revision 246338) +++ if_re.c (working copy) @@ -626,6 +626,9 @@ default: break; } + if (sc-rl_flags RL_FLAG_LINK) + device_printf(sc-rl_dev, CMD 0x%02x\n, + CSR_READ_1(sc, RL_COMMAND)); } /* * RealTek controllers does not provide any interface to moment I'm not even sure if it's the hardware, or if it's FreeBSD's fault (or my fault) ... Best regards Oliver PS: dmesg ... pcib2: ACPI PCI-PCI bridge irq 16 at device 28.4 on pci0 pci2: ACPI PCI bus on pcib2 re0: RealTek 8168/8111 B/C/CP/D/DP/E/F PCIe Gigabit Ethernet port 0xe000-0xe0ff mem 0xf0104000-0xf0104fff,0xf010-0xf0103fff irq 16 at device 0.0 on pci2 re0: Using 1 MSI-X message re0: Chip rev. 0x2c80 re0: MAC rev. 0x miibus0: MII bus on re0 rgephy0: RTL8169S/8110S/8211 1000BASE-T media interface PHY 1 on miibus0 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 90:2b:34:5f:bd:21 pcib3: ACPI PCI-PCI bridge irq 17 at device 28.5 on pci0 pci3: ACPI PCI bus on pcib3 re1: RealTek 8168/8111 B/C/CP/D/DP/E/F PCIe Gigabit Ethernet port 0xd000-0xd0ff mem 0xf0004000-0xf0004fff,0xf000-0xf0003fff irq 17 at device 0.0 on pci3 re1: Using 1 MSI-X message re1: Chip rev. 0x2c80 re1: MAC rev. 0x miibus1: MII bus on re1 rgephy1: RTL8169S/8110S/8211 1000BASE-T media interface PHY 1 on miibus1 rgephy1: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re1: Ethernet address: 90:2b:34:5f:bd:11 ifconfig ... re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE ether 90:2b:34:5f:bd:21 inet ... nd6 options=21PERFORMNUD,AUTO_LINKLOCAL media: Ethernet autoselect (1000baseT full-duplex) status: active re1: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 options=8209bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,WOL_MAGIC,LINKSTATE ether 90:2b:34:5f:bd:11 inet ... nd6 options=21PERFORMNUD,AUTO_LINKLOCAL media: Ethernet autoselect (100baseTX full-duplex) status: active ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: csh/tcsh: odd %~ prompt variable behaviour
Looks like it could be FreeBSD specific... I very rarely use {,t}csh
myself.
user@host:~$ uname -a
Linux host 3.5.0-23-generic #35-Ubuntu SMP Thu Jan 24 13:15:40 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
user@host:~$ sudo -i
[sudo] password for user:
root@host:~# tcsh
host:~# set prompt = %N@%m:%~ %#
root@host:~ # asdfasdf
asdfasdf: Command not found.
root@host:~ # cd ~user
root@host:~user # asdfasdf
asdfasdf: Command not found.
root@host:~user # exit
root@host:~# logout
On Tue, Feb 5, 2013 at 5:10 PM, Jeremy Chadwick j...@koitsu.org wrote:
(Please keep me CC'd as I'm not subscribed to the list)
System is base/stable/9, r245697. tcsh version is 6.18.01:
$ sudo -i
root@icarus:~ # sfdjsdj
sfdjsdj: Command not found.
root@icarus:~ # cd ~root
root@icarus:~ # dsjfdsfdsf
dsjfdsfdsf: Command not found.
root@icarus:~ # cd ~jdc
root@icarus:~jdc # sdjfdjkfjdsk
sdjfdjkfjdsk: Command not found.
root@icarus:/home/jdc # notice sudden prompt change
root@icarus:/home/jdc # cd ~root
root@icarus:~ # dsfjjdskdfs
dsfjjdskdfs: Command not found.
root@icarus:~ # logout
This only happens when an invalid command is issued (e.g. had I used
ls instead of blah the prompt would not have changed).
$prompt is the standard /root/.cshrc (r244005) value:
set prompt = %N@%m:%~ %#
I cannot reproduce this problem on Debian 6.0.1 with tcsh 6.17.02:
$ ssh jdc@192.168.1.161
Linux debian 2.6.32-5-686 #1 SMP Sun Sep 23 09:49:36 UTC 2012 i686
Last login: Tue Feb 3 19:22:19 2013 from icarus.home.lan
jdc@debian:~$ sudo -i
root@debian:~# /bin/tcsh
debian:~# set prompt = %N@%m:%~ %#
root@debian:~ # sdfsdf
sdfsdf: Command not found.
root@debian:~ # cd ~jdc
root@debian:~jdc # sdfssgsgjsj
sdfssgsgjsj: Command not found.
root@debian:~jdc # exit
root@debian:~# logout
The number of changes between 6.17.02 and 6.18.01 seem quite large
(looking at src/contrib/tcsh/Fixes).
Does anyone have a non-FreeBSD system with tcsh 6.18.01 available
to determine if this is a FreeBSD-centric issue or an actual issue with
tcsh that needs to be reported upstream?
Thanks.
--
| Jeremy Chadwick j...@koitsu.org |
| UNIX Systems Administratorhttp://jdc.koitsu.org/ |
| Mountain View, CA, US|
| 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 freebsd-stable-unsubscr...@freebsd.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD-9.1 would not boot on pentium3 laptop
On 05.02.2013 23:38, Mikhail T. wrote: What happened between 6.x and 7.x? Ok, what happened is that device cpufreq is now in GENERIC and the ichss0 along with it. Setting set hint.ichss.0.disabled=1 on the loader prompt allows me to boot -- both my own kernel as well as the 9.1-RELEASE from CD. Solved... Annoying beyond belief, but solved. Now, if only I could figure out, why my network card (3COM's 3C556 Mini PCI) is not seen by the 9.1... It was working perfectly fine with 6.3 -- and still works with the FreeSBIE-2.0.1 -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: csh/tcsh: odd %~ prompt variable behaviour
Michael,
Thank you very much! What tcsh version is that? echo $version should
say. :-)
--
| Jeremy Chadwick j...@koitsu.org |
| UNIX Systems Administratorhttp://jdc.koitsu.org/ |
| Mountain View, CA, US|
| Making life hard for others since 1977. PGP 4BD6C0CB |
On Tue, Feb 05, 2013 at 10:05:44PM -0800, Galati, Michael wrote:
Looks like it could be FreeBSD specific... I very rarely use {,t}csh
myself.
user@host:~$ uname -a
Linux host 3.5.0-23-generic #35-Ubuntu SMP Thu Jan 24 13:15:40 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
user@host:~$ sudo -i
[sudo] password for user:
root@host:~# tcsh
host:~# set prompt = %N@%m:%~ %#
root@host:~ # asdfasdf
asdfasdf: Command not found.
root@host:~ # cd ~user
root@host:~user # asdfasdf
asdfasdf: Command not found.
root@host:~user # exit
root@host:~# logout
On Tue, Feb 5, 2013 at 5:10 PM, Jeremy Chadwick j...@koitsu.org wrote:
(Please keep me CC'd as I'm not subscribed to the list)
System is base/stable/9, r245697. tcsh version is 6.18.01:
$ sudo -i
root@icarus:~ # sfdjsdj
sfdjsdj: Command not found.
root@icarus:~ # cd ~root
root@icarus:~ # dsjfdsfdsf
dsjfdsfdsf: Command not found.
root@icarus:~ # cd ~jdc
root@icarus:~jdc # sdjfdjkfjdsk
sdjfdjkfjdsk: Command not found.
root@icarus:/home/jdc # notice sudden prompt change
root@icarus:/home/jdc # cd ~root
root@icarus:~ # dsfjjdskdfs
dsfjjdskdfs: Command not found.
root@icarus:~ # logout
This only happens when an invalid command is issued (e.g. had I used
ls instead of blah the prompt would not have changed).
$prompt is the standard /root/.cshrc (r244005) value:
set prompt = %N@%m:%~ %#
I cannot reproduce this problem on Debian 6.0.1 with tcsh 6.17.02:
$ ssh jdc@192.168.1.161
Linux debian 2.6.32-5-686 #1 SMP Sun Sep 23 09:49:36 UTC 2012 i686
Last login: Tue Feb 3 19:22:19 2013 from icarus.home.lan
jdc@debian:~$ sudo -i
root@debian:~# /bin/tcsh
debian:~# set prompt = %N@%m:%~ %#
root@debian:~ # sdfsdf
sdfsdf: Command not found.
root@debian:~ # cd ~jdc
root@debian:~jdc # sdfssgsgjsj
sdfssgsgjsj: Command not found.
root@debian:~jdc # exit
root@debian:~# logout
The number of changes between 6.17.02 and 6.18.01 seem quite large
(looking at src/contrib/tcsh/Fixes).
Does anyone have a non-FreeBSD system with tcsh 6.18.01 available
to determine if this is a FreeBSD-centric issue or an actual issue with
tcsh that needs to be reported upstream?
Thanks.
--
| Jeremy Chadwick j...@koitsu.org |
| UNIX Systems Administratorhttp://jdc.koitsu.org/ |
| Mountain View, CA, US|
| 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 freebsd-stable-unsubscr...@freebsd.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD-9.1 would not boot on pentium3 laptop
On 06.02.2013 01:24, Mikhail T. wrote: Now, if only I could figure out, why my network card (3COM's 3C556 Mini PCI) is not seen by the 9.1... Disabling Wake on LAN in the BIOS solved this problem. Now xl0 is seen and functional. Solved. I struggle to understand, how a less seasoned user could be expected to figure these two issues out... -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD-9.1 would not boot on pentium3 laptop
Hi, On Wed, 06 Feb 2013 00:11:28 -0500 Mikhail T. mi+t...@aldan.algebra.com wrote: On 05.02.2013 23:50, Erich Dollansky wrote: USB? That would be a shame -- I'm dressing up this old machine to be used with a couple of USB-devices. try 7.4. This worked for me until a lightning came. I have had a Fujitsu LifeBook which I only could use with 7.x out for the same reason. Is there a PR? Thanks, No. I did not want to bother people for such an old device. Erich ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD-9.1 would not boot on pentium3 laptop
On 06.02.2013 01:57, Erich Dollansky wrote: I have had a Fujitsu LifeBook which I only could use with 7.x out for the same reason. Is there a PR? Thanks, No. I did not want to bother people for such an old device. You should have. If it is listed as supported, it should be working. And FreeBSD still supports 486 CPUs (though not the 386). Testing old devices is difficult for developers, so they'd rely on users like yourself to tell them about regressions... -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD-9.1 would not boot on pentium3 laptop
On Wed, Feb 06, 2013 at 01:40:11AM -0500, Mikhail T. wrote: On 06.02.2013 01:24, Mikhail T. wrote: Now, if only I could figure out, why my network card (3COM's 3C556 Mini PCI) is not seen by the 9.1... Disabling Wake on LAN in the BIOS solved this problem. Now xl0 is seen and functional. Solved. Because I added WOL support xl(4) in the past I'm interested in knowing whether that change broke your controller when BIOS enables WOL. If you boot with bootverbose, do you see a message like No auxiliary remote wakeup connector! from xl(4)? (of course, WOL should be enabled in BIOS before boot) Also show the output of 'pciconf -lcbv. I struggle to understand, how a less seasoned user could be expected to figure these two issues out... -mi ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
