Re: 2.4.x kernel BUG at filemap.c:81

[Todd Shetter]

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: 0000
> > > > > > 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 yet....Again, 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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/