Re: The return of the dreaded "nobody cared" message with a Promise Card
Hi, Alan. First of all, thank you very much for your usual kind responses to me. Second, let me apologize for not being able to reply earlier. :-( I hope that you have not lost interest in fixing this strange situation. I think that I can be speedier with the replies now and, if you wish, I can even go to an IRC channel so that we can exchange information faster, if you want. On Nov 29 2006, Alan wrote: > On Wed, 29 Nov 2006 04:01:30 -0200 > Rogério Brito <[EMAIL PROTECTED]> wrote: > > >> The problem is that whenever I plug the Quantum drive, I get stack > > traces like this one (with a bit of context, so that you can get sense of > > what I am talking about): > > Ok IRQ routing problem on what seems to be an external IRQ. Nice that you have at least identified a possibility. > > ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10 > > PCI: setting IRQ 10 as level-triggered > > ACPI: PCI Interrupt :00:11.0[A] -> Link [LNKB] -> GSI 10 (level, low) > > -> IRQ 10 > > Do your working kernels also have ACPI enabled and what do they say > here ? I have always had ACPI enabled, but, as you asked me, I grabbed a -rc6-mm2 kernel and tried to pass irqpoll. The nice news is that it doesn't hang like vanilla -rc6 with "Uncompressing Linux...", but the unexpected side effect that I got is that none of my Ethernet devices work now. :-( I booted with both "irqpoll" and with "acpi=off irqpoll" and the results were the same. Without any of these options, the kernel boots (like with 2.6.18.x), but it stays there saying that the secondary channel is downgraded due to the lack of 80-pin cable and the drive that *has* an 80-pin cable starts showing "hde: lost interrupt" some times and, after, say, 5 minutes, it still has not completed the boot. :-( > Ok I have a guess here - what does 2.6.19-rc6-mm2 do ? I've been > working on fixing up the VIA IRQ routing bugs as it happens. full > dmesg of the work/fail cases and an lspci -vxxx would be useful so I > can see how the hardware thinks it is configured. Ok, it's quite late at night here and I will upload the dmesg of the 2.6.19-rc6-mm2 kernel (together with lspci -vxxx) to http://www.ime.usp.br/~rbrito/promise/ I will post the behaviour of other kernels as soon as I wake up and you wish. BTW, should I disable ACPI compilation entirely or is "acpi=off" sufficient in further tests? I can do whatever you tell me to... Oh, one thing that is possibly worth bringing up to you is that I have this "nobody cared" problem for some time now (I think that it goes back to several kernel revisions---say, dating back from the 2.6.10 era?). I don't know if git has anything imported from such earlier kernels, but I can bisect/binary search whatever is convenient. One thing that I will try to see if I can get my hands on is on a 80-ribbon cable for this drive, just to see if there are any changes in behaviour (is it worth me trying to find one?). Thank you very much, Rogério Brito. -- Rogério Brito : [EMAIL PROTECTED] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/ - 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: The return of the dreaded nobody cared message with a Promise Card
Hi, Alan. First of all, thank you very much for your usual kind responses to me. Second, let me apologize for not being able to reply earlier. :-( I hope that you have not lost interest in fixing this strange situation. I think that I can be speedier with the replies now and, if you wish, I can even go to an IRC channel so that we can exchange information faster, if you want. On Nov 29 2006, Alan wrote: On Wed, 29 Nov 2006 04:01:30 -0200 Rogério Brito [EMAIL PROTECTED] wrote: The problem is that whenever I plug the Quantum drive, I get stack traces like this one (with a bit of context, so that you can get sense of what I am talking about): Ok IRQ routing problem on what seems to be an external IRQ. Nice that you have at least identified a possibility. ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10 PCI: setting IRQ 10 as level-triggered ACPI: PCI Interrupt :00:11.0[A] - Link [LNKB] - GSI 10 (level, low) - IRQ 10 Do your working kernels also have ACPI enabled and what do they say here ? I have always had ACPI enabled, but, as you asked me, I grabbed a -rc6-mm2 kernel and tried to pass irqpoll. The nice news is that it doesn't hang like vanilla -rc6 with Uncompressing Linux..., but the unexpected side effect that I got is that none of my Ethernet devices work now. :-( I booted with both irqpoll and with acpi=off irqpoll and the results were the same. Without any of these options, the kernel boots (like with 2.6.18.x), but it stays there saying that the secondary channel is downgraded due to the lack of 80-pin cable and the drive that *has* an 80-pin cable starts showing hde: lost interrupt some times and, after, say, 5 minutes, it still has not completed the boot. :-( Ok I have a guess here - what does 2.6.19-rc6-mm2 do ? I've been working on fixing up the VIA IRQ routing bugs as it happens. full dmesg of the work/fail cases and an lspci -vxxx would be useful so I can see how the hardware thinks it is configured. Ok, it's quite late at night here and I will upload the dmesg of the 2.6.19-rc6-mm2 kernel (together with lspci -vxxx) to http://www.ime.usp.br/~rbrito/promise/ I will post the behaviour of other kernels as soon as I wake up and you wish. BTW, should I disable ACPI compilation entirely or is acpi=off sufficient in further tests? I can do whatever you tell me to... Oh, one thing that is possibly worth bringing up to you is that I have this nobody cared problem for some time now (I think that it goes back to several kernel revisions---say, dating back from the 2.6.10 era?). I don't know if git has anything imported from such earlier kernels, but I can bisect/binary search whatever is convenient. One thing that I will try to see if I can get my hands on is on a 80-ribbon cable for this drive, just to see if there are any changes in behaviour (is it worth me trying to find one?). Thank you very much, Rogério Brito. -- Rogério Brito : [EMAIL PROTECTED] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/ - 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: The return of the dreaded "nobody cared" message with a Promise Card
On Wed, 29 Nov 2006 04:01:30 -0200 Rogério Brito <[EMAIL PROTECTED]> wrote: >> The problem is that whenever I plug the Quantum drive, I get stack > traces like this one (with a bit of context, so that you can get sense of > what I am talking about): Ok IRQ routing problem on what seems to be an external IRQ. > ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10 > PCI: setting IRQ 10 as level-triggered > ACPI: PCI Interrupt :00:11.0[A] -> Link [LNKB] -> GSI 10 (level, low) -> > IRQ 10 Do your working kernels also have ACPI enabled and what do they say here ? > I am willing to do a git bisect to see which may be a problematic patch > or not, but the "irq 10: nobody cared (try booting with the "irqpoll" > option)" is one that I reported to Andrew quite some time ago (I thought > that it had gone away), and it didn't manifest itself until I had to > reuse this extra drive, since I am doing a work that is producing a lot > of data. Ok I have a guess here - what does 2.6.19-rc6-mm2 do ? I've been working on fixing up the VIA IRQ routing bugs as it happens. full dmesg of the work/fail cases and an lspci -vxxx would be useful so I can see how the hardware thinks it is configured. - 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: The return of the dreaded nobody cared message with a Promise Card
On Wed, 29 Nov 2006 04:01:30 -0200 Rogério Brito [EMAIL PROTECTED] wrote: The problem is that whenever I plug the Quantum drive, I get stack traces like this one (with a bit of context, so that you can get sense of what I am talking about): Ok IRQ routing problem on what seems to be an external IRQ. ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10 PCI: setting IRQ 10 as level-triggered ACPI: PCI Interrupt :00:11.0[A] - Link [LNKB] - GSI 10 (level, low) - IRQ 10 Do your working kernels also have ACPI enabled and what do they say here ? I am willing to do a git bisect to see which may be a problematic patch or not, but the irq 10: nobody cared (try booting with the irqpoll option) is one that I reported to Andrew quite some time ago (I thought that it had gone away), and it didn't manifest itself until I had to reuse this extra drive, since I am doing a work that is producing a lot of data. Ok I have a guess here - what does 2.6.19-rc6-mm2 do ? I've been working on fixing up the VIA IRQ routing bugs as it happens. full dmesg of the work/fail cases and an lspci -vxxx would be useful so I can see how the hardware thinks it is configured. - 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/
The return of the dreaded "nobody cared" message with a Promise Card
Hi, Andrew, hi Alan, hi others. First of all, I would kindly ask you that you keep me in the Cc'ed messages. I'm currently finishing grades of (loads and loads) of students and I'm having a hard time keeping up with my health problems and real life work, let alone the traffic of lkml. Well, let me get straight to the problem. I have an Asus A7V (Classic) motherboard with a VIA KT133 chipset and it has the two usual VIA IDE controllers and two extra Promise PDC20265 controllers. Right now, my setup is the following (given advice that once Alan gave me, but he may not recall it): * hda: DVD+-RW burner; * hdc: Plain CD-ROM reader; * hde: Seagate ST3160021A (7200.??) drive; * hdg: QUANTUM FIREBALLlct15 30 drive. The problem is that whenever I plug the Quantum drive, I get stack traces like this one (with a bit of context, so that you can get sense of what I am talking about): - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ide1 at 0x170-0x177,0x376 on irq 15 PDC20265: IDE controller at PCI slot :00:11.0 ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10 PCI: setting IRQ 10 as level-triggered ACPI: PCI Interrupt :00:11.0[A] -> Link [LNKB] -> GSI 10 (level, low) -> IRQ 10 PDC20265: chipset revision 2 PDC20265: ROM enabled at 0x3000 PDC20265: 100% native mode on irq 10 PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode. ide2: BM-DMA at 0x7400-0x7407, BIOS settings: hde:pio, hdf:pio ide3: BM-DMA at 0x7408-0x740f, BIOS settings: hdg:DMA, hdh:pio Probing IDE interface ide2... hde: ST3160021A, ATA DISK drive ide2 at 0x8800-0x8807,0x8402 on irq 10 Probing IDE interface ide3... hdg: QUANTUM FIREBALLlct15 30, ATA DISK drive irq 10: nobody cared (try booting with the "irqpoll" option) [] show_trace_log_lvl+0x58/0x16a [] show_trace+0xd/0x10 [] dump_stack+0x19/0x1b [] __report_bad_irq+0x2e/0x6f [] note_interrupt+0x19f/0x1d5 [] __do_IRQ+0xb5/0xeb [] do_IRQ+0x67/0x86 [] common_interrupt+0x1a/0x20 DWARF2 unwinder stuck at common_interrupt+0x1a/0x20 Leftover inexact backtrace: === handlers: [] (ide_intr+0x0/0x19b) Disabling IRQ #10 Warning: Secondary channel requires an 80-pin cable for operation. hdg reduced to Ultra33 mode. ide3 at 0x8000-0x8007,0x7802 on irq 10 hde: max request size: 128KiB hde: 312581808 sectors (160041 MB) w/2048KiB Cache, CHS=19457/255/63, UDMA(100) hde: cache flushes supported hde: hde1 hde2 hde3 hde4 hdg: max request size: 128KiB hdg: 58633344 sectors (30020 MB) w/418KiB Cache, CHS=58168/16/63, UDMA(33) hdg: cache flushes not supported hdg: hdg1 hdg2 hdg3 hdg4 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This is what I get when I boot with a 2.6.18.3 (custom) kernel *AND* with the irqpoll option already enabled. The kernel 2.6.19-rc6 that I have here doesn't work at all if I pass the irqpoll option (it just freezes right at "Uncompressing Linux" nothing is displayed at least during a minute or so---I think that it hanged). Since Linus Torvalds once said something to the effect that "users that are willing to help with patches are worth their weight in gold", I would like to contribute here. :-) I am willing to do a git bisect to see which may be a problematic patch or not, but the "irq 10: nobody cared (try booting with the "irqpoll" option)" is one that I reported to Andrew quite some time ago (I thought that it had gone away), and it didn't manifest itself until I had to reuse this extra drive, since I am doing a work that is producing a lot of data. Please, if you want any further information, don't hesitate to ask. I can test patches that are even moderately invasive, since I'm talking backups of the vital data of my system with regularity. Regards and thank you very much for any help, Rogério Brito. -- Rogério Brito : [EMAIL PROTECTED] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/ - 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/
The return of the dreaded nobody cared message with a Promise Card
Hi, Andrew, hi Alan, hi others. First of all, I would kindly ask you that you keep me in the Cc'ed messages. I'm currently finishing grades of (loads and loads) of students and I'm having a hard time keeping up with my health problems and real life work, let alone the traffic of lkml. Well, let me get straight to the problem. I have an Asus A7V (Classic) motherboard with a VIA KT133 chipset and it has the two usual VIA IDE controllers and two extra Promise PDC20265 controllers. Right now, my setup is the following (given advice that once Alan gave me, but he may not recall it): * hda: DVD+-RW burner; * hdc: Plain CD-ROM reader; * hde: Seagate ST3160021A (7200.??) drive; * hdg: QUANTUM FIREBALLlct15 30 drive. The problem is that whenever I plug the Quantum drive, I get stack traces like this one (with a bit of context, so that you can get sense of what I am talking about): - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ide1 at 0x170-0x177,0x376 on irq 15 PDC20265: IDE controller at PCI slot :00:11.0 ACPI: PCI Interrupt Link [LNKB] enabled at IRQ 10 PCI: setting IRQ 10 as level-triggered ACPI: PCI Interrupt :00:11.0[A] - Link [LNKB] - GSI 10 (level, low) - IRQ 10 PDC20265: chipset revision 2 PDC20265: ROM enabled at 0x3000 PDC20265: 100% native mode on irq 10 PDC20265: (U)DMA Burst Bit ENABLED Primary PCI Mode Secondary PCI Mode. ide2: BM-DMA at 0x7400-0x7407, BIOS settings: hde:pio, hdf:pio ide3: BM-DMA at 0x7408-0x740f, BIOS settings: hdg:DMA, hdh:pio Probing IDE interface ide2... hde: ST3160021A, ATA DISK drive ide2 at 0x8800-0x8807,0x8402 on irq 10 Probing IDE interface ide3... hdg: QUANTUM FIREBALLlct15 30, ATA DISK drive irq 10: nobody cared (try booting with the irqpoll option) [c0103ee6] show_trace_log_lvl+0x58/0x16a [c010451d] show_trace+0xd/0x10 [c010463c] dump_stack+0x19/0x1b [c0132dda] __report_bad_irq+0x2e/0x6f [c0132fba] note_interrupt+0x19f/0x1d5 [c0132684] __do_IRQ+0xb5/0xeb [c0105511] do_IRQ+0x67/0x86 [c01038aa] common_interrupt+0x1a/0x20 DWARF2 unwinder stuck at common_interrupt+0x1a/0x20 Leftover inexact backtrace: === handlers: [c02148d9] (ide_intr+0x0/0x19b) Disabling IRQ #10 Warning: Secondary channel requires an 80-pin cable for operation. hdg reduced to Ultra33 mode. ide3 at 0x8000-0x8007,0x7802 on irq 10 hde: max request size: 128KiB hde: 312581808 sectors (160041 MB) w/2048KiB Cache, CHS=19457/255/63, UDMA(100) hde: cache flushes supported hde: hde1 hde2 hde3 hde4 hdg: max request size: 128KiB hdg: 58633344 sectors (30020 MB) w/418KiB Cache, CHS=58168/16/63, UDMA(33) hdg: cache flushes not supported hdg: hdg1 hdg2 hdg3 hdg4 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - This is what I get when I boot with a 2.6.18.3 (custom) kernel *AND* with the irqpoll option already enabled. The kernel 2.6.19-rc6 that I have here doesn't work at all if I pass the irqpoll option (it just freezes right at Uncompressing Linux nothing is displayed at least during a minute or so---I think that it hanged). Since Linus Torvalds once said something to the effect that users that are willing to help with patches are worth their weight in gold, I would like to contribute here. :-) I am willing to do a git bisect to see which may be a problematic patch or not, but the irq 10: nobody cared (try booting with the irqpoll option) is one that I reported to Andrew quite some time ago (I thought that it had gone away), and it didn't manifest itself until I had to reuse this extra drive, since I am doing a work that is producing a lot of data. Please, if you want any further information, don't hesitate to ask. I can test patches that are even moderately invasive, since I'm talking backups of the vital data of my system with regularity. Regards and thank you very much for any help, Rogério Brito. -- Rogério Brito : [EMAIL PROTECTED] : http://www.ime.usp.br/~rbrito Homepage of the algorithms package : http://algorithms.berlios.de Homepage on freshmeat: http://freshmeat.net/projects/algorithms/ - 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/
