FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian User

 
 
LinkBack Thread Tools
 
Old 08-12-2012, 04:45 PM
Tony Baldwin
 
Default strange behavior after reboot, iceweasel locking everything up

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.
Or even opening a terminal, for instance, a terminator, hangs, waiting
for iceweasel to finish its task.
It's as though iceweasel has dibs on system resources, and is blocking
other applications from using them, even when iceweasel, itself, is
using very few resources.
Now, when this is happening, I do not see any spikes in resource usage
that would explain slowing or stopping the entire machine while
iceweasel does its thing.
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.

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.

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.

Before the reboot yesterday, the machine was working awesomely.
This is Debian Stable, AMD64, as mentioned on a 2.8ghz x 4core AMD APU
with 16gb ram.
I use Openbox window manager with no DE (which further keeps things
generally humming long quite efficiently).

The machine is only 8 months old, essentially (mobo, cpu, ram all
purchased in January, although the hdd is over a year old, about 1 year
and a half, really, so still not very old).

What is going on here?

I ran aptitude update && safe-upgrade yesterday (had been about a week),
so everything is up to date.

./tony
--
http://www.tonybaldwin.me
all tony, all the time!
3F330C6E



----- End forwarded message -----

--
http://www.tonybaldwin.me
all tony, all the time!
3F330C6E
 
Old 08-12-2012, 04:59 PM
Keith McKenzie
 
Default strange behavior after reboot, iceweasel locking everything up

On 12 August 2012 17:45, Tony Baldwin <tony@tonybaldwin.org> 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.
> Or even opening a terminal, for instance, a terminator, hangs, waiting
> for iceweasel to finish its task.
> It's as though iceweasel has dibs on system resources, and is blocking
> other applications from using them, even when iceweasel, itself, is
> using very few resources.
> Now, when this is happening, I do not see any spikes in resource usage
> that would explain slowing or stopping the entire machine while
> iceweasel does its thing.
> 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.
>
> 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.
>
> 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.
>
> Before the reboot yesterday, the machine was working awesomely.
> This is Debian Stable, AMD64, as mentioned on a 2.8ghz x 4core AMD APU
> with 16gb ram.
> I use Openbox window manager with no DE (which further keeps things
> generally humming long quite efficiently).
>
> The machine is only 8 months old, essentially (mobo, cpu, ram all
> purchased in January, although the hdd is over a year old, about 1 year
> and a half, really, so still not very old).
>
> What is going on here?
>
> I ran aptitude update && safe-upgrade yesterday (had been about a week),
> so everything is up to date.
>
> ./tony

Seems like the disk has some damage from when you pulled the plug.

Probably best to do a file system check from a live medium.



--
Sent from FOSS (Free Open Source Software)
Debian GNU/Linux


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CAL36VG=qVTBg8e2eyYEOvL=yrAkUEmNv=434x9i+oK4=bUcSG Q@mail.gmail.com
 
Old 08-12-2012, 05:13 PM
Chris Bannister
 
Default strange behavior after reboot, iceweasel locking everything up

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-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/20120812171318.GA20524@tal
 
Old 08-12-2012, 05:14 PM
Camaleˇn
 
Default strange behavior after reboot, iceweasel locking everything up

On Sun, 12 Aug 2012 12:45:03 -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.

(...)

> 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.
>
> 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.

(...)

Wow! Just to prevent from a disaster, ensure you have a full and updated backup
copy of your whole data. Then you can proceed with some basic tests:

1/ Check the cabling inside the computer, mainly sata cables, they could have been
moved or be badly seated (ensure that all sata connectors are firmly tighten).

2/ Use sata quality cables when possible. For testing purposes, you can try with a
different sata cable, at least for the device attached to ata6.00 port
("dmesg | grep -i ata6.00" will tell what's hanging there).

3/ Download the disk utilities from the hard disk manufacturer (which usually runs
from an ISO livecd) and scan your hard disks for smart or another errors (always run
soft/non-destructive tests).

4/ From a LiveCD, you can additionaly get the results from "smartcl" long test mode
to compare with the results from step 3/.

And provide the results of all these set of tests :-)

Greetings,

--
Camaleˇn


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/k08o9u$fer$20@dough.gmane.org
 
Old 08-12-2012, 09:05 PM
"tony baldwin"
 
Default strange behavior after reboot, iceweasel locking everything up

On Sun, August 12, 2012 1:13 pm, Chris Bannister wrote:
> 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.

Yes, the only thing I see in htop, for instance, that seems odd is way too
many flash-plugins running, or something.

>
> 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?
>

Well, I can see cpu and memory use in a small conky I keep running,
but I was also looking with htop (not ps). These should all show about the
same thing, anyway. I mean, htop and ps will show processes, whereas
conky only gives % of cpu/ram usage, but otherwise.


>> 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.

I ran a back-up since my initial message.
Manually running fsck now.

./tony

--
http://tonybaldwin.me
all tony, all the time


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 21fc286397eb98d61c62cfe7169886db.squirrel@tonybald win.org">http://lists.debian.org/21fc286397eb98d61c62cfe7169886db.squirrel@tonybald win.org
 
Old 08-12-2012, 09:08 PM
"tony baldwin"
 
Default strange behavior after reboot, iceweasel locking everything up

On Sun, August 12, 2012 1:14 pm, Camale´┐Żn wrote:
> On Sun, 12 Aug 2012 12:45:03 -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.
>
> (...)
>
>> 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.
>>
>> 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.
>
> (...)
>
> Wow! Just to prevent from a disaster, ensure you have a full and updated
> backup
> copy of your whole data. Then you can proceed with some basic tests:
>
> 1/ Check the cabling inside the computer, mainly sata cables, they could
> have been
> moved or be badly seated (ensure that all sata connectors are firmly
> tighten).
>
> 2/ Use sata quality cables when possible. For testing purposes, you can
> try with a
> different sata cable, at least for the device attached to ata6.00 port
> ("dmesg | grep -i ata6.00" will tell what's hanging there).
>
> 3/ Download the disk utilities from the hard disk manufacturer (which
> usually runs
> from an ISO livecd) and scan your hard disks for smart or another errors
> (always run
> soft/non-destructive tests).
>
> 4/ From a LiveCD, you can additionaly get the results from "smartcl" long
> test mode
> to compare with the results from step 3/.
>
> And provide the results of all these set of tests :-)
>
> Greetings,
>
> --
> Camale├│n
>

I did a back-up moments after writing my initial message on this thread.
I rebooted to single-user mode and am running fsck -t ext3 /dev/sda6 right
now (/home partition, where the problem seems to be).
Oddly, I don't have a livecd on hand.
I did my most recent installations all from a usb stick.
(writing from another machine, a laptop with no optical drive to burn a cd).

./tony
--
http://tonybaldwin.me
all tony, all the time


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: e3f894dc60e6f170a18cb917f668cf58.squirrel@tonybald win.org">http://lists.debian.org/e3f894dc60e6f170a18cb917f668cf58.squirrel@tonybald win.org
 
Old 08-12-2012, 10:26 PM
Tony Baldwin
 
Default strange behavior after reboot, iceweasel locking everything up

On Sun, Aug 12, 2012 at 05:08:16PM -0400, tony baldwin wrote:
>
> On Sun, August 12, 2012 1:14 pm, Camale´┐Żn wrote:
> > On Sun, 12 Aug 2012 12:45:03 -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.
> >
> > (...)
> >
> >> 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.
> >>
> >> 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.
> >
> > (...)
> >
>
> I did a back-up moments after writing my initial message on this thread.
> I rebooted to single-user mode and am running fsck -t ext3 /dev/sda6 right
> now (/home partition, where the problem seems to be).
> Oddly, I don't have a livecd on hand.
> I did my most recent installations all from a usb stick.
> (writing from another machine, a laptop with no optical drive to burn a cd).

