Re: regression: CD burning (k3b) went broke

2008-02-26 Thread Mike Galbraith
On Tue, 2008-02-26 at 10:48 +0100, Mike Galbraith wrote: > Greetings, > > I straced both a good and a bad kernel (good being .git with attached > revert patch applied) and filtered/diffed/merged the output. Scroll > down to "HERE" to see the problem (resid). > > I'm poking around, but not

Re: regression: CD burning (k3b) went broke

2008-02-26 Thread Mike Galbraith
Greetings, I straced both a good and a bad kernel (good being .git with attached revert patch applied) and filtered/diffed/merged the output. Scroll down to "HERE" to see the problem (resid). I'm poking around, but not having much luck. --- good2008-02-26 09:11:08.0 +0100 +++

Re: regression: CD burning (k3b) went broke

2008-02-26 Thread Mike Galbraith
Greetings, I straced both a good and a bad kernel (good being .git with attached revert patch applied) and filtered/diffed/merged the output. Scroll down to HERE to see the problem (resid). I'm poking around, but not having much luck. --- good2008-02-26 09:11:08.0 +0100 +++ bad

Re: regression: CD burning (k3b) went broke

2008-02-26 Thread Mike Galbraith
On Tue, 2008-02-26 at 10:48 +0100, Mike Galbraith wrote: Greetings, I straced both a good and a bad kernel (good being .git with attached revert patch applied) and filtered/diffed/merged the output. Scroll down to HERE to see the problem (resid). I'm poking around, but not having much

Re: regression: CD burning (k3b) went broke

2008-02-23 Thread Mike Galbraith
On Sat, 2008-02-23 at 08:42 +0100, Mike Galbraith wrote: > Meanwhile back at the ranch, reverting > 6b00769fe1502b4ad97bb327ef7ac971b208bfb5 > 40b01b9bbdf51ae543a04744283bf2d56c4a6afa and the one entangled line from > dde2020754aeb14e17052d61784dcb37f252aac2 did restore my burner. It looks

Re: regression: CD burning (k3b) went broke

2008-02-23 Thread Mike Galbraith
On Sat, 2008-02-23 at 08:42 +0100, Mike Galbraith wrote: Meanwhile back at the ranch, reverting 6b00769fe1502b4ad97bb327ef7ac971b208bfb5 40b01b9bbdf51ae543a04744283bf2d56c4a6afa and the one entangled line from dde2020754aeb14e17052d61784dcb37f252aac2 did restore my burner. It looks like

Re: regression: CD burning (k3b) went broke

2008-02-22 Thread Mike Galbraith
On Fri, 2008-02-22 at 08:32 +0100, Jens Axboe wrote: > On Thu, Feb 21 2008, Mike Galbraith wrote: > > Greetings, > > > > K3b recently (9a4c854..5d9c4a7 pull) began terminally griping about > > buffer underrun upon every attempt to burn a CD. I can't fully bisect > > the problem because

Re: regression: CD burning (k3b) went broke

2008-02-22 Thread Mike Galbraith
On Fri, 2008-02-22 at 08:32 +0100, Jens Axboe wrote: On Thu, Feb 21 2008, Mike Galbraith wrote: Greetings, K3b recently (9a4c854..5d9c4a7 pull) began terminally griping about buffer underrun upon every attempt to burn a CD. I can't fully bisect the problem because intervening

Re: regression: CD burning (k3b) went broke

2008-02-21 Thread Jens Axboe
On Thu, Feb 21 2008, Mike Galbraith wrote: > Greetings, > > K3b recently (9a4c854..5d9c4a7 pull) began terminally griping about > buffer underrun upon every attempt to burn a CD. I can't fully bisect > the problem because intervening kernels hang soft during boot. Using > git bisect visualize,

Re: regression: CD burning (k3b) went broke

2008-02-21 Thread Jens Axboe
On Thu, Feb 21 2008, Mike Galbraith wrote: Greetings, K3b recently (9a4c854..5d9c4a7 pull) began terminally griping about buffer underrun upon every attempt to burn a CD. I can't fully bisect the problem because intervening kernels hang soft during boot. Using git bisect visualize, and