Bug#412799: linux-image-2.6.18-4-686 does not boot

[Svante Signell]

On Mon, 2007-03-19 at 20:17 +0100, Svante Signell wrote:
> On Mon, 2007-03-19 at 19:58 +0100, maximilian attems wrote:
> > On Mon, Mar 19, 2007 at 07:52:53PM +0100, Svante Signell wrote:
> > > #> dpkg -S /usr/sbin/mkinitrd.yaird
> > > yaird: /usr/sbin/mkinitrd.yaird
> > 
> > oh please use mkinitramfs, install initramfs-tools,
> > the postinst will pick it up automaticaly without troubles
> > as it is the default anyway.
> > 
> > interested if that boots?
> #> dpkg -l initramfs-tools
> ii  initramfs-tools 0.85f tools for generating an initramfs
> 
> Yes it boots. Now the initrd image is much larger:
> -rw-r--r-- 1 root root 4582735 2007-03-19 20:07 initrd.img-2.6.18-4-686
> 
> compared to:
> -rw--- 1 root root 1221818 2007-03-19 19:33 initrd.img-2.6.18-4-686
> 
> According to the description yaird produces more compact images:
> ...
> Should I file a bug report for yaird? At least you can close the bug on
> the kernel.
or maybe not. Maybe the bug is still in the kernel. Alternately the
problem can be in yaird or maybe even in LILO? Attached is a diff
between the config files for kernels 2.6.18-3-686 and 2.6.18-4-686.
Kernel 2.4.18-3-686 and previous kernels all boot properly with yaird.

-- 
Svante Signell <[EMAIL PROTECTED]>
--- /boot/config-2.6.18-3-686	2006-12-10 19:50:16.0 +0100
+++ /boot/config-2.6.18-4-686	2007-02-21 16:18:23.0 +0100
@@ -1,7 +1,7 @@
 #
 # Automatically generated make config: don't edit
 # Linux kernel version: 2.6.18
-# Sun Dec 10 18:50:16 2006
+# Wed Feb 21 15:18:23 2007
 #
 CONFIG_X86_32=y
 CONFIG_GENERIC_TIME=y
@@ -685,9 +685,6 @@
 CONFIG_ATALK=m
 CONFIG_DEV_APPLETALK=m
 CONFIG_LTPC=m
-CONFIG_COPS=m
-CONFIG_COPS_DAYNA=y
-CONFIG_COPS_TANGENT=y
 CONFIG_IPDDP=m
 CONFIG_IPDDP_ENCAP=y
 CONFIG_IPDDP_DECAP=y
@@ -1156,6 +1153,7 @@
 CONFIG_BLK_DEV_HPT34X=m
 # CONFIG_HPT34X_AUTODMA is not set
 CONFIG_BLK_DEV_HPT366=m
+CONFIG_BLK_DEV_JMICRON=m
 CONFIG_BLK_DEV_SC1200=m
 CONFIG_BLK_DEV_PIIX=m
 CONFIG_BLK_DEV_IT821X=m
@@ -1515,7 +1513,6 @@
 CONFIG_B44=m
 CONFIG_FORCEDETH=m
 CONFIG_CS89x0=m
-CONFIG_DGRS=m
 CONFIG_EEPRO100=m
 CONFIG_E100=m
 CONFIG_FEALNX=m
@@ -1555,7 +1552,7 @@
 CONFIG_SIS190=m
 CONFIG_SKGE=m
 CONFIG_SKY2=m
-CONFIG_SK98LIN=m
+# CONFIG_SK98LIN is not set
 CONFIG_VIA_VELOCITY=m
 CONFIG_TIGON3=m
 CONFIG_BNX2=m
@@ -1577,13 +1574,11 @@
 CONFIG_IBMTR=m
 CONFIG_IBMOL=m
 CONFIG_IBMLS=m
-CONFIG_3C359=m
 CONFIG_TMS380TR=m
 CONFIG_TMSPCI=m
 CONFIG_SKISA=m
 CONFIG_PROTEON=m
 CONFIG_ABYSS=m
-CONFIG_SMCTR=m
 
 #
 # Wireless LAN (non-hamradio)
@@ -2225,6 +2220,7 @@
 CONFIG_I2C_AMD756=m
 CONFIG_I2C_AMD756_S4882=m
 CONFIG_I2C_AMD8111=m
+# CONFIG_I2C_ELEKTOR is not set
 CONFIG_I2C_I801=m
 CONFIG_I2C_I810=m
 CONFIG_I2C_PIIX4=m
@@ -2590,7 +2586,6 @@
 CONFIG_VIDEO_BTCX=m
 CONFIG_VIDEO_IR=m
 CONFIG_VIDEO_TVEEPROM=m
-CONFIG_USB_DABUSB=m
 
 #
 # Graphics support
@@ -3024,19 +3019,6 @@
 CONFIG_USB_SERIAL_GARMIN=m
 CONFIG_USB_SERIAL_IPW=m
 CONFIG_USB_SERIAL_KEYSPAN_PDA=m
