Re: device_attach: ixv0 attach returned 5
Well then this is really annoying. I can image few other applications besides
virtualization. Jails using vnet bound to VF instead of epair being one of
examples. Any hope that someone will port the SR-IOV from Intel’s code into
the base driver on foreseeable future?
regards
Michal
> On 21 Nov 2019, at 18:52, Richard Gallamore wrote:
>
> Hello Michal,
>
>> I’m running 12-STABLE. Is this a hardware related or possibly a driver
> bug?
> This is probably a driver / module bug.
>
> [1] is a bug on this issue, that I opened some years ago. The last time
> I tested the sr-iov functionality it was working if you compile the intel
> module with sr-iov support enabled but not with the base module. This
> was probably a couple years ago though and on 12-CURRENT before
> 12 was released.
>
> Personally I suggest you just avoid sr-iov though and use bridges. sr-iov
> was
> a cool idea but it just failed to get an attraction. Probably several
> reasons
> for this, based on my experience I would say the primary reason is because
> its designed use case is for virtualization, and if you do use this for
> virtualization, you trade the ability to do live migrations due to using
> physical hardware.
>
> Hope this helps,
> Richard Gallamore
>
> On Thu, Nov 21, 2019 at 3:53 AM Michal Vančo via freebsd-stable <
> freebsd-stable@freebsd.org> wrote:
>
>> Hi,
>>
>> I’m trying to get SR-IOV working with my two port Intel 10G NIC:
>>
>> ix0@pci0:3:0:0: class=0x02 card=0x15ad15d9 chip=0x15ad8086 rev=0x00
>> hdr=0x00
>>vendor = 'Intel Corporation'
>>device = 'Ethernet Connection X552/X557-AT 10GBASE-T'
>>class = network
>>subclass = ethernet
>> ix1@pci0:3:0:1: class=0x02 card=0x15ad15d9 chip=0x15ad8086 rev=0x00
>> hdr=0x00
>>vendor = 'Intel Corporation'
>>device = 'Ethernet Connection X552/X557-AT 10GBASE-T'
>>class = network
>>subclass = ethernet
>>
>> with this iovctl config:
>>
>> # cat /etc/iovctl_ix1.conf
>> PF {
>>device: "ix1";
>>num_vfs: 4;
>> }
>>
>> I get 4 PCI devices created:
>>
>> none57@pci0:3:0:129:class=0x02 card=0x15ad15d9 chip=0x15a88086
>> rev=0x00 hdr=0x00
>>vendor = 'Intel Corporation'
>>device = 'Ethernet Connection X552 Virtual Function'
>>class = network
>>subclass = ethernet
>> none58@pci0:3:0:131:class=0x02 card=0x15ad15d9 chip=0x15a88086
>> rev=0x00 hdr=0x00
>>vendor = 'Intel Corporation'
>>device = 'Ethernet Connection X552 Virtual Function'
>>class = network
>>subclass = ethernet
>> none59@pci0:3:0:133:class=0x02 card=0x15ad15d9 chip=0x15a88086
>> rev=0x00 hdr=0x00
>>vendor = 'Intel Corporation'
>>device = 'Ethernet Connection X552 Virtual Function'
>>class = network
>>subclass = ethernet
>> none60@pci0:3:0:135:class=0x02 card=0x15ad15d9 chip=0x15a88086
>> rev=0x00 hdr=0x00
>>vendor = 'Intel Corporation'
>>device = 'Ethernet Connection X552 Virtual Function'
>>class = network
>>subclass = ethernet
>>
>> But the driver fails to attach with following errors:
>>
>> ixv0: at device 0.129
>> on pci4
>> ixv0: ...reset_hw() failure: Reset Failed!
>> ixv0: IFDI_ATTACH_PRE failed 5
>> device_attach: ixv0 attach returned 5
>> ixv0: at device 0.131
>> on pci4
>> ixv0: ...reset_hw() failure: Reset Failed!
>> ixv0: IFDI_ATTACH_PRE failed 5
>> device_attach: ixv0 attach returned 5
>> ixv0: at device 0.133
>> on pci4
>> ixv0: ...reset_hw() failure: Reset Failed!
>> ixv0: IFDI_ATTACH_PRE failed 5
>> device_attach: ixv0 attach returned 5
>> ixv0: at device 0.135
>> on pci4
>> ixv0: ...reset_hw() failure: Reset Failed!
>> ixv0: IFDI_ATTACH_PRE failed 5
>> device_attach: ixv0 attach returned 5
>>
>> I’m running 12-STABLE. Is this a hardware related or possibly a driver bug?
>>
>> regards
>> Michal
>>
>> ___
>> freebsd-stable@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
>>
> ___
> freebsd-...@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
device_attach: ixv0 attach returned 5
Hi,
I’m trying to get SR-IOV working with my two port Intel 10G NIC:
ix0@pci0:3:0:0: class=0x02 card=0x15ad15d9 chip=0x15ad8086 rev=0x00 hdr=0x00
vendor = 'Intel Corporation'
device = 'Ethernet Connection X552/X557-AT 10GBASE-T'
class = network
subclass = ethernet
ix1@pci0:3:0:1: class=0x02 card=0x15ad15d9 chip=0x15ad8086 rev=0x00 hdr=0x00
vendor = 'Intel Corporation'
device = 'Ethernet Connection X552/X557-AT 10GBASE-T'
class = network
subclass = ethernet
with this iovctl config:
# cat /etc/iovctl_ix1.conf
PF {
device: "ix1";
num_vfs: 4;
}
I get 4 PCI devices created:
none57@pci0:3:0:129:class=0x02 card=0x15ad15d9 chip=0x15a88086 rev=0x00
hdr=0x00
vendor = 'Intel Corporation'
device = 'Ethernet Connection X552 Virtual Function'
class = network
subclass = ethernet
none58@pci0:3:0:131:class=0x02 card=0x15ad15d9 chip=0x15a88086 rev=0x00
hdr=0x00
vendor = 'Intel Corporation'
device = 'Ethernet Connection X552 Virtual Function'
class = network
subclass = ethernet
none59@pci0:3:0:133:class=0x02 card=0x15ad15d9 chip=0x15a88086 rev=0x00
hdr=0x00
vendor = 'Intel Corporation'
device = 'Ethernet Connection X552 Virtual Function'
class = network
subclass = ethernet
none60@pci0:3:0:135:class=0x02 card=0x15ad15d9 chip=0x15a88086 rev=0x00
hdr=0x00
vendor = 'Intel Corporation'
device = 'Ethernet Connection X552 Virtual Function'
class = network
subclass = ethernet
But the driver fails to attach with following errors:
ixv0: at device 0.129 on
pci4
ixv0: ...reset_hw() failure: Reset Failed!
ixv0: IFDI_ATTACH_PRE failed 5
device_attach: ixv0 attach returned 5
ixv0: at device 0.131 on
pci4
ixv0: ...reset_hw() failure: Reset Failed!
ixv0: IFDI_ATTACH_PRE failed 5
device_attach: ixv0 attach returned 5
ixv0: at device 0.133 on
pci4
ixv0: ...reset_hw() failure: Reset Failed!
ixv0: IFDI_ATTACH_PRE failed 5
device_attach: ixv0 attach returned 5
ixv0: at device 0.135 on
pci4
ixv0: ...reset_hw() failure: Reset Failed!
ixv0: IFDI_ATTACH_PRE failed 5
device_attach: ixv0 attach returned 5
I’m running 12-STABLE. Is this a hardware related or possibly a driver bug?
regards
Michal
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ath0: device timeout on 9.0-STABLE
Hi, thanks for your response. Though there is one more thing. Is my adapter supposed to work in 5GHz band? I'm sure it works in windows and linux. Trying to switch to a different SSID (5GHz one) on the same AP, wlan0 stay unassociated (status: no carrier): # ifconfig wlan0 wlan0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:19:7e:52:1c:c4 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid XXX (5 GHz) channel 36 (5180 MHz 11a) regdomain ETSI2 country SK indoor ecm authmode WPA2/802.11i privacy ON deftxkey UNDEF txpower 17 bmiss 7 mcastrate 6 mgmtrate 6 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 12 wme burst roaming MANUAL # /usr/src/tools/tools/ath/athstats/athstats -i ath0 3245 data frames received 1102 data frames transmit 652 mib overflow interrupts 6M current transmit rate 116 rx failed 'cuz of bad CRC 46 rx failed 'cuz of PHY err 46 CCK restart -0/+0TDMA slot adjust (usecs, smoothed) 23 rssi of last ack 25 avg recv rssi -96 rx noise floor 1102 tx frames through raw api 1spur immunity level 1first step level 14 ANI increased spur immunity 889 ANI enabled OFDM weak signal detect 889 ANI disabled CCK weak signal threshold 10 ANI increased first step level 180060 cumulative OFDM phy error count 1709 cumulative CCK phy error count 113 bad FCS 25 average rssi (beacons only) 32 average rssi (all rx'd frames) 23 average rssi (ACKs only) Antenna profile: [0] tx 1056 rx 200 [1] tx0 rx 3045 With these messages in dmesg: ar5212StopDmaReceive: dma failed to stop in 10ms AR_CR=0x0024 AR_DIAG_SW=0x4220 ar5212StopDmaReceive: dma failed to stop in 10ms AR_CR=0x0024 AR_DIAG_SW=0x4220 Michal On 25.1.2012, at 8:52, Adrian Chadd wrote: Hi, The LED stuff may be a bit broken for 9.0. I'll try to fix it up and backport the GPIO and LED fixes. Adrian On 24 January 2012 23:51, Michal Vančo mva...@di-vision.sk wrote: Adrian, believe or not … it simply started to work. I just left my thinkpad turned off during the night and now when I booted, almost everything works as expected: # ifconfig wlan0 wlan0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500 ether 00:19:7e:52:1c:c4 inet 192.168.0.17 netmask 0xff00 broadcast 192.168.0.255 nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL media: IEEE 802.11 Wireless Ethernet OFDM/48Mbps mode 11g status: associated ssid XXX channel 9 (2452 MHz 11g) bssid 10:9a:dd:88:2a:5d regdomain ETSI2 country SK indoor ecm authmode WPA2/802.11i privacy ON deftxkey UNDEF AES-CCM 3:128-bit txpower 30 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme burst roaming MANUAL # /usr/src/tools/tools/ath/athstats/athstats -i ath0 4228 data frames received 818 data frames transmit 3tx frames with an alternate rate 126 long on-chip tx retries 29480mib overflow interrupts 24M current transmit rate 730 tx frames with short preamble 210 rx failed 'cuz of bad CRC 18 rx failed 'cuz of PHY err 18 CCK restart 10 periodic calibrations -0/+0TDMA slot adjust (usecs, smoothed) 37 rssi of last ack 37 avg recv rssi -96 rx noise floor 90 tx frames through raw api 1spur immunity level 1first step level 9ANI increased spur immunity 2ANI decrease spur immunity 103 ANI enabled OFDM weak signal detect 4ANI disabled OFDM weak signal detect 102 ANI disabled CCK weak signal threshold 3ANI increased first step level 7392282 cumulative OFDM phy error count 34526cumulative CCK phy error count 20 ANI forced listen time to zero 126 missing ACK's 291 bad FCS 2928 beacons received 39 average rssi (beacons only) 37 average rssi (all rx'd frames) 37 average rssi (ACKs only) Antenna profile: [0] tx 817 rx 65 [1] tx0 rx 4163 I say almost because that small WiFi-LED doesn't blink as it should. Is there any way to fix this? I see these sysctls: dev.ath.0.softled: 0 dev.ath.0.ledpin: 0 dev.ath.0.ledon: 0 dev.ath.0.ledidle: 2700 but I'm lost with them :) regards michal On 25.1.2012, at 4:46, Adrian Chadd wrote: Sure, can you please: * compile with the following options: options ATH_DEBUG options AH_DEBUG options ATH_DIAGAPI * compile /usr/src/sys/tools/tools/ath/athstats/ * run athstats -i ath0 and email them to me + freebsd-wirel...@freebsd.org Thanks! Adrian On 24
ath0: device timeout on 9.0-STABLE
Hi there,
I've installed 9.0-STABLE (also tried on 9.0-RELEASE) on my Thinkpad T60 and
I'm not able to use WiFi. Kernel is GENERIC.
pciconf -lv:
ath0@pci0:3:0:0:class=0x028000 card=0x0033168c chip=0x0024168c rev=0x01
hdr=0x00
vendor = 'Atheros Communications Inc.'
device = 'AR5008 Wireless Network Adapter'
class = network
relevant part of rc.conf:
wlans_ath0=wlan0
create_args_wlan0=country SK
ifconfig_wlan0=WPA DHCP
and wpa_supplicant.conf:
ctrl_interface=/var/run/wpa_supplicant
network={
ssid=XXX
psk=XXX
}
dmesg just fills with ath0: device timeout messages and wifi just doesn't
work.
any clue?
regards
michal
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ath0: device timeout on 9.0-STABLE
Adrian,
believe or not … it simply started to work. I just left my thinkpad turned off
during the night and now when I booted, almost everything works as expected:
# ifconfig wlan0
wlan0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
ether 00:19:7e:52:1c:c4
inet 192.168.0.17 netmask 0xff00 broadcast 192.168.0.255
nd6 options=29PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL
media: IEEE 802.11 Wireless Ethernet OFDM/48Mbps mode 11g
status: associated
ssid XXX channel 9 (2452 MHz 11g) bssid 10:9a:dd:88:2a:5d
regdomain ETSI2 country SK indoor ecm authmode WPA2/802.11i
privacy ON deftxkey UNDEF AES-CCM 3:128-bit txpower 30 bmiss 7
scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7
roam:rate 5 protmode CTS wme burst roaming MANUAL
# /usr/src/tools/tools/ath/athstats/athstats -i ath0
4228 data frames received
818 data frames transmit
3tx frames with an alternate rate
126 long on-chip tx retries
29480mib overflow interrupts
24M current transmit rate
730 tx frames with short preamble
210 rx failed 'cuz of bad CRC
18 rx failed 'cuz of PHY err
18 CCK restart
10 periodic calibrations
-0/+0TDMA slot adjust (usecs, smoothed)
37 rssi of last ack
37 avg recv rssi
-96 rx noise floor
90 tx frames through raw api
1spur immunity level
1first step level
9ANI increased spur immunity
2ANI decrease spur immunity
103 ANI enabled OFDM weak signal detect
4ANI disabled OFDM weak signal detect
102 ANI disabled CCK weak signal threshold
3ANI increased first step level
7392282 cumulative OFDM phy error count
34526cumulative CCK phy error count
20 ANI forced listen time to zero
126 missing ACK's
291 bad FCS
2928 beacons received
39 average rssi (beacons only)
37 average rssi (all rx'd frames)
37 average rssi (ACKs only)
Antenna profile:
[0] tx 817 rx 65
[1] tx0 rx 4163
I say almost because that small WiFi-LED doesn't blink as it should. Is there
any way to fix this? I see these sysctls:
dev.ath.0.softled: 0
dev.ath.0.ledpin: 0
dev.ath.0.ledon: 0
dev.ath.0.ledidle: 2700
but I'm lost with them :)
regards
michal
On 25.1.2012, at 4:46, Adrian Chadd wrote:
Sure, can you please:
* compile with the following options:
options ATH_DEBUG
options AH_DEBUG
options ATH_DIAGAPI
* compile /usr/src/sys/tools/tools/ath/athstats/
* run athstats -i ath0 and email them to me + freebsd-wirel...@freebsd.org
Thanks!
Adrian
On 24 January 2012 04:01, Michal Vančo mva...@di-vision.sk wrote:
Hi there,
I've installed 9.0-STABLE (also tried on 9.0-RELEASE) on my Thinkpad T60 and
I'm not able to use WiFi. Kernel is GENERIC.
pciconf -lv:
ath0@pci0:3:0:0:class=0x028000 card=0x0033168c chip=0x0024168c
rev=0x01 hdr=0x00
vendor = 'Atheros Communications Inc.'
device = 'AR5008 Wireless Network Adapter'
class = network
relevant part of rc.conf:
wlans_ath0=wlan0
create_args_wlan0=country SK
ifconfig_wlan0=WPA DHCP
and wpa_supplicant.conf:
ctrl_interface=/var/run/wpa_supplicant
network={
ssid=XXX
psk=XXX
}
dmesg just fills with ath0: device timeout messages and wifi just doesn't
work.
any clue?
regards
michal
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Making world but no kernel
On Tue, 2011-07-26 at 13:04 +0200, Jerome Herman wrote: Hello, I would like to know if it is possible to rebuild world, but without upgrading or even compiling the kernel. The problem is such : I am presently working on a FreeBSD station that seems to have quite a lot of problem, notably with fsck. I am starting to wonder whether this BSD station was properly installed, or if some of the system tools were pasted from older FreeBSD setup. Since the machine is in a remote location, I would prefer to avoid full reinstall if possible. Among other things, single user mode is not available. So I was wondering, if I get the full sources with sysinstall, can I make buildworld and then installworld without going through the kernel phase or would this be a bad idea ? Thanks for your help Jerome Herman `make buildworld installworld` won't build and install new kernel at all, so that basically answers your first question. You'd need to use `make buildworld installworld kernel` for that effect. To answer your other concern - reinstalling FreeBSD on the fly should be without any issues as long as you use the right src revisions corresponding to your current system (and kernel). Mixing worlds and kernels of different revisions should *mostly* work if there were no ABI changes during that time period, but you probably don't want trying this blindly without any means of recovery. Basically - it's doable, but I wouldn't do it with just a single shot on my disposal. Note that you don't necessarily need to install a new kernel in single user mode. While this is generally a good practice and a safer way to do things, I haven't even done this for half a decade, and I'm re/installing FreeBSD builds practically on a daily basis. My advice: Personally, I'd consider it much safer to roll a new build of kernel along with the world, but again, that's just me. As you're already fully rebuilding a possibly broken installation (which you didn't do and thus don't know everything that might be rotting inside), chances of some magical failure are already pretty decent. Rolling an up-to-date kernel with the rest of the world shouldn't make them any lower, on the opposite, might even raise your chances of a successfull reboot. m. PS: Whatever that means, please don't get your sources through sysinstall, that monster shouldn't even be present in a seriously maintained FreeBSD installation. Get your sources the proper way with csup: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html (note - csup, not cvsup, it's explained on the page in detail) -- Michal Varga, Stonehenge (Gmail account) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Making world but no kernel
On Tue, 2011-07-26 at 16:28 +0200, Jerome Herman wrote: PS: Whatever that means, please don't get your sources through sysinstall, that monster shouldn't even be present in a seriously maintained FreeBSD installation. Get your sources the proper way with csup: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/cvsup.html (note - csup, not cvsup, it's explained on the page in detail) Well since I am not upgrading, but just making sure things are where they should be I figured that sysinstall was OK for the job. Any problems with sysinstall ? I have been quite happy with it in the 10+ years I have been using FreeBSD. Well, that depends. Probably every single time I've seen someone touching sysinstal in a post-install environment, that OS was instantly rendered as much as good for a complete reinstall. It's just one of those things that shouldn't be present in any rescue scenario. Anyway - I can't comment on the specific procedure you're going to employ through sysinstall as I haven't even physically seen that thing for years (and as far as I know, it has been finally nuked from orbit for the upcoming FreeBSD 9 release), but it wasn't even being actively developed for those past 10 years you mention (I might be exaggerating a bit, but it has been a well known fact for years that sysinstall is an unmaintained rotting mess, which in turn recently led to it being finally replaced). Using csup was just an advice to make yourself perfectly sure about the outcome. It's very easy to point your supfile to - *default release=cvs tag=RELENG_8_2 (that's the vanilla release I understand you need to rebuild) - and be 100% sure about what's going to happen and what sources you're going to get. Upgrading or not, that plays no role in this scenario, as csup is just a way of getting a specific source tree, no matter how you're going to use it later. Basically, I wouldn't trust sysinstall with installing FreeBSD for a start, and surely not with a recovery procedure where you have exactly 0 tries left in case you fail. So I'm just pointing that out. m. -- Michal Varga, Stonehenge (Gmail account) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Making world but no kernel
On Tue, 2011-07-26 at 08:34 -0700, Chuck Swiger wrote: On Jul 26, 2011, at 8:19 AM, Michal Varga wrote: Well, that depends. Probably every single time I've seen someone touching sysinstal in a post-install environment, that OS was instantly rendered as much as good for a complete reinstall. It's just one of those things that shouldn't be present in any rescue scenario. I've been using sysinstall at dozens of customer sites since the 1990's without ever once running into a problem resembling what you've described. Considering the absence of specific details, I think you're exaggerating well past the point of credibility. This is an opinion you're entitled to and I have no particular need to start proving you otherwise. As far as my concerns go, you're free to update your source trees by whatever means that suit you best, I was just pointing the OP a possible point of failure that is easy to avoid by a simple and easily controlled procedure, as there is perfectly nothing that can go wrong with csup. A vital part of any one-shot rescue operation is minimizing things that may go wrong, beforehand. Sysinstall is everything but 'minimal'. Anyway, if someone does something bad using sysinstall and needs to fix it, restoring from backups should be all that is needed. When people talk about doing a complete reinstall, it implies to me that they don't have backups in the first place. Yes, and interestingly this is, in my own experience, very common among people who use sysinstall to manage their systems (usually only about once or twice). Regards, m. -- Michal Varga, Stonehenge (Gmail account) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Best way to switch from Linux to BSD
On Wed, 2011-03-30 at 16:26 +0200, Oliver Pinter wrote: http://hup.hu/node/94286 ;) 1. $ portinstall -v www/epiphany $ epiphany http://www.youtube.com/html5; $ epiphany http://www.youtube.com/watch?v=XBH1dcHoL6Y; 2. $ portinstall -v multimedia/quvi multimedia/mplayer $ cat ~/bin/streamvid quvi -f best $1 --exec mplayer -prefer-ipv4 %u 12 /dev/null $ streamvid http://www.youtube.com/watch?v=XBH1dcHoL6Y; 3. $ portinstall -v multimedia/cclive $ cclive -f best http://www.youtube.com/watch?v=XBH1dcHoL6Y; m. -- Michal Varga, Stonehenge (Gmail account) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Best way to switch from Linux to BSD
On Wed, 2011-03-30 at 10:17 -0700, Charlie Kester wrote: On Wed 30 Mar 2011 at 08:10:23 PDT Michal Varga wrote: On Wed, 2011-03-30 at 16:26 +0200, Oliver Pinter wrote: http://hup.hu/node/94286 ;) 1. $ portinstall -v www/epiphany $ epiphany http://www.youtube.com/html5; $ epiphany http://www.youtube.com/watch?v=XBH1dcHoL6Y; Firefox4 is now in ports, and also supports html5. Only partially. Firefox supports only Google's WEBM video codec for political reasons, completely ignoring the major one - H.264 (sure, there is Ogg Theora too, but nobody uses that). So Firefox's usefulness on HTML5 video is at this moment very limited. I picked Epiphany in my example as it uses gstreamer backend for HTML5 video and thus plays everything that gstreamer has codecs for, which is basically everything. m. -- Michal Varga, Stonehenge (Gmail account) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Best way to switch from Linux to BSD
As with other people that replied before - my opinions reflect my opinions that might actually *not* suit your personal needs. But you asked. On Tue, 2011-03-29 at 01:32 -0400, Jason Hsu wrote: Some questions: 1. Is it possible to install KDE, GNOME, or other DE from the FreeBSD CD in a reasonable amount of time? KDE and GNOME are huge programs, and having to download them would take too long. I feel that this was alwas the case, so yes as far as I know (haven't been installing any stock off-the-disc FreeBSD recently). But I can hardly imagine any FreeBSD power user (what a silly term that is anyway) that doesn't want to build his own, *proper* and properli fine-tuned FreeBSD. If prebuilt packages are what you're looking for, you are most probably not looking for FreeBSD, but something like a PC-BSD or a similar toy. FreeBSD is, to help you draw a comparison, very close to the Gentoo of the Linux world. Hope that clears some things up. 2. What's lighter than PCBSD and GhostBSD? I tried the live DVDs on my laptop (1.4 GHz processor, 1.25 GB of RAM) and found both BSD distros to be very sluggish. Ubuntu and Mint were faster and fit on a CD, and these two distros have been criticized as bloatware. Also, the keyboard didn't work in GhostBSD. Deploy your own fine tuned FreeBSD (not that there is any other way to properly use FreeBSD in a single/home configuration anyway). After that, build and install the ports you need, properly configure them (both compile-time and run-time). There is nothing more lighter, adn faster, you could ever get from anywhere. Comparison with the monstrous bloatware the kind of Ubuntu and Mint is really silly, probably comparison with ArchLinux cold still hold somehow, but even that's a borderline case. The comparison you're looking for again is Gentoo. Also somewhat more opinionated piece: Get a real desktop computer. Seriously. You don't want to build your own ports/packages on a 1.4GHz laptop, or at least, not for too long (pun intended). 3. How do I triple-boot Puppy Linux, antiX/Swift Linux, and DragonflyBSD? I'm not sure that's the best question for a FreeBSD mailing list, or at least, I'm not able to anwser to that. 4. What are the Linux Mint and Puppy Linux of the BSD universe? I consider these two distros to set the standard in the Linux universe, because they're so user-friendly. These are the distros I've set out to compete against in developing Swift Linux. None, there is no Windows Vista equivalent for a FreeBSD world. Again - if that's what you're looking for instead of a hand-built and fine-tuned operating system, you're much better with systems like PC-BSD. FreeBSD won't do you much good and only hinder you in this case. FreeBSD is an amazing desktop OS (which I say as an exclusive FreeBSD desktop user for a decade, so I probably even have a little bit of experience in that field, in contrast with 'some' other specific people that replied to you before me), but only If you're looking to put what FreeBSD offers into good use (that is, for a start - a solid, clean, polished and very modular and maintaineable OS). But the feel I get from your questions is that you're really looking for a magical Windows Vista clone, but with a magical BSD sticker that will magically raise your horse power just by the sheer magical power of its own awesomeness. It really doesn't work that way. I mean, seriously - Linux Mint? (Yes, and sadly, I know it well, but I'm somewhat baffled that you might be actually looking for that *again* in a BSD world, like if the Linux version wasn't enough for a lifetime). So honestly, In that case, for the love of god, at least get a proper Mac. Because that's what you're in fact looking for. m. (Disclaimer: I'm in no way trolling and everything I wrote is completely dead serious.) -- Michal Varga, Stonehenge (Gmail account) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Best way to switch from Linux to BSD
a lumbering 7-legged dinosaur the stock FreeBSD is and why it needs to be cleansed with fire, first, and repeatedly. Additionally, using compiler optimization doesn't seem to be that recommended anymore, since it can break code, thus leading to nasty results. I wouldn't agree there. The basic O2 is perfectly safe for ages now (O3 not so, *but* depends on your time and resources to put into testing and possible troublesolving, and even then you might still turn out to be a winner in most cases in the end). Processor specific optimizations are a must too, otherwise you don't even need the fancy new one with the latest SE9-THIS-TIME-IN-STEREO, when your plan is to keep using just the raw i386 out of it, that's like buying a latest state-of-the-art sportbike and for the rest of the life keep dragging it tied behind a Pinto. Which is why several developers state in their trouble shooting guide to rebuild their application with default settings before opening a bug report. This further decreases the benefit of compiling everything from scratch. State. Several developers are simply lazy and nobody pays them to debug someone elses issues. Keeping it simple and unified saves anyone's time, but mostly theirs. I personally support this approach and everyone sane should. [I snipped a large part because this is getting seriously way too long, but I agree with many of your points there, so now just to one more thing...] On the downside there seem to be some work needing to be done IRT kernel based 3D acceleration. I don't know the current status, but the last I heard was that NVidias drivers can't be ported to FreeBSD because the kernel lacks some functionality required (something related to addressing the graphics board directly from software, AFAIK). Nvidia has 100% support on FreeBSD (not comparable to their Windows/Linux support, but great nevertheless): http://www.nvidia.com/object/freebsd-x86-260.19.44-driver.html http://www.nvidia.com/object/freebsd-x64-260.19.44-driver.html Nvidia's drivers on FreeBSD are pure complete awesome sauce and they would cook you a dinner if you asked them to, and clean up in the morning afterwards. (No, really, I don't work for Nvidia and I'm probably years away from any possibilities for fanboy-ishms, but this is how it really is.. So you are mistaken, Nvidia single handedly saved FreeBSD on desktops many years ago and does it till present times, over and over. No, they're not that much into charity, but some of their corporate customers run FreeBSD, so this is the outcome, and it's pretty good). So if you want the latest features and eye candy (say, KDE4s Plasma) and make heavy use of xcompmgr, there might be better choices. Don't believe that (see above). m. -- Michal Varga, Stonehenge (Gmail account) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Best way to switch from Linux to BSD
On Tue, 2011-03-29 at 11:43 -0500, Paul Schmehl wrote: FreeBSD is first and foremost a server OS. Could you support your claim with some examples, please? Desktop support is lacking when compared to the other major OSes (Windows, Mac and Linux). Here too. How is desktop support on FreeBSD lacking? You can make it work, if you want to, but that's not what its primary function is. Where can I find some detailed information about what is FreeBSD's primary funtion and what does that even mean in the first place? If you want a user friendly desktop OS, FreeBSD is probably not your best choice. Why? How is KDE, Gnome, XFCE or some potential other desktop environment different from the literally exactly same one running on, say, Linux? m. -- Michal Varga, Stonehenge (Gmail account) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Best way to switch from Linux to BSD
On Tue, 2011-03-29 at 10:51 -0700, Matthew Fleming wrote: On Tue, Mar 29, 2011 at 10:27 AM, Michal Varga varga.mic...@gmail.com wrote: Here too. How is desktop support on FreeBSD lacking? I realize a desktop means many things to many people, but the biggest thing holding me back from using FreeBSD on a desktop is flash support. I spent a little time trying to follow online instructions and I didn't get anything working. Lack of Flash support - a proprietary closed exploit-ridden hellhole - sorry, I mean - application - that's in no way tied to FreeBSD and controlled by a legendarily uncompetent company that blantantly refuses to release a FreeBSD version of this very fine and awesome rootkit (a good decision that one can only support, so really, what's the issue) is hardly something that could even remotely be FreeBSD's fault. I mean, this is what we're talking about: http://secunia.com/advisories/search/?search=adobe+flash But even in a completely hypothetical scenario where Flash wouldn't be the world's most famous never-ending exploit carnival in the entire existence of the universe, how that makes FreeBSD less desktop friendly or less desktop capable? Adobe decided to not release their software on FreeBSD (again, thank you Adobe, that's a thousand less attack vectors daily to worry about), but there is no issue with FreeBSD with regard to that, isn't it? This isn't the case that FreeBSD broke the Flash (ok, this isn't funny anymore), there was never any FreeBSD Flash in the first place. So no FreeBSD issue exists, or at least I can't see it, or maybe I simply don't get something here. There is also no Microsoft Windows Management Console for FreeBSD, does it make FreeBSD lacking, insufficient, or broken in some specific server area? m. -- Michal Varga, Stonehenge (Gmail account) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: FreeBSD partitioning
On Tue, 2011-03-22 at 16:24 -0500, Jason Hsu wrote: How does partitioning work in FreeBSD? GParted recognizes FAT16, FAT32, NTFS, ext2, ext3, ext4, swap, and many other formats but labels the FreeBSD partition as unknown. Then there are the sub-partitions within the main FreeBSD partition. I'm finding it much more difficult to learn BSD than it was to learn Linux. However, I'm sure it will be worth it, as BSD is legendary for stability and is the basis for Mac OS and other proprietary systems. http://www.freebsd.org/doc/handbook/install-steps.html Note that you don't actually need sysinstall to work with FreeBSD partitions at all (but you need a working FreeBSD for that, obviously). The handbook page will give you a very good step-by-step overview on how freebsd *partitions* and *slices* work and what they generally stand for. In fact, shortly after you get a grip on the basics, you will start hating sysinstall completely (this is guaranteed) and never ever use it again (continue with man fdisk, man bsdlabel after that). But first, read the mentioned handbook section carefuly - from that on, you should find partitioning in FreeBSD very easy and intuitive. m. -- Michal Varga, Stonehenge (Gmail account) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
ZFS and Storage Systems
Morning, Apologies for the basic question but I just want to make sure. I have been looking at storage systems like this one http://www.icc-usa.com/storage-35-2u.asp. I am guessing it would be a case of sorting the discs out, probably on some GUI or command line for the box it self, then using a FreeBSD box I can set up ZFS over the drives...or is it not that simple? Thanks Chris ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: ZFS and Storage Systems
It would be even better to simply ask them what exact Supermicro hardware (specifically, model numbers) they're using to build these systems. You can see Supermicro mentioned in thetitle of their site, so that's definitely what they're using, even down to the controller card offerings (some of which (Marvell) are known to behave oddly on FreeBSD (yes there are success stories, but there are also follow-up horror stories) -- consider yourself warned). I think the best option is to just build it your self using similar components which I have looked at before. My ideal is build a system where you can extend the storage easily by adding another box instead of either replacing the HDD's with bigger HDD's or having multiple targets for the data. One target whose storage can be expanded by simply adding another box. However, that is harder in practice to work out ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Extending your zfs pool with multiple devices
What is really odd is I see your replies but not my original post, how very strange?? Thank you for all of your assistance. I would like to move to being able to build a cheap san-like storage area for a DB, I don't know how well it would work but I'd like to try it anyway since things like HP MSA's are hugely expensive. I like these suggestions of filling a second box and connecting this to the 1st box using these expanders and port replicators. I don't really need as fast as I can get as this is not a high-use DB backend or many user file server. A few users here and there but nothing that worries me about the bottleneck caused by these replicators. This way is ALOT better then my system of trying to export iscsi disks or something like that. This way I can add create a second box then have a cable into an expander or replicator on the 1st box, a 3rd box could then be added to the expander/replicator at a later date. There is a limit on how far this could go realistically, but I like this way. I could go further by adding SSD's for the L2ARC and ZIL if I wanted to. I found zfsbuild.com to be a quite nice site/blog Thanks for all your help ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Tuning the scheduler? Desktop with a CPU-intensive task becomes rapidly unusable.
On Fri, 2010-09-03 at 14:03 -0500, Jim Bryant wrote: i just noticed this too... had a build going of qt-creator, and then started a /usr/src make clean, and had to abort the qt-creator build to get the make clean to finish. it was taking forever to even paint the xterm in the make clean window. This has been the state of -stable for at least an year, I have yet to see a 7-stable machine that doesn't exhibit this behavior. This wasn't the case with 7 in the very beginning and only started slowly building up over time, particularly around the time of one specific xorg import - which one it was? 7.4? I guess. Every bit of performance went down the drain hole by that time and it's on that same level ever since (it's rather easy to get used to it while working on a 7-stable desktop, but would be nice having the old pre-ULE performance levels back, sometime). On the other hand, at least from some of my observations, the terrible desktop performance isn't strictly CPU-bound, I/O definitely has some say in this. You can (you should, mileage may vary) see this by trying to extract a few-GB archive in the background. While clearly no more than a single CPU is ever occupied by that process (and there's few other happily idling), you can spend waiting up to a few minutes just to get a new application launched (or even just a running one getting redrawn, in case part of it was swapped out at the moment). But as I said, for 7-stable, this has been the case for a veery long time. m. -- Michal Varga, Stonehenge (Gmail account) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Extending your zfs pool with multiple devices
I have a small problem that I am trying to work out a solution for. Imagine you create a NAS box. Fill a small server with 5 hard drives, zfs them with raidz or whatever, create your pools and then shear this to the network using samba. Simple NAS box for your network to put their files and they just connenct to \\nas1 This box is now full, my problem is that I could create a 2nd NAS box and people use \\nas1 and \\nas2 but it's not very use friendly. Can I somehow build a 2nd box which is identicle, but extend my pools into nas2. I was thinking something like exporting the nas2 drives via iscsi and then nas1 add's the drives to the pool...or something similar. I find that with any NAS whether its home build or shop bought you will eventually run out of space, and sure you can replace the HDD's with bigger ones but you will see run out of space, and having multiple locations, in my mind, is not very elegant. I cannot simply add more HDD's to the box as well as it's at full capacity Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Unable to boot FreeBSD 8.0-p3
I am currently running memtest86 here on my livecd. If there is no error, then this could be something else. I've seen memtest pass but it still be a RAM problem. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Unable to boot FreeBSD 8.0-p3
On 01/07/2010 17:20, GNUbie wrote: Hello Jeremy, On Fri, Jul 2, 2010 at 12:15 AM, Jeremy Chadwick free...@jdc.parodius.com wrote: Simple: replace the RAM, file for an RMA, etc.. If there's no warranty or the warranty has expired and you need brand recommendations for a new purchase: Crucial is excellent, avoid Corsair at all costs. I'm using Kingston and it's still less than a year since I bought this RAM. I have to ask the shop where I bought this RAM and hopefully they will replace it. Regards, GNUbie You can file an RMA with kingston if you have the serial number (I think) it should be on the sticks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Adding a second device to my zfs pool
I am having problems getting my head around a small ZFS issue. If I build a fileserver, say for example a 20 x 1TB disk server with zfs and create a file server, it can work fine and I can have RADIZ or RAIDZ2 or whatever. I could create 4 groups of 5 1TB HDD's and do all things like that...It's shared using iSCSI or samba or whatever, desktops and servers can see the files, everything works fine. But one day I run out of space, so I think right, build an exact copy of the one I have so I have another 20 TB server, given me 40TB, but I want nothing to change for the desktops/servers and as far as they know nothing as happened. But my problem is I could set that second server up, but how do I add the space to my existing pools? I create my RAIDZ2 zpools of hard drives, the raid works and everything, but now I want to increase my existing storage. I could go to my first server and simply add the storage to my groups, thus increasing the size...but then if that server fails I will lose all data? will I not? Basically I'm having trouble finding information on what happens when you add a second file server to increase your space. I see lots of guides and documents for 1 device and adding more HDD's to that device, but not when you need to add a second device (run out of HDD space in the device for example) Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: *BSD meetup, London May 27th
On 16/05/2010 20:27, Owain Ainsworth wrote: On Sat, May 15, 2010 at 11:38:34PM +0100, Edd Barrett wrote: On Tue, May 11, 2010 at 1:44 PM, Sevan / Venture37 ventur...@gmail.com wrote: Hi Guys Some of us are meeting at the Barrowboy Banker by London bridge on the 27th this month, 7pm More details here: http://mailman.uk.freebsd.org/pipermail/ukfreebsd/2010-May/012735.html Sevan / Venture37 Anyone considering this? Sure, why not. -0- Yeah I'm hoping to ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
iscsi, zfs, RAIS = Cheap SAN...maybe
*I apologise about the length of this e-mail, I tried to cover all details*
I am following up on a previous post which is here
http://unix.derkeiler.com/Mailing-Lists/FreeBSD/stable/2010-03/msg00392.html
The sum up my end goal is this;
To have a SAN type system where I have multiple servers that contain
multiple disks. I can lose a server and due to RAID1 across the servers,
the data will still be on the network, IO will increase due to their
being multiple servers to read from simultaneously as opposed to one NAS
box and lastly to be able to add new servers to the system to increase
the storage (to the end users the amount of available space increases).
Stage one is to create a two server system that can take a failure of a
server. Second stage is to get better IO from two servers then from one
NAS box. Last stage is to have all that and the ability to easily add
more storage
I have created 3 (not great spec just some spear) servers, two of which
have 2 HDD's each and I will call storedevice1 and storedevice2 these
are my devices that will hold the data. My 3rd server is my controller
which controls the devices. Each server has two hard drives which using
iscsi-target I export as data0 and data1 and in the controller I use the
iscsi-initiator to connect to these 4 HDD's. Here is the config files
storedevice1:
#cat /usr/local/etc/iscsi/targets
# extents filestart length
#extent0/tmp/iscsi-target0 0 100MB
extent0 /data0/data 0 28GB
extent1 /data1/data 0 28GB
# targetflags storage netmask
target0 rw extent0 192.168.2.0/24
target1 rw extent1 192.168.2.0/24
# ls -lh /data0/
total 2195442
drwxrwxr-x 2 root operator 512B Apr 20 17:49 .snap
-rw-r--r-- 1 root wheel 28G May 5 21:37 data
# ls -lh /data1/
total 2195442
drwxrwxr-x 2 root operator 512B Apr 22 13:27 .snap
-rw-r--r-- 1 root wheel 28G May 5 21:37 data
storedevice2:
#cat /usr/local/etc/iscsi/targets
# extents filestart length
extent2 /data0/data 0 28GB
extent3 /data1/data 0 28GB
# targetflags storage netmask
target2 rw extent2 192.168.2.0/24
target3 rw extent3 192.168.2.0/24
# ls -lh /data0/
total 2191250
drwxrwxr-x 2 root operator 512B Apr 22 15:09 .snap
-rw-r--r-- 1 root wheel 28G May 5 21:37 data
# ls -lh /data1/
total 2191250
drwxrwxr-x 2 root operator 512B Apr 22 17:40 .snap
-rw-r--r-- 1 root wheel 28G May 5 21:37 data
which gives me 4 extents and 4 targets accross both. /dataX/data is a
file which I think it needs to be (???)
On my controller I have;
OffSanCtrl1# cat /etc/iscsi.conf
offsan0 {
TargetName = iqn.1994-04.org.netbsd.iscsi-target:target0
TargetAddress = 192.168.2.160:3260,1
}
offsan1 {
TargetName = iqn.1994-04.org.netbsd.iscsi-target:target1
TargetAddress = 192.168.2.160:3260,1
}
offsan2 {
TargetName = iqn.1994-04.org.netbsd.iscsi-target:target2
TargetAddress = 192.168.2.161:3260,1
offsan3 {
TargetName = iqn.1994-04.org.netbsd.iscsi-target:target3
TargetAddress = 192.168.2.161:3260,1
}
which is my initiator and connects to my 4 targets
Up to this point I think I am doing everything correctly. I then setup a
zpool on the controller
OffSanCtrl1# zpool status
pool: store0
state: ONLINE
scrub: none requested
config:
NAMESTATE READ WRITE CKSUM
store0 ONLINE 0 0 0
mirrorONLINE 0 0 0
da1s1d ONLINE 0 0 0
da3s1d ONLINE 0 0 0
mirrorONLINE 0 0 0
da2s1d ONLINE 0 0 0
da4s1d ONLINE 0 0 0
errors: No known data errors
with da1s1d and da2s1d being from storedevice1 and da3s1d and da4s1d
from storedevice2 so if I am correct this should be a a sort of RAID10
(anything that could be done better please tell me).
I now set-up zfs on this zpool (again, I think I'm doing this the right way)
OffSanCtrl1# zfs list
NAME USED AVAIL REFER MOUNTPOINT
store04.12G 50.5G19K /store0
store0/users 4.12G 50.5G 4.12G /store0/users
Lastly, I need to be able to allow network users/servers to connect to
this. My choices I think are iscsi and samba as I have *nix and windows
machines, so I'll try iscsi. From the controller, create a target from
the zfs mount point I have created. If I am correct, a user should be
able to connect to the target from the controller, write data which will
actually be writing data across both storedevice's
OffSanCtrl1# cat /usr/local/etc/iscsi/targets
# extents filestart length
extent0 /store0/users/data 0
Re: Multi node storage, ZFS
On 25/03/2010 08:54, Patrick M. Hausen wrote: Hi, all, On Wed, Mar 24, 2010 at 11:45:25PM +, Michal wrote: I am thinking a cheap solution but one that has IO throughput, redundancy and is easy to manange and expand across multiple nodes Fast, reliable, cheap. Pick any two. IMHO this is just as true today as it was twenty years ago. Best regards, Patrick I will never get what you would get by spending a lot of money, by doing it on the cheap. But yes I agree to a certain extent, it's still expensive and out of the SMB reach If you want an appliance, a Sun/Oracle 7000 series may be close: http://www.oracle.com/us/products/servers-storage/storage/open-storage/ The 7310 allows for two active-active heads, with fail over if one dies. Does NFS, SMB/CIFS, and iSCSI; the newest software release (2010.Q1) gives SAN functionality so you can export LUNs via FC if you purchase the optional HBAs. There are cheaper options yes I agree, but I think even that might be out of my budget. I've been fighting for months. Time is ok as a factor, learning it only helps me in the long run so it's win win for me. I, too, am still unsure how Oracle buy out will effect Sun...I'm not optimistic though...I'm expecting to move off MySQL at some point, when I don't know but I think I will be forced to for some reason or another ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Multi node storage, ZFS
I wrote a really long e-mail but realised I could ask this question far far easier, if it doesn't make sense, the original e-mail is bellow Can I use ZFS to create a multinode storage area. Multiple HDD's in Multiple servers to create one target of, for example, //officestorage Allowing me to expand the storage space when needed and clients being able to retrieve data (like RAID0 but over devices not HDD) Here is an example I found which is where I'm getting some ideas from http://www.howtoforge.com/how-to-build-a-low-cost-san-p3 Any pointers would be helpful, Thanks - I've been searching around and I am finding myself confused and reading conflicting information. I would like to build a Storage system where by I have multiple nodes. At the minute I have a number or NAS's which work well and RAID6 works well in the situation we have, but unfortunately it's a short-term solution I inherited and once you crunch the numbers of 6 devices with 6 HDD's in RAID6 you realise how much space you have wasted then say, 1 device of RAID6 with 36 HDD's (the saving is a fair few TB) There are other issues as well, increasing the size, 3rd party NAS device features missing which other storage devices have...etc so I looked around and my grand idea was basically this; Build a system where I can have multiple nodes which create one target (we will use //officestorage for our example) as opposed to //nas1/ which is of course 1 device. Using multiple nodes will allow us to add a new device, thus increasing the space available but the target will always be the same and to the client nothing has change (other then available space) (Think of this as RAID0). Multiple nodes will also allow for redundancy across devices (think RAID1) and give better IO as it's multiple devices and not just 1 device. I could have devices in different locations so a whole building could burn down and still not lose the data After looking around I found this https://help.ubuntu.com/community/HighlyAvailableAoETarget Which looks quite good, it's basically RAID1 but instead of HDD's it's across servers, I've used DRBD and it worked well, but this doesn't give me better IO as only 1 device is live. I then found this http://www.howtoforge.com/how-to-build-a-low-cost-san-p3 Which looks fantastic, though I will need a master server to create the RAID0 and RAID1 across the multiple nodes and then share this out, which is ok but I would need a hot swap master server, so I'm looking at two of those. I then started thinking about ZFS, I've heard lots of good things about it in the past and thinking can ZFS do what I want. I have read some things which say it can do what that 2nd link does and others which say it can't. Everything I come across is about using just 1 device and I could build 1 device with DRBD, but that doesn't help, nor will it allow me to expand it (if your server runs out of physical space you can't add more HDD's. Anyone point me in the right direction?? Thanks ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Multi node storage, ZFS
On 24/03/2010 16:20, Freddie Cash wrote: Horribly, horribly, horribly complex. But, then, that's the Linux world. :) Yes I know, it's not very clean, but was trying to gather ideas and I found that Server 1: bunch of disks exported via iSCSI Server 2: bunch of disks exported via iSCSI Server 3: bunch of disks exported via iSCSI SAN box: uses all those iSCSI exports to create a ZFS pool Use 1 iSCSI export from each server to create a raidz vdev. Or multiple mirror vdevs. When you need more storage, just add another server full of disks, export them via iSCSI to the SAN box, and expand the ZFS pool. And, if you need fail-over, on your SAN box, you can use HAST at the lower layers (currently only available in 9-CURRENT) to mirror the storage across two systems, and use CARP to provide a single IP for the two boxes. - This is pretty much what I have been looking for, I don't mind using a SAN Controller server in which to deal with all of this in fact I expected that, but I wanted to present the disks from a server full of HDD's (which in effect is just a storage device) and then join them up. I've briefly looked over RAIDz, will give it a good reading over later. I'm thinking 6 disks in each server, and two raidz vdev created from 3 disks in each server. I can them serve them to the network. I've never used ISCSI on FreeBSD however, I played with AOE on different *nix's so I will give ISCSI a good looking over. Yes, you save space, but your throughput will be horribly horribly horribly low. RAID arrays should be narrow (1-9 disks), not wide (30+ disks), and then combined into a larger array (multiple small RAID6 arrays joined into a RAID0 stripe). Oh Yes I agree, was doing some very crude calculations and the difference in space was quite a lot, but no I would never do that in reality If you were to do something like this, I'd make sure to have a fast local ZIL (log) device on the head node. That would reduce latency for writes, you might also do the same for reads. Then your bulk storage comes from the iSCSI boxes. Just a thought. I've not come across ZIL so I think I will have to do my research At least in theory you could use geom_gate and zfs I suppose, never tried it though. ggatec(8), ggated(8) are your friends for that. Vince Just had a look at ggatec, I've not seen or heard of that so I will continue looking through that. Many thanks to all, if I get something solid working I will be sure to update the list with what will hopefully be a very cheap (other then HDD's) SAN ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Multi node storage, ZFS
On 24/03/2010 17:14, Freddie Cash wrote: Yes, that would be helpful (mirrored slogs, until we get slog removal support). As would an L2ARC (cache) device in the head node. As well as lots and lots and lots of RAM. And as fast of ethernet NICs as you can get between the head node and the storage nodes. And, and, and, and ... :) As far as I know more RAM is more important the fast CPU, so RAM is the order of the day, and I guess it depends what you think fast CPU is, but I wasn't planning on a duel CPU or anything top of the range. I have some duel core's knocking around...I think testing will show how good/bad my calculations/assumptions are. Most are done in batched, nightly and weekly so extremely fast isn't THAT important as we are looking at device/server backup's and stored data which is moved off servers once a week. At the minute we are not looking at 100 user file system or anything along those lines. For NICS I can sort out a Gb switch or some point-to-point Gb connections betweeen the nodes, there is also the option is trying getting some cheap fibre cards (I have a few laying around) and a cheap fibre switch (something off ebay for testing might do) to have fibre between the nodes. This however all goes out the water for trying to do replication to other sites which are 100mb lines, but for the minute I will focus on 1 location to stop it getting too complex. There are quite a lot of hardware things which need to be done correctly, and yes I do need to look at lots of other things. But stage one is just getting a few Storage devices talking to a Storage controller and seeing if my ideas work (improve IO, improved redundancy, easy to add storage) Michael, I sort of understand what you are talking about with ZIL, but not completely, so thanks for the pointers, there are clearly things I have not thought about. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Multi node storage, ZFS
On 24/03/2010 22:19, Ivan Voras wrote: For what it's worth - I think this is a good idea! iSCSI and ZFS make it extraordinarily flexible to do this. You can have a RAIS - redundant array of inexpensive servers :) For example: each server box hosts 8-12 drives - use a hardware controller with RAID6 and a BBU to create a single volume (if FreeBSD booting issues allow, but that can be worked around). Export this volume via iSCSI. Repeat for the rest of the servers. Then, on the client, create a RAIDZ. or if you trust your setup that much. a straight striped ZFS volume. If you do it the RAIDZ way, one of your storage servers can fail completely. As you need more space, add more servers in batches of three (if you did RAIDZ, else the number doesn't matter), add them to the client as usual. The client in this case can be a file server, and you can achieve failover between several of those by using e.g. carp, heartbeat, etc. - if the master node fails, some other one can reconstitute the ZFS pool ad make it available. But, you need very fast links between the nodes, and I wouldn't use something like this without extensively testing the failure modes. I do aswell :D The thing is, I see it two ways; I worked for a a huge online betting company, and we had the money for HP MSA's and big expensive SAN's, then we have a lot of SMB's with no where near the budget for that but the same problem with lots of data and the need for backend storage for databases. It's all well and good having 1 ZFS server, but it's fragile in the the sense of no redundancy, then we have 1 ZFS server and a 2nd with DRBD, but that's a waste of money...think 12 TB, and you need to pay for another 12TB box for redundancy, and you are still looking at 1 server. I am thinking a cheap solution but one that has IO throughput, redundancy and is easy to manange and expand across multiple nodes A NAS based solution...one based on a single NAS device which has single targets //nas1 //nas2 etc is ok, but has many problems. A SAN based solution can overcome these, it does add cost, but the amount can be minimised. I'll work on it over the next few days and get some notes typed up as well as some run some performance numbers. I'll try and do it modular by adding more RAM and sorting our ZLS and cache, comparing how they effect performance ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: suspend to disk
On Tue, Feb 9, 2010 at 12:13 AM, Christof Schulze christof.schu...@gmx.com wrote: Hello everyone today I tried whether my samsung q35 laptop would suspend using acpiconf on RELENG_8. I was amazed that acpiconf -s3 works out of the box. However acpiconf -s4 does not work which would be the useful side of hibernation for me. http://www.freebsd.org/projects/acpi/ Excerpt: suspend to disk -- Implement a suspend/resume from disk mechanism. Possibly use the dump functions to dump pages to disk, then use ACPI to put the system in S4 or power-off. Resume would require changes to the loader to load the memory image directly and then begin executing again. -- Not done. Did anything change in recent years? m. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Multiple serial consoles via null modem cable
On 12/01/2010 16:08, Jeremy Chadwick wrote: On Tue, Jan 12, 2010 at 05:14:44PM +0200, Marin Atanasov wrote: Hello there, I'd like to ask you about the following - is it possible to have multiple serial consoles coming from a single host? What I am talking about is connecting multiple machines using a null modem cable - I know it is possible only to connect two machines and they need to be connected on sio0 (COM1). I'm thinking about the following situation - 1 system acting like a host with a serial port hub, each port of the hub is connected to a different machine on sio0, using null modem cables. This would make the first machine something like a cheaper kind of a terminal concentrator :) What do you think, have someone tried this and is it possible at all? What you're describing is basically the concept of a serial console server, where a FreeBSD box contains a multi-port serial card that's connected to multiple other servers. An individual would get on the FreeBSD box with a multiport serial card (see below) and attach to the serial port associated (wired to) whatever other box they want to log on to. Yes this is possible with FreeBSD -- but you'll need to purchase a multiport serial card that's supported natively by FreeBSD. The two I'm familiar with are Cyclades and DigiBoard, but this would've been back in the day of FreeBSD 2.2.x and I've no idea what people use present-day. I'm certain others here can recommend stuff that works. snip You've actually mentioned one here, Digi. They make console devices and I've used, with great success. Ours had modems as well so we had a normal TCP and a phone line for DR. There is a range of sizes, SSH2 and some have 2 psu's. They have American as well as European providers, though I can't remember where we purchased ours from. We didn't use ours on servers however, they where just for switches, routers, load balancers et al so I can't comment on how well they worked with those, but I can't see it being any different. http://www.digi.com/products/consoleservers/digicm.jsp ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: RELENG_7 changes for rc.d/named
On Fri, Jan 1, 2010 at 8:58 PM, Doug Barton do...@freebsd.org wrote: Oliver Lehmann wrote: Hi, since my last RELENG_7 update a new rc.conf variable named_conf appeared. How is this supposted to work with a chroot named? I guess not at all? I realize that you're frustrated and upset, so I will disregard the mildly obnoxious tone of your message, and this comment in particular. FWIW, I have been maintaining BIND bits in FreeBSD for 9 years. I have 15 years experience as a DNS administrator, and have donated literally hundreds of hours to make the default BIND configuration conform to best practices in terms of both security and operations. Your suggestion that I've simply foisted some untested crap onto the FreeBSD community is at best, rude. At worst, it's just plain stupid given that named is chroot'ed by default, and has been for years. I'm sorry to put it this way, Doug, as I (as many other people around) really value the work you do for FreeBSD and for all of us. But in this case, your whole reply seems like you are just randomly punching a guy out of some (external?) frustration, only because he was, well, in the wrong place at the wrong time. From what I see (but well, I may be nobody to judge that, after all) in OP's quite polite and nonconfrontational original mail, he is just confused by the recent changes and is raising a question. On the other hand, you take it rather personally with all that OMG you think I would ever do that?! How dare you! Burn the witch! tone. I don't know, it may be just me, but wouldn't be a simple No sir, you are wrong. It's your configuration that doesn't work in this setup, please see here: I say created for yourself because the default configuration directory in FreeBSD (and I believe most/all of the other *BSDs too) is /etc/namedb, not /etc/named. [...] etc, etc, somewhat more constructive here? Sure, you eventually did that in the end, but only after you gave him a father-to-child scolding speech for, well, I can't really see for what reason, or how the guy deserved that for raising a simple question. Anyway, just my two cents. Keep up the good work, and, again, please, don't take it rather personally. m. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Most files in subversion stable/8/sys touched by bms
On Tue, Dec 29, 2009 at 7:37 PM, Oliver Fromme o...@lurza.secnetix.de wrote: By the way, here is another little tool that can be used to watch changes in 8-stable conveniently: http://www.secnetix.de/olli/FreeBSD/svnews/?p=stable/8/sys Thank you for mentioning this, this is a great tool for everyone to have around (instantly bookmarked). I'd have one question to ask - would you consider adding one more piece of information to the output, namely age of the commit? So that 17:38:50 - r201208 by rwatson would look like: 17:38:50 - r201208 (17 hours, 30 minutes old) by rwatson or 17:38:50 - r201208 (3 days, 15 hours old) by rwatson etc. Little extra like this makes tracking down some specific changes easier, or makes some quick point of reference where you left the last time, etc. I guess you get the idea.. It's not exactly critical, just would be handy to see there, if possible :) m. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: Phoronix Benchmarks: Waht's wrong with FreeBSD 8.0?
O. Hartmann wrote: I'm just wondering what's wrong with FreeBSD 8.0/amd64 when I read the Benchmarks on Phoronix.org's website. Especially FreeBSD's threaded I/O shows in contrast to all claims that have been to be improoved the opposite. oh This all reminds me of a few releases ago MySQL performance being terrible. I guess this is still the same? We've had arguments internally weather certain machines are FreeBSD like some existing or Linux like other existing as Linux always out-performed by miles. We never tested these using on OpenBSD however, so I don't know if that had the same problem... ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: atacontrol spindown equivalent for ahci/ada
Arnaud Houdelette wrote: Is there a equivalent command (camcontrol something ... ?) to atacontrol spindown when using ahci(4) ? I'd like to continue using this feature to reduce power consumption during night hours. Arnaud ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org someone even wrote a script. Search the OpenBSD archives ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: /bin/sh core dumps on FreeBSD 7.2
Ivan Voras wrote: Hans F. Nordhaug wrote: Hi! Suddenly /bin/sh started to crash all the time with core dumps. I'm running FreeBSD 7.2-RELEASE-p4 (i386) and I have not updated anything lately. The /bin/sh binary seems to be untouched. It might be some hardware trouble, but the machine seems to run OK now. (I had to replace /bin/sh with a symlink to /rescue/sh.) I would like to track down the problem, but running sh I only get Segmentation fault: 11 (core dumped). I would be happy to run gdb and give you a backtrace. Any clues? Hans PS! I tried to run freebsd-update IDS to see if any files are broken, but it stops at Inspecting system... sha256: ///boot/kernel/utopia.ko.symbols: Input/output error All of this points to a hardware problem. Last time I saw things like this it was either a hard drive on the way out, or a PSU dying. Run some pre-OS tests (Ultimate boot cd or something) to try and get some results outside of the OS I think the best thing you can try is to manually get a hash fingerprint of your sh and compare it with another, known good copy. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
UVNC Repeater
Good afternoon, I am having a few niggly problems setting up a VNC repeater on my FreeBSD box and I am finding it very hard to find any information anywhere. I freshly installed FreeBSD on the box today and updated ports and system. I then make make build make install /usr/ports/net/repeater/ and made a few customer modifications to the uvncrepeater.ini script, I supplied it bellow. I also set-up the UVNC single click app, it was very simple while I testing, also supplied bellow. When I run the listener on my PC, I see these errors in the repeater.log file (please note IP address's have been changed, but they are public) UltraVnc Wed Oct 14 15:29:30 2009 acceptConnection(): connection accepted ok from ip: 1.2.3.4 UltraVnc Wed Oct 14 15:29:31 2009 findServerList(): server not found (code = 7001) So when my tester outside my network starts the single click and tries to connect, it just fails. Has anyone seen this, or point me in the right direction?? Many Thanks Chris helpdesk.txt (for singleclick.exe) --- [TITLE] UltraVnc SC [HOST] Internet support -connect 1.2.3.10:5500 -noregistry -id 7001 uvncrepeater.ini [general] ;Ports viewerport = 5900 serverport = 5500 ;Repeater's own ip address in case your server happens to have several ;ip addresses (for example, one physical machine running several virtual ;machines each having their own ip address) ;default (0.0.0.0 = INADDR_ANY = uses all addresses) is the same that ;older repeater versions (before 0.12) did -- listens to all interfaces ;Notice ! This IS NOT address of server or viewer, but repeater itself ! ownipaddress = 1.2.3.10 ;How many sessions can we have active at the same time ? ;values can be [1...1000] ;Notice: If you actually *have* computer(s) capable ;of 1000 simultaneous sessions, you are probably a *very big company*, ;so please invite me to visit and admire your server(s) ;-) maxsessions = 100 ;If program is started as root (to allow binding ports below 1024), ;it changes to this user after ports have been bound in startup ;You need to create a suitable (normal, non-privileged) user/group and change name here runasuser = uvncrep ;Allowed modes for repeater ;0=None, 1=Only Mode 1, 2=Only Mode 2, 3=Both modes ;Notice: If you set allowedmodes = 0, repeater will run without listening to any ports, ;it will just wait for your ctlr + c ;-) allowedmodes = 3 ;Logging level ;0 = Very little (fatal() messages, relaying done) ;1 = 0 + Important messages + Connections opened / closed ;2 = 1 + Ini values + exceptions in logic flow ;3 = 2 + Everything else (very detailed and exhaustive logging == BIG log files) logginglevel = 2 [mode1] ;0=All allowedmode1serverport = 0 ;0=Allow connections to all server addressess, ;1=Require that server address (or range of addresses) is listed in ;srvListAllow[0]...srvListAllow[SERVERS_LIST_SIZE-1] requirelistedserver = 0 ;List of allowed server addresses / ranges ;Ranges can be defined by setting corresponding number to 0, e.g. 10.0.0.0 allows all addresses 10.x.x.x ;Address 255.255.255.255 (default) does not allow any connections ;Address 0.0.0.0 allows all connections ;Only IP addresses can be used here, not DNS names ;There can be max SERVERS_LIST_SIZE (default 50) srvListAllow lines srvListAllow0 = 10.0.0.0;Allow network 10.x.x.x srvListAllow1 = 192.168.0.0 ;Allow network 192.168.x.x ;List of denied server addresses / ranges ;Ranges can be defined by setting corresponding number to 0, e.g. 10.0.0.0 denies all addresses 10.x.x.x ;Address 255.255.255.255 (default) does not deny any connections ;Address 0.0.0.0 denies all connections ;Only IP addresses can be used here, not DNS names ;If addresss/range is both allowed and denied, it will be denied (deny is stronger) ;There can be max SERVERS_LIST_SIZE (default 50) srvListDeny lines srvListDeny0 = 10.0.0.0 ;Deny network 10.x.x.x srvListDeny1 = 192.168.2.22 ;Deny host 192.168.2.22 [mode2] ;0=Allow all IDs, 1=Allow only IDs listed in idList[0]...idList[ID_LIST_SIZE-1] requirelistedid = 0 ;List of allowed ID: numbers ;Value 0 means this authenticates negatively ;If value is not listed, default is 0 ;Values should be between [1...LONG_MAX-1] ;There can be max ID_LIST_SIZE (default 100) idList lines idlist0 = 7000 idlist1 = 7001 idlist2 = 7002 idlist3 = 7003 idlist4 = 7004 idlist5 = 7005 idlist6 = 7006 idlist7 = 7007 idlist8 = 7008 idlist9 = 7009 [eventinterface] ;Use event interface (for reporting repeater events to outside world) ? ;This could be used to send email, write webpage, update database etc. ;Possible values: true/false useeventinterface = false ;Hostname/Ip address + port of event listener we send events to eventlistenerhost = localhost eventlistenerport = 2002 ;Make HTTP/1.0 GET request to event listener (instead of normal write dump) ;Somebody wanted this for
RE: Open Vs Free BSD
-Original Message- From: owner-freebsd-sta...@freebsd.org [mailto:owner-freebsd-sta...@freebsd.org] On Behalf Of Charlie Kester Sent: 19 June 2009 20:24 To: freebsd-stable@freebsd.org Subject: Re: Open Vs Free BSD On Fri 19 Jun 2009 at 11:23:26 PDT Michael R. Wayne wrote: OK, I'm going to take a guess here that English may not be Michal's primary language and re-ask his question: Given the several versions of *BSD, I have been led to understand that each excells in different ways. How do I select which one is right for my application, what are the underlying reasons that would lead me to that choice and what are the the disadvantages I am risking? This is, actually, not an inappropriate question coming from a potential new user who is not familiar with the history surrounding the various versions and would make an outstanding FAQ. As an example, we run FreeBSD on our firewalling machines because it works well enough and we prefer the reduced support costs of using a single O/S across our network. I am unsure of what the advantage of moving to OpenBSD might be and would find it very difficult to quantify the advantages (if any) versus the increased support resources required. This is a very real issue. Linux has a similar problem; I've personally been in meetings where clients examined the myriad Linux distributions and say It's very likely that we will make the incorrect choice. So we'll go with Windows. I suspect similar events have occurred with *BSD. So, rather than jumping on people about them bringing up religous wars (because, face it, you CAN edit a file perfectly well in either vi or emacs :-), we'd all be better served by giving them enough information to make the right choice in their situation while realizing the tradeoffs they are making. I agree, this shouldn't necessarily be treated as flamebait or trolling. But shouldn't the question be redirected to the advocacy mailing list/team? -- Sorry, I would just like to add that English is my first and only language. As I said at a Terremark Europe meeting, (everyone else spoke [mostly] Dutch and English, I speak English and bad English. I think my dyslexia and general ignorance may have caused the confusion in my question. I was never asking WHO WINS WHO WINS, as I have multiple OS's running, more looking forward 2-5 years, upgrades and so forth, what should I take in to account. From the answers I have got, I've learn that I should ask my questions better, most importantly I think there, and OBSD may not have lots of packages but it has brilliant security. A desktop might be served better with Linux of FreeBSD, but at the end of the day, it's your horse, your course. You choose as you wish. I thank you all ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Open Vs Free BSD
Someone once said this too me Comparing FreeBSD and OpenBSD, FreeBSD is generally better at disk-related I/O whereas OpenBSD handles net-I/O better. No test has been carried out to prove this though. Every offence to the person which said this, but they are not the best admin ever, though they like to think they are (the worst kind I think) Can anyone shed any light, the reason I ask is we where debating about a network and he said OpenBSD on the network (routers firewall etc) and FreeBSD as the app servers (mail, files etc etc), which I can see makes sense.but without having evidence it's pointless making a claim. Thanks :-) ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
RE: Open Vs Free BSD
It wasn't an argument or a versus anything. It was just a question relating to what he had said and the truth in it and the two OS's being used for different reasons. That's all. No rage, no debate or looking for any winner! -Original Message- From: owner-m...@openbsd.org [mailto:owner-m...@openbsd.org] On Behalf Of dem...@thephinix.org Sent: 19 June 2009 12:42 To: freebsd-stable@freebsd.org; m...@openbsd.org Subject: Re: Open Vs Free BSD Oh why can't this versus this versus that never dies? There had been raging debate about which OSes is much better compared to the others since time immemorial. Sure, each one has its own merits over the others and vice versa. So why feeding this issue up since up to this very moment, there is no winner. and the security is in netbsd: http://netbsd.gw.com/cgi-bin/man-cgi?security+8+NetBSD-5.0 http://www.netbsd.org/~elad/recent/recent06.pdf On 6/19/09, Ivan Voras ivo...@freebsd.org wrote: Kim Attree wrote: NetBSD runs on just about anything. That's it's primary goal. Since I don't have any weird hardware, I've never had a use for NetBSD. I don't use NetBSD either but some recent development that come from that camp are very interesting: * Journalling UFS (smart journalling, not gjournal) * PUFFS (BSD implementation of FUSE-like system [file system in userland]) * They had Xen dom0 and domU for years * They are starting to show decent results in SMP support, including a new scheduler (a bit similar to ULE); their GENERIC has SMP included * Possibly superpages, I'm not sure how to parse Merged amd64 and i386 pmap. Large pages are always used if available * I think they are working on their own ZFS port * They have ported or reimplemented Linux LVM (read+write+admin) There are of course other things; see for example http://www.netbsd.org/releases/formal-5/NetBSD-5.0.html I have a feeling the project has been revitalized in the last few years. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: no USB mice detected on GA-MA74GM-S2
On Tue, Apr 14, 2009 at 12:52 PM, Andrew MacIntyre andy...@bullseye.apana.org.au wrote: If it works with the OP's USB mouse, a USB - PS/2 (male) adapter might at least get him running provided that the mobo has a PS/2 port... [...] Guess what :-) http://www.gigabyte.com.tr/images/products/motherboard_productimageback_ga-ma74gm-s2_big.jpg (yes, I know it's not really funny under the circumstances, but still made me chuckle in a way..) m. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: no USB mice detected on GA-MA74GM-S2
2009/4/13 piotr.smy...@heron.pl: Yes, I'm 100% positive I tried plugging mouse after the boot up had finished. Honestly I am late asking here. I was struggling with this and looking for cases online for more than 2 weeks at least. And I came across your thread from 2007, too. That's really bad. Though closest I can find to your board with freebsd people I know is AMD770+SB600, while your is AMD740G+SB700, all of them dating back to my first AMD690G/V (and maybe prior to that) so far exhibited the same symptoms and the late-plug approach always worked.. Yours would be then the first one that Gigabyte botched even more (congrats). I guess that's one more reason to push on USB guys to finally fix it. While I'm not really sure what to propose, maybe starting a new thread Attention Gigabyte owners - speak up! could achieve something. At least I know few of them that never bothered reporting anything, because somebody will fix it eventually, it's a known issue. Maybe it's not that well known for someone to consider it a priority yet.. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: no USB mice detected on GA-MA74GM-S2
2009/4/12 piotr.smy...@heron.pl: On Thu, 9 Apr 2009 12:57:30 +0200, piotr.smyrak wrote On Wed, 8 Apr 2009 22:49:25 +0200, Martin wrote Am Wed, 8 Apr 2009 21:08:05 +0200 schrieb Piotr Smyrak piotr.smy...@heron.pl: I'm overall satisfied with -CURRENT. I've always wanted to say that FreeBSD developers do a really great job on the -CURRENT branch. It's running very stable and has plenty of new features. I know I shouldn't recommend to migrate to -CURRENT, but I'm almost sure, it runs much better than every -CURRENT I've seen before and sometimes I have the impression that it's even nicer than the -STABLE branch. Well, I am not scared by -CURRENT at all, but I was hesitating to upgrade main build since it is after all a moving target and I would like to keep my main work horse as much steady as possible. Sadly this is all I can get out of 8.0-CURRENT as of yesterday. Both with BIOS option for USB mouse support on and off. Don't bother with BIOS settings for USB/keyboard mouse support, they won't help. This is a long standing (bios?) bug for *MANY* Gigabyte motherboards (like this one from 2007: http://lists.freebsd.org/pipermail/freebsd-current/2007-October/078191.html ). A quick workaround is to attach your mouse (or any other USB device that dies during boot - mices, keyboards, card readers, etc. do this with FreeBSD 6/7's usb1 and Gigabyte boards) -after- all USB drivers are loaded and initialized. That always works. Also in one case I know of, having an external powered USB hub 'solved' the issue (if that counts as a fix). Still, having it properly fixed in usb1 drivers wouldn't hurt, of course, but until then, just detach your mouse before boot, plug it after, and you're fine. m. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: no USB mice detected on GA-MA74GM-S2
2009/4/13 piotr.smy...@heron.pl: ). A quick workaround is to attach your mouse (or any other USB device that dies during boot - mices, keyboards, card readers, etc. do this with FreeBSD 6/7's usb1 and Gigabyte boards) -after- all USB drivers are loaded and initialized. That always works. Unfortunately not in my case. I have tried this path before without success. Are you sure you plugged the mouse out, then powered the computer on, and plugged the mouse back in only after FreeBSD fully finished booting? To make it perfectly redundantly safe, let's say, plugged mouse in at the login prompt? Because I'm 100% positive (well, me and everyone else with any recent Gigabyte board that I know) that plugging the device in after the USB drivers are fully initialized will prevent the lockup and port timeout, always. Still, having it properly fixed in usb1 drivers wouldn't hurt, of course, How do you go about that? I mean fixing a device in usb1.1. Well, I guess that would need someone with both FreeBSD USB expertise and some interest in fixing that bug (and probably an access to particular Gigabyte hardware, though as it seems so far, anything recent from Gigabyte and probably AMD6xx/7xx based will do it). Anyway, I tried reporting it back then in 2007, all I got was a bunch of arguments about power source fluctuations, carbon footprints, Windows, PS/2 mices (for christ sake..), and well, being a lazy coward, I gave up. Maybe you'll be luckier this time. m. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: SCHED_ULE + SMP Phenom freeze
On Tue, Mar 10, 2009 at 11:37 PM, Timothy Brown stimbr...@fastmail.com.au wrote: I had the same problem. I searched the FreeBSD problem report database and came across this: http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/120138 After manually applying the patch and recompiling the kernel, I am able to boot with SCHED_ULE and SMP enabled. Cheers, Tim Wow, thank you for this, going to apply in a moment (but I guess it's pretty obvious that this is the same issue and also explains the X3 mystery). Adding Jeff Roberson to cc: to remind about the issue, I think it wouldn't be a bad idea to get this committed eventually. m. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Re: SCHED_ULE + SMP Phenom freeze [SOLVED]
Just a quick success report - kern/120138 does indeed solve the Phenom X3 SCHED_ULE problem. Attached patch against recent -STABLE in case someone else runs into it in the near future: --- sys/kern/sched_ule.c.orig 2008-12-08 05:07:30.0 +0100 +++ sys/kern/sched_ule.c2009-03-11 00:09:43.0 +0100 @@ -1399,7 +1399,7 @@ * prevents excess thrashing on large machines and excess idle on * smaller machines. */ - steal_thresh = min(ffs(mp_ncpus) - 1, 4); + steal_thresh = min(fls(mp_ncpus) - 1, 4); affinity = SCHED_AFFINITY_DEFAULT; #endif } ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
SCHED_ULE + SMP Phenom freeze
Guys, I'd like to point out a still present (rather serious I guess) problem with SCHED_ULE, possibly triggered when Phenom X3 CPUs are used. First time I encountered this problem in early January, it took me quite a while to narrow the freeze down to ULE with SMP support, well, after eliminating every other possibility one by one. After that, it wasn't that hard to find that I'm not the only one seeing this: http://lists.freebsd.org/pipermail/freebsd-stable/2008-August/044167.html http://lists.freebsd.org/pipermail/freebsd-stable/2008-October/045714.html (continued) http://lists.freebsd.org/pipermail/freebsd-amd64/2008-December/011722.html (there were few more with the same symptoms back then, but sadly I can't figure out the right keywords to google them at the moment) Basically, the system can't get past the boot stage with ULE + SMP support in kernel and hangs after SMP: AP CPU #X Launched! (see the linked October thread for details). But it gets better - there are absolutely no problems with either uniprocessor SCHED_ULE, nor SCHED_4BSD (both UP and SMP). No interrupt storms, no suspicious behaviour, no crashes, everything acts rock solid. I've been running this system with SCHED_ULE minus SMP support for more than a month under heavy load, tested SCHED_4BSD minus SMP for a brief moment, and then another month with SCHED_4BSD + SMP. Everything works perfectly and also all three cores behave correctly with 4BSD + SMP. It only gets messy when ULE + SMP combo is used. I was also wondering why only Phenom X3 people report this problem, but this may be just a coincidence, who knows. Still, I'm also one of them: FreeBSD 7.1-STABLE #0: Sat Mar 7 21:37:27 CET 2009 r...@xenon:/usr/obj/usr/src/sys/KERNEL Timecounter i8254 frequency 1193182 Hz quality 0 CPU: AMD Phenom(tm) 8450 Triple-Core Processor (2109.74-MHz 686-class CPU) Origin = AuthenticAMD Id = 0x100f23 Stepping = 3 Features=0x178bfbffFPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,MMX,FXSR,SSE,SSE2,HTT Features2=0x802009SSE3,MON,CX16,POPCNT AMD Features=0xee500800SYSCALL,NX,MMX+,FFXSR,Page1GB,RDTSCP,LM,3DNow!+,3DNow! AMD Features2=0x7ffLAHF,CMP,SVM,ExtAPIC,CR8,b5,b6,b7,Prefetch,b9,b10 TSC: P-state invariant Cores per package: 3 Same as with other reports, with SCHED_ULE + SMP, as soon as I hit the SMP: AP CPU Launched stage, the system is dead. m. ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to freebsd-stable-unsubscr...@freebsd.org
Panic with umass (with USB tape and Amanda)
in umass_bbb_state (xfer=0x0, priv=0xff005bcd8800, err=USBD_NORMAL_COMPLETION) at ../../../dev/usb/umass.c:1626 Residue = 0 next_xfer = 0x0 #17 0x8023a50f in usb_transfer_complete (xfer=0xff007b962000) at ../../../dev/usb/usbdi.c:863 pipe = 0xff005994bb00 dmap = (usb_dma_t *) 0x80517ea0 sync = 0 erred = 0 repeat = 0 polling = 0 #18 0x8022fdb0 in uhci_softintr (v=0x0) at ../../../dev/usb/uhci.c:1374 sc = (uhci_softc_t *) 0x866ad000 ii = (uhci_intr_info_t *) 0x0 nextii = (uhci_intr_info_t *) 0x0 #19 0x8022faab in uhci_intr1 (sc=0x866ad000) at ../../../dev/usb/uhci.c:1274 status = 1 ack = 1 #20 0x80267269 in ithread_loop (arg=0xff007b9de540) at ../../../kern/kern_intr.c:682 ie = (struct intr_event *) 0xff029800 __func__ = Óc\200Óc\200˙ #21 0x8026606b in fork_exit ( callout=0x80267121 ithread_loop, arg=0xff007b9de540, frame=0xb197ac50) at ../../../kern/kern_fork.c:821 p = (struct proc *) 0xff007b6c5a08 #22 0x8036e77e in Xapic_isr3 () at apic_vector.S:134 I can probably provide some more information, possibly even trying to reproduce it on similar system (this one is in production). Thank you Michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
em(4) interface freezing on 6.2
Hello, I have got Dell PowerEdge 750 with on-board em(4) network cards and I use it as a router. The interface em0 stops forwarding traffic from time to time. Resetting the interface with ifconfig down up fixes the problem. [EMAIL PROTECTED]:1:0: class=0x02 card=0x01651028 chip=0x10758086 rev=0x00 hdr=0x00 vendor = 'Intel Corporation' device = '82547EI Gigabit Ethernet Controller' class= network subclass = ethernet em0: Intel(R) PRO/1000 Network Connection Version - 6.2.9 port 0xece0-0xecff mem 0xfe2e-0xfe2f irq 18 at device 1.0 on pci1 em0: Reserved 0x2 bytes for rid 0x10 type 3 at 0xfe2e em0: Reserved 0x20 bytes for rid 0x18 type 4 at 0xece0 em0: bpf attached em0: Ethernet address: 00:14:22:7a:1c:10 ioapic0: routing intpin 18 (PCI IRQ 18) to vector 49 em0: [MPSAFE] I am running RELENG_6_2, with CARP. PF with traffic normalization is active (scrub in all fragment reassemble). I have tried turning off checksum offload. When the interface does not pass traffic it looks normal in ifconfig(8). ARP does not work and nothing interesting get written to the logs. em0: flags=8943UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST mtu 1500 options=bRXCSUM,TXCSUM,VLAN_MTU inet 192.168.1.8 netmask 0xfff0 broadcast 192.168.1.15 ether 00:14:22:7a:1c:10 media: Ethernet autoselect (1000baseTX full-duplex) status: active The machine is processing couple of megabits worth of traffic all the time and it takes anywhere from an hour to more than a day to occur. I had about 10 interface freezes on em0 interface but none on em1. When I put additional network card into the machine (xl(4)) and use it together with em1 it works without a problem. The only difference between em0 and em1 there I can think of is that there may be some out-of-band management functions in the em0 which driver does not correctly turn of or something. I have noticed a small update to the driver in -STABLE but I don't think this could fix my issues. Due to the nature of the problem and use of the machine I am afraid I can not do much to help narrow the problem further down. Thank you Michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em, bge, network problems survey.
Kris Kennaway wrote: On Fri, Oct 06, 2006 at 08:54:35AM +0200, Michal Mertl wrote: Kris Kennaway wrote: On Wed, Oct 04, 2006 at 05:14:27PM -0600, Scott Long wrote: All, I'm seeing some patterns here with all of the network driver problem reports, but I need more information to help narrow it down further. I ask all of you who are having problems to take a minute to fill out this survey and return it to Kris Kennaway (on cc:) and myself. Thanks. 1. Are you experiencing network hangs and/or timeout messages on the console? If yes, please provide a _brief_ description of the problem. OK, next question, to all em users: If your em device is using a shared interrupt, and you are NOT experiencing timeout problems when using this device, please let me know. I haven't seen any timeout message in long time but I experience frozen network (and also the already reported panic when doing ifconfig down/up then). Are these details in a PR? I don't know. As I have seen somebody else reporting the same issue (even with backtrace) and the problem was believed to be understood I dind't pay much attention, sorry. I have also seen strange problem which may be completely unrelated: When doing 'find . -ls' on SMB mounted drive - find was spitting the contents of the drive but never finishes. Network seemed dead but when I interrupted find with Ctrl-C I got the replies to the pings sent when it was running (e.g. thousands ms) - this looks like something was preventing RX to work and the packets were just queued somewhere. I belive I should be able to easily reproduce it. genius# vmstat -i interrupt total rate irq0: clk 43784465 1000 irq1: atkbd0 66248 1 irq5: pcm0 5877 0 irq8: rtc5603682128 irq9: acpi0 8820 0 irq11: fwohci0 em*205749 4 irq12: psm0 586848 13 irq14: ata0 340844 7 irq15: ata1 61 0 Total 50602594 1155 I don't think I remember debug.mpsafenet tunable being mentioned in the threads about the problems. It prevents all the problems on my system (UP non-APIC system), including the SMB issue mentioned above. I suspect both of your problems are some unrelated issue. I'd need root access a test setup before I can say more though. It is possible, but your patch to change INTR_FAST to INTR_MPSAFE seems to help with both of these too. I am planning to try to reproduce the SMB temporary network lockup (with original CURRENT driver) and probably do a panic then to get a core. Michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: em, bge, network problems survey.
Michal Mertl wrote: Kris Kennaway wrote: On Wed, Oct 04, 2006 at 05:14:27PM -0600, Scott Long wrote: All, I'm seeing some patterns here with all of the network driver problem reports, but I need more information to help narrow it down further. I ask all of you who are having problems to take a minute to fill out this survey and return it to Kris Kennaway (on cc:) and myself. Thanks. 1. Are you experiencing network hangs and/or timeout messages on the console? If yes, please provide a _brief_ description of the problem. OK, next question, to all em users: If your em device is using a shared interrupt, and you are NOT experiencing timeout problems when using this device, please let me know. I forgot to note I am running fresh current, not stable. I haven't seen any timeout message in long time but I experience frozen network (and also the already reported panic when doing ifconfig down/up then). I have also seen strange problem which may be completely unrelated: When doing 'find . -ls' on SMB mounted drive - find was spitting the contents of the drive but never finishes. Network seemed dead but when I interrupted find with Ctrl-C I got the replies to the pings sent when it was running (e.g. thousands ms) - this looks like something was preventing RX to work and the packets were just queued somewhere. I belive I should be able to easily reproduce it. genius# vmstat -i interrupt total rate irq0: clk 43784465 1000 irq1: atkbd0 66248 1 irq5: pcm0 5877 0 irq8: rtc5603682128 irq9: acpi0 8820 0 irq11: fwohci0 em*205749 4 irq12: psm0 586848 13 irq14: ata0 340844 7 irq15: ata1 61 0 Total 50602594 1155 I don't think I remember debug.mpsafenet tunable being mentioned in the threads about the problems. It prevents all the problems on my system (UP non-APIC system), including the SMB issue mentioned above. Michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel panic with PF
Max Laier píše v pá 21. 07. 2006 v 02:05 +0200: [CC'ing -pf] On Thursday 20 July 2006 17:53, Michal Mertl wrote: Hello, I am deploying FreeBSD based application proxies' based firewall (www.kernun.com, but not much English there) and am having frequent panics of RELENG_6_1 under load. The server has IP forwarding disabled. I've got two machines in a carp cluster and the transparent proxies use PF to get the data. Which proxies are you using? The pool_ticket: 1429 != 1430 messages you quote below indicate a synchronization problem within the app talking to pf via ioctl's. Tickets are used to ensure atomic commits for operations that require more than one ioctl. If your proxy app runs in parallel it might screw up the internal state and thus leave it undefined afterwards. I give you that this shouldn't cause a kernel problem, but if we could fix the app we can probably find the right sanity check more easily. The proxy in fact runs in parallel (according to pfctl -s info it did about 50 inserts and removal in the state table per second - some 10Mbit of traffic, probably mostly HTTP) and it is quite possible that your explanation is correct. I will forward your suspicion to the vendor. This functionality of the software (using PF with anchors) is quite new - they used different mechanisms in previous versions so it may well have some bugs. Thanks Michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel panic with PF
Daniel Hartmeier wrote: On Fri, Jul 21, 2006 at 02:05:45AM +0200, Max Laier wrote: Which proxies are you using? The pool_ticket: 1429 != 1430 messages you quote below indicate a synchronization problem within the app talking to pf via ioctl's. Tickets are used to ensure atomic commits for operations that require more than one ioctl. If your proxy app runs in parallel it might screw up the internal state and thus leave it undefined afterwards. I give you that this shouldn't cause a kernel problem, but if we could fix the app we can probably find the right sanity check more easily. This looks like a bug in pf_ioctl.c pfioctl() DIOCCHANGERULE if (newrule-action == PF_NAT) || (newrule-action == PF_RDR) || (newrule-action == PF_BINAT) || (newrule-rt PF_FASTROUTE)) - !pcr-anchor[0])) + !newrule-anchor)) (TAILQ_FIRST(newrule-rpool.list) == NULL)) error = EINVAL; i.e. the pool must not be empty for routing and translation rules, except for translation rules that are actually anchor _calls_. The confusion is between translation rules within anchors (pcr-anchor[0] != '\0') and calls to anchors' translation rules (rule-anchor != NULL). If the proxy is using DIOCCHANGERULE (it must be the proxy, pfctl isn't using it at all), AND is trying to add/update a rule that requires at least one replacement address but contains an empty list, then this would cause the panic seen when that rule later matches a packet. This needs fixing in OpenBSD as well. Michal, can you please confirm that the patch above fixes the panic? The proxy will still misbehave and cause the log messages (one more EINVAL in this case ;), but the kernel shouldn't crash anymore. I am afraid I can't test it at the moment. I am going to get one of the machines to my lab and will experiment with it there. I am afraid I will have problems generating enough traffic for the problem to appear but I will try. Thanks for the excellent bug report! Thank you. I don't think is was that good as I now see that you had to guess there are anchors used. The rules look like this (except the rules seen by 'pfctl -s nat' they are generated by the proxies when they start): fw1#pfctl -s rule fw1#pfctl -s nat nat-anchor /kernun/* all rdr-anchor /kernun/* all fw1#pfctl -s Anchors -v kernun kernun/4026 kernun/4039 kernun/4088 kernun/4112 kernun/4134 kernun/4164 kernun/4197 kernun/4257 kernun/4296 kernun/4338 kernun/4383 kernun/4431 kernun/4482 kernun/4590 kernun/4649 fw1# pfctl -a kernun/4039 -s nat rdr on em0 inet proto tcp from any to any port = http label HTTP - 127.0.0.1 When the system was under load I saw ~5000 states in 'pfctl -s state'. Thank you again. I will let you know when I get a chance to test your patch and or find out anything new. Michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel panic with PF
Daniel Hartmeier wrote: On Fri, Jul 21, 2006 at 10:57:28AM +0200, Michal Mertl wrote: The proxy in fact runs in parallel (according to pfctl -s info it did about 50 inserts and removal in the state table per second - some 10Mbit of traffic, probably mostly HTTP) and it is quite possible that your explanation is correct. I will forward your suspicion to the vendor. This functionality of the software (using PF with anchors) is quite new - they used different mechanisms in previous versions so it may well have some bugs. Anchors were introduced for this purpose, i.e. splitting the ruleset into separate pieces, over each of which a single process can have authority, so different processes don't stomp on each other's toes with ruleset modifications. They (the Kernun authors) run multiple processes for each proxy. Originally they used slightly modified Apached core for their proxies I believe. Thus there are probably more processes using the same anchor. I don't really understand what they do inside - I would think that when there are no traffic blocking rules, there's no point in doing anything with PF except initial setting of the rdr rule to the proxy. Ask them if they really need to still use DIOCCHANGERULE, as the idea with anchors is generally to only operate within one anchor, and usually flush or replace the (smaller) ruleset within. Each anchor has its own ticket, so if you're seeing ticket mismatches, that means there are concurrent operations on the same anchor, even. I see. It would be better if they were part of this communication because I don't know the internals (although I have the source code). I have problems reaching them at the moment though. Daniel ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Kernel panic with PF
#19 0x8053020e in fork_trampoline () at ../../../amd64/amd64/exception.S:394 #20 0x in ?? () The firewall also reports lots of PF problems durings operation: Jul 20 10:44:11 fw1 kernel: Jul 20 10:44:11 fw1 HTTP[7607]: KERN-100-E [natutil.c:770] ioctl(): Invalid argument (EINVAL=22) Jul 20 10:44:11 fw1 kernel: Jul 20 10:44:11 fw1 HTTP[7607]: NATT-111-E add_rule(): PF ioctl DIOCADDRULE failed Jul 20 10:44:11 fw1 kernel: Jul 20 10:44:11 fw1 HTTP[7607]: NATT-701-E addnatmap out(): Adding TCP NAT MAP from [127.0.0.1]:60860 to [212.80.76.13]:80 - [193.179.161.10]:60860 failed Jul 20 10:44:11 fw1 kernel: Jul 20 10:44:11 fw1 HTTP[7607]: NETL-210-E netbind(server,10): NAT binding failed Kernel often reports pool_ticket: 1429 != 1430 (with increasing numbers over time). Thank you very much for any advice. Regards Michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Kernel panic with PF
Michael Proto wrote: Michal Mertl wrote: Hello, I am deploying FreeBSD based application proxies' based firewall (www.kernun.com, but not much English there) and am having frequent panics of RELENG_6_1 under load. The server has IP forwarding disabled. I've got two machines in a carp cluster and the transparent proxies use PF to get the data. I don't know much about kernel internals and PF but from the following backtrace I understand that the crash happens because rpool-cur on line 2158 in src/sys/contrib/pf/net/pf.c is NULL and is dereferenced. It probably shouldn't happen yet it does. The machines are SMP and were running SMP kernel. The only places where pool.cur (or pool-cur) is assigned to are in pf_ioctl.c. It seems there are some lock operations though so it is probably believed that the coder is properly locked. I have been running with kern.smp.disabled=1 for a moment before I put the old firewall in place and haven't seen the panic but the time was deffinitely too short to make me believe it fixes the issue. Can setting debug.mpsafenet to 0 possibly also help? ... Are you using user and/or group rules in your PF ruleset? If so, then you will want to set debug.mpsafenet to 0 as its a known issue with pf(4) currently. Thank you. No, I am not using it and I am quite sure the proxies aren't doing it behind my back either. In fact there isn't a single entry in the rules tables - there are only rdr rules generated on the fly by the proxies. I will try to set this (in addition to running UP) to see whether it helps anyway. Thanks Michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Temperature monitoring in FreeBSD 4/5/6
O. Hartmann wrote: O. Hartmann schrieb: Roland Smith schrieb: On Thu, Mar 16, 2006 at 07:22:14PM -0500, Stephan Koenig wrote: Does anyone know of an easy way to get temperature information out of a Dell PowerEdge 1550/1650/1750/1850/2650/2850 running FreeBSD4/5/6? Something that has a very simple CLI that just outputs the temperature without any formatting, or a library/sysctl, would be ideal. /usr/ports/sysutils/mbmon If you want an additional X frontend, try /usr/ports/sysutils/xmbmon Roland This port does not work for me on any DELL Optiplex GX270/280 and 820 around here. Especially on GX270/280 I tried every knob of the port I found without a positive result. Oliver It does also not work on ASUS A8N32-SLI due to an unsupported chipset. O. On one machine where mbmon doesn't report anything useful lmmon does. HTH Michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Page fault, GEOM problem??
Johan Ström wrote: Hi! On 18 nov 2005, at 18.43, Xin LI wrote: Hi, Johan, large snip So, it seems it does run savecore after running dumpon and mounting disks etc... Is that wrong? No, this is normal. When you run savecore you need to have mounted filesystems. In order to mount the filesystems they may have to be checked. The fsck program requires big amount of memory to check larger filesystems so the swap has to be enabled. Core dumps are written to the dump device (swap) from the end whereas the swap is normally used from the beginning (or the other way around). Therefore there's quite a big chance that, even when the swap has to be used for fsck, the core dump is intact and usable. If the usage of the swap file by fsck corrupts the core dump you may start after next crash in single user mode and run the commands manually (without enabling swap). As to why you can write kernel core dumps only to certain devices the answer is that at the time, when the kernel is dumping core, it is usually in pretty bad state, kernel internals may be corrupted and so on. The dumping code is therefore written to be quite low level so that even wedged kernel can be dumped. The dumping code is part of hard disk controller's drivers. The gmirror is quite high-level device and geom itself needs working scheduler so there will probably never be a way to dump on gmirror provided swap. When you issue the dumpon command the check is performed whether the driver for the disk you want to dump on supports kernel core dumps. Michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Page fault, GEOM problem??
Parv wrote: in message [EMAIL PROTECTED], wrote Michal Mertl thusly... Johan Ström wrote: On 18 nov 2005, at 18.43, Xin LI wrote: ... So, it seems it does run savecore after running dumpon and mounting disks etc... Is that wrong? No, this is normal. When you run savecore you need to have mounted filesystems. In order to mount the filesystems they may have to be checked. The fsck program requires big amount of memory to check larger filesystems so the swap has to be enabled. Core dumps are written to the dump device (swap) from the end whereas the swap is normally used from the beginning (or the other way around). Therefore there's quite a big chance that, even when the swap has to be used for fsck, the core dump is intact and usable. Is there any formula to calculate the size of swap to account for fsck core dump while assigning swap size (short of having two swap partitions)? None that I know of. Someone posted to some FreeBSD mailing list some figures about the fsck consumption of memory. I really don't remember, but I think it was something like some MBs of memory per quite a lot of GB of file system space. E.g. that the fsck on normally sized file systems (e.g. at most a couple of hundred GB) doesn't normally cosume all of normally sized memory (=256MB) and thus doesn't need to swap. If the usage of the swap file by fsck corrupts the core dump you may start after next crash in single user mode and run the commands manually (without enabling swap). Is that after kernel (re)boots? And would the commands to be executed be savecore followed by swapon? If the dump got corrupted by fsck, you would have to wait for another crash and dump. Then you would reboot and start in single user mode, repair the file systems without swap enabled (fsck would crash on the large file system(s)) and then run savecore. Swapon is then irrelevant, you probably don't need swap for savecore. After running savecore you can start normally multi user (exit from the single user shell). I didn't try all of that but I believe it should work. Michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: upgrading 5.4 - 6.0 without reinstalling. safe ?
On Wed, 9 Nov 2005, Ronald Klop wrote: 7. reboot into single-usermode and verify your new kernel works How do you reboot into single-usermode from remote? (Rebooting isn't really the problem, working in single-usermode is.) /etc/ttys # If console is marked insecure, then init will ask for the root password # when going to single-user mode. http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/boot-init.html#BOOT-SINGLEUSER -- Michał 'max' Marciniak felix.fizyka.amu.edu.pl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Routes not deleted after link down
On Sunday 19 June 2005 10:29, Gleb Smirnoff wrote: On Sat, Jun 18, 2005 at 10:14:32PM +0200, Jose M Rodriguez wrote: J Second, you may need a route daemon for this. ospf is a well known J canditate where convergence in case of lost link is a must. While an OSPF daemon may stop advertising the affected route to its neighbors, the kernel will still have the route installed and thus the box won't be able to contact other hosts on the connected net, while they are reachable via alternate pass. Routing protocol should be responsible for removing affected routes from FIB. For example quagga should remove all routes learned via particular ospf neighbour when that neighbour is not reachable anymore due to link goes down. But in case when no daemons are used (`static' and `connected' are also `routing protocols'), kernel should be responsible for doing that. I've checked that Cisco routers remove route from FIB when interface link goes down. I haven't checked Junipers yet. Junipers do the same. It is the only feasible behaviour for router. From my viewpoint, removing route (or marking it unusable) is a correct behavior for router. Not sure it is correct for desktop. Sure. My vote is that we should implement this functionality and make it switchable via sysctl. I'd leave the default as is. Agree. pgp8nMK3Ubf8W.pgp Description: PGP signature
Routes not deleted after link down
Hi, i discovered that routes are not deleted from routing table after link on interface goes down. For example: netstat -rnf inet | grep bge0 default10.1.14.1 UGS 0 135968 bge0 10.1/17link#1 UC 00 bge0 route -n monitor got message of size 96 on Sat Jun 18 15:10:38 2005 RTM_IFINFO: iface status change: len 96, if# 1, link: down, +flags:UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST netstat -rnf inet | grep bge0 default10.1.14.1 UGS 0 136011 bge0 10.1/17link#1 UC 00 bge0 Should't all routes via bge0 be deleted after link on bge0 goes down? thanks michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Routes not deleted after link down
On Saturday 18 June 2005 20:48, Chuck Swiger wrote: Michal Vanco wrote: i discovered that routes are not deleted from routing table after link on interface goes down. For example: [ ... ] Should't all routes via bge0 be deleted after link on bge0 goes down? Maybe. If the system was not going to be reconnected to that network anytime soon, it would be a good idea. On the other hand, if the link down was due to a transient failure of a wireless connection, which will be back up in a second or two, it's much better not to drop the route and kill any open connections. hmm ... this approach is may be appropriate for deskop instalation. what about internet router? shouldn't fast convergence be better in this case? imagine two links connected to the same router with different metrics. if first of them goes down, the second never gets used in this case. michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
MS USB Wireless Mouse
Hi, my problem with %subj% continues. Recently I have forced ums to detect it as mouse but there are still some weird things. ums0: Microsoft Microsoft USB Wireless Mouse, rev 2.00/0.17, addr 2, iclass 3/1 ums_attach: bLength=7 bDescriptorType=5 bEndpointAddress=1-in bmAttributes=3 wMaxPacketSize=8 bInterval=10 ums0: 5 buttons and Z dir. ums_attach: sc=0xc1bcb800 ums_attach: X 48/8 ums_attach: Y 56/8 ums_attach: Z 64/8 ums_attach: B1 40/1 ums_attach: B2 41/1 ums_attach: B3 42/1 ums_attach: B4 43/1 ums_attach: B5 44/1 ums_attach: size=11, id=19 ... seems like reported locations X,Y,Z and buttons are wrong. any clues? thanx michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: MS USB Wireless Mouse
Michal Vanco wrote:
... seems like reported locations X,Y,Z and buttons are wrong.
well ... this works. but i'm not sure for other mices
diff -Nrua usb/ums.c /sys/dev/usb/ums.c
--- usb/ums.c Sun Jan 30 02:00:10 2005
+++ /sys/dev/usb/ums.c Mon Jun 13 16:24:50 2005
@@ -76,6 +76,7 @@
#include machine/mouse.h
#endif
+
#ifdef USB_DEBUG
#define DPRINTF(x) if (umsdebug) logprintf x
#define DPRINTFN(n,x) if (umsdebug(n)) logprintf x
@@ -287,6 +288,9 @@
if (hid_locate(desc, size, HID_USAGE2(HUP_GENERIC_DESKTOP,
HUG_TWHEEL),
hid_input, sc-sc_loc_t, flags)) {
sc-sc_loc_t.pos = sc-sc_loc_t.pos + 8;
+ sc-sc_loc_x.pos = sc-sc_loc_x.pos - 40;
+ sc-sc_loc_y.pos = sc-sc_loc_y.pos - 40;
+ sc-sc_loc_z.pos = sc-sc_loc_z.pos - 40;
sc-flags |= UMS_T;
}
@@ -307,9 +311,12 @@
sc-nbuttons, sc-flags UMS_Z? and Z dir : ,
sc-flags UMS_T? and a TILT dir: );
- for (i = 1; i = sc-nbuttons; i++)
+ for (i = 1; i = sc-nbuttons; i++) {
hid_locate(desc, size, HID_USAGE2(HUP_BUTTON, i),
hid_input, sc-sc_loc_btn[i-1], 0);
+ if (sc-flags UMS_T)
+ sc-sc_loc_btn[i - 1].pos -= 40;
+ }
sc-sc_isize = hid_report_size(desc, size, hid_input, sc-sc_iid);
sc-sc_ibuf = malloc(sc-sc_isize, M_USB, M_NOWAIT);
@@ -458,8 +465,9 @@
*/
if (sc-flags UMS_T) {
if (sc-sc_iid) {
- if (*ibuf++ == 0x02)
- return;
+ ibuf++;
+ if (*(ibuf - 1) == 0x02 || *(ibuf - 1) == 0x14)
+ return;
}
} else {
if (sc-sc_iid) {
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Microsoft USB Wireless Mouse not working
Hi, I'm running 5.4-STABLE and I'm not able to get my MS USB Wireless mouse working. After plugging the mouse I see this in my dmesg: uhid0: Microsoft Microsoft USB Wireless Mouse, rev 2.00/0.17, addr 2, iclass 3/1 But there is no ums device. I have device ums in kernel. Is there any patch available to get this working? thanks in advance michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Microsoft USB Wireless Mouse not working
Ronald Klop wrote: On Fri, 10 Jun 2005 15:38:42 +0200, Michal Vanco [EMAIL PROTECTED] wrote: Hi, I'm running 5.4-STABLE and I'm not able to get my MS USB Wireless mouse working. After plugging the mouse I see this in my dmesg: uhid0: Microsoft Microsoft USB Wireless Mouse, rev 2.00/0.17, addr 2, iclass 3/1 But there is no ums device. I have device ums in kernel. Is there any patch available to get this working? Do you also have 'uhid' in your kernel or loaded as a module? Maybe it attaches before ums. If yes, try removing it from your kernel and boot again. This is just a thought, so maybe it doesn't work. hmm ... but for other USB mices (wired) it works normaly. doesn't ums depend on uhid? michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: FreeBSD and NMAP
On Tue, 19 Apr 2005, peceka wrote: How can i hide from nmap that my OS is FreeBSD? Is this possible? # sysctl -ad | grep random_id net.inet.ip.random_id: Assign random ip_id values # echo 'net.inet.ip.random_id=1' /etc/sysctl.conf After that: Interesting ports on 192.168.1.248: (The 1643 ports scanned but not shown below are in state: closed) Port State Service 22/tcp openssh Device type: general purpose Running (JUST GUESSING) : FreeBSD 5.X|4.X (95%), Apple Mac OS X 10.1.X (88%), OpenBSD 3.X|2.X (88%), Apple Mac OS 8.X (85%) Aggressive OS guesses: FreeBSD 5.0-RELEASE (95%), Apple Mac OS X 10.1.5 (88%), FreeBSD 4.3 - 4.4PRERELEASE (88%), FreeBSD 5.0-RELEASE (x86) (88%), FreeBSD 5.1-CURRENT (June 2003) on Sparc64 (88%), OpenBSD 3.0 or 3.3 (88%), Apple Mac OS X 10.1.4 (Darwin Kernel 5.4) on iMac (86%), FreeBSD 4.5-RELEASE (or -STABLE) through 4.6-RC (X86) (86%), FreeBSD 4.7-RELEASE (86%), FreeBSD 5.0-RELEASE or -CURRENT (Jan 2003) (86%) No exact OS matches for host (test conditions non-ideal). Uptime 0.003 days (since Tue Apr 19 13:22:41 2005) So it didn't help much... So, try this: block in log quick proto tcp flags FUP/WEUAPRSF block in log quick proto tcp flags WEUAPRSF/WEUAPRSF block in log quick proto tcp flags SRAFU/WEUAPRSF block in log quick proto tcp flags /WEUAPRSF block in log quick proto tcp flags SR/SR block in log quick proto tcp flags SF/SF (in pf.conf) -- Micha 'max' Marciniak felix.fizyka.amu.edu.pl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB JetFlash
Mikhail Godovitcin wrote: I believe I should be able to help you. I've got smaller JetFlash which works. Yours might need a quirk entry in umass.c. Can you send us the output of 'usbdevs -v'? Hello! FreeBSD 5.4-PRERELEASE #0: Mon Mar 21 12:07:18 MSK 2005 JetFlash TS512MJF2B 2.00 (512Mb) works well: umass0: USB Flash Disk, rev 2.00/2.00, addr 2 da0 at umass-sim0 bus 0 target 0 lun 0 da0: JetFlash TS512MJF2B 2.00 Removable Direct Access SCSI-2 device da0: 1.000MB/s transfers da0: 500MB (1024000 512 byte sectors: 64H 32S/T 500C) umass0: at uhub0 port 1 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry umass0: detached but JetFlash TS1GJF2B 2.00 produses many errors: da0: Attempt to query device size failed: UNIT ATTENTION, Not ready to ready change, (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 and so on until (da0:umass-sim0:0:0:0): Retries Exhausted Opened disk da0 - 6 (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): UNIT ATTENTION asc:28,0 (da0:umass-sim0:0:0:0): Not ready to ready change, medium may have changed (da0:umass-sim0:0:0:0): Retrying Command (per Sense Data) umass0: at uhub0 port 1 (addr 2) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry umass0: detached How can I fix this? Thanks in advance. -- Mikhail Godovitcin http://www.kc.ru/~mg/pgpkey.txt ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Re[2]: USB JetFlash
Mikhail Godovitcin wrote:
Hello!
Thursday, March 31, 2005, 16:48, you wrote:
I believe I should be able to help you. I've got smaller JetFlash which
works. Yours might need a quirk entry in umass.c.
Can you send us the output of 'usbdevs -v'?
Yes, sure. Here it is.
# usbdevs -v
Controller /dev/usb0:
addr 1: full speed, self powered, config 1, UHCI root hub(0x),
Intel(0x), rev 1.00
port 1 addr 2: full speed, power 100 mA, config 1, Flash Disk(0x2168),
USB(0x0ea0), rev 2.00
port 2 powered
# camcontrol inquiry da0
pass0: JetFlash TS1GJF2B 2.00 Removable Direct Access SCSI-2 device
pass0: Serial Number
pass0: 1.000MB/s transfers
Thank you.
I'm afraid I can't easily help you because your device is different than
mine.
You can try attached patch anyways. Apply with 'cd /sys/dev/usb;patch
jmtek.diff;cd /sys/modules/umass;make -DUSB_DEBUG=1;make unload;make
load'.
I won't be surprised if it didn't fix your disk though. You might try to
change UMASS_ADD_DELAY in
{ USB_VENDOR_OTI, USB_PRODUCT_OTI_JETFLASH2, RID_WILDCARD,
UMASS_PROTO_SCSI | UMASS_PROTO_BBB,
UMASS_ADD_DELAY
},
to 'IGNORE_RESIDUE | NO_GETMAXLUN | RS_NO_CLEAR_UA'. Maybe
FORCE_SHORT_INQUIRY instead/in addition to these.
After modifying umass.c you need to rebuild and unloadload the kld. If
you have umass (or whole usb) in your kernel ('device umass') you should
comment it out, reinstall kernel and reboot. Then you'll be able to try
different quirk values.
HTH
Michal
Index: umass.c
===
RCS file: /home/fcvs/cvs/src/sys/dev/usb/umass.c,v
retrieving revision 1.121
diff -u -r1.121 umass.c
--- umass.c 25 Mar 2005 01:47:01 - 1.121
+++ umass.c 31 Mar 2005 19:53:51 -
@@ -314,6 +314,8 @@
# define NO_INQUIRY 0x0400
/* Device cannot handle INQUIRY EVPD, return CHECK CONDITION */
# define NO_INQUIRY_EVPD 0x0800
+ /* Device needs time to settle down - should be fixed elsewhere*/
+# define UMASS_ADD_DELAY 0x1000
};
Static struct umass_devdescr_t umass_devdescrs[] = {
@@ -387,6 +389,10 @@
UMASS_PROTO_ATAPI | UMASS_PROTO_BBB,
NO_QUIRKS
},
+ { USB_VENDOR_MSYSTEMS, USB_PRODUCT_MSYSTEMS_DELLMEMKEY, RID_WILDCARD,
+ UMASS_PROTO_SCSI | UMASS_PROTO_BBB,
+ UMASS_ADD_DELAY
+ },
{ USB_VENDOR_NEODIO, USB_PRODUCT_NEODIO_ND3260, RID_WILDCARD,
UMASS_PROTO_SCSI | UMASS_PROTO_BBB,
FORCE_SHORT_INQUIRY
@@ -399,6 +405,10 @@
UMASS_PROTO_ATAPI | UMASS_PROTO_BBB,
NO_INQUIRY | NO_GETMAXLUN
},
+ { USB_VENDOR_OTI, USB_PRODUCT_OTI_JETFLASH2, RID_WILDCARD,
+ UMASS_PROTO_SCSI | UMASS_PROTO_BBB,
+ UMASS_ADD_DELAY
+ },
{ USB_VENDOR_PANASONIC, USB_PRODUCT_PANASONIC_KXLCB20AN, RID_WILDCARD,
UMASS_PROTO_SCSI | UMASS_PROTO_BBB,
NO_QUIRKS
@@ -891,6 +901,7 @@
(void) umass_match_proto(sc, sc-iface, uaa-device);
id = usbd_get_interface_descriptor(sc-iface);
+
#ifdef USB_DEBUG
printf(%s: , USBDEVNAME(sc-sc_dev));
switch (sc-protoUMASS_PROTO_COMMAND) {
@@ -2263,6 +2274,7 @@
Static int
umass_cam_attach(struct umass_softc *sc)
{
+ int delay_len;
#ifndef USB_DEBUG
if (bootverbose)
#endif
@@ -2279,7 +2291,11 @@
* completed, when interrupts have been enabled.
*/
- usb_callout(sc-cam_scsi_rescan_ch, MS_TO_TICKS(200),
+ if (sc-quirks UMASS_ADD_DELAY)
+ delay_len = 2000;
+ else
+ delay_len = 200;
+ usb_callout(sc-cam_scsi_rescan_ch, MS_TO_TICKS(delay_len),
umass_cam_rescan, sc);
}
Index: usbdevs
===
RCS file: /home/fcvs/cvs/src/sys/dev/usb/usbdevs,v
retrieving revision 1.226
diff -u -r1.226 usbdevs
--- usbdevs 21 Mar 2005 08:43:54 - 1.226
+++ usbdevs 31 Mar 2005 19:54:21 -
@@ -529,6 +529,7 @@
vendor SITECOM 0x6189 Sitecom
vendor INTEL 0x8086 Intel
vendor HP2 0xf003 Hewlett Packard
+vendor JMTEK 0x0c76 JMTek, LLC.
/*
* List of known products. Grouped by vendor.
@@ -1188,6 +1189,7 @@
/* M-Systems products */
product MSYSTEMS DISKONKEY 0x0010 DiskOnKey
product MSYSTEMS DISKONKEY2 0x0011 DiskOnKey
+product MSYSTEMS DELLMEMKEY 0x0015 Dell Memory Key
/* National Semiconductor */
product NATIONAL BEARPAW1200 0x1000 BearPaw 1200
@@ -1560,3 +1562,9 @@
/* ZyXEL Communication Co. products */
product ZYXEL OMNI56K 0x1500 Omni 56K Plus
product ZYXEL 980N 0x2011 Scorpion-980N keyboard
+
+/* JMTek, LLC. products */
+product JMTEK JETFLASH 0x0005 Transcend JetFlash
+
+/* Ours Technology, Inc. products */
+product OTI JETFLASH2 0x2168 Transcend JetFlash 2.0
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Cannot build kernel with options WITNESS
look in /usr/src/UPDATING *** 20040710: A revamp of the debugging code in the kernel with some visible changes beyond just the debugging experience: o The DDB option is now specific to the DDB debugger backend and should not be used any more for conditional compilation of debugging code for when debugging is enabled. Use the KDB option for this. o The WITNESS_DDB, DDB_TRACE and DDB_UNATTENDED options have been renamed to WITNESS_KDB, KDB_TRACE and KDB_UNATTENDED respectively. This is in line with the first bullet. o The remote GDB support has been untangled from DDB and needs to be enabled separately now. Use the GDB option for this. o The GDB_REMOTE_CHAT option has been removed. Support for this homegrown feature is discontinued. The GDB remote protocol supports console output and it makes sense to use that. o The DDB_NOKLDSYM option has been removed. The DDB debugger now supports both direct symbol table lookups as well as KLD symbol lookups through the linker. *** Best Regards fofo I cvssed just an hour ago. 5.3-STABLE and cannot build kernel with WITNES. It complains: cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -W missing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -st d=c99 -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/contrib/dev/acpica -I/us r/src/sys/contrib/altq -I/usr/src/sys/contrib/ipfilter -I/usr/src/sys/contrib/pf -I/usr/src/sys/contrib/dev/ath -I/usr/src/sys/contrib/dev/ath/freebsd -I/usr/sr c/sys/contrib/ngatm -D_KERNEL -include opt_global.h -fno-common -finline-limit=8 000 --param inline-unit-growth=100 --param large-function-growth=1000 -mno-alig n-long-strings -mpreferred-stack-boundary=2 -ffreestanding -Werror /usr/src/sys /kern/subr_witness.c /usr/src/sys/kern/subr_witness.c:1737: warning: 'witness_proc_has_locks' defined but not used *** Error code 1 Stop in /usr/obj/usr/src/sys/OMNI2. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. THE KERNEL CONFIG FILE : machine i386 cpu I486_CPU cpu I586_CPU cpu I686_CPU ident OMNI2 options SMP options QUOTA options SCHED_4BSD # 4BSD scheduler options INET # InterNETworking options INET6 # IPv6 communications protocols options FFS # Berkeley Fast Filesystem options SOFTUPDATES # Enable FFS soft updates support options UFS_ACL # Support for access control lists options UFS_DIRHASH # Improve performance on big directories #options MD_ROOT # MD is a potential root device #options NFSCLIENT # Network Filesystem Client #options NFSSERVER # Network Filesystem Server #options NFS_ROOT # NFS usable as /, requires NFSCLIENT options MSDOSFS # MSDOS Filesystem options CD9660 # ISO 9660 Filesystem options PROCFS # Process filesystem (requires PSEUDOFS) options PSEUDOFS # Pseudo-filesystem framework options GEOM_GPT # GUID Partition Tables. options COMPAT_43 # Compatible with BSD 4.3 [KEEP THIS!] options COMPAT_FREEBSD4 # Compatible with FreeBSD4 #options SCSI_DELAY=15000 # Delay (in ms) before probing SCSI options KTRACE # ktrace(1) support options SYSVSHM # SYSV-style shared memory options SYSVMSG # SYSV-style message queues options SYSVSEM # SYSV-style semaphores #options _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions #options KBD_INSTALL_CDEV # install a CDEV entry in /dev #options ADAPTIVE_GIANT # Giant mutex is adaptive. device apic # I/O APIC # Bus support. Do not remove isa, even if you have no isa slots device isa device pci # Floppy drives device fdc # ATA and ATAPI devices device ata device atadisk # ATA disk drives device ataraid # ATA RAID drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID # Static device numbering # SCSI peripherals device scbus # SCSI bus (required for SCSI) device da # Direct Access (disks) device pass # Passthrough device (direct SCSI access) device twe # 3ware ATA RAID # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc # AT keyboard controller device atkbd # AT keyboard device psm # PS/2 mouse device vga # VGA video card driver device splash # Splash screen and screen saver support # syscons is the default console driver, resembling an SCO console device sc device agp # support several AGP chipsets # Floating point support - do not disable. device npx # Power management support (see NOTES for more options) #device apm # Add suspend/resume support for the i8254. #device pmtimer # Serial (COM) ports device sio # 8250, 16[45]50 based serial ports # Parallel port device ppc device ppbus # Parallel port bus (required) device lpt # Printer device ppi # Parallel port interface device #device vpo # Requires scbus and da device miibus # MII
Re: strange ucom (uplcom) error
Emanuel Strobl wrote: Am Donnerstag, 20. Januar 2005 14:18 schrieb Michal Mertl: I tested my patch for binary safety on CURRENT yesterday (dialed with ppp) and didn't notice any problem. I'm attaching my patch again because some recipients didn't probably receive it yesterday. This didn't apply cleanly against my -stable from today. Attached is a cleaned version (#define RSAQ_STATUS_CTS doesn't exist in -stable uplcom.c) for -stable which compiles for me. Thank you. I found I can't run getty on the converter. I see some output on the remote computer but it stops pretty soon. If I issue setty -f /dev/cuaU0 crtscts I get some more output. It works really realiably in the other direction (running getty on real serial and connecting to it with cu through the converter). I will try to find out more. Michal ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange ucom (uplcom) error
I wrote:
Emanuel Strobl wrote:
Am Dienstag, 18. Januar 2005 16:17 schrieb Andrew L. Neporada:
On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote:
Dear experts,
I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working
the other one not (I hate to say it but both are working under win).
The not working (more expensive) one gets recognized as ucom0 and I have
ucom0, also I can receive signal but not transmit.
[skip]
Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch
http://gate.intercaf.ru/~lesha/6100/pl2303x.patch
It can break old (working) PL2303 chip, but it works for me with newer
Thanks a lot, this indeed fixes the revision 3.0 adaptor but unfortunately
also breakes the 2.02 version :(
Perhaps there's a goog guy out there who can refurbish the uplcom driver
with
this information (akiyama?)?
Thanks a lot,
I've just recently been looking into this too. I used the mentioned
patch and also linux driver source and have come with the attached
patch. It contains one more change but I don't know if it's correct. It
works for both chips on CURRENT for serial console. It detects if the
chip is rev 3.00 and aplies the patch only for it.
The author of the patch mentions it isn't binary safe - sometimes the
chip stops working. I planned to test it with binary transfers (ppp)
today, check if it's working and submit it (with some cleanup) for
inclusion in FreeBSD.
Michal Mertl
I tested my patch for binary safety on CURRENT yesterday (dialed with
ppp) and didn't notice any problem.
I'm attaching my patch again because some recipients didn't probably
receive it yesterday.
Michal
Index: uplcom.c
===
RCS file: /home/fcvs/cvs/src/sys/dev/usb/uplcom.c,v
retrieving revision 1.25
diff -u -r1.25 uplcom.c
--- uplcom.c 6 Jan 2005 01:43:29 - 1.25
+++ uplcom.c 20 Jan 2005 13:15:40 -
@@ -97,10 +97,13 @@
#include sys/sysctl.h
#include sys/uio.h
+#include machine/bus.h
+
#include dev/usb/usb.h
#include dev/usb/usbcdc.h
#include dev/usb/usbdi.h
+#include dev/usb/usbdivar.h
#include dev/usb/usbdi_util.h
#include usbdevs.h
#include dev/usb/usb_quirks.h
@@ -113,30 +116,34 @@
SYSCTL_INT(_hw_usb_uplcom, OID_AUTO, debug, CTLFLAG_RW,
uplcomdebug, 0, uplcom debug level);
-#define DPRINTFN(n, x) do { \
+#define DPRINTFN(n, x) do { \
if (uplcomdebug (n)) \
logprintf x; \
} while (0)
#else
-#define DPRINTFN(n, x)
+#define DPRINTFN(n, x)
#endif
-#define DPRINTF(x) DPRINTFN(0, x)
+#define DPRINTF(x) DPRINTFN(0, x)
-#define UPLCOM_MODVER 1 /* module version */
+#define UPLCOM_MODVER 1 /* module version */
#define UPLCOM_CONFIG_INDEX 0
#define UPLCOM_IFACE_INDEX 0
#define UPLCOM_SECOND_IFACE_INDEX 1
#ifndef UPLCOM_INTR_INTERVAL
-#define UPLCOM_INTR_INTERVAL 100 /* ms */
+#define UPLCOM_INTR_INTERVAL 100 /* ms */
#endif
#define UPLCOM_SET_REQUEST 0x01
#define UPLCOM_SET_CRTSCTS 0x41
-#define RSAQ_STATUS_CTS 0x80
-#define RSAQ_STATUS_DSR 0x02
-#define RSAQ_STATUS_DCD 0x01
+#define UPLCOM_SET_CRTSCTS_2303X 0x61
+#define RSAQ_STATUS_CTS 0x80
+#define RSAQ_STATUS_DSR 0x02
+#define RSAQ_STATUS_DCD 0x01
+
+#define CHIPTYPE_PL2303 0
+#define CHIPTYPE_PL2303X 1
struct uplcom_softc {
struct ucom_softc sc_ucom;
@@ -156,14 +163,15 @@
u_char sc_lsr; /* Local status register */
u_char sc_msr; /* uplcom status register */
+ int sc_chiptype;
};
/*
* These are the maximum number of bytes transferred per frame.
* The output buffer size cannot be increased due to the size encoding.
*/
-#define UPLCOMIBUFSIZE 256
-#define UPLCOMOBUFSIZE 256
+#define UPLCOMIBUFSIZE 256
+#define UPLCOMOBUFSIZE 256
Static usbd_status uplcom_reset(struct uplcom_softc *);
Static usbd_status uplcom_set_line_coding(struct uplcom_softc *,
@@ -299,6 +307,7 @@
char *devinfo;
const char *devname;
usbd_status err;
+ usb_device_descriptor_t *udd;
int i;
devinfo = malloc(1024, M_USBDEV, M_WAITOK);
@@ -374,7 +383,14 @@
sc-sc_isize = UGETW(ed-wMaxPacketSize);
}
}
-
+ udd = dev-ddesc;
+ if (UGETW(udd-bcdDevice) == 0x300) {
+ DPRINTF((chiptype 2303X\n));
+ sc-sc_chiptype = CHIPTYPE_PL2303X;
+ } else {
+ DPRINTF((chiptype 2303\n));
+ sc-sc_chiptype = CHIPTYPE_PL2303;
+ }
if (sc-sc_intr_number == -1) {
printf(%s: Could not find interrupt in\n,
USBDEVNAME(ucom-sc_dev));
@@ -617,7 +633,10 @@
req.bmRequestType = UT_WRITE_VENDOR_DEVICE;
req.bRequest = UPLCOM_SET_REQUEST;
USETW(req.wValue, 0);
- USETW(req.wIndex, UPLCOM_SET_CRTSCTS);
+ if (sc-sc_chiptype == CHIPTYPE_PL2303X)
+ USETW(req.wIndex, UPLCOM_SET_CRTSCTS_2303X);
+ else
+ USETW(req.wIndex, UPLCOM_SET_CRTSCTS);
USETW(req.wLength, 0);
err = usbd_do_request(sc-sc_ucom.sc_udev, req, 0);
@@ -713,6 +732,43 @@
return (0);
}
+#define DO_REQ(type, reQ, wVal, wInd) do
Re: strange ucom (uplcom) error
Emanuel Strobl wrote:
Am Dienstag, 18. Januar 2005 16:17 schrieb Andrew L. Neporada:
On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote:
Dear experts,
I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working
the other one not (I hate to say it but both are working under win).
The not working (more expensive) one gets recognized as ucom0 and I have
ucom0, also I can receive signal but not transmit.
[skip]
Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch
http://gate.intercaf.ru/~lesha/6100/pl2303x.patch
It can break old (working) PL2303 chip, but it works for me with newer
Thanks a lot, this indeed fixes the revision 3.0 adaptor but unfortunately
also breakes the 2.02 version :(
Perhaps there's a goog guy out there who can refurbish the uplcom driver with
this information (akiyama?)?
Thanks a lot,
I've just recently been looking into this too. I used the mentioned
patch and also linux driver source and have come with the attached
patch. It contains one more change but I don't know if it's correct. It
works for both chips on CURRENT for serial console.
The author of the patch mentions it isn't binary safe - sometimes the
chip stops working. I planned to test it with binary transfers (ppp)
today, check if it's working and submit it (with some cleanup) for
inclusion in FreeBSD.
Michal Mertl
Index: uplcom.c
===
RCS file: /home/fcvs/cvs/src/sys/dev/usb/uplcom.c,v
retrieving revision 1.25
diff -u -r1.25 uplcom.c
--- uplcom.c 6 Jan 2005 01:43:29 - 1.25
+++ uplcom.c 15 Jan 2005 00:44:20 -
@@ -97,10 +97,13 @@
#include sys/sysctl.h
#include sys/uio.h
+#include machine/bus.h
+
#include dev/usb/usb.h
#include dev/usb/usbcdc.h
#include dev/usb/usbdi.h
+#include dev/usb/usbdivar.h
#include dev/usb/usbdi_util.h
#include usbdevs.h
#include dev/usb/usb_quirks.h
@@ -113,30 +116,33 @@
SYSCTL_INT(_hw_usb_uplcom, OID_AUTO, debug, CTLFLAG_RW,
uplcomdebug, 0, uplcom debug level);
-#define DPRINTFN(n, x) do { \
+#define DPRINTFN(n, x) do { \
if (uplcomdebug (n)) \
logprintf x; \
} while (0)
#else
-#define DPRINTFN(n, x)
+#define DPRINTFN(n, x)
#endif
-#define DPRINTF(x) DPRINTFN(0, x)
+#define DPRINTF(x) DPRINTFN(0, x)
-#define UPLCOM_MODVER 1 /* module version */
+#define UPLCOM_MODVER 1 /* module version */
#define UPLCOM_CONFIG_INDEX 0
#define UPLCOM_IFACE_INDEX 0
#define UPLCOM_SECOND_IFACE_INDEX 1
#ifndef UPLCOM_INTR_INTERVAL
-#define UPLCOM_INTR_INTERVAL 100 /* ms */
+#define UPLCOM_INTR_INTERVAL 100 /* ms */
#endif
#define UPLCOM_SET_REQUEST 0x01
#define UPLCOM_SET_CRTSCTS 0x41
-#define RSAQ_STATUS_CTS 0x80
-#define RSAQ_STATUS_DSR 0x02
-#define RSAQ_STATUS_DCD 0x01
+#define RSAQ_STATUS_CTS 0x80
+#define RSAQ_STATUS_DSR 0x02
+#define RSAQ_STATUS_DCD 0x01
+
+#define CHIPTYPE_PL2303 0
+#define CHIPTYPE_PL2303X 1
struct uplcom_softc {
struct ucom_softc sc_ucom;
@@ -156,14 +162,15 @@
u_char sc_lsr; /* Local status register */
u_char sc_msr; /* uplcom status register */
+ int sc_chiptype;
};
/*
* These are the maximum number of bytes transferred per frame.
* The output buffer size cannot be increased due to the size encoding.
*/
-#define UPLCOMIBUFSIZE 256
-#define UPLCOMOBUFSIZE 256
+#define UPLCOMIBUFSIZE 256
+#define UPLCOMOBUFSIZE 256
Static usbd_status uplcom_reset(struct uplcom_softc *);
Static usbd_status uplcom_set_line_coding(struct uplcom_softc *,
@@ -299,6 +306,7 @@
char *devinfo;
const char *devname;
usbd_status err;
+ usb_device_descriptor_t *udd;
int i;
devinfo = malloc(1024, M_USBDEV, M_WAITOK);
@@ -374,7 +382,14 @@
sc-sc_isize = UGETW(ed-wMaxPacketSize);
}
}
-
+ udd = dev-ddesc;
+ if (UGETW(udd-bcdDevice) == 0x300) {
+ DPRINTF((chiptype 2303X\n));
+ sc-sc_chiptype = CHIPTYPE_PL2303X;
+ } else {
+ DPRINTF((chiptype 2303\n));
+ sc-sc_chiptype = CHIPTYPE_PL2303;
+ }
if (sc-sc_intr_number == -1) {
printf(%s: Could not find interrupt in\n,
USBDEVNAME(ucom-sc_dev));
@@ -617,7 +632,10 @@
req.bmRequestType = UT_WRITE_VENDOR_DEVICE;
req.bRequest = UPLCOM_SET_REQUEST;
USETW(req.wValue, 0);
- USETW(req.wIndex, UPLCOM_SET_CRTSCTS);
+ if (sc-sc_chiptype == CHIPTYPE_PL2303X)
+ USETW(req.wIndex, 0x61);
+ else
+ USETW(req.wIndex, UPLCOM_SET_CRTSCTS);
USETW(req.wLength, 0);
err = usbd_do_request(sc-sc_ucom.sc_udev, req, 0);
@@ -713,6 +731,43 @@
return (0);
}
+#define DO_REQ(type, reQ, wVal, wInd) do {\
+ req.bmRequestType = (type); \
+ req.bRequest = (reQ); \
+ USETW(req.wValue, (wVal)); \
+ USETW(req.wIndex, (wInd)); \
+ USETW(req.wLength, 0); \
+ err = usbd_do_request(sc-sc_ucom.sc_udev, req, 0); \
+ if (err) { \
+ printf(%s: uplcom_initPL2303X_%d: %s\n, \
+ USBDEVNAME(sc-sc_ucom.sc_dev), i++, usbd_errstr(err)); \
+ return (EIO
[Fwd: Re: strange ucom (uplcom) error]
Emanuel Strobl wrote: Am Dienstag, 18. Januar 2005 16:17 schrieb Andrew L. Neporada: On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote: Dear experts, I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working the other one not (I hate to say it but both are working under win). The not working (more expensive) one gets recognized as ucom0 and I have ucom0, also I can receive signal but not transmit. [skip] Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch http://gate.intercaf.ru/~lesha/6100/pl2303x.patch It can break old (working) PL2303 chip, but it works for me with newer Thanks a lot, this indeed fixes the revision 3.0 adaptor but unfortunately also breakes the 2.02 version :( Perhaps there's a goog guy out there who can refurbish the uplcom driver with this information (akiyama?)? Thanks a lot, I've just recently been looking into this too. I used the mentioned patch and also linux driver source and have come with the attached patch. It contains one more change but I don't know if it's correct. It works for both chips on CURRENT for serial console. It detects if the chip is rev 3.00 and aplies the patch only for it. The author of the patch mentions it isn't binary safe - sometimes the chip stops working. I planned to test it with binary transfers (ppp) today, check if it's working and submit it (with some cleanup) for inclusion in FreeBSD. Michal Mertl ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: strange ucom (uplcom) error
Sorry to reply to myself but I would better really attach the patch.
I wrote:
Emanuel Strobl wrote:
Am Dienstag, 18. Januar 2005 16:17 schrieb Andrew L. Neporada:
On Tue, Jan 18, 2005 at 01:06:43PM +0100, Emanuel Strobl wrote:
Dear experts,
I have two USB-RS232 Adaptors, both with PL2303 chipset. One is working
the other one not (I hate to say it but both are working under win).
The not working (more expensive) one gets recognized as ucom0 and I have
ucom0, also I can receive signal but not transmit.
[skip]
Take a look at http://gate.intercaf.ru/~lesha/6100/ and try patch
http://gate.intercaf.ru/~lesha/6100/pl2303x.patch
It can break old (working) PL2303 chip, but it works for me with newer
Thanks a lot, this indeed fixes the revision 3.0 adaptor but unfortunately
also breakes the 2.02 version :(
Perhaps there's a goog guy out there who can refurbish the uplcom driver
with
this information (akiyama?)?
Thanks a lot,
I've just recently been looking into this too. I used the mentioned
patch and also linux driver source and have come with the attached
patch. It contains one more change but I don't know if it's correct. It
works for both chips on CURRENT for serial console. It detects if the
chip is rev 3.00 and aplies the patch only for it.
The author of the patch mentions it isn't binary safe - sometimes the
chip stops working. I planned to test it with binary transfers (ppp)
today, check if it's working and submit it (with some cleanup) for
inclusion in FreeBSD.
Michal Mertl
Index: uplcom.c
===
RCS file: /home/fcvs/cvs/src/sys/dev/usb/uplcom.c,v
retrieving revision 1.25
diff -u -r1.25 uplcom.c
--- uplcom.c 6 Jan 2005 01:43:29 - 1.25
+++ uplcom.c 15 Jan 2005 00:44:20 -
@@ -97,10 +97,13 @@
#include sys/sysctl.h
#include sys/uio.h
+#include machine/bus.h
+
#include dev/usb/usb.h
#include dev/usb/usbcdc.h
#include dev/usb/usbdi.h
+#include dev/usb/usbdivar.h
#include dev/usb/usbdi_util.h
#include usbdevs.h
#include dev/usb/usb_quirks.h
@@ -113,30 +116,33 @@
SYSCTL_INT(_hw_usb_uplcom, OID_AUTO, debug, CTLFLAG_RW,
uplcomdebug, 0, uplcom debug level);
-#define DPRINTFN(n, x) do { \
+#define DPRINTFN(n, x) do { \
if (uplcomdebug (n)) \
logprintf x; \
} while (0)
#else
-#define DPRINTFN(n, x)
+#define DPRINTFN(n, x)
#endif
-#define DPRINTF(x) DPRINTFN(0, x)
+#define DPRINTF(x) DPRINTFN(0, x)
-#define UPLCOM_MODVER 1 /* module version */
+#define UPLCOM_MODVER 1 /* module version */
#define UPLCOM_CONFIG_INDEX 0
#define UPLCOM_IFACE_INDEX 0
#define UPLCOM_SECOND_IFACE_INDEX 1
#ifndef UPLCOM_INTR_INTERVAL
-#define UPLCOM_INTR_INTERVAL 100 /* ms */
+#define UPLCOM_INTR_INTERVAL 100 /* ms */
#endif
#define UPLCOM_SET_REQUEST 0x01
#define UPLCOM_SET_CRTSCTS 0x41
-#define RSAQ_STATUS_CTS 0x80
-#define RSAQ_STATUS_DSR 0x02
-#define RSAQ_STATUS_DCD 0x01
+#define RSAQ_STATUS_CTS 0x80
+#define RSAQ_STATUS_DSR 0x02
+#define RSAQ_STATUS_DCD 0x01
+
+#define CHIPTYPE_PL2303 0
+#define CHIPTYPE_PL2303X 1
struct uplcom_softc {
struct ucom_softc sc_ucom;
@@ -156,14 +162,15 @@
u_char sc_lsr; /* Local status register */
u_char sc_msr; /* uplcom status register */
+ int sc_chiptype;
};
/*
* These are the maximum number of bytes transferred per frame.
* The output buffer size cannot be increased due to the size encoding.
*/
-#define UPLCOMIBUFSIZE 256
-#define UPLCOMOBUFSIZE 256
+#define UPLCOMIBUFSIZE 256
+#define UPLCOMOBUFSIZE 256
Static usbd_status uplcom_reset(struct uplcom_softc *);
Static usbd_status uplcom_set_line_coding(struct uplcom_softc *,
@@ -299,6 +306,7 @@
char *devinfo;
const char *devname;
usbd_status err;
+ usb_device_descriptor_t *udd;
int i;
devinfo = malloc(1024, M_USBDEV, M_WAITOK);
@@ -374,7 +382,14 @@
sc-sc_isize = UGETW(ed-wMaxPacketSize);
}
}
-
+ udd = dev-ddesc;
+ if (UGETW(udd-bcdDevice) == 0x300) {
+ DPRINTF((chiptype 2303X\n));
+ sc-sc_chiptype = CHIPTYPE_PL2303X;
+ } else {
+ DPRINTF((chiptype 2303\n));
+ sc-sc_chiptype = CHIPTYPE_PL2303;
+ }
if (sc-sc_intr_number == -1) {
printf(%s: Could not find interrupt in\n,
USBDEVNAME(ucom-sc_dev));
@@ -617,7 +632,10 @@
req.bmRequestType = UT_WRITE_VENDOR_DEVICE;
req.bRequest = UPLCOM_SET_REQUEST;
USETW(req.wValue, 0);
- USETW(req.wIndex, UPLCOM_SET_CRTSCTS);
+ if (sc-sc_chiptype == CHIPTYPE_PL2303X)
+ USETW(req.wIndex, 0x61);
+ else
+ USETW(req.wIndex, UPLCOM_SET_CRTSCTS);
USETW(req.wLength, 0);
err = usbd_do_request(sc-sc_ucom.sc_udev, req, 0);
@@ -713,6 +731,43 @@
return (0);
}
+#define DO_REQ(type, reQ, wVal, wInd) do {\
+ req.bmRequestType = (type); \
+ req.bRequest = (reQ); \
+ USETW(req.wValue, (wVal)); \
+ USETW(req.wIndex, (wInd)); \
+ USETW(req.wLength, 0); \
+ err = usbd_do_request(sc
Re: Marvell 88E8001 on sk0 and RELENG_5_3 - big problems
On Thu, Dec 16, 2004 at 01:45:50PM +, Bjoern A. Zeeb wrote: @@ -2490,8 +2495,10 @@ sk_init_yukon(sc_if) YU_TPR_JAM_IPG(0xb) | YU_TPR_JAM2DATA_IPG(0x1a) ); /* serial mode register */ - SK_YU_WRITE_2(sc_if, YUKON_SMR, YU_SMR_DATA_BLIND(0x1c) | - YU_SMR_MFL_VLAN | YU_SMR_IPG_DATA(0x1e)); + reg = YU_SMR_DATA_BLIND(0x1c) | YU_SMR_MFL_VLAN | YU_SMR_IPG_DATA(0x1e); + if (ifp-if_mtu (ETHERMTU + ETHER_HDR_LEN + ETHER_CRC_LEN)) Or: if (ifp-if_mtu ETHER_MAX_LEN) ? -- Michal Belczyk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Marvell 88E8001 on sk0 and RELENG_5_3 - big problems
On Tue, Dec 14, 2004 at 11:00:40PM +0100, Heinz Knocke wrote: b) according to the vendor's info, NIC should be able to do jumboframes. (http://www.marvell.com/products/pcconn/yukon/Yukon_88E8001_10_073103_final.pdf) ifconfig mtu 9000 works, but packets seems to come truncated (in both directions) host1% sudo ping -s 2000 host2 PING host2 (10.10.10.2): 2000 data bytes ^C --- host2 ping statistics --- 23 packets transmitted, 0 packets received, 100% packet loss host2% sudo tcpdump -i sk0 -c 30 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on sk0, link-type EN10MB (Ethernet), capture size 96 bytes 22:23:23.514150 IP truncated-ip - 524 bytes missing! dyplom1g dyplom2g: icmp 2008: echo request seq 3 22:23:24.524147 IP truncated-ip - 524 bytes missing! dyplom1g dyplom2g: icmp 2008: echo request seq 4 22:23:25.534282 IP truncated-ip - 524 bytes missing! dyplom1g dyplom2g: icmp 2008: echo request seq 5 22:23:26.544280 IP truncated-ip - 524 bytes missing! dyplom1g dyplom2g: icmp 2008: echo request seq 6 ^C Here's the fix: http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_sk.c.diff?r1=1.51r2=1.52 -- Michal Belczyk ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: options GRE in 4.7-stable
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Nov 28, 2002 at 11:21:49AM +0700, Eugene Grosbein wrote: pirat sriyotha wrote: i would like to ask that if options GRE is now in 4.7-stable ? if not then what options can be substituted for? It seems GRE is present in 5.0-CURRENT now but not in -STABLE. You will need some kind of kernel patch, there is no option for STABLE. Strange... # uname -a FreeBSD kyblik.pieskovisko.sk 4.7-STABLE FreeBSD 4.7-STABLE #3: Tue Dec 10 18:17:34 CET 2002 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/KYBLIK i386 # ifconfig gre0 gre0: flags=9050POINTOPOINT,RUNNING,LINK0,MULTICAST mtu 1476 Take look at http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/net/if_gre.c - --- the GRE driver has been MFCed on Fri Nov 15 00:00:15 2002 UTC (3 weeks, 4 days ago) by sam. mf - -- What do you care what other people think? -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE99jPPQgEMP0l2aH4RAig4AKC1q9mqfsprSMEpk4fFxW/7WGy2/gCeK5pq /JjLC0bS8IySam69jFs01Zg= =vajA -END PGP SIGNATURE- To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
syslogd stopping to work
After upgrade from 4.2-REL to 4.4-SECURITY syslogd stops logging after several days of operation. I use it to log routers and such and it's pretty important for me. I don't want to use some different syslogd unless absolutelly necessary. It has happened already several times. 'ps axO wchan' gives '49083 sbwait ?? Is 0:06.07 /usr/sbin/syslogd -a '. CPU usage is 0% and the daemon stays like this forever. I have built the binary with debug information and have the coredump. The backtrace (I sent the daemon ABORT signal) is: #0 0x280a7674 in recvfrom () from /usr/lib/libc.so.4 #1 0x280b4cb4 in res_send () from /usr/lib/libc.so.4 #2 0x280b7e7d in res_query () from /usr/lib/libc.so.4 #3 0x280b7bd3 in freehostent () from /usr/lib/libc.so.4 #4 0x280b5d91 in getipnodebyaddr () from /usr/lib/libc.so.4 #5 0x280b5494 in getnameinfo () from /usr/lib/libc.so.4 #6 0x804b4e2 in cvthname (f=0xbfbff9e0) at /data/src/usr.sbin/syslogd/syslogd.c:1215 #7 0x804a18d in main (argc=9, argv=0xbfbffb8c) at /data/src/usr.sbin/syslogd/syslogd.c:546 #8 0x8049745 in _start () From my reading of it it seems syslogd tries to do reverse DNS loookup (will be disabled by -n ?) and hangs in it. It's quite possible that there was interminent problem with DNS. May be the problem isn't in syslogd but in resolver. Any suggestion as to what else to check? What to do when next time I catch syslogd frozen? I installed cron script which checks the syslog state and for about 14 days it didn't happen :-(. -- Michal Mertl [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
RE: SSH Problem
It seems to me that's because OpenSSH_2.9 has been MFC. It by default has ForwardAgent option off (at least on FreeBSD with default config). You can fix it with ~/.ssh/config or change /etc/ssh/ssh_config Host * ForwardAgentyes -- Michal Mertl [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-stable in the body of the message
Re: kernel message
On Fri, 22 Dec 2000, Ling Ling wrote: Dear all, I have this message appeared in my /var/log/messages from time to time. Could anyone please explain to me what is happening here ?? /kernel: rl0: promiscuous mode disabled Yours rl0 interface turning off promiscous mode , probably you are using tcpdump, snort or other program like this. BS. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
