Re: 2.6.11-rc3-mm1 bad scheduling while atomic + lockup

2005-02-08 Thread Jens Axboe
On Tue, Feb 08 2005, Andrew Morton wrote: > Jens Axboe <[EMAIL PROTECTED]> wrote: > > > > > ->axboe! > > > > :-) > > > > The thing wants a rewrite. Ideally the serializing point would be a > > special request. The patch is still better than nothing right now, it's > > really easy to

Re: 2.6.11-rc3-mm1 bad scheduling while atomic + lockup

2005-02-08 Thread Andrew Morton
Jens Axboe <[EMAIL PROTECTED]> wrote: > > >->axboe! > > :-) > > The thing wants a rewrite. Ideally the serializing point would be a > special request. The patch is still better than nothing right now, it's > really easy to hang the device with hdparm in -linus since it's > impos

Re: 2.6.11-rc3-mm1 bad scheduling while atomic + lockup

2005-02-08 Thread Jens Axboe
On Tue, Feb 08 2005, Andrew Morton wrote: > Maciej Soltysiak <[EMAIL PROTECTED]> wrote: > > > > Feb 6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady > > SeekComplete Error } > > Feb 6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError > > BadCRC } > > Feb 6 17:07

Re: 2.6.11-rc3-mm1 bad scheduling while atomic + lockup

2005-02-08 Thread Andrew Morton
Maciej Soltysiak <[EMAIL PROTECTED]> wrote: > > Feb 6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady > SeekComplete Error } > Feb 6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError > BadCRC } > Feb 6 17:07:47 dns kernel: ide: failed opcode was: unknown > Feb

Re[2]: 2.6.11-rc3-mm1 bad scheduling while atomic + lockup

2005-02-07 Thread Maciej Soltysiak
Hello Hans, Monday, February 7, 2005, 9:19:47 PM, you wrote: > Maciej Soltysiak wrote: >>) >> >>Feb 6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady >>SeekComplete Error } >>Feb 6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError >>BadCRC } >> >> > this means

Re: 2.6.11-rc3-mm1 bad scheduling while atomic + lockup

2005-02-07 Thread Hans Reiser
Maciej Soltysiak wrote: ) Feb 6 17:07:47 dns kernel: hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } Feb 6 17:07:47 dns kernel: hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } this means bad hard drive, or at least a bad sector on it. - To unsubscribe from this list: send th

2.6.11-rc3-mm1 bad scheduling while atomic + lockup

2005-02-06 Thread Maciej Soltysiak
Hello, I just want to report a lockup on my 2.6.11-rc3-mm1 machine. I was working on it via ssh and suddenly the machine stopped responding. When, the next day I came up to the console it was printing over and over this oops. In the logs I could find the oops. I am posting it inline here along w