Re: 2.4.x kernel BUG at filemap.c:81
Jeff Garzik wrote: Marcelo Tosatti wrote: On Wed, Feb 09, 2005 at 11:23:42PM -0500, Todd Shetter wrote: Marcelo Tosatti wrote: On Wed, Feb 09, 2005 at 03:47:28PM -0500, Todd Shetter wrote: Running slackware 10 and 10.1, with kernels 2.4.26, 2.4.27, 2.4.28, 2.4.29 with highmem 4GB, and highmem i/o support enabled, I get a system lockup. This happens in both X and console. Happens with and without my Nvidia drivers loaded. I cannot determine what makes this bug present it self besides highmem and high i/o support enabled. Im guessing the system is fine until highmem is actually used to some point and then it borks, but I really have no idea and so im just making a random guess. I ran memtest86 for a few hours a while ago thinking that it may be bad memory, but that did not seem to be the problem. If you need anymore information, or have questions, or wish me to test anything, PLEASE feel free to contact me, I would really like to see this bug resolved. =) Todd Shetter Feb 8 19:49:31 quark kernel: kernel BUG at filemap.c:81! Feb 8 19:49:31 quark kernel: invalid operand: Feb 8 19:49:31 quark kernel: CPU:0 Feb 8 19:49:31 quark kernel: EIP:0010:[] Tainted: P Hi Todd, Why is your kernel tainted ? I had the nvidia 1.0-6629 driver loaded when I got that error. I compiled the kernel using the slackware 10.1 config, enabled highmem 4GB support, highmem i/o, and then some kernel hacking options including debugging for highmen related things. I booted, loaded X with KDE, opened firefox a few times, and then started running hdparm because some newer 2.4.x kernels dont play nice with my SATA, ICH5, and DMA. hdparm segfaulted while running the drive read access portion of its tests, and things locked up from there in about 30secs. I've gotten the same error with the nvidia driver not loaded, so I dont think that is part of the problem. As I said, if you want me to test or try anything feel free to ask. =) Todd, Would be interesting to have the oops output without the kernel nvidia module. Do you have that saved? Sorry, it took me FOREVER to get this bug to appear again, and this time its a little different. Hum, both BUGs are due to a page with alive ->buffers mapping. Did it crashed right after hdparm now too? Can you boot your box without SATA drivers, configuring the interface to IDE mode ? Which problems are you facing with newer v2.4.x kernels and SATA? Im waiting for the system to crash, so I figured I might as well get on with the SATA problems Running 2.4.29 neither the CONFIG_BLK_DEV_IDE_SATA nor the CONFIG_SCSI_SATA are set currently and DMA is not enabled on either of my drives, hda: ST380013AS, hdb: WDC WD2500SD-01KCB0, hdc: Maxtor 94610U6. Setting DMA manually on the hard drives yields a HDIO_SET_DMA failed: Operation not permitted error. Using 2.4.26, DMA worked fine on the drives. Under 2.4.27, 2.4.28, and 2.4.29 using CONFIG_SCSI_SATA does not allow setting of DMA on the drives, yielding a HDIO_SET_DMA failed: Operation not permitted error, and the transfer speeds reported by hdparm are at about 3MB/s. I think thats expected. Jeff? If (a) this is Intel ICH hardware and (b) it is running in combined mode, it will get poor performance. For the SATA drivers, they ALWAYS run in DMA mode, so there is no need to support HDIO_SET_DMA. Jeff Yes, I am running the SATA in combined mode. That, along with Auto mode, is the only way I can get all my devices to work properly under linux. Under Enhanced mode there is no primary IDE, only second and third. My ATA drive and CDROM are hdc and hdd, which is normal, my first SATA drive which would normally be hda should be hde and the other drive should be hdf. But the kernel doesnt see them and I cant boot off my normally hda, I get an invalid root= option kernel panic. I did edit lilo to reflect the change, but the drive wasnt even listed when hdc and hdd were. Under SATA only, I only get the SATA drives, and not my ATA drive nor my CDROM. With SATA diabled, I cant get the SATA drives at all which I expected. Under Auto, which is the same as combined as far as I can tell, the kernel doesnt enable DMA for the drives using libata, and trying to enable it by hand yields the HDIO_SET_DMA failed: Operation not permitted error. So, unless there is better performance from libata with ICH5 combined mode, I am 'forced' to stay with CONFIG_BLK_DEV_IDE_SATA, which isnt a bad thing really. I get good performance from the drives, and havent had any problems yet. On a another note, kernel 2.4.30-pre1 with highmem is working fine for me, using CONFIG_BLK_DEV_IDE_SATA, uptime was a little over 2 days. -- Todd Shetter - 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.4.x kernel BUG at filemap.c:81
Jeff Garzik wrote: Marcelo Tosatti wrote: On Wed, Feb 09, 2005 at 11:23:42PM -0500, Todd Shetter wrote: Marcelo Tosatti wrote: On Wed, Feb 09, 2005 at 03:47:28PM -0500, Todd Shetter wrote: Running slackware 10 and 10.1, with kernels 2.4.26, 2.4.27, 2.4.28, 2.4.29 with highmem 4GB, and highmem i/o support enabled, I get a system lockup. This happens in both X and console. Happens with and without my Nvidia drivers loaded. I cannot determine what makes this bug present it self besides highmem and high i/o support enabled. Im guessing the system is fine until highmem is actually used to some point and then it borks, but I really have no idea and so im just making a random guess. I ran memtest86 for a few hours a while ago thinking that it may be bad memory, but that did not seem to be the problem. If you need anymore information, or have questions, or wish me to test anything, PLEASE feel free to contact me, I would really like to see this bug resolved. =) Todd Shetter Feb 8 19:49:31 quark kernel: kernel BUG at filemap.c:81! Feb 8 19:49:31 quark kernel: invalid operand: Feb 8 19:49:31 quark kernel: CPU:0 Feb 8 19:49:31 quark kernel: EIP:0010:[c01280d1] Tainted: P Hi Todd, Why is your kernel tainted ? I had the nvidia 1.0-6629 driver loaded when I got that error. I compiled the kernel using the slackware 10.1 config, enabled highmem 4GB support, highmem i/o, and then some kernel hacking options including debugging for highmen related things. I booted, loaded X with KDE, opened firefox a few times, and then started running hdparm because some newer 2.4.x kernels dont play nice with my SATA, ICH5, and DMA. hdparm segfaulted while running the drive read access portion of its tests, and things locked up from there in about 30secs. I've gotten the same error with the nvidia driver not loaded, so I dont think that is part of the problem. As I said, if you want me to test or try anything feel free to ask. =) Todd, Would be interesting to have the oops output without the kernel nvidia module. Do you have that saved? Sorry, it took me FOREVER to get this bug to appear again, and this time its a little different. Hum, both BUGs are due to a page with alive -buffers mapping. Did it crashed right after hdparm now too? Can you boot your box without SATA drivers, configuring the interface to IDE mode ? Which problems are you facing with newer v2.4.x kernels and SATA? Im waiting for the system to crash, so I figured I might as well get on with the SATA problems Running 2.4.29 neither the CONFIG_BLK_DEV_IDE_SATA nor the CONFIG_SCSI_SATA are set currently and DMA is not enabled on either of my drives, hda: ST380013AS, hdb: WDC WD2500SD-01KCB0, hdc: Maxtor 94610U6. Setting DMA manually on the hard drives yields a HDIO_SET_DMA failed: Operation not permitted error. Using 2.4.26, DMA worked fine on the drives. Under 2.4.27, 2.4.28, and 2.4.29 using CONFIG_SCSI_SATA does not allow setting of DMA on the drives, yielding a HDIO_SET_DMA failed: Operation not permitted error, and the transfer speeds reported by hdparm are at about 3MB/s. I think thats expected. Jeff? If (a) this is Intel ICH hardware and (b) it is running in combined mode, it will get poor performance. For the SATA drivers, they ALWAYS run in DMA mode, so there is no need to support HDIO_SET_DMA. Jeff Yes, I am running the SATA in combined mode. That, along with Auto mode, is the only way I can get all my devices to work properly under linux. Under Enhanced mode there is no primary IDE, only second and third. My ATA drive and CDROM are hdc and hdd, which is normal, my first SATA drive which would normally be hda should be hde and the other drive should be hdf. But the kernel doesnt see them and I cant boot off my normally hda, I get an invalid root= option kernel panic. I did edit lilo to reflect the change, but the drive wasnt even listed when hdc and hdd were. Under SATA only, I only get the SATA drives, and not my ATA drive nor my CDROM. With SATA diabled, I cant get the SATA drives at all which I expected. Under Auto, which is the same as combined as far as I can tell, the kernel doesnt enable DMA for the drives using libata, and trying to enable it by hand yields the HDIO_SET_DMA failed: Operation not permitted error. So, unless there is better performance from libata with ICH5 combined mode, I am 'forced' to stay with CONFIG_BLK_DEV_IDE_SATA, which isnt a bad thing really. I get good performance from the drives, and havent had any problems yet. On a another note, kernel 2.4.30-pre1 with highmem is working fine for me, using CONFIG_BLK_DEV_IDE_SATA, uptime was a little over 2 days. -- Todd Shetter - 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.4.x kernel BUG at filemap.c:81
Marcelo Tosatti wrote: On Wed, Feb 09, 2005 at 03:47:28PM -0500, Todd Shetter wrote: Running slackware 10 and 10.1, with kernels 2.4.26, 2.4.27, 2.4.28, 2.4.29 with highmem 4GB, and highmem i/o support enabled, I get a system lockup. This happens in both X and console. Happens with and without my Nvidia drivers loaded. I cannot determine what makes this bug present it self besides highmem and high i/o support enabled. Im guessing the system is fine until highmem is actually used to some point and then it borks, but I really have no idea and so im just making a random guess. I ran memtest86 for a few hours a while ago thinking that it may be bad memory, but that did not seem to be the problem. If you need anymore information, or have questions, or wish me to test anything, PLEASE feel free to contact me, I would really like to see this bug resolved. =) -- Todd Shetter Feb 8 19:49:31 quark kernel: kernel BUG at filemap.c:81! Feb 8 19:49:31 quark kernel: invalid operand: Feb 8 19:49:31 quark kernel: CPU:0 Feb 8 19:49:31 quark kernel: EIP:0010:[]Tainted: P Hi Todd, Why is your kernel tainted ? I had the nvidia 1.0-6629 driver loaded when I got that error. I compiled the kernel using the slackware 10.1 config, enabled highmem 4GB support, highmem i/o, and then some kernel hacking options including debugging for highmen related things. I booted, loaded X with KDE, opened firefox a few times, and then started running hdparm because some newer 2.4.x kernels dont play nice with my SATA, ICH5, and DMA. hdparm segfaulted while running the drive read access portion of its tests, and things locked up from there in about 30secs. I've gotten the same error with the nvidia driver not loaded, so I dont think that is part of the problem. As I said, if you want me to test or try anything feel free to ask. =) Todd, Would be interesting to have the oops output without the kernel nvidia module. Do you have that saved? Sorry, it took me FOREVER to get this bug to appear again, and this time its a little different. Hum, both BUGs are due to a page with alive ->buffers mapping. Did it crashed right after hdparm now too? Can you boot your box without SATA drivers, configuring the interface to IDE mode ? Which problems are you facing with newer v2.4.x kernels and SATA? Im waiting for the system to crash, so I figured I might as well get on with the SATA problems Running 2.4.29 neither the CONFIG_BLK_DEV_IDE_SATA nor the CONFIG_SCSI_SATA are set currently and DMA is not enabled on either of my drives, hda: ST380013AS, hdb: WDC WD2500SD-01KCB0, hdc: Maxtor 94610U6. Setting DMA manually on the hard drives yields a HDIO_SET_DMA failed: Operation not permitted error. Using 2.4.26, DMA worked fine on the drives. Under 2.4.27, 2.4.28, and 2.4.29 using CONFIG_SCSI_SATA does not allow setting of DMA on the drives, yielding a HDIO_SET_DMA failed: Operation not permitted error, and the transfer speeds reported by hdparm are at about 3MB/s. Under 2.4.29 using CONFIG_BLK_DEV_IDE_SATA the DMA is set fine upon boot, and I get good transfers, hdparm reports 58MB/s on my Western Digital drive. I have not tested using CONFIG_BLK_DEV_IDE_SATA on any previous kernel versions. Well, still no crash yetAgain, anything else you want me to try or do just let me know. -- Todd Shetter - 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.4.x kernel BUG at filemap.c:81
Marcelo Tosatti wrote: On Wed, Feb 09, 2005 at 11:30:05AM -0500, Todd Shetter wrote: Marcelo Tosatti wrote: On Wed, Feb 09, 2005 at 12:15:03AM -0500, Todd Shetter wrote: Running slackware 10 and 10.1, with kernels 2.4.26, 2.4.27, 2.4.28, 2.4.29 with highmem 4GB, and highmem i/o support enabled, I get a system lockup. This happens in both X and console. Happens with and without my Nvidia drivers loaded. I cannot determine what makes this bug present it self besides highmem and high i/o support enabled. Im guessing the system is fine until highmem is actually used to some point and then it borks, but I really have no idea and so im just making a random guess. I ran memtest86 for a few hours a while ago thinking that it may be bad memory, but that did not seem to be the problem. If you need anymore information, or have questions, or wish me to test anything, PLEASE feel free to contact me, I would really like to see this bug resolved. =) -- Todd Shetter Feb 8 19:49:31 quark kernel: kernel BUG at filemap.c:81! Feb 8 19:49:31 quark kernel: invalid operand: Feb 8 19:49:31 quark kernel: CPU:0 Feb 8 19:49:31 quark kernel: EIP:0010:[]Tainted: P Hi Todd, Why is your kernel tainted ? - 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/ I had the nvidia 1.0-6629 driver loaded when I got that error. I compiled the kernel using the slackware 10.1 config, enabled highmem 4GB support, highmem i/o, and then some kernel hacking options including debugging for highmen related things. I booted, loaded X with KDE, opened firefox a few times, and then started running hdparm because some newer 2.4.x kernels dont play nice with my SATA, ICH5, and DMA. hdparm segfaulted while running the drive read access portion of its tests, and things locked up from there in about 30secs. I've gotten the same error with the nvidia driver not loaded, so I dont think that is part of the problem. As I said, if you want me to test or try anything feel free to ask. =) Todd, Would be interesting to have the oops output without the kernel nvidia module. Do you have that saved? - 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/ Sorry, it took me FOREVER to get this bug to appear again, and this time its a little different. Feb 9 15:20:37 quark kernel: kernel BUG at page_alloc.c:142! Feb 9 15:20:37 quark kernel: invalid operand: Feb 9 15:20:37 quark kernel: CPU:0 Feb 9 15:20:37 quark kernel: EIP:0010:[]Not tainted Feb 9 15:20:37 quark kernel: EFLAGS: 00013206 Feb 9 15:20:37 quark kernel: eax: 0114 ebx: c17e1160 ecx: 4000 edx: Feb 9 15:20:37 quark kernel: esi: edi: eea037f0 ebp: f0f27f24 esp: f0f27ef0 Feb 9 15:20:37 quark kernel: ds: 0018 es: 0018 ss: 0018 Feb 9 15:20:37 quark kernel: Process X (pid: 2206, stackpage=f0f27000) Feb 9 15:20:37 quark kernel: Stack: c0324d68 00037000 c120 c17e11c0 c0324cb8 c1030020 c0324cf0 3207 Feb 9 15:20:37 quark kernel:c17e1160 f0f27f24 2a05c067 001fc000 eea037f0 f0f27f68 c012531c c17e1160 Feb 9 15:20:37 quark kernel:c17e1160 01fd 002f 4980 496f f0eee494 4940 Feb 9 15:20:37 quark kernel: Call Trace:[] [] [] [] Feb 9 15:20:37 quark kernel: Feb 9 15:20:37 quark kernel: Code: 0f 0b 8e 00 bf 06 2e c0 8b 53 08 85 d2 74 08 0f 0b 90 00 bf Feb 9 15:30:41 quark kernel: <6>SysRq : SAK 00:00.0 Host bridge: Intel Corp. 82875P Memory Controller Hub (rev 02) Subsystem: ABIT Computer Corp.: Unknown device 1014 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Latency: 0 Region 0: Memory at e800 (32-bit, prefetchable) [size=128M] Capabilities: [e4] #09 [2106] Capabilities: [a0] AGP version 3.0 Status: RQ=32 Iso- ArqSz=2 Cal=2 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8 Command: RQ=1 ArqSz=0 Cal=2 SBA+ AGP- GART64- 64bit- FW- Rate= 00:01.0 PCI bridge: Intel Corp. 82875P Processor to AGP Controller (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Latency: 64 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: f000-0fff Memory behind bridge: f800-faff Prefetchable memory behind bridge: f000-f7ff BridgeCtl: Parity-
Re: 2.4.x kernel BUG at filemap.c:81
Marcelo Tosatti wrote: On Wed, Feb 09, 2005 at 12:15:03AM -0500, Todd Shetter wrote: Running slackware 10 and 10.1, with kernels 2.4.26, 2.4.27, 2.4.28, 2.4.29 with highmem 4GB, and highmem i/o support enabled, I get a system lockup. This happens in both X and console. Happens with and without my Nvidia drivers loaded. I cannot determine what makes this bug present it self besides highmem and high i/o support enabled. Im guessing the system is fine until highmem is actually used to some point and then it borks, but I really have no idea and so im just making a random guess. I ran memtest86 for a few hours a while ago thinking that it may be bad memory, but that did not seem to be the problem. If you need anymore information, or have questions, or wish me to test anything, PLEASE feel free to contact me, I would really like to see this bug resolved. =) -- Todd Shetter Feb 8 19:49:31 quark kernel: kernel BUG at filemap.c:81! Feb 8 19:49:31 quark kernel: invalid operand: Feb 8 19:49:31 quark kernel: CPU:0 Feb 8 19:49:31 quark kernel: EIP:0010:[]Tainted: P Hi Todd, Why is your kernel tainted ? - 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/ I had the nvidia 1.0-6629 driver loaded when I got that error. I compiled the kernel using the slackware 10.1 config, enabled highmem 4GB support, highmem i/o, and then some kernel hacking options including debugging for highmen related things. I booted, loaded X with KDE, opened firefox a few times, and then started running hdparm because some newer 2.4.x kernels dont play nice with my SATA, ICH5, and DMA. hdparm segfaulted while running the drive read access portion of its tests, and things locked up from there in about 30secs. I've gotten the same error with the nvidia driver not loaded, so I dont think that is part of the problem. As I said, if you want me to test or try anything feel free to ask. =) -- Todd Shetter - 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.4.x kernel BUG at filemap.c:81
Marcelo Tosatti wrote: On Wed, Feb 09, 2005 at 12:15:03AM -0500, Todd Shetter wrote: Running slackware 10 and 10.1, with kernels 2.4.26, 2.4.27, 2.4.28, 2.4.29 with highmem 4GB, and highmem i/o support enabled, I get a system lockup. This happens in both X and console. Happens with and without my Nvidia drivers loaded. I cannot determine what makes this bug present it self besides highmem and high i/o support enabled. Im guessing the system is fine until highmem is actually used to some point and then it borks, but I really have no idea and so im just making a random guess. I ran memtest86 for a few hours a while ago thinking that it may be bad memory, but that did not seem to be the problem. If you need anymore information, or have questions, or wish me to test anything, PLEASE feel free to contact me, I would really like to see this bug resolved. =) -- Todd Shetter Feb 8 19:49:31 quark kernel: kernel BUG at filemap.c:81! Feb 8 19:49:31 quark kernel: invalid operand: Feb 8 19:49:31 quark kernel: CPU:0 Feb 8 19:49:31 quark kernel: EIP:0010:[c01280d1]Tainted: P Hi Todd, Why is your kernel tainted ? - 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/ I had the nvidia 1.0-6629 driver loaded when I got that error. I compiled the kernel using the slackware 10.1 config, enabled highmem 4GB support, highmem i/o, and then some kernel hacking options including debugging for highmen related things. I booted, loaded X with KDE, opened firefox a few times, and then started running hdparm because some newer 2.4.x kernels dont play nice with my SATA, ICH5, and DMA. hdparm segfaulted while running the drive read access portion of its tests, and things locked up from there in about 30secs. I've gotten the same error with the nvidia driver not loaded, so I dont think that is part of the problem. As I said, if you want me to test or try anything feel free to ask. =) -- Todd Shetter - 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.4.x kernel BUG at filemap.c:81
Marcelo Tosatti wrote: On Wed, Feb 09, 2005 at 11:30:05AM -0500, Todd Shetter wrote: Marcelo Tosatti wrote: On Wed, Feb 09, 2005 at 12:15:03AM -0500, Todd Shetter wrote: Running slackware 10 and 10.1, with kernels 2.4.26, 2.4.27, 2.4.28, 2.4.29 with highmem 4GB, and highmem i/o support enabled, I get a system lockup. This happens in both X and console. Happens with and without my Nvidia drivers loaded. I cannot determine what makes this bug present it self besides highmem and high i/o support enabled. Im guessing the system is fine until highmem is actually used to some point and then it borks, but I really have no idea and so im just making a random guess. I ran memtest86 for a few hours a while ago thinking that it may be bad memory, but that did not seem to be the problem. If you need anymore information, or have questions, or wish me to test anything, PLEASE feel free to contact me, I would really like to see this bug resolved. =) -- Todd Shetter Feb 8 19:49:31 quark kernel: kernel BUG at filemap.c:81! Feb 8 19:49:31 quark kernel: invalid operand: Feb 8 19:49:31 quark kernel: CPU:0 Feb 8 19:49:31 quark kernel: EIP:0010:[c01280d1]Tainted: P Hi Todd, Why is your kernel tainted ? - 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/ I had the nvidia 1.0-6629 driver loaded when I got that error. I compiled the kernel using the slackware 10.1 config, enabled highmem 4GB support, highmem i/o, and then some kernel hacking options including debugging for highmen related things. I booted, loaded X with KDE, opened firefox a few times, and then started running hdparm because some newer 2.4.x kernels dont play nice with my SATA, ICH5, and DMA. hdparm segfaulted while running the drive read access portion of its tests, and things locked up from there in about 30secs. I've gotten the same error with the nvidia driver not loaded, so I dont think that is part of the problem. As I said, if you want me to test or try anything feel free to ask. =) Todd, Would be interesting to have the oops output without the kernel nvidia module. Do you have that saved? - 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/ Sorry, it took me FOREVER to get this bug to appear again, and this time its a little different. Feb 9 15:20:37 quark kernel: kernel BUG at page_alloc.c:142! Feb 9 15:20:37 quark kernel: invalid operand: Feb 9 15:20:37 quark kernel: CPU:0 Feb 9 15:20:37 quark kernel: EIP:0010:[c0131095]Not tainted Feb 9 15:20:37 quark kernel: EFLAGS: 00013206 Feb 9 15:20:37 quark kernel: eax: 0114 ebx: c17e1160 ecx: 4000 edx: Feb 9 15:20:37 quark kernel: esi: edi: eea037f0 ebp: f0f27f24 esp: f0f27ef0 Feb 9 15:20:37 quark kernel: ds: 0018 es: 0018 ss: 0018 Feb 9 15:20:37 quark kernel: Process X (pid: 2206, stackpage=f0f27000) Feb 9 15:20:37 quark kernel: Stack: c0324d68 00037000 c120 c17e11c0 c0324cb8 c1030020 c0324cf0 3207 Feb 9 15:20:37 quark kernel:c17e1160 f0f27f24 2a05c067 001fc000 eea037f0 f0f27f68 c012531c c17e1160 Feb 9 15:20:37 quark kernel:c17e1160 01fd 002f 4980 496f f0eee494 4940 Feb 9 15:20:37 quark kernel: Call Trace:[c012531c] [c0127adf] [c0127ba2] [c0108d23] Feb 9 15:20:37 quark kernel: Feb 9 15:20:37 quark kernel: Code: 0f 0b 8e 00 bf 06 2e c0 8b 53 08 85 d2 74 08 0f 0b 90 00 bf Feb 9 15:30:41 quark kernel: 6SysRq : SAK 00:00.0 Host bridge: Intel Corp. 82875P Memory Controller Hub (rev 02) Subsystem: ABIT Computer Corp.: Unknown device 1014 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- Latency: 0 Region 0: Memory at e800 (32-bit, prefetchable) [size=128M] Capabilities: [e4] #09 [2106] Capabilities: [a0] AGP version 3.0 Status: RQ=32 Iso- ArqSz=2 Cal=2 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8 Command: RQ=1 ArqSz=0 Cal=2 SBA+ AGP- GART64- 64bit- FW- Rate=none 00:01.0 PCI bridge: Intel Corp. 82875P Processor to AGP Controller (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: f000-0fff Memory behind bridge: f800-faff Prefetchable memory behind
Re: 2.4.x kernel BUG at filemap.c:81
Marcelo Tosatti wrote: On Wed, Feb 09, 2005 at 03:47:28PM -0500, Todd Shetter wrote: Running slackware 10 and 10.1, with kernels 2.4.26, 2.4.27, 2.4.28, 2.4.29 with highmem 4GB, and highmem i/o support enabled, I get a system lockup. This happens in both X and console. Happens with and without my Nvidia drivers loaded. I cannot determine what makes this bug present it self besides highmem and high i/o support enabled. Im guessing the system is fine until highmem is actually used to some point and then it borks, but I really have no idea and so im just making a random guess. I ran memtest86 for a few hours a while ago thinking that it may be bad memory, but that did not seem to be the problem. If you need anymore information, or have questions, or wish me to test anything, PLEASE feel free to contact me, I would really like to see this bug resolved. =) -- Todd Shetter Feb 8 19:49:31 quark kernel: kernel BUG at filemap.c:81! Feb 8 19:49:31 quark kernel: invalid operand: Feb 8 19:49:31 quark kernel: CPU:0 Feb 8 19:49:31 quark kernel: EIP:0010:[c01280d1]Tainted: P Hi Todd, Why is your kernel tainted ? I had the nvidia 1.0-6629 driver loaded when I got that error. I compiled the kernel using the slackware 10.1 config, enabled highmem 4GB support, highmem i/o, and then some kernel hacking options including debugging for highmen related things. I booted, loaded X with KDE, opened firefox a few times, and then started running hdparm because some newer 2.4.x kernels dont play nice with my SATA, ICH5, and DMA. hdparm segfaulted while running the drive read access portion of its tests, and things locked up from there in about 30secs. I've gotten the same error with the nvidia driver not loaded, so I dont think that is part of the problem. As I said, if you want me to test or try anything feel free to ask. =) Todd, Would be interesting to have the oops output without the kernel nvidia module. Do you have that saved? Sorry, it took me FOREVER to get this bug to appear again, and this time its a little different. Hum, both BUGs are due to a page with alive -buffers mapping. Did it crashed right after hdparm now too? Can you boot your box without SATA drivers, configuring the interface to IDE mode ? Which problems are you facing with newer v2.4.x kernels and SATA? Im waiting for the system to crash, so I figured I might as well get on with the SATA problems Running 2.4.29 neither the CONFIG_BLK_DEV_IDE_SATA nor the CONFIG_SCSI_SATA are set currently and DMA is not enabled on either of my drives, hda: ST380013AS, hdb: WDC WD2500SD-01KCB0, hdc: Maxtor 94610U6. Setting DMA manually on the hard drives yields a HDIO_SET_DMA failed: Operation not permitted error. Using 2.4.26, DMA worked fine on the drives. Under 2.4.27, 2.4.28, and 2.4.29 using CONFIG_SCSI_SATA does not allow setting of DMA on the drives, yielding a HDIO_SET_DMA failed: Operation not permitted error, and the transfer speeds reported by hdparm are at about 3MB/s. Under 2.4.29 using CONFIG_BLK_DEV_IDE_SATA the DMA is set fine upon boot, and I get good transfers, hdparm reports 58MB/s on my Western Digital drive. I have not tested using CONFIG_BLK_DEV_IDE_SATA on any previous kernel versions. Well, still no crash yetAgain, anything else you want me to try or do just let me know. -- Todd Shetter - 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.4.x kernel BUG at filemap.c:81
Running slackware 10 and 10.1, with kernels 2.4.26, 2.4.27, 2.4.28, 2.4.29 with highmem 4GB, and highmem i/o support enabled, I get a system lockup. This happens in both X and console. Happens with and without my Nvidia drivers loaded. I cannot determine what makes this bug present it self besides highmem and high i/o support enabled. Im guessing the system is fine until highmem is actually used to some point and then it borks, but I really have no idea and so im just making a random guess. I ran memtest86 for a few hours a while ago thinking that it may be bad memory, but that did not seem to be the problem. If you need anymore information, or have questions, or wish me to test anything, PLEASE feel free to contact me, I would really like to see this bug resolved. =) -- Todd Shetter Feb 8 19:49:31 quark kernel: kernel BUG at filemap.c:81! Feb 8 19:49:31 quark kernel: invalid operand: Feb 8 19:49:31 quark kernel: CPU:0 Feb 8 19:49:31 quark kernel: EIP:0010:[]Tainted: P Feb 8 19:49:31 quark kernel: EFLAGS: 00210206 Feb 8 19:49:31 quark kernel: eax: 4000 ebx: c18012f0 ecx: edx: f7f06e60 Feb 8 19:49:31 quark kernel: esi: 0001 edi: f7f06e60 ebp: f3461e9c esp: f3461e98 Feb 8 19:49:31 quark kernel: ds: 0018 es: 0018 ss: 0018 Feb 8 19:49:31 quark kernel: Process hdparm (pid: 2191, stackpage=f3461000) Feb 8 19:49:31 quark kernel: Stack: c18012f0 f3461eb0 c0128c78 f07d0360 c18012f0 47a0 f3461edc c0128d20 Feb 8 19:49:31 quark kernel:c18012f0 f07d0360 47a0 f7f06e60 f7f06e60 eed4ab34 47a0 Feb 8 19:49:31 quark kernel:eed4ab34 f3461f00 c012941e 001f 479f 0020 012a1f16 f7f06de4 Feb 8 19:49:31 quark kernel: Call Trace:[] [] [] [] [] Feb 8 19:49:31 quark kernel: [] [] [] [] [] Feb 8 19:49:31 quark kernel: Feb 8 19:49:31 quark kernel: Code: 0f 0b 51 00 a8 05 2e c0 6a 01 53 e8 ef 7e 00 00 8b 5d fc 89 00:00.0 Host bridge: Intel Corp. 82875P Memory Controller Hub (rev 02) Subsystem: ABIT Computer Corp.: Unknown device 1014 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Latency: 0 Region 0: Memory at e800 (32-bit, prefetchable) [size=128M] Capabilities: [e4] #09 [2106] Capabilities: [a0] AGP version 3.0 Status: RQ=32 Iso- ArqSz=2 Cal=2 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8 Command: RQ=1 ArqSz=0 Cal=2 SBA+ AGP+ GART64- 64bit- FW- Rate=x8 00:01.0 PCI bridge: Intel Corp. 82875P Processor to AGP Controller (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Latency: 64 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: f000-0fff Memory behind bridge: f800-faff Prefetchable memory behind bridge: f000-f7ff BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B- 00:03.0 PCI bridge: Intel Corp. 82875P Processor to PCI to CSA Bridge (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Latency: 32 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: a000-afff Memory behind bridge: fb00-fb0f Prefetchable memory behind bridge: fff0-000f BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- >Reset- FastB2B- 00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to PCI Bridge (rev c2) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- SERR- Latency: 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=32 I/O behind bridge: f000-0fff Memory behind bridge: fff0-000f Prefetchable memory behind bridge: fff0-000f BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- >Reset- FastB2B- 00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 0 00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) Serial ATA 150 Storage Controller (rev 02) (prog-if 8a [Master SecP PriP]) Subsystem: ABIT Computer Corp.: Unknown device 1014 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Latency: 0 Interrupt: pin A routed to IRQ 11 Region 0: I/O ports
2.4.x kernel BUG at filemap.c:81
Running slackware 10 and 10.1, with kernels 2.4.26, 2.4.27, 2.4.28, 2.4.29 with highmem 4GB, and highmem i/o support enabled, I get a system lockup. This happens in both X and console. Happens with and without my Nvidia drivers loaded. I cannot determine what makes this bug present it self besides highmem and high i/o support enabled. Im guessing the system is fine until highmem is actually used to some point and then it borks, but I really have no idea and so im just making a random guess. I ran memtest86 for a few hours a while ago thinking that it may be bad memory, but that did not seem to be the problem. If you need anymore information, or have questions, or wish me to test anything, PLEASE feel free to contact me, I would really like to see this bug resolved. =) -- Todd Shetter Feb 8 19:49:31 quark kernel: kernel BUG at filemap.c:81! Feb 8 19:49:31 quark kernel: invalid operand: Feb 8 19:49:31 quark kernel: CPU:0 Feb 8 19:49:31 quark kernel: EIP:0010:[c01280d1]Tainted: P Feb 8 19:49:31 quark kernel: EFLAGS: 00210206 Feb 8 19:49:31 quark kernel: eax: 4000 ebx: c18012f0 ecx: edx: f7f06e60 Feb 8 19:49:31 quark kernel: esi: 0001 edi: f7f06e60 ebp: f3461e9c esp: f3461e98 Feb 8 19:49:31 quark kernel: ds: 0018 es: 0018 ss: 0018 Feb 8 19:49:31 quark kernel: Process hdparm (pid: 2191, stackpage=f3461000) Feb 8 19:49:31 quark kernel: Stack: c18012f0 f3461eb0 c0128c78 f07d0360 c18012f0 47a0 f3461edc c0128d20 Feb 8 19:49:31 quark kernel:c18012f0 f07d0360 47a0 f7f06e60 f7f06e60 eed4ab34 47a0 Feb 8 19:49:31 quark kernel:eed4ab34 f3461f00 c012941e 001f 479f 0020 012a1f16 f7f06de4 Feb 8 19:49:31 quark kernel: Call Trace:[c0128c78] [c0128d20] [c012941e] [c0129692] [c0129bd0] Feb 8 19:49:31 quark kernel: [c0129d3d] [c0129bd0] [c011af11] [c01384aa] [c0108d23] Feb 8 19:49:31 quark kernel: Feb 8 19:49:31 quark kernel: Code: 0f 0b 51 00 a8 05 2e c0 6a 01 53 e8 ef 7e 00 00 8b 5d fc 89 00:00.0 Host bridge: Intel Corp. 82875P Memory Controller Hub (rev 02) Subsystem: ABIT Computer Corp.: Unknown device 1014 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- Latency: 0 Region 0: Memory at e800 (32-bit, prefetchable) [size=128M] Capabilities: [e4] #09 [2106] Capabilities: [a0] AGP version 3.0 Status: RQ=32 Iso- ArqSz=2 Cal=2 SBA+ ITACoh- GART64- HTrans- 64bit- FW+ AGP3+ Rate=x4,x8 Command: RQ=1 ArqSz=0 Cal=2 SBA+ AGP+ GART64- 64bit- FW- Rate=x8 00:01.0 PCI bridge: Intel Corp. 82875P Processor to AGP Controller (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 64 Bus: primary=00, secondary=01, subordinate=01, sec-latency=32 I/O behind bridge: f000-0fff Memory behind bridge: f800-faff Prefetchable memory behind bridge: f000-f7ff BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- Reset- FastB2B- 00:03.0 PCI bridge: Intel Corp. 82875P Processor to PCI to CSA Bridge (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 32 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: a000-afff Memory behind bridge: fb00-fb0f Prefetchable memory behind bridge: fff0-000f BridgeCtl: Parity- SERR- NoISA+ VGA- MAbort- Reset- FastB2B- 00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB/EB/ER Hub interface to PCI Bridge (rev c2) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Bus: primary=00, secondary=03, subordinate=03, sec-latency=32 I/O behind bridge: f000-0fff Memory behind bridge: fff0-000f Prefetchable memory behind bridge: fff0-000f BridgeCtl: Parity- SERR+ NoISA+ VGA- MAbort- Reset- FastB2B- 00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02) Control: I/O+ Mem+ BusMaster+ SpecCycle+ MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) Serial ATA 150 Storage Controller (rev 02) (prog-if 8a [Master SecP PriP]) Subsystem: ABIT Computer Corp.: Unknown device 1014 Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR
