--
---
| Juha Jäykkä, ju...@iki.fi |
| http://www.maths.leeds.ac.uk/~juhaj |
---
signature.asc
Description: This is a digitally signed message part.
Cheers,
Juha
--
---
| Juha Jäykkä, ju...@iki.fi |
| http://www.maths.leeds.ac.uk/~juhaj |
---
signature.asc
Description: This is
; Disabling L0S
Does this have any effect? What are L1 and L0S anyway?
> [ 12.630680] iwlwifi :03:00.0: device EEPROM VER=0x11e, CALIB=0x4
My EEPROM VER=0x11f, but otherwise everything matches.
Cheers,
Juha
--
---
at helps.
Cheers,
Juha
--
---
| Juha Jäykkä, ju...@iki.fi |
| http://www.maths.leeds.ac.uk/~juhaj |
---
signature.asc
Description: This is a digitally signed message part.
newest
wireless tools).
-Juha
--
-------
| Juha Jäykkä, ju...@iki.fi |
| http://www.maths.leeds.ac.uk/~juhaj |
---
signature.asc
Description: Thi
few months before!
-Juha
--
---
| Juha Jäykkä, ju...@iki.fi |
| http://www.maths.leeds.ac.uk/~juhaj |
---
[75926.876147] [ cut here ]
[75926.876171] WARNING
> 0.35, and if I still see this, I will go back to ~0.30 to see if that
> fixes the issue.
Down to 0.33, no help if running kernel 3.2. Now testing 0.33 & 2.6.39...
-Juha
--
---
| Juha Jäykkä, ju
o far as a starting point.
Please CC me if you do.
Cheers,
Juha
--
-------
| Juha Jäykkä, ju...@iki.fi |
| http://www.maths.leeds.ac.uk/~juhaj |
--
, wait 60 seconds – this
should do it) the laptop does NOT fix it, so I concur: the kernel must retain
some bogus information somewhere since the hw has definitely lost its status
info.
Cheers,
-Juha
--
---
| Juha Jäykkä
Package: initramfs-tools
Version: 0.84
Severity: critical
Justification: breaks unrelated software
Initramfs-tools modifies the behaviour of mdadm when mdadm is run from
initramfs.
There is a debconf question for mdadm which defines the raid arrays to start
from
initramfs, however initramfs-too
37,7 @@
sch_tree_unlock(sch);
if (--cl->refcnt == 0)
- cbq_destroy_class(cl);
+ cbq_destroy_class(sch, cl);
return 0;
}
-
--
---
| Juha Jäykkä, [EMAIL PROTECTED]
Package: kernel-source-2.6.10
Version: 2.6.10-5
Severity: important
I am experiencing the same symptoms as bugs #291029, #290964 and #291940. This
time the device
is just an ordinary eth0 (happens to be a prism54) - no tunnels, bridges or
anything. I even
removed all IPv6- and tunneling support
12 matches
Mail list logo