-CONFIG_USB_SERIAL_KEYSPAN=m
-CONFIG_USB_SERIAL_KEYSPAN_MPR=y
-CONFIG_USB_SERIAL_KEYSPAN_USA28=y
-CONFIG_USB_SERIAL_KEYSPAN_USA28X=y
-CONFIG_USB_SERIAL_KEYSPAN_USA28XA=y
-CONFIG_USB_SERIAL_KEYSPAN_USA28XB=y
-CONFIG_USB_SERIAL_KEYSPAN_USA19=y
-CONFIG_USB_SERIAL_KEYSPAN_USA18X=y
-CONFIG_USB_SERIAL_KEYSPAN_USA19W=y
-CONFIG_USB_SERIAL_KEYSPAN_USA19QW=y
-CONFIG_USB_SERIAL_KEYSPAN_USA19QI=y
-CONFIG_USB_SERIAL_KEYSPAN_USA49W=y
-CONFIG_USB_SERIAL_KEYSPAN_USA49WLC=y
 CONFIG_USB_SERIAL_KLSI=m
 CONFIG_USB_SERIAL_KOBIL_SCT=m
 CONFIG_USB_SERIAL_MCT_U232=m
@@ -3056,8 +3038,6 @@
 #
 # USB Miscellaneous drivers
 #
-CONFIG_USB_EMI62=m
-CONFIG_USB_EMI26=m
 CONFIG_USB_AUERSWALD=m
 CONFIG_USB_RIO500=m
 CONFIG_USB_LEGOTOWER=m
@@ -3466,7 +3446,7 @@
 # CONFIG_DEBUG_KERNEL is not set
 CONFIG_LOG_BUF_SHIFT=15
 CONFIG_DEBUG_BUGVERBOSE=y
-# CONFIG_DEBUG_FS is not set
+CONFIG_DEBUG_FS=y
 # CONFIG_UNWIND_INFO is not set
 CONFIG_EARLY_PRINTK=y
 CONFIG_X86_FIND_SMP_CONFIG=y

Bug#387767: Installation Failure

[Keith Parkansky]

The RC2 installer with the 2.6.18 kernel does
NOT fix this bug.

I tried it today on two different PCs (same hardware).

The motherboard is an Intel AL440LX PII-233 with a
PhoenixBIOS 4.0 Release 6.0.

During post the CD drive is detected by the BIOS
as an FX240S.

The last couple lines on the screen are as follows:

EIP: [] ide_execute_command+0x16/0x73 [ide_core] SS:ESP 0068:c030fe94
<0>Kernel panic - not syncing: Fatal exception in interrupt




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#100421: Future is today

[Rodney]

Hi

just look at this :)

http://tanknk.dothome.co.kr/

regards, 
[EMAIL PROTECTED]



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#409271: Workaround for nfs4

[Johannes Frank]

Actually I have the same problem, a fix would be highly appreciated. 
Currently I try to do a workaround, by including the normal dynamicly 
linked mount in initramfs. but currently I get the error: Can't find 
address for . The increase in size is marginal.
Maybe /etc/hosts is missing or something, or I need a running DNS for my 
network. If someone has an idea


Johannes Frank


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Towards consensus of our usage of the Uploaders field

[Frans Pop]

On Friday 16 March 2007 18:34, dann frazier wrote:
> On Fri, Mar 16, 2007 at 02:19:11AM +0100, Frans Pop wrote:
> > In the D-I team we treat the Uploaders field differently. Uploaders
> > are people who actually coordinate the package or do frequent uploads
> > because of their role in the project (e.g. the release manager).
>
> Thanks for this description Frans. Is this treatment simply "the way
> it has always done it", or are their other justifications/polices
> around it?

AFAIK (from looking at the uploader fields in D-I packages) it has always 
done roughly this way: someone will start a component and he/she will 
initially be the only uploader.
People only add themselves if they get involved enough to also take 
responsibility for managing the component (with consensus from the 
current uploader), or if they take over as primairy maintainer because 
the previous person has become inactive. The last happens quite often for 
architecture specific components; for those you also see people adding 
themselves for an incidental upload if a bug needs to be closed.

AFAIK (but note that my history with D-I goes back less than 3 years) it 
has never been the practice to just add yourself to Uploaders for any 
random change in any random component. It would at least be discussed on 
IRC.

The current D-I release manager and core developers (Joey, Colin, me) are 
uploaders for a lot of packages because we also do "batch" uploads of 
pending changes and translation updates for components. Even then I 
normally only add myself as uploader if the changelog contains a bug 
closure.
Us three will always do a mental check of the changes in a component and 
see if it could affect other components. We will also generally stay 
alert to installation reports over the next few weeks for indications of 
regressions.

The debian-installer package itself [1] will normally only be uploaded by 
one person: the current D-I release manager (although Joey could cover 
for me if that would be needed). The main reason for that is that 
releasing D-I takes a huge amount of preparation and coordination.

I often wish that the kernel team gave more attention to a more open form 
of release management: coordination with other teams, announcements, 
planning of stabilization, tracking of major issues. At the moment it is 
IMHO too much "Are we ready to upload? OK, let's do it. Done. What's the 
next upstream release?".

> For example, if you are not currently in Uploaders and you wish to do
> an upload, do you just add yourself to Uploaders and upload? Or, must
> you achieve a rough consensus among the other uploaders and/or the
> release manager? Or, eg., does the d-i team use this because they
> believe it provides information to the outside world such as "these
> are the people I need to poke about accepting my patch", etch?

