Re: rtorrent + OpenBSD = freeze

2008-02-25 Thread sebastian . rother
Well this bug wont get fixed.
That's what Theo said months ago... :)
 

Yes. I found the thread where you bashed each other before I made my first
post . I
guess I'll go with FreeBSD or NetBSD instead.


Daniel

Each user OpenBSD looses is a lost for the whole project.
That's my oppinion no matter if Theo or Henning do get nuts.

It's sick that a personal difference affects users like you. Because that
shouldn't happen at all...

And I hope some day Theo transforms from the I don't care-Theo to a You
piss me off you retard but I'll take a look anyway-Theo. Feel free to
replace Theo with any developer wich dislikes me...

Bugs just don't disappear if I shut up...

Kind regards,
Sebastian



Re: rtorrent + OpenBSD = freeze

2008-02-25 Thread Ted Unangst
On 2/25/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
  Bugs just don't disappear if I shut up...

No, but developers do disappear if you don't shut up.



Re: rtorrent + OpenBSD = freeze

2008-02-25 Thread Jacob Meuser
On Mon, Feb 25, 2008 at 05:52:26PM +0100, [EMAIL PROTECTED] wrote:
 Well this bug wont get fixed.
 That's what Theo said months ago... :)
  
 
 Yes. I found the thread where you bashed each other before I made my first
 post . I
 guess I'll go with FreeBSD or NetBSD instead.
 
 
 Daniel
 
 Each user OpenBSD looses is a lost for the whole project.

no.  if _you_ got lost, it would be a gain for the whole project
and everyone involved.

really, man, what's your purpose?  to be annoying?  to sling muck?

seriously, have you actually contributed anything positive to OpenBSD,
ever?

 It's sick that a personal difference affects users like you. Because that
 shouldn't happen at all...
 
 And I hope some day Theo transforms from the I don't care-Theo to a You
 piss me off you retard but I'll take a look anyway-Theo. Feel free to
 replace Theo with any developer wich dislikes me...

huh?  we all work on what interests us.  you make people disinterested.
you think that's bad, then quit being an annoying twit and quit making
people disinterested.  pretty easy, no?

-- 
[EMAIL PROTECTED]
SDF Public Access UNIX System - http://sdf.lonestar.org



Re: rtorrent + OpenBSD = freeze

2008-02-24 Thread sebastian . rother
Well this bug wont get fixed.
That's what Theo said months ago... :)

http://www.nabble.com/Re:-kernel-5690:-system-crash-when-running-rtorrent-td14534018.html
Or just browse the web using google.

It's one of these I told you so they love me for. :-)

Of course Henning and others will start trolling again and start telling
you I've no clue (sure they're right. I'm no god, can't know everything..)
but it was not my intention to flame here. I just wanted to show this bug
is not new and that others knew about it for some months now.

So you might compare it to the reports I submitted.
Back then (if I remember correctly) I had two Broadcom (xl0) NICs. Also
routing and co worked.

Since I used another OS for Bittorrent I had no problems anymore (used
rtorrent on the router back then..).

And maybe somebody explains the Bug also in case it gets discovered.
I'm sure it would be pretty interesting. Specialy if somebody who knows
how free() works explains it... :-)

Kind regards,
Sebastian

p.s.
And if you ever wonder where my help is: I send it all to Theo back
then... dmesgs and co. So please don't claim I never did anything.

p.p.s
If you feel the need to flame me mail me personaly. No need to mess up
this thread...



Re: rtorrent + OpenBSD = freeze

2008-02-24 Thread Daniel Andersson
Well this bug wont get fixed.
That's what Theo said months ago... :)
 

Yes. I found the thread where you bashed each other before I made my first
post . I
guess I'll go with FreeBSD or NetBSD instead.


Daniel



Re: rtorrent + OpenBSD = freeze

2008-02-22 Thread nicodache
As promised, and as my server is up again, here is the dmesg.
Now, why is rtorrent freezing the server... not a clue

OpenBSD 4.2 (GENERIC.RAID) #1: Sun Jan  6 22:08:19 CET 2008
[EMAIL PROTECTED]:/sys/arch/i386/compile/GENERIC.RAID
cpu0: Intel Pentium III (GenuineIntel 686-class) 795 MHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem  = 1073311744 (1023MB)
avail mem = 1029783552 (982MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 12/31/99, BIOS32 rev. 0 @
0xeca00, SMBIOS rev. 2.3 @ 0xf2000 (41 entries)
bios0: vendor Compaq version D05/F05 System ROM date 11/15/2002
bios0: Compaq ProLiant DL320
pcibios0 at bios0: rev 2.1 @ 0xeca00/0x3600
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfaca0/160 (8 entries)
pcibios0: PCI Interrupt Router at 000:15:0 (ServerWorks OSB4 rev 0x00)
pcibios0: PCI bus #0 is the last bus
bios0: ROM list: 0xc/0x8000 0xc8000/0x8000 0xd/0x3400 0xe8000/0x8000!
acpi at mainbus0 not configured
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 ServerWorks CNB20LE Host rev 0x05
pchb1 at pci0 dev 0 function 1 ServerWorks CNB20LE Host rev 0x05
pci1 at pchb1 bus 1
pciide0 at pci1 dev 1 function 0 Promise PDC20375 rev 0x02: DMA
wd0 at pciide0 channel 0 drive 0: ST380811AS
wd0: 16-sector PIO, LBA48, 76319MB, 156301488 sectors
wd0(pciide0:0:0): using BIOS timings, Ultra-DMA mode 6
wd1 at pciide0 channel 1 drive 0: ST380811AS
wd1: 16-sector PIO, LBA48, 76319MB, 156301488 sectors
wd1(pciide0:1:0): using BIOS timings, Ultra-DMA mode 6
pciide0: using irq 3 for native-PCI interrupt
siop0 at pci1 dev 2 function 0 Symbios Logic 53c895A rev 0x01: irq
3, using 8K of on-board RAM
scsibus0 at siop0: 16 targets
fxp0 at pci1 dev 3 function 0 Intel 8255x rev 0x08, i82559: irq 11,
address 00:50:8b:e8:56:04
inphy0 at fxp0 phy 1: i82555 10/100 PHY, rev. 4
fxp1 at pci1 dev 4 function 0 Intel 8255x rev 0x08, i82559: irq 11,
address 00:50:8b:e8:56:05
inphy1 at fxp1 phy 1: i82555 10/100 PHY, rev. 4
vga1 at pci0 dev 2 function 0 ATI Rage XL rev 0x27
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
Compaq Netelligent ASMC rev 0x00 at pci0 dev 3 function 0 not configured
piixpm0 at pci0 dev 15 function 0 ServerWorks OSB4 rev 0x51: polling
iic0 at piixpm0
adm1022 at iic0 addr 0x2c not configured
iic0: addr 0x2c 13=3a 14=4d 15=02 17=46 18=64 19=00 20=80 26=30 27=1b
2b=7f 2c=80 37=48 38=c9 39=35 3a=c9 3e=41 3f=c9 40=2b 41=10 43=11
44=0c 47=50 4a=01 4c=10 93=3a 94=4d 95=02 97=46 98=64 99=00 a0=80
a6=30 a7=1b ab=7f ac=80 b7=48 b8=c9 b9=35 ba=c9 be=41 bf=c9 c0=2b
c1=10 c3=11 c4=0c c7=50 ca=01 cc=10: adm1022
pciide1 at pci0 dev 15 function 1 ServerWorks OSB4 IDE rev 0x00: DMA
atapiscsi0 at pciide1 channel 1 drive 0
scsibus1 at atapiscsi0: 2 targets
cd0 at scsibus1 targ 0 lun 0: COMPAQ, CD-ROM CRN-8241B, 2.23 SCSI0
5/cdrom removable
cd0(pciide1:1:0): using PIO mode 4, DMA mode 2
ohci0 at pci0 dev 15 function 2 ServerWorks OSB4/CSB5 USB rev 0x04:
irq 5, version 1.0, legacy support
usb0 at ohci0: USB revision 1.0
uhub0 at usb0: ServerWorks OHCI root hub, rev 1.00/1.00, addr 1
isa0 at mainbus0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
spkr0 at pcppi0
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask f7ed netmask ffed ttymask ffef
pctr: 686-class user-level performance counters enabled
mtrr: Pentium Pro MTRR support
Kernelized RAIDframe activated
cd0(atapiscsi0:0:0): Check Condition (error 0x70) on opcode 0x0
SENSE KEY: Not Ready
 ASC/ASCQ: Medium Not Present
raid0 at root: (RAID Level 1) total number of sectors is 156091648
(76216 MB) as root
dkcsum: wd0 matches BIOS drive 0x80
dkcsum: wd1 matches BIOS drive 0x81



Re: rtorrent + OpenBSD = freeze

2008-02-20 Thread Girish Venkatachalam
On 16:43:00 Feb 19, Daniel Andersson wrote:
 
 Could you please elaborate? The only thing that was working after
 the freeze was the routing. I guess I could try FreeBSD since they
 have pf too. iptables is driving me nuts.
 

Sorry I was out and just came back home.

I think my answer would be irrelevant now since many other people seem
to be facing problems. So there seems to be something wrong somewhere.

I did notice a freeze but I don't think it has anything to do with what
others are saying.

Almost in every case I thought it was due to the tracker being down or
some such bittorrent issue. Since p2p networks have so much churn I am
always wary of concluding anything based on this.

Beyond this I have nothing more to add to this. As to iptables and pf, I
honestly think comparing the two would be like comparing darkness to
light. ;)

On a different note, I  have seen my OpenBSD box freeze badly whenever I
access my Sony SATA DVD R/W drive. I never got time to diagnose the
exact cause. It is a serious issue and something needs to be done about
it soon. In fact I install using FTP or HTTP due to this hairy issue.

Other than that I have seen OpenBSD freeze with the ImageMagick convert(1)
program as well.

Here goes one more freeze. 

I used to have trouble recording voice 
with the new Intel HDA driver, but nowadays that problem does not seem
to be there.

