Hi, Many moons ago (well, a moon and a half ago) I submitted a bug report about a kernel and / or Reiser file system problem whose symptom was fairly serious (applications hanging, a whole file system effectively out of service and snagging every process that tried to access it, all accompanied by a clot of kernel messages). See <https://bugzilla.novell.com/show_bug.cgi?id=129623> for the details. Now, all these weeks later, its status is still "NEW," as if no one has even looked at it. What can or should I do to get this investigated? Randall Schulz
Randall R Schulz <rschulz@sonic.net> writes:
Hi,
Many moons ago (well, a moon and a half ago) I submitted a bug report about a kernel and / or Reiser file system problem whose symptom was fairly serious (applications hanging, a whole file system effectively out of service and snagging every process that tried to access it, all accompanied by a clot of kernel messages). See <https://bugzilla.novell.com/show_bug.cgi?id=129623> for the details.
Now, all these weeks later, its status is still "NEW," as if no one has even looked at it.
It has been assigned to Chris, one of our ReiserFS experts, and yes, nothing further seems to have happened. Is this a reproducable problem? In that case you should mention it.
What can or should I do to get this investigated?
If it's a critical bug, you could ask me. The bug is rated as normal and the developer is busy working on other stuff. Such kind of bugs will have a high priority in the beta phase but after release this might go under. I've pinged again... Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Andreas, On Friday 02 December 2005 23:35, Andreas Jaeger wrote:
Randall R Schulz <rschulz@sonic.net> writes:
Hi,
Many moons ago (well, a moon and a half ago) I submitted a bug report about a kernel and / or Reiser file system problem whose symptom was fairly serious (applications hanging, a whole file system effectively out of service and snagging every process that tried to access it, all accompanied by a clot of kernel messages). See <https://bugzilla.novell.com/show_bug.cgi?id=129623> for the details.
Now, all these weeks later, its status is still "NEW," as if no one has even looked at it.
It has been assigned to Chris, one of our ReiserFS experts, and yes, nothing further seems to have happened.
Is this a reproducable problem? In that case you should mention it.
I've been loath to try running KAudioCreator again, but I suppose I could give it a try. I've got a large batch of CDs to process, since I lost a hard drive and did not have those files backed up. Now that I think if of it, it probably would have been a good idea to say something about the hardware, since it's one of them new-fangled SATA drives...
What can or should I do to get this investigated?
If it's a critical bug, you could ask me. The bug is rated as normal and the developer is busy working on other stuff. Such kind of bugs will have a high priority in the beta phase but after release this might go under. I've pinged again...
I certainly consider it critical--the symptoms are pretty nasty and it seems to be a kernel- or driver- or file-system-level problem. This is the first bug I've submitted to that system and I didn't know how to treat the priority (or even whether an outside submitter could actually change it) so I left it at its default setting.
Andreas
Randall Schulz
Randall R Schulz <rschulz@sonic.net> writes:
Andreas,
On Friday 02 December 2005 23:35, Andreas Jaeger wrote:
Randall R Schulz <rschulz@sonic.net> writes:
Hi,
Many moons ago (well, a moon and a half ago) I submitted a bug report about a kernel and / or Reiser file system problem whose symptom was fairly serious (applications hanging, a whole file system effectively out of service and snagging every process that tried to access it, all accompanied by a clot of kernel messages). See <https://bugzilla.novell.com/show_bug.cgi?id=129623> for the details.
Now, all these weeks later, its status is still "NEW," as if no one has even looked at it.
It has been assigned to Chris, one of our ReiserFS experts, and yes, nothing further seems to have happened.
Is this a reproducable problem? In that case you should mention it.
I've been loath to try running KAudioCreator again, but I suppose I could give it a try. I've got a large batch of CDs to process, since I lost a hard drive and did not have those files backed up.
Now that I think if of it, it probably would have been a good idea to say something about the hardware, since it's one of them new-fangled SATA drives...
And what kind of SATA controller?
What can or should I do to get this investigated?
If it's a critical bug, you could ask me. The bug is rated as normal and the developer is busy working on other stuff. Such kind of bugs will have a high priority in the beta phase but after release this might go under. I've pinged again...
I certainly consider it critical--the symptoms are pretty nasty and it seems to be a kernel- or driver- or file-system-level problem.
This is the first bug I've submitted to that system and I didn't know how to treat the priority (or even whether an outside submitter could actually change it) so I left it at its default setting.
If it is reproduceable, please raise it, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
Andreas, On Monday 05 December 2005 01:16, Andreas Jaeger wrote:
Randall R Schulz <rschulz@sonic.net> writes: ...
Is this a reproducable problem? In that case you should mention it.
I've been loath to try running KAudioCreator again, but I suppose I could give it a try. I've got a large batch of CDs to process, since I lost a hard drive and did not have those files backed up.
Now that I think if of it, it probably would have been a good idea to say something about the hardware, since it's one of them new-fangled SATA drives...
And what kind of SATA controller?
It's the on-board controller on my Intel 865 PERL board. The drive itself is a Western Digital 300 GB WD30000JDRTL (reported by the Hardware Information tool as WD3000JD-00K.
...
If it is reproduceable, please raise it,
OK. When I get some time, I'll try ripping some CDs again to see if it's repeatable. If it is reproduceable, what level should I assign it?
Andreas
Randall Schulz
Randall R Schulz <rschulz@sonic.net> writes:
Andreas,
On Monday 05 December 2005 01:16, Andreas Jaeger wrote:
Randall R Schulz <rschulz@sonic.net> writes: ...
Is this a reproducable problem? In that case you should mention it.
I've been loath to try running KAudioCreator again, but I suppose I could give it a try. I've got a large batch of CDs to process, since I lost a hard drive and did not have those files backed up.
Now that I think if of it, it probably would have been a good idea to say something about the hardware, since it's one of them new-fangled SATA drives...
And what kind of SATA controller?
It's the on-board controller on my Intel 865 PERL board.
The drive itself is a Western Digital 300 GB WD30000JDRTL (reported by the Hardware Information tool as WD3000JD-00K.
Please add this to the bugreport. Sorry, should have been more clear on this.
...
If it is reproduceable, please raise it,
OK. When I get some time, I'll try ripping some CDs again to see if it's repeatable. If it is reproduceable, what level should I assign it?
Critical. Thanks, Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
participants (2)
-
Andreas Jaeger
-
Randall R Schulz