System logging and kernel bugs
2 participantes
Página 1 de 1.
System logging and kernel bugs
Keltek Dom Ene 02, 2011 12:06 am
Hi all,
I start this thread because the user jpg12305 opens the discussion about logging the all messages. I have started the syslog daemon on my notebook with Windows (using the Cygwin binaries) allowing the remote logging. Now I capture the logging events.
1) Start the syslog daemon on LG which sends all events to my host
2) Start the syslogd daemon your machine (Linux or Windows with Cygwin)
Under Linux just enable the remote logging in configuration file of your favorite syslog daemon. If you use generic syslogd daemon, it can be started/setup-ed like the syslogd in Cygwin.
Configuration is in /etc/syslog.conf where should be
To start daemon issue command
The default syslogd in Cygwin is little weird (events appear in log file with extending delay) so I try to use the "syslog-ng" and is a far better.
In configuration just un-comment UDP logging interface or use this:
Now you can monitor you file by
I start this thread because the user jpg12305 opens the discussion about logging the all messages. I have started the syslog daemon on my notebook with Windows (using the Cygwin binaries) allowing the remote logging. Now I capture the logging events.
1) Start the syslog daemon on LG which sends all events to my host
- Código:
klogd
sysklog -R [ip of your notebook or desktop machine]
2) Start the syslogd daemon your machine (Linux or Windows with Cygwin)
Under Linux just enable the remote logging in configuration file of your favorite syslog daemon. If you use generic syslogd daemon, it can be started/setup-ed like the syslogd in Cygwin.
Configuration is in /etc/syslog.conf where should be
- Código:
*.* /var/log/messages
To start daemon issue command
- Código:
syslogd -r
The default syslogd in Cygwin is little weird (events appear in log file with extending delay) so I try to use the "syslog-ng" and is a far better.
In configuration just un-comment UDP logging interface or use this:
- Código:
source s_network {
udp();
};
log {
...
source(s_network);
...
};
Now you can monitor you file by
- Código:
tail -f /var/log/messages
Última edición por Keltek el Lun Ene 03, 2011 3:54 pm, editado 1 vez
Keltek- Mensajes : 291
Fecha de inscripción : 10/03/2010
Edad : 47
Localización : Praha - Czech Republic -
Kerel oops: pluging the USB
Keltek Dom Ene 02, 2011 12:17 am
I catch the first oops while I plug the USB disk (500MB WD Passport).
As you can see there is a SIGSEGV sending to USB which makes the kernel panic and reboot in 60 seconds. The "page_fault" means the problem with memory. I have running the rtorrent with snatching about 13GB file which makes the memory heavily under load so there can be a memory problem.
Maybe we can prepare command in the rcS which start the remote logging to catch the reboot-loop issue.
- Código:
Jan 1 21:08:39 LG400 kernel: usb 1-2: new high speed USB device using ehci_hcd and address 4
Jan 1 21:08:39 192.168.1.12 kernel: scsi4 : SCSI emulation for USB Mass Storage devices
Jan 1 21:08:39 192.168.1.12 kernel: usb-storage: device found at 4
Jan 1 21:08:39 192.168.1.12 kernel: usb-storage: waiting for device to settle before scanning
Jan 1 21:08:39 192.168.1.12 kernel: Hotplug got one USB Hotplug of "Add" from port "2".^M
Jan 1 21:08:39 192.168.1.12 kernel: do_page_fault() #2: sending SIGSEGV to USB for invalid read access from
Jan 1 21:08:39 192.168.1.12 kernel: 0000003c (epc == 00d8507c, ra == 00d85078)
Jan 1 21:08:39 192.168.1.12 kernel: current context: 16c
Jan 1 21:08:39 192.168.1.12 kernel: dvr_asid: 0x6c
Jan 1 21:08:39 192.168.1.12 kernel: ########## User stack address: 8e67b000
Jan 1 21:08:39 192.168.1.12 kernel: Page flags: 21000078, index: 512511, count: 0, mapcount: 0
Jan 1 21:08:39 192.168.1.12 kernel: sending signal: 11
Jan 1 21:08:39 192.168.1.12 kernel: Call Trace:
Jan 1 21:08:39 LG400 kernel: [<80149344>] force_sig_info+0x54/0x17c
Jan 1 21:08:39 LG400 kernel: [<8011a348>] do_page_fault+0x3b8/0x450
Jan 1 21:08:39 LG400 kernel: [<8011a10c>] do_page_fault+0x17c/0x450
Jan 1 21:08:39 LG400 kernel: [<801fd18c>] sysfs_dir_close+0x224/0x248
Jan 1 21:08:39 LG400 kernel: [<801ce808>] dput+0x2c/0x34c
Jan 1 21:08:39 LG400 kernel: [<801a537c>] __fput+0x2dc/0x3ec
Jan 1 21:08:39 LG400 kernel: [<801a5108>] __fput+0x68/0x3ec
Jan 1 21:08:39 LG400 kernel: [<801c97c8>] sys_getdents64+0x2b8/0x2f0
Jan 1 21:08:39 LG400 kernel: [<801c96b8>] sys_getdents64+0x1a8/0x2f0
Jan 1 21:08:39 LG400 kernel: [<801128b8>] _sys_rt_sigsuspend+0x13c/0x158
Jan 1 21:08:39 LG400 kernel: [<8011a900>] tlb_do_page_fault_0+0x100/0x108
Jan 1 21:08:39 LG400 kernel: [<80117b00>] stack_done+0x20/0x3c
Jan 1 21:08:40 LG400 kernel: clear pli setting....
Jan 1 21:08:40 LG400 kernel: ***256MB version...
Jan 1 21:08:40 LG400 kernel: Memory address 0x40000000
Jan 1 21:08:40 LG400 kernel: umount: can't umount /usr/local/etc: Device or resource busy^M
Jan 1 21:08:40 LG400 kernel: mount: mounting /dev/mtdblock/2 on /usr/local/etc failed: Device or resource busy^M
As you can see there is a SIGSEGV sending to USB which makes the kernel panic and reboot in 60 seconds. The "page_fault" means the problem with memory. I have running the rtorrent with snatching about 13GB file which makes the memory heavily under load so there can be a memory problem.
Maybe we can prepare command in the rcS which start the remote logging to catch the reboot-loop issue.
Keltek- Mensajes : 291
Fecha de inscripción : 10/03/2010
Edad : 47
Localización : Praha - Czech Republic -
Re: System logging and kernel bugs
vic1972 Dom Ene 02, 2011 6:01 pm
wow, this is very interesing, thans for the investigation.
as soon as i return home, i will give a try.
as soon as i return home, i will give a try.
vic1972- Mensajes : 2260
Fecha de inscripción : 09/12/2009
Edad : 52
Localización : Malaga
Frequent logs - Xfer fail - TXABORT
Keltek Miér Ene 05, 2011 3:36 am
You can find following events in log
It means there cannot be HDMI communication. (I turn off the TV connected with PVR). So this is only information, not error.
- Código:
Jan 5 01:28:38 10 user.warn kernel: -----------------------------------------
Jan 5 01:28:38 10 user.warn kernel: [I2C0] Xfer fail - TXABORT (1/2), Reason=0001
Jan 5 01:28:38 10 user.warn kernel: msg->addr = 3a
Jan 5 01:28:38 10 user.warn kernel: msg->flags = 0001
Jan 5 01:28:38 10 user.warn kernel: msg->len = 1
Jan 5 01:28:38 10 user.warn kernel: msg->buf = 8fea7e00
Jan 5 01:28:38 10 user.warn kernel: -----------------------------------------
It means there cannot be HDMI communication. (I turn off the TV connected with PVR). So this is only information, not error.
Keltek- Mensajes : 291
Fecha de inscripción : 10/03/2010
Edad : 47
Localización : Praha - Czech Republic -
SCSI error
Keltek Jue Ene 20, 2011 4:55 pm
I detected a very nasty bug which totally damage the system. It happen after 20hours of work and it is kernel bug (or driver bug)
Errors in this logs are fatal. I logged to PVR and see the EXT3 partition is remounted to read-only. I can't make anything. Only 'reboot' helps.
This log have following aspects:
1) if something like this occurs, system is broken and must be rebooted - after reboot, all seems to works ok
2) as you can see, I issue the 'reboot' command and it seems the all processes receive the TERM signal, system try to unmount devices, turn off swap devices and then reboot, it is good so this is the correct way. I don't know what happen if you press the reset button.
Is this a possibility of reboot-loop issue????
- Código:
Jan 19 23:12:39 192.168.1.12 kernel: Get back MASTERSHIP PTS= 0x5c137ed4,LPTS= 0x5c13807b,count= 0x00000001
Jan 19 23:12:46 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:12:46 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929695045
Jan 19 23:12:46 192.168.1.12 kernel: EXT3-fs error (device sda4): ext3_get_inode_loc: unable to read inode block - inode=8223, block=32790
Jan 19 23:12:48 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:12:48 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929695057
Jan 19 23:12:48 192.168.1.12 kernel: EXT3-fs error (device sda4): ext3_get_inode_loc: unable to read inode block - inode=8271, block=32796
Jan 19 23:12:48 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:12:48 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929695161
Jan 19 23:12:48 192.168.1.12 kernel: EXT3-fs error (device sda4): ext3_get_inode_loc: unable to read inode block - inode=8682, block=32848
Jan 19 23:12:48 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:12:48 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929695161
Jan 19 23:12:48 192.168.1.12 kernel: EXT3-fs error (device sda4): ext3_get_inode_loc: unable to read inode block - inode=8681, block=32848
Jan 19 23:12:48 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:12:48 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929695061
Jan 19 23:12:48 192.168.1.12 kernel: EXT3-fs error (device sda4): ext3_get_inode_loc: unable to read inode block - inode=8282, block=32798
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657643
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657651
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657659
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657667
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657675
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657683
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657691
Jan 19 23:15:21 192.168.1.12 kernel: i2c_0 : time out
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657699
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657707
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657715
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657723
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657731
Jan 19 23:15:21 192.168.1.12 kernel: Get back MASTERSHIP PTS= 0x5cf145d4,LPTS= 0x5cf148ea,count= 0x00000002
Jan 19 23:15:21 192.168.1.12 kernel: WARNING[1]:<4>VO: audio master RCD jumps -3301 PTS. Video re-sync to audio.
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657739
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657747
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657755
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657763
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657643
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657643
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657643
Jan 19 23:15:21 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:21 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929657643
Jan 19 23:15:27 192.168.1.12 transmission-daemon[395]: Closing session
Jan 19 23:15:27 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:27 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929706291
Jan 19 23:15:27 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:27 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929705277
Jan 19 23:15:27 192.168.1.12 kernel: EXT3-fs error (device sda4): ext3_find_entry: reading directory #8110 offset 0
Jan 19 23:15:27 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:27 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929705277
Jan 19 23:15:27 192.168.1.12 kernel: EXT3-fs error (device sda4): ext3_find_entry: reading directory #8110 offset 0
Jan 19 23:15:37 192.168.1.12 kernel: __journal_remove_journal_head: freeing b_committed_data
Jan 19 23:15:37 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:15:37 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2929630005
Jan 19 23:15:37 192.168.1.12 kernel: Buffer I/O error on device sda4, logical block 270
Jan 19 23:15:37 192.168.1.12 kernel: lost page write due to I/O error on sda4
Jan 19 23:18:02 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:18:02 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 16217
Jan 19 23:18:02 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 16225
Jan 19 23:18:02 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:18:02 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18145
Jan 19 23:18:02 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:18:02 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18153
Jan 19 23:18:02 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:18:02 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18161
Jan 19 23:18:02 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:18:02 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18169
Jan 19 23:18:02 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:18:02 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18177
Jan 19 23:18:02 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:18:02 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18185
Jan 19 23:18:02 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:18:02 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18193
Jan 19 23:18:02 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:18:02 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18201
Jan 19 23:18:02 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:18:02 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18145
Jan 19 23:18:02 192.168.1.12 kernel: Get back MASTERSHIP PTS= 0x5dcec1d4,LPTS= 0x5dced018,count= 0x00000001
Jan 19 23:18:07 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:18:07 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18145
Jan 19 23:18:10 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:18:10 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18145
Jan 19 23:18:19 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:18:19 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18145
Jan 19 23:18:40 192.168.1.12 kernel: Get back MASTERSHIP PTS= 0x5e028fb4,LPTS= 0x5e0292b2,count= 0x00000001
Jan 19 23:19:01 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:19:01 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18145
Jan 19 23:19:06 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:19:06 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 335824561
Jan 19 23:19:06 192.168.1.12 kernel: Buffer I/O error on device sda1, logical block 41976062
Jan 19 23:19:06 192.168.1.12 kernel: lost page write due to I/O error on sda1
Jan 19 23:19:11 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:19:11 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 16169
Jan 19 23:19:11 192.168.1.12 kernel: Buffer I/O error on device sda1, logical block 13
Jan 19 23:19:11 192.168.1.12 kernel: lost page write due to I/O error on sda1
Jan 19 23:19:24 192.168.1.12 kernel: Get back MASTERSHIP PTS= 0x5e3f26a4,LPTS= 0x5e3f28bf,count= 0x00000001
Jan 19 23:19:35 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:19:35 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 16169
Jan 19 23:20:06 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:20:06 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 335824561
Jan 19 23:20:06 192.168.1.12 kernel: Buffer I/O error on device sda1, logical block 41976062
Jan 19 23:20:06 192.168.1.12 kernel: lost page write due to I/O error on sda1
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18209
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18217
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18225
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18233
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18241
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18249
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18257
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18265
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 262569
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 262577
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 262593
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: Get back MASTERSHIP PTS= 0x5f5aff54,LPTS= 0x5f5b01eb,count= 0x00000001
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 262601
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 262609
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 262617
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 262625
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 262633
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 262641
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 262649
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 262657
Jan 19 23:22:51 192.168.1.12 kernel: i2c_0 : time out
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 262665
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 262673
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 262681
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 262689
Jan 19 23:22:51 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:22:51 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 18145
Jan 19 23:23:10 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:23:10 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 16169
Jan 19 23:23:10 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:23:10 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 335824561
Jan 19 23:23:10 192.168.1.12 kernel: Buffer I/O error on device sda1, logical block 41976062
Jan 19 23:23:10 192.168.1.12 kernel: lost page write due to I/O error on sda1
Jan 19 23:23:10 192.168.1.12 init: starting pid 1814, tty '': 'umount -a -r'
Jan 19 23:23:10 192.168.1.12 kernel: SCSI error : <1 0 0 0> return code = 0x40000
Jan 19 23:23:10 192.168.1.12 kernel: end_request: I/O error, dev sda, sector 2896022577
Jan 19 23:23:10 192.168.1.12 kernel: Buffer I/O error on device sda3, logical block 273
Jan 19 23:23:10 192.168.1.12 kernel: lost page write due to I/O error on sda3
Jan 19 23:23:10 192.168.1.12 kernel: umount: can't remount /dev/scsi/host1/bus0/target0/lun0/part1 read-only
Jan 19 23:23:10 192.168.1.12 kernel: umount: can't remount /dev/rd/0 read-only
Jan 19 23:23:10 192.168.1.12 kernel: umount: can't remount none read-only
Jan 19 23:23:10 192.168.1.12 kernel: umount: can't remount /dev/mtdblock/2 read-only
Jan 19 23:23:10 192.168.1.12 kernel: umount: devpts busy - remounted read-only
Jan 19 23:23:10 192.168.1.12 kernel: umount: none busy - remounted read-only
Jan 19 23:23:10 192.168.1.12 init: starting pid 1815, tty '': 'swapoff -a'
Jan 19 23:23:10 192.168.1.12 init: The system is going down NOW!
Jan 19 23:23:10 192.168.1.12 kernel:
The system is going down NOW!
Errors in this logs are fatal. I logged to PVR and see the EXT3 partition is remounted to read-only. I can't make anything. Only 'reboot' helps.
This log have following aspects:
1) if something like this occurs, system is broken and must be rebooted - after reboot, all seems to works ok
2) as you can see, I issue the 'reboot' command and it seems the all processes receive the TERM signal, system try to unmount devices, turn off swap devices and then reboot, it is good so this is the correct way. I don't know what happen if you press the reset button.
Is this a possibility of reboot-loop issue????
Keltek- Mensajes : 291
Fecha de inscripción : 10/03/2010
Edad : 47
Localización : Praha - Czech Republic -
Re: System logging and kernel bugs
vic1972 Jue Ene 20, 2011 6:17 pm
Good finding 
very weird. what i think is that the main problem we are handling somehow affect different to different equipments; ..
why some people have suffered this many times... and others (like me , or keltek, etc) have EVER not suffered...
What is differences?... the hard disk I suppose...
Would it be feasible to create a daemon program that keep looking for that error you detected, and then issue the reset command .....
thanks for the investigation and sharing to us.
very weird. what i think is that the main problem we are handling somehow affect different to different equipments; ..
why some people have suffered this many times... and others (like me , or keltek, etc) have EVER not suffered...
What is differences?... the hard disk I suppose...
Would it be feasible to create a daemon program that keep looking for that error you detected, and then issue the reset command .....
thanks for the investigation and sharing to us.
vic1972- Mensajes : 2260
Fecha de inscripción : 09/12/2009
Edad : 52
Localización : Malaga
Página 1 de 1.
Permisos de este foro:
No puedes responder a temas en este foro.