Re: Multiple stability issues with r208557, r208809 on amd64

2010-06-08 Thread Garrett Cooper
On Tue, Jun 8, 2010 at 4:59 PM, Xin LI wrote: > Do you mean between the two revisions or something?  I committed > r208557 which doesn't seem likely to cause any runtime issue; 208809 > is isp(4) change which is not part of your kernel... > > [delp...@delta] /usr/src> svn log -r 208557 > -

Re: Multiple stability issues with r208557, r208809 on amd64

2010-06-08 Thread Xin LI
Do you mean between the two revisions or something? I committed r208557 which doesn't seem likely to cause any runtime issue; 208809 is isp(4) change which is not part of your kernel... [delp...@delta] /usr/src> svn log -r 208557 ---

Re: patch submission for multiple branches

2010-06-08 Thread Garrett Cooper
On Tue, Jun 8, 2010 at 3:05 PM, Xin LI wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi, Tom, > > On 2010/06/08 14:42, Tom Couch wrote: >> I have updated the twa driver (src/sys/dev/twa) and generated patches >> against RELENG_7 and RELENG_8. >> I submitted the patches separately

Re: patch submission for multiple branches

2010-06-08 Thread Xin LI
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, Tom, On 2010/06/08 14:42, Tom Couch wrote: > I have updated the twa driver (src/sys/dev/twa) and generated patches > against RELENG_7 and RELENG_8. > I submitted the patches separately in PR 147694 (RELENG_7) and PR 147695 > (RELENG_8). > PR 147

Multiple stability issues with r208557, r208809 on amd64

2010-06-08 Thread Garrett Cooper
Hi, I'm noticing a lot more LORs nowadays and my development box is livelocking a lot. The cases I've seen with LORs are: 1. When unplugging a Dell USB keyboard with a USB hub on r208557; this wasn't reproducible on r208809 though. 2. Creating DOS floppies in a build environment (ch

patch submission for multiple branches

2010-06-08 Thread Tom Couch
I have updated the twa driver (src/sys/dev/twa) and generated patches against RELENG_7 and RELENG_8. I submitted the patches separately in PR 147694 (RELENG_7) and PR 147695 (RELENG_8). PR 147694 has been closed as a duplicate of PR 147695. What happens to the patch for RELENG_7 (PR 147694)? What

Re: RFC: New event timers infrastructure

2010-06-08 Thread Alexander Motin
Brandon Gooch wrote: > I'm giving http://people.freebsd.org/~mav/et.20100607.patch a go right now... > > After patching and recompiling the kernel, I'm up and running. > > What information/feedback would you like to see from us users? As always: what is working and especially what is not. What t

VM ware crash with current...

2010-06-08 Thread Randall Stewart
Hi all: I am getting a mysterious crash on my vmware machine running head. http://people.freebsd.org/~rrs/crash1.png and http://people.freebsd.org/~rrs/crash2.png are snapshots. If I run the same kernel with one core.. no problem Note also this does NOT have SCTP in it.. I took it out to make s

Re: RFC: New event timers infrastructure

2010-06-08 Thread Brandon Gooch
On Tue, Jun 8, 2010 at 9:40 AM, Alexander Motin wrote: > Brandon Gooch wrote: >> Alexander, do you feel that the code is at a stage where meaningful >> user testing can occur? > > I think yes. I've touched a lot of legacy code, so it would be nice to > know what I may have broken. For example, i82

Re: ports/139483: x11-fm/thunar name is in lowercase while package name is in uppercase

2010-06-08 Thread vermaden
> I agree with you that this is a bit inconsistent and this had > been done right in the first place when the port was created. > But changing it now - I fear to much problems which may occur by very less > gain on th eother hand and this is why I'll not change the package name. I also agree with

Re: RFC: New event timers infrastructure

2010-06-08 Thread Alexander Motin
Brandon Gooch wrote: > Alexander, do you feel that the code is at a stage where meaningful > user testing can occur? I think yes. I've touched a lot of legacy code, so it would be nice to know what I may have broken. For example, i8254 and RTC drivers now more dependent on attaching to PnP/ACPI re

Re: RFC: New event timers infrastructure

2010-06-08 Thread Brandon Gooch
On Tue, Jun 8, 2010 at 12:24 AM, Tsuyoshi Ozawa wrote: > 2010/6/6, Alexander Motin : >> Hi. >> >> Most of x86 systems now has at least 4 types of event timers: i8254, >> RTC, LAPIC and HPET. Respective code in kernel is very tangled, heavily >> hardcoded and absolutely not scalable. I have reimple

Re: RFC: New event timers infrastructure

2010-06-08 Thread Tsuyoshi Ozawa
2010/6/6, Alexander Motin : > Hi. > > Most of x86 systems now has at least 4 types of event timers: i8254, > RTC, LAPIC and HPET. Respective code in kernel is very tangled, heavily > hardcoded and absolutely not scalable. I have reimplemented it, trying > to solve these issues. > > I did such thing

Panic on S3 suspend call.

2010-06-08 Thread Alexander Motin
Hi. Just noted that fresh HEAD i386 system panics on suspend request when build with INVARIANTS and WITNESS: panic: mutex ACPI global lock owned at ../../../kern/kern_event.c:1899 cpuid = 1 KDB: enter: panic [ thread pid 1047 tid 100138 ] Stopped at 0x408d29df: movl$0,0x40dded34 db>

Re: ioapic_assign_cpu() on active level-triggered interrupt

2010-06-08 Thread Alexander Motin
Hi. John Baldwin wrote: > On Friday 04 June 2010 2:30:13 pm Alexander Motin wrote: >> I am working on driver for HPET event timers. It works mostly fine, >> except after some cases when ioapic_assign_cpu() called while timer is >> active. Under interrupt rate of 10KHz it is enough a dozen cpuset r