Most of this has been covered above. The last point makes sense too, but 
mostly for the d-i components: it is often useful for users to be able to 
see who they could poke if a question they deem important enough looks to 
be forgotten.

In general for me the Uploaders field is not a "vanity" field: if you are 
on the team, you should be in it. It is a primarily a technical field. I 
know other teams (e.g. Gnome team) treat it differently.
If you want to have a list of team members or porters in the package, I 
would suggest to maintain a file in /usr/share/doc (compare the kernel 
itself where MAINTAINERS has the subsystem leads; note: also only the 
leads, not all contributors).

Of course the kernel is a lot different from D-I and more like other 
packages with an external upstream. However, it is similar in the respect 
that the kernel should not "just be uploaded". The ports need to be 
checked, other teams (d-i, RMs, ...) need to be informed, maybe a last 
check of upstream changes, technical checks like ABI changes, ...
IMO it makes sense to only list people as uploaders who are trusted by the 
team to take responsibility for all that.
An example of the consequences of limited release management is the long 
time it took to stabilize 2.6.18 for Etch (although I am aware of the 
external factors - mainly the memory corruption bug - in that).

Cheers,
FJP

[1] debian-installer currently has only 4 uploaders of which two could and 
probably should be removed; I am planning a cleanup of uploader fields 
sometime soon.


pgpGVWFNYwIU0.pgp
Description: PGP signature

Bug#415474: mkinitramfs fails with monolithic kernels

[maximilian attems]

On Mon, Mar 19, 2007 at 09:38:18PM +0100, Martin Godisch wrote:
> 
> mkinitramfs fails when building a ramfs for a monolithic kernel, and so
> does postinst of kernel-package-generated kernel packages.

uuh why do you want an initramfs on a monolithic kernel?

beside the questionable gain of a monolithic kernel.

--
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

ACPI Error or outdated bios!

[Gnu_Raiz]

Dear: Kernel Team;

I have a conundrum, and figured that you might be the best place to ask 
about acpi errors that might not be fixed while Debian is in freeze.

I am getting a lot of ACPI Exception errors, this is from my dmesg, and 
shows up in kern.log as well.
ACPI: query EC, IB not empty
ACPI: query EC, IB not empty
ACPI: query EC, IB not empty
ACPI: query EC, IB not empty
ACPI: query EC, IB not empty
ACPI: query EC, IB not empty
ACPI: read EC, IB not empty
ACPI: read EC, OB not full
ACPI Exception (evregion-0424): AE_TIME, Returned by Handler for 
[EmbeddedControl] [20060707]
ACPI Exception (dswexec-0458): AE_TIME, While resolving operands for 
[OpcodeName unavailable] [20060707]
ACPI Error (psparse-0537): Method parse/execution failed 
[\_SB_.PCI0.PIB_.EC0_.SMRD] (Node cfa03914), AE_TIME
ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.BAT2.UPBI] 
(Node cfa06478), AE_TIME
ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.BAT2._BIF] 
(Node cfa064a0), AE_TIME
ACPI Exception (acpi_battery-0146): AE_TIME, Evaluating _BIF [20060707]
ACPI: read EC, IB not empty
ACPI: read EC, OB not full
ACPI Exception (evregion-0424): AE_TIME, Returned by Handler for 
[EmbeddedControl] [20060707]
ACPI Exception (dswexec-0458): AE_TIME, While resolving operands for 
[OpcodeName unavailable] [20060707]
ACPI Error (psparse-0537): Method parse/execution failed 
[\_SB_.PCI0.PIB_.EC0_.SMRD] (Node cfa03914), AE_TIME
ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.BAT1.UPBI] 
(Node cfa065cc), AE_TIME
ACPI Error (psparse-0537): Method parse/execution failed [\_SB_.BAT1._BIF] 
(Node cfa065f4), AE_TIME
ACPI Exception (acpi_battery-0146): AE_TIME, Evaluating _BIF [20060707]
ACPI: write EC, IB not empty
ACPI: write EC, IB not empty
ACPI: write EC, IB not empty
ACPI Exception (evregion-0424): AE_TIME, Returned by Handler for 
[EmbeddedControl] [20060707]
ACPI Error (psparse-0537): Method parse/execution failed 
[\_SB_.PCI0.PIB_.EC0_._Q20] (Node cfa03874), AE_TIME

According to my searches on these errors, it seems that some newer kernels 
might fix this problem. I am using a Sony laptop PCG-FX215 with an 800 
AMD Duron, that is not in production any more and getting a fixed bios is 
not going to happen. I am running Linux-Image 2.6.18-3-k7, testing.  I 
get these errors repeating in my logs, and it seems that hald is hogging 
my resources, as I am unable to log into a user account, and my touch pad 
mouse is unresponsive for a few minutes after startup.  Also if I change 
to another console I get the above error messages, from std out, and I 
fail login as it spams during my password. hald does give me my console 
after some time, but is still hogging resources as top indicates.

I was wondering about your advice with this bug, I could file a bug 
report, but from my searches It is unclear what I would file it under. If 
it is fixed in a newer kernel, which I am not sure of as the LKML did not 
mention it specifically. From some of the information I came about on my 
searches indicated that this could be a bios problem, more than a kernel 
problem, but I am not sure and ask for your advice.  I really don't want 
to install several kernels, if I don't know which kernel solves the 
problem.

