Bug#585513: Kernel oops related to ext3 on iSCSI usage
Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-21lenny4 On a fully up-to-date (as of last wednesday) Debian Lenny I got a kernel oops related to ext3 and iSCSI. I'm using the system as an iSCSI initiator using Open-iSCSI, and drive was partitioned and then formated with ext3. That same wednesday, I started an rsync to that partition in a screen session. Today I resumed my previously detached screen session and noticed that the mount point was not accessible anymore: ls /mnt/iscsi/ ls: reading directory /mnt/iscsi/: Input/output error Unfortunately, I am not sure whether there have been network problems during that period which might have been related. When investigating the problem I noticed a related kernel oops: 58601.554939] connection1:0: detected conn error (1011) [58723.877887] session1: session recovery timed out after 120 secs [58723.877881] sd 4:0:0:0: Device offlined - not ready after error recovery [58723.877881] sd 4:0:0:0: [sdc] Result: hostbyte=DID_BUS_BUSY driverbyte=DRIVER_OK,SUGGEST_OK [58723.877881] end_request: I/O error, dev sdc, sector 12375 [58723.877881] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #2 offset 0 [58723.877881] sd 4:0:0:0: rejecting I/O to offline device [58723.877881] Buffer I/O error on device sdc1, logical block 0 [58723.877881] lost page write due to I/O error on sdc1 [116604.384962] connection1:0: ping timeout of 5 secs expired, last rx 4322173053, last ping 4322174303, now 4322175553 [116604.385018] connection1:0: detected conn error (1011) [116738.158957] session1: session recovery timed out after 120 secs [150180.464021] sd 4:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK [150180.464026] end_request: I/O error, dev sdc, sector 12375 [150180.464059] EXT3-fs error (device sdc1): ext3_find_entry: reading directory #2 offset 0 [150180.464400] [ cut here ] [150180.464402] WARNING: at fs/buffer.c:1186 mark_buffer_dirty +0x23/0x77() [150180.464404] Modules linked in: ipv6 crc32c libcrc32c ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi scsi_transport_iscsi loop joydev snd_pcm snd_timer snd pcspkr soundcore psmouse snd_page_alloc serio_raw usbhid hid ff_memless button evdev dcdbas ext3 jbd mbcache sg sr_mod cdrom ata_generic usb_storage ata_piix libata dock sd_mod ehci_hcd ide_pci_generic ide_core uhci_hcd tg3 mptsas mptscsih mptbase scsi_transport_sas scsi_mod thermal processor fan thermal_sys [last unloaded: scsi_wait_scan] [150180.464439] Pid: 5549, comm: standard Not tainted 2.6.26-2-amd64 #1 [150180.464440] [150180.464441] Call Trace: [150180.464448] [802348d0] warn_on_slowpath+0x51/0x7a [150180.464453] [80373240] notify_update+0x2b/0x30 [150180.464456] [803773f0] vt_console_print+0x26f/0x282 [150180.464460] [8023536b] printk+0x4e/0x56 [150180.464471] [a0159821] :ext3:ext3_count_free_blocks +0x2a/0x49 [150180.464475] [802bab62] mark_buffer_dirty+0x23/0x77 [150180.464483] [a0162b10] :ext3:ext3_commit_super+0x49/0x65 [150180.464492] [a01635f6] :ext3:ext3_handle_error+0x83/0xaa [150180.464501] [a0163701] :ext3:ext3_error+0x83/0x90 [150180.464506] [802bafcd] sync_buffer+0x0/0x3f [150180.464510] [8042946c] out_of_line_wait_on_bit+0x6c/0x78 [150180.464513] [8024613f] wake_bit_function+0x0/0x23 [150180.464522] [a016020f] :ext3:ext3_find_entry+0x423/0x5b7 [150180.464531] [80248af6] hrtimer_start+0x112/0x134 [150180.464541] [a0161b50] :ext3:ext3_lookup+0x31/0xc9 [150180.464544] [802ab708] d_alloc+0x15b/0x1a8 [150180.464548] [802a1e72] do_lookup+0xd7/0x1c1 [150180.464552] [802a3fd5] __link_path_walk+0x87a/0xd05 [150180.464555] [802adbed] touch_atime+0xc3/0x112 [150180.464558] [802b07d9] mnt_drop_write+0x25/0xdd [150180.464562] [802a44a6] path_walk+0x46/0x8b [150180.464566] [802a47d2] do_path_lookup+0x158/0x1cf [150180.464569] [802a35dd] getname+0x140/0x1a7 [150180.464572] [802a5141] __user_walk_fd+0x37/0x4c [150180.464575] [8029e24d] vfs_stat_fd+0x1b/0x4a [150180.464578] [80246111] autoremove_wake_function+0x0/0x2e [150180.464581] [8023748f] do_wait+0x968/0x9f8 [150180.464586] [8029e2d8] sys_newstat+0x19/0x31 [150180.464588] [8029b778] vfs_read+0x11e/0x152 [150180.464592] [8023f92c] sys_rt_sigprocmask+0xba/0xd3 [150180.464596] [8020beda] system_call_after_swapgs+0x8a/0x8f [150180.464600] [150180.464602] ---[ end trace b66073b8bb4bc5fa ]--- [150180.464612] sd 4:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK [150180.464615] end_request: I/O error, dev sdc, sector 63 [150180.464642] Buffer I/O error on device sdc1, logical block 0 [150180.464669] lost page write due to I/O error on sdc1 [162615.853654] sd 4:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT
Bug#395031: Kernel complains about DMA
Hi, On Wed, Oct 25, 2006 at 06:25:09AM +0200, Frederik Schueler wrote: Hello, On Tue, Oct 24, 2006 at 04:30:50PM +0200, Panagiotis Issaris wrote: Oct 24 11:00:25 localhost kernel: CMD643: IDE controller at PCI slot :00:08.0 Oct 24 11:00:25 localhost kernel: CMD643: chipset revision 0 Oct 24 11:00:25 localhost kernel: CMD643: not 100%% native mode: will probe irqs later Oct 24 11:00:25 localhost kernel: CMD643: simplex device: DMA forced ^^ Oct 24 11:00:25 localhost kernel: ide0: BM-DMA at 0xfe00-0xfe07, BIOS settings: hda:pio, hdb:pio Oct 24 11:00:25 localhost kernel: ide1: BM-DMA at 0xfe08-0xfe0f, BIOS settings: hdc:pio, hdd:pio I doubt this box will do DMA, ever. AFAIK the chipset just does not support it. Apparently drivers/ide/setup-pci.c forces it to use DMA as there's a switch in which certain chipsets are forced to use DMA, while the default handling is to disable it. Thanks for your useful reply! With friendly regards, Takis -- vCard: http://www.issaris.be/pi.vcf Public key: http://www.issaris.be/pi.key diff --git a/drivers/ide/setup-pci.c b/drivers/ide/setup-pci.c index 0719b64..5a7b6f6 100644 --- a/drivers/ide/setup-pci.c +++ b/drivers/ide/setup-pci.c @@ -226,7 +226,6 @@ #endif /* CONFIG_BLK_DEV_IDEDMA_FORCED * case PCI_DEVICE_ID_AL_M5219: case PCI_DEVICE_ID_AL_M5229: case PCI_DEVICE_ID_AMD_VIPER_7409: - case PCI_DEVICE_ID_CMD_643: case PCI_DEVICE_ID_SERVERWORKS_CSB5IDE: case PCI_DEVICE_ID_REVOLUTION: simplex_stat = hwif-INB(dma_base + 2); -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395031: Kernel complains about DMA
Hi, As requested, the bug-id in the Linux kernel Bugzilla database is 7413 and thus the URL is: http://bugzilla.kernel.org/show_bug.cgi?id=7413 With friendly regards, Takis -- vCard: http://www.issaris.be/pi.vcf Public key: http://www.issaris.be/pi.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395031: Kernel complains about DMA
Package: kernel-image-2.6.8-3-386
Version: 2.6.8-16sarge5
When booting the abovementioned kernel on a friends laptop, it shows errors when
trying to initialize the IDE controller. When showing the errors, it waits for
quite some time, increasing the boottime with about a minute (raw guestimate).
The laptop is a Dell Lattitude xpi cd p150st and it is running the current
Debian stable.
Oct 24 11:00:24 localhost kernel: Linux version 2.6.8-3-386 ([EMAIL PROTECTED])
(gcc
version 3.3.5 (Debian 1:3.3.5-13)) #1 Sat Jul 15 09:26:40 UTC 2006
Oct 24 11:00:24 localhost kernel: BIOS-provided physical RAM map:
Oct 24 11:00:24 localhost kernel: BIOS-e820: -
000a (usable)
Oct 24 11:00:24 localhost kernel: BIOS-e820: 0010 -
0300 (usable)
Oct 24 11:00:24 localhost kernel: 48MB LOWMEM available.
Oct 24 11:00:24 localhost kernel: On node 0 totalpages: 12288
Oct 24 11:00:24 localhost kernel: DMA zone: 4096 pages, LIFO batch:1
Oct 24 11:00:24 localhost kernel: Normal zone: 8192 pages, LIFO batch:2
Oct 24 11:00:24 localhost kernel: HighMem zone: 0 pages, LIFO batch:1
Oct 24 11:00:24 localhost kernel: DMI not present.
Oct 24 11:00:24 localhost kernel: ACPI: Unable to locate RSDP
Oct 24 11:00:24 localhost kernel: Built 1 zonelists
Oct 24 11:00:24 localhost kernel: Kernel command line: root=/dev/hda1 ro
Oct 24 11:00:24 localhost kernel: No local APIC present or hardware disabled
Oct 24 11:00:24 localhost kernel: Initializing CPU#0
Oct 24 11:00:24 localhost kernel: PID hash table entries: 256 (order 8: 2048
bytes)
Oct 24 11:00:24 localhost kernel: Detected 150.429 MHz processor.
Oct 24 11:00:24 localhost kernel: Using tsc for high-res timesource
...
Oct 24 11:00:25 localhost kernel: SCSI subsystem initialized
Oct 24 11:00:25 localhost kernel: libata version 1.02 loaded.
Oct 24 11:00:25 localhost kernel: Uniform Multi-Platform E-IDE driver Revision:
7.00alpha2
Oct 24 11:00:25 localhost kernel: ide: Assuming 33MHz system bus speed for PIO
modes; override with idebus=xx
Oct 24 11:00:25 localhost kernel: CMD643: IDE controller at PCI slot
:00:08.0
Oct 24 11:00:25 localhost kernel: CMD643: chipset revision 0
Oct 24 11:00:25 localhost kernel: CMD643: not 100%% native mode: will probe
irqs later
Oct 24 11:00:25 localhost kernel: CMD643: simplex device: DMA forced
Oct 24 11:00:25 localhost kernel: ide0: BM-DMA at 0xfe00-0xfe07, BIOS
settings: hda:pio, hdb:pio
Oct 24 11:00:25 localhost kernel: ide1: BM-DMA at 0xfe08-0xfe0f, BIOS
settings: hdc:pio, hdd:pio
Oct 24 11:00:25 localhost kernel: hda: IBM-DCRA-22160, ATA DISK drive
Oct 24 11:00:25 localhost kernel: Using anticipatory io scheduler
Oct 24 11:00:25 localhost kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Oct 24 11:00:25 localhost kernel: hda: max request size: 128KiB
Oct 24 11:00:25 localhost kernel: hda: 4233600 sectors (2167 MB) w/96KiB Cache,
CHS=4200/16/63, DMA
Oct 24 11:00:25 localhost kernel: /dev/ide/host0/bus0/target0/lun0:4hda:
dma_timer_expiry: dma status == 0x24
Oct 24 11:00:25 localhost kernel: hda: DMA timeout error
Oct 24 11:00:25 localhost kernel: hda: dma timeout error: status=0x50 {
DriveReady SeekComplete }
Oct 24 11:00:25 localhost kernel:
Oct 24 11:00:25 localhost kernel: p1 p2 4hda: dma_timer_expiry: dma status
== 0x24
Oct 24 11:00:25 localhost kernel: hda: DMA timeout error
Oct 24 11:00:25 localhost kernel: hda: dma timeout error: status=0x50 {
DriveReady SeekComplete }
Oct 24 11:00:25 localhost kernel:
Oct 24 11:00:25 localhost kernel: p5
Oct 24 11:00:25 localhost kernel: hdc: CD-ROM CDR-N16D, ATAPI CD/DVD-ROM drive
Oct 24 11:00:25 localhost kernel: ide1 at 0x170-0x177,0x376 on irq 15
Oct 24 11:00:25 localhost kernel: ide2: I/O resource 0x3EE-0x3EE not free.
Oct 24 11:00:25 localhost kernel: ide2: ports already in use, skipping probe
Oct 24 11:00:25 localhost kernel: hda: dma_timer_expiry: dma status == 0x24
Oct 24 11:00:25 localhost kernel: hda: DMA timeout error
Oct 24 11:00:25 localhost kernel: hda: dma timeout error: status=0x50 {
DriveReady SeekComplete }
Oct 24 11:00:25 localhost kernel:
Oct 24 11:00:25 localhost kernel: hda: dma_timer_expiry: dma status == 0x24
Oct 24 11:00:25 localhost kernel: hda: DMA timeout error
Oct 24 11:00:25 localhost kernel: hda: dma timeout error: status=0x50 {
DriveReady SeekComplete }
Oct 24 11:00:25 localhost kernel:
Oct 24 11:00:25 localhost kernel: EXT3-fs: INFO: recovery required on readonly
filesystem.
Oct 24 11:00:25 localhost kernel: EXT3-fs: write access will be enabled during
recovery.
Oct 24 11:00:25 localhost kernel: kjournald starting. Commit interval 5 seconds
...
For now, I've compiled a 2.6.19-rc3 kernel without DMA support which boots fine
(and fast). I'm about to test a 2.6.19-rc3 kernel _with_ DMA to see if the bug
has been fixed sometime after the 2.6.8 kernels.
With friendly regards,
Takis
--
vCard: http://www.issaris.be/pi.vcf
Public key: http://www.issaris.be/pi.key
--
To UNSUBSCRIBE, email to [EMAIL
Bug#395031: Kernel complains about DMA
Hi, I've also reported this bug to the main Linux kernel mailinglist. Links to the report listed below: http://marc.theaimsgroup.com/?t=11617026821r=1w=2 http://thread.gmane.org/gmane.linux.kernel/460176/focus=460176 -- vCard: http://www.issaris.be/pi.vcf Public key: http://www.issaris.be/pi.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395031: Kernel complains about DMA
I've tested this on Linux 2.6.19-rc3, and the problem remains. With friendly regards, Takis -- vCard: http://www.issaris.be/pi.vcf Public key: http://www.issaris.be/pi.key -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#343694: devscripts: debcommit doesn't support git
Package: devscripts
Version: 2.9.10
Severity: wishlist
Tags: patch
There's no support in debcommit for maintainers using GIT.
The accompanying patch adds GIT support to debcommit.
diff -Naur devscripts-2.9.10-orig/debcommit.pl devscripts-2.9.10/debcommit.pl
--- devscripts-2.9.10-orig/debcommit.pl 2005-12-17 10:53:36.0 +0100
+++ devscripts-2.9.10/debcommit.pl 2005-12-17 11:19:01.0 +0100
@@ -11,8 +11,8 @@
=head1 DESCRIPTION
debcommit generates a commit message based on new text in debian/changelog,
-and commits the change to a package's cvs, svn, svk, arch, or bzr
-repository. It must be run in a cvs, svn, svk, arch, or bzr working copy for
+and commits the change to a package's cvs, svn, svk, arch, bzr or git
+repository. It must be run in a cvs, svn, svk, arch, bzr or git working copy
for
the package.
=head1 OPTIONS
@@ -22,7 +22,7 @@
=item -r --release
Commit a release of the package. The version number is determined from
-debian/changelog, and is used to tag the package in cvs, svn, svk, or arch.
+debian/changelog, and is used to tag the package in cvs, svn, svk, arch or git.
bzr does not yet support symbolic tags, so you will only get a normal
commit.
@@ -106,6 +106,9 @@
elsif (-d .bzr) {
return bzr;
}
+elsif (-d .git) {
+ return git;
+}
else {
# svk has no useful directories so try to run it.
my $svkpath=`svk info . 2/dev/null| grep -i '^Depot Path:' | cut -d '
' -f 2`;
@@ -133,6 +136,11 @@
die commit failed\n;
}
}
+elsif ($prog eq 'git') {
+ if (! action($prog, commit, -a, -m, $message)) {
+ die commit failed\n;
+ }
+}
elsif ($prog eq 'tla' || $prog eq 'baz') {
my $summary=$message;
$summary=~s/^((?:\* )?[^\n]{1,72})(?:(?:\s|\n).*|$)/$1/ms;
@@ -199,17 +207,24 @@
elsif ($prog eq 'bzr') {
warn No support for symbolic tags in bzr yet.\n;
}
+elsif ($prog eq 'git') {
+ $tag=~s/^[0-9]+://; # strip epoch
+ $tag=debian_version_$tag;
+ if (! action($prog, tag, $tag)) {
+ die failed tagging with $tag\n;
+ }
+}
}
sub getmessage {
my $ret;
if ($prog eq 'cvs' || $prog eq 'svn' || $prog eq 'svk' ||
- $prog eq 'tla' || $prog eq 'baz' || $prog eq 'bzr') {
+ $prog eq 'tla' || $prog eq 'baz' || $prog eq 'bzr' || $prog eq 'git') {
$ret='';
my $subcommand;
if ($prog eq 'cvs' || $prog eq 'svn' || $prog eq 'svk' ||
- $prog eq 'bzr') {
+ $prog eq 'bzr' || $prog eq 'git' ) {
$subcommand = 'diff';
} else {
$subcommand = 'file-diff';
diff -Naur devscripts-2.9.10-orig/README devscripts-2.9.10/README
--- devscripts-2.9.10-orig/README 2005-12-17 10:53:36.0 +0100
+++ devscripts-2.9.10/README2005-12-17 11:21:53.0 +0100
@@ -59,8 +59,8 @@
the .diffs and original files, though, so that the binaries and
other files can be rebuilt if necessary.
-- debcommit [cvs | subversion | tla | bazaar ]: Commits changes to
- cvs, svn, or arch, using new entries in debian/changelog as the
+- debcommit [cvs | subversion | tla | bazaar | git]: Commits changes to
+ cvs, svn, arch or git, using new entries in debian/changelog as the
commit message. Also supports tagging Debian package releases.
- debdiff [wdiff, patchutils]: A program which examines two .deb files
@@ -175,7 +175,7 @@
2. Editing of files
3. Log the changes with: dch -i I changed this
- If desired, use debcommit to commit changes to cvs, svn, or arch.
+ If desired, use debcommit to commit changes to cvs, svn, arch or git.
4. Run debuild to compile it. If it fails, return to 2. (You could
also just test the compilation by running the appropriate part of
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
