I installed linux-image-3.9.0-030900-generic_3.9.0-030900.201304291257_amd64.deb and the associated linux-headers- packages from the mainline builds repository. This was the latest version available for raring, which I am using.
Attached is a dmesg log. I…
- boot
- power on the enclosure, connected to the USB 2.0 port
- mount a partition from one disk in the enclosure
- transfer some data to it from another disk using dd, i.e.:
$ sudo dd if=/dev/sdb of=/media/khaeru/eebb644a-a12f-469c-a5d5-b50dfccf074c/tmp.img bs=1G count=1 iflag=direct oflag=direct
1+0 records in
1+0 records out
1073741824 bytes (1.1 GB) copied, 63.4855 s, 16.9 MB/s
- unmount the partition, power off the enclosure
- connect the enclosure to the USB 3.0 port, power on the enclosure
- mount the same partition and attempt to run the same dd command
The attached dmesg is from just before dd is run. The attached image is the kernel panic screen.
The mainline kernel does not fix this bug.
I installed linux-image- 3.9.0-030900- generic_ 3.9.0-030900. 201304291257_ amd64.deb and the associated linux-headers- packages from the mainline builds repository. This was the latest version available for raring, which I am using.
Attached is a dmesg log. I…
- boot
- power on the enclosure, connected to the USB 2.0 port
- mount a partition from one disk in the enclosure
- transfer some data to it from another disk using dd, i.e.:
$ sudo dd if=/dev/sdb of=/media/ khaeru/ eebb644a- a12f-469c- a5d5-b50dfccf07 4c/tmp. img bs=1G count=1 iflag=direct oflag=direct
1+0 records in
1+0 records out
1073741824 bytes (1.1 GB) copied, 63.4855 s, 16.9 MB/s
- unmount the partition, power off the enclosure
- connect the enclosure to the USB 3.0 port, power on the enclosure
- mount the same partition and attempt to run the same dd command
The attached dmesg is from just before dd is run. The attached image is the kernel panic screen.