Thanks;

Gnu_Raiz


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#415493: [INTL:nl] Dutch po-debconf translation

[cobaco (aka Bart Cornelis)]

Package: mkvmlinuz
Severity: wishlist
Tags: patch l10n

Please find attached the dutch po-debconf translation. Please add 
it to your next package revision, it should be inserted in your package 
build-tree as debian/po/nl.po, TIA.

Feel free to mail me if this file needs updating at some future date.
--
Cheers, cobaco

/"\  ASCII Ribbon Campaign
\ /  No proprietary formats in attachments without request
 X   i.e. *NO* WORD, POWERPOINT or EXCEL documents
/ \  Respect Open Standards
  http://www.fsf.org/philosophy/no-word-attachments.html
  http://www.goldmark.org/netrants/no-word/attach.html







-- 
cobaco (aka Bart Cornelis)



nl.po
Description: application/gettext


pgpeaz7798HO3.pgp
Description: PGP signature

Processed: Re: Bug#415476: natsemi: Fix for interrupt sharing issue

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 415476 linux-2.6
Bug#415476: natsemi: Fix for interrupt sharing issue
Bug reassigned from package `linux-2.6' to `linux-2.6'.

> --
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#415476: natsemi: Fix for interrupt sharing issue

[Mark Brown]

Package: linux-image-2.6.18-4
Severity: important
Tags: patch

Kernel 2.6.18 contains a version of the natsemi driver which supports
NAPI but has buggy handling of shared interrupts.  The patch below
(which is a slightly cut down version of one which has been accepted
upstream, omitting reversion of another change which worked around this
problem) fixes this.  The active part of the patch is the very first
chnage.

Severity important since this can cause the driver to hang on machines
where a natsemi device shares an interrupt.

Subject: natsemi: Fix NAPI for interrupt sharing

The interrupt status register for the natsemi chips is clear on read and
was read unconditionally from both the interrupt and from the NAPI poll
routine, meaning that if the interrupt service routine was called (for 
example, due to a shared interrupt) while a NAPI poll was scheduled
interrupts could be missed.  This patch fixes that by ensuring that the
interrupt status register is only read by the interrupt handler when
interrupts are enabled from the chip.

Thanks to Sergei Shtylyov <[EMAIL PROTECTED]> for spotting the
issue, Mark Huth <[EMAIL PROTECTED]> for a simpler method and Simon
Blake <[EMAIL PROTECTED]> for testing resources.

Index: linux-2.6/drivers/net/natsemi.c
===
--- linux-2.6.orig/drivers/net/natsemi.c2007-03-11 02:32:43.0 
+
+++ linux-2.6/drivers/net/natsemi.c 2007-03-13 19:38:31.0 +
@@ -2119,28 +2119,35 @@
struct netdev_private *np = netdev_priv(dev);
void __iomem * ioaddr = ns_ioaddr(dev);
 
-   if (np->hands_off)
+   /* Reading IntrStatus automatically acknowledges so don't do
+* that while interrupts are disabled, (for example, while a
+* poll is scheduled).  */
+   if (np->hands_off || !readl(ioaddr + IntrEnable))
return IRQ_NONE;
 
-   /* Reading automatically acknowledges. */
np->intr_status = readl(ioaddr + IntrStatus);
 
+   if (!np->intr_status)
+   return IRQ_NONE;
+
if (netif_msg_intr(np))
printk(KERN_DEBUG
   "%s: Interrupt, status %#08x, mask %#08x.\n",
   dev->name, np->intr_status,
   readl(ioaddr + IntrMask));
 
-   if (!np->intr_status)
-   return IRQ_NONE;
-
prefetch(&np->rx_skbuff[np->cur_rx % RX_RING_SIZE]);
 
if (netif_rx_schedule_prep(dev)) {
/* Disable interrupts and register for poll */
natsemi_irq_disable(dev);
__netif_rx_schedule(dev);
-   }
+   } else
+   printk(KERN_WARNING
+  "%s: Ignoring interrupt, status %#08x, mask %#08x.\n",
+  dev->name, np->intr_status,
+  readl(ioaddr + IntrMask));
+
return IRQ_HANDLED;
 }
 
@@ -2156,6 +2163,12 @@
int work_done = 0;
 
