Bug#502452: Info received (kernel: UDF written file corrupted by zeros)
Selon Debian Bug Tracking System ow...@bugs.debian.org: Thank you for the additional information you have supplied regarding this Bug report. In fact, UDF for those 33 Gbytes cartridge seams to work fine with linux debian both 32 bits and 64 bits, both kernel 2.6.18 (for reading) and 2.6.24, both IDE and USB. However, cartridge written with linux is not fully readable under windows XP: Cartridge is recognized as plug and play when connecting USB. Three directory in root are displayed in explorer. According to windows explorer, lost+found directory is empty (ok). log directory contain a single file witch is readable (ok). data directory containing about 20 or 40 files including some files up to 3-4 Gyga bytes is marked as broken, so those 20-40 files are not displayed by explorer. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#502452: kernel: UDF written file corrupted by zeros
Selon Moritz Muehlenhoff j...@inutil.org: On Thu, Oct 16, 2008 at 06:04:53PM +0200, Jean-Michel wrote: Package: kernel Version: 2.6.24-etchnhalf.1-amd64 Severity: important Due to existing bugs I had with UDF in kernel 2.6.18, I use 2.6.24 for 8 days. With 2.6.18 some file were not copied/created, when my log file was mainly right. With 2.6.24 my log file is corrupt. Some monthes ago, I made one script which copy files to the 33 Gbytes IOMEGA /dev/hda drive I formatted just before, with udf filesystem, in the same time it writes the text log file. Everithing looks nice, but begin of log file contains null bytes till around offset 0x06e3, when begin of this text file is missing. The log file is obtained by redirecting stdout. Sorry for the late reply. Is this error reproducible or does it only occur from time to time? If so, does it only show up with 2.6.24 and not with 2.6.18? Cheers, Moritz I do not remember if I added a workaround in the script or not. I just made some test: Now, files are written under a 2.6.24 kernel on 64 bits architecture with IDE drive. And looks like beeing readable. It also looks readbale from a 2.6.26 kernel on another 64 bits computer, via USB drive. I mean files can be readen without error, and log file does not contain any zero at begining. I did not check for vilidity of data nor is it is readble from an older kernel or a 32 bits architecture. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#407112: kernel: network and system crashes.
Package: kernel Version: NetworkManager Severity: normal During the night, while there is no activity on computer but samba traffic, network crashed, and computer too. At the morning, computer was unavailable by ssh, nor by X local session. Here after, logs: /var/log/debug: Jan 15 23:32:21 computername last message repeated 4 times Jan 16 00:31:50 computername kernel: usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 128 rq 6 len 255 ret -110 Jan 16 00:31:51 computername kernel: usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 128 rq 6 len 255 ret -110 Jan 16 00:41:11 computername NetworkManager: debug info^I[1168904471.056781] nm_hal_device_removed (): Device removed (hal udi is '/org/freedesktop/Hal/devices/volume_empty_unknown'). Jan 16 00:53:44 computername kernel: sky2 eth2: transmit ring 314 .. 273 report=314 done=314 Jan 16 01:07:59 computername kernel: sky2 eth2: transmit ring 273 .. 232 report=314 done=314 Jan 16 01:09:34 computername kernel: sky2 eth2: transmit ring 314 .. 273 report=314 done=314 (manual reboot) Jan 16 08:18:05 computername kernel: ACPI: RSDP (v000 ACPIAM /var/log/syslog: Jan 16 00:41:15 computername postfix/smtp[12742]: C07976BE4F: to=[EMAIL PROTECTED], relay=192.168.236.22[192.168.236.22]:25, delay=11, delays=7.6/0.41/1.3/1.5, dsn=2.0.0, status=sent (250 Ok: queued as 3E7A06032) Jan 16 00:41:15 computername postfix/qmgr[3471]: C07976BE4F: removed Jan 16 00:41:15 computername postfix/smtp[12741]: 260E06BE4E: to=[EMAIL PROTECTED], relay=192.168.236.22[192.168.236.22]:25, delay=4.4, delays=1.1/0.33/1.4/1.6, dsn=2.0.0, status=sent (250 Ok: queued as DC7076030) Jan 16 00:41:15 computername postfix/qmgr[3471]: 260E06BE4E: removed Jan 16 00:45:02 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 00:46:16 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 00:47:30 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 00:48:44 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 00:49:58 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 00:51:12 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 00:52:26 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 00:53:40 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 00:53:44 computername kernel: NETDEV WATCHDOG: eth2: transmit timed out Jan 16 00:53:44 computername kernel: sky2 eth2: tx timeout Jan 16 00:53:44 computername kernel: sky2 eth2: transmit ring 314 .. 273 report=314 done=314 Jan 16 00:53:44 computername kernel: sky2 hardware hung? flushing Jan 16 00:54:54 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 00:56:08 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 00:57:22 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 00:58:36 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 00:59:30 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 01:00:24 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 01:01:18 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 01:02:12 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 01:04:00 computername last message repeated 2 times Jan 16 01:04:54 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 01:05:48 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 01:06:42 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 01:07:36 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 01:07:59 computername kernel: NETDEV WATCHDOG: eth2: transmit timed out Jan 16 01:07:59 computername kernel: sky2 eth2: tx timeout Jan 16 01:07:59 computername kernel: sky2 eth2: transmit ring 273 .. 232 report=314 done=314 Jan 16 01:07:59 computername kernel: sky2 status report lost? Jan 16 01:08:30 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 01:09:02 computername /USR/SBIN/CRON[14089]: (root) CMD ( [ -d /var/lib/php4 ] find /var/lib/php4/ -type f -cmin +$(/usr/lib/php4/maxlifetime) -print0 | xargs -r -0 rm) Jan 16 01:09:02 computername /USR/SBIN/CRON[14090]: (root) CMD ( [ -d /var/lib/php5 ] find /var/lib/php5/ -type f -cmin +$(/usr/lib/php5/maxlifetime) -print0 | xargs -r -0 rm) Jan 16 01:09:24 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 01:09:34 computername kernel: NETDEV WATCHDOG: eth2: transmit timed out Jan 16 01:09:34 computername kernel: sky2 eth2: tx timeout Jan 16 01:09:34 computername kernel: sky2 eth2: transmit ring 314 .. 273 report=314 done=314 Jan 16 01:09:34 computername kernel: sky2 hardware hung? flushing Jan 16 01:10:18 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 01:11:12 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 01:12:06 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 01:13:00 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 01:13:54 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 01:14:48 computername ypbind[2992]: broadcast: RPC: Timed out. Jan 16 01:15:42
Bug#406601: network: remote host disconnected
Package: network Severity: normal All remote host are disconected (rsync/samba, ssh ) Read from remote host simi: Connection timed out On the server, /var/log/messages contient: Jan 11 19:07:33 localhost kernel: NETDEV WATCHDOG: eth2: transmit timed out Jan 11 19:07:33 localhost kernel: sky2 hardware hung? flushing Jan 11 19:20:33 localhost kernel: NETDEV WATCHDOG: eth2: transmit timed out Jan 11 19:20:33 localhost kernel: sky2 status report lost? Jan 11 19:21:43 localhost kernel: NETDEV WATCHDOG: eth2: transmit timed out Jan 11 19:21:43 localhost kernel: sky2 hardware hung? flushing Jan 11 19:36:53 localhost kernel: NETDEV WATCHDOG: eth2: transmit timed out Jan 11 19:36:53 localhost kernel: sky2 status report lost? Jan 11 19:38:03 localhost kernel: NETDEV WATCHDOG: eth2: transmit timed out Jan 11 19:38:03 localhost kernel: sky2 hardware hung? flushing Jan 11 19:54:43 localhost kernel: NETDEV WATCHDOG: eth2: transmit timed out Jan 11 19:54:43 localhost kernel: sky2 status report lost? Jan 11 19:55:58 localhost kernel: NETDEV WATCHDOG: eth2: transmit timed out Jan 11 19:55:58 localhost kernel: sky2 status report lost? etc etc etc Jan 11 20:50:58 localhost kernel: NETDEV WATCHDOG: eth2: transmit timed out Jan 11 20:50:58 localhost kernel: sky2 status report lost? Jan 11 20:51:03 localhost kernel: NETDEV WATCHDOG: eth2: transmit timed out Jan 11 20:51:03 localhost kernel: sky2 status report lost? Jan 11 20:51:06 localhost kernel: printk: 72 messages suppressed. Jan 11 20:51:06 localhost kernel: sky2 eth2: rx error, status 0x7ffc0001 length 60 Jan 11 21:06:52 localhost -- MARK -- Jan 11 21:26:52 localhost -- MARK -- What is sky2? while /var/log/kernel.log says: Jan 11 09:27:35 localhost kernel: usb-storage: device scan complete Jan 11 09:27:36 localhost kernel: FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! Jan 11 09:48:57 localhost kernel: usb 5-4: USB disconnect, address 3 Jan 11 09:53:43 localhost kernel: cdrom: This disc doesn't have any tracks I recognize! Jan 11 09:56:55 localhost kernel: cdrom: This disc doesn't have any tracks I recognize! Jan 11 10:20:03 localhost kernel: cdrom: This disc doesn't have any tracks I recognize! Jan 11 12:25:48 localhost kernel: usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 8 ret -110 Jan 11 14:49:44 localhost kernel: usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 8 ret -110 Jan 11 16:14:11 localhost kernel: usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 128 rq 6 len 255 ret -110 Jan 11 16:14:12 localhost kernel: usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 128 rq 6 len 255 ret -110 Jan 11 16:16:52 localhost kernel: ISO 9660 Extensions: Microsoft Joliet Level 3 Jan 11 16:16:52 localhost kernel: ISO 9660 Extensions: RRIP_1991A Jan 11 19:07:33 localhost kernel: NETDEV WATCHDOG: eth2: transmit timed out Jan 11 19:07:33 localhost kernel: sky2 eth2: tx timeout Jan 11 19:07:33 localhost kernel: sky2 eth2: transmit ring 139 .. 98 report=139 done=139 Jan 11 19:07:33 localhost kernel: sky2 hardware hung? flushing Jan 11 19:15:53 localhost kernel: usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 8 ret -110 Jan 11 19:20:33 localhost kernel: NETDEV WATCHDOG: eth2: transmit timed out Jan 11 19:20:33 localhost kernel: sky2 eth2: tx timeout Jan 11 19:20:33 localhost kernel: sky2 eth2: transmit ring 98 .. 58 report=139 done=139 Jan 11 19:20:33 localhost kernel: sky2 status report lost? Jan 11 19:21:43 localhost kernel: NETDEV WATCHDOG: eth2: transmit timed out Jan 11 19:21:43 localhost kernel: sky2 eth2: tx timeout Jan 11 19:21:43 localhost kernel: sky2 eth2: transmit ring 139 .. 99 report=139 done=139 Jan 11 19:21:43 localhost kernel: sky2 hardware hung? flushing Jan 11 19:36:53 localhost kernel: NETDEV WATCHDOG: eth2: transmit timed out Jan 11 19:36:53 localhost kernel: sky2 eth2: tx timeout Jan 11 19:36:53 localhost kernel: sky2 eth2: transmit ring 99 .. 58 report=139 done=139 etc etc etc Jan 11 20:51:03 localhost kernel: sky2 eth2: tx timeout Jan 11 20:51:03 localhost kernel: sky2 eth2: transmit ring 138 .. 97 report=139 done=139 Jan 11 20:51:03 localhost kernel: sky2 status report lost? Jan 11 20:51:06 localhost kernel: printk: 72 messages suppressed. Jan 11 20:51:06 localhost kernel: sky2 eth2: rx error, status 0x7ffc0001 length 60 Jan 11 21:13:06 localhost kernel: usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 161 rq 1 len 8 ret -110 Jan 11 21:48:44 localhost kernel: usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd newhidups rqt 128 rq 6 len 255 ret -110 while syslog.0 says: Jan 11 16:16:17 localhost NetworkManager: debug info^I[1168528577.254898] nm_hal_device_removed (): Device removed (hal udi is '/org/freedesktop/Hal/devices/volume_empty_dvd_plus_r'). Jan 11 16:16:52 localhost NetworkManager: debug info^I[1168528612.145810] nm_hal_device_added (): New device added (hal udi is
Bug#377024: nfs_common: nfs client crash nfs server? ; [TCP CHECKSUM INCORRECT]
2 additional information: the checksum is bad: * with NFS and SMB over TCP, but not with telnet. * only in TCP blocks wich size (Len under ethereal) is not null this means checksum is good with both telnet blocks empty TCP blocks. Moreover on another computer, without the upgrade, NFS seams to work with UDP instead of TCP! Unless ethereal give bad information? I am not used to these protocols, and do not know what to do with that. Any idea?
Bug#377024: nfs_common: nfs client crash nfs server? ; [TCP CHECKSUM INCORRECT]
I just find a relation between the bad checksum and lenth: I have seen: bad checksum: 5a1c , when Len is 120 bad checksum: 5f58 , when Len is 1460 bad checksum: 5e1c , when Len is 1144 bad checksum: 5a28 , when Len is 132 This seams to mean that: checksum= 0x59A4 + Len but why on earth do I have this bug?