It is a little unnerving to note that OpenBSD userland code sometimes
hangs the whole machine very much like Windoze but then...let us better
be open about it and do something.

I am quite well versed with OpenBSD's kernel code but I need experience
with driver development and fixing such freezes. If someone can throw
some light on the debugging process I can definitely give it a shot.

Would I have to use a serial console and run the kernel with ddb(4) ?

Thanks.

Best,
Girish



Re: rtorrent + OpenBSD = freeze

2008-02-20 Thread Paul Thorn

On Tue, 19 Feb 2008, Brian wrote:


I have seen this freeze with both xl(4) and nfe(4).


Maybe it's time folks start posting their dmesg.

Brian


I've seen this freeze, too. Seems to be related to rtorrent use.
More prevalent when rtorrent is handling multiple torrents.

The machine isn't setup as a router but after the freeze, the 
computer responds to pings, but neither console nor sshd responds 
leaving me no choice but hard reboot.


I originally had assumed that this was due to me using an old
-current, but since others seem to be experiencing similar freezes,
it may be worthwhile to post my dmesg, too.

I'd certainly be willing to help in any ongoing debugging effort.

dmesg below:

OpenBSD 4.2-current (GENERIC) #476: Fri Nov  2 14:41:26 MDT 2007
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Sempron(tm) 2200+ (AuthenticAMD 686-class, 256KB L2 cache) 1.50 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem  = 234385408 (223MB)
avail mem = 218775552 (208MB)
mainbus0 at root
bios0 at mainbus0: AT/286+ BIOS, date 07/07/04, BIOS32 rev. 0 @ 0xfb590, SMBIOS 
rev. 2.2 @ 0xf (34 entries)
bios0: vendor Phoenix Technologies, LTD version 6.00 PG date 07/07/2004
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
pcibios0 at bios0: rev 2.1 @ 0xf/0xdf74
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfdec0/176 (9 entries)
pcibios0: PCI Exclusive IRQs: 3 5 10 11
pcibios0: PCI Interrupt Router at 000:17:0 (VIA VT82C596A ISA rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0xda00 0xd/0x8000!
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 VIA VT8378 PCI rev 0x00
ppb0 at pci0 dev 1 function 0 VIA VT8377 AGP rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 VIA VT8378 VGA rev 0x01: aperture at 
0xe400, size 0x1000
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
uhci0 at pci0 dev 16 function 0 VIA VT83C572 USB rev 0x80: irq 11
uhci1 at pci0 dev 16 function 1 VIA VT83C572 USB rev 0x80: irq 3
uhci2 at pci0 dev 16 function 2 VIA VT83C572 USB rev 0x80: irq 10
ehci0 at pci0 dev 16 function 3 VIA VT6202 USB rev 0x82: irq 5
usb0 at ehci0: USB revision 2.0
uhub0 at usb0 VIA EHCI root hub rev 2.00/1.00 addr 1
viapm0 at pci0 dev 17 function 0 VIA VT8235 ISA rev 0x00
iic0 at viapm0
spdmem0 at iic0 addr 0x50: 256MB DDR SDRAM non-parity PC3200CL3.0
pciide0 at pci0 dev 17 function 1 VIA VT82C571 IDE rev 0x06: ATA133, channel 
0 configured to compatibility, channel 1 configured to compatibility
wd0 at pciide0 channel 0 drive 0: ST3250620A
wd0: 16-sector PIO, LBA48, 238475MB, 488397168 sectors
wd1 at pciide0 channel 0 drive 1: ST3320620A
wd1: 16-sector PIO, LBA48, 305245MB, 625142448 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
wd1(pciide0:0:1): using PIO mode 4, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 0
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: PIONEER, DVD-RW DVR-106D, 1.06 SCSI0 5/cdrom 
removable
cd0(pciide0:1:0): using PIO mode 4, Ultra-DMA mode 2
auvia0 at pci0 dev 17 function 5 VIA VT8233 AC97 rev 0x50: irq 10
ac97: codec id 0x414c4760 (Avance Logic ALC655 rev 0)
audio0 at auvia0
vr0 at pci0 dev 18 function 0 VIA RhineII-2 rev 0x74: irq 11, address 
00:11:5b:0a:44:14
ukphy0 at vr0 phy 1: Generic IEEE 802.3u media interface, rev. 8: OUI 0x004063, 
model 0x0032
usb1 at uhci0: USB revision 1.0
uhub1 at usb1 VIA UHCI root hub rev 1.00/1.00 addr 1
usb2 at uhci1: USB revision 1.0
uhub2 at usb2 VIA UHCI root hub rev 1.00/1.00 addr 1
usb3 at uhci2: USB revision 1.0
uhub3 at usb3 VIA UHCI root hub rev 1.00/1.00 addr 1
isa0 at mainbus0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
it0 at isa0 port 0x290/8: IT87
npx0 at isa0 port 0xf0/16: reported by CPUID; using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask ff6d netmask ff6d ttymask ffef
mtrr: Pentium Pro MTRR support
dkcsum: wd0 matches BIOS drive 0x80
dkcsum: wd1 matches BIOS drive 0x81
root on wd0a swap on wd0b dump on wd0b
WARNING: / was not properly unmounted



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread Stuart Henderson
On 2008/02/19 11:56, Daniel Andersson wrote:
 I tried OpenBSD last autumn but had some trouble running rtorrent.
 Quoting a post I made at a forum:
 
 Every now and then it Freezes. I can't access it through ssh or
 physically.

..
 
 Is there is a fix for it yet?

No, but it has been reported that if the system is doing other things
at the same time, the chance of freezing is much less. (specifically
freezes were seen with rtorrent+top, they were not seen when logging
vmstat output at the same time).

We also have transmission in ports, which works nicely, btw - command
line, GUI, and there's a nice DHTML webinterface (clutch) available
too (clutch is not in ports yet but I have a nearly-finished port for
it).



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread Paul Irofti
On Tue, Feb 19, 2008 at 11:25:09AM +, Stuart Henderson wrote:
 On 2008/02/19 11:56, Daniel Andersson wrote:
  I tried OpenBSD last autumn but had some trouble running rtorrent.
  Quoting a post I made at a forum:
  
  Every now and then it Freezes. I can't access it through ssh or
  physically.
 
 ..
  
  Is there is a fix for it yet?
 
 No, but it has been reported that if the system is doing other things
 at the same time, the chance of freezing is much less. (specifically
 freezes were seen with rtorrent+top, they were not seen when logging
 vmstat output at the same time).
 
 We also have transmission in ports, which works nicely, btw - command
 line, GUI, and there's a nice DHTML webinterface (clutch) available
 too (clutch is not in ports yet but I have a nearly-finished port for
 it).
 

Speaking of transmission, there's a grammar error/typo in DESCR-main:

``This is the command line and daemon clients.''

I think it should be:

``These are the command line and daemon clients.''

And to the OP:

I've been using rtorrent for more than a year now and it never
stopped/blocked/froze/etc.



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread Girish Venkatachalam
On 14:42:37 Feb 19, Paul Irofti wrote:
 I've been using rtorrent for more than a year now and it never
 stopped/blocked/froze/etc.
 

I can second that . Little annoyances here and there but overall
rtorrent works very well under OpenBSD.

If it freezes very likely it is a network issue.

-Girish



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread Daniel Andersson
Thanks for the speedy replies guys!

No, but it has been reported that if the system is doing other things
at the same time, the chance of freezing is much less. (specifically
freezes were seen with rtorrent+top, they were not seen when logging
vmstat output at the same time).

We also have transmission in ports, which works nicely, btw - command
line, GUI, and there's a nice DHTML webinterface (clutch) available
too (clutch is not in ports yet but I have a nearly-finished port for
it).

Okay, too bad. Does transmission support rss, or the watch_directory thingie
that rtorrent has?


On 14:42:37 Feb 19, Paul Irofti wrote:
 I've been using rtorrent for more than a year now and it never
 stopped/blocked/froze/etc.


I can second that . Little annoyances here and there but overall
rtorrent works very well under OpenBSD.

If it freezes very likely it is a network issue.

-Girish

Could you please elaborate? The only thing that was working after
the freeze was the routing. I guess I could try FreeBSD since they
have pf too. iptables is driving me nuts.



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread raven

Girish Venkatachalam ha scritto:

On 14:42:37 Feb 19, Paul Irofti wrote:
  

I've been using rtorrent for more than a year now and it never
stopped/blocked/froze/etc.




I can second that . Little annoyances here and there but overall
rtorrent works very well under OpenBSD.

If it freezes very likely it is a network issue.

-Girish


  
I agree. I use rtorrent and my system never freeze. I think it's a 
network problem. Maybe a network card that freak out...


Francesco



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread bofh
On Feb 19, 2008 10:45 AM, nicodache [EMAIL PROTECTED] wrote:
 I've been using rtorrent on openbsd 4.1 for more than 6 months without
 a single breakdown.
 now, in less than 2 weeks, my 4.2 box (the same hardware, just
 upgraded version) froze twice...

 is it really a network issue ? or is it more like an rtorrent problem ?

You've been using windows too much.  If an application freezes the OS,
it's an OS issue (it still may be an application issue, but no amount
of application tickling of the OS should freeze the OS).


-- 
http://www.glumbert.com/media/shift
http://www.youtube.com/watch?v=tGvHNNOLnCk
This officer's men seem to follow him merely out of idle curiosity.
-- Sandhurst officer cadet evaluation.
Securing an environment of Windows platforms from abuse - external or
internal - is akin to trying to install sprinklers in a fireworks
factory where smoking on the job is permitted.  -- Gene Spafford
learn french:  http://www.youtube.com/watch?v=j1G-3laJJP0feature=related



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread Han Boetes
Please report bugs to libtorrent/rtorrent to the rtorrent
website. He is more than willing to resolve bugs.

As a matter of fact the main developer has a shell on my machine
and regularly testbuilds before releasing stuff to ensure it
builds out of the box on OpenBSD.

~% sudo grep rak /var/log/sshd/current U
Password:
2007-09-07 23:24:13.714581500 Accepted publickey for rakshasa from x.x.x.x port 
3731 ssh2
2007-10-25 16:27:34.605498500 Accepted publickey for rakshasa from x.x.x.x port 
59548 ssh2
2008-01-29 13:49:04.304542500 Accepted publickey for rakshasa from x.x.x.x port 
47815 ssh2


# Han



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread nicodache
I've been using rtorrent on openbsd 4.1 for more than 6 months without
a single breakdown.
now, in less than 2 weeks, my 4.2 box (the same hardware, just
upgraded version) froze twice...

