When I connect to the internal usb port, i find the following error msg in dmesg :
usb 3-2: device descriptor read/all, error -71
Is this benign, can i ignore?
The message doesnot appear when I connect to the external ports.
googling pointed me to this [URL]
AT the moment the stick is being detected and all works. But still confused as to whether I have a serious problem that may lead to the usb stick going missing or hanging at some point or is this error msg just a spurious one that I can safely ignore?
I am new here and have only been using Linux for about 3 months so please help by explaining things clearly and don't assume I should know. However, for reasons too detailed to mention here I want to know how dmesg works. What I understand is that it provides log details of the startup, hardware etc until logger takes over. What I want to know is this: Do you still get new log messages in dmesg after boot and after the logger has taken over or is it simply a snapshot of what happens at boot time If you shutdown you machine or more importantly something happens to cause it to crash, does it or is it possible to make it record dmesg logs or is it purly a function of boot up
I run F15 on my desktop PC and /var/log/dmesg is not being updated. I used preupgrade to upgrade from F14 to F15 on June 3. I boot F15 at least once per day. /var/log/dmesg has not been updated since June 3. /var/log/dmesg was being updated correctly when I ran F14. On f15, if I issue "dmesg" from the command line, I get the expected result. Is this a bug?
When I run dmesg I get Code: [drm:drm_mode_rmfb] *ERROR* tried to remove a fb that we didn't own Does anyone have any idea what that means? Fedora 12 Gnome 2.28
I have enabled usb storage debug prints for the debugging of my driver in kernel 2.6.24.4 of Fedora 8. When I type dmesg and press enter I see many prints on the screen. There are however lot many prints and I want all those prints from the beginning. However it seems that the older prints are overwritten with newer prints. SO if just redirect the dmesg output to some file, I get only newest prints but older are lost.
Surprisingly /var/log/messages doesn't contain those prints! Also I see there is a file named /var/log/dmesg , but that files never gets updated with the prints I see on the screen. So, my question is can I get all those dmesg prints right from the beginning in a file somewhere?
I have two servers. One in production (lets call it the OLD ONE) and the other (lets call it the NEW ONE) in tests to replace the OLD ONE.This is the basic hardware of each one: (I can post more detailed info if you need, but beside the erros on dmesg, look at the the L2 cache of the NEW ONE )
Old one: 2 quad core processors that linux recognize as 8 x Intel(R) Xeon(R) CPU E5440 @ 2.83GHz - 32Kb L1 - 6Mb L2 48Gb RAM
New one: 8 quad core processor that linux recognize as 32 x AMD Opteron(tm) Processor 6136 @ 2.400Mhz (- 64Kb L1 - 512Kb L2 128Gb RAM
The scenario:We run a dataflex system on the old one, with average of 3000 users, with tops at 3300 users and sometimes less then 2000. In the old one, we have a load average from 2 to 6 with the 3000 users, depending on the type of application (sometimes we run reports to txt files that take more then 6 hours to complete and the load average can raise to 12). 85% of this conections are from remote links. Dataflex is a language that derives from C that have their own sgbd (if we can call it that way), and have a limit of 2gb per table. This size we almost have on 5 tables and we use a dataflex feature to compress the data.
The problem:We are migrating (or trying to) the tables to oracle, so we bought new machines for the DB and the new one to replace the old one, becouse we think that could not handle the job with 2 oracles (load balance).In some tests we could see (or suposed) that the oracle database was not so fast with more then 1000 users (opening same table and doing the same task) and we decided to test the new one with the system that is in production right now, with dataflex tables, to ensure that the problem could be oracle.We change the HDs and IP. Started the system on the new one, and started to monitorate as the real users start their jobs. At 800 users the Load Average raised to 26 and with 1300 users we had more then 115 on Load Average. More users login in and the TOP become slow, pointing 400 of LA. From here we started to get some "Lock time out" erros and we had to change to the old one again, to prevent corruption on the tables. I'm analizing all report tools I know about performance and hardware and I cant see nothing. I saw some errors on dmesg, but I can say that is related to that problem.
had upgraded from slackware 13 to 13.1 and finally 13.37.After this I noticed that 'dmesg' could only be executed as root. So inorder for a user to execute 'dmesg' I executed 'ln -s /bin/dmesg /usr/bin/dmesg'.What happened next is the symlink was created but the dmesg executable was deleted.I do not want to reinstall the OS (very time consuming on a P3 with 512MB RAM) so I want to know which package provides dmesg so that I can reinstall it.The dmesg man page indicated that klogd will provide the package but then when I reinstalled it it was a no go.
REASON: I want to find out how to improve my boot-up and hibernate-awake time for ubuntu (it is 300% slower as hibernate on windows xp on the same machine)
QUESTION: well my question is concerning the tool dmesg. As I understood from reading the quite brief >>man dmesg this tool will show the messages the kernel put out during the boot-up. true? A typical line on my dmesg output I receive would look like this:
Code: [...] [ 39.632219] i915 0000:00:02.0: LVDS-1: EDID invalid. [ 46.964733] wlan0: authenticate with AP 00:23:08:20:58:6f [ 46.965988] wlan0: authenticated
subquestion:
a) the number in the beginning (is it the time between the two kernel messages?) in the example it wold be about 7 seconds
b) if it is the time in seconds: does it mean the kernel was abusing 7 dseconds for the output of the line? how can I track what causes the delays?
PS: maybe I should post this in a different ubuntuforums subgroup (if so which?) PSS: is there any good webpage (I have not found any yet) on this topic?
I have been having some problems with a mouse on my system (amd64 variant).The problem has exhibited both with Karmic and Lucid, even after a clean install of Lucid. have a logictech wireless keyboard and mouse combo. After some time, the mouse just randomlyeezes, although the keyboard is still responsive.I plugged in a second USB (standalone) mouse.It initially worked, but after some time, it also freezes. I attempted to unplug the frozensecond mouse and place into another USB port. When I did, the red light on the bottom of the mouse failed to light up. I then attempted to plug in a third mouse, and it failed to show the light as well.When ssh'ing from another box, I get the following from dmesg:
Code: [79275.300031] usb 4-1: new low speed USB device using ohci_hcd and address 2 [79275.524106] usb 4-1: configuration #1 chosen from 1 choice
I would like to find where logs form dmesg(command) are stored on my hdd drive. I'm testing broken hdd with badsectors, and I've got some i/o errors, that I can read (just the most recent) using dmesg command (dmesg buffer). I would like to see whole log, that is interesting for me, but I cannot find where it is stored in /var/log
dmesg command(buffer) (last few lines) Code: [245129.080558] end_request: I/O error, dev sdb, sector 218246624 [245129.080562] Buffer I/O error on device sdb, logical block 27280828 [245132.037921] sd 2:0:0:0: [sdb] Unhandled sense code [245132.037925] sd 2:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [245132.037928] sd 2:0:0:0: [sdb] Sense Key : Medium Error [current] [245132.037932] sd 2:0:0:0: [sdb] Add. Sense: Unrecovered read error [245132.037936] end_request: I/O error, dev sdb, sector 218246624 [245132.037940] Buffer I/O error on device sdb, logical block 27280828 .....
I've been getting messages, that should be in the dmesg log, on the console.This has been happening for a while, but I finally got tired of them.My system is Fedora release 14, Kernel 2.6.35.11-83 on an x86_64.When I reboot I get the following displayed with the login prompt.[ 52.492937] readahead-collector: starting delayed service auditd[ 52.795508] readahead-collector: sorting[ 53.033970] readahead-collector: finished
I have a gentoo distribution and need to store the information of dmesg collected until a system crash. At present, after a reboot or a crash the information in dmesg are lost and are not available at the next reboot. How can I save all the information in dmesg until a crash and read them after the succeed reboot?I also checked for dmesg.x files in /var/log or similar files but with no success.
Occaisonally I use 'dmesg' to see what's happening with my system. Lately I've noticed something that I've never seen before: the output from dmesg is polluted with logs of network packets. At the moment, the output of 'dmesg' looks like this:
I recently assembled a new computer so that all hardware is pretty new. Since then I've been experiencing some problem with IRQs when running Debian 6.0. On random occasions, usually after an hour or so of running I hear a beep and this shows up in dmesg:
I scan dmesg continuously for warning or fatal messages and mail the lines containing the errors to someone.- I presume a script can be used.- How can this process involked at system startup ?
It started when I tried to install Kubuntu 10.10. It booted OK from the CD, but after I installed it, it wouldn't boot. It would hang showing "floppy: no floppy found". I think the next part is either initializing swap or disks. No matter what, I couldn't it to boot.
So, I installed with Xubuntu. it worked great, and booted fine a few times. Worked a couple days.
But just today, after updating to the new kernel, it won't boot at all. It gets stuck at the same place!
It does this even if I go back to the old kernel on the boot list.
When I boot into recovery mode, SOMETIMES it will boot. Actually, just once. All other times, it failed to boot even in recovery. I attached the dmesg from one of these boots.
I booted into a puppy partition, and fsck -f my other partitions. It reported no problems.
Could it be a hard drive problem? I don't hear anything from the drive, but it's getting old and I was planning on replacing it soon anyhow.
My computer is a Compaq R3000 AMD64, but I'm running the 32 bit OS.
Kernel driver function was called via ioctl and returned success, but when I checked the kernel display buffer with dmesg the printk message was not there. Then when you do lsmod, the driver you were calling showed "used by zero". So it seems like the kernel driver was not accessed. In the kernel driver, I had many printk statements, but nothing printed in the buffer. if the driver get accessed and what could cause this?
It's been a while but I just hit a brick wall. Well, this has been building for a week or so, I can't figure out what's causing it. I thought there was a sudden conflich with the bluetooth dongle, since that one piece of hardware is not listed right from boot (sometimes has a dmesg error related to loading the module), but I find now this is not the case. Today I ran the full update to the current kernel hoping to fix the problem, but to no avail (caused some interesting issued with the video (intel 945) which I ironed out). Symptom: With the exception of the bluetooth, all devices hooked up to the USB ports at boot are recognized and usable. No device that I plug in after booting is recognized, period. lsusb output does not change. Plugging in a USB flash drive produces no output for dmesg.
I have a Dell Inspiron E4300 provided to me by my employer. I have installed CentOS 5 without much of a problem. The only issue is the wifi isn't working (doh!). I've had much experience with this kind of thing in the past (FreeBSD/ndiswrapper) with successes. Here are some details:
[Code]...
The device does not appear in dmesg :(I have installed ndiswrapper (dkms-ndiswrapper and ndisgtk from RPMForge) and provided it with the correct Windows XP driver. It has installed the driver and ndisgtk tells me that the hardware is present.
I just installed CentOS 5.2 on a Dell Studio XPS 435 MT, which is a fairly new machine (Intel Core i7) and I'm having trouble getting networking working. The word "network" doesn't appear anywhere in the dmesg output, so I can't even tell what hardware my machine has, or what drivers are missing. How do I tackle this?
