On Sun, 2010-11-21 at 21:07 -0500, Jon Williams wrote: > Package: linux-2.6 > Version: 2.6.32-27 > Severity: critical > Tags: d-i upstream > Justification: breaks the whole system You're claiming that: - This bug occurs in the installer - This bug is present in the upstream code - This bug breaks every system where the package is installed How much of the above is actually true? > Symptoms similar to > https://partner-bugzilla.redhat.com/show_bug.cgi?format=multiple&id=603776 > > -- Package-specific info: > ** Kernel log: boot messages should be attached [...] There is no message "Initializing cgroup subsys blkio" at boot, because that feature doesn't actually exist in the Debian package. It is not at all helpful to us if you look for a half-remembered log message and tell us we have the same bug. Think about it - how likely is it that a single bug specifically affects *both* Xen x86 domU systems and UltraSparc systems? We need to see the actual kernel boot log. I suggest you use a serial console to capture it. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.
Attachment:
signature.asc
Description: This is a digitally signed message part