is it really a network issue ? or is it more like an rtorrent problem ?

Cheers,

On Feb 19, 2008 3:53 PM, Girish Venkatachalam
[EMAIL PROTECTED] wrote:
 On 14:42:37 Feb 19, Paul Irofti wrote:
  I've been using rtorrent for more than a year now and it never
  stopped/blocked/froze/etc.
 

 I can second that . Little annoyances here and there but overall
 rtorrent works very well under OpenBSD.

 If it freezes very likely it is a network issue.

 -Girish



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread Brian
--- Daniel Andersson [EMAIL PROTECTED] wrote:

 Hi!
 
 I tried OpenBSD last autumn but had some trouble running rtorrent.

For the longest time, I ran the port net/BitTorrent with a script, and I
recently solved some hardware related issues I had with it.  But I never had
system freezes.

Yesterday, I switched over the net/ktorrent since it supports encryption, which
I am finding I need for some very low seeded torrents, where all the seeds are
running encryption.  I have not experienced any system freezes with
net/ktorrent, and I would definitely recommend it.

Brian

Note: I still run the default fvwm.



  

Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread Daniel Andersson
Yesterday, I switched over the net/ktorrent since it supports encryption,
which
I am finding I need for some very low seeded torrents, where all the seeds
are
running encryption.  I have not experienced any system freezes with
net/ktorrent, and I would definitely recommend it.

Brian

Note: I still run the default fvwm.

Thanks for the suggestion. However, I will not be running a GUI on that box.


'Ive been using rtorrent on openbsd 4.1 for more than 6 months without
a single breakdown.
now, in less than 2 weeks, my 4.2 box (the same hardware, just
upgraded version) froze twice...

is it really a network issue ? or is it more like an rtorrent problem ?

Cheers,

Hrm. I'm not sure if my box froze with 4.1. I remember having other issues
with the integrated NICs though.


I agree. I use rtorrent and my system never freeze. I think it's a
network problem. Maybe a network card that freak out...

Francesco

I don't think it is the NICs, I bought two Intel PRO/1000 something.



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread Tasmanian Devil
 I tried OpenBSD last autumn but had some trouble running rtorrent.
 Quoting a post I made at a forum:

 Every now and then it Freezes. I can't access it through ssh or
 physically.
 The login prompt is blinking normally(I can't input anything though).
 The network still works though since I can browse the world wide web from
 my desktop(openbsd is fw/router).

I tried to find out myself by reading this thread a few times, but I'm
still not sure, so I need to ask: With Every now and then it
Freezes  you mean permanently? Your box doesn't recover by itself
after a minute or two?

Because I've a remotely similar problem at the moment, also since 4.2
or even a bit earlier (I run current). I don't think yet that it's
similar enough to post about it in this thread, and if your box
freezes permanently, it's probably not related.

Tas.



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread Christian Weisgerber
Paul Irofti [EMAIL PROTECTED] wrote:

 Speaking of transmission, there's a grammar error/typo in DESCR-main:
 
 ``This is the command line and daemon clients.''
 
 I think it should be:
 
 ``These are the command line and daemon clients.''

I intended this to refer to _this package_, but I agree that the
concord mismatch is very clunky.  I'll rephrase the sentence.

-- 
Christian naddy Weisgerber  [EMAIL PROTECTED]



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread Jon Olsson
On Tue, Feb 19, 2008 at 06:11:12PM +0100, Daniel Andersson wrote:
 I don't think it is the NICs, I bought two Intel PRO/1000 something.

FWIW, I also saw this freeze while using rtorrent, and I also have 
an Intel PRO/1000 NIC:

em0 at pci0 dev 2 function 0 Intel PRO/1000MT (82540EM) rev 0x02: irq 10, 
address 00:c0:9f:1e:26:2c

I have no more data than this, it's just a mere 'me too' and one thing
we have in common (the NIC).

Cheers,
-- 
Jon



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread Bernhard Leiner
On 19/02/2008, nicodache [EMAIL PROTECTED] wrote:
 I've been using rtorrent on openbsd 4.1 for more than 6 months without
 a single breakdown.
 now, in less than 2 weeks, my 4.2 box (the same hardware, just
 upgraded version) froze twice...

I have very similar experiences. Since my upgrade to 4.2 and rtorrent
0.7.4 + libtorrent 0.11.4 my system (soekris 4801) freezes after
running rtorrent for a couple of hours. I had no problems at all
before upgrading.

Some interesting facts:
  - no running daemon is responding any more (sshd, dhcpd, smbd)
  - no response to pings
  - no response to commands via serial connection
BUT
  - routing and NAT still works

Some debug output can be found below:

ddb trace
Debugger(d0b1fc00,d3c95700,d3bc6016,f9040001,3f8) at Debugger+0x4
comintr(d0b1f000) at comintr+0x9f
Xrecurse_legacy4() at Xrecurse_legacy4+0xad
--- interrupt ---
apm_cpu_idle(c0,d078d380,d078d200,7fff,d0335a7b) at apm_cpu_idle+0x42
idle_loop(d08c7f00,4,d08c7f18,d0332d66,d08c7f00) at idle_loop+0x5
sleep_finish(d08c7f00,1,4,d06979cc,0) at sleep_finish+0x4d
tsleep(d078d200,4,d06979cc,0) at tsleep+0x7a
uvm_scheduler(d078d1dc,3,0,d064e610,2) at uvm_scheduler+0x1b
main(0,0,0,0,0) at main+0x713
ddb ps
   PID   PPID   PGRPUID  S   FLAGS  WAIT  COMMAND
 12318  30727  30727  0  3  0x4000  km_alloc1wnewsyslog
 30727  24283  30727  0  3  0x4080  pause sh
 24283   8572   8572  0  30x80  piperdcron
  5981   9083   5981   1001  3  0x4002  km_alloc1wrtorrent
  9083  28865   9083   1001  3  0x4082  pause ksh
 28865  1  28865   1001  30x80  selectscreen
 11974  1  11974  0  3  0x4002  inode login
  8572  1   8572  0  3  0x2000  km_alloc1wcron
 20227  1  20227  0  30x81  selectnmbd
  5055   9940   9940  0  3   0x181  pause smbd
  9940  1   9940  0  3   0x181  selectsmbd
  4635  1   4635  0  30x80  selectsshd
 23343  1  23343  0  3   0x180  selectinetd
  7434  11543  11543 74  3   0x180  bpf   pflogd
 11543  1  11543  0  30x80  netio pflogd
 16394  20490  20490 73  3   0x180  poll  syslogd
 20490  1  20490  0  30x88  netio syslogd
 19176  1  19176 77  3   0x180  poll  dhclient
 13003  1  13276  0  30x82  poll  dhclient
12  0  0  0  30x100200  crypto_wait   crypto
11  0  0  0  30x100200  aiodoned  aiodoned
10  0  0  0  30x100200  syncerupdate
 9  0  0  0  30x100200  cleaner   cleaner
 8  0  0  0  30x100200  reaperreaper
 7  0  0  0  30x100200  inode pagedaemon
 6  0  0  0  30x100200  pftm  pfpurge
 5  0  0  0  30x100200  usbtskusbtask
 4  0  0  0  30x100200  usbevtusb0
 3  0  0  0  30x100200  bored syswq
 2  0  0  0  30x100200  kmalloc   kmthread
 1  0  1  0  3  0x4080  wait  init
 0 -1  0  0  3 0x80200  scheduler swapper



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread Pierre Riteau
On Tue, Feb 19, 2008 at 08:08:50PM +0100, Jon Olsson wrote:
 On Tue, Feb 19, 2008 at 06:11:12PM +0100, Daniel Andersson wrote:
  I don't think it is the NICs, I bought two Intel PRO/1000 something.
 
 FWIW, I also saw this freeze while using rtorrent, and I also have 
 an Intel PRO/1000 NIC:
 
 em0 at pci0 dev 2 function 0 Intel PRO/1000MT (82540EM) rev 0x02: irq 10, 
 address 00:c0:9f:1e:26:2c
 
 I have no more data than this, it's just a mere 'me too' and one thing
 we have in common (the NIC).
 
 Cheers,
 -- 
 Jon
 

I have seen this freeze with both xl(4) and nfe(4).

--
Pierre Riteau



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread Daniel Andersson
I have very similar experiences. Since my upgrade to 4.2 and rtorrent
0.7.4 + libtorrent 0.11.4 my system (soekris 4801) freezes after
running rtorrent for a couple of hours. I had no problems at all
before upgrading.

Some interesting facts:
 - no running daemon is responding any more (sshd, dhcpd, smbd)
 - no response to pings
 - no response to commands via serial connection
BUT
  - routing and NAT still works

Yes. That is exactly how it was for me too.


I tried to find out myself by reading this thread a few times, but I'm
still not sure, so I need to ask: With Every now and then it
Freezes  you mean permanently? Your box doesn't recover by itself
after a minute or two?

Because I've a remotely similar problem at the moment, also since 4.2
or even a bit earlier (I run current). I don't think yet that it's
similar enough to post about it in this thread, and if your box
freezes permanently, it's probably not related.

Tas.

Yes. it is a permanent freeze. It would freeze sometime at night, and the
next morning it would still be frozen. Only the routing part works.

Daniel Andersson



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread Julien Cabillot
On mar, 2008-02-19 at 20:08 +0100, Jon Olsson wrote:
 On Tue, Feb 19, 2008 at 06:11:12PM +0100, Daniel Andersson wrote:
  I don't think it is the NICs, I bought two Intel PRO/1000 something.
 
 FWIW, I also saw this freeze while using rtorrent, and I also have 
 an Intel PRO/1000 NIC:
 
 em0 at pci0 dev 2 function 0 Intel PRO/1000MT (82540EM) rev 0x02: irq 10, 
 address 00:c0:9f:1e:26:2c
 
 I have no more data than this, it's just a mere 'me too' and one thing
 we have in common (the NIC).
 
 Cheers,

me too :) with an
em0 at pci2 dev 1 function 0 Intel PRO/1000XT (82544EI) rev 0x02: apic
4 int 0 (irq 10), address 00:40:d0:2e:96:ef
rtorrent freeze some time when I have many torrent in download, now I'm
using btpd since 1 week and I have no freeze anymore.



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread Brian
--- Pierre Riteau [EMAIL PROTECTED] wrote:


 I have seen this freeze with both xl(4) and nfe(4).

