Re: libfreetype.a: Bad address -- hard error reading
On Fri, 12 Mar 2004 09:59:17 +1100 (EST) eodyna [EMAIL PROTECTED] wrote: Greetings all, Due to yesterday error on 4.9-RELEASE of FreeBSD. snip hard error reading fsbn ad0: DMA problem fallback to PIO mode libfreetype.a: Bad address /snip The two are completely unrelated. For the first what you say below could be a solution, if set them to 0; (an 5.x I would add that also acpi and apic could count) For the second you have to provide more details. hard error reading fsbn ad0: DMA problem fallback to PIO mode However this usually suggest hw trouble. -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libfreetype.a: Bad address -- hard error reading
Hello, Thanks for your response. I dont think they are totally unrelated, because when i try to install XFree86-4 and that particular library it gets the error messages stated below (one to stdout and the other to dmesg). All other port installations work fine. (Before and after the XFree86-4 install) I orginally thought it was a hardware problem as well. but to have it fail on two disks with the same sort of error? that is highly unlikely, and installing 4.8-RELEASE yeilds no errors. fsck doesn't produce any errors either. And i dont think it is a ports problem because XFree86-4.3.0,1 works on 4.8-RELEASE. So this has left me thinking its either a bios thingy or something in 4.9-RELEASE kernel that doesn't like my laptop. or maybe i jump to too many conculsions? Hence why i would like some advice on how to trouble shoot this. thanks again This is the post from yesterday with the main error msg: large snip further more, when i look in dmesg i get the following: ad0s1g: hard error reading fsbn 17696655 of 7946848-7946879 (ad0s1 bn 17696655; cn 18726 tn 9 sn 18) trying PIO mode ad0: DMA problem fallback to PIO mode ad0s1g: hard error reading fsbn 17696671 of 7946848-7946879 (ad0s1 bn 17696671; cn 18726 tn 9 sn 34) status=59 error=40 ad0s1g: hard error reading fsbn 17696671 of 7946848-7946879 (ad0s1 bn 17696671; cn 18726 tn 9 sn 34) status=59 error=40 vm_fault: pager read error, pid 418 (install) Ive taken out the harddrive and replaced it with a different one and i still see the same sort of error message ive also tried running fsck, but it yields no errors. I have gone to install XFree86-4 and get the following error installing in lib/font/Speedo... installing in lib/font/Speedo/module... /usr/bin/install -c -m 0444 libspeedo.a /usr/X11R6/lib/modules/fonts install in lib/font/Speedo/module done installing in lib/font/Type1... installing in lib/font/Type1/module... /usr/bin/install -c -m 0444 libtype1.a /usr/X11R6/lib/modules/fonts install in lib/font/Type1/module done installing in lib/font/FreeType... installing in lib/font/FreeType/module... /usr/bin/install -c -m 0444 libfreetype.a /usr/X11R6/lib/modules/fonts install: /usr/X11R6/lib/modules/fonts/libfreetype.a: Bad address *** Error code 71 Stop in /usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/font/FreeType/module. *** Error code 1 Stop in /usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/font/FreeType. *** Error code 1 Stop in /usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/font. *** Error code 1 Stop in /usr/ports/x11-servers/XFree86-4-Server. *** Error code 1 Stop in /usr/ports/x11/XFree86-4. /snip Ive tried looking for libfreetype.a and it does exist in /usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/font/FreeType/module. -rw-r--r-- 1 root wheel 281366 Mar 10 23:22 libfreetype.a I have also tried to install it manually /usr/bin/install -c -m 0444 /usr/ports/x11-servers/XFree86-4-Server/work/xc/lib/font/FreeType/module/libfreetype.a /usr/X11R6/lib/modules/fonts and i get the same error install: /usr/X11R6/lib/modules/fonts/libfreetype.a: Bad address /snip --- Ion-Mihai Tetcu [EMAIL PROTECTED] wrote: On Fri, 12 Mar 2004 09:59:17 +1100 (EST) eodyna [EMAIL PROTECTED] wrote: Greetings all, Due to yesterday error on 4.9-RELEASE of FreeBSD. snip hard error reading fsbn ad0: DMA problem fallback to PIO mode libfreetype.a: Bad address /snip The two are completely unrelated. For the first what you say below could be a solution, if set them to 0; (an 5.x I would add that also acpi and apic could count) For the second you have to provide more details. hard error reading fsbn ad0: DMA problem fallback to PIO mode However this usually suggest hw trouble. -- IOnut Unregistered ;) FreeBSD user Find local movie times and trailers on Yahoo! Movies. http://au.movies.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libfreetype.a: Bad address -- hard error reading
[ please don't post on top, it's hard to read ] On Fri, 12 Mar 2004 11:33:08 +1100 (EST) eodyna [EMAIL PROTECTED] wrote: Hello, Thanks for your response. I dont think they are totally unrelated, because when i try to install XFree86-4 and that particular library it gets the error messages stated below (one to stdout and the other to dmesg). All other port installations work fine. (Before and after the XFree86-4 install) I orginally thought it was a hardware problem as well. but to have it fail on two disks with the same sort of error? that is highly unlikely, and installing 4.8-RELEASE yeilds no errors. fsck doesn't produce any errors either. And i dont think it is a ports problem because XFree86-4.3.0,1 works on 4.8-RELEASE. So this has left me thinking its either a bios thingy or something in 4.9-RELEASE kernel that doesn't like my laptop. This happen when an error is detected by the disk driver. This can be caused by hardware failure or incompatibility, or a driver bug. You get a vm_fault if the kernel is trying to page in a block of memory for a process but it can't. You probably get this instead of a regular read error because AFAIR cp and install uses mmap() on files smaller than 8 MB. Since you changed the HDD it's probably a driver bug. However I would be curios if you get the always the same fsbn numbers. I would be very strange. Stage also is that it's failing on the same file. or maybe i jump to too many conculsions? Hence why i would like some advice on how to trouble shoot this. Aside from posting this + boot -v on mobile, I don't know. This is the post from yesterday with the main error msg: missed that, sorry. -- IOnut Unregistered ;) FreeBSD user ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: libfreetype.a: Bad address -- hard error reading
i forgot to include the mailing list. doh! --- Ion-Mihai Tetcu [EMAIL PROTECTED] wrote: [ please don't post on top, it's hard to read ] sorry :/ Hello, Thanks for your response. I dont think they are totally unrelated, because when i try to install XFree86-4 and that particular library it gets the error messages stated below (one to stdout and the other to dmesg). All other port installations work fine. (Before and after the XFree86-4 install) I orginally thought it was a hardware problem as well. but to have it fail on two disks with the same sort of error? that is highly unlikely, and installing 4.8-RELEASE yeilds no errors. fsck doesn't produce any errors either. And i dont think it is a ports problem because XFree86-4.3.0,1 works on 4.8-RELEASE. So this has left me thinking its either a bios thingy or something in 4.9-RELEASE kernel that doesn't like my laptop. This happen when an error is detected by the disk driver. This can be caused by hardware failure or incompatibility, or a driver bug. You get a vm_fault if the kernel is trying to page in a block of memory for a process but it can't. You probably get this instead of a regular read error because AFAIR cp and install uses mmap() on files smaller than 8 MB. Since you changed the HDD it's probably a driver bug. Oh. um this is a silly question, but how do i know which driver it is? However I would be curios if you get the always the same fsbn numbers. I would be very strange. Stage also is that it's failing on the same file. i cannot remember if its the same fsbn numbers or not. i didn't keep a log. or maybe i jump to too many conculsions? Hence why i would like some advice on how to trouble shoot this. Aside from posting this + boot -v on mobile, I don't know. well my thanks anyway for your help thus far. This is the post from yesterday with the main error msg: missed that, sorry. thats ok these things happen :D i am very grateful that you have taken the time to answer my post. :) Find local movie times and trailers on Yahoo! Movies. http://au.movies.yahoo.com Find local movie times and trailers on Yahoo! Movies. http://au.movies.yahoo.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
