I need a hardware wizard... I have been beating my head on the wall..
Hi, I have posted a couple of times in the past to no avail... I have an Intel 31244 SATA controller that is supposed to work with the sata_vsc driver module... It does in fact, almost You can insert the module in a running kernel and after barking as follows (once for each disk attached) it runs just fine. Jan 24 13:55:37 linux kernel: irq 3: nobody cared! Jan 24 13:55:37 linux kernel: [] __report_bad_irq+0x22/0x90 Jan 24 13:55:37 linux kernel: [] note_interrupt+0x58/0x90 Jan 24 13:55:37 linux kernel: [] __do_IRQ+0xd8/0xe0 Jan 24 13:55:37 linux kernel: [] do_IRQ+0x1a/0x30 Jan 24 13:55:37 linux kernel: [] common_interrupt+0x1a/0x20 Jan 24 13:55:37 linux kernel: [] __do_softirq+0x30/0x90 Jan 24 13:55:37 linux kernel: [] do_softirq+0x35/0x40 Jan 24 13:55:37 linux kernel: [] do_IRQ+0x1f/0x30 Jan 24 13:55:37 linux kernel: [] common_interrupt+0x1a/0x20 Jan 24 13:55:37 linux kernel: [] default_idle+0x0/0x40 Jan 24 13:55:37 linux kernel: [] default_idle+0x24/0x40 Jan 24 13:55:37 linux kernel: [] cpu_idle+0x2e/0x40 Jan 24 13:55:37 linux kernel: [] start_kernel+0x15b/0x190 Jan 24 13:55:37 linux kernel: handlers: Jan 24 13:55:37 linux kernel: [] (ide_intr+0x0/0x120) Jan 24 13:55:37 linux kernel: [] (ide_intr+0x0/0x120) Jan 24 13:55:37 linux kernel: [] (vsc_sata_interrupt+0x0/0xa0 [sata_vsc]) Jan 24 13:55:37 linux kernel: Disabling IRQ #3 The problem is that when you insert the module at boot time, the machine just hangs while trying to enumerate the first disk Same when booting with the module builtin to a monolithic kernel To facilitate helping me, I have gathered the requisite stuff and posted it on my website as follows: http://www.dpsims.com/~dpsims/31244/ If someone would be so kind as to help me, I would be willing to provide access to the machine in question for testing, etc... I believe the problem is caused by the Intel 31244 having multiple ways of sending interrupts... The Intel documentation is located at: http://www.dpsims.com/~dpsims/31244/31244_developers_guide.pdf and I draw your attention to section 5.8 and 5.9 The code for the sata_vsc.c from kernel 2.6.10 can be found at http://www.dpsims.com/~dpsims/31244/sata_vsc.c I would make this work myself if I had the required skill sets... but I don't Thus I am reduced to pleading ;) Please help me. I will try to contribute whatever I can... quickly test /etc... Dave - 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/
Re: I need a hardware wizard... I have been beating my head on the wall..
On Thu, 27 Jan 2005, Jeff Garzik wrote: > David Sims wrote: > > Hi, > > > > I have posted a couple of times in the past to no avail... I have an > > Intel 31244 SATA controller that is supposed to work with the sata_vsc > > driver module... It does in fact, almost > > > > 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... > > Jeff > > 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... Dave - 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/
Re: I need a hardware wizard... I have been beating my head on the wall..
Hi Paulo! Your patch generated the following: Jan 28 19:11:51 linux kernel: vsc_sata int status: 0083 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: [] __report_bad_irq+0x22/0x90 Jan 28 19:11:51 linux kernel: [] note_interrupt+0x58/0x90 Jan 28 19:11:51 linux kernel: [] __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/
Re: I need a hardware wizard... I have been beating my head on the wall..
Hello people, Now I _really_ need to bang my head on the wall... :( and thank all you people who responded to my cry for help... I have to admit that I have been stupid (or just a little clueless) but I have worked the puzzle!! It seems that sata_vsc works just fine My entire problem involved the PCI IRQ routing mechanism and my lack of understanding of the interaction between 'Loacl APIC', 'IO-APIC' and power management It seems that you can do what you want with 'Local APIC' and 'IO-APIC' but if you have not enabled ACPI, the APIC stuff is not enabled... and doesn't seem to do anything I have now enabled both ACPI and APIC (with IO-APIC) and the IRQ barking has gone away!! I had a similar problem today with another computer (ASUS MS4800-MX) where the built in Ethernet on a Via PHY chip (supported by the SiS900 driver) refused to work... In this case I booted up Knoppix which worked just fine and then started trying to figure out why there was a difference between knoppix and a vanilla Slackware kernel It seems that Slackware 9.1 does not have ACPI (or APIC or IO-APIC) enabled... Once I figured that out, it was seemed to make the SIS900 driver work so I decided to try it on the sata_vsc problem The result is history and everything is working as it should It's a shame that the knoppix 3.4 kernel doesn't probe for SATA stuff or I would probably have figured this out a week ago :( Meanwhile, a working sata_vsc allows one to turn a Dell Powervault 745N (Dell's foray into Network Attached Storage) into a good and cheap unix server with dual gig NICs and 4 SATA disks that can either be run independently or via software raid!! Cool! Thanks again for your support for and patience with me... I will be humble for a while now... ;) Dave - 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/
irq 3: nobody cared! with Intel 31244 SATA.... Advice??
Hi folks, I have a Dell Powervault 745N appliance that I am trying to install Slackware Linux on I have temporarily installed a dual port IDE card in the expansion slot so I can have the benefit of a CD-ROM and IDE PATA HD Slackware 9.1 installs straightforwardly to the IDE PATA HD and it boots up fine I first tried to get the SATA disk talking with the 2.4.29 kernel... This kernel boots but hangs when it tries to load module sata_vsc either from rc.modules or manually after startup using "modprobe sata_vsc" I then downloaded and built kernel 2.6.10 which boots up fine without the sata_vsc module If you then load the sata_vsc module manually using "modprobe sata_vsc" it will cause the following error once for each attached disk drive: Jan 23 09:08:21 linux kernel: Disabling IRQ #3 Jan 23 09:08:23 linux kernel: irq 3: nobody cared! Jan 23 09:08:23 linux kernel: [] __report_bad_irq+0x22/0x90 Jan 23 09:08:23 linux kernel: [] note_interrupt+0x58/0x90 Jan 23 09:08:23 linux kernel: [] __do_IRQ+0xd8/0xe0 Jan 23 09:08:23 linux kernel: [] do_IRQ+0x1a/0x30 Jan 23 09:08:23 linux kernel: [] common_interrupt+0x1a/0x20 Jan 23 09:08:23 linux kernel: [] __do_softirq+0x30/0x90 Jan 23 09:08:23 linux kernel: [] do_softirq+0x35/0x40 Jan 23 09:08:23 linux kernel: [] do_IRQ+0x1f/0x30 Jan 23 09:08:23 linux kernel: [] common_interrupt+0x1a/0x20 Jan 23 09:08:23 linux kernel: [] default_idle+0x0/0x40 Jan 23 09:08:23 linux kernel: [] default_idle+0x24/0x40 Jan 23 09:08:23 linux kernel: [] cpu_idle+0x2e/0x40 Jan 23 09:08:23 linux kernel: [] start_kernel+0x15b/0x190 Jan 23 09:08:23 linux kernel: handlers: Jan 23 09:08:23 linux kernel: [] (ide_intr+0x0/0x120) Jan 23 09:08:23 linux kernel: [] (ide_intr+0x0/0x120) Jan 23 09:08:23 linux kernel: [] (vsc_sata_interrupt+0x0/0xa0 [sata_vsc]) but it will then load and work ok and allow me to fdisk, format and mount the disk normally. If I run 'modprobe sata_vsc' from rc.modules, then it hangs while trying to talk to the first disk just like kernel 2.4.29 did I have repetitively seen this behavior both with a module and with the module builtin to the kernel I have also built the kernel with and without ACPI as some of the traffic in the newsgroups indicated that could be a problem... This caused no change in behavior Since my ambition is to get this machine to boot from the SATA disk I am stuck at this point If anyone can provide a little advice or direction I would be indebted... I have fiddled with the PCI BIOS IRQ settings without joy... You can change which IRQ is used by the sata controller but then the error message just changes to that IRQ (i.e., irq 7: nobody cared!) It may be of interest to note that the SATA controller (Intel 31244) and the dual port IDE card in the expansion slot seem to be forced in the BIOS to share the IRQ that is assigned to either one... Again, any advice would be very welcome at this point TIA, Dave Sims Houston, Texas USA - 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/
RE: irq 3: nobody cared! with Intel 31244 SATA.... Advice??
Hi Atul, If I enable APIC on the 2.6.10 kernel I get exactly the same behavior as I got without APIC If I enable APIC-IO, then it starts barking about Interrupt 22 and never finishes... SO... At the minimum, both of these settings do not help and one makes the problem worse in that the sata-vsc module never finishes loading Thanks for your response though... At this point I am ready to climb a tree and bark at the moon if it will help ;) Dave On Mon, 24 Jan 2005, Atul Bhouraskar wrote: > > > > -Original Message- > > From: [EMAIL PROTECTED] [mailto:linux-kernel- > > [EMAIL PROTECTED] On Behalf Of David Sims > > Sent: Monday, 24 January 2005 13:57 > > > > I then downloaded and built kernel 2.6.10 which boots up fine without > the > > sata_vsc module If you then load the sata_vsc module manually > using > > "modprobe sata_vsc" it will cause the following error once for each > > attached disk drive: > > > > Jan 23 09:08:21 linux kernel: Disabling IRQ #3 > > Jan 23 09:08:23 linux kernel: irq 3: nobody cared! > > I once had the same problem, I think enabling APIC solved it > > Atul > > - 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/
sata_vsc problem.... Please help me.
Hi, With kernel 2.6.10 on Intel (Dell Powervault 745N) When I insert the sata_vsc module via 'modprobe sata_vsc' from the command line, the module immediately recognizes the controller card and then enumerates the attached disks. During this process I am getting errors logged in syslog for each disk as follows: Jan 24 13:55:37 linux kernel: irq 3: nobody cared! Jan 24 13:55:37 linux kernel: [] __report_bad_irq+0x22/0x90 Jan 24 13:55:37 linux kernel: [] note_interrupt+0x58/0x90 Jan 24 13:55:37 linux kernel: [] __do_IRQ+0xd8/0xe0 Jan 24 13:55:37 linux kernel: [] do_IRQ+0x1a/0x30 Jan 24 13:55:37 linux kernel: [] common_interrupt+0x1a/0x20 Jan 24 13:55:37 linux kernel: [] __do_softirq+0x30/0x90 Jan 24 13:55:37 linux kernel: [] do_softirq+0x35/0x40 Jan 24 13:55:37 linux kernel: [] do_IRQ+0x1f/0x30 Jan 24 13:55:37 linux kernel: [] common_interrupt+0x1a/0x20 Jan 24 13:55:37 linux kernel: [] default_idle+0x0/0x40 Jan 24 13:55:37 linux kernel: [] default_idle+0x24/0x40 Jan 24 13:55:37 linux kernel: [] cpu_idle+0x2e/0x40 Jan 24 13:55:37 linux kernel: [] start_kernel+0x15b/0x190 Jan 24 13:55:37 linux kernel: handlers: Jan 24 13:55:37 linux kernel: [] (ide_intr+0x0/0x120) Jan 24 13:55:37 linux kernel: [] (ide_intr+0x0/0x120) Jan 24 13:55:37 linux kernel: [] (vsc_sata_interrupt+0x0/0xa0 [sata_vsc]) Jan 24 13:55:37 linux kernel: Disabling IRQ #3 and in /proc/interrupts the count for irq3 advances by 500,000 (i.e., 100,000 for the controller and 100,000 for each attached disk). It seems to me that this driver is initializing itself and enabling interrupts before it is fully loaded and ready to deal with them If I insert the module during the boot up process, the machine just hangs trying to read/identify the first disk... Is there a way to disable or ignore these interrupts until the driver is fully loaded, the disks are identified and all of the necessary housekeeping is finished and the driver is finished loading?? Once the sata_vsc module finishes identifying the attached drives and the 'modprobe sata_vsc' returns to the command prompt the errors stop coming and it seems to work just fine You can fdisk and format the disks and all is well... If I could just get it load at boot time I would be happy Any advice would be welcome at this point. ;) TIA, Dave Sims - 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/
Re: sata_vsc problem.... Please help me.
On Mon, 24 Jan 2005, Marcelo Tosatti wrote: > On Mon, Jan 24, 2005 at 04:09:08PM -0600, David Sims wrote: > > Hi, > > > > With kernel 2.6.10 on Intel (Dell Powervault 745N) When I insert the > > sata_vsc module via 'modprobe sata_vsc' from the command line, the module > > immediately recognizes the controller card and then enumerates the > > attached disks. During this process I am getting errors logged in syslog > > for each disk as follows: > > > > Jan 24 13:55:37 linux kernel: irq 3: nobody cared! > > Jan 24 13:55:37 linux kernel: [] __report_bad_irq+0x22/0x90 > > Jan 24 13:55:37 linux kernel: [] note_interrupt+0x58/0x90 > > Jan 24 13:55:37 linux kernel: [] __do_IRQ+0xd8/0xe0 > > Jan 24 13:55:37 linux kernel: [] do_IRQ+0x1a/0x30 > > Jan 24 13:55:37 linux kernel: [] common_interrupt+0x1a/0x20 > > Jan 24 13:55:37 linux kernel: [] __do_softirq+0x30/0x90 > > Jan 24 13:55:37 linux kernel: [] do_softirq+0x35/0x40 > > Jan 24 13:55:37 linux kernel: [] do_IRQ+0x1f/0x30 > > Jan 24 13:55:37 linux kernel: [] common_interrupt+0x1a/0x20 > > Jan 24 13:55:37 linux kernel: [] default_idle+0x0/0x40 > > Jan 24 13:55:37 linux kernel: [] default_idle+0x24/0x40 > > Jan 24 13:55:37 linux kernel: [] cpu_idle+0x2e/0x40 > > Jan 24 13:55:37 linux kernel: [] start_kernel+0x15b/0x190 > > Jan 24 13:55:37 linux kernel: handlers: > > Jan 24 13:55:37 linux kernel: [] (ide_intr+0x0/0x120) > > Jan 24 13:55:37 linux kernel: [] (ide_intr+0x0/0x120) > > Jan 24 13:55:37 linux kernel: [] (vsc_sata_interrupt+0x0/0xa0 > > [sata_vsc]) > > Jan 24 13:55:37 linux kernel: Disabling IRQ #3 > > > > and in /proc/interrupts the count for irq3 advances by 500,000 (i.e., > > 100,000 for the controller and 100,000 for each attached disk). > > > > > > It seems to me that this driver is initializing itself and enabling > > interrupts before it is fully loaded and ready to deal with them > > > > If I insert the module during the boot up process, the machine just > > hangs trying to read/identify the first disk... > > > > Is there a way to disable or ignore these interrupts until the driver is > > fully loaded, the disks are identified and all of the necessary > > housekeeping is finished and the driver is finished loading?? > > > > Once the sata_vsc module finishes identifying the attached drives and > > the 'modprobe sata_vsc' returns to the command prompt the errors stop > > coming and it seems to work just fine You can fdisk and format the > > disks and all is well... If I could just get it load at boot time I would > > be happy > > > > Any advice would be welcome at this point. ;) > > > You can use the following to disable the interrupt debugging: > > Documentation/kernel-parameters.txt: > > noirqdebug [IA-32] Disables the code which attempts to detect and > disable unhandled interrupt sources. > > But there is definately something wrong with the driver. Jeff? > Hi, With 'noirqdebug' passed to the kernel, then it just hangs while trying to talk to the first disk much like calling the driver from rc.modules Dave - 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/
Re: sata_vsc, sata_core problem.... Please help me. (another clue)
> On Mon, Jan 24, 2005 at 02:03:38PM -0600, David Sims wrote: > > Hi, > > > > With kernel 2.6.10 on Intel (Dell Powervault 745N) When I insert the > > sata_vsc module via 'modprobe sata_vsc' from the command line, the module > > immediately recognizes the controller card and when it then enumerates the > > attached disks, I am getting errors logged in syslog for each disk as > > follows: > > > > Jan 24 13:55:37 linux kernel: irq 3: nobody cared! > > Jan 24 13:55:37 linux kernel: [] __report_bad_irq+0x22/0x90 > > Jan 24 13:55:37 linux kernel: [] note_interrupt+0x58/0x90 > > Jan 24 13:55:37 linux kernel: [] __do_IRQ+0xd8/0xe0 > > Jan 24 13:55:37 linux kernel: [] do_IRQ+0x1a/0x30 > > Jan 24 13:55:37 linux kernel: [] common_interrupt+0x1a/0x20 > > Jan 24 13:55:37 linux kernel: [] __do_softirq+0x30/0x90 > > Jan 24 13:55:37 linux kernel: [] do_softirq+0x35/0x40 > > Jan 24 13:55:37 linux kernel: [] do_IRQ+0x1f/0x30 > > Jan 24 13:55:37 linux kernel: [] common_interrupt+0x1a/0x20 > > Jan 24 13:55:37 linux kernel: [] default_idle+0x0/0x40 > > Jan 24 13:55:37 linux kernel: [] default_idle+0x24/0x40 > > Jan 24 13:55:37 linux kernel: [] cpu_idle+0x2e/0x40 > > Jan 24 13:55:37 linux kernel: [] start_kernel+0x15b/0x190 > > Jan 24 13:55:37 linux kernel: handlers: > > Jan 24 13:55:37 linux kernel: [] (ide_intr+0x0/0x120) > > Jan 24 13:55:37 linux kernel: [] (ide_intr+0x0/0x120) > > Jan 24 13:55:37 linux kernel: [] (vsc_sata_interrupt+0x0/0xa0 > > [sata_vsc]) > > Jan 24 13:55:37 linux kernel: Disabling IRQ #3 > > > > > > It seems to me that this driver is initializing itself and enabling > > interrupts before it is fully loaded and ready to deal with them > > > > If I insert the module during the boot up process, the machine just > > hangs trying to read/identify the first disk... > > > > Is there a way to disable or ignore these interrupts until the driver is > > fully loaded, the disks are identified and all of the necessary > > housekeeping is finished and the driver is finished loading?? > > > > Once the sata_vsc module finishes identifying the attached drives and > > the 'modprobe sata_vsc' returns to the command prompt the errors stop > > coming and it seems to work just fine You can fdisk and format the > > disks and all is well... If I could just get it load at boot time I > > would be happy > > > > Any advice would be welcome at this point. ;) > > > > TIA, > > > > Dave Sims > > > Sorry, but I really don't have any clues at this point. The driver is > really more a set of subroutines, and most of this stuff is done by the > libata and scsi i/f. > > jeremy > Hi again, This may sound like a dumb idea, but I decided to remove all the disks from the SATA controller and fiddle with the module a bit... So... Interestingly enough, the module loads without a peep both at the command line AND when autoloading from rc.modules AND when builtin to a monolithic kernel!! So... The interrupt problem is coming when the controller tries to enumerate its disks... I have verified this by unloading the module, installing one disk, and then reinserting the module... I get 200,000 additional interrupts on IRQ3 in /proc/interrupts and the normal error message shown above logged to syslog for the one disk... What do you think about that?? Dave - 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/
