* Kernel Panics on IDE Initialization @ 2002-02-28 4:34 Kristopher Kersey 2002-03-01 1:22 ` Alan Cox 0 siblings, 1 reply; 11+ messages in thread From: Kristopher Kersey @ 2002-02-28 4:34 UTC (permalink / raw) To: linux-kernel All, On two seperate motherboards that I have been testing, the ABIT KR7A-RAID and the SOYO FIRE DRAGON, 2.4 kernels panic on boot up during IDE initialization. I don't really know how to track down the problem but now that I've seen it on two boards I'm a bit worried. This does not happen with 2.2 kernels so it is 2.4 specific. I have tested with 2.4.17 and 2.4.18 pre releases. I will try to field any questions to solve the problem. Please CC me directly on any correspondence as I am not currently subscribed to this list. Thanks, Kris Kersey (Augustus) LinuxHardware.org augustus@linuxhardware.org ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Kernel Panics on IDE Initialization 2002-02-28 4:34 Kernel Panics on IDE Initialization Kristopher Kersey @ 2002-03-01 1:22 ` Alan Cox 2002-03-01 3:49 ` Kristopher Kersey 0 siblings, 1 reply; 11+ messages in thread From: Alan Cox @ 2002-03-01 1:22 UTC (permalink / raw) To: Kristopher Kersey; +Cc: linux-kernel > On two seperate motherboards that I have been testing, the ABIT > KR7A-RAID and the SOYO FIRE DRAGON, 2.4 kernels panic on boot up during > IDE initialization. I don't really know how to track down the problem but > now that I've seen it on two boards I'm a bit worried. This does not > happen with 2.2 kernels so it is 2.4 specific. I have tested with 2.4.17 > and 2.4.18 pre releases. I will try to field any questions to solve the Try 2.4.18 proper and 2.4.18-ac2 - we fixed at least one oops caused by controllers and mishandling of new revisions not in our tables. If it still fails send me the pci data for them ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Kernel Panics on IDE Initialization 2002-03-01 1:22 ` Alan Cox @ 2002-03-01 3:49 ` Kristopher Kersey 2002-03-01 9:33 ` Martin Dalecki 0 siblings, 1 reply; 11+ messages in thread From: Kristopher Kersey @ 2002-03-01 3:49 UTC (permalink / raw) To: Alan Cox; +Cc: linux-kernel [-- Attachment #1: Type: TEXT/PLAIN, Size: 854 bytes --] Still panics at initialization. I have attached the /proc/pci and lspci output. This is for the SOYO board. I will see about getting the ABIT board information. Kris On Fri, 1 Mar 2002, Alan Cox wrote: > > On two seperate motherboards that I have been testing, the ABIT > > KR7A-RAID and the SOYO FIRE DRAGON, 2.4 kernels panic on boot up during > > IDE initialization. I don't really know how to track down the problem but > > now that I've seen it on two boards I'm a bit worried. This does not > > happen with 2.2 kernels so it is 2.4 specific. I have tested with 2.4.17 > > and 2.4.18 pre releases. I will try to field any questions to solve the > > Try 2.4.18 proper and 2.4.18-ac2 - we fixed at least one oops caused by > controllers and mishandling of new revisions not in our tables. If it > still fails send me the pci data for them > [-- Attachment #2: Type: TEXT/PLAIN, Size: 4593 bytes --] PCI devices found: Bus 0, device 0, function 0: Host bridge: Intel Unknown device (rev 4). Vendor id=8086. Device id=1a30. Fast devsel. Fast back-to-back capable. Master Capable. No bursts. Prefetchable 32 bit memory at 0xe0000000 [0xe0000008]. Bus 0, device 1, function 0: PCI bridge: Intel Unknown device (rev 4). Vendor id=8086. Device id=1a31. Fast devsel. Fast back-to-back capable. Master Capable. Latency=64. Min Gnt=14. Bus 0, device 30, function 0: PCI bridge: Intel Unknown device (rev 5). Vendor id=8086. Device id=244e. Fast devsel. Fast back-to-back capable. Master Capable. No bursts. Min Gnt=6. Bus 0, device 31, function 0: ISA bridge: Intel Unknown device (rev 5). Vendor id=8086. Device id=2440. Medium devsel. Fast back-to-back capable. Master Capable. No bursts. Bus 0, device 31, function 1: IDE interface: Intel Unknown device (rev 5). Vendor id=8086. Device id=244b. Medium devsel. Fast back-to-back capable. Master Capable. No bursts. I/O at 0xf000 [0xf001]. Bus 0, device 31, function 2: USB Controller: Intel Unknown device (rev 5). Vendor id=8086. Device id=2442. Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. No bursts. I/O at 0xb000 [0xb001]. Bus 0, device 31, function 3: SM Bus: Intel Unknown device (rev 5). Vendor id=8086. Device id=2443. Medium devsel. Fast back-to-back capable. IRQ 10. I/O at 0x5000 [0x5001]. Bus 0, device 31, function 4: USB Controller: Intel Unknown device (rev 5). Vendor id=8086. Device id=2444. Medium devsel. Fast back-to-back capable. IRQ 9. Master Capable. No bursts. I/O at 0xb800 [0xb801]. Bus 1, device 0, function 0: VGA compatible controller: NVidia Unknown device (rev 163). Vendor id=10de. Device id=201. Medium devsel. Fast back-to-back capable. IRQ 12. Master Capable. Latency=32. Min Gnt=5.Max Lat=1. Non-prefetchable 32 bit memory at 0xec000000 [0xec000000]. Prefetchable 32 bit memory at 0xe4000000 [0xe4000008]. Prefetchable 32 bit memory at 0xe8000000 [0xe8000008]. Bus 2, device 6, function 0: RAID storage controller: Triones Technologies, Inc. Unknown device (rev 5). Vendor id=1103. Device id=4. Medium devsel. IRQ 11. Master Capable. Latency=64. Min Gnt=8.Max Lat=8. I/O at 0x9000 [0x9001]. I/O at 0x9400 [0x9401]. I/O at 0x9800 [0x9801]. I/O at 0x9c00 [0x9c01]. I/O at 0xa000 [0xa001]. Bus 2, device 7, function 0: Multimedia audio controller: Unknown vendor Unknown device (rev 16). Vendor id=13f6. Device id=111. Medium devsel. IRQ 5. Master Capable. Latency=32. Min Gnt=2.Max Lat=24. I/O at 0xa400 [0xa401]. Bus 2, device 8, function 0: Ethernet controller: Intel Unknown device (rev 3). Vendor id=8086. Device id=2449. Medium devsel. Fast back-to-back capable. IRQ 10. Master Capable. Latency=32. Min Gnt=8.Max Lat=56. Non-prefetchable 32 bit memory at 0xef005000 [0xef005000]. I/O at 0xa800 [0xa801]. Bus 2, device 9, function 0: FireWire (IEEE 1394): Texas Instruments Unknown device (rev 0). Vendor id=104c. Device id=8023. Medium devsel. IRQ 9. Master Capable. Latency=32. Min Gnt=2.Max Lat=4. Non-prefetchable 32 bit memory at 0xef004000 [0xef004000]. Non-prefetchable 32 bit memory at 0xef000000 [0xef000000]. 00:00.0 Host bridge: Intel Corporation: Unknown device 1a30 (rev 04) 00:01.0 PCI bridge: Intel Corporation: Unknown device 1a31 (rev 04) 00:1e.0 PCI bridge: Intel Corporation: Unknown device 244e (rev 05) 00:1f.0 ISA bridge: Intel Corporation: Unknown device 2440 (rev 05) 00:1f.1 IDE interface: Intel Corporation: Unknown device 244b (rev 05) 00:1f.2 USB Controller: Intel Corporation: Unknown device 2442 (rev 05) 00:1f.3 SMBus: Intel Corporation: Unknown device 2443 (rev 05) 00:1f.4 USB Controller: Intel Corporation: Unknown device 2444 (rev 05) 01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0201 (rev a3) 02:06.0 RAID bus controller: Triones Technologies, Inc. HPT366 (rev 05) 02:07.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) 02:08.0 Ethernet controller: Intel Corporation: Unknown device 2449 (rev 03) 02:09.0 FireWire (IEEE 1394): Texas Instruments: Unknown device 8023 ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Kernel Panics on IDE Initialization 2002-03-01 3:49 ` Kristopher Kersey @ 2002-03-01 9:33 ` Martin Dalecki 2002-03-01 11:39 ` Andre Hedrick 0 siblings, 1 reply; 11+ messages in thread From: Martin Dalecki @ 2002-03-01 9:33 UTC (permalink / raw) To: Kristopher Kersey; +Cc: Alan Cox, linux-kernel Kristopher Kersey wrote: > Still panics at initialization. I have attached the /proc/pci and lspci > output. This is for the SOYO board. I will see about getting the ABIT > board information. > > Kris > > On Fri, 1 Mar 2002, Alan Cox wrote: > > >>>On two seperate motherboards that I have been testing, the ABIT >>>KR7A-RAID and the SOYO FIRE DRAGON, 2.4 kernels panic on boot up during >>>IDE initialization. I don't really know how to track down the problem but >>>now that I've seen it on two boards I'm a bit worried. This does not >>>happen with 2.2 kernels so it is 2.4 specific. I have tested with 2.4.17 >>>and 2.4.18 pre releases. I will try to field any questions to solve the >>> >>Try 2.4.18 proper and 2.4.18-ac2 - we fixed at least one oops caused by >>controllers and mishandling of new revisions not in our tables. If it >>still fails send me the pci data for them >> >> >> >>------------------------------------------------------------------------ >> >>PCI devices found: >> Bus 0, device 0, function 0: >> Host bridge: Intel Unknown device (rev 4). >> Vendor id=8086. Device id=1a30. >> Fast devsel. Fast back-to-back capable. Master Capable. No bursts. >> Prefetchable 32 bit memory at 0xe0000000 [0xe0000008]. >> Bus 0, device 1, function 0: >> PCI bridge: Intel Unknown device (rev 4). >> Vendor id=8086. Device id=1a31. >> Fast devsel. Fast back-to-back capable. Master Capable. Latency=64. Min Gnt=14. >> Bus 0, device 30, function 0: >> PCI bridge: Intel Unknown device (rev 5). >> Vendor id=8086. Device id=244e. >> Fast devsel. Fast back-to-back capable. Master Capable. No bursts. Min Gnt=6. >> Bus 0, device 31, function 0: >> ISA bridge: Intel Unknown device (rev 5). >> Vendor id=8086. Device id=2440. >> Medium devsel. Fast back-to-back capable. Master Capable. No bursts. >> Bus 0, device 31, function 1: >> IDE interface: Intel Unknown device (rev 5). >> Vendor id=8086. Device id=244b. >> Medium devsel. Fast back-to-back capable. Master Capable. No bursts. >> I/O at 0xf000 [0xf001]. >> Bus 0, device 31, function 2: >> USB Controller: Intel Unknown device (rev 5). >> Vendor id=8086. Device id=2442. >> Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. No bursts. >> I/O at 0xb000 [0xb001]. >> Bus 0, device 31, function 3: >> SM Bus: Intel Unknown device (rev 5). >> Vendor id=8086. Device id=2443. >> Medium devsel. Fast back-to-back capable. IRQ 10. >> I/O at 0x5000 [0x5001]. >> Bus 0, device 31, function 4: >> USB Controller: Intel Unknown device (rev 5). >> Vendor id=8086. Device id=2444. >> Medium devsel. Fast back-to-back capable. IRQ 9. Master Capable. No bursts. >> I/O at 0xb800 [0xb801]. >> Bus 1, device 0, function 0: >> VGA compatible controller: NVidia Unknown device (rev 163). >> Vendor id=10de. Device id=201. >> Medium devsel. Fast back-to-back capable. IRQ 12. Master Capable. Latency=32. Min Gnt=5.Max Lat=1. >> Non-prefetchable 32 bit memory at 0xec000000 [0xec000000]. >> Prefetchable 32 bit memory at 0xe4000000 [0xe4000008]. >> Prefetchable 32 bit memory at 0xe8000000 [0xe8000008]. >> Bus 2, device 6, function 0: >> RAID storage controller: Triones Technologies, Inc. Unknown device (rev 5). >> Vendor id=1103. Device id=4. >> Medium devsel. IRQ 11. Master Capable. Latency=64. Min Gnt=8.Max Lat=8. >> I/O at 0x9000 [0x9001]. >> I/O at 0x9400 [0x9401]. >> I/O at 0x9800 [0x9801]. >> I/O at 0x9c00 [0x9c01]. >> I/O at 0xa000 [0xa001]. >> Bus 2, device 7, function 0: >> Multimedia audio controller: Unknown vendor Unknown device (rev 16). >> Vendor id=13f6. Device id=111. >> Medium devsel. IRQ 5. Master Capable. Latency=32. Min Gnt=2.Max Lat=24. >> I/O at 0xa400 [0xa401]. >> Bus 2, device 8, function 0: >> Ethernet controller: Intel Unknown device (rev 3). >> Vendor id=8086. Device id=2449. >> Medium devsel. Fast back-to-back capable. IRQ 10. Master Capable. Latency=32. Min Gnt=8.Max Lat=56. >> Non-prefetchable 32 bit memory at 0xef005000 [0xef005000]. >> I/O at 0xa800 [0xa801]. >> Bus 2, device 9, function 0: >> FireWire (IEEE 1394): Texas Instruments Unknown device (rev 0). >> Vendor id=104c. Device id=8023. >> Medium devsel. IRQ 9. Master Capable. Latency=32. Min Gnt=2.Max Lat=4. >> Non-prefetchable 32 bit memory at 0xef004000 [0xef004000]. >> Non-prefetchable 32 bit memory at 0xef000000 [0xef000000]. >> >> >> >>00:00.0 Host bridge: Intel Corporation: Unknown device 1a30 (rev 04) >>00:01.0 PCI bridge: Intel Corporation: Unknown device 1a31 (rev 04) >>00:1e.0 PCI bridge: Intel Corporation: Unknown device 244e (rev 05) >>00:1f.0 ISA bridge: Intel Corporation: Unknown device 2440 (rev 05) >>00:1f.1 IDE interface: Intel Corporation: Unknown device 244b (rev 05) Please add this device ID to the abnormally long list in ide-pci.c and your chances may increase. >>00:1f.2 USB Controller: Intel Corporation: Unknown device 2442 (rev 05) >>00:1f.3 SMBus: Intel Corporation: Unknown device 2443 (rev 05) >>00:1f.4 USB Controller: Intel Corporation: Unknown device 2444 (rev 05) >>01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0201 (rev a3) >>02:06.0 RAID bus controller: Triones Technologies, Inc. HPT366 (rev 05) >>02:07.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) >>02:08.0 Ethernet controller: Intel Corporation: Unknown device 2449 (rev 03) >>02:09.0 FireWire (IEEE 1394): Texas Instruments: Unknown device 8023 >> -- - phone: +49 214 8656 283 - job: eVision-Ventures AG, LEV .de (MY OPINIONS ARE MY OWN!) - langs: de_DE.ISO8859-1, en_US, pl_PL.ISO8859-2, last ressort: ru_RU.KOI8-R ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Kernel Panics on IDE Initialization 2002-03-01 9:33 ` Martin Dalecki @ 2002-03-01 11:39 ` Andre Hedrick 2002-03-01 20:22 ` Kristopher Kersey 0 siblings, 1 reply; 11+ messages in thread From: Andre Hedrick @ 2002-03-01 11:39 UTC (permalink / raw) To: Martin Dalecki; +Cc: Kristopher Kersey, Alan Cox, linux-kernel On Fri, 1 Mar 2002, Martin Dalecki wrote: > Kristopher Kersey wrote: > > Still panics at initialization. I have attached the /proc/pci and lspci > > output. This is for the SOYO board. I will see about getting the ABIT > > board information. > > > > Kris > > > > On Fri, 1 Mar 2002, Alan Cox wrote: > > > > > >>>On two seperate motherboards that I have been testing, the ABIT > >>>KR7A-RAID and the SOYO FIRE DRAGON, 2.4 kernels panic on boot up during > >>>IDE initialization. I don't really know how to track down the problem but > >>>now that I've seen it on two boards I'm a bit worried. This does not > >>>happen with 2.2 kernels so it is 2.4 specific. I have tested with 2.4.17 > >>>and 2.4.18 pre releases. I will try to field any questions to solve the > >>> > >>Try 2.4.18 proper and 2.4.18-ac2 - we fixed at least one oops caused by > >>controllers and mishandling of new revisions not in our tables. If it > >>still fails send me the pci data for them > >> > >> > >> > >>------------------------------------------------------------------------ > >> > >>PCI devices found: > >> Bus 0, device 0, function 0: > >> Host bridge: Intel Unknown device (rev 4). > >> Vendor id=8086. Device id=1a30. > >> Fast devsel. Fast back-to-back capable. Master Capable. No bursts. > >> Prefetchable 32 bit memory at 0xe0000000 [0xe0000008]. > >> Bus 0, device 1, function 0: > >> PCI bridge: Intel Unknown device (rev 4). > >> Vendor id=8086. Device id=1a31. > >> Fast devsel. Fast back-to-back capable. Master Capable. Latency=64. Min Gnt=14. > >> Bus 0, device 30, function 0: > >> PCI bridge: Intel Unknown device (rev 5). > >> Vendor id=8086. Device id=244e. > >> Fast devsel. Fast back-to-back capable. Master Capable. No bursts. Min Gnt=6. > >> Bus 0, device 31, function 0: > >> ISA bridge: Intel Unknown device (rev 5). > >> Vendor id=8086. Device id=2440. > >> Medium devsel. Fast back-to-back capable. Master Capable. No bursts. > >> Bus 0, device 31, function 1: > >> IDE interface: Intel Unknown device (rev 5). > >> Vendor id=8086. Device id=244b. > >> Medium devsel. Fast back-to-back capable. Master Capable. No bursts. > >> I/O at 0xf000 [0xf001]. > >> Bus 0, device 31, function 2: > >> USB Controller: Intel Unknown device (rev 5). > >> Vendor id=8086. Device id=2442. > >> Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. No bursts. > >> I/O at 0xb000 [0xb001]. > >> Bus 0, device 31, function 3: > >> SM Bus: Intel Unknown device (rev 5). > >> Vendor id=8086. Device id=2443. > >> Medium devsel. Fast back-to-back capable. IRQ 10. > >> I/O at 0x5000 [0x5001]. > >> Bus 0, device 31, function 4: > >> USB Controller: Intel Unknown device (rev 5). > >> Vendor id=8086. Device id=2444. > >> Medium devsel. Fast back-to-back capable. IRQ 9. Master Capable. No bursts. > >> I/O at 0xb800 [0xb801]. > >> Bus 1, device 0, function 0: > >> VGA compatible controller: NVidia Unknown device (rev 163). > >> Vendor id=10de. Device id=201. > >> Medium devsel. Fast back-to-back capable. IRQ 12. Master Capable. Latency=32. Min Gnt=5.Max Lat=1. > >> Non-prefetchable 32 bit memory at 0xec000000 [0xec000000]. > >> Prefetchable 32 bit memory at 0xe4000000 [0xe4000008]. > >> Prefetchable 32 bit memory at 0xe8000000 [0xe8000008]. > >> Bus 2, device 6, function 0: > >> RAID storage controller: Triones Technologies, Inc. Unknown device (rev 5). > >> Vendor id=1103. Device id=4. > >> Medium devsel. IRQ 11. Master Capable. Latency=64. Min Gnt=8.Max Lat=8. > >> I/O at 0x9000 [0x9001]. > >> I/O at 0x9400 [0x9401]. > >> I/O at 0x9800 [0x9801]. > >> I/O at 0x9c00 [0x9c01]. > >> I/O at 0xa000 [0xa001]. > >> Bus 2, device 7, function 0: > >> Multimedia audio controller: Unknown vendor Unknown device (rev 16). > >> Vendor id=13f6. Device id=111. > >> Medium devsel. IRQ 5. Master Capable. Latency=32. Min Gnt=2.Max Lat=24. > >> I/O at 0xa400 [0xa401]. > >> Bus 2, device 8, function 0: > >> Ethernet controller: Intel Unknown device (rev 3). > >> Vendor id=8086. Device id=2449. > >> Medium devsel. Fast back-to-back capable. IRQ 10. Master Capable. Latency=32. Min Gnt=8.Max Lat=56. > >> Non-prefetchable 32 bit memory at 0xef005000 [0xef005000]. > >> I/O at 0xa800 [0xa801]. > >> Bus 2, device 9, function 0: > >> FireWire (IEEE 1394): Texas Instruments Unknown device (rev 0). > >> Vendor id=104c. Device id=8023. > >> Medium devsel. IRQ 9. Master Capable. Latency=32. Min Gnt=2.Max Lat=4. > >> Non-prefetchable 32 bit memory at 0xef004000 [0xef004000]. > >> Non-prefetchable 32 bit memory at 0xef000000 [0xef000000]. > >> > >> > >> > >>00:00.0 Host bridge: Intel Corporation: Unknown device 1a30 (rev 04) > >>00:01.0 PCI bridge: Intel Corporation: Unknown device 1a31 (rev 04) > >>00:1e.0 PCI bridge: Intel Corporation: Unknown device 244e (rev 05) > >>00:1f.0 ISA bridge: Intel Corporation: Unknown device 2440 (rev 05) > >>00:1f.1 IDE interface: Intel Corporation: Unknown device 244b (rev 05) > > Please add this device ID to the abnormally long list in ide-pci.c and > your chances may increase. No, that only allows it to be reported. It does not nothing until is is indexed in the Host core. But you know that, it is obvious. > >>00:1f.2 USB Controller: Intel Corporation: Unknown device 2442 (rev 05) > >>00:1f.3 SMBus: Intel Corporation: Unknown device 2443 (rev 05) > >>00:1f.4 USB Controller: Intel Corporation: Unknown device 2444 (rev 05) > >>01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0201 (rev a3) > >>02:06.0 RAID bus controller: Triones Technologies, Inc. HPT366 (rev 05) Oh and you forgot this one here, too > >>02:07.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) > >>02:08.0 Ethernet controller: Intel Corporation: Unknown device 2449 (rev 03) > >>02:09.0 FireWire (IEEE 1394): Texas Instruments: Unknown device 8023 > >> > Cheers, Andre Hedrick Linux Disk Certification Project Linux ATA Development ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Kernel Panics on IDE Initialization 2002-03-01 11:39 ` Andre Hedrick @ 2002-03-01 20:22 ` Kristopher Kersey 2002-03-01 20:56 ` Alan Cox 0 siblings, 1 reply; 11+ messages in thread From: Kristopher Kersey @ 2002-03-01 20:22 UTC (permalink / raw) To: Andre Hedrick; +Cc: Martin Dalecki, Alan Cox, linux-kernel I have word that it's the HighPoint controller's fault. I will verify this myself and let you know. Kris On Fri, 1 Mar 2002, Andre Hedrick wrote: > On Fri, 1 Mar 2002, Martin Dalecki wrote: > > > Kristopher Kersey wrote: > > > Still panics at initialization. I have attached the /proc/pci and lspci > > > output. This is for the SOYO board. I will see about getting the ABIT > > > board information. > > > > > > Kris > > > > > > On Fri, 1 Mar 2002, Alan Cox wrote: > > > > > > > > >>>On two seperate motherboards that I have been testing, the ABIT > > >>>KR7A-RAID and the SOYO FIRE DRAGON, 2.4 kernels panic on boot up during > > >>>IDE initialization. I don't really know how to track down the problem but > > >>>now that I've seen it on two boards I'm a bit worried. This does not > > >>>happen with 2.2 kernels so it is 2.4 specific. I have tested with 2.4.17 > > >>>and 2.4.18 pre releases. I will try to field any questions to solve the > > >>> > > >>Try 2.4.18 proper and 2.4.18-ac2 - we fixed at least one oops caused by > > >>controllers and mishandling of new revisions not in our tables. If it > > >>still fails send me the pci data for them > > >> > > >> > > >> > > >>------------------------------------------------------------------------ > > >> > > >>PCI devices found: > > >> Bus 0, device 0, function 0: > > >> Host bridge: Intel Unknown device (rev 4). > > >> Vendor id=8086. Device id=1a30. > > >> Fast devsel. Fast back-to-back capable. Master Capable. No bursts. > > >> Prefetchable 32 bit memory at 0xe0000000 [0xe0000008]. > > >> Bus 0, device 1, function 0: > > >> PCI bridge: Intel Unknown device (rev 4). > > >> Vendor id=8086. Device id=1a31. > > >> Fast devsel. Fast back-to-back capable. Master Capable. Latency=64. Min Gnt=14. > > >> Bus 0, device 30, function 0: > > >> PCI bridge: Intel Unknown device (rev 5). > > >> Vendor id=8086. Device id=244e. > > >> Fast devsel. Fast back-to-back capable. Master Capable. No bursts. Min Gnt=6. > > >> Bus 0, device 31, function 0: > > >> ISA bridge: Intel Unknown device (rev 5). > > >> Vendor id=8086. Device id=2440. > > >> Medium devsel. Fast back-to-back capable. Master Capable. No bursts. > > >> Bus 0, device 31, function 1: > > >> IDE interface: Intel Unknown device (rev 5). > > >> Vendor id=8086. Device id=244b. > > >> Medium devsel. Fast back-to-back capable. Master Capable. No bursts. > > >> I/O at 0xf000 [0xf001]. > > >> Bus 0, device 31, function 2: > > >> USB Controller: Intel Unknown device (rev 5). > > >> Vendor id=8086. Device id=2442. > > >> Medium devsel. Fast back-to-back capable. IRQ 11. Master Capable. No bursts. > > >> I/O at 0xb000 [0xb001]. > > >> Bus 0, device 31, function 3: > > >> SM Bus: Intel Unknown device (rev 5). > > >> Vendor id=8086. Device id=2443. > > >> Medium devsel. Fast back-to-back capable. IRQ 10. > > >> I/O at 0x5000 [0x5001]. > > >> Bus 0, device 31, function 4: > > >> USB Controller: Intel Unknown device (rev 5). > > >> Vendor id=8086. Device id=2444. > > >> Medium devsel. Fast back-to-back capable. IRQ 9. Master Capable. No bursts. > > >> I/O at 0xb800 [0xb801]. > > >> Bus 1, device 0, function 0: > > >> VGA compatible controller: NVidia Unknown device (rev 163). > > >> Vendor id=10de. Device id=201. > > >> Medium devsel. Fast back-to-back capable. IRQ 12. Master Capable. Latency=32. Min Gnt=5.Max Lat=1. > > >> Non-prefetchable 32 bit memory at 0xec000000 [0xec000000]. > > >> Prefetchable 32 bit memory at 0xe4000000 [0xe4000008]. > > >> Prefetchable 32 bit memory at 0xe8000000 [0xe8000008]. > > >> Bus 2, device 6, function 0: > > >> RAID storage controller: Triones Technologies, Inc. Unknown device (rev 5). > > >> Vendor id=1103. Device id=4. > > >> Medium devsel. IRQ 11. Master Capable. Latency=64. Min Gnt=8.Max Lat=8. > > >> I/O at 0x9000 [0x9001]. > > >> I/O at 0x9400 [0x9401]. > > >> I/O at 0x9800 [0x9801]. > > >> I/O at 0x9c00 [0x9c01]. > > >> I/O at 0xa000 [0xa001]. > > >> Bus 2, device 7, function 0: > > >> Multimedia audio controller: Unknown vendor Unknown device (rev 16). > > >> Vendor id=13f6. Device id=111. > > >> Medium devsel. IRQ 5. Master Capable. Latency=32. Min Gnt=2.Max Lat=24. > > >> I/O at 0xa400 [0xa401]. > > >> Bus 2, device 8, function 0: > > >> Ethernet controller: Intel Unknown device (rev 3). > > >> Vendor id=8086. Device id=2449. > > >> Medium devsel. Fast back-to-back capable. IRQ 10. Master Capable. Latency=32. Min Gnt=8.Max Lat=56. > > >> Non-prefetchable 32 bit memory at 0xef005000 [0xef005000]. > > >> I/O at 0xa800 [0xa801]. > > >> Bus 2, device 9, function 0: > > >> FireWire (IEEE 1394): Texas Instruments Unknown device (rev 0). > > >> Vendor id=104c. Device id=8023. > > >> Medium devsel. IRQ 9. Master Capable. Latency=32. Min Gnt=2.Max Lat=4. > > >> Non-prefetchable 32 bit memory at 0xef004000 [0xef004000]. > > >> Non-prefetchable 32 bit memory at 0xef000000 [0xef000000]. > > >> > > >> > > >> > > >>00:00.0 Host bridge: Intel Corporation: Unknown device 1a30 (rev 04) > > >>00:01.0 PCI bridge: Intel Corporation: Unknown device 1a31 (rev 04) > > >>00:1e.0 PCI bridge: Intel Corporation: Unknown device 244e (rev 05) > > >>00:1f.0 ISA bridge: Intel Corporation: Unknown device 2440 (rev 05) > > >>00:1f.1 IDE interface: Intel Corporation: Unknown device 244b (rev 05) > > > > Please add this device ID to the abnormally long list in ide-pci.c and > > your chances may increase. > > No, that only allows it to be reported. > It does not nothing until is is indexed in the Host core. > But you know that, it is obvious. > > > >>00:1f.2 USB Controller: Intel Corporation: Unknown device 2442 (rev 05) > > >>00:1f.3 SMBus: Intel Corporation: Unknown device 2443 (rev 05) > > >>00:1f.4 USB Controller: Intel Corporation: Unknown device 2444 (rev 05) > > >>01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0201 (rev a3) > > >>02:06.0 RAID bus controller: Triones Technologies, Inc. HPT366 (rev 05) > > Oh and you forgot this one here, too > > > >>02:07.0 Multimedia audio controller: C-Media Electronics Inc CM8738 (rev 10) > > >>02:08.0 Ethernet controller: Intel Corporation: Unknown device 2449 (rev 03) > > >>02:09.0 FireWire (IEEE 1394): Texas Instruments: Unknown device 8023 > > >> > > > > Cheers, > > Andre Hedrick > Linux Disk Certification Project Linux ATA Development > ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Kernel Panics on IDE Initialization 2002-03-01 20:22 ` Kristopher Kersey @ 2002-03-01 20:56 ` Alan Cox 2002-03-02 0:17 ` Andre Hedrick 2002-03-02 12:03 ` Vojtech Pavlik 0 siblings, 2 replies; 11+ messages in thread From: Alan Cox @ 2002-03-01 20:56 UTC (permalink / raw) To: Kristopher Kersey; +Cc: Andre Hedrick, Martin Dalecki, Alan Cox, linux-kernel > I have word that it's the HighPoint controller's fault. I will verify > this myself and let you know. Ok ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Kernel Panics on IDE Initialization 2002-03-01 20:56 ` Alan Cox @ 2002-03-02 0:17 ` Andre Hedrick 2002-03-02 4:47 ` Kristopher Kersey 2002-03-02 12:03 ` Vojtech Pavlik 1 sibling, 1 reply; 11+ messages in thread From: Andre Hedrick @ 2002-03-02 0:17 UTC (permalink / raw) To: Alan Cox; +Cc: Kristopher Kersey, linux-kernel Oh I already have the skinny and working on it. I still have the touch! Also I have a sponsor for the 374 code so now to find somebody for the 372 and the variations it shows up in :-/ Cheers, On Fri, 1 Mar 2002, Alan Cox wrote: > > I have word that it's the HighPoint controller's fault. I will verify > > this myself and let you know. > > Ok > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ > Andre Hedrick Linux Disk Certification Project Linux ATA Development ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Kernel Panics on IDE Initialization 2002-03-02 0:17 ` Andre Hedrick @ 2002-03-02 4:47 ` Kristopher Kersey 0 siblings, 0 replies; 11+ messages in thread From: Kristopher Kersey @ 2002-03-02 4:47 UTC (permalink / raw) To: Andre Hedrick; +Cc: Alan Cox, linux-kernel I have verified that it is indeed the HighPoint IDE that it's getting hung up on. I simply disabled it in the BIOS and it booted just fine. Any ideas on a fix though would still be appreciated. I will test this out on the ABIT board also since it has a HighPoint on board also. thanks, Kris On Fri, 1 Mar 2002, Andre Hedrick wrote: > > Oh I already have the skinny and working on it. > I still have the touch! > > Also I have a sponsor for the 374 code so now to find somebody for the 372 > and the variations it shows up in :-/ > > Cheers, > > > On Fri, 1 Mar 2002, Alan Cox wrote: > > > > I have word that it's the HighPoint controller's fault. I will verify > > > this myself and let you know. > > > > Ok > > - > > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > > the body of a message to majordomo@vger.kernel.org > > More majordomo info at http://vger.kernel.org/majordomo-info.html > > Please read the FAQ at http://www.tux.org/lkml/ > > > > Andre Hedrick > Linux Disk Certification Project Linux ATA Development > ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Kernel Panics on IDE Initialization 2002-03-01 20:56 ` Alan Cox 2002-03-02 0:17 ` Andre Hedrick @ 2002-03-02 12:03 ` Vojtech Pavlik 2002-03-18 17:13 ` Kristopher Kersey 1 sibling, 1 reply; 11+ messages in thread From: Vojtech Pavlik @ 2002-03-02 12:03 UTC (permalink / raw) To: Alan Cox Cc: Kristopher Kersey, Andre Hedrick, Martin Dalecki, linux-kernel, linux-ide [-- Attachment #1: Type: text/plain, Size: 553 bytes --] On Fri, Mar 01, 2002 at 08:56:59PM +0000, Alan Cox wrote: > > I have word that it's the HighPoint controller's fault. I will verify > > this myself and let you know. > > Ok I have many reports the HPT RAID controllers cause kernels (RH 7.3 install) to crash, unfortunately because the VIA IDE spits an unrelated warning message on many of the affected mainboards just before the HPT code crashes ... Well, this patch fixes two possible array overflows in the HPT code. There is quite likely a lot more of stuff to fix. -- Vojtech Pavlik SuSE Labs [-- Attachment #2: hpt366fixes.diff --] [-- Type: text/plain, Size: 878 bytes --] --- hpt366.c Thu Jan 31 16:45:20 2002 +++ hpt366.c.new Sat Mar 2 13:00:16 2002 @@ -375,7 +375,8 @@ class_rev &= 0xff; p += sprintf(p, "\nController: %d\n", i); - p += sprintf(p, "Chipset: HPT%s\n", chipset_nums[class_rev]); + p += sprintf(p, "Chipset: HPT%s\n", + class_rev < sizeof(chipset_nums) / sizeof(char *) ? chipset_nums[class_rev] : "???"); p += sprintf(p, "--------------- Primary Channel " "--------------- Secondary Channel " "--------------\n"); @@ -1120,12 +1121,11 @@ if (test != 0x08) pci_write_config_byte(dev, PCI_MAX_LAT, 0x08); - if (pci_rev_check_hpt3xx(dev)) { + if (pci_rev_check_hpt3xx(dev)) init_hpt370(dev); + + if (n_hpt_devs < HPT366_MAX_DEVS) hpt_devs[n_hpt_devs++] = dev; - } else { - hpt_devs[n_hpt_devs++] = dev; - } #if defined(DISPLAY_HPT366_TIMINGS) && defined(CONFIG_PROC_FS) if (!hpt366_proc) { ^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: Kernel Panics on IDE Initialization 2002-03-02 12:03 ` Vojtech Pavlik @ 2002-03-18 17:13 ` Kristopher Kersey 0 siblings, 0 replies; 11+ messages in thread From: Kristopher Kersey @ 2002-03-18 17:13 UTC (permalink / raw) To: Vojtech Pavlik Cc: Alan Cox, Andre Hedrick, Martin Dalecki, linux-kernel, linux-ide Just wanted to let everyone know that the problem with the HighPoint controller on the SOYO Dragon has been fixed with the latest 2.4.19 pre patches. Thanks, Kris Kersey augustus@linuxhardware.org On Sat, 2 Mar 2002, Vojtech Pavlik wrote: > On Fri, Mar 01, 2002 at 08:56:59PM +0000, Alan Cox wrote: > > > I have word that it's the HighPoint controller's fault. I will verify > > > this myself and let you know. > > > > Ok > > I have many reports the HPT RAID controllers cause kernels (RH 7.3 > install) to crash, unfortunately because the VIA IDE spits an unrelated > warning message on many of the affected mainboards just before the HPT > code crashes ... > > Well, this patch fixes two possible array overflows in the HPT code. > There is quite likely a lot more of stuff to fix. > > -- > Vojtech Pavlik > SuSE Labs > ^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2002-03-18 17:26 UTC | newest] Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2002-02-28 4:34 Kernel Panics on IDE Initialization Kristopher Kersey 2002-03-01 1:22 ` Alan Cox 2002-03-01 3:49 ` Kristopher Kersey 2002-03-01 9:33 ` Martin Dalecki 2002-03-01 11:39 ` Andre Hedrick 2002-03-01 20:22 ` Kristopher Kersey 2002-03-01 20:56 ` Alan Cox 2002-03-02 0:17 ` Andre Hedrick 2002-03-02 4:47 ` Kristopher Kersey 2002-03-02 12:03 ` Vojtech Pavlik 2002-03-18 17:13 ` Kristopher Kersey
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).