Maybe it's time folks start posting their dmesg.

Brian


  

Looking for last minute shopping deals?  
Find them fast with Yahoo! Search.  
http://tools.search.yahoo.com/newsearch/category.php?category=shopping



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread Jacob Winther
I've also experienced issues with rtorrent on 4.2. During a busy  
(freeleech) period where I had more than my usual number of torrent  
and pairs, the system would freeze after approx 3 hrs. This happened  
regularly for the 3 or so days that things were busy. When the system  
froze I found I could still ping it, but it was otherwise unresponsive  
and required a hard boot. I was not able to find any evidence after  
the crash. The only other process running on the system is screen +  
irc with very low traffic. The otherall traffic for rtorfrent was  
fairly low as I'm rate limited to about 1Mb/s international. This was  
on a vmware server. Since then I've had no issues and regularly  
transfer files from that system at 25Mb/s or proxy traffic at about  
85Mb/s.


Cheers
Jacob




On 20/02/2008, at 9:05 AM, Pierre Riteau wrote:


On Tue, Feb 19, 2008 at 08:08:50PM +0100, Jon Olsson wrote:

On Tue, Feb 19, 2008 at 06:11:12PM +0100, Daniel Andersson wrote:

I don't think it is the NICs, I bought two Intel PRO/1000 something.


FWIW, I also saw this freeze while using rtorrent, and I also have
an Intel PRO/1000 NIC:

em0 at pci0 dev 2 function 0 Intel PRO/1000MT (82540EM) rev 0x02:  
irq 10, address 00:c0:9f:1e:26:2c


I have no more data than this, it's just a mere 'me too' and one  
thing

we have in common (the NIC).

Cheers,
--
Jon



I have seen this freeze with both xl(4) and nfe(4).

--
Pierre Riteau




Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread K K
I've left rTorrent running on 4.1 for weeks on end, (on both i386 and
Sparc64), never had the OS freeze.   I will try it again with 4.2, see
if the results are different.

Recently I've seen several unexplained freezes on very simple 4.2
servers (e.g running nothing but BIND and arpwatch), similar to the
symptoms reported earlier in this thread with rTorrent.


On Feb 19, 2008 10:46 AM, bofh [EMAIL PROTECTED] wrote:
 You've been using windows too much.  If an application freezes the OS,
 it's an OS issue (it still may be an application issue, but no amount
 of application tickling of the OS should freeze the OS).

Agreed.  I'd bet the issue boils down to networking and/or disk I/O.

The rTorrent application exercises so many facets of the OS,  myriad
places where it could trigger a kernel/disk/routing/pf/etc bug, one
which lesser applications wouldn't trip.

If there's interest in putting up a tracker for a bunch of OpenBSD
ports/packages/distfiles torrents, I'll gladly assist in
exercising/exorcising this problem by running a seedbox.

Kevin



Re: rtorrent + OpenBSD = freeze

2008-02-19 Thread Matthew Dempsky
On 2/19/08, Brian [EMAIL PROTECTED] wrote:
 Maybe it's time folks start posting their dmesg.

Since I can recall rtorrent causing similar symptoms on my OpenBSD
firewall as well, I'll post mine too:

