Re: yenta_socket "nobody cared - Disabling IRQ #4" - WORKING!!
On Saturday 19 March 2005 09:05, Jonas Oreland wrote: > Hi again and thx again, > > SUMMARY: It's working with new hook (wo/ trying second part) > I'll post again if error comes up again. that's good news! > > Daniel Ritz wrote: > > On Saturday 19 March 2005 00:00, Jonas Oreland wrote: > >> > >>>it's the second time now i see this problem with an atheros chipset in > >>>combination with a TI bridge. last time it was the 1225... > >>>attached a patch that could help... > >>> > >> > >>Report: > >>1) It works somewhat better. irq doesn't get disabled. > >>2) however wlan card get disfunctional. I haven't been able to contact my > >>wap > >> even if i'm standing on it... > > > > > > i was afraid that it could have some side effects. it's probably because > > just > > writing a 0 to the MFUNC register is stupid...can you try to replace > > ti12xx_hook() > > in ti113x.h with this one? > > > > yes, now it works!!! (limited testing) > I tried rebooting plugging/unplugging/swsuspending maybe 6 times. > All of them working, that a new record :-) > > Should I try "second step" anyway? not neccessarily.. > > >>3) unplug has resulted in kernel panic (twice) > >> (btw: how do I do to capture and report those) > > > > > > at a first guess i would blame the atheros driver which taints the kernel. > > so try _not_ loading the atheros driver and see if it still happens. if > > so the messages please. to capture them you can use a serial console > > (null modem cable to second pc). check out the "remote serial console" > > howto on www.tldp.org > > might be...the driver...haven't tried wo/ it. > > note: I never got this after new hook, > > > > > > >>4) when unlug don't produce kernel panic, then there is no way of > >>power-oning that card again. > >>5) booting with the card inserted makes it not power on when yenta_socket > >>is loaded (module) > > > > > > anything in dmesg then? > > zero > > >>comment: the card being disfunction could have something to with the driver. > >>but before it worked sometimes... > >> > >> > >>>-- > >>> > >>>for TI bridges: turn off interrupts during card power-on. this seems > >>>to be neccessary for some combination of TI bridges with at least CB cards > >>>with atheros chipset...problem is that they produce an interrupt storm > >>>during power-on so the kernel happens to disable the IRQ which is a bad > >>>thing (tm). > >>>adds a generic hook function so that a socket driver can hook into > >>>almost anywhere (by adding more hook points of course). this is the > >>>cleanest way i can think of. and it allows adding more workarounds > >>>for more problems... > >>>for the TI specific interrupt on-off stuff just save the MFUNC register > >>>and set it to 0 to disable all interrupts, restore it afterwards. > >>> > >>>Signed-off-by: Daniel Ritz <[EMAIL PROTECTED]> > >> > >>Some thoughts: (not I'm neither pcmcia nor linux expert). > >> > >>The "irq storm", shouldn't that be "acked" in someway. > >>I.e. the card produced a lot of irq's (that get ignored) > >>isn't the "real" solution to capture them, and "do something clever"? > >> > >>Instead of just "shutting the card down". > >> > >>hmmm...wonder if that made sence > > > > > > it's the CB device that is making the interrupt storm and the TI > > bridge is stupid enough to let the interrupts thru during power > > on. thing is you can't ack them at this time because the cardbus > > resources are not set up at this time and ack'ing an IRQ is > > device specifc. > > ok > > >>Question: Why do you think that it worked sometimes before? > > > > > > pure luck? > > How about 2.4? can you compare cs code with 2.6? > It always worked in 2.4... the problem is there also, it just doesn't show up. 2.6 checks for every interrupt if one of the handlers took care of it. if not the dump is printed and a counter is increased. if this counter reaches a limit the interrupt line is disabled. 2.4 doesn't do it so the interrupt storm is there too, it just recovers...you can try with 2.4...after you have the card up do a "cat /proc/interrupts" and you'll see a high number for yenta's interrupt line... > > /Jonas > > > can you also give me a dump of /proc/iomem? > [snip /proc/iomem] it was just to be sure nothing is mapped over existing physical RAM which is not the case... i'll cook up a more flexible patch which handles other TI bridges as well (the current one will fail on some older controllers and on 2-slot controllers) rgds -daniel - 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: yenta_socket "nobody cared - Disabling IRQ #4" - WORKING!!
Hi again and thx again, SUMMARY: It's working with new hook (wo/ trying second part) I'll post again if error comes up again. Daniel Ritz wrote: On Saturday 19 March 2005 00:00, Jonas Oreland wrote: it's the second time now i see this problem with an atheros chipset in combination with a TI bridge. last time it was the 1225... attached a patch that could help... Report: 1) It works somewhat better. irq doesn't get disabled. 2) however wlan card get disfunctional. I haven't been able to contact my wap even if i'm standing on it... i was afraid that it could have some side effects. it's probably because just writing a 0 to the MFUNC register is stupid...can you try to replace ti12xx_hook() in ti113x.h with this one? yes, now it works!!! (limited testing) I tried rebooting plugging/unplugging/swsuspending maybe 6 times. All of them working, that a new record :-) Should I try "second step" anyway? 3) unplug has resulted in kernel panic (twice) (btw: how do I do to capture and report those) at a first guess i would blame the atheros driver which taints the kernel. so try _not_ loading the atheros driver and see if it still happens. if so the messages please. to capture them you can use a serial console (null modem cable to second pc). check out the "remote serial console" howto on www.tldp.org might be...the driver...haven't tried wo/ it. note: I never got this after new hook, 4) when unlug don't produce kernel panic, then there is no way of power-oning that card again. 5) booting with the card inserted makes it not power on when yenta_socket is loaded (module) anything in dmesg then? zero comment: the card being disfunction could have something to with the driver. but before it worked sometimes... -- for TI bridges: turn off interrupts during card power-on. this seems to be neccessary for some combination of TI bridges with at least CB cards with atheros chipset...problem is that they produce an interrupt storm during power-on so the kernel happens to disable the IRQ which is a bad thing (tm). adds a generic hook function so that a socket driver can hook into almost anywhere (by adding more hook points of course). this is the cleanest way i can think of. and it allows adding more workarounds for more problems... for the TI specific interrupt on-off stuff just save the MFUNC register and set it to 0 to disable all interrupts, restore it afterwards. Signed-off-by: Daniel Ritz <[EMAIL PROTECTED]> Some thoughts: (not I'm neither pcmcia nor linux expert). The "irq storm", shouldn't that be "acked" in someway. I.e. the card produced a lot of irq's (that get ignored) isn't the "real" solution to capture them, and "do something clever"? Instead of just "shutting the card down". hmmm...wonder if that made sence it's the CB device that is making the interrupt storm and the TI bridge is stupid enough to let the interrupts thru during power on. thing is you can't ack them at this time because the cardbus resources are not set up at this time and ack'ing an IRQ is device specifc. ok Question: Why do you think that it worked sometimes before? pure luck? How about 2.4? can you compare cs code with 2.6? It always worked in 2.4... /Jonas can you also give me a dump of /proc/iomem? -0009efff : System RAM 0009f000-0009 : reserved 000a-000b : Video RAM area 000c-000c7fff : Video ROM 000cd000-000ce7ff : Adapter ROM 000e-000e : Extension ROM 000f-000f : System ROM 0010-0f6e : System RAM 0010-00409648 : Kernel code 00409649-005183ff : Kernel data 0f6f-0f6f : reserved 0f70-3f6e : System RAM 3f6f-3f6f7fff : ACPI Tables 3f6f8000-3f6f9fff : ACPI Non-volatile Storage 3f70-3fff : reserved 4000-43ff : :00:1f.1 40001000-40001fff : :02:01.0 40001000-40001fff : yenta_socket 4040-407f : PCI CardBus #03 4080-40bf : PCI CardBus #03 4080-4080 : :03:00.0 4080-4080 : ath d000-d007 : :00:02.0 d008-d00f : :00:02.1 d010-d01003ff : :00:1d.7 d010-d01003ff : ehci_hcd d0100800-d01008ff : :00:1f.5 d0100800-d01008ff : Intel 82801DB-ICH4 d0100c00-d0100dff : :00:1f.5 d0100c00-d0100dff : Intel 82801DB-ICH4 d020-d020 : :02:00.0 d020-d020 : tg3 e000-e7ff : :00:02.0 e800-efff : :00:02.1 ff80- : reserved - 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: yenta_socket nobody cared - Disabling IRQ #4 - WORKING!!
Hi again and thx again, SUMMARY: It's working with new hook (wo/ trying second part) I'll post again if error comes up again. Daniel Ritz wrote: On Saturday 19 March 2005 00:00, Jonas Oreland wrote: it's the second time now i see this problem with an atheros chipset in combination with a TI bridge. last time it was the 1225... attached a patch that could help... Report: 1) It works somewhat better. irq doesn't get disabled. 2) however wlan card get disfunctional. I haven't been able to contact my wap even if i'm standing on it... i was afraid that it could have some side effects. it's probably because just writing a 0 to the MFUNC register is stupid...can you try to replace ti12xx_hook() in ti113x.h with this one? yes, now it works!!! (limited testing) I tried rebooting plugging/unplugging/swsuspending maybe 6 times. All of them working, that a new record :-) Should I try second step anyway? 3) unplug has resulted in kernel panic (twice) (btw: how do I do to capture and report those) at a first guess i would blame the atheros driver which taints the kernel. so try _not_ loading the atheros driver and see if it still happens. if so the messages please. to capture them you can use a serial console (null modem cable to second pc). check out the remote serial console howto on www.tldp.org might be...the driver...haven't tried wo/ it. note: I never got this after new hook, 4) when unlug don't produce kernel panic, then there is no way of power-oning that card again. 5) booting with the card inserted makes it not power on when yenta_socket is loaded (module) anything in dmesg then? zero comment: the card being disfunction could have something to with the driver. but before it worked sometimes... -- for TI bridges: turn off interrupts during card power-on. this seems to be neccessary for some combination of TI bridges with at least CB cards with atheros chipset...problem is that they produce an interrupt storm during power-on so the kernel happens to disable the IRQ which is a bad thing (tm). adds a generic hook function so that a socket driver can hook into almost anywhere (by adding more hook points of course). this is the cleanest way i can think of. and it allows adding more workarounds for more problems... for the TI specific interrupt on-off stuff just save the MFUNC register and set it to 0 to disable all interrupts, restore it afterwards. Signed-off-by: Daniel Ritz [EMAIL PROTECTED] Some thoughts: (not I'm neither pcmcia nor linux expert). The irq storm, shouldn't that be acked in someway. I.e. the card produced a lot of irq's (that get ignored) isn't the real solution to capture them, and do something clever? Instead of just shutting the card down. hmmm...wonder if that made sence it's the CB device that is making the interrupt storm and the TI bridge is stupid enough to let the interrupts thru during power on. thing is you can't ack them at this time because the cardbus resources are not set up at this time and ack'ing an IRQ is device specifc. ok Question: Why do you think that it worked sometimes before? pure luck? How about 2.4? can you compare cs code with 2.6? It always worked in 2.4... /Jonas can you also give me a dump of /proc/iomem? -0009efff : System RAM 0009f000-0009 : reserved 000a-000b : Video RAM area 000c-000c7fff : Video ROM 000cd000-000ce7ff : Adapter ROM 000e-000e : Extension ROM 000f-000f : System ROM 0010-0f6e : System RAM 0010-00409648 : Kernel code 00409649-005183ff : Kernel data 0f6f-0f6f : reserved 0f70-3f6e : System RAM 3f6f-3f6f7fff : ACPI Tables 3f6f8000-3f6f9fff : ACPI Non-volatile Storage 3f70-3fff : reserved 4000-43ff : :00:1f.1 40001000-40001fff : :02:01.0 40001000-40001fff : yenta_socket 4040-407f : PCI CardBus #03 4080-40bf : PCI CardBus #03 4080-4080 : :03:00.0 4080-4080 : ath d000-d007 : :00:02.0 d008-d00f : :00:02.1 d010-d01003ff : :00:1d.7 d010-d01003ff : ehci_hcd d0100800-d01008ff : :00:1f.5 d0100800-d01008ff : Intel 82801DB-ICH4 d0100c00-d0100dff : :00:1f.5 d0100c00-d0100dff : Intel 82801DB-ICH4 d020-d020 : :02:00.0 d020-d020 : tg3 e000-e7ff : :00:02.0 e800-efff : :00:02.1 ff80- : reserved - 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: yenta_socket nobody cared - Disabling IRQ #4 - WORKING!!
On Saturday 19 March 2005 09:05, Jonas Oreland wrote: Hi again and thx again, SUMMARY: It's working with new hook (wo/ trying second part) I'll post again if error comes up again. that's good news! Daniel Ritz wrote: On Saturday 19 March 2005 00:00, Jonas Oreland wrote: it's the second time now i see this problem with an atheros chipset in combination with a TI bridge. last time it was the 1225... attached a patch that could help... Report: 1) It works somewhat better. irq doesn't get disabled. 2) however wlan card get disfunctional. I haven't been able to contact my wap even if i'm standing on it... i was afraid that it could have some side effects. it's probably because just writing a 0 to the MFUNC register is stupid...can you try to replace ti12xx_hook() in ti113x.h with this one? yes, now it works!!! (limited testing) I tried rebooting plugging/unplugging/swsuspending maybe 6 times. All of them working, that a new record :-) Should I try second step anyway? not neccessarily.. 3) unplug has resulted in kernel panic (twice) (btw: how do I do to capture and report those) at a first guess i would blame the atheros driver which taints the kernel. so try _not_ loading the atheros driver and see if it still happens. if so the messages please. to capture them you can use a serial console (null modem cable to second pc). check out the remote serial console howto on www.tldp.org might be...the driver...haven't tried wo/ it. note: I never got this after new hook, 4) when unlug don't produce kernel panic, then there is no way of power-oning that card again. 5) booting with the card inserted makes it not power on when yenta_socket is loaded (module) anything in dmesg then? zero comment: the card being disfunction could have something to with the driver. but before it worked sometimes... -- for TI bridges: turn off interrupts during card power-on. this seems to be neccessary for some combination of TI bridges with at least CB cards with atheros chipset...problem is that they produce an interrupt storm during power-on so the kernel happens to disable the IRQ which is a bad thing (tm). adds a generic hook function so that a socket driver can hook into almost anywhere (by adding more hook points of course). this is the cleanest way i can think of. and it allows adding more workarounds for more problems... for the TI specific interrupt on-off stuff just save the MFUNC register and set it to 0 to disable all interrupts, restore it afterwards. Signed-off-by: Daniel Ritz [EMAIL PROTECTED] Some thoughts: (not I'm neither pcmcia nor linux expert). The irq storm, shouldn't that be acked in someway. I.e. the card produced a lot of irq's (that get ignored) isn't the real solution to capture them, and do something clever? Instead of just shutting the card down. hmmm...wonder if that made sence it's the CB device that is making the interrupt storm and the TI bridge is stupid enough to let the interrupts thru during power on. thing is you can't ack them at this time because the cardbus resources are not set up at this time and ack'ing an IRQ is device specifc. ok Question: Why do you think that it worked sometimes before? pure luck? How about 2.4? can you compare cs code with 2.6? It always worked in 2.4... the problem is there also, it just doesn't show up. 2.6 checks for every interrupt if one of the handlers took care of it. if not the dump is printed and a counter is increased. if this counter reaches a limit the interrupt line is disabled. 2.4 doesn't do it so the interrupt storm is there too, it just recovers...you can try with 2.4...after you have the card up do a cat /proc/interrupts and you'll see a high number for yenta's interrupt line... /Jonas can you also give me a dump of /proc/iomem? [snip /proc/iomem] it was just to be sure nothing is mapped over existing physical RAM which is not the case... i'll cook up a more flexible patch which handles other TI bridges as well (the current one will fail on some older controllers and on 2-slot controllers) rgds -daniel - 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/
