linux-kernel - Re: Linux 2.6.25-rc4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 17 Mar 2008 22:09:00 +0100
From:	Anders Eriksson <aeriksson@...tmail.fm>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
cc:	Anders Eriksson <aeriksson@...tmail.fm>,
	Bartlomiej Zolnierkiewicz <bzolnier@...il.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Jens Axboe <jens.axboe@...cle.com>,
	Ingo Molnar <mingo@...e.hu>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.25-rc4 


torvalds@...ux-foundation.org said:
> Can you try to sprinkle printk's around to see where it actually ends up
> stopping?

> Since all special commands should now go through the taskfile interface
> (Bartlomiej - correct?), I guess just a printk() at the top of
> do_rw_taskfile() should at least get the ball rolling. Even something that
> just prints out task->data_phase and tf->command would start to unravel at
> least what the last command is before it hangs.. 

Tossing a prink in like so:
ide_startstop_t do_rw_taskfile (ide_drive_t *drive, ide_task_t *task)
{
        ide_hwif_t *hwif        = HWIF(drive);
        struct ide_taskfile *tf = &task->tf;
        ide_handler_t *handler = NULL;

        printk("do_rw_taskfile(task->data_phase=%i, tf->command=%i\n",task->data_phase,tf->command);

        if (task->data_phase == TASKFILE_MULTI_IN ||



Yields:
Mar 17 21:57:29 tippex smartd[5810]: smartd version 5.37 [i686-pc-linux-gnu] Copyright (C) 2002-6 Bruce Allen
Mar 17 21:57:29 tippex smartd[5810]: Home page is http://smartmontools.sourceforge.net/
Mar 17 21:57:29 tippex smartd[5810]: Opened configuration file /etc/smartd.conf
Mar 17 21:57:29 tippex do_rw_taskfile(task->data_phase=32, tf->command=37
Mar 17 21:57:29 tippex do_rw_taskfile(task->data_phase=1, tf->command=236
Mar 17 21:57:29 tippex smartd[5810]: Configuration file /etc/smartd.conf parsed.
Mar 17 21:57:29 tippex smartd[5810]: Device: /dev/hda, opened
Mar 17 21:57:29 tippex do_rw_taskfile(task->data_phase=0, tf->command=176
Mar 17 21:57:29 tippex smartd[5810]: Device: /dev/hda, found in smartd database.
Mar 17 21:57:29 tippex do_rw_taskfile(task->data_phase=0, tf->command=176
Mar 17 21:57:30 tippex do_rw_taskfile(task->data_phase=1, tf->command=176
Mar 17 21:57:30 tippex do_rw_taskfile(task->data_phase=1, tf->command=176
Mar 17 21:57:30 tippex do_rw_taskfile(task->data_phase=1, tf->command=236
Mar 17 21:57:30 tippex smartd[5810]: Device: /dev/hda, can't monitor Current Pending Sector count - no Attribute 197
Mar 17 21:57:30 tippex smartd[5810]: Device: /dev/hda, can't monitor Offline Uncorrectable Sector count  - no Attribute 198
Mar 17 21:57:30 tippex smartd[5810]: Device: /dev/hda, can't monitor Temperature, ignoring -W Directive
Mar 17 21:57:30 tippex smartd[5810]: Device: /dev/hda, appears to lack SMART Self-Test log; disabling -l selftest (override with -T permissive Directive)
Mar 17 21:57:30 tippex smartd[5810]: Device: /dev/hda, appears to lack SMART Error log; disabling -l error (override with -T permissive Directive)
Mar 17 21:57:30 tippex smartd[5810]: Device: /dev/hda, is SMART capable. Adding to "monitor" list.
Mar 17 21:57:30 tippex smartd[5810]: Device: /dev/hda, opened
Mar 17 21:57:30 tippex smartd[5810]: Device: /dev/hda, found in smartd database.
Mar 17 21:57:30 tippex do_rw_taskfile(task->data_phase=0, tf->command=176
Mar 17 21:57:30 tippex do_rw_taskfile(task->data_phase=1, tf->command=176
Mar 17 21:58:00 tippex hda: lost interrupt


And the usual freeze. This is on -rc5 with Barts latest suggestion.

next?

/A

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/