On Sun, Aug 12, 2012 at 12:45:03PM -0400, Tony Baldwin wrote: > Yesterday I had to reboot my machine. > Cleaning house, I had dislodged the plug for a power strip that powered > the computer, monitor, and printer. > > Now, I am seeing very odd behavior. > Iceweasel hangs forever on some of the simplest tasks, such as loading a > static html page. > Not only that, but when it does so, other tasks on my machine are held > up. For instance, if I have iceweasel loading a page on my first > workspace, and try to load a message in mutt on another, mutt waits for > iceweasel to finish what it's doing before proceeding, which was not > previously the case. > I find this very, very odd.
I've suffered the same problem, very annoying. A ps indicates its plugin-container, have to wait for ages to get mouse response so I can quit iceweasel. It seems to happen sometimes If I leave iceweasel open for a long time. I have installed noscript (highly recommended!) but am not sure if it is a script causing it. Once there was a message about a script being busy, which tied up iceweasel and that was before I installed noscript. There was a dialog box indicating this. > For instance, the machine will be using 2% of CPU and 4% of ram, but be > completely dormant until iceweasel succeeds in downloading a page. > This machine is a 2.8ghz x 4core AMD APU with 16gb of ram, too, so I'm > not exactly lacking in resources. Mmmm, is this from ps? > The only anomalies I have noted in dmesg, etc., are that some sectors of > my hdd are not reading correctly, or something. > A file system check forced on a second reboot yesterday failed, which is > disconcerting, but I'm not certain what to make of that. eeek! Grab any data you need, quick. > dmesg | tail gives me > [79477.080607] ata6.00: failed command: READ DMA EXT > [79477.080621] ata6.00: cmd 25/00:08:9d:23:9f/00:00:6c:00:00/e0 tag 0 > dma 4096 in > [79477.080624] res 51/40:00:9d:23:9f/40:00:6c:00:00/00 Emask > 0x9 (media error) > [79477.080631] ata6.00: status: { DRDY ERR } > [79477.080635] ata6.00: error: { UNC } > [79477.196994] ata6.00: configured for UDMA/33 > [78506.185310] sd 5:0:0:0: [sda] Unhandled sense code > [78506.185315] sd 5:0:0:0: [sda] Result: hostbyte=DID_OK > driverbyte=DRIVER_SENSE > [78506.185322] sd 5:0:0:0: [sda] Sense Key : Medium Error [current] > [descriptor] > [78506.185331] Descriptor sense data with sense descriptors (in hex): > [78506.185335] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 > [78506.185351] 6c 9f 23 9d > [78506.185358] sd 5:0:0:0: [sda] Add. Sense: Unrecovered read error - > auto reallocate failed > [78506.185368] sd 5:0:0:0: [sda] CDB: Read(10): 28 00 6c 9f 23 9d 00 00 > 08 00 > [78506.185378] end_request: I/O error, dev sda, sector 1822368669 > [78506.185398] ata6: EH complete > > I don't know what to make of that. Hard disk *could* be on way out. Get a testdisk, or use smartctl, but I'd treat it as though its going to fail any minute and get any crucial data off it now! But just a heads up about iceweasel problems. So not necessarily related to hdd errors. -- "If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing." --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120812171318.GA20524@tal