On Wed, 2013-01-16 at 10:29 +0100, Michel Dänzer wrote:
> On Die, 2013-01-15 at 22:33 +0100, Martin Kuball wrote:
> > Am Tuesday 15 January 2013 schrieb Michel Dänzer:
> > > On Mon, 2013-01-14 at 19:47 +0100, Martin Kuball wrote:
> > > >
> > > > After spending to much time figuring out what's go
On Die, 2013-01-15 at 22:33 +0100, Martin Kuball wrote:
> Am Tuesday 15 January 2013 schrieb Michel Dänzer:
> > On Mon, 2013-01-14 at 19:47 +0100, Martin Kuball wrote:
> > >
> > > After spending to much time figuring out what's going on, I have at
> > > least a working system. The error is trigg
* Martin Kuball [2013-01-15 22:57 +0100]:
> Am Tuesday 15 January 2013 schrieb Elimar Riesebieter:
[...]
> > I experienced such "bugs" as a misbehavior of networkmanager. I
> > always purge all the nm stuff, use /etc/network/interfaces and
> > for laptops a heaviliy customized netenv package.
>
Am Tuesday 15 January 2013 schrieb Elimar Riesebieter:
> * Michel Dänzer [2013-01-15 09:58 +0100]:
>
> > On Mon, 2013-01-14 at 19:47 +0100, Martin Kuball wrote:
> > >
> > > After spending to much time figuring out what's going on, I have at
> > > least a working system. The error is triggered w
Am Tuesday 15 January 2013 schrieb Michel Dänzer:
> On Mon, 2013-01-14 at 19:47 +0100, Martin Kuball wrote:
> >
> > After spending to much time figuring out what's going on, I have at
> > least a working system. The error is triggered when laptop-mode is
> > setting the auto negotiation attribute
* Michel Dänzer [2013-01-15 09:58 +0100]:
> On Mon, 2013-01-14 at 19:47 +0100, Martin Kuball wrote:
> >
> > After spending to much time figuring out what's going on, I have at
> > least a working system. The error is triggered when laptop-mode is
> > setting the auto negotiation attribute. So i
On Mon, 2013-01-14 at 19:47 +0100, Martin Kuball wrote:
>
> After spending to much time figuring out what's going on, I have at
> least a working system. The error is triggered when laptop-mode is
> setting the auto negotiation attribute. So it may be a hardware error
> after all. Because if I br
Am Thursday 03 January 2013 schrieb Martin Kuball:
> Am Wednesday 02 January 2013 schrieb Martin Kuball:
> > Am Wednesday 02 January 2013 schrieb Michel Dänzer:
> > > On Mit, 2013-01-02 at 14:40 +0100, Martin Kuball wrote:
> > > > Am Wednesday 02 January 2013 schrieb Michel Dänzer:
> > > > > On Di
Am Wednesday 02 January 2013 schrieb Martin Kuball:
> Am Wednesday 02 January 2013 schrieb Michel Dänzer:
> > On Mit, 2013-01-02 at 14:40 +0100, Martin Kuball wrote:
> > > Am Wednesday 02 January 2013 schrieb Michel Dänzer:
> > > > On Die, 2013-01-01 at 21:52 +0100, Martin Kuball wrote:
> > > > >
Am Wednesday 02 January 2013 schrieb Michel Dänzer:
> On Mit, 2013-01-02 at 14:40 +0100, Martin Kuball wrote:
> > Am Wednesday 02 January 2013 schrieb Michel Dänzer:
> > > On Die, 2013-01-01 at 21:52 +0100, Martin Kuball wrote:
> > > > Hello,
> > > >
> > > > I made some progress. After switching
On Mit, 2013-01-02 at 14:40 +0100, Martin Kuball wrote:
> Am Wednesday 02 January 2013 schrieb Michel Dänzer:
> > On Die, 2013-01-01 at 21:52 +0100, Martin Kuball wrote:
> > > Hello,
> > >
> > > I made some progress. After switching update to sequential boot I saw
> > > the following exception:
Am Wednesday 02 January 2013 schrieb Michel Dänzer:
> On Die, 2013-01-01 at 21:52 +0100, Martin Kuball wrote:
> > Hello,
> >
> > I made some progress. After switching update to sequential boot I saw
> > the following exception:
> >
> > machine check in kernel mode
> > caused by (from SRR1=49030)
On Die, 2013-01-01 at 21:52 +0100, Martin Kuball wrote:
> Hello,
>
> I made some progress. After switching update to sequential boot I saw
> the following exception:
>
> machine check in kernel mode
> caused by (from SRR1=49030): Transfer error ack signal
> oops: machine check, sig: 7 [#1]
>
>
Hello,
I made some progress. After switching update to sequential boot I saw the
following exception:
machine check in kernel mode
caused by (from SRR1=49030): Transfer error ack signal
oops: machine check, sig: 7 [#1]
the top entry of the call trace is:
gem_ioct
Hi,
Happy new year to all of you.
My old G3 iBook running debian testing stopped booting after the last update.
The last two lines of output are:
[ok] Cleaning up temporary files
[] Setting kernel variables ...[22.330585] input: Macintosh mouse
button emulation as /devices/virtual/
15 matches
Mail list logo