Re: Western Digital MyBook 250GB USB takes *really* long to be recognized
On Wed, 6 Jun 2007 23:45:25 +0200 Marc "UBM" Bocklet <[EMAIL PROTECTED]> wrote: > > Hiho! ;-) > > I just bought a Western Digital MyBook 250GB external USB 2.0 drive > and I stumbled upon the problem mentioned in: > > kern/107495: Fix long wait before WD My Book 250GB (USB) is recognized > > There's a patch attached to that PR, which I applied, but it didn't > help. > > FreeBSD version is FreeBSD ubm.mine.nu 6.2-STABLE FreeBSD 6.2-STABLE > 4: Wed Jun 6 19:58:12 CEST 2007 > > > > Symptoms are as follows: > > when I plug the drive in, it is immediately > recognized by umass as: > > umass0: Western Digital External HDD, rev 2.00/1.08, addr 2 > > About 10 to 15 minutes later, cam kicks in and recognizes it as: > > da0 at umass-sim0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-0 device > da0: 40.000MB/s transfers > da0: 238475MB (488397168 512 byte sectors: 255H 63S/T 30401C) > > >From that point onwards, everything works fine, I just finished > rsyncing my entire home directory (about 40gb) to the disk with ehci > enabled. > > I'm just curious if there is anything to be done about the long delay? > (not that I care that much, drive is attached to my "server", so it > won't be unplugged or be turned off very soon :-)) > > Thanks in advance! :-) forgot my dmesg, find it attached to this mail :-) Bye Marc dmesg Description: Binary data ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: cvsup error
Wesley Shields wrote: On Wed, Jun 06, 2007 at 10:20:11AM -0700, Doug Barton wrote: Wesley Shields wrote: The difference is that csup is written in C and included in the base. The only lacking feature in csup is that it doesn't work in checkout mode, which shouldn't be a problem for your average use. You have it backwards. csup _only_ works in checkout mode, what it can't do is mirror a repository. This is fine for the average FreeBSD user however, since checking out the current version of the src or ports tree is what the vast majority do anyway. You're right, my apologies. Not working in checkout mode defeats the purpose for the vast majority of the people using it. I guess I just wasn't thinking straight. I may be wrong about checkout mode, but that was a caveat when it went into the tree IIRC. If that is no longer the case I apologize for the misinformation. If you are going to offer advice on the lists, please take the time to verify that what you're saying is correct. Otherwise it's just a waste of time for all concerned. I'm picking on your post here a little because it's a good example of a disturbing trend, please don't take it personally. Don't worry, I'm not taking it personally. It just goes to show that I should think twice and double check things before sending anything. :) Thank you for the clarification. -- WXS just for clarification, using csup working flawlessly Thanks all for the responds. such a great community TIA ZeN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Server setup as a Diskless Server on reboot sends DHCP Discover packets out
Hey Guys, I have a strange one: I've setup a machine as a diskless server, using PXEBoot with ihc-dhcpd to offer dhcp and dhcp configuration information. I did a test reboot on the server, and found to my dismay that the server NIC's are sending out dhcp discover packets and trying to get an address. The NIC's IP info is captured correctly in /etc/rc.conf: ifconfig_bge0="inet 196.30.157.162 media 100baseTX mediaopt full-duplex netmask 255.255.255.192" ifconfig_bge1="inet 196.31.157.162 media 100baseTX mediaopt full-duplex netmask 255.255.255.0" and the /etc/dhclient.conf file is empty. I thought maybe it was the /conf directory used in the diskless Root structure creation, so I renamed it out of the way, but that made no difference. I can't seem to find where the definition is that makes the NIC's ask for DHCP info. Shortened output of /var/run/dmesg.boot pertaining to the DHCP Discover packets: Sending DHCP Discover packet from interface bge0 (00:0b:db:e6:a9:33) Sending DHCP Discover packet from interface bge1 (00:0b:db:e6:a9:35) DHCP/BOOTP timeout for server 255.255.255.255 DHCP/BOOTP timeout for server 255.255.255.255 DHCP/BOOTP timeout for server 255.255.255.255 DHCP/BOOTP timeout for server 255.255.255.255 DHCP/BOOTP timeout for server 255.255.255.255 Received DHCP Offer packet on bge0 from 196.30.157.161 (accepted) (no root path) Sending DHCP Request packet from interface bge0 (00:0b:db:e6:a9:33) DHCP/BOOTP timeout for server 255.255.255.255 Received DHCP Ack packet on bge0 from 196.30.157.161 (accepted) (got root path) DHCP timeout for interface bge1 bge0 at 196.30.157.149 server 196.30.157.161 server name diskless.csc.jnb6.za.uu.net boot file pxeboot subnet mask 255.255.255.192 router 196.30.157.129 rootfs 196.30.157.161:/diskless_root Adjusted interface bge0 Shutdown interface bge1 Trying to mount root from ufs:/dev/aacd0s1a 9 times out of ten the DHCP will just sit and timeout (it gets a DHCP return from my other diskless server running DHCPD) and then the 1 time out of 10 will mount the hard drive / partition. Thanks Kim Attree ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: calcru: runtime went backwards, RELENG_6, SMP
On Wednesday 06 June 2007 17:17:28 Ivan Voras wrote: > Dmitry Morozovsky wrote: > > Dear colleagues, > > > > on a newly built Supermicro with Pentium D 2.8 (Dual core) with SMP > > kernel I got zillions of 'runtime went backwards' errors, both on i386 > > and amd64 kernels. > > > > Upd: on GENERIC/amd64 kernel I got the same errors. > > Do you perhaps run with TSC timecounter? (that's the only cause I've > notice that can generate this message). I got recently some squid panics where the machines freezed accusing calcru went backwards too. This happened on amd64 with sources from first week of may. I got it on 20-30 days uptime untouched smp dual-core amds and two opteron server. On all of them acpi-fast seems to be the counter. Anyway I did a cvsup and haven't seen the problem again so far. I did't get any message before, the first caused a panic and funny all panics happened almost the same hour last friday. -- João A mensagem foi scaneada pelo sistema de e-mail e pode ser considerada segura. Service fornecido pelo Datacenter Matik https://datacenter.matik.com.br ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: iSCSI initiator tester wanted
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Danny Braniss wrote: > > Hi all, > > I'm in the last mile before crossing the beta->release line, > > so I'd like to get some input, and update the list of targets it supports. > > you can obtain the driver from: > > ftp://ftp.cs.huji.ac.il/users/danny/freebsd/iscsi-2.0.92.tar.gz Just tried it out. Set up a vmware FreeBSD 6.2 install on my windows box. Installed the kernel module and initiator program and targeted it at an OpenSolaris machine running ZFS and exporting a 1GB volume over iSCSI on our network. Did a newfs on the imported iSCSI /dev/da0 and mounted it OK. Copied files over to it OK. Ran bonnie++ over it as an experiment. Had the following kernel message pop-up twice, however: lnc0: Missed packet -- no receive buffer Not sure what the cause was. Perhaps I was just thrashing out my virtual NIC... -BEGIN PGP SIGNATURE- iD8DBQFGZ8lGcuckYiL1ACcRAgOcAKCIjdUMGZe+e+eqq6wI5zu20kx5EgCeNO6F MUKU9HSk5IQUFVehTKs9vt4= =gKDc -END PGP SIGNATURE- ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
VPN using bundled ppp?
Hi, all! Is it possible to use VPN connections using bundled ppp without installing any additional software in FreeBSD 6.2 STABLE? Dmitry "d-Metrius" Baranov === e-mail: private: [EMAIL PROTECTED] www: http://www.d-metrius.ru icq: 87-97-07 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: VPN using bundled ppp?
Hi, all! Is it possible to use VPN connections using bundled ppp without installing any additional software in FreeBSD 6.2 STABLE? Dmitry "d-Metrius" Baranov === e-mail: private: [EMAIL PROTECTED] www: http://www.d-metrius.ru icq: 87-97-07 Not as far as i know. Install /usr/ports/net/pptpclient/ That's what I use for pptp vpn's. It's easy to set up and works like a charm. -Clay ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: iSCSI initiator tester wanted
Nathan Butcher wrote: > Danny Braniss wrote: > lnc0: Missed packet -- no receive buffer > > Not sure what the cause was. Perhaps I was just thrashing out my virtual > NIC... Yeah, thats an issue with the default vmware emulated nic... Ta, Joe ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: VPN using bundled ppp?
On Thu, 07 Jun 2007 13:41:47 +0200, Clayton Milos <[EMAIL PROTECTED]> wrote: Hi, all! Is it possible to use VPN connections using bundled ppp without installing any additional software in FreeBSD 6.2 STABLE? Dmitry "d-Metrius" Baranov === e-mail: private: [EMAIL PROTECTED] www: http://www.d-metrius.ru icq: 87-97-07 Not as far as i know. Install /usr/ports/net/pptpclient/ That's what I use for pptp vpn's. It's easy to set up and works like a charm. In 6-STABLE there is the lagg(4) driver. Ronald -- Ronald Klop Amsterdam, The Netherlands ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Hard Hang, nothing in logs / no panics
On Friday 11 May 2007 16:47, Kris Kennaway wrote: > > Am I possible looking at a hardware issue? If so > > what is the best way to test for it? > > If that doesn't work then in my experience it is likely to be > hardware-related. The usual debugging procedure then involves trying > to replicate on an unrelated machine, and/or swapping out hardware > components. Kris, Sorry for the time delay. But we have confirmed this is not a hardware issue. We have is dead locking across multiple systems, when bridge a moderate amount of tcp connections. I have no idea how to debug this. Could it be an issues with if_config of pf? We are using the latest drivers form intel. But have ruled it out as being an driver or network card related problem. Roger ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Unrecognized archive format with RELENG_6_2 and RELENG_6
Quoting Tim Kientzle <[EMAIL PROTECTED]>: This morning I have revert libarchive (src/lib/libarchive) and tar (src/usr.bin/tar) back to RELENG_6_1 and surprisingly (or maybe not) it works fine now. After that I try to read/list the tar from tape with tar -t: $ sudo tar -tf /dev/sa0 archive.dmp tar: Unrecognized archive format: Inappropriate file type or format But when I extract the archive from tape, it works perfectly: $ sudo tar -xvf /dev/sa0 x archive.dmp What SCSI controller are you using? This could conceivably be an issue with a particular SCSI controller. A few lines from 'dmesg' could help here. Here you go ciss0: port 0x4000-0x40ff mem 0xfdff-0xfdff1fff,0xfdf800 00-0xfdfb irq 51 at device 3.0 on pci4 ciss0: [GIANT-LOCKED] .. sa0 at ciss0 bus 33 target 5 lun 0 sa0: Removable Sequential Access SCSI-3 device sa0: 135.168MB/s transfers P.S. In the meantime, of course, tar from 6.1 and gtar should both work in this situation. Yep, at the moment I have switched the tar release back to the one from 6.1. Kind regards, Robin Gruyters Network and Security Engineer Yirdis B.V. I: http://yirdis.com P: +31 (0)36 5300394 F: +31 (0)36 5489119 pgpNv9Aco2ggJ.pgp Description: PGP Digital Signature
Re: Unrecognized archive format with RELENG_6_2 and RELENG_6
Quoting Tim Kientzle <[EMAIL PROTECTED]>: After that I try to read/list the tar from tape with tar -t: $ sudo tar -tf /dev/sa0 archive.dmp tar: Unrecognized archive format: Inappropriate file type or format But when I extract the archive from tape, it works perfectly: $ sudo tar -xvf /dev/sa0 Using dd to feed tar does work though. (I think this agrees with Robin's findings although the fact that it works with -z is curious) This is a Tandberg TS400 (LTO2 drive, LTO1 tape) idd, same problem here. When using -z option, works perfectly. Without it, it fails. Our tapedrive is a "HP C7438A V312". (DAT) Please try the following: sudo ktrace tar -tf /dev/sa0 Then run 'kdump | less' and see if you can find a pair of 'lseek' calls, which will probably look something like this: 53127 bsdtar CALL lseek(0x3,0,0,0,0x1) 53127 bsdtar RET lseek 6656000/0x659000 53127 bsdtar CALL lseek(0x3,0,0x70800,0,0x1) 53127 bsdtar RET lseek 7116800/0x6c9800 Here you go: 95225 bsdtar CALL lseek(0x3,0,0,0,0x1) 95225 bsdtar RET lseek 65536/0x1 95225 bsdtar CALL lseek(0x3,0,0,0,0x1) 95225 bsdtar RET lseek 65536/0x1 Robin Gruyters Network and Security Engineer Yirdis B.V. I: http://yirdis.com P: +31 (0)36 5300394 F: +31 (0)36 5489119 pgpBeBLBin0Cu.pgp Description: PGP Digital Signature
Re: ACPI hanging shutdown
On Wed, Jun 06, 2007 at 11:50:00PM -0400, Tom McLaughlin wrote: > Sometime between the beginning of April and May 14(?) there appears to > have been a change in ACPI which is causing my IBM R51 to hang when > shutting down. I see syslog exit and then nothing. I need to do a hard > shutdown with the partitions still mounted for it to turn off. I booted > without ACPI and the problem has gone away. Successive updates have not > solved this. Anyone know what could be causing this? Thanks. Have you checked and/or tried setting the following two sysctls? I believe the one you might want is hw.acpi.handle_reboot=1. $ sysctl -a | grep 'acpi.*reboot' hw.acpi.disable_on_reboot: 0 hw.acpi.handle_reboot: 0 -- | Jeremy Chadwickjdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: VPN using bundled ppp?
On 6/7/07, Baranov Dmitry <[EMAIL PROTECTED]> wrote: Hi, all! Is it possible to use VPN connections using bundled ppp without installing any additional software in FreeBSD 6.2 STABLE? Dmitry "d-Metrius" Baranov === e-mail: private: [EMAIL PROTECTED] www: http://www.d-metrius.ru icq: 87-97-07 VPN connections between FreeBSD and what ? Another FreeBSD or Windows ? I use VPN between FreeBSD and FreeBSD using ssh as a secure tunnel and run /usr/sbin/ppp over that. Works very fine for me. If you mean that, i can send you my configs and scripts. -- ghozzy ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: VPN using bundled ppp?
Baranov Dmitry wrote: Hi, all! Is it possible to use VPN connections using bundled ppp without installing any additional software in FreeBSD 6.2 STABLE? Dmitry "d-Metrius" Baranov === e-mail: private: [EMAIL PROTECTED] www: http://www.d-metrius.ru icq: 87-97-07 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]" Yes, but be prepared! :-) Man ppp: "...It is possible to configure ppp to participate in Microsoft's Windows VPN..." Regards, Muxas ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Problems with BCE network adapter (Dell PE2950)
Hi, I am seeing some problems with one of my Dell PowerEdge 2950's (running RELENG_6_2) on board bce NICs. The interface seems to crash with the following errors, to which the fix seems to be and "ifconfig bce0 down; ifconfig bce0 up": Jun 7 12:20:29 gonzo kernel: bce0: discard frame w/o leading ethernet header (len 4294967292 pkt len 4294967292) Jun 7 12:20:29 gonzo last message repeated 54 times Jun 7 12:20:58 gonzo kernel: nfs server nfs-server:/usr/home: not responding Is this a know problem? If so is there a solution? Tom #uname -a FreeBSD gonzo.mintel.co.uk 6.2-RELEASE FreeBSD 6.2-RELEASE #10: Thu Apr 5 10:53:39 BST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/PE2950 amd64 amd64 Intel(R) Xeon(R) CPU 5160 @ 3.00GHz FreeBSD ## dmesg.boot snippet bce0: mem 0xf400-0xf5ff irq 16 at device 0.0 on pci9 bce0: ASIC ID 0x57081020; Revision (B2); PCI-X 64-bit 133MHz miibus0: on bce0 brgphy0: on miibus0 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bce0: Ethernet address: 00:18:8b:88:d8:81 ## pciconf -lv snippet [EMAIL PROTECTED]:0:0: class=0x02 card=0x01b21028 chip=0x164c14e4 rev=0x12 hdr=0x00 vendor = 'Broadcom Corporation' class= network subclass = ethernet #ifconfig bce0 bce0: flags=8843 mtu 8192 options=3b inet 172.31.0.13 netmask 0xff00 broadcast 172.31.0.255 inet 172.31.0.157 netmask 0x broadcast 172.31.0.157 inet 172.31.0.161 netmask 0x broadcast 172.31.0.161 ether 00:18:8b:88:d8:81 media: Ethernet autoselect (1000baseTX ) status: active #Switch port counters console# show interfaces counters ethernet g10 PortInOctets InUcastPkts InMcastPkts InBcastPkts -- --- --- --- g102615415297 875639870 13480 Port OutOctets OutUcastPkts OutMcastPkts OutBcastPkts -- g102535595313 136391705 10740316 1420686 FCS Errors: 0 Single Collision Frames: 0 Late Collisions: 0 Excessive Collisions: 0 Internal MAC Tx Errors: 0 Oversize Packets: 0 Internal MAC Rx Errors: 0 Received Pause Frames: 0 Transmitted Pause Frames: 0 ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Hard Hang, nothing in logs / no panics
On Thu, Jun 07, 2007 at 08:23:32AM -0500, Roger Miranda wrote: > On Friday 11 May 2007 16:47, Kris Kennaway wrote: > > > Am I possible looking at a hardware issue? If so > > > what is the best way to test for it? > > > > If that doesn't work then in my experience it is likely to be > > hardware-related. The usual debugging procedure then involves trying > > to replicate on an unrelated machine, and/or swapping out hardware > > components. > > Kris, > > Sorry for the time delay. > > But we have confirmed this is not a hardware issue. We have is dead locking > across multiple systems, when bridge a moderate amount of tcp connections. > > I have no idea how to debug this. > > Could it be an issues with if_config of pf? We are using the latest drivers > form intel. But have ruled it out as being an driver or network card related > problem. And to confirm, WITNESS finds nothing and you are unable to break to DDB even with STOP_NMI? Kris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
unionfs through whole / with upper layer on remote NFS directory
Hi all, can you advise me if it is real and realizable what I plan ? Here it is, I have installed fbsd-6-stable pc with the last unionfs diff-19 patch and have a recompiled kernel with this new unionfs implementation and I would like this: - /dev/ad0s1a on CF card is read-only permanently - mdconfig is forbiden to create var and tmp ramdisks in rc.conf - to my custom directory for example /unionfs is mounted remote NFS directory with read-write rights and with no_all_squash or no_root_squash and sync options etc. - the upper layer of unionfs should be on this remote NFS directory - the lower layer of unionfs should be the whole mount point / the whole CF card with ro When I tried to start this command, new error message appeared and I do not know what to do with this probably because I do something wrong. The mount_unionfs utility attaches directory above uniondir in such a way that the contents of both directory trees remain visible. By default, directory becomes the upper layer and uniondir becomes the lower layer. So directory is /unionfs and lower layer is the whole / # mount -t unionfs /unionfs / mount_unionfs: /unionfs (/unionfs) and / (/) are not distinct paths the second try: # mount -t unionfs /unionfs /dev/ad0s1a like with cd-rom mount: /dev/ad0s1a: not a directory but with /var it is okay # mount -t unionfs /unionfs /var # mount /dev/ad0s1a on / (ufs, NFS exported, local) devfs on /dev (devfs, local) /dev/ad0s2a on /free (ufs, local, soft-updates) procfs on /proc (procfs, local) :/unionfs on /var (unionfs, local) NFS:/home/buffer on /unionfs (nfs) It seems that lower layer could not be the whole / or /dev/ad0s1a, doesn´t it ? Bye Dan ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: ACPI hanging shutdown
On Thu, 2007-06-07 at 06:27 -0700, Jeremy Chadwick wrote: > On Wed, Jun 06, 2007 at 11:50:00PM -0400, Tom McLaughlin wrote: > > Sometime between the beginning of April and May 14(?) there appears to > > have been a change in ACPI which is causing my IBM R51 to hang when > > shutting down. I see syslog exit and then nothing. I need to do a hard > > shutdown with the partitions still mounted for it to turn off. I booted > > without ACPI and the problem has gone away. Successive updates have not > > solved this. Anyone know what could be causing this? Thanks. > > Have you checked and/or tried setting the following two sysctls? > I believe the one you might want is hw.acpi.handle_reboot=1. > > $ sysctl -a | grep 'acpi.*reboot' > hw.acpi.disable_on_reboot: 0 > hw.acpi.handle_reboot: 0 > Setting hw.acpi.handle_reboot=1 and a reboot did the trick. Thanks. Curious what has changed to cause this. tom -- | tmclaugh at sdf.lonestar.org tmclaugh at FreeBSD.org | | FreeBSD http://www.FreeBSD.org | | BSD#http://www.mono-project.com/Mono:FreeBSD | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: iSCSI initiator tester wanted
> This is an OpenPGP/MIME signed message (RFC 2440 and 3156) > --enig2465C3FB4D976B8B44FBA3F0 > Content-Type: text/plain; charset=UTF-8 > Content-Transfer-Encoding: quoted-printable > > Danny Braniss wrote: > > Hi all, > > I'm in the last mile before crossing the beta->release line, > > so I'd like to get some input, and update the list of targets it suppor= > ts. > > you can obtain the driver from: > > Have you tested it with net/iscsi-target from ports? I get the following > messages and errors when I try it: > > Jun 7 22:53:08 finstall kernel: ic_action: called > Jun 7 22:53:08 finstall kernel: ic_action: func_code=3D0x901 flags=3D0xc= > 0 > status=3D0x0 target=3D0 lun=3D0 retry_count=3D1 timeout=3D30 > Jun 7 22:53:08 finstall kernel: ic_action: XPT_SCSI_IO cmd=3D0x35 > Jun 7 22:53:08 finstall kernel: scsi_encap: called > Jun 7 22:53:08 finstall kernel: scsi_encap: ccb->sp=3D0xc2e97c00 > Jun 7 22:53:08 finstall kernel: dwl: called > Jun 7 22:53:08 finstall kernel: isc_qout: called > Jun 7 22:53:08 finstall kernel: 0] isc_qout: enqued: pq=3D0xc37ff0bc > Jun 7 22:53:08 finstall kernel: proc_out: called > Jun 7 22:53:08 finstall kernel: 0] proc_out: opcode=3D0x1 sn(cmd=3D0x27 > expCmd=3D0x26 maxCmd=3D0x26 expStat=3D0x0 itt=3D0x27) > Jun 7 22:53:08 finstall kernel: isc_sendPDU: called > Jun 7 22:53:08 finstall kernel: 0] ism_proc: odone=3D1 > Jun 7 22:53:08 finstall kernel: proc_out: called > Jun 7 22:53:08 finstall kernel: 0] ism_proc: odone=3D0 > Jun 7 22:53:08 finstall kernel: so_input: called > Jun 7 22:53:08 finstall kernel: so_getbhs: called > Jun 7 22:53:08 finstall kernel: proc_out: called > Jun 7 22:53:08 finstall kernel: 0] ism_proc: odone=3D0 > Jun 7 22:53:08 finstall kernel: so_recv: called > Jun 7 22:53:08 finstall kernel: 0] so_recv: len=3D48] opcode=3D0x21 > ahs_len=3D0x0 ds_len=3D0x0 > Jun 7 22:53:08 finstall kernel: ism_recv: called > Jun 7 22:53:08 finstall kernel: 0] ism_recv: opcode=3D0x21 itt=3D0x27 > stat#0x1 maxcmd=3D0x27 > Jun 7 22:53:08 finstall kernel: _scsi_rsp: called > Jun 7 22:53:08 finstall kernel: _scsi_rsp: itt=3D27 pq=3D0xc37ff5e0 > opq=3D0xc37ff0bc > Jun 7 22:53:08 finstall kernel: iscsi_done: called > Jun 7 22:53:08 finstall kernel: _scsi_done: called > Jun 7 22:53:08 finstall kernel: _scsi_done: ccb_h->status=3D1 > Jun 7 22:53:08 finstall kernel: so_input: called > Jun 7 22:53:08 finstall kernel: so_getbhs: called > Jun 7 22:53:08 finstall kernel: proc_out: called > Jun 7 22:53:08 finstall kernel: 0] ism_proc: odone=3D0 > Jun 7 22:53:08 finstall iscontrol[2084]: cam_open_btl: no passthrough > device found at 1:0:1 > Jun 7 22:53:08 finstall iscontrol[2084]: cam_open_btl: no passthrough > device found at 1:0:2 > Jun 7 22:53:08 finstall iscontrol[2084]: cam_open_btl: no passthrough > device found at 1:0:3 > Jun 7 22:53:38 finstall kernel: _nop_out: called > Jun 7 22:53:38 finstall kernel: 0] _nop_out: cws=3D1 > Jun 7 22:53:38 finstall kernel: proc_out: called > Jun 7 22:53:38 finstall kernel: 0] ism_proc: odone=3D0 > > The message on the machine running scsi-target is: "Unsupported INQUIRY > VPD page 80" yes, I have tested it against ports/net/iscsi-target, I use it to try out errror recovery :-), and as far as I could tell it's harmelss. Anothere thing I can report is that running both (target/initiator) does not work, and it seems that the target gets stuck. danny ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
