Hi Paulo! Your patch generated the following:
Jan 28 19:11:51 linux kernel: vsc_sata int status: 00000083 Jan 28 19:11:51 linux last message repeated 19 times Jan 28 19:11:51 linux kernel: irq 7: nobody cared! Jan 28 19:11:51 linux kernel: [<c0128972>] __report_bad_irq+0x22/0x90 Jan 28 19:11:51 linux kernel: [<c0128a68>] note_interrupt+0x58/0x90 Jan 28 19:11:51 linux kernel: [<c01285f8>] __do_IRQ+0xd8/0xe0 . . . . Thanks for helping me... I hope this is useful info.... Dave Sims ************************************************************************ On Fri, 28 Jan 2005, Paulo Marques wrote: > David Sims wrote: > > On Thu, 27 Jan 2005, Jeff Garzik wrote: > >>David Sims wrote: > >> > >>>[...] > >>> You can insert the module in a running kernel and after barking as > >>>follows (once for each disk attached) it runs just fine. > >> > >>Basically nobody has ever had hardware to test sata_vsc with that > >>hardware. We should probably remove the PCI ID until an engineer can > >>fix it... > > > > Hi again, > > > > I am willing to make this hardware available to any engineer that wants > > to help me solve this problem.... and I will do whatever I can to make it > > an easy job... Please help me... > > Well, I don't consider myself a hardware wizard, but at least I'm an > engineer, so I decided to give it a go :) > > It seems that the driver is not acknowledging the interrupt from the > controller. It would be nice to know what kind of interrupt is > triggering this. > > Could you run the attached patch and show the output from dmesg? > > -- > Paulo Marques - www.grupopie.com > > All that is necessary for the triumph of evil is that good men do nothing. > Edmund Burke (1729 - 1797) > - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/