From owner-freebsd-hardware Sun Apr 14 12: 3: 3 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from wartch.sapros.com (rularan.sapros.com [204.182.55.17]) by hub.freebsd.org (Postfix) with ESMTP id 8F15B37B400 for ; Sun, 14 Apr 2002 12:02:59 -0700 (PDT) Received: from wartch.sapros.com (localhost.sapros.com [127.0.0.1]) by wartch.sapros.com (8.12.1/8.12.1) with ESMTP id g3EJ2rRg031891 for ; Sun, 14 Apr 2002 12:02:53 -0700 (PDT) (envelope-from peterh@wartch.sapros.com) Message-Id: <200204141902.g3EJ2rRg031891@wartch.sapros.com> To: hardware@freebsd.org Subject: Reading from the USB ugen device. Date: Sun, 14 Apr 2002 12:02:52 -0700 From: Peter Haight X-Spam-Status: No, hits=1.8 required=7.0 tests=NO_MX_FOR_FROM version=2.11 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I've been working with an application called coldsync to get my Sony Clie to sync to my computer. I'm using FreeBSD-4.5-STABLE. I've gotten it to work, but I ran into an issue I don't understand and I'd like to know what's going on. The software begins by sending a USB_DISCOVER on usb0 and then tries to open /dev/ugen0. If that succeeds it checks to make sure the device is the Clie (using USB_GET_DEVICEINFO) and then it sends a vendor information request over the control endpoint. From the information it gets back from that it figures out which endpoint to open and then it opens that one (Usually ugen0.2). Then it sends the USB_SET_SHORT_XFER on that device. The original author of the code, had a routine which reads data from the ugen0.2 device 1024 bytes at a time. A comment in the code indicates that it needs to make sure it reads any data available because the kernel isn't buffering anything. Well, that would work for about 8 reads (read(2)) and if I ran it under gdb, each of those reads would actually just return whatever amount of data we were expecting according to the protocol. Probably about 6-100 bytes at a time. Then it would just block indefinitely when I was expecting 64 bytes. I managed to fix it by getting rid of the 1024 byte reads and just reading whatever I was expecting. Once I made that change, it didn't block on that read and then went on to read the rest of about 6MB from the device. I don't get it. My only guess is that when doing it the other way the timing changes subtly so that I'm not in the read when the next set of data comes and since it is unbuffered it just gets discarded by the kernel. The problem with this theory is that I've not changed the part of the code that manages the buffer. So I don't really see how the timing could be different because if I run it with the buffering on, it never gets a read longer than what I was expecting. The actual read lengths are exactly the same whether I request 1024 bytes or the number of bytes I'm expecting, but if I use 1024 it eventually blocks. Anyway, this all has me worried about timing with an unbuffered device. I don't have a good understanding of what's going on, so I'm not sure what's a good way to deal with this issue. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Apr 14 16: 5:45 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from twinlark.arctic.org (twinlark.arctic.org [208.44.199.239]) by hub.freebsd.org (Postfix) with ESMTP id 3B5D437B404 for ; Sun, 14 Apr 2002 16:05:43 -0700 (PDT) Received: (qmail 14615 invoked by uid 1347); 14 Apr 2002 14:05:42 -0000 Date: 14 Apr 2002 14:05:42 -0000 Message-ID: <20020414140542.14614.qmail@twinlark.arctic.org> From: atk2@arctic.org To: freebsd-hardware@freebsd.org Subject: trest Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org test to see if i get message... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Apr 14 16:53:57 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [62.49.12.213]) by hub.freebsd.org (Postfix) with ESMTP id 9CC2337B404 for ; Sun, 14 Apr 2002 16:53:43 -0700 (PDT) Received: by arg1.demon.co.uk (Postfix, from userid 1002) id 6F5EC9B06; Mon, 15 Apr 2002 00:53:42 +0100 (BST) Received: from localhost (localhost [127.0.0.1]) by arg1.demon.co.uk (Postfix) with ESMTP id 669465D0C; Mon, 15 Apr 2002 00:53:42 +0100 (BST) Date: Mon, 15 Apr 2002 00:53:42 +0100 (BST) From: Andrew Gordon X-X-Sender: To: Peter Haight Cc: Subject: Re: Reading from the USB ugen device. In-Reply-To: <200204141902.g3EJ2rRg031891@wartch.sapros.com> Message-ID: <20020415002005.W79917-100000@server.arg.sj.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sun, 14 Apr 2002, Peter Haight wrote: > > I've been working with an application called coldsync to get my Sony Clie to > sync to my computer. I'm using FreeBSD-4.5-STABLE. I've gotten it to work, > but I ran into an issue I don't understand and I'd like to know what's going > on. I don't know anything about coldsync, but here are a few notes about receiving with the ugen driver. Apologies if I'm telling you stuff that's obvious or you already know. > The software begins by sending a USB_DISCOVER on usb0 and then tries to open > /dev/ugen0. If that succeeds it checks to make sure the device is the Clie > (using USB_GET_DEVICEINFO) and then it sends a vendor information request > over the control endpoint. From the information it gets back from that it > figures out which endpoint to open and then it opens that one (Usually > ugen0.2). Then it sends the USB_SET_SHORT_XFER on that device. USB_SET_SHORT_XFER indicates that you are expecting the device to indicate the end of a transaction, rather than you knowing the exact size in advance. The way bulk read transfers work on the bus is that the host polls the USB device repeatedly: the device can respond with a NAK (no data currently available; this is just flow-control and has no impact on terminating the transaction unless it NAKs repeatedly and a timeout occurs); or it can respond with a full-size packet, indicating that the transaction isn't complete and it should be polled again immediately to get more; or it can respond with a less-than-full-size packet indicating end of transaction (zero-length is permitted to cover the case where the transaction is a multiple of the packet size). The definition of 'full size' is fixed in the device's configuration, normally 64 bytes. > The original author of the code, had a routine which reads data from the > ugen0.2 device 1024 bytes at a time. A comment in the code indicates that it > needs to make sure it reads any data available because the kernel isn't > buffering anything. > > Well, that would work for about 8 reads (read(2)) and if I ran it under gdb, > each of those reads would actually just return whatever amount of data we > were expecting according to the protocol. Probably about 6-100 bytes at a > time. Then it would just block indefinitely when I was expecting 64 bytes. > > I managed to fix it by getting rid of the 1024 byte reads and just reading > whatever I was expecting. Once I made that change, it didn't block on that > read and then went on to read the rest of about 6MB from the device. With the ugen driver, you are expected to either: a) Don't set USB_SET_SHORT_XFER, and do read() calls with exactly the buffer size required. b) Set USB_SET_SHORT_XFER and use a buffer larger than the largest possible transaction; the result will contain exactly one transaction. I haven't analysed exactly what happens when you use a buffer shorter than the transaction size (the devices I've been playing with don't do huge transfers in one lump). However, there is an obvious ambiguity when the transaction size turns out to be an exact multiple of the buffer size you are using: after reading N full buffers, you don't know if the last buffer was full because there is more data to follow, or if it was full because the transaction ended there, as for the USB_SET_SHORT_TRANSFER=0 case. Possibly you get a 0-length read next time, but I suspect that in fact that the information is lost and you can't tell. > Anyway, this all has me worried about timing with an unbuffered device. I > don't have a good understanding of what's going on, so I'm not sure what's a > good way to deal with this issue. Timing isn't usually an issue with bulk transfers (unless your device has overall throughput requirements) since the flow-control is fairly transparent. However, there are a number of things that work really badly with the ugen driver: - Full duplex: you can only achieve this by forking two processes, as the driver doesn't support select()/poll(), mainly because it doesn't allow queued transactions. - Streaming throughput: You have the choice of doing large transactions, which give good throughput (transferred as fast as the bus/device can go) but leave your process blocked for the duration and unable to work on preparing for the next transaction; or you do small transactions, in which case the throughput drops off disasterously since there will be a delay between exiting one read()/write() call on the driver and initiating the next, during which the USB bus goes idle - this will often be quite a long delay if your process has got de-scheduled in the meantime. I had been thinking of adding another mode to ugen where there is a queue of read/write transactions and you can use select() to pace the creation of new transactions - as you do with a socket or a tty style device. This would be quite easy to add to ugen to suit my requirements (maintaining a smooth stream of smallish (~1Kbyte) transactions in both directions), but enhancing it to solve your problem of wanting to break a huge transaction into small pieces (and presumably to start processing those pieces before the transaction is complete) would be more tricky. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Apr 14 17:23: 1 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from twinlark.arctic.org (twinlark.arctic.org [208.44.199.239]) by hub.freebsd.org (Postfix) with ESMTP id 043A937B405 for ; Sun, 14 Apr 2002 17:22:58 -0700 (PDT) Received: (qmail 8441 invoked by uid 1347); 14 Apr 2002 13:16:16 -0000 Date: 14 Apr 2002 13:16:16 -0000 Message-ID: <20020414131616.8440.qmail@twinlark.arctic.org> From: atk2@arctic.org To: freebsd-hardware@FreeBSD.ORG Subject: Is kt333 or nvida 415D stable enough for bsd 4.5 ? Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I currently run freebsd 2.2.7 (rather dated) on a p100 as an interactive system (not a server). The system has been up for over 570 days so it is fairly stable (though I had to reset the x-server once about 2 months ago when I switched mouse - due to the old one failing). I plan on upgrading in the next few weeks with the following hardware: Maxtor 6L040L3 hard disk $100 Lite-on 16x dvd player $50 Lite-on 163 cdrw $85 AMD 1.8XP $130 2x256mb ddr pc2100 2x$70 antec 840 case $110 (360w power supply) (from old sytem 3 scsi ii drives, cheap nic card, scsi ii card and vodoo 3/2000 (hey it has good 2d)) Now the question is what motherbord. I'd like to go with either the abit nv7-133 $128 or asus a7v-333 $125 I realize that 4.5 does not suppor the sound/nic on the nv7-133 (the raid chip is supported but I'm not planning on using it). The sound card on the asus a7v333 is supported (not sure about the usb 2.0). Anyways I've heard that the older via chips (kt266/kt266a) are not so stable hence this question. I mention the other hardware in case there are other problems (I wouldn't mind swapping the Lite-on for pioneer/plextor for example if they are bad drives). However, given prices I'd rather not go with an (for example) ultra 160 scsi drisk ($130 for controller + $150 for drive) -- I'd like to keep this system rather inexpensive -- and go for stability over performance when I have to compromise. On the other hand benchmarks I've seen show that the write (to eide hard drive) performance is significantly better with either of these boards (10 to 15 percent) compared to older boards (kt266/kt266a, amd 761 and ali). Oh well any suggestions/comments ? Thanks, Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Apr 14 18: 7:53 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from wartch.sapros.com (rularan.sapros.com [204.182.55.17]) by hub.freebsd.org (Postfix) with ESMTP id 388BF37B404 for ; Sun, 14 Apr 2002 18:07:47 -0700 (PDT) Received: from wartch.sapros.com (localhost.sapros.com [127.0.0.1]) by wartch.sapros.com (8.12.1/8.12.1) with ESMTP id g3F17WRg033229; Sun, 14 Apr 2002 18:07:32 -0700 (PDT) (envelope-from peterh@wartch.sapros.com) Message-Id: <200204150107.g3F17WRg033229@wartch.sapros.com> To: Andrew Gordon Cc: hardware@freebsd.org Subject: Re: Reading from the USB ugen device. Date: Sun, 14 Apr 2002 18:07:32 -0700 From: Peter Haight X-Spam-Status: No, hits=1.8 required=7.0 tests=NO_MX_FOR_FROM version=2.11 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >I don't know anything about coldsync, but here are a few notes about >receiving with the ugen driver. Apologies if I'm telling you stuff that's >obvious or you already know. Your explanations are great. I'm really ignorant on this stuff. >I haven't analysed exactly what happens when you use a buffer shorter than >the transaction size (the devices I've been playing with don't do huge >transfers in one lump). However, there is an obvious ambiguity when the >transaction size turns out to be an exact multiple of the buffer size you >are using: after reading N full buffers, you don't know if the last buffer >was full because there is more data to follow, or if it was full because >the transaction ended there, as for the USB_SET_SHORT_TRANSFER=0 case. >Possibly you get a 0-length read next time, but I suspect that in fact >that the information is lost and you can't tell. This gives me an idea. Here are two short logs of what's happening. They are both with short transfer on, but with the first, I'm always asking for 1024 and with the second, I'm just asking for what I expect the size of the transaction to be: First log: Attempting read(3, 0x8091800, 1024) read 6 bytes Attempting read(3, 0x8091800, 1024) read 22 bytes Attempting read(3, 0x8091800, 1024) read 6 bytes Attempting read(3, 0x8091800, 1024) read 50 bytes Attempting read(3, 0x8091800, 1024) read 6 bytes Attempting read(3, 0x8091800, 1024) read 8 bytes Attempting read(3, 0x8091800, 1024) read 6 bytes Attempting read(3, 0x8091800, 1024) read 34 bytes Attempting read(3, 0x8091800, 1024) read 6 bytes Attempting read(3, 0x8091800, 1024) read 38 bytes Attempting read(3, 0x8091800, 1024) read 6 bytes Attempting read(3, 0x8091800, 1024) read 44 bytes Attempting read(3, 0x8091800, 1024) read 6 bytes Attempting read(3, 0x8091800, 1024) read 49 bytes Attempting read(3, 0x8091800, 1024) read 6 bytes Attempting read(3, 0x8091800, 1024) read 88 bytes Attempting read(3, 0x8091800, 1024) read 6 bytes Attempting read(3, 0x8091800, 1024) read -1 bytes Second Log: Attempting read(3, 0x8091800, 6) read 6 bytes Attempting read(3, 0x8091800, 22) read 22 bytes Attempting read(3, 0x8091800, 6) read 6 bytes Attempting read(3, 0x8091800, 50) read 50 bytes Attempting read(3, 0x8091800, 6) read 6 bytes Attempting read(3, 0x8091800, 8) read 8 bytes Attempting read(3, 0x8091800, 6) read 6 bytes Attempting read(3, 0x8091800, 34) read 34 bytes Attempting read(3, 0x8091800, 6) read 6 bytes Attempting read(3, 0x8091800, 38) read 38 bytes Attempting read(3, 0x8091800, 6) read 6 bytes Attempting read(3, 0x8091800, 44) read 44 bytes Attempting read(3, 0x8091800, 6) read 6 bytes Attempting read(3, 0x8091800, 49) read 49 bytes Attempting read(3, 0x8091800, 6) read 6 bytes Attempting read(3, 0x8091800, 88) read 88 bytes Attempting read(3, 0x8091800, 6) read 6 bytes Attempting read(3, 0x8091800, 64) read 64 bytes From what you told me and a brief look at the USB spec, I'm guessing it isn't a coincidence that it is failing on that read where I'm expecting 64 bytes (the max size of a USB packet payload). I'm guessing that in short read mode, the driver gets a full length packet and is expecting another data packet but it never comes because that's the end of the data, so it doesn't return from the read until it gets a timeout. I'd like to watch the debug messages for the ugen driver, but I'm having trouble getting the debug messages to go. I put 'options UGEN_DEBUG' in my kernel conf file and I recompiled and installed, but when I do a 'nm /modules/ugen.ko | grep ugendebug' that symbol isn't defined and if I try to do an ioctl(USB_SETDEBUG) I get an 'Invalid Argument' error. It turns out that if I do 'nm ugen.o | grep ugendebug' in my kernel compile directory it prints out the symbol, but the kernel module doesn't seem to be getting the option. In fact if I look at opt_usb.h in my kernel compile directory I see '#define UGEN_DEBUG 1', but if I look at 'modules/usr/src/sys/modules/ugen/opt_usb.h' under my kernel compile directory, it is blank. >I had been thinking of adding another mode to ugen where there is a queue >of read/write transactions and you can use select() to pace the creation >of new transactions - as you do with a socket or a tty style device. This >would be quite easy to add to ugen to suit my requirements (maintaining a >smooth stream of smallish (~1Kbyte) transactions in both directions), but >enhancing it to solve your problem of wanting to break a huge transaction >into small pieces (and presumably to start processing those pieces before >the transaction is complete) would be more tricky. Ahh. I'm beginning to understand why he did it. His scenario would go something like this: - write a request to the palm for a list of databases - read the packet header returned from the palm: read(6) - from the packet header, get the length and read that: read(123) I think the problem he was trying to combat was that he thought that the following could happen: - write a request to the palm for a list of databases - read the packet header returned from the palm: read(6) - the ugen driver reads a 129 byte transaction from the USB bus and returns 6 bytes, but deletes the other 123 bytes because it doesn't buffer between reads. - from the packet header, get the length and read that: read(123), but this read would then fail because the rest of that data was wiped after the previous read Is that possible? If it is, I think that it is working without his buffering because the header is sent in a separate transaction from the payload. So when he does that read(6) it is just grabbing the header transaction and the next 123 bytes comes in the next transaction. (These headers and payloads are a protocol on top of USB, not the USB protocol headers and payloads). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 15 2:32:11 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from van-laarhoven.org (ap-z-5ab8.adsl.wanadoo.nl [212.129.218.184]) by hub.freebsd.org (Postfix) with SMTP id 4C1C937B416 for ; Mon, 15 Apr 2002 02:32:04 -0700 (PDT) Received: (qmail 58024 invoked from network); 15 Apr 2002 09:32:03 -0000 Received: from heather.van-laarhoven.org (10.66.0.2) by uitsmijter.van-laarhoven.org with SMTP; 15 Apr 2002 09:32:03 -0000 Date: Mon, 15 Apr 2002 11:32:03 +0200 (CEST) From: Nick Hibma To: Peter Haight Cc: Andrew Gordon , "hardware@freebsd.org" Subject: Re: Reading from the USB ugen device. In-Reply-To: <200204150107.g3F17WRg033229@wartch.sapros.com> Message-ID: <20020415112318.L36693-100000@heather.van-laarhoven.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > From what you told me and a brief look at the USB spec, I'm guessing it > isn't a coincidence that it is failing on that read where I'm expecting 64 > bytes (the max size of a USB packet payload). I'm guessing that in short > read mode, the driver gets a full length packet and is expecting another > data packet but it never comes because that's the end of the data, so it > doesn't return from the read until it gets a timeout. No. If you read 64 byes in 64 bytes with short_XFER switched on you will be reading 64 bytes and then 0 bytes. > I'd like to watch the debug messages for the ugen driver, but I'm having > trouble getting the debug messages to go. I put 'options UGEN_DEBUG' in my > kernel conf file and I recompiled and installed, but when I do a 'nm > /modules/ugen.ko | grep ugendebug' that symbol isn't defined and if I try to > do an ioctl(USB_SETDEBUG) I get an 'Invalid Argument' error. It turns out > that if I do 'nm ugen.o | grep ugendebug' in my kernel compile directory it > prints out the symbol, but the kernel module doesn't seem to be getting the > option. In fact if I look at opt_usb.h in my kernel compile directory I see > '#define UGEN_DEBUG 1', but if I look at > 'modules/usr/src/sys/modules/ugen/opt_usb.h' under my kernel compile > directory, it is blank. kernel config doesn't cover module build. Add CFLAGS+= -DUGEN_DEBUG in /sys/modules/ugen/Makefile. > - write a request to the palm for a list of databases > - read the packet header returned from the palm: read(6) > - from the packet header, get the length and read that: read(123) > > I think the problem he was trying to combat was that he thought that the > following could happen: > - write a request to the palm for a list of databases > - read the packet header returned from the palm: read(6) > - the ugen driver reads a 129 byte transaction from the USB bus and returns > 6 bytes, but deletes the other 123 bytes because it doesn't buffer between > reads. > - from the packet header, get the length and read that: read(123), but this > read would then fail because the rest of that data was wiped after the > previous read > > Is that possible? If it is, I think that it is working without his buffering > because the header is sent in a separate transaction from the payload. So > when he does that read(6) it is just grabbing the header transaction and > the next 123 bytes comes in the next transaction. > (These headers and payloads are a protocol on top of USB, not the USB > protocol headers and payloads). The USB subsystem does not do any buffering at all on bulk transfers. When you ask for N bytes the ugen driver goes and asks for the device for N bytes, or up to N bytes if SHORT_XFER is switched on, possibly in multiple transfers, but always a multiple of the packet size on the wire (to avoid missing a short tranfser). Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 15 2:33:23 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from van-laarhoven.org (ap-z-5ab8.adsl.wanadoo.nl [212.129.218.184]) by hub.freebsd.org (Postfix) with SMTP id 45B0B37B416 for ; Mon, 15 Apr 2002 02:33:04 -0700 (PDT) Received: (qmail 58036 invoked from network); 15 Apr 2002 09:33:03 -0000 Received: from heather.van-laarhoven.org (10.66.0.2) by uitsmijter.van-laarhoven.org with SMTP; 15 Apr 2002 09:33:03 -0000 Date: Mon, 15 Apr 2002 11:33:03 +0200 (CEST) From: Nick Hibma To: Chris Child Cc: "freebsd-hardware@freebsd.org" Subject: Re: Logitech iFeel USB mouse attach error In-Reply-To: <000801c1e288$9f491100$0700a8c0@spiderman> Message-ID: <20020415113212.D36693-100000@heather.van-laarhoven.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This sounds like a problem that is not very easy to fix. Did you try with a (self-powered) hub in between the host and the mouse? The fact that the ugen driver does not attach might mean that the mouse has gone south by the time it is time to attach to it. Nick On Fri, 12 Apr 2002, Chris Child wrote: > Hi. I'm new to freebsd, and am having some trouble getting my mouse to > work. > > I installed the 4.5-mini .iso. After booting, everything appeared to be > working fine except for my mouse. I have a Logitech iFeel USB mouse. In > dmesg, I can see and error after recognizing it (device_probe_and_attach: > ums0 attach returned 6). I'm attached my kernel config file (JACKICE) and > the dmesg output (dmesg.log). > > As a secondary question, dmesg seems to show the result of three boots, one > with the GENERIC kernel, and two with my new kernel. Is this supposed to > be? Thanks. > > -Chris Child > > Thanks in advance, and I'm not sure if it's standard practice on these > message lists, but please cc a copy of the reply to me. > -- n_hibma@van-laarhoven.org http://www.van-laarhoven.org/ n_hibma@FreeBSD.org http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 15 10:47:41 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from wartch.sapros.com (rularan.sapros.com [204.182.55.17]) by hub.freebsd.org (Postfix) with ESMTP id 7238437B405 for ; Mon, 15 Apr 2002 10:47:37 -0700 (PDT) Received: from wartch.sapros.com (localhost.sapros.com [127.0.0.1]) by wartch.sapros.com (8.12.1/8.12.1) with ESMTP id g3FHlPRg037046; Mon, 15 Apr 2002 10:47:25 -0700 (PDT) (envelope-from peterh@wartch.sapros.com) Message-Id: <200204151747.g3FHlPRg037046@wartch.sapros.com> To: Nick Hibma Cc: hardware@freebsd.org Subject: Re: Reading from the USB ugen device. Date: Mon, 15 Apr 2002 10:47:25 -0700 From: Peter Haight X-Spam-Status: No, hits=1.8 required=7.0 tests=NO_MX_FOR_FROM version=2.11 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >> From what you told me and a brief look at the USB spec, I'm guessing it >> isn't a coincidence that it is failing on that read where I'm expecting 64 >> bytes (the max size of a USB packet payload). I'm guessing that in short >> read mode, the driver gets a full length packet and is expecting another >> data packet but it never comes because that's the end of the data, so it >> doesn't return from the read until it gets a timeout. > >No. If you read 64 byes in 64 bytes with short_XFER switched on you will >be reading 64 bytes and then 0 bytes. Ok. But why does this happen: read(3, 0x8091800, 1024) read -1 bytes At that same point in the protocol if I do: read(3, 0x8091800, 64) read 64 bytes I would expect: read(3, 0x8091800, 1024) read 64 bytes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 15 11:48:20 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from van-laarhoven.org (ap-z-5ab8.adsl.wanadoo.nl [212.129.218.184]) by hub.freebsd.org (Postfix) with SMTP id A443B37B416 for ; Mon, 15 Apr 2002 11:48:15 -0700 (PDT) Received: (qmail 61475 invoked from network); 15 Apr 2002 18:48:12 -0000 Received: from heather.van-laarhoven.org (10.66.0.2) by uitsmijter.van-laarhoven.org with SMTP; 15 Apr 2002 18:48:12 -0000 Date: Mon, 15 Apr 2002 20:48:12 +0200 (CEST) From: Nick Hibma To: Peter Haight Cc: "hardware@freebsd.org" Subject: Re: Reading from the USB ugen device. In-Reply-To: <200204151747.g3FHlPRg037046@wartch.sapros.com> Message-ID: <20020415204427.P26630-100000@heather.van-laarhoven.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > >No. If you read 64 bytes in 64 bytes with short_XFER switched on you > >will be reading 64 bytes and then 0 bytes. This should have beenL If you read 64 byte reads with SHORT_XFER on you will be reading 64 bytes and then 0 bytes. > Ok. But why does this happen: > > read(3, 0x8091800, 1024) > read -1 bytes If you print the errno at that point I can tell you. But probably the errno is ETIMEDOUT, which means that the device told us that there is no data, so it NACKed the transfer until we got bored. > At that same point in the protocol if I do: > read(3, 0x8091800, 64) > read 64 bytes > > I would expect: > read(3, 0x8091800, 1024) > read 64 bytes I don't know why it reads 64 instead of 1024 bytes. Most probably the author of the program assumes that he has to do the chunking that is automatically done by the uhci controller driver. Or maybe I misunderstood your question. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 15 12:56:52 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from wartch.sapros.com (rularan.sapros.com [204.182.55.17]) by hub.freebsd.org (Postfix) with ESMTP id CE62637B400 for ; Mon, 15 Apr 2002 12:56:42 -0700 (PDT) Received: from wartch.sapros.com (localhost.sapros.com [127.0.0.1]) by wartch.sapros.com (8.12.1/8.12.1) with ESMTP id g3FJuURg037596; Mon, 15 Apr 2002 12:56:30 -0700 (PDT) (envelope-from peterh@wartch.sapros.com) Message-Id: <200204151956.g3FJuURg037596@wartch.sapros.com> To: Nick Hibma Cc: hardware@freebsd.org Subject: Re: Reading from the USB ugen device. Date: Mon, 15 Apr 2002 12:56:30 -0700 From: Peter Haight X-Spam-Status: No, hits=1.8 required=7.0 tests=NO_MX_FOR_FROM version=2.11 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >> Ok. But why does this happen: >> >> read(3, 0x8091800, 1024) >> read -1 bytes > >If you print the errno at that point I can tell you. But probably the >errno is ETIMEDOUT, which means that the device told us that there is >no data, so it NACKed the transfer until we got bored. Actually, I'm getting an EIO here. >> At that same point in the protocol if I do: >> read(3, 0x8091800, 64) >> read 64 bytes >> >> I would expect: >> read(3, 0x8091800, 1024) >> read 64 bytes > >I don't know why it reads 64 instead of 1024 bytes. Most probably the >author of the program assumes that he has to do the chunking that is >automatically done by the uhci controller driver. Or maybe I >misunderstood your question. Yeah. I don't think I'm being clear. What's going on at this point is that the program is requesting a bunch of information from the palm pilot about what's on it. These are all very short bulk data transfers. Each set goes like this: write(/dev/ugen0.2, header, 6) (length of next write is in header) write(/dev/ugen0.2, data, 8) read(/dev/ugen0.2, header, 6) read(/dev/ugen0.2, data, 62) (length of this read is read from header) I'll call the 'expected read length' the length I read from the header, not the argument I pass to read(). I'll call the argument I pass to read 'requested read length'. The wierd thing is that if 'expected read length' = 'requested read length' everything works fine, but if 'expected read length' = 64 and 'requested read length' = 1024, it hangs and eventually I get a EIO. I would expect that if I have SHORT_XFER set on /dev/ugen0.2, then I could always set my 'requested read length' to 1024 (i.e. read(/dev/ugen0.2, buffer, 1024)) and that should just always return a buffer that is as long as whatever is read from the bus. (Let's ignore the case where the amount of data is bigger than 1024. That isn't happening. These are all very small amounts of data.) I'll stick the function that I'm using to do the read on the end of this email. Someone else wrote this function and it wasn't working for me as you see it below. To get it to work, I had to change the line: u->iobuflen = read(p->fd, u->iobufp, 1024); to: u->iobuflen = read(p->fd, u->iobufp, len); len is the expected read length. This makes no sense to me. I think it should work with the original function. Thanks for putting up with my inability to explain my problem clearly. static int usb_read(PConnection *p, unsigned char *buf, int len) { /* * We've got to do intermediate buffering of the USB data * from the Visor's bulk endpoint. This is because the kernel * USB driver isn't buffering any data, and we must have a read * operation pending at least as large as the USB transfer size * might potentially be. * * Here, we use a 1024 byte buffer, and return data out of * it. This could return "short" reads to the caller, but * isn't semantically any different than reading an TTY device * which won't return a necessarily predicatable amount of * data. */ struct usb_data *u = p->io_private; int copy_len, retlen = 0; do { /* (?) Return leftover stuff from the previous read. */ if (u->iobuflen > 0) { copy_len = (len > u->iobuflen) ? u->iobuflen : len; memcpy(buf, u->iobufp, copy_len); /* XXX - Potential buffer overflow? */ u->iobufp += copy_len; u->iobuflen -= copy_len; buf += copy_len; len -= copy_len; retlen += copy_len; } if (retlen == 0) { /* (?) There wasn't anything left over from the * last read(). Read some new stuff. */ if (u->iobuflen > 0) { fprintf(stderr, _("usb: trying to fill a non-empty " "buffer.\n")); abort(); } u->iobufp = u->iobuf; u->iobuflen = read(p->fd, u->iobufp, 1024); if (u->iobuflen < 0) { perror("usb read"); return u->iobuflen; } } } while (retlen == 0); return retlen; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 15 20:11:43 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mta7.pltn13.pbi.net (mta7.pltn13.pbi.net [64.164.98.8]) by hub.freebsd.org (Postfix) with ESMTP id 7B43037B405 for ; Mon, 15 Apr 2002 20:11:40 -0700 (PDT) Received: from stingray ([63.194.85.207]) by mta7.pltn13.pbi.net (iPlanet Messaging Server 5.1 (built May 7 2001)) with ESMTP id <0GUN0055L4VFYD@mta7.pltn13.pbi.net> for freebsd-hardware@freebsd.org; Mon, 15 Apr 2002 20:11:40 -0700 (PDT) Date: Mon, 15 Apr 2002 20:11:39 -0700 From: Chris Child Subject: Re: Logitech iFeel USB mouse attach error To: Nick Hibma Cc: freebsd-hardware@freebsd.org Message-id: <000d01c1e4f4$6d4535d0$0300a8c0@stingray> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Mailer: Microsoft Outlook Express 6.00.2600.0000 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <20020415113212.D36693-100000@heather.van-laarhoven.org> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have not yet tried it with a hub (I will as soon as I get a chance). One thing I forgot to mention (which probabally confuses the issue more) is that the mouse works fine under Windows, and worked fine under freebsd-4.4 (i reinstalled from the iso to get to 4.5, I wanted to start clean). I'll try the hub idea, please let me know if you can think of anything else. -Chris ----- Original Message ----- From: "Nick Hibma" To: "Chris Child" Cc: Sent: Monday, April 15, 2002 2:33 AM Subject: Re: Logitech iFeel USB mouse attach error > > This sounds like a problem that is not very easy to fix. Did you try > with a (self-powered) hub in between the host and the mouse? > > The fact that the ugen driver does not attach might mean that the mouse > has gone south by the time it is time to attach to it. > > Nick > > > On Fri, 12 Apr 2002, Chris Child wrote: > > > Hi. I'm new to freebsd, and am having some trouble getting my mouse to > > work. > > > > I installed the 4.5-mini .iso. After booting, everything appeared to be > > working fine except for my mouse. I have a Logitech iFeel USB mouse. In > > dmesg, I can see and error after recognizing it (device_probe_and_attach: > > ums0 attach returned 6). I'm attached my kernel config file (JACKICE) and > > the dmesg output (dmesg.log). > > > > As a secondary question, dmesg seems to show the result of three boots, one > > with the GENERIC kernel, and two with my new kernel. Is this supposed to > > be? Thanks. > > > > -Chris Child > > > > Thanks in advance, and I'm not sure if it's standard practice on these > > message lists, but please cc a copy of the reply to me. > > > > -- > n_hibma@van-laarhoven.org http://www.van-laarhoven.org/ > n_hibma@FreeBSD.org http://www.etla.net/~n_hibma/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 15 20:27:24 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id A658437B404 for ; Mon, 15 Apr 2002 20:27:21 -0700 (PDT) Received: by peitho.fxp.org (Postfix, from userid 1206) id D206613667; Mon, 15 Apr 2002 23:27:20 -0400 (EDT) Date: Mon, 15 Apr 2002 23:27:20 -0400 From: Bob Bomar To: hardware@freebsd.org Subject: New Hardware Message-ID: <20020416032720.GA48585@peitho.fxp.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="EeQfGwPcQSOJBaQU" Content-Disposition: inline User-Agent: Mutt/1.3.24i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --EeQfGwPcQSOJBaQU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable I am in the process of building a new computer. The hardware I=20 am looking at is: AMD Athlon XP 2100+ Abit MAX AT7 512 Mb 333 Mhz DDR ATI All-In-Wonder 8500DV Phillips DVD-RW I was wondering if anybody has had any expierence with any of=20 the hardware, and if you have had good or bad opinions of it. Thanks --=20 |------------------------------------| | Bob Bomar | | bulldog@fxp.org | | http://fly.homeunix.org/~bob | |=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D| | FreeBSD: The Power to Serve | | http://www.FreeBSD.org | |------------------------------------| --EeQfGwPcQSOJBaQU Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE8u5oY9Jm/aTrtdKoRAt0ZAJ40U5pOwcWLFVdXvHv3VuxHI7sb4ACcCFKN 4GOPOzNZwiNAcy0ZQ4Jr2XY= =DbNL -----END PGP SIGNATURE----- --EeQfGwPcQSOJBaQU-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Apr 15 23:43:23 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from ulairi.csun.edu (ulairi.csun.edu [130.166.10.16]) by hub.freebsd.org (Postfix) with SMTP id 4783737B404 for ; Mon, 15 Apr 2002 23:43:20 -0700 (PDT) Received: (qmail 6138 invoked by uid 60001); 16 Apr 2002 06:40:59 -0000 Received: from 68.66.191.245 ( [68.66.191.245]) as user ulairi@ulairi.csun.edu by ulairi.csun.edu with HTTP; Mon, 15 Apr 2002 23:40:58 +0700 Message-ID: <1018939258.3cbbc77ade362@ulairi.csun.edu> Date: Mon, 15 Apr 2002 23:40:58 +0700 From: ulairi@ulairi.org To: hardware@freebsd.org Subject: Weirdness with HD geometry MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 8bit User-Agent: Internet Messaging Program (IMP) 2.3.7-cvs Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org First, the setup particulars: SuperMicro P6DBE motherboard, bios rev 3.1 Seagate 40 GB UDMA drive is master on IDE0 36x generic CDROM is master on IDE1 BIOS says geometry is 16838/16/63, which matches the printed label on the drive. 4.5R install CD in boot-v mode shows that ad0 is detected with 77545/16/63 geometry, which is... insane. Tried using both the kernel-detected geometry, and the BIOS-detected one - same result: "read error" trying to boot. Am I missing something blatantly obvious or should I go get the chicken and the goat ready for the sacrificial rites of Black Magic of FreeBSD (tm)? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 16 7:54:46 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id AC76D37B404 for ; Tue, 16 Apr 2002 07:54:39 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id AAA20031; Wed, 17 Apr 2002 00:54:15 +1000 Date: Wed, 17 Apr 2002 00:54:46 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Peter Haight Cc: Nick Hibma , Subject: Re: Reading from the USB ugen device. In-Reply-To: <200204151747.g3FHlPRg037046@wartch.sapros.com> Message-ID: <20020417003939.B8131-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 15 Apr 2002, Peter Haight wrote: > >> From what you told me and a brief look at the USB spec, I'm guessing it > >> isn't a coincidence that it is failing on that read where I'm expecting 64 > >> bytes (the max size of a USB packet payload). I'm guessing that in short > >> read mode, the driver gets a full length packet and is expecting another > >> data packet but it never comes because that's the end of the data, so it > >> doesn't return from the read until it gets a timeout. > > > >No. If you read 64 byes in 64 bytes with short_XFER switched on you will > >be reading 64 bytes and then 0 bytes. > > Ok. But why does this happen: > > read(3, 0x8091800, 1024) > read -1 bytes > > At that same point in the protocol if I do: > read(3, 0x8091800, 64) > read 64 bytes > > I would expect: > read(3, 0x8091800, 1024) > read 64 bytes This might be caused by longstanding brokenness in sys_generic.c. E.g., in dofileread(): cnt = nbyte; if ((error = fo_read(fp, &auio, fp->f_cred, flags, td))) { if (auio.uio_resid != cnt && (error == ERESTART || ^^^^^^^^^^^^^^^^^^^^ error == EINTR || error == EWOULDBLOCK)) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ error = 0; } cnt -= auio.uio_resid; The underlined code arranges for the correct i/o count for non-null i/o to actually be returned to the application if the next lowest level of read() returned ERESTART, EINTR or EWOULDBLOCK. All other cases are broken -- both POSIX and POLA specify that if any i/o was done, then read()/write() shall return a count of the amount done (usually but not necessarily a short count). Try removing this and all other similar "&&" clauses in sys_generic.c. There are surprisingly few files where this actually matters. For regular files on most filesystems, the filesystem unwinds the i/o, so the auio.uio_resid != cnt case is not even seen here. But i/o is normally unwindable for devices. Here the problem may be the more immediate one that usb returns EIO instead of EWOULDBLOCK when it can't proceed. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 16 11:34: 5 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mile.nevermind.kiev.ua (freebsddiary.org.ua [213.186.199.26]) by hub.freebsd.org (Postfix) with ESMTP id 5096137B419; Tue, 16 Apr 2002 11:33:57 -0700 (PDT) Received: from mile.nevermind.kiev.ua (never@localhost [127.0.0.1]) by mile.nevermind.kiev.ua (8.12.2/8.12.2) with ESMTP id g3GIXr8W010422; Tue, 16 Apr 2002 21:33:53 +0300 (EEST) (envelope-from never@mile.nevermind.kiev.ua) Received: (from never@localhost) by mile.nevermind.kiev.ua (8.12.2/8.12.2/Submit) id g3GIXrVq010421; Tue, 16 Apr 2002 21:33:53 +0300 (EEST) Date: Tue, 16 Apr 2002 21:33:53 +0300 From: Nevermind To: freebsd-stable@freebsd.org Cc: freebsd-hardware@freebsd.org Subject: i810 hangs without panic Message-ID: <20020416183352.GA10258@nevermind.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline User-Agent: Mutt/1.3.28i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, Sorry for crossposting, but I think that it may be both hardware related and software related. I have box, based on Intel i810 chipset running 4.4-RELEASE-p9. It has xl0 3Com card running 100BaseT/full-duplex connected to Cisco Catalyst. Has 2 IDE HDD running UDMA2 (because of non-ATA66 cables) on different IDE channels, FUJITSU 6Gb, IBM 20Gb. S3 Trio V64+ PCI adapter in PCI slot, onboard video is turned off. device apm0 is in disabled state (but it doesn't matter, it used to hang with apm0 enabled also). (I'm describing this manually because it hanged just after I wrote 'Hello', and machine is on colocation). It hangs unexpectedly from 1 to 4 times a day without having any suspicious entries in logs and don't panics. Maybe someone expected similar problems and knows right solution? P.S. I'm aware that it looks like "underground knocking", but I cannot provide more details for now... Thank you. -- NEVE-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 16 11:58:42 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from beck.quonix.net (beck.quonix.net [64.239.136.146]) by hub.freebsd.org (Postfix) with ESMTP id E731437B416 for ; Tue, 16 Apr 2002 11:58:29 -0700 (PDT) Received: from [192.168.1.100] (pa-steclge-u1-c6b-396.stcgpa.adelphia.net [24.54.121.140]) by beck.quonix.net (8.11.6/8.11.6) with ESMTP id g3GIkhg03195; Tue, 16 Apr 2002 11:46:43 -0700 (PDT) (envelope-from john@essenz.com) User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 Date: Tue, 16 Apr 2002 14:55:00 -0400 Subject: Re: i810 hangs without panic From: John Von Essen To: Nevermind Cc: Message-ID: In-Reply-To: <20020416183352.GA10258@nevermind.kiev.ua> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have had 810 chipset boards mysteriously panic every month or so. It might be hardware related, I know Intel fixed some problems with 810 chipset and releases a whole new line of 815 chipset boards with identical specs. BIOS update would hurt. Has this problem always been around, or did it just start recently? -John on 4/16/02 2:33 PM, never@nevermind.kiev.ua wrote: > Hello, > > Sorry for crossposting, but I think that it may be both hardware related > and software related. > > I have box, based on Intel i810 chipset running 4.4-RELEASE-p9. > It has xl0 3Com card running 100BaseT/full-duplex connected to Cisco > Catalyst. Has 2 IDE HDD running UDMA2 (because of non-ATA66 cables) on > different IDE channels, FUJITSU 6Gb, IBM 20Gb. S3 Trio V64+ PCI > adapter in PCI slot, onboard video is turned off. > device apm0 is in disabled state (but it doesn't matter, it used to hang > with apm0 enabled also). > > (I'm describing this manually because it hanged just after I wrote > 'Hello', and machine is on colocation). > > It hangs unexpectedly from 1 to 4 times a day without having any > suspicious entries in logs and don't panics. > > Maybe someone expected similar problems and knows right solution? > > P.S. I'm aware that it looks like "underground knocking", but I cannot > provide more details for now... > > Thank you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 16 12: 2: 6 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from beck.quonix.net (beck.quonix.net [64.239.136.146]) by hub.freebsd.org (Postfix) with ESMTP id 4731A37B41A for ; Tue, 16 Apr 2002 12:01:55 -0700 (PDT) Received: from [192.168.1.100] (pa-steclge-u1-c6b-396.stcgpa.adelphia.net [24.54.121.140]) by beck.quonix.net (8.11.6/8.11.6) with ESMTP id g3GIoMg03223; Tue, 16 Apr 2002 11:50:22 -0700 (PDT) (envelope-from john@essenz.com) User-Agent: Microsoft-Outlook-Express-Macintosh-Edition/5.02.2022 Date: Tue, 16 Apr 2002 14:58:39 -0400 Subject: Re: i810 hangs without panic From: John Von Essen To: John Von Essen , Nevermind Cc: Message-ID: In-Reply-To: Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Sorry, Thats... BIOS update WOULDN'T hurt. on 4/16/02 2:55 PM, john@essenz.com wrote: > I have had 810 chipset boards mysteriously panic every month or so. It might > be hardware related, I know Intel fixed some problems with 810 chipset and > releases a whole new line of 815 chipset boards with identical specs. > > BIOS update would hurt. > > Has this problem always been around, or did it just start recently? > > -John > > > > on 4/16/02 2:33 PM, never@nevermind.kiev.ua wrote: > >> Hello, >> >> Sorry for crossposting, but I think that it may be both hardware related >> and software related. >> >> I have box, based on Intel i810 chipset running 4.4-RELEASE-p9. >> It has xl0 3Com card running 100BaseT/full-duplex connected to Cisco >> Catalyst. Has 2 IDE HDD running UDMA2 (because of non-ATA66 cables) on >> different IDE channels, FUJITSU 6Gb, IBM 20Gb. S3 Trio V64+ PCI >> adapter in PCI slot, onboard video is turned off. >> device apm0 is in disabled state (but it doesn't matter, it used to hang >> with apm0 enabled also). >> >> (I'm describing this manually because it hanged just after I wrote >> 'Hello', and machine is on colocation). >> >> It hangs unexpectedly from 1 to 4 times a day without having any >> suspicious entries in logs and don't panics. >> >> Maybe someone expected similar problems and knows right solution? >> >> P.S. I'm aware that it looks like "underground knocking", but I cannot >> provide more details for now... >> >> Thank you. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 16 12: 5:26 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mile.nevermind.kiev.ua (freebsddiary.org.ua [213.186.199.26]) by hub.freebsd.org (Postfix) with ESMTP id E34BB37B404 for ; Tue, 16 Apr 2002 12:05:20 -0700 (PDT) Received: from mile.nevermind.kiev.ua (never@localhost [127.0.0.1]) by mile.nevermind.kiev.ua (8.12.2/8.12.2) with ESMTP id g3GJ4t8W010767; Tue, 16 Apr 2002 22:04:55 +0300 (EEST) (envelope-from never@mile.nevermind.kiev.ua) Received: (from never@localhost) by mile.nevermind.kiev.ua (8.12.2/8.12.2/Submit) id g3GJ4se3010766; Tue, 16 Apr 2002 22:04:54 +0300 (EEST) Date: Tue, 16 Apr 2002 22:04:54 +0300 From: Nevermind To: John Von Essen Cc: freebsd-hardware@freebsd.org Subject: Re: i810 hangs without panic Message-ID: <20020416190454.GA10685@nevermind.kiev.ua> References: <20020416183352.GA10258@nevermind.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, John Von Essen! On Tue, Apr 16, 2002 at 02:55:00PM -0400, you wrote: > I have had 810 chipset boards mysteriously panic every month or so. It might It doesn't panic, and does this 1-4 times a day :( > be hardware related, I know Intel fixed some problems with 810 chipset and > releases a whole new line of 815 chipset boards with identical specs. > > BIOS update would hurt. > > Has this problem always been around, or did it just start recently? I've just got this motherboard and problem exists from the beginning of server running. > > Sorry for crossposting, but I think that it may be both hardware related > > and software related. > > > > I have box, based on Intel i810 chipset running 4.4-RELEASE-p9. > > It has xl0 3Com card running 100BaseT/full-duplex connected to Cisco > > Catalyst. Has 2 IDE HDD running UDMA2 (because of non-ATA66 cables) on > > different IDE channels, FUJITSU 6Gb, IBM 20Gb. S3 Trio V64+ PCI > > adapter in PCI slot, onboard video is turned off. > > device apm0 is in disabled state (but it doesn't matter, it used to hang > > with apm0 enabled also). > > > > (I'm describing this manually because it hanged just after I wrote > > 'Hello', and machine is on colocation). > > > > It hangs unexpectedly from 1 to 4 times a day without having any > > suspicious entries in logs and don't panics. > > > > Maybe someone expected similar problems and knows right solution? > > > > P.S. I'm aware that it looks like "underground knocking", but I cannot > > provide more details for now... > > > > Thank you. -- NEVE-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 16 12:16: 8 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mile.nevermind.kiev.ua (freebsddiary.org.ua [213.186.199.26]) by hub.freebsd.org (Postfix) with ESMTP id 2605837B419 for ; Tue, 16 Apr 2002 12:16:04 -0700 (PDT) Received: from mile.nevermind.kiev.ua (never@localhost [127.0.0.1]) by mile.nevermind.kiev.ua (8.12.2/8.12.2) with ESMTP id g3GJFq8W010909; Tue, 16 Apr 2002 22:15:52 +0300 (EEST) (envelope-from never@mile.nevermind.kiev.ua) Received: (from never@localhost) by mile.nevermind.kiev.ua (8.12.2/8.12.2/Submit) id g3GJFoIX010908; Tue, 16 Apr 2002 22:15:50 +0300 (EEST) Date: Tue, 16 Apr 2002 22:15:50 +0300 From: Nevermind To: John Von Essen Cc: freebsd-hardware@freebsd.org Subject: Re: i810 hangs without panic Message-ID: <20020416191550.GA10814@nevermind.kiev.ua> References: <20020416183352.GA10258@nevermind.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, John Von Essen! On Tue, Apr 16, 2002 at 02:55:00PM -0400, you wrote: > I have had 810 chipset boards mysteriously panic every month or so. It might > be hardware related, I know Intel fixed some problems with 810 chipset and > releases a whole new line of 815 chipset boards with identical specs. BTW, I've just found info about i810 on Intel site, it is about Linux and video, but it could make a sense: http://www.intel.com/support/graphics/intel810/Release_Notes_1.htm # Specify an amount of RAM. For the kernel to know how much RAM you # have available for use you will need to supply a boot parameter to # LILO, either at the boot prompt or in the configuration file. At the # LILO prompt, enter the name of the kernel you want (Usually 'linux' # unless you changed it) followed by mem=##M. The ## is the amount of # memory you have in megabytes. REMEMBER to subtract 1 MB for the part # taken by the graphics chip; otherwise your kernel will die during # boot-up. If it still dies, subtract another 1MB; this could be taken # by vendor specific BIOS needs. If your distribution has a graphical # boot screen, boot parameters may not be possible. You may still be # able to edit the lilo.conf as is detailed below. LILO: linux mem=63M But I've already said that "Init video first" BIOS setting it set to PCI, but cannot tell if onboard video is disabled completely or not by this setting. -- NEVE-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 16 13: 8:41 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from workhorse.imach.com (barbwire.iMach.com [206.127.77.82]) by hub.freebsd.org (Postfix) with ESMTP id 633FA37B404 for ; Tue, 16 Apr 2002 13:08:38 -0700 (PDT) Received: from localhost (forrestc@localhost) by workhorse.imach.com (8.11.6/8.11.6) with ESMTP id g3GE3xF45977; Tue, 16 Apr 2002 14:04:00 GMT (envelope-from forrestc@imach.com) Date: Tue, 16 Apr 2002 14:03:59 +0000 (GMT) From: "Forrest W. Christian" To: John Von Essen Cc: Nevermind , Subject: Re: i810 hangs without panic In-Reply-To: Message-ID: <20020416140156.V45945-100000@workhorse.imach.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org on 4/16/02 2:33 PM, never@nevermind.kiev.ua wrote: > It hangs unexpectedly from 1 to 4 times a day without having any > suspicious entries in logs and don't panics. Does it recover after the hang or do you have to reboot it? If so, could you post a copy of " netstat -m " ran after the next hang? - Forrest W. Christian (forrestc@imach.com) AC7DE ---------------------------------------------------------------------- The Innovation Machine Ltd. P.O. Box 5749 http://www.imach.com/ Helena, MT 59604 Home of PacketFlux Technogies and BackupDNS.com (406)-442-6648 ---------------------------------------------------------------------- Protect your personal freedoms - visit http://www.lp.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 16 14: 4:21 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from alcanet.com.au (mail2.alcanet.com.au [203.62.196.17]) by hub.freebsd.org (Postfix) with ESMTP id AE5D537B404 for ; Tue, 16 Apr 2002 14:04:16 -0700 (PDT) Received: from mfg1.cim.alcatel.com.au (localhost.localdomain [127.0.0.1]) by alcanet.com.au (8.12.1/8.12.1/Alcanet1.2) with ESMTP id g3GL4DjX026797 for ; Wed, 17 Apr 2002 07:04:13 +1000 Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01KGNTM17Z5S9S6TXF@cim.alcatel.com.au> for freebsd-hardware@freebsd.org; Wed, 17 Apr 2002 07:04:10 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.6/8.11.6) id g3GL4Ac44459 for freebsd-hardware@freebsd.org; Wed, 17 Apr 2002 07:04:10 +1000 Content-return: prohibited Date: Wed, 17 Apr 2002 07:04:10 +1000 From: Peter Jeremy Subject: Buslogic BT-445S problems To: freebsd-hardware@freebsd.org Mail-Followup-To: freebsd-hardware@freebsd.org Message-id: <20020417070409.E69202@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I recently acquired a BT-445S (VLB SCSI). Whilst it probes OK itself, the SCSI bus probe locks up: It reports "Using Strict Round Robin Mailbox Mode", sits for a long time and starts reporting CCB timeouts. I've tried both with and without anything attached to the SCSI bus, in two different boxes running both -CURRENT and 4.5-RELEASE. Does anyone have any suggestions, or is the card stuffed? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 16 17: 0: 9 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.tcworks.net (mail.tcworks.net [216.61.218.4]) by hub.freebsd.org (Postfix) with ESMTP id F090C37B400 for ; Tue, 16 Apr 2002 17:00:01 -0700 (PDT) Received: from tcworks.net (staind.tcworks.net [216.61.218.6]) by mail.tcworks.net (8.10.2/8.10.2) with ESMTP id g3GNtbs22722; Tue, 16 Apr 2002 18:55:37 -0500 (CDT) Message-ID: <3CBCBAC5.734666AB@tcworks.net> Date: Tue, 16 Apr 2002 18:59:01 -0500 From: Chris Cook X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: Christopher Schulte , freebsd-hardware@freebsd.org Subject: Re: subscribe References: <5.1.0.14.0.20020416185016.0439b380@pop3s.schulte.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Christopher Schulte wrote: > > Might want to send that to majordomo@freebsd.org. > yes, I'm quite the retard at times... -- Chris o----< ccook@tcworks.net >------------------------------------o |Chris Cook - Admin |TCWORKS.NET - http://www.tcworks.net | |The Computer Works ISP |FreeBSD - http://www.freebsd.org | o-------------------------------------------------------------o To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 16 18: 1:26 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by hub.freebsd.org (Postfix) with ESMTP id 6F8DE37B400 for ; Tue, 16 Apr 2002 18:01:24 -0700 (PDT) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.12.2/8.12.2) with ESMTP id g3H11D2A001540; Tue, 16 Apr 2002 21:01:14 -0400 (EDT) (envelope-from winter@jurai.net) Date: Tue, 16 Apr 2002 21:01:13 -0400 (EDT) From: "Matthew N. Dodd" To: Peter Jeremy Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Buslogic BT-445S problems In-Reply-To: <20020417070409.E69202@gsmx07.alcatel.com.au> Message-ID: <20020416210055.F42854-100000@sasami.jurai.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 17 Apr 2002, Peter Jeremy wrote: > I recently acquired a BT-445S (VLB SCSI). Whilst it probes OK itself, > the SCSI bus probe locks up: It reports "Using Strict Round Robin > Mailbox Mode", sits for a long time and starts reporting CCB timeouts. > I've tried both with and without anything attached to the SCSI bus, > in two different boxes running both -CURRENT and 4.5-RELEASE. > > Does anyone have any suggestions, or is the card stuffed? What does the card probe look like? -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 16 18:37:34 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from smtp-server6.tampabay.rr.com (smtp-server6.tampabay.rr.com [65.32.1.43]) by hub.freebsd.org (Postfix) with ESMTP id 9EACF37B404 for ; Tue, 16 Apr 2002 18:37:31 -0700 (PDT) Received: from dual866 (6534115hfc67.swfla.rr.com [65.34.115.67] (may be forged)) by smtp-server6.tampabay.rr.com (8.12.2/8.11.2) with ESMTP id g3H1bU1F022204 for ; Tue, 16 Apr 2002 21:37:30 -0400 (EDT) Date: Tue, 16 Apr 2002 21:39:14 -0400 From: Jon X-Mailer: The Bat! (v1.60c) Educational X-Priority: 3 (Normal) Message-ID: <891709640.20020416213914@email.com> To: HARDWARE@freebsd.org Subject: pcmcia 3com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org can a 3com pcmcia nic be put in promiscuous mode? if so what models? -- Jon mailto:juostaus@yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 16 22:23:56 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from lariat.org (lariat.org [12.23.109.2]) by hub.freebsd.org (Postfix) with ESMTP id EE91A37B41A for ; Tue, 16 Apr 2002 22:23:52 -0700 (PDT) Received: from mustang.lariat.org (IDENT:ppp0.lariat.org@lariat.org [12.23.109.2]) by lariat.org (8.9.3/8.9.3) with ESMTP id XAA26646 for ; Tue, 16 Apr 2002 23:23:41 -0600 (MDT) X-message-flag: Warning! Use of Microsoft Outlook may make your system susceptible to Internet worms. Message-Id: <4.3.2.7.2.20020416231827.02168710@nospam.lariat.org> X-Sender: brett@nospam.lariat.org X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Tue, 16 Apr 2002 23:21:07 -0600 To: hardware@freebsd.org From: Brett Glass Subject: Intel motherboard "Ethernet console" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm working with an Intel motherboard whose BIOS setup screen says that it has an "Ethernet console" -- in other words, you can supposedly use another system as the console if you attach an Ethernet cable and speak the proper protocol. But what protocol is it? The BIOS almost certainly doesn't have a full TCP/IP implementation, so it can't be telnet. Is it LAT? Something unique? Any ideas welcomed. --Brett Glass To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 16 23:34:31 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from snowflake.apdata.com.au (cerberus.apdata.com.au [202.14.95.17]) by hub.freebsd.org (Postfix) with ESMTP id 6019A37B419 for ; Tue, 16 Apr 2002 23:34:25 -0700 (PDT) Received: from localhost (localhost.apdata.com.au [127.0.0.1]) by snowflake.apdata.com.au (Postfix) with ESMTP id 821F25272B for ; Wed, 17 Apr 2002 16:04:23 +0930 (CST) Received: from holly.apdata.com.au (pirahna.apdata.com.au [192.168.255.14]) by snowflake.apdata.com.au (Postfix) with ESMTP id 2EB815272A for ; Wed, 17 Apr 2002 16:04:21 +0930 (CST) Message-ID: <3CBD176C.1030302@holly.apdata.com.au> Date: Wed, 17 Apr 2002 16:04:20 +0930 From: Bronte Averay User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.4) Gecko/20011126 Netscape6/6.2.1 X-Accept-Language: en-us MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: atacontrol problem with 4.5 Stable Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi everyone, Greetings from Adelaide, South Australia. This is my first posting so if I've left out any valuable information, firstly my apologies and secondly please let me know what else is required. I recently cvsupped a server to 4.5 Stable, and up until that time the unit was successfully running a Seagate STT8000A/5.51 ide tape backup unit. Following the version upgrade the tape drive is no longer responsive and any attempts to query the device result in the process hanging. I have some output here from what I think to be relevant sections: Output from atacontrol list: su-2.05# atacontrol list ATA channel 0: Master: ad0 ATA/ATAPI rev 3 Slave: ast0 ATA/ATAPI rev 0 ATA channel 1: Master: ad2 ATA/ATAPI rev 5 Slave: no device present Relevent lines from most recent kernel rebuild (20020417): ast0: TAPE at ata0-slave PIO4 ast0: failure to execute ATAPI packet command If I run the following command the process hangs in the kernel and cannot be released or stopped, only a reboot will clear the process: mt -f /dev/ast0 status This is the relevant line from ps -ax, resulting from running the above command: 253 p0- DE 0:00.01 mt -f /dev/ast0 status Thanks for taking the time to read this, I hope someone can assist me. Best regards, Bronte Averay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Apr 16 23:50:59 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by hub.freebsd.org (Postfix) with ESMTP id 8D31E37B417 for ; Tue, 16 Apr 2002 23:50:56 -0700 (PDT) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.12.2/8.12.2) with ESMTP id g3H6ot2A005169; Wed, 17 Apr 2002 02:50:56 -0400 (EDT) (envelope-from winter@jurai.net) Date: Wed, 17 Apr 2002 02:50:55 -0400 (EDT) From: "Matthew N. Dodd" To: Brett Glass Cc: hardware@FreeBSD.ORG Subject: Re: Intel motherboard "Ethernet console" In-Reply-To: <4.3.2.7.2.20020416231827.02168710@nospam.lariat.org> Message-ID: <20020417025022.Y42854-100000@sasami.jurai.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 16 Apr 2002, Brett Glass wrote: > Is it LAT? Something unique? Any ideas welcomed. It wouldn't be LAT; if it was DEC flavored it would be MOP-RC. :) -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 17 3:17:27 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from alcanet.com.au (mail2.alcanet.com.au [203.62.196.17]) by hub.freebsd.org (Postfix) with ESMTP id 7548737B404 for ; Wed, 17 Apr 2002 03:17:21 -0700 (PDT) Received: from mfg1.cim.alcatel.com.au (localhost.localdomain [127.0.0.1]) by alcanet.com.au (8.12.1/8.12.1/Alcanet1.2) with ESMTP id g3HAHHQQ017310; Wed, 17 Apr 2002 20:17:18 +1000 Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37645) with ESMTP id <01KGOLBAMBK09S6RJE@cim.alcatel.com.au>; Wed, 17 Apr 2002 20:17:14 +1100 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.6/8.11.6) id g3HAHFN56065; Wed, 17 Apr 2002 20:17:15 +1000 Content-return: prohibited Date: Wed, 17 Apr 2002 20:17:14 +1000 From: Peter Jeremy Subject: Re: Buslogic BT-445S problems In-reply-to: <20020416210055.F42854-100000@sasami.jurai.net>; from winter@jurai.net on Tue, Apr 16, 2002 at 09:01:13PM -0400 To: "Matthew N. Dodd" Cc: freebsd-hardware@FreeBSD.ORG Mail-Followup-To: "Matthew N. Dodd" , freebsd-hardware@FreeBSD.ORG Message-id: <20020417201714.A56049@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <20020417070409.E69202@gsmx07.alcatel.com.au> <20020416210055.F42854-100000@sasami.jurai.net> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 2002-Apr-16 21:01:13 -0400, "Matthew N. Dodd" wrote: >On Wed, 17 Apr 2002, Peter Jeremy wrote: >> I recently acquired a BT-445S (VLB SCSI). Whilst it probes OK itself, >> the SCSI bus probe locks up: It reports "Using Strict Round Robin >> Mailbox Mode", sits for a long time and starts reporting CCB timeouts. >> I've tried both with and without anything attached to the SCSI bus, >> in two different boxes running both -CURRENT and 4.5-RELEASE. >> >> Does anyone have any suggestions, or is the card stuffed? > >What does the card probe look like? Following is hand-copied from booting a 4.5-RELEASE GENERIC kernel user-config'd to match the system. Unfortunately, I don't seem to be able to preserve the kernel message buffer across the reset. Other than the BT-445S, the system has a dual-channel IDE controller 2P+S and an NE2000-clone. The IRQ and IO ports aren't conflicting. adv0: not probed (disabled) bt0 at port 0x330-0x333 irq 11 drq -1 on isa0 bt0: BT-445S FW Rev. 3.36 Narrow SCSI Host Adapter, SCSI ID 7, 30CCBs bt0: Using Strict Round Robin Mailbox Mode aha0: not probed (disabled) ... Waiting 15 seconds for SCSI devices to settle bt0: Using Strict Round Robin Mailbox Mode [~1 min delay] (probe0:bt0:0:0:0): CCB 0xc086ab80 - timed out [~1 sec delay] (probe0:bt0:0:0:0): CCB 0xc086ab80 - timed out bt0: Using Strict Round Robin Mailbox Mode bt: ccb 0xc086aa00 - error 4 occurred. btstat = 22, sdstat = 0 bt: ccb 0xc086aa40 - error 4 occurred. btstat = 22, sdstat = 0 bt: ccb 0xc086aa80 - error 4 occurred. btstat = 22, sdstat = 0 bt: ccb 0xc086aac0 - error 4 occurred. btstat = 22, sdstat = 0 bt: ccb 0xc086ab00 - error 4 occurred. btstat = 22, sdstat = 0 bt: ccb 0xc086ab40 - error 4 occurred. btstat = 22, sdstat = 0 bt: ccb 0xc086ab80 - error 4 occurred. btstat = 22, sdstat = 0 bt0: No longer in timeout [and loop] I noticed that enabling the card BIOS makes it just lock up after the "card found at 0x330" message, but I'm not sure if this is just because it can't find any SCSI disks to boot. The internal terminators are installed, as well as an external active terminator, with no other devices. I've also tried with a couple of internal tape drives (which work OK an an AHA-1542) - in this case, the on-board terminator was removed and an active terminator inside the end tape drive used instead. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 17 5:47:42 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mile.nevermind.kiev.ua (freebsddiary.org.ua [213.186.199.26]) by hub.freebsd.org (Postfix) with ESMTP id E5A0A37B426 for ; Wed, 17 Apr 2002 05:47:21 -0700 (PDT) Received: from mile.nevermind.kiev.ua (never@localhost [127.0.0.1]) by mile.nevermind.kiev.ua (8.12.2/8.12.2) with ESMTP id g3HCko8W018559; Wed, 17 Apr 2002 15:46:51 +0300 (EEST) (envelope-from never@mile.nevermind.kiev.ua) Received: (from never@localhost) by mile.nevermind.kiev.ua (8.12.2/8.12.2/Submit) id g3HCkfgl018558; Wed, 17 Apr 2002 15:46:41 +0300 (EEST) Date: Wed, 17 Apr 2002 15:46:41 +0300 From: Nevermind To: "Forrest W. Christian" Cc: John Von Essen , freebsd-hardware@FreeBSD.ORG Subject: Re: i810 hangs without panic Message-ID: <20020417124641.GA11709@nevermind.kiev.ua> References: <20020416140156.V45945-100000@workhorse.imach.com> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20020416140156.V45945-100000@workhorse.imach.com> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, Forrest W. Christian! On Tue, Apr 16, 2002 at 02:03:59PM +0000, you wrote: > > It hangs unexpectedly from 1 to 4 times a day without having any > > suspicious entries in logs and don't panics. > > Does it recover after the hang or do you have to reboot it? It just hangs, stops responding anything. > > If so, could you post a copy of " netstat -m " ran after the next hang? I cannot, machine is on remote colocation. maxusers is 1024 in kernel, if it is matter. -- NEVE-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 17 5:59:21 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from workhorse.imach.com (barbwire.iMach.com [206.127.77.82]) by hub.freebsd.org (Postfix) with ESMTP id 3686837B404 for ; Wed, 17 Apr 2002 05:59:18 -0700 (PDT) Received: from localhost (forrestc@localhost) by workhorse.imach.com (8.11.6/8.11.6) with ESMTP id g3H6sxx49647; Wed, 17 Apr 2002 06:55:00 GMT (envelope-from forrestc@imach.com) Date: Wed, 17 Apr 2002 06:54:59 +0000 (GMT) From: "Forrest W. Christian" To: Nevermind Cc: John Von Essen , Subject: Re: i810 hangs without panic In-Reply-To: <20020417124641.GA11709@nevermind.kiev.ua> Message-ID: <20020417065050.A48029-100000@workhorse.imach.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 17 Apr 2002, Nevermind wrote: > > Does it recover after the hang or do you have to reboot it? > It just hangs, stops responding anything. > > > > If so, could you post a copy of " netstat -m " ran after the next hang? > I cannot, machine is on remote colocation. > maxusers is 1024 in kernel, if it is matter. The reason I was asking is that the symptom of running out of mbuf clusters is typically a hang which recovers after a while (after the mbufs time out/clear out). Increasing mbufs usually fixes it. And it's pretty obvious when you look at netstat -m after the hang. What is the output of netstat -m right now? - Forrest W. Christian (forrestc@imach.com) AC7DE ---------------------------------------------------------------------- The Innovation Machine Ltd. P.O. Box 5749 http://www.imach.com/ Helena, MT 59604 Home of PacketFlux Technogies and BackupDNS.com (406)-442-6648 ---------------------------------------------------------------------- Protect your personal freedoms - visit http://www.lp.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 17 6:20: 5 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from van-laarhoven.org (ap-z-5ab8.adsl.wanadoo.nl [212.129.218.184]) by hub.freebsd.org (Postfix) with SMTP id A179A37B404 for ; Wed, 17 Apr 2002 06:20:01 -0700 (PDT) Received: (qmail 4812 invoked from network); 17 Apr 2002 13:20:00 -0000 Received: from dhcp0-120.van-laarhoven.org (HELO cecile) (10.66.0.120) by uitsmijter.van-laarhoven.org with SMTP; 17 Apr 2002 13:20:00 -0000 Message-ID: <004501c1e612$ede6a4c0$7800420a@vanlaarhoven.org> From: "Nick Hibma" To: "Bruce Evans" , "Peter Haight" Cc: References: <20020417003939.B8131-100000@gamplex.bde.org> Subject: Re: Reading from the USB ugen device. Date: Wed, 17 Apr 2002 15:22:31 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4807.1700 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Here the problem may be the more immediate one that usb returns EIO > instead of EWOULDBLOCK when it can't proceed. EIO is only returned in case of error. I was mistaken. EWOULDBLOCK can never be returned because the ugen driver can't know whether or no the transfer is going to block. There is no such thing as a poll for data on the USB bus. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 17 7:30:29 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from lariat.org (lariat.org [12.23.109.2]) by hub.freebsd.org (Postfix) with ESMTP id 6F15D37B405 for ; Wed, 17 Apr 2002 07:30:22 -0700 (PDT) Received: from mustang.lariat.org (IDENT:ppp0.lariat.org@lariat.org [12.23.109.2]) by lariat.org (8.9.3/8.9.3) with ESMTP id IAA01074; Wed, 17 Apr 2002 08:30:02 -0600 (MDT) X-message-flag: Warning! Use of Microsoft Outlook may make your system susceptible to Internet worms. Message-Id: <4.3.2.7.2.20020417082658.021c4690@nospam.lariat.org> X-Sender: brett@nospam.lariat.org X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Wed, 17 Apr 2002 08:29:55 -0600 To: "Matthew N. Dodd" From: Brett Glass Subject: Re: Intel motherboard "Ethernet console" Cc: hardware@FreeBSD.ORG In-Reply-To: <20020417025022.Y42854-100000@sasami.jurai.net> References: <4.3.2.7.2.20020416231827.02168710@nospam.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 12:50 AM 4/17/2002, Matthew N. Dodd wrote: >It wouldn't be LAT; if it was DEC flavored it would be MOP-RC. :) Well, whatever it is, it's likely to be right on the MAC layer. And since there doesn't seem to be a place to tell the motherboard the MAC address, it must either discover the console's MAC address or use (shudder!) broadcast packets for everything. --Brett Glass To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 17 9:16:56 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by hub.freebsd.org (Postfix) with ESMTP id 0037037B400 for ; Wed, 17 Apr 2002 09:16:53 -0700 (PDT) Received: from sasami.jurai.net (sasami.jurai.net [66.92.160.223]) by sasami.jurai.net (8.12.2/8.12.2) with ESMTP id g3HGGi2A011863; Wed, 17 Apr 2002 12:16:44 -0400 (EDT) (envelope-from winter@jurai.net) Date: Wed, 17 Apr 2002 12:16:44 -0400 (EDT) From: "Matthew N. Dodd" To: Peter Jeremy Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Buslogic BT-445S problems In-Reply-To: <20020417201714.A56049@gsmx07.alcatel.com.au> Message-ID: <20020417121328.Q42854-100000@sasami.jurai.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 17 Apr 2002, Peter Jeremy wrote: > bt0 at port 0x330-0x333 irq 11 drq -1 on isa0 ^^^^^^ Is this for real or just a transcription error? > bt0: BT-445S FW Rev. 3.36 Narrow SCSI Host Adapter, SCSI ID 7, 30CCBs > bt0: Using Strict Round Robin Mailbox Mode Hummm... The source mentions that firmware revision 3.37 is good and all others need a workaround; it could be the workaround code isn't doing the right thing. > I noticed that enabling the card BIOS makes it just lock up after > the "card found at 0x330" message, but I'm not sure if this is > just because it can't find any SCSI disks to boot. If the BIOS won't come up that sounds like something outside of FreeBSD drvier issues. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | For Great Justice! | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 17 14:22:35 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from alcanet.com.au (mail2.alcanet.com.au [203.62.196.17]) by hub.freebsd.org (Postfix) with ESMTP id 9CA6D37B41A for ; Wed, 17 Apr 2002 14:22:28 -0700 (PDT) Received: from mfg1.cim.alcatel.com.au (localhost.localdomain [127.0.0.1]) by alcanet.com.au (8.12.1/8.12.1/Alcanet1.2) with ESMTP id g3HLMPVP014797; Thu, 18 Apr 2002 07:22:25 +1000 Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37640) with ESMTP id <01KGP8JYX35SVLWWRX@cim.alcatel.com.au>; Thu, 18 Apr 2002 07:22:24 +1000 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.6/8.11.6) id g3HLMNK66340; Thu, 18 Apr 2002 07:22:23 +1000 Content-return: prohibited Date: Thu, 18 Apr 2002 07:22:23 +1000 From: Peter Jeremy Subject: Re: Buslogic BT-445S problems In-reply-to: <20020417121328.Q42854-100000@sasami.jurai.net>; from winter@jurai.net on Wed, Apr 17, 2002 at 12:16:44PM -0400 To: "Matthew N. Dodd" Cc: freebsd-hardware@FreeBSD.ORG Mail-Followup-To: "Matthew N. Dodd" , freebsd-hardware@FreeBSD.ORG Message-id: <20020418072222.N69202@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <20020417201714.A56049@gsmx07.alcatel.com.au> <20020417121328.Q42854-100000@sasami.jurai.net> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 2002-Apr-17 12:16:44 -0400, "Matthew N. Dodd" wrote: >On Wed, 17 Apr 2002, Peter Jeremy wrote: >> bt0 at port 0x330-0x333 irq 11 drq -1 on isa0 > ^^^^^^ >Is this for real or just a transcription error? That's real. /sys/dev/buslogic/bt.c:bt_port_probe() contains: ... if (bt->model[0] == '5') { /* DMA settings only make sense for ISA cards */ ... } else { /* VL/EISA/PCI DMA */ info->drq = -1; } so I assume the probe message is correct and reasonable. > >> bt0: BT-445S FW Rev. 3.36 Narrow SCSI Host Adapter, SCSI ID 7, 30CCBs >> bt0: Using Strict Round Robin Mailbox Mode > >Hummm... The source mentions that firmware revision 3.37 is good and all >others need a workaround; it could be the workaround code isn't doing the >right thing. The only comment I can find is in bt_isa.c:bt_isa_attach() - which refers to a hardware bug in older h/w revisions (I'm fairly certain I have a RevD card - which is affected). F/W 3.37 only runs on RevE cards and is being used to guess the hardware revision. This bug only affects cards where the BIOS is enabled - and I don't have the BIOS enabled so it shouldn't affect me. >> I noticed that enabling the card BIOS makes it just lock up after >> the "card found at 0x330" message, but I'm not sure if this is >> just because it can't find any SCSI disks to boot. > >If the BIOS won't come up that sounds like something outside of FreeBSD >drvier issues. I tend to agree, but I'm not sure how the card is expected to behave in this situation. The manual only discusses booting off SCSI disks attached to the card - which I don't have. There's no indication of what would happen if the BIOS is enabled when there aren't any bootable disks. I was hoping someone else might still have a system with a BT-445 and be able to confirm the normal behaviour. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Apr 17 23: 4:54 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id C2F7137B41D for ; Wed, 17 Apr 2002 23:04:51 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id QAA14419; Thu, 18 Apr 2002 16:03:55 +1000 Date: Thu, 18 Apr 2002 16:04:31 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Nick Hibma Cc: Peter Haight , Subject: Re: Reading from the USB ugen device. In-Reply-To: <004501c1e612$ede6a4c0$7800420a@vanlaarhoven.org> Message-ID: <20020418160144.T13784-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 17 Apr 2002, Nick Hibma wrote: > > Here the problem may be the more immediate one that usb returns EIO > > instead of EWOULDBLOCK when it can't proceed. > > EIO is only returned in case of error. I was mistaken. EWOULDBLOCK can never > be returned because the ugen driver can't know whether or no the transfer is > going to block. There is no such thing as a poll for data on the USB bus. It seems to sometimes return ETIMEDOUT, which causes the same problem. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 18 4:37: 8 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mile.nevermind.kiev.ua (freebsddiary.org.ua [213.186.199.26]) by hub.freebsd.org (Postfix) with ESMTP id 4740937B400 for ; Thu, 18 Apr 2002 04:37:03 -0700 (PDT) Received: from mile.nevermind.kiev.ua (never@localhost [127.0.0.1]) by mile.nevermind.kiev.ua (8.12.2/8.12.2) with ESMTP id g3IBat8W028199 for ; Thu, 18 Apr 2002 14:36:56 +0300 (EEST) (envelope-from never@mile.nevermind.kiev.ua) Received: (from never@localhost) by mile.nevermind.kiev.ua (8.12.2/8.12.2/Submit) id g3IBatUD028198 for freebsd-hardware@FreeBSD.ORG; Thu, 18 Apr 2002 14:36:55 +0300 (EEST) Date: Thu, 18 Apr 2002 14:36:55 +0300 From: Nevermind To: freebsd-hardware@FreeBSD.ORG Subject: Re: i810 hangs without panic Message-ID: <20020418113655.GA28155@nevermind.kiev.ua> References: <20020416183352.GA10258@nevermind.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Disposition: inline In-Reply-To: <20020416183352.GA10258@nevermind.kiev.ua> User-Agent: Mutt/1.3.28i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, Nevermind! On Tue, Apr 16, 2002 at 09:33:53PM +0300, you wrote: > I have box, based on Intel i810 chipset running 4.4-RELEASE-p9. [snip] > It hangs unexpectedly from 1 to 4 times a day without having any > suspicious entries in logs and don't panics. Thank you all for replying. I've managed to get another motherboard on i815EP chipset. It runs perfectly. i810 is the worst MB I've ever seen. -- NEVE-RIPE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 18 15:12:56 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from fremen.dhs.org (pa48.bialystok.sdi.tpnet.pl [213.25.59.48]) by hub.freebsd.org (Postfix) with ESMTP id DAAB137B400 for ; Thu, 18 Apr 2002 15:12:46 -0700 (PDT) Received: by fremen.dhs.org (Postfix, from userid 1000) id 39FD3A762; Fri, 19 Apr 2002 00:14:03 +0200 (CEST) Date: Fri, 19 Apr 2002 00:14:03 +0200 From: Jakub Filonik To: hardware@freebsd.org Subject: burncd / ATAPI CD-R Message-ID: <20020419001403.A530@fremen.dhs.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, I have ATAPI CD-R, MITSUMI 2801TE. I tried to use burncd program, but when I want to run it, it has a problem with 'fixate': # burncd -t -f /dev/acd1a -s 2 -v data FILE fixate adding type 0x08 file FILE size 9 KB 5 blocks (0 padded) next writeable LBA 0 addr = 0 size = 9361 blocks = 5 writing from file FILE size 9 KB written this track 10 KB (111%) total 10 KB fixating CD, please wait.. burncd: ioctl(CDRIOCFIXATE): Input/output error -- [ICQ-UIN: 35638062] [Gadu-Gadu: 533719] [cellular phone: +48603199704] publiczny klucz PGP dostepny na http://black.pl/~sirat/sirat-pub.pgp admin: 213.25.59.48 [fremen.g0ds.org] "A hunchback does not see his own hunch. The hunch may be seen with the aid of mirrors but mirrors may show the whole being." -- Frank Herbert To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 18 16:47:39 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.spot.org (blackhole.spot.org [65.120.117.140]) by hub.freebsd.org (Postfix) with SMTP id 4630337B405 for ; Thu, 18 Apr 2002 16:47:29 -0700 (PDT) Received: (qmail 72407 invoked from network); 18 Apr 2002 23:47:23 -0000 Received: from unknown (HELO gecko) (202.154.25.69) by blackhole.spot.org with SMTP; 18 Apr 2002 23:47:23 -0000 Message-ID: <017b01c1e76d$35f191c0$1700a8c0@gecko> From: "stupid" To: Cc: Subject: Date: Fri, 19 Apr 2002 06:41:12 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org listers, I have a old puter DIGITAL CELEBRIS XL5133 / p133dual ( not the alpha upgrade ) which is being used for a gateway machine, I have yet to revert back to using Freebsd due to a minor SCSI CD problem, I have tried to Install FreeBSD4.5rel on this to no avail. Due to the fact that FreeBSD installer would not detect my CDROM or would often try to ( resetting all SCSI devices ), Yes i could install FreeBSD using another puter and another CDROM. ( in case there are some wise crack monkeys around ) however I only have this problem with FreeBSD. OpenBSD, ( hold the flame ) and Linux distros such as Redhat and Slackware give me no such problems :) if anyone could help me with my problem siop0 at pci0 dev 1 function 0 "Symbios Logic 53c810" rev 0x02: irq 11, siop0: scsi bus reset scsibus0 at siop0: 8 targets cd0 at scsibus0 targ 6 lun 0: SCSI2 5/cdrom removable siop0: target 6 now using 8 bit async xfers thank you listed below is my dmesg from :) my current OS running on the box PS. really need to get SMP support on this box $ dmesg OpenBSD 3.0-stable (ELENCHUS) #5: Wed Apr 17 06:18:17 GMT 2002 root@stupid:/usr/src/sys/arch/i386/compile/ELENCHUS cpu0: F00F bug workaround installed cpu0: Intel Pentium (P54C) ("GenuineIntel" 586-class) 114 MHz cpu0: FPU,V86,DE,PSE,TSC,MSR,MCE,CX8,APIC real mem = 83472384 (81516K) avail mem = 71962624 (70276K) using 1044 buffers containing 4276224 bytes (4176K) of memory mainbus0 (root) bios0 at mainbus0: AT/286+(07) BIOS, date 11/30/95, BIOS32 rev. 0 @ 0xfbdcf apm0 at bios0: Power Management spec V1.1 apm0: AC unknown, battery charge unknown, estimated 0:00 hours pcibios0 at bios0: rev. 2.1 @ 0xfbc90/0x1270 pcibios0: PCI BIOS has 4 Interrupt Routing table entries pcibios0: PCI Exclusive IRQs: 9 10 11 15 pcibios0: no compatible PCI ICU found pcibios0: Warning, unable to fix up PCI interrupt routing pcibios0: PCI bus #0 is the last bus bios0: ROM list: 0xc0000/0x8000 0xc8000/0x4000 pci0 at mainbus0 bus 0: configuration mode 2 (bios) pchb0 at pci0 dev 0 function 0 "Intel 82434LX/NX PCI/Cache/DRAM" rev 0x11 siop0 at pci0 dev 1 function 0 "Symbios Logic 53c810" rev 0x02: irq 11, siop0: scsi bus reset scsibus0 at siop0: 8 targets cd0 at scsibus0 targ 6 lun 0: SCSI2 5/cdrom removable siop0: target 6 now using 8 bit async xfers pcib0 at pci0 dev 2 function 0 "Intel 82378IB PCI-ISA" rev 0x88 vga1 at pci0 dev 6 function 0 "Matrox MGA Millenium 2064W (Storm)" rev 0x01 wsdisplay0 at vga1: console (80x25, vt100 emulation) wsdisplay0: screen 1-5 added (80x25, vt100 emulation) xl0 at pci0 dev 7 function 0 "3Com 3c905 100Base-TX" rev 0x00: irq 10 address 00:a0:24:e0:48:36 nsphy0 at xl0 phy 24: DP83840 10/100 media interface, rev. 0 rl0 at pci0 dev 8 function 0 "Realtek 8139" rev 0x10: irq 15 address 00:c0:26:6f:51:ea rlphy0 at rl0 phy 0: RTL internal phy isa0 at pcib0 isadma0 at isa0 pckbc0 at isa0 port 0x60/5 pckbd0 at pckbc0 (kbd slot) pckbc0: using irq 1 for kbd slot wskbd0 at pckbd0: console keyboard, using wsdisplay0 wdc0 at isa0 port 0x1f0/8 irq 14 wd0 at wdc0 channel 0 drive 0: wd0: 16-sector PIO, LBA, 4110MB, 14848 cyl, 9 head, 63 sec, 8418816 sectors wd0(wdc0:0:0): using BIOS timings pcppi0 at isa0 port 0x61 midi0 at pcppi0: sysbeep0 at pcppi0 lpt0 at isa0 port 0x378/4 irq 7 npx0 at isa0 port 0xf0/16: using exception 16 pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo pccom1 at isa0 port 0x2f8/8 irq 3: ns16550a, 16 byte fifo fdc0 at isa0 port 0x3f0/6 irq 6 drq 2 fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec biomask 4840 netmask cc40 ttymask ccc2 pctr: 586-class performance counters and user-level cycle counter enabled dkcsum: wd0 matched BIOS disk 80 root on wd0a rootdev=0x0 rrootdev=0x300 rawdev=0x302 $ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Apr 18 17:52: 3 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from smtp.adnc.com (epsilon.adnc.com [206.251.252.16]) by hub.freebsd.org (Postfix) with ESMTP id C54B537B405 for ; Thu, 18 Apr 2002 17:52:00 -0700 (PDT) Received: from tech5 (gateway.adnc.com [206.251.251.2]) by smtp.adnc.com (Postfix) with SMTP id F28802935A for ; Thu, 18 Apr 2002 17:51:55 -0700 (PDT) Message-ID: <001b01c1b171$454f99f0$a0320a0a@tech5> From: "Jerome" To: Subject: test Date: Sat, 9 Feb 2002 05:54:19 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0018_01C1B12E.37063450" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0018_01C1B12E.37063450 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_000_0018_01C1B12E.37063450 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
------=_NextPart_000_0018_01C1B12E.37063450-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 19 9:22:59 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mailhost.bonet.ac (mailhost.bonet.ac [194.165.224.191]) by hub.freebsd.org (Postfix) with ESMTP id 5C3A237B405 for ; Fri, 19 Apr 2002 09:22:50 -0700 (PDT) Received: from mabe (as1-1-1.ela.g.bonet.se [212.181.21.3]) by mailhost.bonet.ac (8.8.8/8.8.8) with ESMTP id SAA01287 for ; Fri, 19 Apr 2002 18:22:49 +0200 (MET DST) From: "Magnus Benngard" To: Subject: Compaq ProLiant DL360 No disk found Date: Fri, 19 Apr 2002 18:22:43 +0200 Message-ID: <000701c1e7be$7040c520$0315b5d4@mabe> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.2627 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi! When am trying to install FreeBSD 4.5 from a CD on a Compaq ProLiant DL360 I get No disk found. Does anyone knows how to compile a kernel for a DL360 or is it not possible? Maybe I have screwed up something else... Magnus Benngard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 19 15:56:59 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from wartch.sapros.com (rularan.sapros.com [204.182.55.17]) by hub.freebsd.org (Postfix) with ESMTP id 3CAA437B405 for ; Fri, 19 Apr 2002 15:56:57 -0700 (PDT) Received: from wartch.sapros.com (localhost.sapros.com [127.0.0.1]) by wartch.sapros.com (8.12.1/8.12.1) with ESMTP id g3JMueRg071185; Fri, 19 Apr 2002 15:56:45 -0700 (PDT) (envelope-from peterh@wartch.sapros.com) Message-Id: <200204192256.g3JMueRg071185@wartch.sapros.com> To: Bruce Evans Cc: hardware@freebsd.org Subject: Re: Reading from the USB ugen device. Date: Fri, 19 Apr 2002 15:56:40 -0700 From: Peter Haight X-Spam-Status: No, hits=1.8 required=7.0 tests=NO_MX_FOR_FROM version=2.11 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >This might be caused by longstanding brokenness in sys_generic.c. E.g., >in dofileread(): Finally got a chance to try this out, but making this change didn't work. I did finally get the usb driver to print debug messages to the console and syscons, but the volume of messages is overwhelming syslogd so many messages are getting dropped. This is making it really hard for me to understand what's going on. Is there some way to make the kernel log to a file instead of to syslog? Or log more reliably? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 19 20:30:21 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from smtp.comcast.net (smtp.comcast.net [24.153.64.2]) by hub.freebsd.org (Postfix) with ESMTP id 8ED7537B417 for ; Fri, 19 Apr 2002 20:30:03 -0700 (PDT) Received: from lumeta.com (bgp424141bgs.union01.nj.comcast.net [68.36.190.135]) by mtaout02.icomcast.net (iPlanet Messaging Server 5.1 HotFix 0.3 (built Apr 8 2002)) with ESMTP id <0GUU003UXKE2OM@mtaout02.icomcast.net> for freebsd-hardware@FreeBSD.ORG; Fri, 19 Apr 2002 23:30:02 -0400 (EDT) Date: Fri, 19 Apr 2002 23:35:22 -0400 From: Tom Limoncelli Subject: 4.5 MAKEDEV is buggy for RocketPorts To: freebsd-hardware@FreeBSD.ORG Message-id: <3CC0E1FA.8020900@lumeta.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii; format=flowed Content-transfer-encoding: 7BIT X-Accept-Language: en-us User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4.1) Gecko/20020314 Netscape6/6.2.2 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi! The code in /dev/MAKEDEV to create the cuaR* and ttyR* devices is broken. This is likely because so few people use RocketPort serial ports with FreeBSD (I wish they'd contribute a newer driver!) There are 2 bugs: 1) MAKEDEV assumes that only one "RocketPort = 32" will appear in the output of dmesg. I fixed this by passing the output of dmesg through "sort -u", but there has got to be a better way. (my ugly patch is below). Without this patch, $ndevices="32\n32\n32\n32\n" instead of "32", similar problem with $controllers. The final patch should handle the situation where multiple controller cards are installed. 2) The code relies on "dmesg" to find out what controllers exist. I consider this to be a problem, albiet minor. If the machine hasn't been rebooted in long enough that dmesg no longer mentions "RocketPort0 = 32" (or whatever) then the script fails. (Hey, it actually happened to me. I had a machine up for something like 6 months before I went to run MAKEDEV). I don't see any other use of "dmesg" in MAKEDEV. --Tom # diff -cw /tmp/MAKEDEV /dev/MAKEDEV *** /tmp/MAKEDEV Mon Jan 28 08:13:17 2002 --- /dev/MAKEDEV Fri Apr 19 18:13:50 2002 *************** *** 1404,1410 **** BOARD=1; Rnum=0 MINOR=$(($BOARD * 65536)) controllers=$( ! dmesg | while read first rest; do case "$first" in RocketPort[0-4]) echo "$first" --- 1404,1410 ---- BOARD=1; Rnum=0 MINOR=$(($BOARD * 65536)) controllers=$( ! dmesg | /usr/bin/sort -u | while read first rest; do case "$first" in RocketPort[0-4]) echo "$first" *************** *** 1415,1421 **** rm -f ttyR* ttyiR* ttylR* for i in $controllers; do ndevices=$( ! dmesg | while read first bar ports rest; do case "$first" in $i*) echo "$ports" --- 1415,1421 ---- rm -f ttyR* ttyiR* ttylR* for i in $controllers; do ndevices=$( ! dmesg | /usr/bin/sort -u | while read first bar ports rest; do case "$first" in $i*) echo "$ports" *************** *** 1444,1450 **** BOARD=1; Rnum=0 MINOR=$(($BOARD * 65536)) controllers=$( ! dmesg | while read first rest; do case "$first" in RocketPort[0-4]) echo "$first" --- 1444,1450 ---- BOARD=1; Rnum=0 MINOR=$(($BOARD * 65536)) controllers=$( ! dmesg | /usr/bin/sort -u | while read first rest; do case "$first" in RocketPort[0-4]) echo "$first" *************** *** 1455,1461 **** rm -f cuaR* cuaiR* cualR* for i in $controllers; do ndevices=$( ! dmesg | while read first bar ports rest; do case "$first" in $i*) echo "$ports" --- 1455,1461 ---- rm -f cuaR* cuaiR* cualR* for i in $controllers; do ndevices=$( ! dmesg | /usr/bin/sort -u | while read first bar ports rest; do case "$first" in $i*) echo "$ports" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Apr 19 22: 8:43 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from web14808.mail.yahoo.com (web14808.mail.yahoo.com [216.136.224.224]) by hub.freebsd.org (Postfix) with SMTP id 5713237B41A for ; Fri, 19 Apr 2002 22:08:41 -0700 (PDT) Message-ID: <20020420050841.46374.qmail@web14808.mail.yahoo.com> Received: from [65.59.57.213] by web14808.mail.yahoo.com via HTTP; Fri, 19 Apr 2002 22:08:41 PDT Date: Fri, 19 Apr 2002 22:08:41 -0700 (PDT) From: mingo lu To: freebsd-hardware@freebsd.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1245494000-1019279321=:46195" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --0-1245494000-1019279321=:46195 Content-Type: text/plain; charset=us-ascii Hi: I need some information before I jump into the freebsd wagon... 1) Did anyone here successfully install frfeebsd on Toshiba tecra 8100? 2) Does the winmodem work, ie, dial up with the internal modem work? 3) Do the Toshiba sound (yamaha) and DVD work? TIA _mingo --------------------------------- Do You Yahoo!? Yahoo! Games - play chess, backgammon, pool and more --0-1245494000-1019279321=:46195 Content-Type: text/html; charset=us-ascii Hi:

I need some information before I jump into the freebsd
wagon...

1) Did anyone here successfully install frfeebsd on
Toshiba tecra 8100?
2) Does the winmodem work, ie, dial up with the internal modem work?
3) Do the Toshiba sound (yamaha) and DVD work?


