kernel/6491: amd64 kernel sometimes fails to boot on Thinkpad T410s

2010-10-15 Thread Laurence Tratt
>Number: 6491 >Category: kernel >Synopsis: amd64 kernel sometimes fails to boot on Thinkpad T410s >Confidential: yes >Severity: serious >Priority: medium >Responsible:bugs >State: open >Quarter: >Keywords: >Date-Required: >Class:

user/6490: relayd check https - ssl read timeout

2010-10-15 Thread sthen
>Number: 6490 >Category: user >Synopsis: relayd check https - ssl read timeout >Confidential: yes >Severity: serious >Priority: medium >Responsible:bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter

Un luogo unico per un momento indimenticabile

2010-10-15 Thread SISPOSAEXPO
[IMAGE]

Re: kernel/6486: MCLGETI breaks re(4)

2010-10-15 Thread Alexey Suslikov
On Fri, Oct 15, 2010 at 17:30, Alexey Suslikov wrote: > Claudio Jeker wrote: > >> On Wed, Oct 13, 2010 at 03:33:27PM +0600, Anton Maksimenkov wrote: >> > 2010/10/13 Claudio Jeker : >> > > Most probably re(4) was unable to allocate >> > > clusters and now the RX ring is empty and stuck, in the wors

Re: kernel/6486: MCLGETI breaks re(4)

2010-10-15 Thread Alexey Suslikov
Claudio Jeker wrote: > On Wed, Oct 13, 2010 at 03:33:27PM +0600, Anton Maksimenkov wrote: > > 2010/10/13 Claudio Jeker : > > > Most probably re(4) was unable to allocate > > > clusters and now the RX ring is empty and stuck, in the worst case you hit > > > an interrupt storm. > > > > BTW, in worst

user/6489: opencvs diff exit status discrepancy

2010-10-15 Thread Michael W. Bombardieri
>Number: 6489 >Category: user >Synopsis: opencvs diff exit status discrepancy >Confidential: yes >Severity: serious >Priority: medium >Responsible:bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-

Re: kernel/6486: MCLGETI breaks re(4)

2010-10-15 Thread Claudio Jeker
On Wed, Oct 13, 2010 at 03:33:27PM +0600, Anton Maksimenkov wrote: > 2010/10/13 Claudio Jeker : > > Most probably re(4) was unable to allocate > > clusters and now the RX ring is empty and stuck, in the worst case you hit > > an interrupt storm. > > BTW, in worst case (I used ping -f, just can't f

Re: system/6488

2010-10-15 Thread jsg
Synopsis: Relayd crashes randomly under load State-Changed-From-To: open->closed State-Changed-By: jsg State-Changed-When: Fri Oct 15 02:57:21 MDT 2010 State-Changed-Why: should be fixed in 4.8 and -current, reopen if it still occurs

Re: system/6487: fsck not accepting disklabel uid

2010-10-15 Thread Jiri B.
> This works iff you list the partition by uid in /etc/fstab, e.g. > > $ uid=d3f6b8c752d5141a.a > $ grep $uid /etc/fstab > d3f6b8c752d5141a.a / ffs rw 1 1 > $ fsck -f $uid > ** /dev/wd0a (d3f6b8c752d5141a.a) (NO WRITE) > ** Last Mounted on / > ** Root file system > ** Phase 1 - Check Blocks and Siz