Richard Arends
2004-Nov-08 06:54 UTC
READ_DMA interrupt error after upgrading to 5.3 STABLE
Hello, On my laptop i am running 5.2.1-RELEASE-p11. A few weeks ago i upgraded it to 5.3 BETA7. After building world i went to single user mode, to complete the upgrade. After a few seconds running in single user mode, i got errors about READ_DMA and my laptop was completly frozen. At that time i realy wanted a working laptop, so i checked out the 5.2.1 source and rebuilded it. This morning i had some time over and checked out 5.3 STABLE and when i got in single user mode, my laptop froze without any message. After that i booted it (with the new kernel) in multi user mode and got the following message: ad0: WARNING - READ_DMA interrupt was seen but timeout fired LBA = 351 After some Googling, i found this page: http://lists.freebsd.org/pipermail/freebsd-current/2004-August/035984.html I did not try the solution mentioned in the above message, because that would mean i always have to do that when i'm updating my source tree. My laptop: Compaq Evo N620c Using GENERIC kernel file (always) atapci0: <Intel ICH4 UDMA100 controller> port 0x3c20-0x3c2f,0-0x3,0-0x7,0-0x3,0-0x7 irq 10 at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] GEOM: create disk ad0 dp=0xc2e11960 ad0: 38154MB <HTS548040M9AT00> [77520/16/63] at ata0-master UDMA100 Is there a solution, or something (else) i could try? -- Regards, Richard.
Richard Arends
2004-Nov-08 07:54 UTC
READ_DMA interrupt error after upgrading to 5.3 STABLE
On Mon, Nov 08, 2004 at 03:54:45PM +0100, Richard Arends wrote: Hello,> ad0: WARNING - READ_DMA interrupt was seen but timeout fired LBA = 351Okay, replaying to my own message, but i found a workaround. If i set at bootime hw.ata.ata_dma to 0, i can boot the 5.3 STABLE kernel and even start X. It ran in that state for a few minutes and then i booted it back to my old kernel. Is there an other solution than turning off DMA ? -- Regards, Richard.
Richard Arends
2004-Nov-09 02:43 UTC
READ_DMA interrupt error after upgrading to 5.3 STABLE
On Mon, Nov 08, 2004 at 03:54:45PM +0100, Richard Arends wrote: Again replying to my own message :(> On my laptop i am running 5.2.1-RELEASE-p11. A few weeks ago i upgraded > it to 5.3 BETA7. After building world i went to single user mode, to > complete the upgrade. After a few seconds running in single user mode, > i got errors about READ_DMA and my laptop was completly frozen. > > ad0: WARNING - READ_DMA interrupt was seen but timeout fired LBA = 351This morning i again tried to update to 5.3 STABLE from 5.2.1. After the makeworld i booted in single user mode with "hw.ata.ata_dma=0". Then after running fsck -p for a few minutes, the disk led goed off and i get the following message and can not do anything anymore. ad0: WARNING - READ_MUL interrupt was seen but timeout fired LBA = 15144507 Can anybody shed some light on this??? -- Regards, Richard.