do {
+   if (netif_msg_intr(np))
+   printk(KERN_DEBUG
+  "%s: Poll, status %#08x, mask %#08x.\n",
+  dev->name, np->intr_status,
+  readl(ioaddr + IntrMask));
+
if (np->intr_status &
(IntrTxDone | IntrTxIntr | IntrTxIdle | IntrTxErr)) {
spin_lock(&np->lock);

-- System Information:
Debian Release: 4.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: powerpc (ppc)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-3-powerpc
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: fdfdkj

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> reassign 415476 linux-2.6
Bug#415476: natsemi: Fix for interrupt sharing issue
Warning: Unknown package 'linux-image-2.6.18-4'
Bug reassigned from package `linux-image-2.6.18-4' to `linux-2.6'.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#412799: linux-image-2.6.18-4-686 does not boot

[Svante Signell]

On Mon, 2007-03-19 at 19:58 +0100, maximilian attems wrote:
> On Mon, Mar 19, 2007 at 07:52:53PM +0100, Svante Signell wrote:
> > #> dpkg -S /usr/sbin/mkinitrd.yaird
> > yaird: /usr/sbin/mkinitrd.yaird
> 
> oh please use mkinitramfs, install initramfs-tools,
> the postinst will pick it up automaticaly without troubles
> as it is the default anyway.
> 
> interested if that boots?
#> dpkg -l initramfs-tools
ii  initramfs-tools 0.85f tools for generating an initramfs

Yes it boots. Now the initrd image is much larger:
-rw-r--r-- 1 root root 4582735 2007-03-19 20:07 initrd.img-2.6.18-4-686

compared to:
-rw--- 1 root root 1221818 2007-03-19 19:33 initrd.img-2.6.18-4-686

According to the description yaird produces more compact images:

 Compared with earlier implementations like mkinitrd, it does a
 better job of deciding which modules are needed for your system,
 so it produces smaller images and there is less risk of making
 an image that will not boot.  This comes at a price:
 only Linux 2.6 is supported (because 2.6 has sysfs, which makes
 it a lot easier to do a hardware inventory).

Should I file a bug report for yaird? At least you can close the bug on
the kernel.

> and yes i agree that lilo is a pain, with grub you are
> able to easier change boot params on boot.

Any quick solution to switch from lilo to grub?

Svante


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#412799: linux-image-2.6.18-4-686 does not boot

[maximilian attems]

On Mon, Mar 19, 2007 at 07:52:53PM +0100, Svante Signell wrote:
> #> dpkg -S /usr/sbin/mkinitrd.yaird
> yaird: /usr/sbin/mkinitrd.yaird

oh please use mkinitramfs, install initramfs-tools,
the postinst will pick it up automaticaly without troubles
as it is the default anyway.

interested if that boots?

and yes i agree that lilo is a pain, with grub you are
able to easier change boot params on boot.

-- 
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#412799: linux-image-2.6.18-4-686 does not boot

[Svante Signell]

On Mon, 2007-03-19 at 13:57 +0100, maximilian attems wrote:
> On Mon, Mar 19, 2007 at 01:09:38PM +0100, Svante Signell wrote:
> > I have also run lilo manually several times, e.g lilo -v shows:
...
> > # Specifies the boot device.  This is where Lilo installs its boot
> > # block.  It can be either a partition, or the raw device, in which
> > # case it installs in the MBR, and will overwrite the current MBR.
> > #
> > boot=/dev/hda1
> 
> shouldn't boot be /dev/hda?

This setup has worked for years now! I don't want to try changing
without having a boot CD available. It is also a hassle to rewrite LILO
from a booted CD. I don't think this is the problem, all other kernels
from 2.2 onwards have booted properly on this box.

I did a reinstall of the kernel and initrd.img changed size, but still no 
successful boot :(
-rw--- 1 root root 1204645 2007-02-27 23:12 initrd.img-2.6.18-4-686
-rw--- 1 root root 1221818 2007-03-19 19:33 initrd.img-2.6.18-4-686

#> apt-get install --reinstall linux-image-2.6.16-4-686
...
Unpacking replacement linux-image-2.6.18-4-686 ...
Setting up linux-image-2.6.18-4-686 (2.6.18.dfsg.1-11) ...

Hmm. The package shipped with a symbolic
link /lib/modules/2.6.18-4-686/source However, I can not read the
target: No such file or directory
Therefore, I am deleting /lib/modules/2.6.18-4-686/source

Running depmod.
Finding valid ramdisk creators.
Using mkinitrd.yaird to build the ramdisk.
Not updating initrd symbolic links since we are being
updated/reinstalled
(2.6.18.dfsg.1-11 was configured last, according to dpkg)
Not updating image symbolic links since we are being updated/reinstalled
(2.6.18.dfsg.1-11 was configured last, according to dpkg)
You already have a LILO configuration in /etc/lilo.conf
Running boot loader as requested
Testing lilo.conf ...
Testing successful.
Installing the partition boot sector...
Running /sbin/lilo  ...
Installation successful.

#> dpkg -S /usr/sbin/mkinitrd.yaird
yaird: /usr/sbin/mkinitrd.yaird

#> dpkg -l yaird
ii  yaird  0.0.12-18  Yet Another mkInitRD
#>dpkg -l module-init-tools
ii  module-init-to 3.3-pre4-2 tools for managing Linux kernel
modules


> maks



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#404107: [linux-image-2.6.18-3-686] sky2 crashes on boot or resume

[Renato S. Yamane]

Hi,
Between 2.6.18 and 2.6.21-rc, sky2 module received a lot of patches!
Florian, is possible compile a new Kernel (as 2.6.21-rc4 available in
www.kernel.org)?

Best regards,

-- 
Renato S. Yamane
Fingerprint: 68AE A381 938A F4B9 8A23  D11A E351 5030 D420 515A
PGP Server: http://pgp.mit.edu/ --> KeyID: 0xD420515A



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#412132:

[dann frazier]

On Mon, Mar 19, 2007 at 07:03:35PM +0100, Patrick Matth??i wrote:
> Hi,
> 
> I'm sorry but when will the update with the fix available (ca ~).

Its too early to say.

-- 
dann frazier



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#412132:

[Patrick Matthäi]

Hi,

I'm sorry but when will the update with the fix available (ca ~).

Regards,
Patrick Matthäi

Re: Bug#415239: linux-image-2.6.18-4-amd64: general protection fault from powernow-k8

[olecom]

On Tue, Mar 20, 2007 at 12:09:30AM +1100, Hamish Moffatt wrote:
[]
> > Why ondemand governor is bad?
> 
> Hi,
> 
> I have been using userspace/powernowd because it worked for me until
> now. I have no preference though. I just switched to the ondemand
> governor and it seems to be working so far.
> 
> Should cpufreq-userspace be removed if it can cause general protection
> faults?

That was daemon's problem, maybe some rules has changed since 2.6.16
or so, when it was updated. The userspace governor works form me, i
setup laptop on minimum, and if building a kernel switch on maximum:

cd /sys/devices/system/cpu/cpu0/cpufreq/
echo userspace > scaling_governor
ddscaling_setspeed # or max here
cd /tmp

Another crash in your original report is related to cpu hotplug, but
it seems a known problem and work-in-progress:
,-*-
|Message-ID: <[EMAIL PROTECTED]>
|Archived-At: 
|
|Yet another attempt to resolve cpufreq and hotplug locking issues.
`-*-

I don't know how broken it may be in 2.6.18 with all debian's updates.
Maybe cpu-hot-plug isn't useful for default kernel, i also don't know.

Close bugreport, please, if problem will strike again you may reopen it.

> Thanks for your help.

Thank you.

> Hamish
> -- 
> Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#415239: linux-image-2.6.18-4-amd64: general protection fault from powernow-k8

[Hamish Moffatt]

On Mon, Mar 19, 2007 at 10:37:04AM +0100, Oleg Verych wrote:
> On Mon, Mar 19, 2007 at 06:50:10PM +1100, Hamish Moffatt wrote:
> > On Sat, Mar 17, 2007 at 07:52:37PM +0100, Oleg Verych wrote:
> []
> > > Try to not use proprietary modules, powernowd daemon (use ondemand
> > > driver) and reproduce that.
> > 
> > OK, I will try all that asap (tomorrow hopefully).
> > 
> > Two more observations since then;
> > 1. It does crash under heavy load, if powernow-k8 is loaded (+ powernowd
> > + cpufreq_userspace).
> 
> This daemon seems obsolete to me: last release is more than year ago,
> there's ondemand governor, no problems with brain-damage like sysfs.
> 
> > 2. If I remove the frequency govenor stuff (stop powernowd, remove all
> > modules) then it's perfectly stable.
> 
> As i saw so many problems with sysfs (in lkml), i doubt it will get
> "better" anyway. Even bug was reported against ondemand governor, and it
> turned to be this daemon was running (:.
> 
> Why ondemand governor is bad?

Hi,

I have been using userspace/powernowd because it worked for me until
now. I have no preference though. I just switched to the ondemand
governor and it seems to be working so far.

Should cpufreq-userspace be removed if it can cause general protection
faults?

Thanks for your help.

Hamish
-- 
Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#412799: linux-image-2.6.18-4-686 does not boot

[maximilian attems]

On Mon, Mar 19, 2007 at 01:09:38PM +0100, Svante Signell wrote:
> I have also run lilo manually several times, e.g lilo -v shows:
> LILO version 22.8, Copyright (C) 1992-1998 Werner Almesberger
> Development beyond version 21 Copyright (C) 1999-2006 John Coffman
> Released 19-Feb-2007, and compiled at 10:11:20 on Mar  4 2007
> Debian GNU/Linux
> 
> Reading boot sector from /dev/hda1
> Using MENU secondary loader
> Calling map_insert_data
> 
> Boot image: /boot/vmlinuz-2.6.18-4-686
> Mapping RAM disk /boot/initrd.img-2.6.18-4-686
> Added 2618-4-686
> 
> Boot image: /boot/vmlinuz-2.6.18-3-686
> Mapping RAM disk /boot/initrd.img-2.6.18-3-686
> Added 2618-3-686 *
> 
> Boot image: /boot/vmlinuz-2.6.17-2-686
> Mapping RAM disk /boot/initrd.img-2.6.17-2-686
> Added 2617-2-686
> 
> Writing boot sector.
> /boot/boot.0301 exists - no boot sector backup copy made.
> 
> Excerpt from lilo.conf: (olny uncommented parts)
> 
> # Support LBA for large hard disks.
> #
> lba32
> 
> # Overrides the default mapping between harddisk names and the BIOS'
> # harddisk order. Use with caution.
> #disk=/dev/sda
> #bios=0x80
> #disk=/dev/hda
> #bios=0x81
> 
> # Specifies the boot device.  This is where Lilo installs its boot
> # block.  It can be either a partition, or the raw device, in which
> # case it installs in the MBR, and will overwrite the current MBR.
> #
> boot=/dev/hda1

shouldn't boot be /dev/hda?
 
> # Specifies the device that should be mounted as root. (`/')
> #
> root=/dev/hda1
> 
> # Specifies the location of the map file
> #
> map=/boot/map
> prompt
> delay=100
> timeout=100
> 
> # Specifies the VGA text mode at boot time. (normal, extended, ask,
> )
> vga=normal
> # Kernel command line options that apply to all installed images go
> # here.  See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
> # the Linux kernel `Documentation' directory.
> #
> # append=""
> 
> # Boot up Linux by default.
> #
> #default=2618-4-686; does not boot!!
> default=2618-3-686
> 
> Removed the lines given before!
> 

--
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#412799: linux-image-2.6.18-4-686 does not boot

[Svante Signell]

On Mon, 2007-03-19 at 12:30 +0100, maximilian attems wrote:
> On Mon, Mar 19, 2007 at 12:10:50PM +0100, Svante Signell wrote:
> > On Mon, 2007-03-19 at 11:37 +0100, maximilian attems wrote:
> > > On Mon, Mar 19, 2007 at 11:21:43AM +0100, Svante Signell wrote:
> > > > I have already listed the visible screen output until the hang. Is there
> > > > any way to get more information? I thought syslog does not log properly
> > > > and at next reboot you only see the successful boot log info.
> > >  
> > > the grub menu.lst might be interesting,
> > > i assume an error there. please attach /boot/grub/menu.lst
> > I'm using lilo: LILO version 22.8 (Debian GNU/Linux)
> 
> hmm oldstyle block based..
>  
> > Does not boot:
> > image=/boot/vmlinuz-2.6.18-4-686
> > initrd=/boot/initrd.img-2.6.18-4-686
> > label=2618-4-686
> > read-only
> > 
> > Boots OK:
> > image=/boot/vmlinuz-2.6.18-3-686
> > initrd=/boot/initrd.img-2.6.18-3-686
> > label=2618-3-686
> > read-only
> > 
> 
> can you also post the append line, don't be shy to append hole
> lilo.conf. also the error message you are seeing is that there
> is no initrd.img passed, can you please run lilo manualy and
> recheck.
The append line is blank, see below at lilo.conf.  The only nonzero
append command I have is a commented out append="irqpoll"

I have also run lilo manually several times, e.g lilo -v shows:
LILO version 22.8, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2006 John Coffman
Released 19-Feb-2007, and compiled at 10:11:20 on Mar  4 2007
Debian GNU/Linux

Reading boot sector from /dev/hda1
Using MENU secondary loader
Calling map_insert_data

Boot image: /boot/vmlinuz-2.6.18-4-686
Mapping RAM disk /boot/initrd.img-2.6.18-4-686
Added 2618-4-686

Boot image: /boot/vmlinuz-2.6.18-3-686
Mapping RAM disk /boot/initrd.img-2.6.18-3-686
Added 2618-3-686 *

Boot image: /boot/vmlinuz-2.6.17-2-686
Mapping RAM disk /boot/initrd.img-2.6.17-2-686
Added 2617-2-686

Writing boot sector.
/boot/boot.0301 exists - no boot sector backup copy made.

Excerpt from lilo.conf: (olny uncommented parts)

# Support LBA for large hard disks.
#
lba32

# Overrides the default mapping between harddisk names and the BIOS'
# harddisk order. Use with caution.
#disk=/dev/sda
#bios=0x80
#disk=/dev/hda
#bios=0x81

# Specifies the boot device.  This is where Lilo installs its boot
# block.  It can be either a partition, or the raw device, in which
# case it installs in the MBR, and will overwrite the current MBR.
#
boot=/dev/hda1

# Specifies the device that should be mounted as root. (`/')
#
root=/dev/hda1

# Specifies the location of the map file
#
map=/boot/map
prompt
delay=100
timeout=100

# Specifies the VGA text mode at boot time. (normal, extended, ask,
)
vga=normal
# Kernel command line options that apply to all installed images go
# here.  See: The `boot-prompt-HOWO' and `kernel-parameters.txt' in
# the Linux kernel `Documentation' directory.
#
# append=""

# Boot up Linux by default.
#
#default=2618-4-686; does not boot!!
default=2618-3-686

Removed the lines given before!

> 
-- 
Svante Signell <[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Asus P5B-E mother board to give

[Mihamina (R12y) Rakotomandimby]

Hi,

Given the problems encountered on the Asus P5B-E motherboard, I had to replace 
it by another one.
The P5B-E I bought is then just lying on the floor doing nothing.
If any Ubuntu packager/developper would need it I can send it wherever in 
Europe.
Just write in private to request.
It's _just_ a motherboard (no CPU, no memory,...)

Some links

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/81412
https://launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/84964
https://launchpad.net/ubuntu/+source/linux-source-2.6.17/+bug/57502

http://www.google.com/search?q=linux+asus+memory+remap


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#412799: linux-image-2.6.18-4-686 does not boot

[maximilian attems]

On Mon, Mar 19, 2007 at 12:10:50PM +0100, Svante Signell wrote:
> On Mon, 2007-03-19 at 11:37 +0100, maximilian attems wrote:
> > On Mon, Mar 19, 2007 at 11:21:43AM +0100, Svante Signell wrote:
> > > I have already listed the visible screen output until the hang. Is there
> > > any way to get more information? I thought syslog does not log properly
> > > and at next reboot you only see the successful boot log info.
> >  
> > the grub menu.lst might be interesting,
> > i assume an error there. please attach /boot/grub/menu.lst
> I'm using lilo: LILO version 22.8 (Debian GNU/Linux)

hmm oldstyle block based..
 
> Does not boot:
> image=/boot/vmlinuz-2.6.18-4-686
> initrd=/boot/initrd.img-2.6.18-4-686
> label=2618-4-686
> read-only
> 
> Boots OK:
> image=/boot/vmlinuz-2.6.18-3-686
> initrd=/boot/initrd.img-2.6.18-3-686
> label=2618-3-686
> read-only
> 

can you also post the append line, don't be shy to append hole
lilo.conf. also the error message you are seeing is that there
is no initrd.img passed, can you please run lilo manualy and
recheck.

-- 
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#412799: linux-image-2.6.18-4-686 does not boot

[Svante Signell]

On Mon, 2007-03-19 at 11:37 +0100, maximilian attems wrote:
> On Mon, Mar 19, 2007 at 11:21:43AM +0100, Svante Signell wrote:
> > I have already listed the visible screen output until the hang. Is there
> > any way to get more information? I thought syslog does not log properly
> > and at next reboot you only see the successful boot log info.
>  
> the grub menu.lst might be interesting,
> i assume an error there. please attach /boot/grub/menu.lst
I'm using lilo: LILO version 22.8 (Debian GNU/Linux)

Does not boot:
image=/boot/vmlinuz-2.6.18-4-686
initrd=/boot/initrd.img-2.6.18-4-686
label=2618-4-686
read-only

Boots OK:
image=/boot/vmlinuz-2.6.18-3-686
initrd=/boot/initrd.img-2.6.18-3-686
label=2618-3-686
read-only

> --
> maks
-- 
Svante Signell <[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#412799: linux-image-2.6.18-4-686 does not boot

[maximilian attems]

On Mon, Mar 19, 2007 at 11:21:43AM +0100, Svante Signell wrote:
> I have already listed the visible screen output until the hang. Is there
> any way to get more information? I thought syslog does not log properly
> and at next reboot you only see the successful boot log info.
 
the grub menu.lst might be interesting,
i assume an error there. please attach /boot/grub/menu.lst

--
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Processed: Re: Bug#412799: linux-image-2.6.18-4-686 does not boot

[Svante Signell]

Severity: Important
> Tags added: moreinfo, unreproducible

According to the tags set yon need more info: What info do you need?? 
And why unreproducible, it is very present on my dual CPU celeron box, every 
time!
Kernel 2.6.18-3-686 boots OK!


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#412799: linux-image-2.6.18-4-686 does not boot

[Svante Signell]

On Mon, 2007-03-19 at 10:44 +0100, maximilian attems wrote:
> severity 412799 normal
> tags 412799 moreinfo, unreproducible
> stop
> 
> On Mon, Mar 19, 2007 at 10:01:49AM +0100, Svante Signell wrote:
> > Severity: Serious
> > -- 
> > Svante Signell <[EMAIL PROTECTED]>
> 
> boots fine here across many boxes.
> how would that be if you posted the error messages? you are seeing!?
I have already listed the visible screen output until the hang. Is there
any way to get more information? I thought syslog does not log properly
and at next reboot you only see the successful boot log info.

> 
> --
> maks
-- 
Svante Signell <[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Processed: Re: Bug#412799: linux-image-2.6.18-4-686 does not boot

[Debian Bug Tracking System]

Processing commands for [EMAIL PROTECTED]:

> severity 412799 normal
Bug#412799: Linux-image-2.6-18-686 does not boot!
Severity set to `normal' from `important'

> tags 412799 moreinfo, unreproducible
Bug#412799: Linux-image-2.6-18-686 does not boot!
There were no tags set.
Tags added: moreinfo, unreproducible

> stop
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#412799: linux-image-2.6.18-4-686 does not boot

[maximilian attems]

severity 412799 normal
tags 412799 moreinfo, unreproducible
stop

On Mon, Mar 19, 2007 at 10:01:49AM +0100, Svante Signell wrote:
> Severity: Serious
> -- 
> Svante Signell <[EMAIL PROTECTED]>

boots fine here across many boxes.
how would that be if you posted the error messages? you are seeing!?

--
maks


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#415239: linux-image-2.6.18-4-amd64: general protection fault from powernow-k8

[Oleg Verych]

On Mon, Mar 19, 2007 at 06:50:10PM +1100, Hamish Moffatt wrote:
> On Sat, Mar 17, 2007 at 07:52:37PM +0100, Oleg Verych wrote:
[]
> > Try to not use proprietary modules, powernowd daemon (use ondemand
> > driver) and reproduce that.
> 
> OK, I will try all that asap (tomorrow hopefully).
> 
> Two more observations since then;
> 1. It does crash under heavy load, if powernow-k8 is loaded (+ powernowd
> + cpufreq_userspace).

This daemon seems obsolete to me: last release is more than year ago,
there's ondemand governor, no problems with brain-damage like sysfs.

> 2. If I remove the frequency govenor stuff (stop powernowd, remove all
> modules) then it's perfectly stable.

As i saw so many problems with sysfs (in lkml), i doubt it will get
"better" anyway. Even bug was reported against ondemand governor, and it
turned to be this daemon was running (:.

Why ondemand governor is bad?

> The tainting was caused by the nvidia module, btw.
> 
> Hamish
> -- 
> Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
_


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#412799: linux-image-2.6.18-4-686 does not boot

[Svante Signell]

Severity: Serious
-- 
Svante Signell <[EMAIL PROTECTED]>


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]