Re: [PATCH 0/9] -stable review
Chris Wright wrote: This is the start of the stable review cycle for the 2.6.13.1 release. There are 9 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let us know. If anyone is a maintainer of the proper subsystem, and wants to add a signed-off-by: line to the patch, please respond with it. *snip* I didn't see the patch from Ivan Kokshaysky ( http://marc.theaimsgroup.com/?l=linux-kernel=112541348008047=2 ) included.. Without this one my laptop will freeze and die when inserting a something into the cardbus slot, so I would say that it would kind of fit in there. Any reason why it's not included? -- Henrik signature.asc Description: OpenPGP digital signature
Re: [PATCH 0/9] -stable review
Chris Wright wrote: This is the start of the stable review cycle for the 2.6.13.1 release. There are 9 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let us know. If anyone is a maintainer of the proper subsystem, and wants to add a signed-off-by: line to the patch, please respond with it. *snip* I didn't see the patch from Ivan Kokshaysky ( http://marc.theaimsgroup.com/?l=linux-kernelm=112541348008047w=2 ) included.. Without this one my laptop will freeze and die when inserting a something into the cardbus slot, so I would say that it would kind of fit in there. Any reason why it's not included? -- Henrik signature.asc Description: OpenPGP digital signature
Re: Linux 2.6.13
Greg KH wrote: > On Wed, Aug 31, 2005 at 12:41:03AM +0200, Henrik Persson wrote: > >>Linus Torvalds wrote: >> >>>There it is. >>> >>>The most painful part of 2.6.13 is likely to be the fact that we made x86 >>>use the generic PCI bus setup code for assigning unassigned resources. >>>That uncovered rather a lot of nasty small details, but should also mean >>>that a lot of laptops in particular should be able to discover PCI devices >>>behind bridges that the BIOS hasn't set up. >>> >>>We've hopefully fixed up all the problems that the longish -rc series >>>showed, and it shouldn't be that painful, but if you have device problems, >>>please make a report that at a minimum contains the unified diff of the >>>output of "lspci -vvx" running on 2.6.12 vs 2.6.13. That might give us >>>some clues. >> >>Well. 2.6.13 won't boot if I have my Netgear WG511 in the cardbus slot. >>It boots just fine if it isn't inserted, though. If I insert it later >>on, the computer will freeze and won't respond, just like it does on boot. >> >>2.6.12.5 works just fine, and I just did make oldconfig and used the >>defaults (except for the hardware monitoring). >> >>Suggestions, anyone? > > > Can you try the patch posted to lkml at: > http://marc.theaimsgroup.com/?l=linux-kernel=112541348008047=2 > from Ivan to see if that helps this? Indeed. 2.6.13 now booting without any problems at all (well, no problems yet anyway..) :) -- Henrik Persson signature.asc Description: OpenPGP digital signature
Re: Linux 2.6.13
Greg KH wrote: On Wed, Aug 31, 2005 at 12:41:03AM +0200, Henrik Persson wrote: Linus Torvalds wrote: There it is. The most painful part of 2.6.13 is likely to be the fact that we made x86 use the generic PCI bus setup code for assigning unassigned resources. That uncovered rather a lot of nasty small details, but should also mean that a lot of laptops in particular should be able to discover PCI devices behind bridges that the BIOS hasn't set up. We've hopefully fixed up all the problems that the longish -rc series showed, and it shouldn't be that painful, but if you have device problems, please make a report that at a minimum contains the unified diff of the output of lspci -vvx running on 2.6.12 vs 2.6.13. That might give us some clues. Well. 2.6.13 won't boot if I have my Netgear WG511 in the cardbus slot. It boots just fine if it isn't inserted, though. If I insert it later on, the computer will freeze and won't respond, just like it does on boot. 2.6.12.5 works just fine, and I just did make oldconfig and used the defaults (except for the hardware monitoring). Suggestions, anyone? Can you try the patch posted to lkml at: http://marc.theaimsgroup.com/?l=linux-kernelm=112541348008047w=2 from Ivan to see if that helps this? Indeed. 2.6.13 now booting without any problems at all (well, no problems yet anyway..) :) -- Henrik Persson signature.asc Description: OpenPGP digital signature
Re: Linux 2.6.13
Linus Torvalds wrote: > There it is. > > The most painful part of 2.6.13 is likely to be the fact that we made x86 > use the generic PCI bus setup code for assigning unassigned resources. > That uncovered rather a lot of nasty small details, but should also mean > that a lot of laptops in particular should be able to discover PCI devices > behind bridges that the BIOS hasn't set up. > > We've hopefully fixed up all the problems that the longish -rc series > showed, and it shouldn't be that painful, but if you have device problems, > please make a report that at a minimum contains the unified diff of the > output of "lspci -vvx" running on 2.6.12 vs 2.6.13. That might give us > some clues. Well. 2.6.13 won't boot if I have my Netgear WG511 in the cardbus slot. It boots just fine if it isn't inserted, though. If I insert it later on, the computer will freeze and won't respond, just like it does on boot. 2.6.12.5 works just fine, and I just did make oldconfig and used the defaults (except for the hardware monitoring). Suggestions, anyone? diff -u of lspci -vvx + lspci output attached. It's an Acer Aspire 1302XV. -- Henrik Persson --- lspci-2.6.12.5 2005-08-31 00:31:46.274810568 +0200 +++ lspci-2.6.132005-08-31 00:26:45.718371000 +0200 @@ -6,7 +6,7 @@ Region 0: Memory at a000 (32-bit, prefetchable) [size=64M] Capabilities: [a0] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4 - Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP+ GART64- 64bit- FW- Rate= + Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate= Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- @@ -40,16 +40,16 @@ Interrupt: pin A routed to IRQ 11 Region 0: Memory at 2f00 (32-bit, non-prefetchable) [size=4K] Bus: primary=00, secondary=02, subordinate=05, sec-latency=176 - Memory window 0: 2f40-2f7ff000 (prefetchable) - Memory window 1: 2f80-2fbff000 - I/O window 0: 4000-40ff - I/O window 1: 4400-44ff - BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt- PostWrite+ + Memory window 0: 3000-31fff000 (prefetchable) + Memory window 1: 3200-33fff000 + I/O window 0: 1000-10ff + I/O window 1: 1400-14ff + BridgeCtl: Parity- SERR- ISA- VGA- MAbort- >Reset- 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 00: 17 12 72 69 87 00 10 04 00 00 07 06 00 a8 02 00 -10: 00 00 00 2f a0 00 00 02 00 02 05 b0 00 00 40 2f -20: 00 f0 7f 2f 00 00 80 2f 00 f0 bf 2f 01 40 00 00 -30: fd 40 00 00 01 44 00 00 fd 44 00 00 0b 01 00 05 +10: 00 00 00 2f a0 00 00 02 00 02 05 b0 00 00 00 30 +20: 00 f0 ff 31 00 00 00 32 00 f0 ff 33 01 10 00 00 +30: fd 10 00 00 01 14 00 00 fd 14 00 00 0b 01 80 05 40: 25 10 1d 00 01 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 @@ -163,13 +163,13 @@ Interrupt: pin A routed to IRQ 11 Region 0: Memory at e000 (32-bit, non-prefetchable) [size=512K] Region 1: Memory at 9000 (32-bit, prefetchable) [size=128M] - Expansion ROM at 000c [disabled] [size=64K] + Expansion ROM at 9800 [disabled] [size=64K] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [80] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA- ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x4 - Command: RQ=32 ArqSz=0 Cal=0 SBA- AGP+ GART64- 64bit- FW- Rate=x4 + Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=x4 00: 33 53 02 8d 07 00 30 02 01 00 00 03 04 40 00 00 10: 00 00 00 e0 08 00 00 90 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 25 10 1d 00 :00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 80) Subsystem: Acer Incorporated [ALI]: Unknown device 001d Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- 00: 06 11 05 03 06 00 10 a2 80 00 00 06 00 08 00 00 10: 08 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 25 10 1d 00 30: 00 00 00 00 a0 00 00 00 00 00 00 00 00 00 00 00 :00:
Re: Linux 2.6.13
Linus Torvalds wrote: There it is. The most painful part of 2.6.13 is likely to be the fact that we made x86 use the generic PCI bus setup code for assigning unassigned resources. That uncovered rather a lot of nasty small details, but should also mean that a lot of laptops in particular should be able to discover PCI devices behind bridges that the BIOS hasn't set up. We've hopefully fixed up all the problems that the longish -rc series showed, and it shouldn't be that painful, but if you have device problems, please make a report that at a minimum contains the unified diff of the output of lspci -vvx running on 2.6.12 vs 2.6.13. That might give us some clues. Well. 2.6.13 won't boot if I have my Netgear WG511 in the cardbus slot. It boots just fine if it isn't inserted, though. If I insert it later on, the computer will freeze and won't respond, just like it does on boot. 2.6.12.5 works just fine, and I just did make oldconfig and used the defaults (except for the hardware monitoring). Suggestions, anyone? diff -u of lspci -vvx + lspci output attached. It's an Acer Aspire 1302XV. -- Henrik Persson --- lspci-2.6.12.5 2005-08-31 00:31:46.274810568 +0200 +++ lspci-2.6.132005-08-31 00:26:45.718371000 +0200 @@ -6,7 +6,7 @@ Region 0: Memory at a000 (32-bit, prefetchable) [size=64M] Capabilities: [a0] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4 - Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP+ GART64- 64bit- FW- Rate=none + Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=none Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- @@ -40,16 +40,16 @@ Interrupt: pin A routed to IRQ 11 Region 0: Memory at 2f00 (32-bit, non-prefetchable) [size=4K] Bus: primary=00, secondary=02, subordinate=05, sec-latency=176 - Memory window 0: 2f40-2f7ff000 (prefetchable) - Memory window 1: 2f80-2fbff000 - I/O window 0: 4000-40ff - I/O window 1: 4400-44ff - BridgeCtl: Parity- SERR- ISA- VGA- MAbort- Reset- 16bInt- PostWrite+ + Memory window 0: 3000-31fff000 (prefetchable) + Memory window 1: 3200-33fff000 + I/O window 0: 1000-10ff + I/O window 1: 1400-14ff + BridgeCtl: Parity- SERR- ISA- VGA- MAbort- Reset- 16bInt+ PostWrite+ 16-bit legacy interface ports at 0001 00: 17 12 72 69 87 00 10 04 00 00 07 06 00 a8 02 00 -10: 00 00 00 2f a0 00 00 02 00 02 05 b0 00 00 40 2f -20: 00 f0 7f 2f 00 00 80 2f 00 f0 bf 2f 01 40 00 00 -30: fd 40 00 00 01 44 00 00 fd 44 00 00 0b 01 00 05 +10: 00 00 00 2f a0 00 00 02 00 02 05 b0 00 00 00 30 +20: 00 f0 ff 31 00 00 00 32 00 f0 ff 33 01 10 00 00 +30: fd 10 00 00 01 14 00 00 fd 14 00 00 0b 01 80 05 40: 25 10 1d 00 01 00 00 00 00 00 00 00 00 00 00 00 50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 60: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 @@ -163,13 +163,13 @@ Interrupt: pin A routed to IRQ 11 Region 0: Memory at e000 (32-bit, non-prefetchable) [size=512K] Region 1: Memory at 9000 (32-bit, prefetchable) [size=128M] - Expansion ROM at 000c [disabled] [size=64K] + Expansion ROM at 9800 [disabled] [size=64K] Capabilities: [dc] Power Management version 2 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=0 PME- Capabilities: [80] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA- ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x4 - Command: RQ=32 ArqSz=0 Cal=0 SBA- AGP+ GART64- 64bit- FW- Rate=x4 + Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP- GART64- 64bit- FW- Rate=x4 00: 33 53 02 8d 07 00 30 02 01 00 00 03 04 40 00 00 10: 00 00 00 e0 08 00 00 90 00 00 00 00 00 00 00 00 20: 00 00 00 00 00 00 00 00 00 00 00 00 25 10 1d 00 :00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 80) Subsystem: Acer Incorporated [ALI]: Unknown device 001d Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR+ Latency: 8 Region 0: Memory at a000 (32-bit, prefetchable) [size=64M] Capabilities: [a0] AGP version 2.0 Status: RQ=32 Iso- ArqSz=0 Cal=0 SBA+ ITACoh- GART64- HTrans- 64bit- FW- AGP3- Rate=x1,x2,x4 Command: RQ=1 ArqSz=0 Cal=0 SBA- AGP+ GART64- 64bit- FW- Rate=none Capabilities: [c0] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold
Re: Touchpad "tapping" changes in 2.6.11?
Dmitry Torokhov wrote: On Mon, 07 Mar 2005 14:14:02 +0100, Henrik Persson <[EMAIL PROTECTED]> wrote: Hi there. I noticed that the ALPS driver was added to 2.6.11, a thing that alot of people probably like, but since my touchpad (Acer Aspire 1300XV) worked perfectly before (like, 2.6.10) and now the ALPS driver disables 'hardware tapping', wich makes it hard to tap. I commented out the disable-tapping bits in alps.c and now it's working like a charm again. Hi, Could you please try 2.6.11-mm1. It has bunch of Peter Osterlund's patches that shoudl improve the situation with tapping. Well, -mm1 didn't quite agree with my savage gfx drivers. But I'm booting with psmouse.proto=exps now, and it's working the way I'm used to now. The Aspire 1300-series is quite different from the 1350 ones.. The touchpad on the 1300 will work like a charm without the synaptics driver (but no fancy stuff is supported, I guess). Before you could boot and be happy without the synaptics driver, now you probably have to install the synaptics driver to be happy.. Maybe that's not so good. :) Could this touchpad use the "exps" proto as default and then you could reconfigure if you want to use the ALPS driver..? -- Henrik Persson - 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/
Touchpad "tapping" changes in 2.6.11?
Hi there. I noticed that the ALPS driver was added to 2.6.11, a thing that alot of people probably like, but since my touchpad (Acer Aspire 1300XV) worked perfectly before (like, 2.6.10) and now the ALPS driver disables 'hardware tapping', wich makes it hard to tap. I commented out the disable-tapping bits in alps.c and now it's working like a charm again. Maybe the hardware tapping-thing should be configurable via some boot or config option? -- Henrik Persson - 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/
Touchpad tapping changes in 2.6.11?
Hi there. I noticed that the ALPS driver was added to 2.6.11, a thing that alot of people probably like, but since my touchpad (Acer Aspire 1300XV) worked perfectly before (like, 2.6.10) and now the ALPS driver disables 'hardware tapping', wich makes it hard to tap. I commented out the disable-tapping bits in alps.c and now it's working like a charm again. Maybe the hardware tapping-thing should be configurable via some boot or config option? -- Henrik Persson - 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: Touchpad tapping changes in 2.6.11?
Dmitry Torokhov wrote: On Mon, 07 Mar 2005 14:14:02 +0100, Henrik Persson [EMAIL PROTECTED] wrote: Hi there. I noticed that the ALPS driver was added to 2.6.11, a thing that alot of people probably like, but since my touchpad (Acer Aspire 1300XV) worked perfectly before (like, 2.6.10) and now the ALPS driver disables 'hardware tapping', wich makes it hard to tap. I commented out the disable-tapping bits in alps.c and now it's working like a charm again. Hi, Could you please try 2.6.11-mm1. It has bunch of Peter Osterlund's patches that shoudl improve the situation with tapping. Well, -mm1 didn't quite agree with my savage gfx drivers. But I'm booting with psmouse.proto=exps now, and it's working the way I'm used to now. The Aspire 1300-series is quite different from the 1350 ones.. The touchpad on the 1300 will work like a charm without the synaptics driver (but no fancy stuff is supported, I guess). Before you could boot and be happy without the synaptics driver, now you probably have to install the synaptics driver to be happy.. Maybe that's not so good. :) Could this touchpad use the exps proto as default and then you could reconfigure if you want to use the ALPS driver..? -- Henrik Persson - 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: [BK] upgrade will be needed
Paolo Ciarrocchi wrote: On Mon, 14 Feb 2005 21:36:51 +0100, Adrian Bunk <[EMAIL PROTECTED]> wrote: Disclaimer: I did never use BK and I do not plan to use it. Same here, but just because I'm not a developer ;-) [...] I don't know about copyright law in other countries (and the USA have both a pretty different legal system and a pretty different copyright law than Germany), but in Germany the clause you mentioned is simply void according to German copyright law. German copyright law doesn't distinguish whether you get money for allowing the usage of the program or not. The licence is still valid but the clause is void. I can accept a void licence clause because this doesn't make it non-void. That's not uncommon. Perhaps 95% of all software licences contain clauses that are simply void. In case you ask: No, there is no case law in Germany - we have a different legal system. If you like it or not - at least for people in Germany, I see no way how the law allows you to enforce what you are trying to do. You can say it might be morally wrong to break this licence clause - but this doesn't make it illegal. If we bring moral into the game, alot of people would say that it's immoral of bitmover to have such a license.. I might agree. ;) I think this is true not only in Germany, if I were Larry I would check if the licence is valid in EU. Well..read the archives. This has been discussed at least once before, with the same conclusions. This is just noise noise noise. We've heard it all before. :) -- Henrik Persson - 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: [BK] upgrade will be needed
Paolo Ciarrocchi wrote: On Mon, 14 Feb 2005 21:36:51 +0100, Adrian Bunk [EMAIL PROTECTED] wrote: Disclaimer: I did never use BK and I do not plan to use it. Same here, but just because I'm not a developer ;-) [...] I don't know about copyright law in other countries (and the USA have both a pretty different legal system and a pretty different copyright law than Germany), but in Germany the clause you mentioned is simply void according to German copyright law. German copyright law doesn't distinguish whether you get money for allowing the usage of the program or not. The licence is still valid but the clause is void. I can accept a void licence clause because this doesn't make it non-void. That's not uncommon. Perhaps 95% of all software licences contain clauses that are simply void. In case you ask: No, there is no case law in Germany - we have a different legal system. If you like it or not - at least for people in Germany, I see no way how the law allows you to enforce what you are trying to do. You can say it might be morally wrong to break this licence clause - but this doesn't make it illegal. If we bring moral into the game, alot of people would say that it's immoral of bitmover to have such a license.. I might agree. ;) I think this is true not only in Germany, if I were Larry I would check if the licence is valid in EU. Well..read the archives. This has been discussed at least once before, with the same conclusions. This is just noise noise noise. We've heard it all before. :) -- Henrik Persson - 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: BP6: APIC, rtl8139 & sound
Argh, I just tried the kernels up to 2.4.4-pre4, not the pre5! Some sleep and then I will try it! /P-H Per-Henrik Persson 0703-68 53 86 [EMAIL PROTECTED] http://www.whatever.nu "With digital it's all or nothing!" "Just because something doesn't work, it doesn't mean it can't be used..." On Fri, 20 Apr 2001, Jeff Garzik wrote: > Per-Henrik Persson wrote: > > If i start to use the NIC, like som browsing on the internet i occassionly > > get: > > > > eth0: Too much work at interrupt, IntrStatus=0x0001. > > You need the 8139too driver update, from 2.4.4-pre5, 2.4.3-ac7, or > http://sourceforge.net/projects/gkernel/ > > -- > Jeff Garzik | "The universe is like a safe to which there is a > Building 1024 | combination -- but the combination is locked up > MandrakeSoft | in the safe."-- Peter DeVries > - 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: BP6: APIC, rtl8139 sound
Argh, I just tried the kernels up to 2.4.4-pre4, not the pre5! Some sleep and then I will try it! /P-H Per-Henrik Persson 0703-68 53 86 [EMAIL PROTECTED] http://www.whatever.nu "With digital it's all or nothing!" "Just because something doesn't work, it doesn't mean it can't be used..." On Fri, 20 Apr 2001, Jeff Garzik wrote: Per-Henrik Persson wrote: If i start to use the NIC, like som browsing on the internet i occassionly get: eth0: Too much work at interrupt, IntrStatus=0x0001. You need the 8139too driver update, from 2.4.4-pre5, 2.4.3-ac7, or http://sourceforge.net/projects/gkernel/ -- Jeff Garzik | "The universe is like a safe to which there is a Building 1024 | combination -- but the combination is locked up MandrakeSoft | in the safe."-- Peter DeVries - 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/
BP6: APIC, rtl8139 & sound
Hi, I'v been lurking around all archives from this list trying to find an answer to my problem but with no success so I take the step ant mail it to this list. My hardware setup is as following: Abit BP6, 2xCeleron 366, G400, old Matrox-card, sym53c8xx SCSI, Trident 4DWave NX sound, rtl8139 NIC. lspci: 00:00.0 Host bridge: Intel Corporation 440BX/ZX - 82443BX/ZX Host bridge (rev 03) 00:01.0 PCI bridge: Intel Corporation 440BX/ZX - 82443BX/ZX AGP bridge (rev 03) 00:07.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 02) 00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) 00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) 00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 02) 00:09.0 Multimedia audio controller: Trident Microsystems 4DWave NX (rev 02) 00:0b.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 10) 00:0d.0 SCSI storage controller: Symbios Logic Inc. (formerly NCR) 53c895 (rev 01) 00:0f.0 Display controller: Matrox Graphics, Inc. MGA 2064W [Millennium] (rev 01) 00:13.0 Unknown mass storage controller: Triones Technologies, Inc. HPT366 (rev 01) 00:13.1 Unknown mass storage controller: Triones Technologies, Inc. HPT366 (rev 01) 01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G400 AGP (rev 03) cat /proc/interupts: CPU0 CPU1 0: 79118 75272IO-APIC-edge timer 1: 2261 2358IO-APIC-edge keyboard 2: 0 0 XT-PIC cascade 8: 0 1IO-APIC-edge rtc 12: 33056 32767IO-APIC-edge PS/2 Mouse 14: 3 22IO-APIC-edge ide0 15: 8 24IO-APIC-edge ide1 16: 0 0 IO-APIC-level mga@PCI:1:0:0 17:100 94 IO-APIC-level sym53c8xx 18: 45894 45820 IO-APIC-level ide2, eth0 19: 38881 40110 IO-APIC-level usb-uhci, Trident 4DWave PCI NMI: 0 0 LOC: 154313 154315 ERR:6994982 I recently made a full reinstall of my Debian-system, from scratch. I also upgraded to 2.4.3, ALSA for sound. Now I have a lot of problems! When using my system, not using the NIC, not using sound I get some errors like: APIC error on CPU0: 02(02) APIC error on CPU1: 01(01) APIC error on CPU0: 02(02) APIC error on CPU1: 01(01) If i start to use the NIC, like som browsing on the internet i occassionly get: eth0: Too much work at interrupt, IntrStatus=0x0001. The number of that kind of messages increases with harder network traffic. A floodping TO my computer generates like 50 messages... If I then start to use the sound (playing MP3's) i sometimes get _small_ lockups when X won't respond. If I at the same time generate some activity on the harddisk connected to IDE2 I get longer lockups. A "cat /proc/interupts" shows that I get a lot of interupt errors :( Every now and then i get a lockup for like 10 seconds and as you can see from my /proc/interupts above I get MILLIONS of interrupt errors! A "dmesg" will give me an infinite stream of APIC-errors... Do anyone have a solution for my problem? Last but not least, I haven't joined the kernel-list because I have some troubles with the internet connection to my mailserver. Would it be possible to CC all answers to [EMAIL PROTECTED] ? Thanx in advance, P-H ******** Per-Henrik Persson 0703-68 53 86 [EMAIL PROTECTED] http://www.whatever.nu -stupid webcam online 24h a day "With digital it's all or nothing!" "Just because something doesn't work, it doesn't mean it can't be used..." - 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/
