but as a stopgap it's fine.
Cheers,
C.
2016-05-11 13:42 GMT+02:00 Ben Hutchings :
> Control: tag -1 important
>
> On Wed, 2016-05-11 at 10:37 +0200, Christian Pernegger wrote:
>> Hi,
>>
>> I just wanted to say that this bug broke my LIME2 as well, in a get
>> the
Hi,
I just wanted to say that this bug broke my LIME2 as well, in a get
the ladder out, retrieve box, open it, and attach serial cable kind of
way. A lot of the boards affected will be just as headless (for the
A20 at least Debian doesn't even have a local console by default, much
less a graphics
Package: initramfs-tools
Version: 0.92o
Severity: normal
At the moment the order boot scripts are executed in depends solely on
'prereqs' that are - at least in the scripts on my system - rather
static. While the admin can *add* scripts under /etc/initramfs-tools
there is no elegant way to *overr
> Thanks Christian. This is looking like #464962
Yes it is. Looks like a bunch of "fringe" CPUs got downgraded from a
kernel perspective.
> running the 486 flavor is probably the best option for your system.
Ok. I wonder what that'll do to performance ... it's slow enough as it
is. Well, I can a
Package: linux-image-2.6.24-etchnhalf.1-686
Version: 2.6.24-6~etchnhalf.4
Severity: important
The 2.6.24-etchnhalf kernel will not boot at all on my VIA EPIA EK. I
was rather looking forward to being able to use a stable distro kernel
(2.6.18 doesn't support power management on the CPU, which is
> Of course, I'd suggest fscking the filesystem if you haven't already.
Been there, done that, no errors :)
It still would be good to know what the message actually means. I sure
wish there was an error message policy indicating severity ranging
from "I just feel chatty" to "Turn me off and run
> > slab: cache kmem_cache error: free_objects accounting error
> >
> > twice rather soon after booting.
> >
> > What I'd like to know is, should I be worried? Especially, could there
> > have been fs corruption or corruption at the md-raid5 layer?
>
> Is this something you see on every rebo
Package: linux-image-2.6.24-1-amd64
Version: 2.6.24-4
Severity: normal
File: linux-image-2.6.24
Subject line basically says it all ... I've just upgraded my otherwise
lenny install to the 2.6.24 kernel in unstable to see if it solved an
unrelated problem.
I got the error
slab: cache kmem_cache
Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-12
Severity: normal
Modules: speedstep-centrino, cpufreq-ondemand
The frequency cpufreq-info reports conflicting info for the frequency
of the second core:
-f switch (normal user):
always shows max frequency
-w switch (root only):
shows f
Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-12
Followup-For: Bug #402426
After some more fiddling around I remembered that the board's (Asus
P5B-VM DO) BIOS has an option to set the 'ACPI version' to either of
'ACPI1.0', 'ACPI2.0' and 'ACPI3.0'.
With the first setting (and only the
Package: linux-image-2.6.18-4-686
Version: 2.6.18.dfsg.1-12
Followup-For: Bug #402426
I don't get any cpufreq-support either, on a brand new
Core 2 Duo E6600, SL9ZL. That's a minor revision of the
first version with supposedly lower C1E power consumption.
Trying to insert acpi-cpufreq or even sp
A workaround for this is to make sure the driver modules are loaded in
the desired order by putting them in /etc/initramfs-tools/modules.
The "use udev" comment rather misses the point. All reasonably current
installations use udevd, but nothing uses the "stable" /dev/disk
symlink tree by default
Compiling the latest driver from Intel (e1000-7.0.38) out-of-tree
and using that fixes the issue. The in-kernel version is
significantly older.
Any chance of getting an updated version in the Debian kernel?
Regards,
C.
Yes, shutting down the interface is considered a feature or the kernel
will continue routing/accepting traffic.
Strange feature - the system should provide standby power to devices
that are configured for wake-up. This can include one or more NICs,
but also USB devices (keyboards, mice, some web
Package: linux-image-2.6.16-1-k7
Version: 2.6.16-10
Severity: normal
This machine currently hangs instead of rebooting when I do a shutdown -r
or similar. It will go down ok, but after the screen goes dark it does
not beep and show the POST agian like it should - it just hangs there.
Thanks,
C.
Package: linux-image-2.6.16-1-k7
Version: 2.6.16-10
Severity: normal
I have an ASRock 939A8X-M, which reportedly has an ULi 5289 SATA (rev 10)
controller.
When I set the controller to 'non-RAID mode' in BIOS, current Debian kernels
(tried 2.6.15 and 2.6.16) will not boot. GRUB, the kernel and t
16 matches
Mail list logo
