On Fri, 2009-11-13 at 09:40 +0100, Steffen Dedekind wrote: > Package: base > Severity: important > > While I performing a test with the database postgresql version 8.4 the kernel hangs up: > > Call Trace: > journal_dirty_data > ext3_journal_dirty_data > walk_page_buffers > journal_dirty_data_fn > ext3_ordered_write_end > generic_file_buffered_write > ext3_mark_inode_dirty > __generic_file_aio_write_nolock > update_queue > generic_file_aio_write > ext3_file_write > do_sync_write > autoremove_wake_function > ..... > > I'm using the Debian 5.0.3 lenny with the 2.6.30-2-amd64 kernel (Netinst) on a Dell server. > In the test mentioned above I provide approx. 250 SQL-Inserts to PostgreSQL for performance testing. > The crashtime varies from 20min after the test starts up to 7 hours. > I tried to get help with some PostreSQL support - so we tested several configurations of PostgreSQL without > any success. It semms there is a Disk i/o problem in the kernel. > Contact me if i should provide some more information. Please use 'reportbug' to follow up to this bug from the affected system, and it will automatically gather information about the system. (It did not do this initially because you did not select the kernel package.) We will also need the full 'oops' messages, so please record them with a serial console, netconsole or a screenshot. Ben. -- Ben Hutchings Unix is many things to many people, but it's never been everything to anybody.
Attachment:
signature.asc
Description: This is a digitally signed message part