search for: stack_dump

This is the first attempt to try this program, StreetSmart Pro. I'm running on a Fedora 8 64 bit system using wine-1.1.9-2.fc8 and mono-2.2-gtksharp-2.12.7-win32-5.exe. When I try running the program I get the attached stack_dump.txt: [dhighley at douglas SSPro]$ wine SSPro.exe -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: stack_dump.txt Url: http://www.winehq.org/pipermail/wine-users/attachments/20090117/d0fc02a9/attachment.txt

Hello. On a server running 2.4.25, I have the two following errors in the kernel logfile: Unexpected dirty buffer encountered at do_get_write_access:618 (08:11 blocknr 920707) Unexpected dirty buffer encountered at do_get_write_access:618 (08:11 blocknr 920707) Should I worry about them (disk failure, filesystem damage) ? Thanks. As an addition what does the pair '08:11' means ? Is

...matchmail.com> writes: > >> > >>>Nicolas Kowalski wrote: > >>> > >>>>I will try to reproduce these errors on a non-production server now. > >>> > >>>Beautiful. > >>> > >>>It might be good if you put a stack_dump() call just after the > >>>printk() call in the ext3 source. > >> I apologize, (I am not familiar with kernel debugging), but when > >> compiling the kernel with this call inserted after the printk in the > >> sources, it fails with an resolved symbol error. ....