On Tue, Apr 21, 2009 at 06:25:07PM +0200, Kurt Roeckx wrote: > On Tue, Apr 21, 2009 at 10:05:10AM +0200, Mikael Pettersson wrote: > > Kurt Roeckx writes: > > > On Wed, Jan 16, 2008 at 11:01:20AM +0100, Mikael Pettersson wrote: > > > > Kurt Roeckx writes: > > > > > On Tue, Jan 15, 2008 at 10:28:06AM +0100, Mikael Pettersson wrote: > > > > > > > 00:08.0 RAID bus controller: Promise Technology, Inc. PDC20376 (FastTrak 376) (rev 02) > > > > > > ... > > > > > > > 00:08.0 0104: 105a:3376 (rev 02) > > > > > > > > > > > > Let me guess, this is a Promise chip included on the mainboard > > > > > > as a RAID controller, and not an add-on PCI card? > > > > > > > > > > Yes, it's a K8V motherboard which has that onboard. > > > > > > > > > > > If it's a mainboard chip, please enter the BIOS and see if it > > > > > > can be configured for non-RAID mode. If it can, please reconfigure > > > > > > it and boot Linux. Does it still claim to be a 20376 or is it > > > > > > now a 20378? > > > > > > > > > > I can't find an option to turn that off in the BIOS. If it did, I'd > > > > > probably have turned it off already. I've also opened the case and it > > > > > says PDC20376 on the chip. > > > > > > > > Ok. I haven't yet found any information about the 20376 which > > > > could explain why the 20376 fails while the 20378 works. > > > > For now, you can disable hotplugging in the driver by applying > > > > the patch below. This should at least bring back some stability > > > > to your system. > > > > > > > > Longer-term I guess I'll have to invent a blacklist mechanism > > > > to automatically prevent 20376 chips from enabling hotplugging. > > > > That is, unless someone can show me a system where a 20376 > > > > actually does work with hotplugging, in which case I'd need a > > > > module parameter (yuck) or some form of dynamic detection of > > > > this condition. > > > > > > Hi, > > > > > > I'm still having this problem with a 2.6.29 kernel. I want to > > > avoid always having to patch my kernel, so I would like to see > > > some solution to this. What do you think that the best way > > > forward is? > > > > Since the previous discussion I've seen the 20378s in two > > identical mainboards of a particular model also throw spurious > > hotplug events. It would be possible to blacklist hotplugging > > on all SATA1 models, but that would also affect SATA1-based > > PCI cards like the SATA150 TX2/TX4 which don't appear to > > have this problem. > > > > Can you post the lspci -vvn output for your 20376? > > 00:08.0 0104: 105a:3376 (rev 02) > Subsystem: 1043:809e > Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- > Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 64 (1000ns min, 4500ns max), Cache Line Size: 256 bytes > Interrupt: pin A routed to IRQ 18 > Region 0: I/O ports at ec00 [size=64] > Region 1: I/O ports at dc00 [size=16] > Region 2: I/O ports at cc00 [size=128] > Region 3: Memory at fdf00000 (32-bit, non-prefetchable) [size=4K] > Region 4: Memory at fdb00000 (32-bit, non-prefetchable) [size=128K] > Capabilities: [60] Power Management version 2 > Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) > Status: D0 PME-Enable- DSel=0 DScale=0 PME- > Kernel driver in use: sata_promise > Kernel modules: sata_promise > Any news about this? Kurt -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
