On Fri, Mar 26, 2010 at 3:36 AM, Nick Holland <[email protected]> wrote: > Andreas Gerdd wrote: >> Hello. >> >> I've an Intel E6300 Dual Core 2.8 system. >> >> Whenever I try to see such a dmesg output, I get the following: >> >> # dmesg -N /bsd.sp >> dmesg: pread: Bad address >> dmesg: kvm_read: invalid address (0) (0) >> >> However, typing just "dmesg" works fine, shows the output for GENERIC.MP, >> but i try to see a dmesg output for the GENERIC kernel as well, >> so i can send them both to [email protected] > > dmesg is a property of a running kernel, not of a kernel sitting on > the disk. If you are running snapshot or release kernels, we know > what is in your kernel file, we want to see how it works with your > hardware (of course, we also want to see the first few lines which > show us what version you are running). > > So, to get a dmesg from GENERIC.MP, you run bsd.mp, for GENERIC, you > run bsd. You can't pull a dmesg out of a kernel that wasn't run [...]
If I'm reading this correctly, what you are saying is the -N option to dmesg can be considered to a bug? --patrick