OpenBSD 4.0 (GENERIC) #1107: Sat Sep 16 19:15:58 MDT 2006
[EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/GENERIC
cpu0: AMD Geode NX (AuthenticAMD 686-class, 256KB L2 cache) 1.40 GHz
cpu0: 
FPU,V86,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE
real mem  = 637038592 (622108K)
avail mem = 572289024 (558876K)
using 4256 buffers containing 31952896 bytes (31204K) of memory
mainbus0 (root)
bios0 at mainbus0: AT/286+(1f) BIOS, date 10/18/05, BIOS32 rev. 0 @
0xfb490, SMBIOS rev. 2.2 @ 0xf (33 entries)
apm0 at bios0: Power Management spec V1.2
apm0: AC on, battery charge unknown
apm0: flags 70102 dobusy 1 doidle 1
pcibios0 at bios0: rev 2.1 @ 0xf/0xdef4
pcibios0: PCI IRQ Routing Table rev 1.0 @ 0xfde60/144 (7 entries)
pcibios0: PCI Exclusive IRQs: 3 5 9 10 11
pcibios0: PCI Interrupt Router at 000:02:0 (SiS 85C503 System rev 0x00)
pcibios0: PCI bus #1 is the last bus
bios0: ROM list: 0xc/0x8000 0xc8000/0x8000!
cpu0 at mainbus0
pci0 at mainbus0 bus 0: configuration mode 1 (no bios)
pchb0 at pci0 dev 0 function 0 SiS 741 PCI rev 0x03
ppb0 at pci0 dev 1 function 0 SiS 648FX AGP rev 0x00
pci1 at ppb0 bus 1
vga1 at pci1 dev 0 function 0 SiS 6330 VGA rev 0x00: aperture at
0xd800, size 0x40
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
pcib0 at pci0 dev 2 function 0 SiS 964 ISA rev 0x36
pciide0 at pci0 dev 2 function 5 SiS 5513 EIDE rev 0x01: 741: DMA,
channel 0 configured to compatibility, channel 1 configured to
compatibility
wd0 at pciide0 channel 0 drive 0: ST340015A
wd0: 16-sector PIO, LBA, 38166MB, 78165360 sectors
wd0(pciide0:0:0): using PIO mode 4, Ultra-DMA mode 5
atapiscsi0 at pciide0 channel 1 drive 1
scsibus0 at atapiscsi0: 2 targets
cd0 at scsibus0 targ 0 lun 0: ATAPI-CD, ROM-DRIVE-52MAX, 52PP SCSI0
5/cdrom removable
cd0(pciide0:1:1): using PIO mode 4, Ultra-DMA mode 2
auich0 at pci0 dev 2 function 7 SiS 7012 AC97 rev 0xa0: irq 5, SiS7012 AC97
ac97: codec id 0x414c4760 (Avance Logic ALC655 rev 0)
audio0 at auich0
ohci0 at pci0 dev 3 function 0 SiS 5597/5598 USB rev 0x0f: irq 10,
version 1.0, legacy support
usb0 at ohci0: USB revision 1.0
uhub0 at usb0
uhub0: SiS OHCI root hub, rev 1.00/1.00, addr 1
uhub0: 3 ports with 3 removable, self powered
ohci1 at pci0 dev 3 function 1 SiS 5597/5598 USB rev 0x0f: irq 11,
version 1.0, legacy support
usb1 at ohci1: USB revision 1.0
uhub1 at usb1
uhub1: SiS OHCI root hub, rev 1.00/1.00, addr 1
uhub1: 3 ports with 3 removable, self powered
ohci2 at pci0 dev 3 function 2 SiS 5597/5598 USB rev 0x0f: irq 9,
version 1.0, legacy support
usb2 at ohci2: USB revision 1.0
uhub2 at usb2
uhub2: SiS OHCI root hub, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
ehci0 at pci0 dev 3 function 3 SiS 7002 USB rev 0x00: irq 3
usb3 at ehci0: USB revision 2.0
uhub3 at usb3
uhub3: SiS EHCI root hub, rev 2.00/1.00, addr 1
uhub3: 8 ports with 8 removable, self powered
sis0 at pci0 dev 4 function 0 SiS 900 10/100BaseTX rev 0x91: irq 11,
address 00:14:2a:b7:c9:17
rlphy0 at sis0 phy 9: RTL8201L 10/100 PHY, rev. 1
rl0 at pci0 dev 11 function 0 Accton MPX 5030/5038 rev 0x10: irq 11,
address 00:e0:29:58:9b:eb
rlphy1 at rl0 phy 0: RTL internal PHY
isa0 at pcib0
isadma0 at isa0
pckbc0 at isa0 port 0x60/5
pckbd0 at pckbc0 (kbd slot)
pckbc0: using irq 1 for kbd slot
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pcppi0 at isa0 port 0x61
midi0 at pcppi0: PC speaker
spkr0 at pcppi0
lpt0 at isa0 port 0x378/4 irq 7
it0 at isa0 port 0x290/8: IT87
npx0 at isa0 port 0xf0/16: using exception 16
pccom0 at isa0 port 0x3f8/8 irq 4: ns16550a, 16 byte fifo
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 0: 1.44MB 80 cyl, 2 head, 18 sec
biomask ff4d netmask ff4d ttymask ffcf
pctr: user-level cycle counter enabled
mtrr: Pentium Pro MTRR support
uhidev0 at uhub0 port 1 configuration 1 interface 0
uhidev0: Qtronix Generic USB K/B, rev 1.10/0.01, addr 2, iclass 3/1
ukbd0 at uhidev0: 8 modifier keys, 6 key codes
wskbd1 at ukbd0 mux 1
wskbd1: connecting to wsdisplay0
uhidev1 at uhub0 port 1 configuration 1 interface 1
uhidev1: Qtronix Generic USB K/B, rev 1.10/0.01, addr 2, iclass 3/1
uhidev1: 3 report ids
ums0 at uhidev1 reportid 1: 3 buttons and Z dir.
wsmouse0 at ums0 mux 0
uhid0 at uhidev1 reportid 2: input=1, output=0, feature=0
uhid1 at uhidev1 reportid 3: input=4, output=0, feature=0
dkcsum: wd0 matches BIOS drive 0x80
root on wd0a
rootdev=0x0 rrootdev=0x300 rawdev=0x302