Re: Scanning problems - machine lockups
On Friday 19 January 2001 01:41, Bob Frey wrote: > On Thu, Jan 18, 2001 at 11:24:54PM +0000, Stephen Kitchener wrote: > > The only thing that might be odd is that the scanner's scsi card and the > > display card are using the same IRQ, but I thought that IRQ sharing was > > ok in the new kernels. The display card is an AGP type and the scsi card > > is pci. > > > > As you might have guessed, I am at a loss as to what to do next. Any help > > appriciated, even suggestions as to how I can track down what I haven't > > done (yet!) > > Sharing interrupts could be the problem. Interrupt sharing is supported > in the kernel as far as two different drivers being able to register a > handler for the same interrupt, but not much beyond that. From studying > the code I don't find any handling of unclaimed or spurious interrupts. > > Some drivers (like video cards) do not register a handler for their card's > interrupt. So when another driver (like the advansys driver) shares an > interrupt with this card's "unregistered" interrupt there is no one left > to handle the interrupt. The system will loop taking an interrupt from > the card. I've observed this using the frame buffer driver. Note: this > problem is unnoticed if the (video) card does not share an interrupt with > another driver, because (at least on x86) Linux does not enable the > PIC IRQ bit for IRQs that do not have registered interrupted handlers. > > For Linux I think the right way to handle this is to have each (SA_SHIRQ) > sharing capable interrupt handler return a TRUE or FALSE value indicating > whether the interrupt belongs to the driver. In > kernel/irq.c:handle_IRQ_event() check the return value. If after one pass > through all of the interrupt (action) handlers no one has claimed the > inerrupt then log a warning message (spurious interrupt) and clear the > interrupt. The difficult/painstaking problem is that all SA_SHIRQ drivers > need to be changed to return a return value to make this work. > > Anyway the simplest solution for you is probably if you can is to put > assign the video card its own interrupt. Putting the two advansys cards > on the same interrupt is fine. I have used interrupt sharing between > multiple advansys cards and and ethernet cards without a problem. Hi Bob and the list, I eventually succeeded in putting the grahics card onto a different IRQ from ether of the SCSI cards. Not without some problems though. The AGP card would follow what ever IRQ I assigned the PCI slot nearest it. The mobo is an ASUS P2BD btw. The only way I could make the change was to swap the ethernet card with the scsi card. The Ethernet card now has the same IRQ as the Graphics card. I would try a PCI graphics card, but I haven't one. Just in case the AGP card is getting in the way. Any, I thought that it had cured the problem, but after a few scans, admittedly more than before, the scan head didn't return on the last scan that was successfully started. Trying to scan again, hoping that it would reset the scanner and carry on, ... nothing, no response from scanner. So.. could it be the scsi driver (Advansys 3940uw, in the kernel), or a broken scanner itself?. Is there a way I can test this, run tests, switch on debug etc ? Scsi device is set up as follows... Device Information for AdvanSys SCSI Host 0: Target IDs Detected: 1, 7, (7=Host Adapter) Host: scsi0 Channel: 00 Id: 01 Lun: 00 Vendor: UMAX Model: Astra 2400S Rev: V1.1 Type: Scanner ANSI SCSI revision: 02 EEPROM Settings for AdvanSys SCSI Host 0: Serial Number: AA48A919D387 Host SCSI ID: 7, Host Queue Size: 253, Device Queue Size: 63 termination: 0 (Automatic), bios_ctrl: ffe7 Target ID:0 1 2 3 4 5 6 7 8 9 A B C D E F Disconnects: Y N Y Y Y Y Y Y Y Y Y Y Y Y Y Y Command Queuing: Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Y Start Motor: Y N Y Y Y N Y Y Y Y Y Y Y Y Y Y Synchronous Transfer: Y N Y Y Y Y Y Y Y Y Y Y Y Y Y Y Ultra Transfer: Y N Y Y Y Y Y Y Y Y Y Y Y Y Y Y Wide Transfer:Y N Y Y Y Y Y Y Y Y Y Y Y Y Y Y > > -- > Bob Frey > [EMAIL PROTECTED] > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ -- Stephen Kitchener - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
System beeper - no sound from mobo's own speaker
Hi, I seem to have a problem that, in that when I am using the kernel supplied with Mandrake 10.0 and 10.1 and also fedora 3, there seems to be a distinct lack of beeps coming from the system, once it is up and running. I am NOT talking about sounds that might be coming from any sound card that might be connected to the system, but the plain old speaker that sits in the PC case. This, to my mind, is not very usefull for a server or a laptop that might generate system beeps, ie inserting a wifi card for instance on a laptop. As I'm running Mandrake I have posted this to them, but as of yet I have had no responce or reaction. I did do a search and I found at least one user of Redhat reporting the same sort of problem, so I am guessing that it's not a problem that is of Mandrakes doing, ie they forgot to include it in the kernel that they bult for their distribution. I have installed the latest kernel from fedora 2.6.10, but that didn't change things. Please let me know if I have posted something that is a known problem, and I'll shut up and wait for a new kernel to be release that has this fixed. I cannot beleive that this has been missed in testing, but at the same time I have no beeps at all from any of the 3 machines that I have tested and it has been reported to me, by a friend that is running Mandrake 10.1, he is running different hardware, and can confirm that it was working before the upgrade. The only common thing before we changed as that we were both running 2.4 kernels. I can supply details of hardware if wanted. -- O o _\_ o \\/ o\ . //\___= '' Sun, 23 Jan 2005 18:58:38 + 18:58:38 up 9:13, 0 users, load average: 1.30, 1.15, 1.05 Basic Definitions of Science: If it's green or wiggles, it's biology. If it stinks, it's chemistry. If it doesn't work, it's physics. - 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: System beeper - no sound from mobo's own speaker
On Sunday 23 Jan 2005 19:50, Sergey Vlasov wrote: Hi Sergey, You know - I've just found that and yes it does help on one system, so I'm 50% better off - just need to find out where to put the command so that it loads it on startup...modules.conf would be it I guess. Thanks for quick reply. Steve > On Sun, 23 Jan 2005 19:37:53 + Stephen Kitchener wrote: > > I seem to have a problem that, in that when I am using the kernel > > supplied with Mandrake 10.0 and 10.1 and also fedora 3, there seems to be > > a distinct lack of beeps coming from the system, once it is up and > > running. I am NOT talking about sounds that might be coming from any > > sound card that might be connected to the system, but the plain old > > speaker that sits in the PC case. > > Does "modprobe pcspkr" help? In 2.6.x kernels the PC speaker support > can be built as a loadable module; probably the startup scripts do not > load it automatically. -- O o _\_ o \\/ o\ . //\___= '' Sun, 23 Jan 2005 20:04:43 + 20:04:43 up 10:19, 0 users, load average: 1.24, 1.14, 1.10 The crying baby on board your flight is always seated next to you -- Murphy's Laws for Frequent Flyers n°8 - 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: System beeper - no sound from mobo's own speaker
On Sunday 23 Jan 2005 21:58, Anssi Hannula wrote: > Stephen Kitchener wrote: > > On Sunday 23 Jan 2005 19:50, Sergey Vlasov wrote: > >>Does "modprobe pcspkr" help? In 2.6.x kernels the PC speaker support > >>can be built as a loadable module; probably the startup scripts do not > >>load it automatically. > > > > You know - I've just found that and yes it does help on one system, so > > I'm 50% better off - just need to find out where to put the command so > > that it loads it on startup...modules.conf would be it I guess. > > Put it on /etc/modprobe.preload Thanks -- O o _\_ o \\/ o\ . //\___= '' Mon, 24 Jan 2005 18:55:40 + 18:55:40 up 8:55, 0 users, load average: 1.12, 1.23, 1.19 Life in the state of nature is solitary, poor, nasty, brutish, and short. - Thomas Hobbes, Leviathan - 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/
