Hi Stefan,
We understand what you mean. No one wants there to be bugs but if
there are they need to be documented to be addressed.
My current problem, which is a big one for me, is that a long used
1394 drive with mostly files that are only ever read - my CD
collection ripped to ogg - has, after upgrading to 2.6.17, started to
have MANY files which my system says are no longer viable. I did some
fsck stuff and it started giving me lots of reports about bad things.
I let fsck fix them but it didn't fix any of my files.
In line with this problem there are files that work on some days
and on other days do not. Weird. Unfortunately it only started with
2.6.17 but I tried going back to 2.6.16 and the files acted the same
way so if it's a 1394 problem caused by 2.6.17 it's potentially on the
drive with damage done now. Bummer...
There have been no messages in dmesg that make any sense to me or
seem like they should be posted here. I continue to watch for that.
I do not even know how to enter an actionable bug report on
something like this, but this drive has been up and running for a
couple of year and has worked great. I've not had any power failures
in quite a long time - probably over 6 months - and the system and the
drives run on a UPS so they should be relatively safe. It's possible
that the drive is going bad but to me that's just an excuse on my part
for saying I don't know how to find the real answer.
Again, I don't know what to do at this point. I've been dealing
with this for 2-3 weeks now, since whenever 2.6.17 came out.
- Mark
On 7/2/06, Stefan Richter <stefanr@xxxxxxxxxxxxxxxxx> wrote:
> Hi all,
>
> well, nobody _really_ wants bug reports, but you know what I mean. I
> wanted to take a look at some of the problems reported here during the
> last months but simply lost track of who reported what kind of issue.
> Two types I vaguely remember:
> - breakage of iso transmission since Linux 2.6.13
> - error in selfID reception or invalid node ID after reset since 2.4.21
>
> Therefore, people who have the patience, please use bugzilla.kernel.org
> to pin up everything which you identified as a kernel bug. I am afraid
> that won't speed up bug-fixing much (especially of iso problems; these
> are not my cup of tea), but addresses of reporters to ask back don't get
> lost anymore then.
>
> http://bugzilla.kernel.org/buglist.cgi?product=Drivers&component=IEEE1394
> shows all ieee1394 bugs to avoid duplicate entries. The "Edit this
> Query" link at the bottom lets you filter the query further, e.g. narrow
> it down to New and Assigned bugs. Several distributors have bugzillas
> too, but most if not all ieee1394 kernel bugs are actually "upstream" bugs.
> --
> Stefan Richter
> -=====-=-==- -=== ---=-
> http://arcgraph.de/sr/
>
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> mailing list Linux1394-user@xxxxxxxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/linux1394-user
>
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
|
