Date: Thu, 6 Nov 2003 14:47:13 +0100
From: Jens Axboe <axboe@suse.de>
To: "Prakash K. Cheemplavam" <prakashpublic@gmx.de>
Cc: Nick Piggin <piggin@cyberone.com.au>, linux-kernel@vger.kernel.org
Subject: Re: 2.9test9-mm1 and DAO ATAPI cd-burning corrupt
Message-ID: <20031106134713.GA798@suse.de>
References: <3FAA41C3.9060601@gmx.de> <3FAA45A9.20707@cyberone.com.au> <20031106130030.GC1145@suse.de> <3FAA4737.3060906@cyberone.com.au> <20031106130553.GD1145@suse.de> <3FAA4880.8090600@cyberone.com.au> <20031106131141.GE1145@suse.de> <3FAA4D48.6040709@gmx.de> <20031106133136.GA477@suse.de> <3FAA5043.8060907@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3FAA5043.8060907@gmx.de>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1921
Lines: 57

On Thu, Nov 06 2003, Prakash K. Cheemplavam wrote:
> 
> >>>Heh indeed, maybe because the archs I use are still at 100. Looks
> >>>suspiciously like it's loosing timer interrupts, which would indeed
> >>>point to PIO.
> >>>
> >>
> >>bash-2.05b# hdparm -I /dev/hdc
> >
> >
> >-i please
> 
> bash-2.05b# hdparm -i /dev/hdc
> 
> /dev/hdc:
> 
>  Model=LITE-ON LTR-16102B, FwRev=OS0K, SerialNo=
>  Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
>  RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
>  BuffType=unknown, BuffSize=0kB, MaxMultSect=0
>  (maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
>  IORDY=yes, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:120}
>  PIO modes:  pio0 pio1 pio2 pio3 pio4
>  DMA modes:  mdma0 mdma1 *mdma2
>  AdvancedPM=no
> 
>  * signifies the current active mode
> 
> The same: dma is active.

Indeed, so you are ysing multiword mode 2. Can you try and do a dd from
the drive, while doing a vmstat 1? Also, does that show the jerky
behaviour?

> >>Is it normal that SCSI subsystem gets init'ed, even though nothing of it 
> >>is activated in the kernel?
> >
> >
> >No, you still have it left in your kernel options.
> 
> Cannot be or there is a bug in the makefile. First I tried make 
> oldconfig, then I noticed this thing coming up, so I did make clen and 
> still  it caame, then mrproper and everything in config by hand, and 
> still coming up. But I booted the "old" kernel up, where I didn't have 
> thouse mouse stutterings and it alsa shows that scsi subsystem gets 
> activated. What do I do wrong then? Should I post the .config?

I can't believe there's such a bug, so yeah put your .config somewhere.

-- 
Jens Axboe

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/