So, I manually ran fsck, had to do it three time, but I'm now getting a
clean bill of health (log in /var/log/fsck/checkfs says all good) on the
hdd.
Removing mongodb seems to have maybe been a factor (not sure why I had
it installed, anyway...some python thing I was going to play with but
didn't, I believe, required it).

Still having issues with iceweasel, however, being very, very slow in
loading pages and stuff and other applications hanging at the same time.
Even something as innocuous as running "ls" in a terminal will hang and
wait until iceweasel is done, so very weird.
Iceweasel will blank out, too, so I can not even read another tab or
something while waiting for a new tab to load a page, etc.
It does one of those things where, say, if I go to workspace 2 while
iceweasel is loading a page, workspace 2 being always a terminator
terminal full screen, then go back to workspace 1 (iceweasel), I see the
terminal where the iceweasel window should be.
Or if I go to another workspace that's empty, then go back to wordspace
1, I see the top-bar of the iceweasel window, and the empy desktop.
Weird.

./tony
--
http://www.tonybaldwin.me
all tony, all the time!
3F330C6E
 
Old 08-12-2012, 10:39 PM
Tony Baldwin
 
Default strange behavior after reboot, iceweasel locking everything up

On Sun, Aug 12, 2012 at 06:26:34PM -0400, Tony Baldwin wrote:
> On Sun, Aug 12, 2012 at 05:08:16PM -0400, tony baldwin wrote:
> >
> > On Sun, August 12, 2012 1:14 pm, Camale´┐Żn wrote:
> > > On Sun, 12 Aug 2012 12:45:03 -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.
> > >
... clippage ...
>
> So, I manually ran fsck, had to do it three time, but I'm now getting a
> clean bill of health (log in /var/log/fsck/checkfs says all good) on the
> hdd.
> Removing mongodb seems to have maybe been a factor (not sure why I had
> it installed, anyway...some python thing I was going to play with but
> didn't, I believe, required it).
>
> Still having issues with iceweasel, however, being very, very slow in
> loading pages and stuff and other applications hanging at the same time.
> Even something as innocuous as running "ls" in a terminal will hang and
> wait until iceweasel is done, so very weird.
> Iceweasel will blank out, too, so I can not even read another tab or
> something while waiting for a new tab to load a page, etc.
> It does one of those things where, say, if I go to workspace 2 while
> iceweasel is loading a page, workspace 2 being always a terminator
> terminal full screen, then go back to workspace 1 (iceweasel), I see the
> terminal where the iceweasel window should be.
> Or if I go to another workspace that's empty, then go back to wordspace
> 1, I see the top-bar of the iceweasel window, and the empy desktop.
> Weird.

The problem now is definitely something to do with iceweasel.
I do not have the problem of stuff locking up when iceweasel is not
running.
I can use google-chrome without issue (but do not want to use chrome.
I want to use iceweasel. I do not want google tracking me all over the
internet).

./tony
--
http://www.tonybaldwin.me
all tony, all the time!
3F330C6E
 
Old 08-13-2012, 12:10 AM
Tony Baldwin
 
Default strange behavior after reboot, iceweasel locking everything up

On Sun, Aug 12, 2012 at 06:39:05PM -0400, Tony Baldwin wrote:
> On Sun, Aug 12, 2012 at 06:26:34PM -0400, Tony Baldwin wrote:
> > On Sun, Aug 12, 2012 at 05:08:16PM -0400, tony baldwin wrote:
> > >
> > > On Sun, August 12, 2012 1:14 pm, Camale´┐Żn wrote:
> > > > On Sun, 12 Aug 2012 12:45:03 -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.
> > > >
> ... clippage ...
> > Still having issues with iceweasel, however, being very, very slow in
> > loading pages and stuff and other applications hanging at the same time.
> > Even something as innocuous as running "ls" in a terminal will hang and
> > wait until iceweasel is done, so very weird.
> > Iceweasel will blank out, too, so I can not even read another tab or
> > something while waiting for a new tab to load a page, etc.
> > It does one of those things where, say, if I go to workspace 2 while
> > iceweasel is loading a page, workspace 2 being always a terminator
> > terminal full screen, then go back to workspace 1 (iceweasel), I see the
> > terminal where the iceweasel window should be.
> > Or if I go to another workspace that's empty, then go back to wordspace
> > 1, I see the top-bar of the iceweasel window, and the empy desktop.
> > Weird.
>
> The problem now is definitely something to do with iceweasel.
> I do not have the problem of stuff locking up when iceweasel is not
> running.
> I can use google-chrome without issue (but do not want to use chrome.
> I want to use iceweasel. I do not want google tracking me all over the
> internet).

Okay, so I did some digging around, and found out I had 4 xulrunners
installed (I was seeing a lot of xulrunner in htop with iceweasel
running, and wondering if this was somehow at fault).
I completely removed all of them, which, of course, took iceweasel with
it.
I then reinstalled iceweasel (14, from backports) and it brought back
only one xulrunner, being xulrunner-14.
Things seem to be normal now.
It seems perhaps too much xulrunner was maybe the source of the
iceweasel problem.
The hdd problem seems solved, too, from my manual fscking.

./tony
--
http://www.tonybaldwin.me
all tony, all the time!
3F330C6E
 
Old 08-13-2012, 01:43 AM
Tony Baldwin
 
Default strange behavior after reboot, iceweasel locking everything up

On Sun, Aug 12, 2012 at 08:10:07PM -0400, Tony Baldwin wrote:
> On Sun, Aug 12, 2012 at 06:39:05PM -0400, Tony Baldwin wrote:
> > On Sun, Aug 12, 2012 at 06:26:34PM -0400, Tony Baldwin wrote:
> > > On Sun, Aug 12, 2012 at 05:08:16PM -0400, tony baldwin wrote:
> > > >
> > > > On Sun, August 12, 2012 1:14 pm, Camale´┐Żn wrote:
> > > > > On Sun, 12 Aug 2012 12:45:03 -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.
> > > > >
> > ... clippage ...
> >
> > The problem now is definitely something to do with iceweasel.
> > I do not have the problem of stuff locking up when iceweasel is not
> > running.
> > I can use google-chrome without issue (but do not want to use chrome.
> > I want to use iceweasel. I do not want google tracking me all over the
> > internet).
>
> Okay, so I did some digging around, and found out I had 4 xulrunners
> installed (I was seeing a lot of xulrunner in htop with iceweasel
> running, and wondering if this was somehow at fault).
> I completely removed all of them, which, of course, took iceweasel with
> it.
> I then reinstalled iceweasel (14, from backports) and it brought back
> only one xulrunner, being xulrunner-14.
> Things seem to be normal now.

Nope.
Still hanging....iceweasel hangs a long time just trying to grab pages,
and I can't even go to another tab or something.
The whole browser just locks up, for as much as a minute or two,
when trying to load a page.
It's become almost useless.
I mean, what's the point in tabbed browsing if you can't read one tab
while waiting for another to load?

./tony
--
http://www.tonybaldwin.me
all tony, all the time!
3F330C6E
 

Thread Tools




All times are GMT. The time now is 11:36 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright ę2007 - 2008, www.linux-archive.org