meteor2mc-devel Mailing List for Meteor-II Multi-Channel Linux Driver
Status: Beta
Brought to you by:
furlongm
You can subscribe to this list here.
2004 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
---|---|---|---|---|---|---|---|---|---|---|---|---|
2009 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Marcus F. <fur...@al...> - 2009-02-11 17:15:55
|
test -- Marcus Furlong |
From: <ben...@id...> - 2004-05-25 08:30:24
|
Dear Open Source developer I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate. You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it. With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development. With many thanks for your participation, Benno Luthiger PS: The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/. We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list. _______________________________________________________________________ Benno Luthiger Swiss Federal Institute of Technology Zurich 8092 Zurich Mail: benno.luthiger(at)id.ethz.ch _______________________________________________________________________ |
From: Spencer E. O. <ol...@um...> - 2004-05-01 09:24:46
|
I've been working without the bigphysarea patch. I also figured out a few bugs in the driver and fixed a number of them. I am currently going through the code and trying to make it SMP safe. Though I have a single CPU system, I like to use the preempt patch from Robert Love, so our code needs to be SMP safe. For the most part xawtv works just fine now. There only seems to be one problem that is probably related to a race condition in the driver that needs to be protected against. The stream_buf[2123] kalloc'ation was attempted because I have been forced to use mem=800M to load the meteor2mc driver. It failed because kmalloc cannot allocate more than 1<<17 bytes at a time. I'll send more detailed notes about this later. I fixed this by adding 2 different methods of limiting the number of stream_bufs that can be kalloc'ated at a time. More details later, Spencer Give me a day or two and I'll send you a 'cvs diff -u' patch. On Fri, 2004-04-30 at 05:23, "Marcus Furlong" <fur...@ho...> wrote: > Just had a real quick look at this, will check more tomorrow... > > >kernel with all the appropriate patches last night. (I'm currently > >running 2.4.24 and will just compiled 2.4.26 w/ kdb). > > Is this with the bigphysarea patch? > > >From your logs... > > pr 27 18:54:19 cw-bec kernel: meteor2mc [via_setup_himem_bufs]: buffer > size/num changed (110592->110592/0->1) > Apr 27 18:54:19 cw-bec kernel: meteor2mc [via_setup_himem_bufs]: stream_buf > == NULL > Apr 27 18:54:19 cw-bec kernel: meteor2mc [via_setup_himem_bufs]: > kmalloc(stream_buf[2123]) failed > > On the website I noted that using bigphysarea is currently broken here. It > was last tested working with 2.4.20, can you try with that? Or else try > without bigphysarea. > > Marcus. > > _________________________________________________________________ > Add photos to your messages with MSN 8. Get 2 months FREE*. > http://join.msn.com/?page=features/featuredemail ------------ Spencer Olson Department of Physics University of Michigan Spe...@um... tel: 734-647-9030 tel: 734-763-2544 fax: 734-764-5153 Common sense and a sense of humor are the same thing, moving at different speeds. A sense of humor is just common sense, dancing. -- Clive James |
From: Marcus F. <fur...@ho...> - 2004-04-30 04:23:50
|
Just had a real quick look at this, will check more tomorrow... >kernel with all the appropriate patches last night. (I'm currently >running 2.4.24 and will just compiled 2.4.26 w/ kdb). Is this with the bigphysarea patch? From your logs... pr 27 18:54:19 cw-bec kernel: meteor2mc [via_setup_himem_bufs]: buffer size/num changed (110592->110592/0->1) Apr 27 18:54:19 cw-bec kernel: meteor2mc [via_setup_himem_bufs]: stream_buf == NULL Apr 27 18:54:19 cw-bec kernel: meteor2mc [via_setup_himem_bufs]: kmalloc(stream_buf[2123]) failed On the website I noted that using bigphysarea is currently broken here. It was last tested working with 2.4.20, can you try with that? Or else try without bigphysarea. Marcus. _________________________________________________________________ Add photos to your messages with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail |
From: Spencer E. O. <ol...@um...> - 2004-04-29 16:13:51
|
Marcus, I'm sending this also to the email list so that we can keep a better record of these emails. Attached I've got some relevant logs from the various sources. I've also included a processed oops file (named oopsed.out) from when xawtv dies. Looking through the /var/log/messages (relevant parts also included in tar ball), you can easily see that the problem is that the highmem buffers are being prematurly freed. (The oops corroborates this analysis). The one thing that I can't seem to figure out is why there isn't other log information in my /var/log/messages that indicates why via_free_himem_bufs was called. As I looked through the source, I found that I should expect a number of debug messages before the specific via_free_himem_bufs debug messages that I see. To see where this occurs, look near the end of my messages file. In this log you will find that I started up xawtv, went to fullscreen mode, then killed it (xawtv.log). I then started it up again, went to fullscreen mode and went out of fullscreen mode whereupon xawtv died (xawtv-2.log). This error seems to only occur immediately when I go out of fullscreen mode. Because I can't seem to find why via_free_himem_bufs is being called by reading the logs and source, I'm going to do this again with kdb enabled on the machine and get a stack trace. I just finished recompiling my kernel with all the appropriate patches last night. (I'm currently running 2.4.24 and will just compiled 2.4.26 w/ kdb). (There is another bothersome thing about when I start xawtv the first time that it doesn't seem to work until I go into fullscreen mode. The second time that I start up xawtv, it works from the go, as well as in fullscreen mode. I'm not as worried about this bug yet as it doesn't cause kernel oopses.) I'll send you what I find about the stack trace that I see in kdb. Spencer ------------ Spencer Olson Department of Physics University of Michigan Spe...@um... tel: 734-647-9030 tel: 734-763-2544 fax: 734-764-5153 Common sense and a sense of humor are the same thing, moving at different speeds. A sense of humor is just common sense, dancing. -- Clive James |
From: Marcus F. <fur...@ho...> - 2004-04-17 22:57:14
|
test _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963 |