Re: Do not know which package bug is in
On Friday 01 April 2016 07:43:51 Robin Oberg wrote:
> On Fri, 2016-04-01 at 12:00 +0100, Oliver Elphick wrote:
> > On Fri, 2016-04-01 at 11:34 +0100, Robin Oberg wrote:
> > > On Fri, 2016-04-01 at 11:21 +0100, Oliver Elphick wrote:
> > > > Intermittent failures like that sound more like hardware
> > > > problems. I
> > > > seem to recall reading that charging devices like that demands
> > > > more power than the computer can supply.
> > > >
> > > > Oliver Elphick
> > >
> > > Would that not mean that the same problem exists in other
> > > operating systems as well? But seeing as it works fine to charge
> > > this old iPhone 4
> > > in Windows, so it does not seem like a hardware malfunction in
> > > this particular case.
> >
> > Not necessarily. It might be that Windows doesn't use a particular
> > area of memory that Linux does.
> >
> > I should go for the other poster's suggestion, of using a powered
> > USB hub. If the failures cease, it was a hardware problem.
>
> Of course, unplugging the device from the USB port stops the crashing,
> because the crashing starts when the device is plugged in to begin
> with...
>
> If "Linux" is programmed to use a particular area of memory that makes
> it crash, then this is a software related issue, isn't it?
>
> Isn't there a log file somewhere that can confirm what the problem is,
> whether or not it is hardware related, or at least which package the
> crash is related to?
>
> //Robin Oberg
I believe another poster had the best idea. Locate another machine and
plug it into your network, doing the config to put your 2nd machine on
the same class D as your troublesome one is, and "ssh -Y
troublesome_machine" from the 2nd one as the same user. If you are
first user on both machines its probably a lot easier.
Then, when the lockup occurs, the last screenfull of a freshly
done "dmesg" o that ligin to the first machines screen should show you
what happened.
I do that here for 5 machines, all using static entries
in /etc/network/interfaces file to define that machines address when
bringing up the port at boot or network restart time,
My /etc/resolv.conf says "host,dns", and an identical /etrc/hosts file
on all machines that links the machine FQDN and its shorthand alias to a
given address.
No dhcp involved, all host file lookup. DNS is defined in the interfaces
file as the address of my router, so a hostname lookup failure is
forwarded to the router, and if it doesn't know, its forwarded to my
ISP's dns servers. Gateway is also defined in the interfaces file as
the routers address. And I never have those protracted waits while dhcp
works. And full internet access from any of those machines sure makes
it handy to keep them up to date. The router of course is running
dd-wrt. Best guard dog ever IMO.
Cheers, Gene Heskett
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Genes Web page <http://geneslinuxbox.net:6309/gene>
Reply to: