While printks are useful, if you are using X, it will not be shown on
the terminal unless you specify proper settings. You could alternately
login to a terminal after boot and see those messages. To boot to a
terminal after login, use alt+ctl+Function keys (except F7). You could
also have another machine hooked up with your experiment machine to
using the serial cable to see where it hangs. Please read device drivers
3rd edition debugging chapter for more details on this.
Dinesh
Jesús Velazquez wrote:
Hi,
I'm facing some issues with a device driver, when I try to insert it it
hangs!. I added some printks to debug this issue but as the system hangs
I am not able to execute the dmesg command in order to see the issue. On
the other hand, the /var/log/messages do not display the printks I added
(as KERN_ERR). So, how can I take this situation?. Is there a way to
send all kernel messages (printks) to a serial terminal?. I used the
console=ttyS0 option, but it only shows the boot kernel messages. Where
can I find information about kernel messages system?.
Thanks and regards,
Jesus
--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive: http://mail.nl.linux.org/kernelnewbies/
FAQ: http://kernelnewbies.org/faq/