TIA

_mingo


Do You Yahoo!?
Yahoo! Games - play chess, backgammon, pool and more --0-1245494000-1019279321=:46195-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Apr 20 8:33:27 2002 Delivered-To: freebsd-hardware@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 46C9A37B416 for ; Sat, 20 Apr 2002 08:33:23 -0700 (PDT) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id BAA26137; Sun, 21 Apr 2002 01:33:15 +1000 Date: Sun, 21 Apr 2002 01:33:42 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Peter Haight Cc: hardware@FreeBSD.ORG Subject: Re: Reading from the USB ugen device. In-Reply-To: <200204192256.g3JMueRg071185@wartch.sapros.com> Message-ID: <20020421012548.A22598-100000@gamplex.bde.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, 19 Apr 2002, Peter Haight wrote: > I did finally get the usb driver to print debug messages to the console and > syscons, but the volume of messages is overwhelming syslogd so many messages > are getting dropped. This is making it really hard for me to understand > what's going on. Is there some way to make the kernel log to a file instead > of to syslog? Or log more reliably? I think it wouldn't help much to log to a file -- the kernel message buffer may fill up before syslogd can read it if it is spammed with debug messages. A serial console connected to something with log facilities (I use som_term_prog | tee foo) works best here (use plain printf so that the messages get sent to the serial console synchronously). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message