Re: How to plan a kernel update ?
Hello, I won't be harsh but google is your best friend and first source for it. please take a look at: http://linuxdevices.com/articles/AT3855888078.html They have a good guide and what should need attention in migrating to Kernel 2.6 They also have related articles for drivers in Kernel 2.6,NPTL and such. Best regards -- Michael Thonke Weber Ress schrieb: Hi, I'm responsible to planning a kernel upgrade in many servers, from 2.4 version to 2.6.13 (last stable version), using Debian 3.1r0a My team has good technical skills, but they need to be led. I would like know, what's the best pratices and recommendations that a project manager need think BEFORE an kernel upgrade. A technical guy have a particular vision about this upgrade, but I will be very been thankful if I receive from this community another vision.. a vision centered in the project process (planning, executing, controlling) to make this activity successfully. Thank's ! Weber Ress - 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/ - 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: 2.6.13-mm2
Hello Andrew, I found a problem regarding to multi device support (Linux software Raid). The problem first appears now in 2.6.13-mm2, that the kernel didn't initialize the md devices. 2.6.13-mm1 works very well, and everything is okay. Also one strange thing I found was that my SATA devices were initialized a-sync/disordered e.g SATA1 with one hdd then something like USB and IPv4 and such and at least SATA3: with 2nd hdd. That I've never seen this order init order before. Seems to be mixed all around. I tried irqpoll,pci=routeirq with no success. I can't provide some logs, because I can't grep the dmesg since it doesn't boot. There are changes in libata driver for sata_nv? Or md driver changes that cause that? Thanks Best regards -- Michael Thonke - 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: 2.6.13-mm2
Hello Andrew, I found a problem regarding to multi device support (Linux software Raid). The problem first appears now in 2.6.13-mm2, that the kernel didn't initialize the md devices. 2.6.13-mm1 works very well, and everything is okay. Also one strange thing I found was that my SATA devices were initialized a-sync/disordered e.g SATA1 with one hdd then something like USB and IPv4 and such and at least SATA3: with 2nd hdd. That I've never seen this order init order before. Seems to be mixed all around. I tried irqpoll,pci=routeirq with no success. I can't provide some logs, because I can't grep the dmesg since it doesn't boot. There are changes in libata driver for sata_nv? Or md driver changes that cause that? Thanks Best regards -- Michael Thonke - 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: How to plan a kernel update ?
Hello, I won't be harsh but google is your best friend and first source for it. please take a look at: http://linuxdevices.com/articles/AT3855888078.html They have a good guide and what should need attention in migrating to Kernel 2.6 They also have related articles for drivers in Kernel 2.6,NPTL and such. Best regards -- Michael Thonke Weber Ress schrieb: Hi, I'm responsible to planning a kernel upgrade in many servers, from 2.4 version to 2.6.13 (last stable version), using Debian 3.1r0a My team has good technical skills, but they need to be led. I would like know, what's the best pratices and recommendations that a project manager need think BEFORE an kernel upgrade. A technical guy have a particular vision about this upgrade, but I will be very been thankful if I receive from this community another vision.. a vision centered in the project process (planning, executing, controlling) to make this activity successfully. Thank's ! Weber Ress - 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/ - 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: NCQ support NVidia NForce4 (CK804) SATAII
Jeff Garzik schrieb: Michael Thonke wrote: Jeff Garzik schrieb: Please enable ATA_DEBUG and ATA_VERBOSE_DEBUG, and send me the output. I tried that Jeff, but the base problem is on the low-level.. There may be a BIOS problem, but there is no problem with the controller using SATA II drives. Can you boot with another drive, and then send the output requested above? Sorry, but I can't provide them, because I changed the VIA chipset based mainboard against a NForce4 Ultra chipset mainboard. But on heise.de they also pointed out that it's VIA's bug. Not the harddrives one, they have some but this not apply on VIA. Samsung act and updated the firmware of their drives for compatibility reasons. And the work-around is to jumper the hdd as SATA I hdd. The problem was, that my system to this time was not bootable with my Samsungs Hd160JJ and VIA VT8237. Nos they fix it with a new Chipset the VT8327R...where we don't need a work-around. <http://www.via.com.tw/en/products/chipsets/southbridge/vt8237/> Jeff Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Lennart Sorensen schrieb: On Thu, Aug 11, 2005 at 07:38:12PM +0200, Michael Thonke wrote: I have a ASUS A8V Deluxe too, and can't use the AMD X2 processor on it...this is a feature..right? Supposed to run with DualCore but don't post..hm. Well according to Asus you can if you run BIOS 1013 or 1014 on the board. Any less and it won't boot. What they say is escapist - far away.. Now I certainly can't try it given I don't have such a CPU. Well, don't go to holiday and spend the money for this genial CPU. My SATA II devices. Get not regonized from the VIA SATA controller...this bug is known. So I want to use my HDD's I bought ...why should I set my SATA II device to be SATA I. So a SATA II drive doesn't work at all? Jep. On VIA chipsets..it would be to flacky to say SATA II drives doesn't work at all. But its like the Smart-Table and what vendors implement and who did the interpretation of specs:-) It's like a fairy tale..the hardware fairy tale. Is also a feature of VIA Chipsets, right? "It's not a bug, hey let's say is a feature." Common practice it seems. "Wouldn't be the would in there, the world would be boring." Len Sorensen Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Jeff Garzik schrieb: Michael Thonke wrote: I have a ASUS A8V Deluxe too, and can't use the AMD X2 processor on it...this is a feature..right? Supposed to run with DualCore but don't post..hm. What does ASUS say about this? You can't just plug a new processor into an old motherboard and expect it to work, generally. Hello Jeff, No they don't like AMD x2 DualCore cpus. ASUS is not interesseted in the bugs I found...Silicon Image helped me to get Samsung SATA II drivers working on the Sil3132 chip and gave me a update/firmware. But ASUS ...what should I say? They say no problem encountered by us so far...don't use linux...and thorw off the phone..while you want to talk..*sigh* My SATA II devices. Get not regonized from the VIA SATA controller...this bug is known. So I want to use my HDD's I bought ...why should I set my SATA II device to be SATA I. And nope they don't work, no drive which with SATAII operate without tweak on VIA Southbridges..SATA controller. Hitachi,Samsung,WD I refer to the article of heise.de This article from heise.de is german sorry...but maybe you understand what they wrote http://www.heise.de/newsticker/meldung/62189 Haven't found a Please enable ATA_DEBUG and ATA_VERBOSE_DEBUG, and send me the output. I tried that Jeff, but the base problem is on the low-level.. Like the one I ound with Sil3132. SATA II devices can be used on SATA I controllers just fine, with no need to tweak settings. Jeff Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Lennart Sorensen schrieb: On Thu, Aug 11, 2005 at 01:20:56PM -0400, Jeff Garzik wrote: What specifically does not work, on VIA+AMD64 combination, under Linux? My Athlon64 with VIA chipset works great. Mine does too. Asus A8V Deluxe. No problems so far. Everything on the board I have tried just works. AMD X2 DualCore? Can't say my A7N8X-E Deluxe has any real issues either. I may only get ac97 audio level out of the nifty DSP, but I hardly use sound on the system anyhow, so I don't mind. forcedeth driver works for networking, sil3112a sata works with WD drives no problem, nvidia ide controller seems to work fine with dvd drives, firewire works, yukon sk98lin works Yes, Marvell, Silicon Image no problem as they provide OpenSource drivers. On a normal setup is nearly everything okay. I hold up a hardware testlab to find b** *features* the specification don't show/hold. Things that can go scary for production usage - that's my job. too, usb is fine. No complaints from me. USB works also great for all chipsets :-) Len Sorensen Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Jeff Garzik schrieb: Michael Thonke wrote: There is no other way to use a nearly good chipset for AMD64 cpus. Via's chipsets are really buggy not acceptable, so what else ULi/Ali who cares where to buy? What specifically does not work, on VIA+AMD64 combination, under Linux? I have a ASUS A8V Deluxe too, and can't use the AMD X2 processor on it...this is a feature..right? Supposed to run with DualCore but don't post..hm. My Athlon64 with VIA chipset works great. My SATA II devices. Get not regonized from the VIA SATA controller...this bug is known. So I want to use my HDD's I bought ...why should I set my SATA II device to be SATA I. Is also a feature of VIA Chipsets, right? Jeff "It's not a bug, hey let's say is a feature." Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Roger Heflin schrieb: For high end stuff Serverworks is supposed to have some AMD stuff soon (this is rumor I heard). If there where some pieces for desktop from AMD orignially I would take them..but they don't offer...that's the point...to cry. Like Intel offer ..Intel CPU + Intel Chipset best combination overall ATM. From what Allen said, the implication to me is that something in the current NVIDIA stat NCQ chipset is *not* fully under NVIDIA's control, What the sell hardware they can't support or develop driver for it.. okay that's the point why many windows users complain about Data corruption. Thanks for raising this point. ie they got some piece of technology from someone else and cannot disclose its details, which would be why the could release a "clean" redesigned one. Roger A bit late or not? What we have done to get this punishment? I love Linux and I won't move from it because of it...loyality :-) -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Lee Revell schrieb: On Thu, 2005-08-11 at 17:17 +0200, Michael Thonke wrote: *frustrated* Hey I don't like it any more than you do. But Nvidia is an IP company and they act like one. Most of us would probably do the exact same thing in their position, AKA whatever the lawyers tell them ;-) Lee Jepp Lee your are right. Well, the lawyers sometimes like cancer..nobody wants them nobody need them, but they still there. *hard ironic* Couldn't we tie all togehter, to make the world better? To make more hardware loving Linux? And peace on earth *ironic off - taken from Miss Hardware Support election live from Germany* But omitting a costumer in some decisions could break there neck.. If we would have such company we would may do something like that, but hey..saying my Hardware is Linux friendly is much cooler :-) And mh some goverments and schools using AMD and NForce Chipsets..this is a lost market..they are blind? In my old school we had 200 + 100 computers with NForce2..and they wanted to move to Linux OS..but can't..sharing my knowledge stuck at the point of driver support from NVidia for Linux so the problem was on the root (hardware). Now they changed to Intel and what happen no NVidia anymore - isn't the worth would NVidia say right? Greets & Best regards Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Lee Revell schrieb: On Thu, 2005-08-11 at 09:09 +0200, Gábor Lénárt wrote: I want to buy a new system including motherboard with some Athlon64 CPU. I was told that nforce4 chipset is the "right" choice. However I'm using *only* Linux Who told you that? Some Windows user? (1.) There is no other way to use a nearly good chipset for AMD64 cpus. Via's chipsets are really buggy not acceptable, so what else ULi/Ali who cares where to buy? Any hardware from them on european market..can't see them until yesterday. It's common knowledge that Nvidia is not Linux friendly. Their business is making hardware so people can play games on Windows. (2.) This is not correct, not everybody play games only on windows or only buy hardware for gaming.. reasons please look at (1.) Anything that their lawyers think might have a 0.0001% chance of interfering with that business model in the slightest bit will not happen. Lee *ironic* Mh so I should take my lawyer and say..hey NVidia cheated me..can't use there hardware completly under Linux but I bought it and can't use it correctly. *ironic off* Sum it up either use Intel and Intel Hardware or die on Linux...*frustrated* Greets & Best regards Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Allen Martin schrieb: Erm, why they are not willing to support NCQ under Linux...I mean many people using NVIDIA based mainboards. And that against that what I thought NVidia stands for - Linux friendly but seems only that this statement fit on graficcards? Is there no "responsible" person that says...Hello, Linux is a growing market that we need to serve? With full driver/program support? Likely the only way nForce4 NCQ support could be added under Linux would be with a closed source binary driver, and no one really wants that, especially for storage / boot volume. Who won't have drivers for Linux? Who told you that..? It would be a start point if closed or not closed source but say never ever as your mail suggest is not a way to go.Whats about Servers that using NForce Based Chipsets and they need NCQ? Always saying not needed or so hard to hand out specs..is the lazy way that a company like NVidia shouldn't go. We decided it wasn't worth the headache of a binary driver for this one feature. Yes,you Nvidia decide..what's about the costumer dosn't the costumer option counts? It's the A and the O of costumer relationship. Holding up a possiblity is better than say: "Oh, the costumers buy our hardware but have no right to use it at all." So I paid 120€ for a NVidia Nforce4 and 3 Mainboard..and what..I can't use it correctly only in Windows? NVidia seems only interesseted in GPU market so they hand out a bit of drivers...mh they are also closed source..so the argument you offered aboved is senseless...because NVidia do so for quite a long time. Future nForce chipsets will have a redesigned SATA controller where we can be more open about documenting it. -Allen So this was the last piece of NVidia I bought...about 400 Workstation ..is not the worth. Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Allen Martin schrieb: Erm, why they are not willing to support NCQ under Linux...I mean many people using NVIDIA based mainboards. And that against that what I thought NVidia stands for - Linux friendly but seems only that this statement fit on graficcards? Is there no responsible person that says...Hello, Linux is a growing market that we need to serve? With full driver/program support? Likely the only way nForce4 NCQ support could be added under Linux would be with a closed source binary driver, and no one really wants that, especially for storage / boot volume. Who won't have drivers for Linux? Who told you that..? It would be a start point if closed or not closed source but say never ever as your mail suggest is not a way to go.Whats about Servers that using NForce Based Chipsets and they need NCQ? Always saying not needed or so hard to hand out specs..is the lazy way that a company like NVidia shouldn't go. We decided it wasn't worth the headache of a binary driver for this one feature. Yes,you Nvidia decide..what's about the costumer dosn't the costumer option counts? It's the A and the O of costumer relationship. Holding up a possiblity is better than say: Oh, the costumers buy our hardware but have no right to use it at all. So I paid 120€ for a NVidia Nforce4 and 3 Mainboard..and what..I can't use it correctly only in Windows? NVidia seems only interesseted in GPU market so they hand out a bit of drivers...mh they are also closed source..so the argument you offered aboved is senseless...because NVidia do so for quite a long time. Future nForce chipsets will have a redesigned SATA controller where we can be more open about documenting it. -Allen So this was the last piece of NVidia I bought...about 400 Workstation ..is not the worth. Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Lee Revell schrieb: On Thu, 2005-08-11 at 09:09 +0200, Gábor Lénárt wrote: I want to buy a new system including motherboard with some Athlon64 CPU. I was told that nforce4 chipset is the right choice. However I'm using *only* Linux Who told you that? Some Windows user? (1.) There is no other way to use a nearly good chipset for AMD64 cpus. Via's chipsets are really buggy not acceptable, so what else ULi/Ali who cares where to buy? Any hardware from them on european market..can't see them until yesterday. It's common knowledge that Nvidia is not Linux friendly. Their business is making hardware so people can play games on Windows. (2.) This is not correct, not everybody play games only on windows or only buy hardware for gaming.. reasons please look at (1.) Anything that their lawyers think might have a 0.0001% chance of interfering with that business model in the slightest bit will not happen. Lee *ironic* Mh so I should take my lawyer and say..hey NVidia cheated me..can't use there hardware completly under Linux but I bought it and can't use it correctly. *ironic off* Sum it up either use Intel and Intel Hardware or die on Linux...*frustrated* Greets Best regards Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Lee Revell schrieb: On Thu, 2005-08-11 at 17:17 +0200, Michael Thonke wrote: *frustrated* Hey I don't like it any more than you do. But Nvidia is an IP company and they act like one. Most of us would probably do the exact same thing in their position, AKA whatever the lawyers tell them ;-) Lee Jepp Lee your are right. Well, the lawyers sometimes like cancer..nobody wants them nobody need them, but they still there. *hard ironic* Couldn't we tie all togehter, to make the world better? To make more hardware loving Linux? And peace on earth *ironic off - taken from Miss Hardware Support election live from Germany* But omitting a costumer in some decisions could break there neck.. If we would have such company we would may do something like that, but hey..saying my Hardware is Linux friendly is much cooler :-) And mh some goverments and schools using AMD and NForce Chipsets..this is a lost market..they are blind? In my old school we had 200 + 100 computers with NForce2..and they wanted to move to Linux OS..but can't..sharing my knowledge stuck at the point of driver support from NVidia for Linux so the problem was on the root (hardware). Now they changed to Intel and what happen no NVidia anymore - isn't the worth would NVidia say right? Greets Best regards Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Roger Heflin schrieb: For high end stuff Serverworks is supposed to have some AMD stuff soon (this is rumor I heard). If there where some pieces for desktop from AMD orignially I would take them..but they don't offer...that's the point...to cry. Like Intel offer ..Intel CPU + Intel Chipset best combination overall ATM. From what Allen said, the implication to me is that something in the current NVIDIA stat NCQ chipset is *not* fully under NVIDIA's control, What the sell hardware they can't support or develop driver for it.. okay that's the point why many windows users complain about Data corruption. Thanks for raising this point. ie they got some piece of technology from someone else and cannot disclose its details, which would be why the could release a clean redesigned one. Roger A bit late or not? What we have done to get this punishment? I love Linux and I won't move from it because of it...loyality :-) -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Jeff Garzik schrieb: Michael Thonke wrote: There is no other way to use a nearly good chipset for AMD64 cpus. Via's chipsets are really buggy not acceptable, so what else ULi/Ali who cares where to buy? What specifically does not work, on VIA+AMD64 combination, under Linux? I have a ASUS A8V Deluxe too, and can't use the AMD X2 processor on it...this is a feature..right? Supposed to run with DualCore but don't post..hm. My Athlon64 with VIA chipset works great. My SATA II devices. Get not regonized from the VIA SATA controller...this bug is known. So I want to use my HDD's I bought ...why should I set my SATA II device to be SATA I. Is also a feature of VIA Chipsets, right? Jeff It's not a bug, hey let's say is a feature. Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Lennart Sorensen schrieb: On Thu, Aug 11, 2005 at 01:20:56PM -0400, Jeff Garzik wrote: What specifically does not work, on VIA+AMD64 combination, under Linux? My Athlon64 with VIA chipset works great. Mine does too. Asus A8V Deluxe. No problems so far. Everything on the board I have tried just works. AMD X2 DualCore? Can't say my A7N8X-E Deluxe has any real issues either. I may only get ac97 audio level out of the nifty DSP, but I hardly use sound on the system anyhow, so I don't mind. forcedeth driver works for networking, sil3112a sata works with WD drives no problem, nvidia ide controller seems to work fine with dvd drives, firewire works, yukon sk98lin works Yes, Marvell, Silicon Image no problem as they provide OpenSource drivers. On a normal setup is nearly everything okay. I hold up a hardware testlab to find b** *features* the specification don't show/hold. Things that can go scary for production usage - that's my job. too, usb is fine. No complaints from me. USB works also great for all chipsets :-) Len Sorensen Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Jeff Garzik schrieb: Michael Thonke wrote: I have a ASUS A8V Deluxe too, and can't use the AMD X2 processor on it...this is a feature..right? Supposed to run with DualCore but don't post..hm. What does ASUS say about this? You can't just plug a new processor into an old motherboard and expect it to work, generally. Hello Jeff, No they don't like AMD x2 DualCore cpus. ASUS is not interesseted in the bugs I found...Silicon Image helped me to get Samsung SATA II drivers working on the Sil3132 chip and gave me a update/firmware. But ASUS ...what should I say? They say no problem encountered by us so far...don't use linux...and thorw off the phone..while you want to talk..*sigh* My SATA II devices. Get not regonized from the VIA SATA controller...this bug is known. So I want to use my HDD's I bought ...why should I set my SATA II device to be SATA I. And nope they don't work, no drive which with SATAII operate without tweak on VIA Southbridges..SATA controller. Hitachi,Samsung,WD I refer to the article of heise.de This article from heise.de is german sorry...but maybe you understand what they wrote http://www.heise.de/newsticker/meldung/62189 Haven't found a Please enable ATA_DEBUG and ATA_VERBOSE_DEBUG, and send me the output. I tried that Jeff, but the base problem is on the low-level.. Like the one I ound with Sil3132. SATA II devices can be used on SATA I controllers just fine, with no need to tweak settings. Jeff Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Lennart Sorensen schrieb: On Thu, Aug 11, 2005 at 07:38:12PM +0200, Michael Thonke wrote: I have a ASUS A8V Deluxe too, and can't use the AMD X2 processor on it...this is a feature..right? Supposed to run with DualCore but don't post..hm. Well according to Asus you can if you run BIOS 1013 or 1014 on the board. Any less and it won't boot. What they say is escapist - far away.. Now I certainly can't try it given I don't have such a CPU. Well, don't go to holiday and spend the money for this genial CPU. My SATA II devices. Get not regonized from the VIA SATA controller...this bug is known. So I want to use my HDD's I bought ...why should I set my SATA II device to be SATA I. So a SATA II drive doesn't work at all? Jep. On VIA chipsets..it would be to flacky to say SATA II drives doesn't work at all. But its like the Smart-Table and what vendors implement and who did the interpretation of specs:-) It's like a fairy tale..the hardware fairy tale. Is also a feature of VIA Chipsets, right? It's not a bug, hey let's say is a feature. Common practice it seems. Wouldn't be the would in there, the world would be boring. Len Sorensen Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Jeff Garzik schrieb: Michael Thonke wrote: Jeff Garzik schrieb: Please enable ATA_DEBUG and ATA_VERBOSE_DEBUG, and send me the output. I tried that Jeff, but the base problem is on the low-level.. There may be a BIOS problem, but there is no problem with the controller using SATA II drives. Can you boot with another drive, and then send the output requested above? Sorry, but I can't provide them, because I changed the VIA chipset based mainboard against a NForce4 Ultra chipset mainboard. But on heise.de they also pointed out that it's VIA's bug. Not the harddrives one, they have some but this not apply on VIA. Samsung act and updated the firmware of their drives for compatibility reasons. And the work-around is to jumper the hdd as SATA I hdd. The problem was, that my system to this time was not bootable with my Samsungs Hd160JJ and VIA VT8237. Nos they fix it with a new Chipset the VT8327R...where we don't need a work-around. http://www.via.com.tw/en/products/chipsets/southbridge/vt8237/ Jeff Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: how do I read CPU temperature in ACPI? (w/ P5WD2 motherboard)
David Madore schrieb: Hi. I apologize for what is surely a stupid question: I understand that ACPI should be able to tell me what my CPU's temperature is (I have a sever overheating problem and I am trying to solve it by underclocking somewhat, but I need to be able to read the temperature to do anything worth while), but no matter what ACPI modules I load, I can't find any hint of a CPU temperature reading anywhere below /proc/acpi (the /proc/acpi/thermal_zone/ directory, for example, remains empty). That's with the "thermal", "processor" and "fan" modules loaded (and a few others; full listing follows signature). I tried to load the asus_acpi module also, since I have an ASUS motherboard (a P5WD2 Premium - precise details are given below signature), but I got a "No such device" error. Does that mean my motherboard is unsupported and I cannot read my CPU temperature at all? (But I thought the whole _point_ of ACPI was that it was an abstraction away from the hardware: so why is there such a thing as "Asus" ACPI?) Or else, what am I doing wrong? Hello David, you will have no luck. I also have this Mainboard in my test rig. 1.) The Super/IO Winbond W83627EHG-A is not supported yet by lm_sensors2 or any driver I know of. 2.) I also can't get acpi temperature on Gigabyte 955X Royal and 925Xe Mobo, Abit 925XE, ASUS P5AD2-E 925XE, P5WD2 955X too. The ASUS P5WD2 also has some **EXECUTABLE CODE*** in ACPI Table that cause some errors here..regarding ACPI stuff *sigh* But on the Gigabyte they use a IT8212F Super IO so you can use lm_sensors2. I hope I could help a bit. Greets -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Jeff Garzik schrieb: Ask NVIDIA. They are the only company that gives me -zero- information on their SATA controllers. Hello again, Jeff, did you found any informations about NForce4 SATA Controller? I found a Product Brief/Specification and a Blockdiagramm. Also found out that the CK804 supports TCQ/NCQ -> snip nForce4 Ultra and nForce4 SLi can support tagged command queuing and native command queuing when used with SATA hard disks that support these features --> As such, there are -zero- plans for NCQ on NVIDIA controllers at this time. Jeff If NVidia followed the SATA-IO spec than should be possible to make them work with NCQ, or do I think wrong of that? Or isn't it possible? /Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Jeff Garzik schrieb: Michael Thonke wrote: Hello Jeff, I would like to ask what the plans/timeplan to implement NCQ support for NVidia NForce4(CK804) SATAII based chipsets? Fact is that is it possible to use NCQ with NForce4 SATAII on Windows system, I wonder why it isn't support by libata? Is there something in your git-tree? Or what are the reasons/problems behind that libata is missing NCQ support for (CK804) SATAII? Ask NVIDIA. They are the only company that gives me -zero- information on their SATA controllers. I thought of that.. *sigh* As such, there are -zero- plans for NCQ on NVIDIA controllers at this time. Could it be possible to make reverse engeneering? I think they should work as the SATA-IO SATAII specification says. Jeff, I will also contact NVidia to ask for specification or information about it. Jeff /Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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/
NCQ support NVidia NForce4 (CK804) SATAII
Hello Jeff, I would like to ask what the plans/timeplan to implement NCQ support for NVidia NForce4(CK804) SATAII based chipsets? Fact is that is it possible to use NCQ with NForce4 SATAII on Windows system, I wonder why it isn't support by libata? Is there something in your git-tree? Or what are the reasons/problems behind that libata is missing NCQ support for (CK804) SATAII? Greets and Best regards -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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/
NCQ support NVidia NForce4 (CK804) SATAII
Hello Jeff, I would like to ask what the plans/timeplan to implement NCQ support for NVidia NForce4(CK804) SATAII based chipsets? Fact is that is it possible to use NCQ with NForce4 SATAII on Windows system, I wonder why it isn't support by libata? Is there something in your git-tree? Or what are the reasons/problems behind that libata is missing NCQ support for (CK804) SATAII? Greets and Best regards -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Jeff Garzik schrieb: Michael Thonke wrote: Hello Jeff, I would like to ask what the plans/timeplan to implement NCQ support for NVidia NForce4(CK804) SATAII based chipsets? Fact is that is it possible to use NCQ with NForce4 SATAII on Windows system, I wonder why it isn't support by libata? Is there something in your git-tree? Or what are the reasons/problems behind that libata is missing NCQ support for (CK804) SATAII? Ask NVIDIA. They are the only company that gives me -zero- information on their SATA controllers. I thought of that.. *sigh* As such, there are -zero- plans for NCQ on NVIDIA controllers at this time. Could it be possible to make reverse engeneering? I think they should work as the SATA-IO SATAII specification says. Jeff, I will also contact NVidia to ask for specification or information about it. Jeff /Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: NCQ support NVidia NForce4 (CK804) SATAII
Jeff Garzik schrieb: Ask NVIDIA. They are the only company that gives me -zero- information on their SATA controllers. Hello again, Jeff, did you found any informations about NForce4 SATA Controller? I found a Product Brief/Specification and a Blockdiagramm. Also found out that the CK804 supports TCQ/NCQ - snip nForce4 Ultra and nForce4 SLi can support tagged command queuing and native command queuing when used with SATA hard disks that support these features -- As such, there are -zero- plans for NCQ on NVIDIA controllers at this time. Jeff If NVidia followed the SATA-IO spec than should be possible to make them work with NCQ, or do I think wrong of that? Or isn't it possible? /Michael -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: how do I read CPU temperature in ACPI? (w/ P5WD2 motherboard)
David Madore schrieb: Hi. I apologize for what is surely a stupid question: I understand that ACPI should be able to tell me what my CPU's temperature is (I have a sever overheating problem and I am trying to solve it by underclocking somewhat, but I need to be able to read the temperature to do anything worth while), but no matter what ACPI modules I load, I can't find any hint of a CPU temperature reading anywhere below /proc/acpi (the /proc/acpi/thermal_zone/ directory, for example, remains empty). That's with the thermal, processor and fan modules loaded (and a few others; full listing follows signature). I tried to load the asus_acpi module also, since I have an ASUS motherboard (a P5WD2 Premium - precise details are given below signature), but I got a No such device error. Does that mean my motherboard is unsupported and I cannot read my CPU temperature at all? (But I thought the whole _point_ of ACPI was that it was an abstraction away from the hardware: so why is there such a thing as Asus ACPI?) Or else, what am I doing wrong? Hello David, you will have no luck. I also have this Mainboard in my test rig. 1.) The Super/IO Winbond W83627EHG-A is not supported yet by lm_sensors2 or any driver I know of. 2.) I also can't get acpi temperature on Gigabyte 955X Royal and 925Xe Mobo, Abit 925XE, ASUS P5AD2-E 925XE, P5WD2 955X too. The ASUS P5WD2 also has some **EXECUTABLE CODE*** in ACPI Table that cause some errors here..regarding ACPI stuff *sigh* But on the Gigabyte they use a IT8212F Super IO so you can use lm_sensors2. I hope I could help a bit. Greets -- Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: [ACPI] Re: 2.6.13-rc3-mm3
Hello Andrew, Andrew Morton wrote: Michael, I'm assuming that a) this problem remains in those -mm kernels which include git-acpi.patch and that b) the problems are not present in 2.6.13-rc5 or 2.6.13-rc6, yes? a.) I don't have any problems in 2.6.13-rc5-git[1-3] and 2.6.13-rc4-mm1 they are working quite fantastic. Good work :-) So I think we have a bug in git-acpi.patch? I reverted them and left them in..no problems with kernels I said above. Again good work :-) If that's all correct then can you please test the next -mm (which will include git-acpi.patch - the most recent -mm did not) and if the bug's still there can you raise a bugzilla.kernel.org entry for it? I would, but the motherboard is dropped from my hardware test approval. Maybe I can get it back to test again if it helps to solve some acpi issues. We seem to have a handful of bug reports against the -mm acpi patch. Well, I noticed that there are a lots of bugs and I'm willing to find search and reproduce them. Thanks. I have to say thanks for the great help/feedback. Greets and Best regards -- _Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: [ACPI] Re: 2.6.13-rc3-mm3
Hello Andrew, Andrew Morton wrote: Michael, I'm assuming that a) this problem remains in those -mm kernels which include git-acpi.patch and that b) the problems are not present in 2.6.13-rc5 or 2.6.13-rc6, yes? a.) I don't have any problems in 2.6.13-rc5-git[1-3] and 2.6.13-rc4-mm1 they are working quite fantastic. Good work :-) So I think we have a bug in git-acpi.patch? I reverted them and left them in..no problems with kernels I said above. Again good work :-) If that's all correct then can you please test the next -mm (which will include git-acpi.patch - the most recent -mm did not) and if the bug's still there can you raise a bugzilla.kernel.org entry for it? I would, but the motherboard is dropped from my hardware test approval. Maybe I can get it back to test again if it helps to solve some acpi issues. We seem to have a handful of bug reports against the -mm acpi patch. Well, I noticed that there are a lots of bugs and I'm willing to find search and reproduce them. Thanks. I have to say thanks for the great help/feedback. Greets and Best regards -- _Michael Thonke IT-Systemintegrator / System- and Softwareanalyist - 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: 2.6.11.3 2.6.11.6 2.6.12 2.6.13rc3 Badness in blk_remove_plug at drivers/block/ll_rw_blk.c:1424
Tobias schrieb: Hi I tried 2.6.11.3 2.6.11.6 2.6.12 2.6.13rc3 In all these Kernels syslog reports me every few minutes log-entries like this Badness in blk_remove_plug at drivers/block/ll_rw_blk.c:1424 [] blk_remove_plug+0x69/0x70 [] __generic_unplug_device+0x1a/0x30 [] __make_request+0x248/0x5a0 [] mempool_alloc+0x33/0x110 [] autoremove_wake_function+0x0/0x60 [] generic_make_request+0x11d/0x210 [] autoremove_wake_function+0x0/0x60 [] find_lock_page+0xaf/0xe0 [] autoremove_wake_function+0x0/0x60 [] mempool_alloc+0x33/0x110 [] _pagebuf_lookup_pages+0x1a2/0x2f0 [xfs] [] submit_bio+0x56/0xf0 [] bio_alloc_bioset+0x130/0x1f0 [] bio_add_page+0x34/0x40 [] _pagebuf_ioapply+0x19f/0x2d0 [xfs] [] default_wake_function+0x0/0x20 [] default_wake_function+0x0/0x20 [] pagebuf_iorequest+0x48/0x1b0 [xfs] [] default_wake_function+0x0/0x20 [] default_wake_function+0x0/0x20 [] xfs_bdstrat_cb+0x38/0x50 [xfs] [] pagebuf_iostart+0x46/0xa0 [xfs] [] xfs_bdstrat_cb+0x0/0x50 [xfs] [] xfs_iflush+0x2b8/0x4e0 [xfs] [] xfs_inode_flush+0x157/0x220 [xfs] [] linvfs_write_inode+0x40/0x80 [xfs] [] __sync_single_inode+0x132/0x270 [] __writeback_single_inode+0x3f/0x180 [] enable_8259A_irq+0x48/0x90 [] __do_IRQ+0x111/0x160 [] sync_sb_inodes+0x1a5/0x300 [] writeback_inodes+0xed/0x130 [] wb_kupdate+0xb6/0x140 [] pdflush+0x0/0x30 [] __pdflush+0xd8/0x200 [] pdflush+0x26/0x30 [] wb_kupdate+0x0/0x140 [] pdflush+0x0/0x30 [] kthread+0xa9/0xf0 [] kthread+0x0/0xf0 [] kernel_thread_helper+0x5/0x10 In bugzilla I found it here to: http://bugzilla.kernel.org/show_bug.cgi?id=4837 First I reportet it here : http://bugzilla.kernel.org/show_bug.cgi?id=4438 This message was sent using IMP, the Internet Messaging Program. ( http://www.horde.org ) - 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/ Hello Tobias, did you read the message at bugzilla? A .config file of the kernel would be appropriate to reproduce the failure you've got. Else it is like looking for a needle in a haystack, for the developers. <http://dict.leo.org/se?lp=ende=/Mn4k.=haystack> <http://dict.leo.org/se?lp=ende=/Mn4k.=haystack> Greets & Best regards -- Michael Thonke IT-Systemintegrator & Systemanalist "Is it a fault to think we're independent individuals? Is it conceivable that the human race is a computer assisted simulation of higher individuals? Is it normal for the human race to distroy the basis of their own existence - the earth?" - 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: 2.6.13-rc4-mm1
Hello Andrew, the ACPI bug or the problems with 2.6.13-rc3-mm[2,3] gone. The system boots now noiseless, except on problem with USB. If my Prolific USB-Serialadapter plugged in on reboot the ehci_hcd driver complains about a Hand-off bug in Bios. -> snip ehci_hcd :00:1d.7: EHCI Host Controller ehci_hcd :00:1d.7: debug port 1 ehci_hcd :00:1d.7: BIOS handoff failed (104, 01010001) ehci_hcd :00:1d.7: continuing after BIOS bug... ehci_hcd :00:1d.7: new USB bus registered, assigned bus number 1 ehci_hcd :00:1d.7: irq 161, io mem 0xd2dffc00 -> snip I wonder about this because all other USB devices working without this message on boot. USB Mouse,Keyboard and USB Storage and all mixed from USB 1.1 and 2. When I rebooted without plugged Prolific Adapter and plug them in the same port the kernel prints this message. ->snip usb 4-1: new full speed USB device using uhci_hcd and address 2 pl2303 4-1:1.0: PL-2303 converter detected usb 4-1: PL-2303 converter now attached to ttyUSB0 -> snip Any Ideas what could be wrong here? Greets Best regards Michael - 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: 2.6.13-rc4-mm1
Felipe Alfaro Solana schrieb: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc4/2.6.13-rc4-mm1/ Why was the KERNEL_VERSION(a,b,c) macro removed from include/linux/version.h? The removal breaks external drivers like NDISWRAPPER or nVidia propietary. - 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/ Hello Felipe, I could not regonize a breakage of NVidia (Version 1.0-7667) propietary drivers. They work just perfect. Greets Michael - 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: 2.6.13-rc4-mm1
Felipe Alfaro Solana schrieb: ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.13-rc4/2.6.13-rc4-mm1/ Why was the KERNEL_VERSION(a,b,c) macro removed from include/linux/version.h? The removal breaks external drivers like NDISWRAPPER or nVidia propietary. - 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/ Hello Felipe, I could not regonize a breakage of NVidia (Version 1.0-7667) propietary drivers. They work just perfect. Greets Michael - 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: 2.6.13-rc4-mm1
Hello Andrew, the ACPI bug or the problems with 2.6.13-rc3-mm[2,3] gone. The system boots now noiseless, except on problem with USB. If my Prolific USB-Serialadapter plugged in on reboot the ehci_hcd driver complains about a Hand-off bug in Bios. - snip ehci_hcd :00:1d.7: EHCI Host Controller ehci_hcd :00:1d.7: debug port 1 ehci_hcd :00:1d.7: BIOS handoff failed (104, 01010001) ehci_hcd :00:1d.7: continuing after BIOS bug... ehci_hcd :00:1d.7: new USB bus registered, assigned bus number 1 ehci_hcd :00:1d.7: irq 161, io mem 0xd2dffc00 - snip I wonder about this because all other USB devices working without this message on boot. USB Mouse,Keyboard and USB Storage and all mixed from USB 1.1 and 2. When I rebooted without plugged Prolific Adapter and plug them in the same port the kernel prints this message. -snip usb 4-1: new full speed USB device using uhci_hcd and address 2 pl2303 4-1:1.0: PL-2303 converter detected usb 4-1: PL-2303 converter now attached to ttyUSB0 - snip Any Ideas what could be wrong here? Greets Best regards Michael - 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: 2.6.11.3 2.6.11.6 2.6.12 2.6.13rc3 Badness in blk_remove_plug at drivers/block/ll_rw_blk.c:1424
Tobias schrieb: Hi I tried 2.6.11.3 2.6.11.6 2.6.12 2.6.13rc3 In all these Kernels syslog reports me every few minutes log-entries like this Badness in blk_remove_plug at drivers/block/ll_rw_blk.c:1424 [c0249559] blk_remove_plug+0x69/0x70 [c024957a] __generic_unplug_device+0x1a/0x30 [c024ac88] __make_request+0x248/0x5a0 [c0140583] mempool_alloc+0x33/0x110 [c0131240] autoremove_wake_function+0x0/0x60 [c024b3ed] generic_make_request+0x11d/0x210 [c0131240] autoremove_wake_function+0x0/0x60 [c013cfaf] find_lock_page+0xaf/0xe0 [c0131240] autoremove_wake_function+0x0/0x60 [c0140583] mempool_alloc+0x33/0x110 [d8f315b2] _pagebuf_lookup_pages+0x1a2/0x2f0 [xfs] [c024b536] submit_bio+0x56/0xf0 [c0163ca0] bio_alloc_bioset+0x130/0x1f0 [c0164244] bio_add_page+0x34/0x40 [d8f325ef] _pagebuf_ioapply+0x19f/0x2d0 [xfs] [c0116cc0] default_wake_function+0x0/0x20 [c0116cc0] default_wake_function+0x0/0x20 [d8f32768] pagebuf_iorequest+0x48/0x1b0 [xfs] [c0116cc0] default_wake_function+0x0/0x20 [c0116cc0] default_wake_function+0x0/0x20 [d8f39268] xfs_bdstrat_cb+0x38/0x50 [xfs] [d8f322b6] pagebuf_iostart+0x46/0xa0 [xfs] [d8f39230] xfs_bdstrat_cb+0x0/0x50 [xfs] [d8f0bbe8] xfs_iflush+0x2b8/0x4e0 [xfs] [d8f2c867] xfs_inode_flush+0x157/0x220 [xfs] [d8f399f0] linvfs_write_inode+0x40/0x80 [xfs] [c0185fa2] __sync_single_inode+0x132/0x270 [c018611f] __writeback_single_inode+0x3f/0x180 [c0108b78] enable_8259A_irq+0x48/0x90 [c013b591] __do_IRQ+0x111/0x160 [c0186405] sync_sb_inodes+0x1a5/0x300 [c018664d] writeback_inodes+0xed/0x130 [c0143806] wb_kupdate+0xb6/0x140 [c0144400] pdflush+0x0/0x30 [c01442d8] __pdflush+0xd8/0x200 [c0144426] pdflush+0x26/0x30 [c0143750] wb_kupdate+0x0/0x140 [c0144400] pdflush+0x0/0x30 [c0130ca9] kthread+0xa9/0xf0 [c0130c00] kthread+0x0/0xf0 [c0101395] kernel_thread_helper+0x5/0x10 In bugzilla I found it here to: http://bugzilla.kernel.org/show_bug.cgi?id=4837 First I reportet it here : http://bugzilla.kernel.org/show_bug.cgi?id=4438 This message was sent using IMP, the Internet Messaging Program. ( http://www.horde.org ) - 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/ Hello Tobias, did you read the message at bugzilla? A .config file of the kernel would be appropriate to reproduce the failure you've got. Else it is like looking for a needle in a haystack, for the developers. http://dict.leo.org/se?lp=endep=/Mn4k.search=haystack http://dict.leo.org/se?lp=endep=/Mn4k.search=haystack Greets Best regards -- Michael Thonke IT-Systemintegrator Systemanalist Is it a fault to think we're independent individuals? Is it conceivable that the human race is a computer assisted simulation of higher individuals? Is it normal for the human race to distroy the basis of their own existence - the earth? - 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: PROBLEM: "drive appears confused" and "irq 18: nobody cared!"
Alexander Fieroch schrieb:
Andrew Morton wrote:
> Is 2.6.13-rc4 running OK? If not, please cc linux-kernel on the
reply and
> re-summarise the problem, thanks.
Same problems as before occur in kernel 2.6.13rc4, too.
I've attached the syslog with kernel parameters "acpi=debug pci=routeirq
apic=debug".
Regards,
Alexander
CPU0 CPU1
0: 56856 0IO-APIC-edge timer
1:147 0IO-APIC-edge i8042
7: 0 0IO-APIC-edge parport0
8: 0 0IO-APIC-edge rtc
9: 0 0 IO-APIC-level acpi
10: 0 0IO-APIC-edge MPU401 UART
169:497 0 IO-APIC-level skge, uhci_hcd:usb5, HDA Intel
177: 0 0 IO-APIC-level Ensoniq AudioPCI
185:274 0 IO-APIC-level ide2, ide3, ehci_hcd:usb1,
uhci_hcd:usb2
193: 3920 0 IO-APIC-level libata, uhci_hcd:usb3
201: 90 0 IO-APIC-level ide0, uhci_hcd:usb4
209: 5 0 IO-APIC-level bttv0, ohci1394
NMI: 52 1
LOC: 55103 55092
ERR: 1
MIS: 0
Jul 29 12:42:36 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:36 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:36 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:36 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:36 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: irq 201: nobody cared (try booting with the
"irqpoll" option)
Jul 29 12:42:37 orclex kernel:
Jul 29 12:42:37 orclex kernel: Call Trace: {__report_bad_irq+48} {note_interrupt+144}
Jul 29 12:42:37 orclex kernel: {__do_IRQ+237}
{do_IRQ+67}
Jul 29 12:42:37 orclex kernel: {ret_from_intr+0}
{find_vma+22}
Jul 29 12:42:37 orclex kernel: {do_page_fault+409}
{do_wait+830}
Jul 29 12:42:37 orclex kernel: {default_wake_function+0}
{error_exit+0}
Jul 29 12:42:37 orclex kernel:
Jul 29 12:42:37 orclex kernel: handlers:
Jul 29 12:42:37 orclex kernel: [] (ide_intr+0x0/0x17a)
Jul 29 12:42:37 orclex kernel: [] (usb_hcd_irq+0x0/0x68)
Jul 29 12:42:37 orclex kernel: Disabling IRQ #201
Jul 29 12:42:37 orclex kernel: scsi: unknown opcode 0x85
Jul 29 12:42:37 orclex lpd[4513]: restarted
Jul 29 12:42:38 orclex nmbd[4523]: [2005/07/29 12:42:38, 0, pid=4523]
nmbd/asyncdns.c:start_async_dns(149)
Jul 29 12:42:38 orclex nmbd[4523]: started asyncdns process 4524
Jul 29 12:42:38 orclex smartd[4530]: smartd version 5.32 Copyright (C) 2002-4
Bruce Allen
Jul 29 12:42:38 orclex smartd[4530]: Home page is
http://smartmontools.sourceforge.net/
Jul 29 12:42:38 orclex smartd[4530]: Opened configuration file /etc/smartd.conf
Jul 29 12:42:38 orclex smartd[4530]: Drive: DEVICESCAN, implied '-a' Directive
on line 23 of file /etc/smartd.conf
Jul 29 12:42:38 orclex smartd[4530]: Configuration file /etc/smartd.conf was
parsed, found DEVICESCAN, scanning devices
Jul 29 12:42:38 orclex smartd[4530]: Device: /dev/hda, opened
Jul 29 12:42:47 orclex kernel: hda: lost interrupt
Jul 29 12:42:47 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:47 orclex smartd[4530]: Device: /dev/hda, found in smartd database.
Jul 29 12:42:48 orclex hddtemp[4508]: /dev/hda: IC35L060AVV207-0: 36 C
Jul 29 12:42:48 orclex kernel: irq 201: nobody cared (try booting with the
"irqpoll" option)
Jul 29 12:42:48 orclex kernel:
Jul 29 12:42:48 orclex kernel: Call Trace: {__report_bad_irq+48} {note_interrupt+144}
Jul 29 12:42:48 orclex kernel: {__do_IRQ+237}
{do_IRQ+67}
Jul 29 12:42:48 orclex kernel: {ret_from_intr+0}
{system_call+126}
Jul 29 12:42:48 orclex kernel:
Jul 29 12:42:48 orclex kernel: handlers:
Jul 29 12:42:48 orclex kernel: [] (ide_intr+0x0/0x17a)
Jul 29
Re: [ACPI] Re: 2.6.13-rc3-mm3
Moore, Robert schrieb: +ACPI-0287: *** Error: Region SystemMemory(0) has no handler +ACPI-0127: *** Error: acpi_load_tables: Could not load namespace: AE_NOT_EXIST +ACPI-0136: *** Error: acpi_load_tables: Could not load tables: This looks like a nasty case where some executable code in the table is attempting to access a SystemMemory operation region before any OpRegion handlers are initialized. We certainly want to see the output of acpidump to attempt to diagnose and/or reproduce the problem. Bob Sorry for double post. With this mail I hand over the acpidump output with the pmtools Andrew pointed me to. And a dmesg output with CONFIG_KALLSYMS=y. I attached them in bz2 format, because of the length. I hope we find the problem. Best regards Michael acpidump.2613rc3mm3.bz2 Description: application/bzip dmesg_ksyms.hda-intel.bz2 Description: application/bzip
Re: 2.6.13-rc3-mm3
Andrew Morton schrieb: Michael Thonke <[EMAIL PROTECTED]> wrote: Andrew Morton schrieb: Michael Thonke <[EMAIL PROTECTED]> wrote: here again I have two problems. With 2.6.13-rc3-mm3 I have problems using my SATA drives on Intel ICH6. The kernel can't route there IRQs or can't discover them. the option irqpoll got them to work now. The problem is new because 2.6.13-rc3[-mm1,mm2] work without any problems. OK. Please generate the full dmesg output for -mm2 and for -mm3 and run `diff -u dmesg.mm2 dmesg.mm3' and send it? And keep those files because we may end up needing to add them to an acpi bugzilla entry ;) Well I did a little mistake..it only worked correctly up to 2.6.13-rc3-mm1 but this dmesg output I have. Well as I save mm[2,3] are unable to setup the correct IRQs for the devices..and please note that 2.6.13-rc3-mm3 only booted with irqpoll so its in the dmesg output "dmesg.mm3" Normaly the IRQ routed to something about 1xx now they are 1-21?! Caused by irqpoll? Are these problems only present in -mm kernels? Does 2.6.13-rc4 work OK? I'm sorry to say that, Yes. I finially compiled a fresh 2.6.13-rc4-git1 kernel with ck-patch and Gregh-kh patches. With this kernel non of the problems I had with mm-kernel are present. Here is everthing just perfect..now I attached a dmesg output for review :-) The Oops on probing snd-hda-intel gone. It works now ... Mozart rocks :-) I look at the CVS tree of Alsa later. I finialy converted my reiser4 root to reiser 3.6. Where I can get acpidumb or what it is called? Odd trace. Do you have CONFIG_KALLSYMS enabled? If not, please turn it on. Okay, i will do so ... what else we need to back that out. Mh I tried but my system freezes on boot then. And screen leaves blank. Oh geeze. Like oh my god? ;-) @@ -53,10 +23,18 @@ Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. +ACPI-0287: *** Error: Region SystemMemory(0) has no handler +ACPI-0127: *** Error: acpi_load_tables: Could not load namespace: AE_NOT_EXIST +ACPI-0136: *** Error: acpi_load_tables: Could not load tables: AE_NOT_EXIST +ACPI: Unable to load the System Description Tables ENABLING IO-APIC IRQs -..TIMER: vector=0x31 pin1=2 pin2=0 +..TIMER: vector=0x31 pin1=2 pin2=-1 The pin2=-1 is wrong I think, right? NET: Registered protocol family 16 PCI: Using configuration type 1 +ACPI: Subsystem revision 20050708 +ACPI: Interpreter disabled. Well it looks like ACPI committed suicide, so there's probably not much point looking at the other things until that gets addressed. Would you have time to raise a kernel bugzilla entry for this? Raise it against the ACPI AML interpreter, version 20050708 and mention the above failure. The output of acpidump (from ftp://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/pmtools-20050727.tar.gz) will probably be asked for. Thanks. Sorry for my different mail accounts, gmail have some problems. Let me say, Thanks again for the help Andrew and all others. IO-APIC IRQs ..TIMER: vector=0x31 pin1=2 pin2=-1 NET: Registered protocol family 16 ACPI: bus type pci registered PCI: Using configuration type 1 ACPI: Subsystem revision 20050408 ACPI-0362: *** Error: Looking up [CHAF] in namespace, AE_NOT_FOUND search_node b1994240 start_node b1994240 return_node ACPI-0362: *** Error: Looking up [OC06] in namespace, AE_NOT_FOUND search_node b1994f60 start_node b1994f60 return_node ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (:00) PCI: Probing PCI hardware (bus 00) ACPI: Assume root bridge [\_SB_.PCI0] segment is 0 PCI: Ignoring BAR0-3 of IDE controller :00:1f.1 Boot video device is :04:00.0 PCI: Transparent bridge - :00:1e.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P3._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11 12 14 15) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 14 devices SCSI subsystem initialized usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: Using ACPI for IRQ routing PC
Re: 2.6.13-rc3-mm3
Andrew Morton schrieb: Michael Thonke [EMAIL PROTECTED] wrote: Andrew Morton schrieb: Michael Thonke [EMAIL PROTECTED] wrote: here again I have two problems. With 2.6.13-rc3-mm3 I have problems using my SATA drives on Intel ICH6. The kernel can't route there IRQs or can't discover them. the option irqpoll got them to work now. The problem is new because 2.6.13-rc3[-mm1,mm2] work without any problems. OK. Please generate the full dmesg output for -mm2 and for -mm3 and run `diff -u dmesg.mm2 dmesg.mm3' and send it? And keep those files because we may end up needing to add them to an acpi bugzilla entry ;) Well I did a little mistake..it only worked correctly up to 2.6.13-rc3-mm1 but this dmesg output I have. Well as I save mm[2,3] are unable to setup the correct IRQs for the devices..and please note that 2.6.13-rc3-mm3 only booted with irqpoll so its in the dmesg output dmesg.mm3 Normaly the IRQ routed to something about 1xx now they are 1-21?! Caused by irqpoll? Are these problems only present in -mm kernels? Does 2.6.13-rc4 work OK? I'm sorry to say that, Yes. I finially compiled a fresh 2.6.13-rc4-git1 kernel with ck-patch and Gregh-kh patches. With this kernel non of the problems I had with mm-kernel are present. Here is everthing just perfect..now I attached a dmesg output for review :-) The Oops on probing snd-hda-intel gone. It works now ... Mozart rocks :-) I look at the CVS tree of Alsa later. I finialy converted my reiser4 root to reiser 3.6. Where I can get acpidumb or what it is called? Odd trace. Do you have CONFIG_KALLSYMS enabled? If not, please turn it on. Okay, i will do so ... what else we need to back that out. Mh I tried but my system freezes on boot then. And screen leaves blank. Oh geeze. Like oh my god? ;-) @@ -53,10 +23,18 @@ Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. +ACPI-0287: *** Error: Region SystemMemory(0) has no handler +ACPI-0127: *** Error: acpi_load_tables: Could not load namespace: AE_NOT_EXIST +ACPI-0136: *** Error: acpi_load_tables: Could not load tables: AE_NOT_EXIST +ACPI: Unable to load the System Description Tables ENABLING IO-APIC IRQs -..TIMER: vector=0x31 pin1=2 pin2=0 +..TIMER: vector=0x31 pin1=2 pin2=-1 The pin2=-1 is wrong I think, right? NET: Registered protocol family 16 PCI: Using configuration type 1 +ACPI: Subsystem revision 20050708 +ACPI: Interpreter disabled. Well it looks like ACPI committed suicide, so there's probably not much point looking at the other things until that gets addressed. Would you have time to raise a kernel bugzilla entry for this? Raise it against the ACPI AML interpreter, version 20050708 and mention the above failure. The output of acpidump (from ftp://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/pmtools-20050727.tar.gz) will probably be asked for. Thanks. Sorry for my different mail accounts, gmail have some problems. Let me say, Thanks again for the help Andrew and all others. IO-APIC IRQs ..TIMER: vector=0x31 pin1=2 pin2=-1 NET: Registered protocol family 16 ACPI: bus type pci registered PCI: Using configuration type 1 ACPI: Subsystem revision 20050408 ACPI-0362: *** Error: Looking up [CHAF] in namespace, AE_NOT_FOUND search_node b1994240 start_node b1994240 return_node ACPI-0362: *** Error: Looking up [OC06] in namespace, AE_NOT_FOUND search_node b1994f60 start_node b1994f60 return_node ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (:00) PCI: Probing PCI hardware (bus 00) ACPI: Assume root bridge [\_SB_.PCI0] segment is 0 PCI: Ignoring BAR0-3 of IDE controller :00:1f.1 Boot video device is :04:00.0 PCI: Transparent bridge - :00:1e.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P3._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11 12 14 15) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init pnp: PnP ACPI: found 14 devices SCSI subsystem initialized usbcore: registered new driver usbfs usbcore: registered new driver hub PCI: Using ACPI for IRQ routing PCI: If a device doesn't work, try
Re: [ACPI] Re: 2.6.13-rc3-mm3
Moore, Robert schrieb: +ACPI-0287: *** Error: Region SystemMemory(0) has no handler +ACPI-0127: *** Error: acpi_load_tables: Could not load namespace: AE_NOT_EXIST +ACPI-0136: *** Error: acpi_load_tables: Could not load tables: This looks like a nasty case where some executable code in the table is attempting to access a SystemMemory operation region before any OpRegion handlers are initialized. We certainly want to see the output of acpidump to attempt to diagnose and/or reproduce the problem. Bob Sorry for double post. With this mail I hand over the acpidump output with the pmtools Andrew pointed me to. And a dmesg output with CONFIG_KALLSYMS=y. I attached them in bz2 format, because of the length. I hope we find the problem. Best regards Michael acpidump.2613rc3mm3.bz2 Description: application/bzip dmesg_ksyms.hda-intel.bz2 Description: application/bzip
Re: PROBLEM: drive appears confused and irq 18: nobody cared!
Alexander Fieroch schrieb:
Andrew Morton wrote:
Is 2.6.13-rc4 running OK? If not, please cc linux-kernel on the
reply and
re-summarise the problem, thanks.
Same problems as before occur in kernel 2.6.13rc4, too.
I've attached the syslog with kernel parameters acpi=debug pci=routeirq
apic=debug.
Regards,
Alexander
CPU0 CPU1
0: 56856 0IO-APIC-edge timer
1:147 0IO-APIC-edge i8042
7: 0 0IO-APIC-edge parport0
8: 0 0IO-APIC-edge rtc
9: 0 0 IO-APIC-level acpi
10: 0 0IO-APIC-edge MPU401 UART
169:497 0 IO-APIC-level skge, uhci_hcd:usb5, HDA Intel
177: 0 0 IO-APIC-level Ensoniq AudioPCI
185:274 0 IO-APIC-level ide2, ide3, ehci_hcd:usb1,
uhci_hcd:usb2
193: 3920 0 IO-APIC-level libata, uhci_hcd:usb3
201: 90 0 IO-APIC-level ide0, uhci_hcd:usb4
209: 5 0 IO-APIC-level bttv0, ohci1394
NMI: 52 1
LOC: 55103 55092
ERR: 1
MIS: 0
Jul 29 12:42:36 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:36 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:36 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:36 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:36 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:37 orclex kernel: irq 201: nobody cared (try booting with the
irqpoll option)
Jul 29 12:42:37 orclex kernel:
Jul 29 12:42:37 orclex kernel: Call Trace: IRQ 80156e67{__report_bad_irq+48} 80156f60{note_interrupt+144}
Jul 29 12:42:37 orclex kernel: 8015678b{__do_IRQ+237}
80110715{do_IRQ+67}
Jul 29 12:42:37 orclex kernel: 8010e051{ret_from_intr+0} EOI
8016ac7f{find_vma+22}
Jul 29 12:42:37 orclex kernel: 8011ecfe{do_page_fault+409}
801389c6{do_wait+830}
Jul 29 12:42:37 orclex kernel: 801300a5{default_wake_function+0}
8010e4dd{error_exit+0}
Jul 29 12:42:37 orclex kernel:
Jul 29 12:42:37 orclex kernel: handlers:
Jul 29 12:42:37 orclex kernel: [8031c835] (ide_intr+0x0/0x17a)
Jul 29 12:42:37 orclex kernel: [803615f5] (usb_hcd_irq+0x0/0x68)
Jul 29 12:42:37 orclex kernel: Disabling IRQ #201
Jul 29 12:42:37 orclex kernel: scsi: unknown opcode 0x85
Jul 29 12:42:37 orclex lpd[4513]: restarted
Jul 29 12:42:38 orclex nmbd[4523]: [2005/07/29 12:42:38, 0, pid=4523]
nmbd/asyncdns.c:start_async_dns(149)
Jul 29 12:42:38 orclex nmbd[4523]: started asyncdns process 4524
Jul 29 12:42:38 orclex smartd[4530]: smartd version 5.32 Copyright (C) 2002-4
Bruce Allen
Jul 29 12:42:38 orclex smartd[4530]: Home page is
http://smartmontools.sourceforge.net/
Jul 29 12:42:38 orclex smartd[4530]: Opened configuration file /etc/smartd.conf
Jul 29 12:42:38 orclex smartd[4530]: Drive: DEVICESCAN, implied '-a' Directive
on line 23 of file /etc/smartd.conf
Jul 29 12:42:38 orclex smartd[4530]: Configuration file /etc/smartd.conf was
parsed, found DEVICESCAN, scanning devices
Jul 29 12:42:38 orclex smartd[4530]: Device: /dev/hda, opened
Jul 29 12:42:47 orclex kernel: hda: lost interrupt
Jul 29 12:42:47 orclex kernel: hdb: cdrom_pc_intr: The drive appears confused
(ireason = 0x01)
Jul 29 12:42:47 orclex smartd[4530]: Device: /dev/hda, found in smartd database.
Jul 29 12:42:48 orclex hddtemp[4508]: /dev/hda: IC35L060AVV207-0: 36 C
Jul 29 12:42:48 orclex kernel: irq 201: nobody cared (try booting with the
irqpoll option)
Jul 29 12:42:48 orclex kernel:
Jul 29 12:42:48 orclex kernel: Call Trace: IRQ 80156e67{__report_bad_irq+48} 80156f60{note_interrupt+144}
Jul 29 12:42:48 orclex kernel:
Re: 2.6.13-rc3-mm3
Hello Andrew, here again I have two problems. With 2.6.13-rc3-mm3 I have problems using my SATA drives on Intel ICH6. The kernel can't route there IRQs or can't discover them. the option irqpoll got them to work now. The problem is new because 2.6.13-rc3[-mm1,mm2] work without any problems. The SATA drives are Samsung HD160JJ SATAII. The mainboard I use is a ASUS P4GPL-X. Second one is about Intel HD-Codec (snd-hda-intel) on modprobe when loading the module it gives me ---> snip hda_codec: Unknown model for ALC880, trying auto-probe from BIOS... Unable to handle kernel NULL pointer dereference at virtual address printing eip: f88713f4 *pde = Oops: 0002 [#1] PREEMPT last sysfs file: Modules linked in: snd_hda_intel snd_hda_codec nvidia CPU:0 EIP:0060:[]Tainted: P VLI EFLAGS: 00010293 (2.6.13-rc3-mm3pm) eax: fffe ebx: f3b33548 ecx: edx: esi: f3b33400 edi: ebp: 0006 esp: f0371ddc ds: 007b es: 007b ss: 0068 Process modprobe (pid: 7398, threadinfo=f037 task=f4183560) Stack: f3b33400 f3b33548 f0f1d000 f8871933 f3b33400 f0f1d000 f8871bbd f8875478 f88748f6 0001 f886d77e 0f00 0005 f0f1d000 f54d04c0 f886d984 0f00 0002 Call Trace: [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] [] Code: 31 c0 53 83 ec 10 89 d3 89 e7 f3 ab 8b 12 31 ff 83 fa 00 7e 45 89 f6 0f b7 44 7b 04 8d 48 ec 66 83 f9 03 77 13 8b 56 3c 83 e8 16 <66> 89 04 7a 8b 13 c7 04 8c 01 00 00 00 47 39 fa 7f da 31 ff 83 --> snip I also attached the kernel-config and the lspci -vv output. Thanks again for the patience and the help. Best regards Michael - 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: 2.6.13-rc3-mm3
Nick Sillik schrieb: Andrew Morton wrote: Michael Thonke <[EMAIL PROTECTED]> wrote: Hello Andrew, I have some questions :-) Reiser4: why there are undefined functions implemented that currently not in use? This messages appeared first time in 2.6.13-rc3-mm2. Any why it complains even CONFIG_REISER4_DEBUG is not set? That's due to the code using `#if CONFIG_xx' instead of `#ifdef'. I previously posted a patch that got rid of one of these, find it attached again below. Signed-off-by: Nick Sillik <[EMAIL PROTECTED]> diff -urN a/fs/reiser4/plugin/node/node40.h b/fs/reiser4/plugin/node/node40.h --- a/fs/reiser4/plugin/node/node40.h 2005-07-27 18:14:04.0 -0400 +++ b/fs/reiser4/plugin/node/node40.h 2005-07-27 18:14:53.0 -0400 @@ -80,7 +80,7 @@ int check_node40(const znode * node, __u32 flags, const char **error); int parse_node40(znode * node); int init_node40(znode * node); -#if GUESS_EXISTS +#ifdef GUESS_EXISTS int guess_node40(const znode * node); #endif void change_item_size_node40(coord_t * coord, int by); Thanks, this fixed the complains on compiling kernel :-) - 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: 2.6.13-rc3-mm3
Hello Andrew, I have some questions :-) Reiser4: why there are undefined functions implemented that currently not in use? This messages appeared first time in 2.6.13-rc3-mm2. Any why it complains even CONFIG_REISER4_DEBUG is not set? Please have a look at the -->snip SCSI: CONFIG_SCSI_QLA2XXX=y ? I haven't choose that one..I never did..and where is the config located? In the place where it is..is no option marked. Thanks for help, Greets Michael --> snip fs/reiser4/plugin/item/static_stat.c:1158:5: warning: "REISER4_DEBUG_OUTPUT" is not defined fs/reiser4/plugin/item/static_stat.c:1176:5: warning: "REISER4_DEBUG_OUTPUT" is not defined fs/reiser4/plugin/item/static_stat.c:1194:5: warning: "REISER4_DEBUG_OUTPUT" is not defined fs/reiser4/plugin/item/static_stat.c:1213:5: warning: "REISER4_DEBUG_OUTPUT" is not defined CC fs/reiser4/plugin/item/sde.o In file included from fs/reiser4/plugin/item/../plugin.h:26, from fs/reiser4/plugin/item/sde.c:11: fs/reiser4/plugin/item/../node/node40.h:83:5: warning: "GUESS_EXISTS" is not defined fs/reiser4/plugin/item/sde.c:21:5: warning: "REISER4_DEBUG_OUTPUT" is not defined CC fs/reiser4/plugin/item/cde.o In file included from fs/reiser4/plugin/item/../plugin.h:26, from fs/reiser4/plugin/item/cde.c:65: fs/reiser4/plugin/item/../node/node40.h:83:5: warning: "GUESS_EXISTS" is not def - 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: 2.6.13-rc3-mm3
Hello Andrew, I have some questions :-) Reiser4: why there are undefined functions implemented that currently not in use? This messages appeared first time in 2.6.13-rc3-mm2. Any why it complains even CONFIG_REISER4_DEBUG is not set? Please have a look at the --snip SCSI: CONFIG_SCSI_QLA2XXX=y ? I haven't choose that one..I never did..and where is the config located? In the place where it is..is no option marked. Thanks for help, Greets Michael -- snip fs/reiser4/plugin/item/static_stat.c:1158:5: warning: REISER4_DEBUG_OUTPUT is not defined fs/reiser4/plugin/item/static_stat.c:1176:5: warning: REISER4_DEBUG_OUTPUT is not defined fs/reiser4/plugin/item/static_stat.c:1194:5: warning: REISER4_DEBUG_OUTPUT is not defined fs/reiser4/plugin/item/static_stat.c:1213:5: warning: REISER4_DEBUG_OUTPUT is not defined CC fs/reiser4/plugin/item/sde.o In file included from fs/reiser4/plugin/item/../plugin.h:26, from fs/reiser4/plugin/item/sde.c:11: fs/reiser4/plugin/item/../node/node40.h:83:5: warning: GUESS_EXISTS is not defined fs/reiser4/plugin/item/sde.c:21:5: warning: REISER4_DEBUG_OUTPUT is not defined CC fs/reiser4/plugin/item/cde.o In file included from fs/reiser4/plugin/item/../plugin.h:26, from fs/reiser4/plugin/item/cde.c:65: fs/reiser4/plugin/item/../node/node40.h:83:5: warning: GUESS_EXISTS is not def - 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: 2.6.13-rc3-mm3
Nick Sillik schrieb: Andrew Morton wrote: Michael Thonke [EMAIL PROTECTED] wrote: Hello Andrew, I have some questions :-) Reiser4: why there are undefined functions implemented that currently not in use? This messages appeared first time in 2.6.13-rc3-mm2. Any why it complains even CONFIG_REISER4_DEBUG is not set? That's due to the code using `#if CONFIG_xx' instead of `#ifdef'. I previously posted a patch that got rid of one of these, find it attached again below. Signed-off-by: Nick Sillik [EMAIL PROTECTED] diff -urN a/fs/reiser4/plugin/node/node40.h b/fs/reiser4/plugin/node/node40.h --- a/fs/reiser4/plugin/node/node40.h 2005-07-27 18:14:04.0 -0400 +++ b/fs/reiser4/plugin/node/node40.h 2005-07-27 18:14:53.0 -0400 @@ -80,7 +80,7 @@ int check_node40(const znode * node, __u32 flags, const char **error); int parse_node40(znode * node); int init_node40(znode * node); -#if GUESS_EXISTS +#ifdef GUESS_EXISTS int guess_node40(const znode * node); #endif void change_item_size_node40(coord_t * coord, int by); Thanks, this fixed the complains on compiling kernel :-) - 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: 2.6.13-rc3-mm3
Hello Andrew, here again I have two problems. With 2.6.13-rc3-mm3 I have problems using my SATA drives on Intel ICH6. The kernel can't route there IRQs or can't discover them. the option irqpoll got them to work now. The problem is new because 2.6.13-rc3[-mm1,mm2] work without any problems. The SATA drives are Samsung HD160JJ SATAII. The mainboard I use is a ASUS P4GPL-X. Second one is about Intel HD-Codec (snd-hda-intel) on modprobe when loading the module it gives me --- snip hda_codec: Unknown model for ALC880, trying auto-probe from BIOS... Unable to handle kernel NULL pointer dereference at virtual address printing eip: f88713f4 *pde = Oops: 0002 [#1] PREEMPT last sysfs file: Modules linked in: snd_hda_intel snd_hda_codec nvidia CPU:0 EIP:0060:[f88713f4]Tainted: P VLI EFLAGS: 00010293 (2.6.13-rc3-mm3pm) eax: fffe ebx: f3b33548 ecx: edx: esi: f3b33400 edi: ebp: 0006 esp: f0371ddc ds: 007b es: 007b ss: 0068 Process modprobe (pid: 7398, threadinfo=f037 task=f4183560) Stack: f3b33400 f3b33548 f0f1d000 f8871933 f3b33400 f0f1d000 f8871bbd f8875478 f88748f6 0001 f886d77e 0f00 0005 f0f1d000 f54d04c0 f886d984 0f00 0002 Call Trace: [f8871933] [f8871bbd] [f886d77e] [f886d984] [f886d592] [c025b87e] [f8f5c871] [f8f5c100] [f8f5c220] [f8f5d533] [c026866a] [c02686be] [c02686f6] [c02bf763] [c02bf899] [c02bee1a] [c02bf8b6] [c02bf860] [c02bf30c] [c02bfc85] [c0268958] [c013b5c9] [c0102fcb] Code: 31 c0 53 83 ec 10 89 d3 89 e7 f3 ab 8b 12 31 ff 83 fa 00 7e 45 89 f6 0f b7 44 7b 04 8d 48 ec 66 83 f9 03 77 13 8b 56 3c 83 e8 16 66 89 04 7a 8b 13 c7 04 8c 01 00 00 00 47 39 fa 7f da 31 ff 83 -- snip I also attached the kernel-config and the lspci -vv output. Thanks again for the patience and the help. Best regards Michael - 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/
Support for Silicon Image 3132 SATA II Controller
Hello, I've got a new Silicon Image 3132 SATA II host-controller, this one is designed along the SATA (II) specification - (Hot-Plug,NCQ,3GB/s transfer). This controller is linked to the pci-express bus. I guess it operate like the 3124 controller with some addition :-) On the Silicon Image website I found some papers for this controller and his architecture. It can be found here http://www.siliconimage.com/products/product.aspx?id=32=1 I can provide a pci-ids for some specific boards if needed...I found this controller on some new motherboards Gigabyte's 955X Royal, ABIT AW8,ECS PF88 Extreme, TUL,Foxconn and maybe others coming. Is it possible to implement this controller to libata: sata_sil driver? I also would spend some time to test the driver. Thanks for help and assistence Greets -- Mit freundlichen Grüßen Michael Thonke Best regards Michael Thonke - 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/
Support for Silicon Image 3132 SATA II Controller
Hello, I've got a new Silicon Image 3132 SATA II host-controller, this one is designed along the SATA (II) specification - (Hot-Plug,NCQ,3GB/s transfer). This controller is linked to the pci-express bus. I guess it operate like the 3124 controller with some addition :-) On the Silicon Image website I found some papers for this controller and his architecture. It can be found here http://www.siliconimage.com/products/product.aspx?id=32ptid=1 I can provide a pci-ids for some specific boards if needed...I found this controller on some new motherboards Gigabyte's 955X Royal, ABIT AW8,ECS PF88 Extreme, TUL,Foxconn and maybe others coming. Is it possible to implement this controller to libata: sata_sil driver? I also would spend some time to test the driver. Thanks for help and assistence Greets -- Mit freundlichen Grüßen Michael Thonke Best regards Michael Thonke - 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: 2.6.12-rc2-mm2
Hello Andrew, along the 2.6.12-rcX-mmX PCI-Express is not usable at all with mm-patchsets. I posted some days ago the problem taht the IRQs get not regonized by the kernel also with pci=routeirq nothing helped. The problem still the same and some new problems now with 2.6.12-rc2-mm2 in addition. This computer has an Intel Pentium 4 630 with HT,EIST and EMT64 enabled. In 2.6.12-rc2 everything works perfect. So I post my dmesg output maybe you can see some interesting things there. I hope you'll find the issue or bug..whatever hope that its possible to sort the problems out. Thanks in Advanced Now I post the 2.6.12-rc2-mm2 and after that the 2.6.12-rc2 vanilla kernel output 2.6.12-rc2-mm2 output: Bootdata ok (command line is root=/dev/md1 vga=794 quiet) Linux version 2.6.12-rc2-mm2-md1 ([EMAIL PROTECTED]) (gcc-Version 3.4.3 20041125 (Gentoo Linux 3.4.3-r1, ssp-3.4.3-0, pie-8.7.7)) #2 SMP PREEMPT Fri Apr 8 13:35:42 CEST 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000e4000 - 0010 (reserved) BIOS-e820: 0010 - 3ffb (usable) BIOS-e820: 3ffb - 3ffbe000 (ACPI data) BIOS-e820: 3ffbe000 - 3fff (ACPI NVS) BIOS-e820: 3fff - 4000 (reserved) BIOS-e820: ffb0 - 0001 (reserved) ACPI: RSDP (v002 ACPIAM) @ 0x000fafa0 ACPI: XSDT (v001 A M I OEMXSDT 0x02000503 MSFT 0x0097) @ 0x3ffb0100 ACPI: FADT (v003 A M I OEMFACP 0x02000503 MSFT 0x0097) @ 0x3ffb0290 ACPI: MADT (v001 A M I OEMAPIC 0x02000503 MSFT 0x0097) @ 0x3ffb0390 ACPI: OEMB (v001 A M I AMI_OEM 0x02000503 MSFT 0x0097) @ 0x3ffbe040 ACPI: MCFG (v001 A M I OEMMCFG 0x02000503 MSFT 0x0097) @ 0x3ffb6c40 ACPI: DSDT (v001 A0144 A0144000 0x INTL 0x02002026) @ 0x On node 0 totalpages: 262064 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 257968 pages, LIFO batch:16 HighMem zone: 0 pages, LIFO batch:1 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 15:4 APIC version 16 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Processor #1 15:4 APIC version 16 ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Setting APIC routing to flat Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 4000 (gap: 4000:bfb0) Built 1 zonelists Initializing CPU#0 Kernel command line: root=/dev/md1 vga=794 quiet console=tty0 PID hash table entries: 4096 (order: 12, 131072 bytes) time.c: Using 1.193182 MHz PIT timer. time.c: Detected 3527.408 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) Memory: 1024964k/1048256k available (3240k kernel code, 22664k reserved, 1218k data, 212k init) Calibrating delay loop... 6963.20 BogoMIPS (lpj=3481600) Security Framework v1.0.0 initialized Capability LSM initialized Mount-cache hash table entries: 256 CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K using mwait in idle threads. CPU: Physical Processor ID: 0 CPU0: Thermal monitoring enabled (TM1) Using IO APIC NMI watchdog activating NMI Watchdog ... done. Using local APIC timer interrupts. Detected 13.778 MHz APIC timer. Booting processor 1/1 rip 6000 rsp 81003ff35f58 Initializing CPU#1 Calibrating delay loop... 7045.12 BogoMIPS (lpj=3522560) CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K CPU: Physical Processor ID: 0 CPU1: Thermal monitoring enabled (TM1) Intel(R) Pentium(R) 4 CPU 3.20GHz stepping 03 Synced TSC of CPU 1 difference 107374180328 APIC error on CPU1: 00(40) Brought up 2 CPUs time.c: Using PIT/TSC based timekeeping. CPU0 attaching sched-domain: domain 0: span 3 groups: 1 2 CPU1 attaching sched-domain: domain 0: span 3 groups: 2 1 NET: Registered protocol family 16 PCI: Using configuration type 1 PCI: Using MMCONFIG at e000 mtrr: v2.0 (20020519) ACPI: Subsystem revision 20050309 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (:00) PCI: Probing PCI hardware (bus 00) ACPI: Assume root bridge [\_SB_.PCI0] segment is 0 PCI: Ignoring BAR0-3 of IDE controller :00:1f.1 Boot video device is :04:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: Can't get handler for
Re: 2.6.12-rc2-mm2
Hello Andrew, along the 2.6.12-rcX-mmX PCI-Express is not usable at all with mm-patchsets. I posted some days ago the problem taht the IRQs get not regonized by the kernel also with pci=routeirq nothing helped. The problem still the same and some new problems now with 2.6.12-rc2-mm2 in addition. This computer has an Intel Pentium 4 630 with HT,EIST and EMT64 enabled. In 2.6.12-rc2 everything works perfect. So I post my dmesg output maybe you can see some interesting things there. I hope you'll find the issue or bug..whatever hope that its possible to sort the problems out. Thanks in Advanced Now I post the 2.6.12-rc2-mm2 and after that the 2.6.12-rc2 vanilla kernel output 2.6.12-rc2-mm2 output: Bootdata ok (command line is root=/dev/md1 vga=794 quiet) Linux version 2.6.12-rc2-mm2-md1 ([EMAIL PROTECTED]) (gcc-Version 3.4.3 20041125 (Gentoo Linux 3.4.3-r1, ssp-3.4.3-0, pie-8.7.7)) #2 SMP PREEMPT Fri Apr 8 13:35:42 CEST 2005 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000e4000 - 0010 (reserved) BIOS-e820: 0010 - 3ffb (usable) BIOS-e820: 3ffb - 3ffbe000 (ACPI data) BIOS-e820: 3ffbe000 - 3fff (ACPI NVS) BIOS-e820: 3fff - 4000 (reserved) BIOS-e820: ffb0 - 0001 (reserved) ACPI: RSDP (v002 ACPIAM) @ 0x000fafa0 ACPI: XSDT (v001 A M I OEMXSDT 0x02000503 MSFT 0x0097) @ 0x3ffb0100 ACPI: FADT (v003 A M I OEMFACP 0x02000503 MSFT 0x0097) @ 0x3ffb0290 ACPI: MADT (v001 A M I OEMAPIC 0x02000503 MSFT 0x0097) @ 0x3ffb0390 ACPI: OEMB (v001 A M I AMI_OEM 0x02000503 MSFT 0x0097) @ 0x3ffbe040 ACPI: MCFG (v001 A M I OEMMCFG 0x02000503 MSFT 0x0097) @ 0x3ffb6c40 ACPI: DSDT (v001 A0144 A0144000 0x INTL 0x02002026) @ 0x On node 0 totalpages: 262064 DMA zone: 4096 pages, LIFO batch:1 Normal zone: 257968 pages, LIFO batch:16 HighMem zone: 0 pages, LIFO batch:1 ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled) Processor #0 15:4 APIC version 16 ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled) Processor #1 15:4 APIC version 16 ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0]) IOAPIC[0]: apic_id 2, version 32, address 0xfec0, GSI 0-23 ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) ACPI: IRQ0 used by override. ACPI: IRQ2 used by override. ACPI: IRQ9 used by override. Setting APIC routing to flat Using ACPI (MADT) for SMP configuration information Allocating PCI resources starting at 4000 (gap: 4000:bfb0) Built 1 zonelists Initializing CPU#0 Kernel command line: root=/dev/md1 vga=794 quiet console=tty0 PID hash table entries: 4096 (order: 12, 131072 bytes) time.c: Using 1.193182 MHz PIT timer. time.c: Detected 3527.408 MHz processor. Console: colour dummy device 80x25 Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes) Memory: 1024964k/1048256k available (3240k kernel code, 22664k reserved, 1218k data, 212k init) Calibrating delay loop... 6963.20 BogoMIPS (lpj=3481600) Security Framework v1.0.0 initialized Capability LSM initialized Mount-cache hash table entries: 256 CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K using mwait in idle threads. CPU: Physical Processor ID: 0 CPU0: Thermal monitoring enabled (TM1) Using IO APIC NMI watchdog activating NMI Watchdog ... done. Using local APIC timer interrupts. Detected 13.778 MHz APIC timer. Booting processor 1/1 rip 6000 rsp 81003ff35f58 Initializing CPU#1 Calibrating delay loop... 7045.12 BogoMIPS (lpj=3522560) CPU: Trace cache: 12K uops, L1 D cache: 16K CPU: L2 cache: 2048K CPU: Physical Processor ID: 0 CPU1: Thermal monitoring enabled (TM1) Intel(R) Pentium(R) 4 CPU 3.20GHz stepping 03 Synced TSC of CPU 1 difference 107374180328 APIC error on CPU1: 00(40) Brought up 2 CPUs time.c: Using PIT/TSC based timekeeping. CPU0 attaching sched-domain: domain 0: span 3 groups: 1 2 CPU1 attaching sched-domain: domain 0: span 3 groups: 2 1 NET: Registered protocol family 16 PCI: Using configuration type 1 PCI: Using MMCONFIG at e000 mtrr: v2.0 (20020519) ACPI: Subsystem revision 20050309 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: PCI Root Bridge [PCI0] (:00) PCI: Probing PCI hardware (bus 00) ACPI: Assume root bridge [\_SB_.PCI0] segment is 0 PCI: Ignoring BAR0-3 of IDE controller :00:1f.1 Boot video device is :04:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: Can't get handler for
Re: 2.6.12-rc1-bk6 boot problem
[EMAIL PROTECTED] wrote: >Dual P4 (Tyan S2662/I7505) > >Booting of 2.6.12-rc1-bk6 stops after these lines .. > >.. >Enabling IO-APIC IRQs >.. TIMER; vector=0x31 oin1=2 pin2=-1 >checking TSC synchronization across 4 CPUs: passed >Brought up 4 CPUs > >2.6.12-rc1 works. >Please cc me, I am not subscribed. > > Hello kladit, Searching on lkml.org show The fix was posted yesterday again. http://lkml.org/lkml/2005/4/3/74 = net/core/sock.c 1.67 vs edited = --- 1.67/net/core/sock.c2005-03-26 17:04:35 -06:00 +++ edited/net/core/sock.c 2005-04-02 13:37:20 -06:00 @@ -1352,7 +1352,7 @@ EXPORT_SYMBOL(sk_common_release); -static rwlock_t proto_list_lock; +static DEFINE_RWLOCK(proto_list_lock); static LIST_HEAD(proto_list); int proto_register(struct proto *prot, int alloc_slab) Best regards Mit freundlichen Grüßen M.Thonke - 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: 2.6.12-rc1-bk6 boot problem
[EMAIL PROTECTED] wrote: Dual P4 (Tyan S2662/I7505) Booting of 2.6.12-rc1-bk6 stops after these lines .. .. Enabling IO-APIC IRQs .. TIMER; vector=0x31 oin1=2 pin2=-1 checking TSC synchronization across 4 CPUs: passed Brought up 4 CPUs 2.6.12-rc1 works. Please cc me, I am not subscribed. Hello kladit, Searching on lkml.org show The fix was posted yesterday again. http://lkml.org/lkml/2005/4/3/74 = net/core/sock.c 1.67 vs edited = --- 1.67/net/core/sock.c2005-03-26 17:04:35 -06:00 +++ edited/net/core/sock.c 2005-04-02 13:37:20 -06:00 @@ -1352,7 +1352,7 @@ EXPORT_SYMBOL(sk_common_release); -static rwlock_t proto_list_lock; +static DEFINE_RWLOCK(proto_list_lock); static LIST_HEAD(proto_list); int proto_register(struct proto *prot, int alloc_slab) Best regards Mit freundlichen Grüßen M.Thonke - 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: 2.6.12-rc1-bk does not boot x86_64
Thanks Alexander this sort this out. No system boots w/o problems :-) Alexander Nyberg wrote: >>I tried the recent 2.6.12-rc1-bk5 snapshot from kernel.org. >>When I want to boot my x86_64 system only a green line appears on screen. >>The config is the same as in 2.6.12-rc1-bk4 which works flawlessly on my >>system. >> >>I only saw the message that CPU0 and CPU1 where initialized. And then >>there was >>Brinnging up CPUs and it stopped. >> >>Its an Intel Pentium4 640 with (EMT64,HT,EIST,CIE enabled). >>The graphic card is an Nvidia 6600GT PCIe device. >> >> > >I had the same nasty surprise this morning, this will probably help: > > >Well, this is a brown paper bag for someone. The new protocol >registration locking uses a rwlock to limit access to the protocol list. >Unfortunately, the initialisation: > >static rwlock_t proto_list_lock; > >Only works to initialise the lock as unlocked on platforms whose unlock >signal is all zeros. On other platforms, they think it's already locked >and hang forever. > >Signed-off-by: James Bottomley <[EMAIL PROTECTED]> > > >= net/core/sock.c 1.67 vs edited = >--- 1.67/net/core/sock.c 2005-03-26 17:04:35 -06:00 >+++ edited/net/core/sock.c 2005-04-02 13:37:20 -06:00 >@@ -1352,7 +1352,7 @@ > > EXPORT_SYMBOL(sk_common_release); > >-static rwlock_t proto_list_lock; >+static DEFINE_RWLOCK(proto_list_lock); > static LIST_HEAD(proto_list); > > int proto_register(struct proto *prot, int alloc_slab) > > >- > > > > > - 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/
2.6.12-rc1-bk does not boot x86_64
Hello, I tried the recent 2.6.12-rc1-bk5 snapshot from kernel.org. When I want to boot my x86_64 system only a green line appears on screen. The config is the same as in 2.6.12-rc1-bk4 which works flawlessly on my system. I only saw the message that CPU0 and CPU1 where initialized. And then there was Brinnging up CPUs and it stopped. Its an Intel Pentium4 640 with (EMT64,HT,EIST,CIE enabled). The graphic card is an Nvidia 6600GT PCIe device. Thanks Best regards - 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/
2.6.12-rc1-bk does not boot x86_64
Hello, I tried the recent 2.6.12-rc1-bk5 snapshot from kernel.org. When I want to boot my x86_64 system only a green line appears on screen. The config is the same as in 2.6.12-rc1-bk4 which works flawlessly on my system. I only saw the message that CPU0 and CPU1 where initialized. And then there was Brinnging up CPUs and it stopped. Its an Intel Pentium4 640 with (EMT64,HT,EIST,CIE enabled). The graphic card is an Nvidia 6600GT PCIe device. Thanks Best regards - 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: PCI-Express not working/unuseable on Intel 925XE Chipset since 2.6.12-rc1[mm1-4]
Hello Jacek, I finially got it working :-) my PCI-Express devices working now... I grabbed the last bk-snapshot from kernel.org 2.6.12-rc1-bk3 and et volia everything except the Marvell Yokon PCI-E device working. I hope Andrew will look into the mm-line to find the bug? Greets and Best regards |Jacek Luczak schrieb: hello Michael :) This message: ACPI: No ACPI bus support for 00:00 means that acpi_get_bus_type() is unable to determinate bus type! Mayby someone forgot about PCI-E? Regards Jacek - 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: PCI-Express not working/unuseable on Intel 925XE Chipset since 2.6.12-rc1[mm1-4]
hello Jacek, its not related to the vendor so far we are :-) Maybe Andrew Morton or some other will read this. Because 2.6.12 should be a stable version not a flacky one. But what is wrong now on 2.6.12-rc1 **. It work flawlessly on 2.6.11.X kernels. Mebye we back that out :-) Greetz |Jacek Luczak schrieb: Michael Thonke napisaÅ(a): Hello, since the first version of 2.6.12-rc1 and mm[1-4] kernel I can't use any of my PCI-Express devices that worked with all 2.6.11.[1-6] kernels. It's a real odd right now. I have 25 computers with an Intel 925XE Chipset based motherboards and Intel 6xx CPU on it. So far it does not metter which vendor I choose (ASUS,ABIT,MSI etc.) the problem stay the same and spread all over.I tried to boot with pci=routeicq but it did not help to get one device working with any 2.6.12-rc1-xx kernel. As I mentioned before I tested it with on several (over 25 computer) with various motherboards (with ASUS,ABIT,MSI etc.) no luck. Its an 64bit system with [EMT64] and SMP/SMT and preempt enabled + cpufreq. My first look was on PCI Routingtable and I found a difference to 2.6.11.x working kernel: I've got the same problem with i915 on Asus P5GDC V Deluxe Mainboard. This fragment of dmesg is from 2.6.12-rc1-mm4 kernel: PCI: Probing PCI hardware (bus 00) ACPI: Assume root bridge [\_SB_.PCI0] segment is 0 Boot video device is :00:02.0 PCI: Ignoring BAR0-3 of IDE controller :00:1f.1 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: Can't get handler for :00:02.0 ACPI: Can't get handler for :00:02.1 ACPI: Can't get handler for :00:1b.0 ACPI: Can't get handler for :00:1f.3 ACPI: Can't get handler for :02:00.0 ACPI: Can't get handler for :01:04.0 ACPI: Can't get handler for :01:0a.0 ACPI: Can't get handler for :01:0b.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P3._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 *7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 *4 5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11 12 14 15) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init ACPI: No ACPI bus support for 00:00 ACPI: No ACPI bus support for 00:01 ACPI: No ACPI bus support for 00:02 ACPI: No ACPI bus support for 00:03 ACPI: No ACPI bus support for 00:04 ACPI: No ACPI bus support for 00:05 ACPI: No ACPI bus support for 00:06 ACPI: No ACPI bus support for 00:07 ACPI: No ACPI bus support for 00:08 ACPI: No ACPI bus support for 00:09 ACPI: No ACPI bus support for 00:0a ACPI: No ACPI bus support for 00:0b ACPI: No ACPI bus support for 00:0c ACPI: No ACPI bus support for 00:0d ACPI: No ACPI bus support for 00:0e ACPI: No ACPI bus support for 00:0f ACPI: No ACPI bus support for 00:10 pnp: PnP ACPI: found 17 devices SCSI subsystem initialized LSPCI OUTPUT: 00:00.0 Host bridge: Intel Corp.: Unknown device 2580 (rev 04) Subsystem: Intel Corp.: Unknown device 2580 Flags: bus master, fast devsel, latency 0 Capabilities: [e0] #09 [2109] 00:02.0 VGA compatible controller: Intel Corp.: Unknown device 2582 (rev 04) (prog-if 00 [VGA]) Subsystem: Asustek Computer, Inc.: Unknown device 2582 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at cfc8 (32-bit, non-prefetchable) [size=512K] I/O ports at 9800 [size=8] Memory at d000 (32-bit, prefetchable) [size=256M] Memory at cfd8 (32-bit, non-prefetchable) [size=256K] Expansion ROM at [disabled] Capabilities: [d0] Power Management version 2 00:02.1 Display controller: Intel Corp.: Unknown device 2782 (rev 04) Subsystem: Asustek Computer, Inc.: Unknown device 2582 Flags: bus master, fast devsel, latency 0 Memory at cfd0 (32-bit, non-prefetchable) [size=512K] Capabilities: [d0] Power Management version 2 00:1b.0 Class 0403: Intel Corp.: Unknown device 2668 (rev 03) Subsystem: Asustek Computer, Inc.: Unknown device 813d Flags: bus master, fast devsel, latency 0, IRQ 10 Memory at cfdf4000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [70] #10 [0091] 00:1c.0 PCI bridge: Intel Corp. I/O Controller Hub PCI Express Port 0 (rev 03) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: e000-efff Capabilities: [40] #10 [0141] Capabilities: [80] Message Signalled
PCI-Express not working/unuseable on Intel 925XE Chipset since 2.6.12-rc1[mm1-4]
Hello, since the first version of 2.6.12-rc1 and mm[1-4] kernel I can't use any of my PCI-Express devices that worked with all 2.6.11.[1-6] kernels. It's a real odd right now. I have 25 computers with an Intel 925XE Chipset based motherboards and Intel 6xx CPU on it. So far it does not metter which vendor I choose (ASUS,ABIT,MSI etc.) the problem stay the same and spread all over.I tried to boot with pci=routeicq but it did not help to get one device working with any 2.6.12-rc1-xx kernel. As I mentioned before I tested it with on several (over 25 computer) with various motherboards (with ASUS,ABIT,MSI etc.) no luck. Its an 64bit system with [EMT64] and SMP/SMT and preempt enabled + cpufreq. My first look was on PCI Routingtable and I found a difference to 2.6.11.x working kernel: So far Thanks in advance and best regards //possible bug/problem PCI: Ignoring BAR0-3 of IDE controller :00:1f.1 Boot video device is :04:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: Can't get handler for :00:1b.0 --> why this happen ACPI: Can't get handler for :00:1f.3 --> it does not appear ACPI: Can't get handler for :04:00.0 --> on 2.6.11.x kernels. ACPI: Can't get handler for :02:00.0 --> - * - ACPI: Can't get handler for :01:09.0 --> - * - ACPI: Can't get handler for :01:0a.0 --> - * - //this looks like a garbage routing and handler table here ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P3._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKF] (IRQs 3 *4 5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11 12 14 15) //lspci -v output :00:00.0 Host bridge: Intel Corporation 925X/XE Memory Controller Hub (rev 0e) Subsystem: Intel Corporation: Unknown device 2580 Flags: bus master, fast devsel, latency 0 Capabilities: [e0] #09 [0109] :00:01.0 PCI bridge: Intel Corporation 925X/XE PCI Express Root Port (rev 0e) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: e000-efff Memory behind bridge: d2f0-d7ff Prefetchable memory behind bridge: d800-dfff Expansion ROM at e000 [disabled] [size=4K] Capabilities: [88] #0d [] Capabilities: [80] Power Management version 2 Capabilities: [90] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+ Capabilities: [a0] #10 [0141] :00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04) Subsystem: ASUSTeK Computer Inc.: Unknown device 813d Flags: bus master, fast devsel, latency 0, IRQ 169 Memory at d2cf4000 (64-bit, non-prefetchable) Capabilities: [50] Power Management version 2 Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [70] #10 [0091] :00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 04) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: d000-dfff Expansion ROM at d000 [disabled] [size=4K] Capabilities: [40] #10 [0141] Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+ Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 :00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 (rev 04) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: c000-cfff Memory behind bridge: d2e0-d2ef Expansion ROM at c000 [disabled] [size=4K] Capabilities: [40] #10 [0141] Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+ Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 :00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 04) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc.: Unknown device 80a6 Flags: bus master, medium devsel, latency 0, IRQ 50 I/O ports at 9880 [size=32] :00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 04) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc.: Unknown device 80a6
PCI-Express not working/unuseable on Intel 925XE Chipset since 2.6.12-rc1[mm1-4]
Hello, since the first version of 2.6.12-rc1 and mm[1-4] kernel I can't use any of my PCI-Express devices that worked with all 2.6.11.[1-6] kernels. It's a real odd right now. I have 25 computers with an Intel 925XE Chipset based motherboards and Intel 6xx CPU on it. So far it does not metter which vendor I choose (ASUS,ABIT,MSI etc.) the problem stay the same and spread all over.I tried to boot with pci=routeicq but it did not help to get one device working with any 2.6.12-rc1-xx kernel. As I mentioned before I tested it with on several (over 25 computer) with various motherboards (with ASUS,ABIT,MSI etc.) no luck. Its an 64bit system with [EMT64] and SMP/SMT and preempt enabled + cpufreq. My first look was on PCI Routingtable and I found a difference to 2.6.11.x working kernel: So far Thanks in advance and best regards //possible bug/problem PCI: Ignoring BAR0-3 of IDE controller :00:1f.1 Boot video device is :04:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: Can't get handler for :00:1b.0 -- why this happen ACPI: Can't get handler for :00:1f.3 -- it does not appear ACPI: Can't get handler for :04:00.0 -- on 2.6.11.x kernels. ACPI: Can't get handler for :02:00.0 -- - * - ACPI: Can't get handler for :01:09.0 -- - * - ACPI: Can't get handler for :01:0a.0 -- - * - //this looks like a garbage routing and handler table here ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P3._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKF] (IRQs 3 *4 5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11 12 14 15) //lspci -v output :00:00.0 Host bridge: Intel Corporation 925X/XE Memory Controller Hub (rev 0e) Subsystem: Intel Corporation: Unknown device 2580 Flags: bus master, fast devsel, latency 0 Capabilities: [e0] #09 [0109] :00:01.0 PCI bridge: Intel Corporation 925X/XE PCI Express Root Port (rev 0e) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: e000-efff Memory behind bridge: d2f0-d7ff Prefetchable memory behind bridge: d800-dfff Expansion ROM at e000 [disabled] [size=4K] Capabilities: [88] #0d [] Capabilities: [80] Power Management version 2 Capabilities: [90] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+ Capabilities: [a0] #10 [0141] :00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04) Subsystem: ASUSTeK Computer Inc.: Unknown device 813d Flags: bus master, fast devsel, latency 0, IRQ 169 Memory at d2cf4000 (64-bit, non-prefetchable) Capabilities: [50] Power Management version 2 Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [70] #10 [0091] :00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 04) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: d000-dfff Expansion ROM at d000 [disabled] [size=4K] Capabilities: [40] #10 [0141] Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+ Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 :00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 (rev 04) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: c000-cfff Memory behind bridge: d2e0-d2ef Expansion ROM at c000 [disabled] [size=4K] Capabilities: [40] #10 [0141] Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+ Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 :00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 04) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc.: Unknown device 80a6 Flags: bus master, medium devsel, latency 0, IRQ 50 I/O ports at 9880 [size=32] :00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 04) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc.: Unknown device 80a6
Re: PCI-Express not working/unuseable on Intel 925XE Chipset since 2.6.12-rc1[mm1-4]
hello Jacek, its not related to the vendor so far we are :-) Maybe Andrew Morton or some other will read this. Because 2.6.12 should be a stable version not a flacky one. But what is wrong now on 2.6.12-rc1 **. It work flawlessly on 2.6.11.X kernels. Mebye we back that out :-) Greetz |Jacek Luczak schrieb: Michael Thonke napisa(a): Hello, since the first version of 2.6.12-rc1 and mm[1-4] kernel I can't use any of my PCI-Express devices that worked with all 2.6.11.[1-6] kernels. It's a real odd right now. I have 25 computers with an Intel 925XE Chipset based motherboards and Intel 6xx CPU on it. So far it does not metter which vendor I choose (ASUS,ABIT,MSI etc.) the problem stay the same and spread all over.I tried to boot with pci=routeicq but it did not help to get one device working with any 2.6.12-rc1-xx kernel. As I mentioned before I tested it with on several (over 25 computer) with various motherboards (with ASUS,ABIT,MSI etc.) no luck. Its an 64bit system with [EMT64] and SMP/SMT and preempt enabled + cpufreq. My first look was on PCI Routingtable and I found a difference to 2.6.11.x working kernel: I've got the same problem with i915 on Asus P5GDC V Deluxe Mainboard. This fragment of dmesg is from 2.6.12-rc1-mm4 kernel: PCI: Probing PCI hardware (bus 00) ACPI: Assume root bridge [\_SB_.PCI0] segment is 0 Boot video device is :00:02.0 PCI: Ignoring BAR0-3 of IDE controller :00:1f.1 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: Can't get handler for :00:02.0 ACPI: Can't get handler for :00:02.1 ACPI: Can't get handler for :00:1b.0 ACPI: Can't get handler for :00:1f.3 ACPI: Can't get handler for :02:00.0 ACPI: Can't get handler for :01:04.0 ACPI: Can't get handler for :01:0a.0 ACPI: Can't get handler for :01:0b.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P3._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 *5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 *7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 *4 5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11 12 14 15) Linux Plug and Play Support v0.97 (c) Adam Belay pnp: PnP ACPI init ACPI: No ACPI bus support for 00:00 ACPI: No ACPI bus support for 00:01 ACPI: No ACPI bus support for 00:02 ACPI: No ACPI bus support for 00:03 ACPI: No ACPI bus support for 00:04 ACPI: No ACPI bus support for 00:05 ACPI: No ACPI bus support for 00:06 ACPI: No ACPI bus support for 00:07 ACPI: No ACPI bus support for 00:08 ACPI: No ACPI bus support for 00:09 ACPI: No ACPI bus support for 00:0a ACPI: No ACPI bus support for 00:0b ACPI: No ACPI bus support for 00:0c ACPI: No ACPI bus support for 00:0d ACPI: No ACPI bus support for 00:0e ACPI: No ACPI bus support for 00:0f ACPI: No ACPI bus support for 00:10 pnp: PnP ACPI: found 17 devices SCSI subsystem initialized LSPCI OUTPUT: 00:00.0 Host bridge: Intel Corp.: Unknown device 2580 (rev 04) Subsystem: Intel Corp.: Unknown device 2580 Flags: bus master, fast devsel, latency 0 Capabilities: [e0] #09 [2109] 00:02.0 VGA compatible controller: Intel Corp.: Unknown device 2582 (rev 04) (prog-if 00 [VGA]) Subsystem: Asustek Computer, Inc.: Unknown device 2582 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at cfc8 (32-bit, non-prefetchable) [size=512K] I/O ports at 9800 [size=8] Memory at d000 (32-bit, prefetchable) [size=256M] Memory at cfd8 (32-bit, non-prefetchable) [size=256K] Expansion ROM at unassigned [disabled] Capabilities: [d0] Power Management version 2 00:02.1 Display controller: Intel Corp.: Unknown device 2782 (rev 04) Subsystem: Asustek Computer, Inc.: Unknown device 2582 Flags: bus master, fast devsel, latency 0 Memory at cfd0 (32-bit, non-prefetchable) [size=512K] Capabilities: [d0] Power Management version 2 00:1b.0 Class 0403: Intel Corp.: Unknown device 2668 (rev 03) Subsystem: Asustek Computer, Inc.: Unknown device 813d Flags: bus master, fast devsel, latency 0, IRQ 10 Memory at cfdf4000 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [70] #10 [0091] 00:1c.0 PCI bridge: Intel Corp. I/O Controller Hub PCI Express Port 0 (rev 03) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: e000-efff Capabilities: [40] #10 [0141] Capabilities: [80] Message
Re: PCI-Express not working/unuseable on Intel 925XE Chipset since 2.6.12-rc1[mm1-4]
Hello Jacek, I finially got it working :-) my PCI-Express devices working now... I grabbed the last bk-snapshot from kernel.org 2.6.12-rc1-bk3 and et volia everything except the Marvell Yokon PCI-E device working. I hope Andrew will look into the mm-line to find the bug? Greets and Best regards |Jacek Luczak schrieb: hello Michael :) This message: ACPI: No ACPI bus support for 00:00 means that acpi_get_bus_type() is unable to determinate bus type! Mayby someone forgot about PCI-E? Regards Jacek - 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/
Unusable/non working PCI-Express on Intel 925XE Chipset since 2.6.12-rc1[mm1-4]
Hello, since the first version of 2.6.12-rc1 and mm[1-4] kernel I can't use any of my PCI-Express devices that work with all 2.6.11.[1-6] kernels. Its a real odd right now. I have 25 computers with an Intel 925XE Chipset and Intel 6xx CPU. It does not metter which vendor I choose the problem spread all over.I tried to boot with pci=routeicq but it did not help to get one device working ith 2.6.12-rc1-xx kernel. As I mentioned before I tested it with over 25 computer (with ASUS,ABIT,MSI etc.) no luck. Its an 64bit system [EMT64] and SMP/SMT enabled and preempt. My first look was on PCI Routingtable and what I found in difference to 2.6.11.x working kernel is that: Here I print the posssible bug/problem, lspci and dmesg output from kernel. So far Thanks in advance and best regards //possible bug/problem PCI: Ignoring BAR0-3 of IDE controller :00:1f.1 Boot video device is :04:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: Can't get handler for :00:1b.0 ACPI: Can't get handler for :00:1f.3 ACPI: Can't get handler for :04:00.0 ACPI: Can't get handler for :02:00.0 ACPI: Can't get handler for :01:09.0 ACPI: Can't get handler for :01:0a.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P3._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKF] (IRQs 3 *4 5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11 12 14 15) //lspci -v output :00:00.0 Host bridge: Intel Corporation 925X/XE Memory Controller Hub (rev 0e) Subsystem: Intel Corporation: Unknown device 2580 Flags: bus master, fast devsel, latency 0 Capabilities: [e0] #09 [0109] :00:01.0 PCI bridge: Intel Corporation 925X/XE PCI Express Root Port (rev 0e) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: e000-efff Memory behind bridge: d2f0-d7ff Prefetchable memory behind bridge: d800-dfff Expansion ROM at e000 [disabled] [size=4K] Capabilities: [88] #0d [] Capabilities: [80] Power Management version 2 Capabilities: [90] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+ Capabilities: [a0] #10 [0141] :00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04) Subsystem: ASUSTeK Computer Inc.: Unknown device 813d Flags: bus master, fast devsel, latency 0, IRQ 169 Memory at d2cf4000 (64-bit, non-prefetchable) Capabilities: [50] Power Management version 2 Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [70] #10 [0091] :00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 04) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: d000-dfff Expansion ROM at d000 [disabled] [size=4K] Capabilities: [40] #10 [0141] Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+ Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 :00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 (rev 04) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: c000-cfff Memory behind bridge: d2e0-d2ef Expansion ROM at c000 [disabled] [size=4K] Capabilities: [40] #10 [0141] Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+ Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 :00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 04) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc.: Unknown device 80a6 Flags: bus master, medium devsel, latency 0, IRQ 50 I/O ports at 9880 [size=32] :00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 04) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc.: Unknown device 80a6 Flags: bus master, medium devsel, latency 0, IRQ 233 I/O ports at 9c00 [size=32] :00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB
Unusable/non working PCI-Express on Intel 925XE Chipset since 2.6.12-rc1[mm1-4]
Hello, since the first version of 2.6.12-rc1 and mm[1-4] kernel I can't use any of my PCI-Express devices that work with all 2.6.11.[1-6] kernels. Its a real odd right now. I have 25 computers with an Intel 925XE Chipset and Intel 6xx CPU. It does not metter which vendor I choose the problem spread all over.I tried to boot with pci=routeicq but it did not help to get one device working ith 2.6.12-rc1-xx kernel. As I mentioned before I tested it with over 25 computer (with ASUS,ABIT,MSI etc.) no luck. Its an 64bit system [EMT64] and SMP/SMT enabled and preempt. My first look was on PCI Routingtable and what I found in difference to 2.6.11.x working kernel is that: Here I print the posssible bug/problem, lspci and dmesg output from kernel. So far Thanks in advance and best regards //possible bug/problem PCI: Ignoring BAR0-3 of IDE controller :00:1f.1 Boot video device is :04:00.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] ACPI: Can't get handler for :00:1b.0 ACPI: Can't get handler for :00:1f.3 ACPI: Can't get handler for :04:00.0 ACPI: Can't get handler for :02:00.0 ACPI: Can't get handler for :01:09.0 ACPI: Can't get handler for :01:0a.0 ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P1._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P3._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P4._PRT] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.P0P5._PRT] ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 *7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs *3 4 5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKF] (IRQs 3 *4 5 6 7 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 10 11 12 14 15) *0, disabled. ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 5 6 7 10 *11 12 14 15) //lspci -v output :00:00.0 Host bridge: Intel Corporation 925X/XE Memory Controller Hub (rev 0e) Subsystem: Intel Corporation: Unknown device 2580 Flags: bus master, fast devsel, latency 0 Capabilities: [e0] #09 [0109] :00:01.0 PCI bridge: Intel Corporation 925X/XE PCI Express Root Port (rev 0e) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=04, subordinate=04, sec-latency=0 I/O behind bridge: e000-efff Memory behind bridge: d2f0-d7ff Prefetchable memory behind bridge: d800-dfff Expansion ROM at e000 [disabled] [size=4K] Capabilities: [88] #0d [] Capabilities: [80] Power Management version 2 Capabilities: [90] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+ Capabilities: [a0] #10 [0141] :00:1b.0 Class 0403: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller (rev 04) Subsystem: ASUSTeK Computer Inc.: Unknown device 813d Flags: bus master, fast devsel, latency 0, IRQ 169 Memory at d2cf4000 (64-bit, non-prefetchable) Capabilities: [50] Power Management version 2 Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable- Capabilities: [70] #10 [0091] :00:1c.0 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 (rev 04) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=0 I/O behind bridge: d000-dfff Expansion ROM at d000 [disabled] [size=4K] Capabilities: [40] #10 [0141] Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+ Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 :00:1c.1 PCI bridge: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 (rev 04) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: c000-cfff Memory behind bridge: d2e0-d2ef Expansion ROM at c000 [disabled] [size=4K] Capabilities: [40] #10 [0141] Capabilities: [80] Message Signalled Interrupts: 64bit- Queue=0/0 Enable+ Capabilities: [90] #0d [] Capabilities: [a0] Power Management version 2 :00:1d.0 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 (rev 04) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc.: Unknown device 80a6 Flags: bus master, medium devsel, latency 0, IRQ 50 I/O ports at 9880 [size=32] :00:1d.1 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 (rev 04) (prog-if 00 [UHCI]) Subsystem: ASUSTeK Computer Inc.: Unknown device 80a6 Flags: bus master, medium devsel, latency 0, IRQ 233 I/O ports at 9c00 [size=32] :00:1d.2 USB Controller: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB
