Re: DragonFly-2.2.1 installation problem
On Fri, May 8, 2009 at 12:35 AM, Matthew Dillon dil...@apollo.backplane.com wrote: : Basically this solves the problem dealing with USB keyboard. Somehow, : another problem get stuck on me in proceeding the installation. I : encountered this problem 'panic: command is on another queue'. Details : on the panic logs can be seen on the attached JPEG files. I also : provide dmesg log taken from FreeBSD-8.0 CURRENT (successfully : installed on this machine) for reference on the hardware specs. : : Thanks : Archimedes : :Here we go... instead of sending the large image files, I just uploaded it = :here : :http://www.flickr.com/photos/38158...@n03/3510136106/sizes/l/ :http://www.flickr.com/photos/38158...@n03/3510136108/sizes/l/ : :Any idea on the panic problem? : :Thanks, :Archimedes This is really odd. The flags are 0x3 from the picture. Those flags are fine, they shouldn't cause any panic. The flags which cause the panic are: #define AAC_ON_AACQ_MASK ((15)|(16)|(17)|(18)|(110)|(111)) And as you can see a flags value of 0x3 does not match any of those. Did you compile the kernel with any sort of weird optimizations? -Matt Hi, Due to this fix http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/320f7d77741ef115f3893c7a9be4db0909be7d36, I would like to close the aac(4) panic issue. I was now able to install successfully with my IBM x3650. Many thanks to Sascha and Sephe. Archimedes
Hammer error?
Hello, I was doing some backup from Machine0 to Machine1 using hammer mirror-copy and got a suppicious new file called hammer.core. Looking around the files it looks like a success copy but i still curious about this new 720kb file. Someone can tell me if i need to worry about it and where can i start checking for errors in case there was one? Machine0 has DFBSD2.2.0-release, Machine1 has DFBSD2.2.1-release, could it be the problem? should i just upgrade both? Sdav -- Sdävtaker prays to Rikku goddess for a good treasure.
Re: Hammer error?
Sdävtaker wrote: Hello, I was doing some backup from Machine0 to Machine1 using hammer mirror-copy and got a suppicious new file called hammer.core. Looking around the files it looks like a success copy but i still curious about this new 720kb file. Someone can tell me if i need to worry about it and where can i start checking for errors in case there was one? Machine0 has DFBSD2.2.0-release, Machine1 has DFBSD2.2.1-release, could it be the problem? should i just upgrade both? Sdav ISTR *several* places where 'tis said hammer really needs to be 'matched' As you've got 2.0 and skipped 2.1 for 2.2.1, I'd suggest having the odd core dump is b***dy lucky. An upgrade will probably deliver more immediate 'treasure' than Rikku has time or inclination to bless you with... ;-) Bill
pkgsrc bulk build question
Hi, is anyone using the bulk build script mk/bulk/build successfully on DragonFly? After setting up a chroot environment and bootstrapping I can manually build packages, but sh mk/bulk/build gives me (after a while): Complete dependency database left in /usr/pkgsrc/.bulk_db Appending to database in /usr/pkgsrc/.bulk_db bmake: don't know how to make print-summary-data. Stop *** Error code 1 Stop. bmake: stopped in /usr/pkgsrc mk/bulk/build: error: Could not create the bulk build cache. Any ideas? Regards, Johannes PS: Are there any prebuilt Q12009 packages available?
Re: pkgsrc bulk build question
Johannes Hofmann wrote: Hi, is anyone using the bulk build script mk/bulk/build successfully on DragonFly? [...] Any ideas? I suggest you use the new method of doing bulk builds - pbulk. It's a package available at /usr/pkgsrc/pkgtools/pbulk. Some documentation on how to use: 1. http://www.dragonflybsd.org/docs/developer/PbulkBuilding/ 2. /usr/pkgsrc/doc/HOWTO-pbulk 3. http://wiki.netbsd.se/pbulk-HOWTO
Re: Hammer error?
:Hello, :I was doing some backup from Machine0 to Machine1 using hammer :mirror-copy and got a suppicious new file called hammer.core. :Looking around the files it looks like a success copy but i still :curious about this new 720kb file. :Someone can tell me if i need to worry about it and where can i start :checking for errors in case there was one? :Machine0 has DFBSD2.2.0-release, Machine1 has DFBSD2.2.1-release, :could it be the problem? should i just upgrade both? :Sdav A hammer.core could only come from the hammer utility core dumping. This wouldn't be a filesystem error but it certainly indicates a bug somewhere in the hammer utility. If you haven't updated the sources relative to when the core was generated you can recompile the hammer utility with DEBUG_FLAGS=-g and then gdb the binary and core file and get a backtrace to see where it died. If you have updated the sources since then you'd have to wait for a new core file to be generated for a newly debug-compiled hammer utility to match the core file. cd /usr/src/sbin/hammer make clean make obj make DEBUG_FLAGS=-g all install ... gdb /sbin/hammer hammer.core ... gdb back -Matt Matthew Dillon dil...@backplane.com
