Re: testig request for your code..
On Mon, 17 Sep 2001, Julian Elischer wrote: If you find a module that worked in a kernel from before September 11 but does not work on -current, please let [EMAIL PROTECTED] know. NTFS was working correctly in a kernel from sometime in August, it now fails with an easily reproducable panic about locks. Unfortunately, I never wrote down the trace since I was planning on using gdb -k to debug it.. but: # gdb -k kernel.6 vmcore.6 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-freebsd... (no debugging symbols found)... IdlePTD 4620288 initial pcb at 370340 panicstr: bremfree: bp 0xc8977ba0 not locked panic messages: --- panic: lockmgr: pid 943, not exclusive lock holder 942 unlocking dumping to dev ad0s4b, offset 584197 dump ata0: resetting devices .. done 256 [snip] 1 --- Bus error (core dumped) So, I guess I'll need to copy it down by hand next time I'm prepared to crash my system.. (A simple cd /mnt/w2k/; ls; crashes the box. Oddly enough, it didn't seem to have the same effect in single-user mode, not sure why...) -- David Taylor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: testig request for your code..
If you can try a kernel from JUST before the KSE integration.. that migh talso be a good test.. On Tue, 18 Sep 2001, David Taylor wrote: On Mon, 17 Sep 2001, Julian Elischer wrote: If you find a module that worked in a kernel from before September 11 but does not work on -current, please let [EMAIL PROTECTED] know. NTFS was working correctly in a kernel from sometime in August, it now fails with an easily reproducable panic about locks. Unfortunately, I never wrote down the trace since I was planning on using gdb -k to debug it.. but: # gdb -k kernel.6 vmcore.6 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type show copying to see the conditions. There is absolutely no warranty for GDB. Type show warranty for details. This GDB was configured as i386-unknown-freebsd... (no debugging symbols found)... IdlePTD 4620288 initial pcb at 370340 panicstr: bremfree: bp 0xc8977ba0 not locked panic messages: --- panic: lockmgr: pid 943, not exclusive lock holder 942 unlocking dumping to dev ad0s4b, offset 584197 dump ata0: resetting devices .. done 256 [snip] 1 --- Bus error (core dumped) So, I guess I'll need to copy it down by hand next time I'm prepared to crash my system.. (A simple cd /mnt/w2k/; ls; crashes the box. Oddly enough, it didn't seem to have the same effect in single-user mode, not sure why...) -- David Taylor [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
Re: testig request for your code..
On Tue, 18 Sep 2001, Julian Elischer wrote: If you can try a kernel from JUST before the KSE integration.. that migh talso be a good test.. A kernel from cvs up -D2001-09-10 works perfectly, A kernel from after the KSE milestone 2 produces various panics like the following: (find .; running on ntfs partition) | (sleep; god knows where) | ( it came from ) vv panic: lockmgr: pid 30856, not exclusive lock holder 30814 unlocking. backtrace: panic lockmgr vop_stdunlock ntfs_inactive vput lstat Unfortunately, gdb -k kernel.X vmcore.X is still coring on startup, so I can't get any more info, unless someone has something they want me to do at the DDB prompt. -- David Taylor [EMAIL PROTECTED] PGP signature
testig request for your code..
As many FreeBSD users know, a large set of changes was committed to -current recently, as part of the development of real threading support. Most parts of the kernel were changed to a greater or lesser extent. Some parts have not been able to be tested fully however. If you have a section of the kernel, that you use, but otherwise might not often test (e.g. CODA or a special driver) it may be a good time to compile up a -current kernel and see if it still works. There have been few problems but it will be easier to catch these things right now than to try find problems further down the track. If you find a module that worked in a kernel from before September 11 but does not work on -current, please let [EMAIL PROTECTED] know. To Unsubscribe: send mail to [EMAIL PROTECTED] with unsubscribe freebsd-current in the body of the message
