Bug#414322: linux-source-2.6.18: kernel freeze on disk i/o (regression) - Debian

This is a discussion on Bug#414322: linux-source-2.6.18: kernel freeze on disk i/o (regression) - Debian ; Package: linux-source-2.6.18 Version: 2.6.18.dfsg.1-11 Severity: important Hello, I have recently dist-upgraded my workstation from Sarge to Etch. As usual, this operation worked fine, but sadly I get some trouble with the 2.6.18 kernel included into Etch. To begin, I have ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: Bug#414322: linux-source-2.6.18: kernel freeze on disk i/o (regression)

  1. Bug#414322: linux-source-2.6.18: kernel freeze on disk i/o (regression)

    Package: linux-source-2.6.18
    Version: 2.6.18.dfsg.1-11
    Severity: important


    Hello,

    I have recently dist-upgraded my workstation from Sarge to Etch. As usual,
    this operation worked fine, but sadly I get some trouble with the 2.6.18
    kernel included into Etch.


    To begin, I have tried the linux-image-2.6.18-4-k7 but at the first boot
    the kernel freeze completely (the MagicSysReq keys doesn't work). So I
    build my own image from the current linux-source-2.6.18 to test if the
    problem could be eventualy solved with more specific options related to
    my hardware configuration.

    After rebooting without problem on my own linux-image kernel, for a moment
    all seemed to work fine... until the whole system freeze again during the
    configuration process of some new packages I have planned to install.

    Despite the log files contains nothing useful, investigating a bit (eg.
    more reboots and freezes later :-D show that the problem always occurs
    during disk i/o operations, specially when loading the system at boot or
    installing/deinstalling packages (heavy disk usage = faster freeze).


    Of course, I did not have any problem when I use my previous kernel as
    fallback (an old 2.6.8 version build with the Debian Sarge sources).

    Perhaps a disk driver (I use the AIC7XXX kernel module) bug ?


    my lspci :
    00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-760 MP [IGD4-2P]
    System Controller (rev 11)
    00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-760 MP [IGD4-2P]
    AGP Bridge
    00:07.0 ISA bridge: Advanced Micro Devices [AMD] AMD-766 [ViperPlus] ISA
    (rev 02)
    00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-766 [ViperPlus]
    IDE (rev 01)
    00:07.3 Bridge: Advanced Micro Devices [AMD] AMD-766 [ViperPlus] ACPI
    (rev 01)
    00:07.4 USB Controller: Advanced Micro Devices [AMD] AMD-766 [ViperPlus]
    USB (rev 07)
    00:0a.0 SCSI storage controller: Adaptec AHA-3960D / AIC-7899A U160/m
    (rev 01)
    00:0a.1 SCSI storage controller: Adaptec AHA-3960D / AIC-7899A U160/m
    (rev 01)
    00:0c.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
    00:0d.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado]
    (rev 78)
    01:05.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti
    4400] (rev a2)


    Thanx for your help,
    THR4K



    -- System Information:
    Debian Release: 4.0
    APT prefers testing
    APT policy: (500, 'testing')
    Architecture: i386 (i686)
    Shell: /bin/sh linked to /bin/bash
    Kernel: Linux 2.6.8-16.6-tigermp
    Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

    Versions of packages linux-source-2.6.18 depends on:
    ii binutils 2.17-3 The GNU assembler, linker and bina
    ii bzip2 1.0.3-6 high-quality block-sorting file co

    Versions of packages linux-source-2.6.18 recommends:
    ii gcc 4:4.1.1-15 The GNU C compiler
    ii libc6-dev [libc-dev] 2.3.6.ds1-13 GNU C Library: Development Librari
    ii make 3.81-2 The GNU version of the "make" util

    -- no debconf information


    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  2. Bug#414322: linux-source-2.6.18: kernel freeze on disk i/o (regression)

    tags 414322 moreinfo
    stop

    On Sun, Mar 11, 2007 at 12:41:33AM +0100, THR4K wrote:
    >
    > Hello,
    >
    > I have recently dist-upgraded my workstation from Sarge to Etch. As usual,
    > this operation worked fine, but sadly I get some trouble with the 2.6.18
    > kernel included into Etch.
    >
    >
    > To begin, I have tried the linux-image-2.6.18-4-k7 but at the first boot
    > the kernel freeze completely (the MagicSysReq keys doesn't work). So I
    > build my own image from the current linux-source-2.6.18 to test if the
    > problem could be eventualy solved with more specific options related to
    > my hardware configuration.
    >
    > After rebooting without problem on my own linux-image kernel, for a moment
    > all seemed to work fine... until the whole system freeze again during the
    > configuration process of some new packages I have planned to install.
    >
    > Despite the log files contains nothing useful, investigating a bit (eg.
    > more reboots and freezes later :-D show that the problem always occurs
    > during disk i/o operations, specially when loading the system at boot or
    > installing/deinstalling packages (heavy disk usage = faster freeze).
    >
    >
    > Of course, I did not have any problem when I use my previous kernel as
    > fallback (an old 2.6.8 version build with the Debian Sarge sources).
    >
    > Perhaps a disk driver (I use the AIC7XXX kernel module) bug ?
    >


    can you please try the 2.6.20 linux image from trunk buildserver
    see for aptlines -> http://wiki.debian.org/DebianKernel

    if there it doesn't work you'd need to bug upstream in
    bugzilla.kernel.org

    thanks for keeping us posted.

    --
    maks


    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  3. Processed: Re: Bug#414322: linux-source-2.6.18: kernel freeze on disk i/o (regression)

    Processing commands for control@bugs.debian.org:

    > tags 414322 moreinfo

    Bug#414322: linux-source-2.6.18: kernel freeze on disk i/o (regression)
    There were no tags set.
    Tags added: moreinfo

    > stop

    Stopping processing here.

    Please contact me if you need assistance.

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


    --
    To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  4. Bug#414322: linux-source-2.6.18: kernel freeze on disk i/o (regression)

    This is due to the clocsourse set up. (Bug#412194:
    linux-image-2.6.18-3-k7: total system freeze after max. 10 minutes uptime).
    Add boot option: clocksource=tsc


    See below for GRUB /boot/grub/menu.lst

    --------------snip------------------------------------------------
    > Hello all,
    > I've done as Alexander has suggested:
    > added a boot option in /boot/grub/menu.lst
    > ----snip---->
    >> title Debian GNU/Linux, kernel 2.6.18-4-k7
    >> root (hd0,0)
    >> kernel /vmlinuz-2.6.18-4-k7 root=/dev/sda2 ro clocksource=tsc
    >> initrd /initrd.img-2.6.18-4-k7
    >> savedefault

    > rebooted and:
    > ># echo "tsc" >

    > /sys/devices/system/clocksource/clocksource0/current_clocksource <
    > ># cat /sys/devices/system/clocksource/clocksource0/* <

    > jiffies tsc pit
    > tsc
    > We are up and running now (45min.). Alex. has been up for some hours
    > (9+) using this method. So maybe others can use this and help us
    > understand later the "why" of it.
    > Anyway, fingers crossed let us see........
    > matthew
    >
    > Alexander Schories wrote:
    > Hello Steve,
    >
    >
    > uptime with "nosmp" so far: 57 min. Everything runs fine and
    > smoothly. Of course overall system load is about 5 percent (average)
    > to 20 percent (peak) higher than usual - man, i do love and miss smp..
    >
    > Just kidding, i can easily live happily either with "nosmp" or
    > particularly with 2.6.17 for now. Maybe other affected users might
    > agree to lower the initial severity to "important"?
    >
    >
    > But guess who appears on stage now again (dmesg log):
    >
    > #Time: pit clocksource has been installed.
    > #...
    > #Real Time Clock Driver v1.12ac
    > #Generic RTC Driver v1.07
    >
    > RTC is back for good!
    >
    > This makes me so curios about the mysticals of linux time again:
    >
    > http://www.kernel.org/git/?p=linux/k...9aa867ecf3eea1
    >
    >
    > After reading, re-reading and hopefully understanding i will try to
    > find a solution, why 2.6.18-k7 decides to use "Programmable Interval
    > Timer" of 1981(!) instead of our even younger and trusted friend "rtc"
    > or even the fancy "acpi_pm" ..
    >
    > Once i find helpful information or even a solution, i will post it here.
    >
    >
    > Thank you very much again!
    >
    >
    > Alexander Schories
    > Tuebingen, Germany
    >
    >
    >> Sure, it could be, but I don't know anything about the architecture
    >> of the
    >> kernel's clocksource stuff.
    >>
    >> Good luck,
    >> --Steve Langasek Give me a lever long enough and a
    >> Free OS
    >> Debian Developer to set it on, and I can move the
    >> world.
    >> vorlon@debian.org
    >> http://www.debian.org/

    ---------------------------------------------------------------------------------------------------------------------------------------------------------------------
    Iv'e been running for 2 weeks since.
    Thank you,
    matthew


    THR4K wrote:
    > Package: linux-source-2.6.18
    > Version: 2.6.18.dfsg.1-11
    > Severity: important
    >
    >
    > Hello,
    >
    > I have recently dist-upgraded my workstation from Sarge to Etch. As usual,
    > this operation worked fine, but sadly I get some trouble with the 2.6.18
    > kernel included into Etch.
    >
    >
    > To begin, I have tried the linux-image-2.6.18-4-k7 but at the first boot
    > the kernel freeze completely (the MagicSysReq keys doesn't work). So I
    > build my own image from the current linux-source-2.6.18 to test if the
    > problem could be eventualy solved with more specific options related to
    > my hardware configuration.
    >
    > After rebooting without problem on my own linux-image kernel, for a moment
    > all seemed to work fine... until the whole system freeze again during the
    > configuration process of some new packages I have planned to install.
    >
    > Despite the log files contains nothing useful, investigating a bit (eg.
    > more reboots and freezes later :-D show that the problem always occurs
    > during disk i/o operations, specially when loading the system at boot or
    > installing/deinstalling packages (heavy disk usage = faster freeze).
    >
    >
    > Of course, I did not have any problem when I use my previous kernel as
    > fallback (an old 2.6.8 version build with the Debian Sarge sources).
    >
    > Perhaps a disk driver (I use the AIC7XXX kernel module) bug ?
    >
    >
    > my lspci :
    > 00:00.0 Host bridge: Advanced Micro Devices [AMD] AMD-760 MP [IGD4-2P]
    > System Controller (rev 11)
    > 00:01.0 PCI bridge: Advanced Micro Devices [AMD] AMD-760 MP [IGD4-2P]
    > AGP Bridge
    > 00:07.0 ISA bridge: Advanced Micro Devices [AMD] AMD-766 [ViperPlus] ISA
    > (rev 02)
    > 00:07.1 IDE interface: Advanced Micro Devices [AMD] AMD-766 [ViperPlus]
    > IDE (rev 01)
    > 00:07.3 Bridge: Advanced Micro Devices [AMD] AMD-766 [ViperPlus] ACPI
    > (rev 01)
    > 00:07.4 USB Controller: Advanced Micro Devices [AMD] AMD-766 [ViperPlus]
    > USB (rev 07)
    > 00:0a.0 SCSI storage controller: Adaptec AHA-3960D / AIC-7899A U160/m
    > (rev 01)
    > 00:0a.1 SCSI storage controller: Adaptec AHA-3960D / AIC-7899A U160/m
    > (rev 01)
    > 00:0c.0 Multimedia audio controller: Ensoniq 5880 AudioPCI (rev 02)
    > 00:0d.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado]
    > (rev 78)
    > 01:05.0 VGA compatible controller: nVidia Corporation NV25 [GeForce4 Ti
    > 4400] (rev a2)
    >
    >
    > Thanx for your help,
    > THR4K
    >
    >
    >
    > -- System Information:
    > Debian Release: 4.0
    > APT prefers testing
    > APT policy: (500, 'testing')
    > Architecture: i386 (i686)
    > Shell: /bin/sh linked to /bin/bash
    > Kernel: Linux 2.6.8-16.6-tigermp
    > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
    >
    > Versions of packages linux-source-2.6.18 depends on:
    > ii binutils 2.17-3 The GNU assembler, linker and bina
    > ii bzip2 1.0.3-6 high-quality block-sorting file co
    >
    > Versions of packages linux-source-2.6.18 recommends:
    > ii gcc 4:4.1.1-15 The GNU C compiler
    > ii libc6-dev [libc-dev] 2.3.6.ds1-13 GNU C Library: Development Librari
    > ii make 3.81-2 The GNU version of the "make" util
    >
    > -- no debconf information
    >
    >
    >




    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  5. Bug#414322: linux-source-2.6.18: kernel freeze on disk i/o (regression)


    Requoted




    Figaro wrote:
    > This is due to the clocksource set up. (Bug#412194:
    > linux-image-2.6.18-3-k7: total system freeze after max. 10 minutes
    > uptime).
    > Add boot option: clocksource=tsc
    >
    >
    > See below for GRUB /boot/grub/menu.lst
    >
    > --------------snip------------------------------------------------
    > from 022507
    >> Hello all,
    >> I've done as Alexander has suggested:
    >> added a boot option in /boot/grub/menu.lst
    >> ----snip---->
    >>> title Debian GNU/Linux, kernel 2.6.18-4-k7
    >>> root (hd0,0)
    >>> kernel /vmlinuz-2.6.18-4-k7 root=/dev/sda2 ro clocksource=tsc
    >>> initrd /initrd.img-2.6.18-4-k7
    >>> savedefault

    >> rebooted and:
    >> ># echo "tsc" >

    >> /sys/devices/system/clocksource/clocksource0/current_clocksource <
    >> ># cat /sys/devices/system/clocksource/clocksource0/* <

    >> jiffies tsc pit
    >> tsc
    >> We are up and running now (45min.). Alex. has been up for some hours
    >> (9+) using this method. So maybe others can use this and help us
    >> understand later the "why" of it.
    >> Anyway, fingers crossed let us see........
    >> matthew
    >>
    >> Alexander Schories wrote:
    >> Hello Steve,
    >> Hello Steve,
    >>
    >>
    >> uptime with "nosmp" so far: 57 min. Everything runs fine and
    >> smoothly. Of course overall system load is about 5 percent (average)
    >> to 20 percent (peak) higher than usual - man, i do love and miss
    >> smp..
    >>
    >> Just kidding, i can easily live happily either with "nosmp" or
    >> particularly with 2.6.17 for now. Maybe other affected users might
    >> agree to lower the initial severity to "important"?
    >>
    >>
    >> But guess who appears on stage now again (dmesg log):
    >>
    >> #Time: pit clocksource has been installed.
    >> #...
    >> #Real Time Clock Driver v1.12ac
    >> #Generic RTC Driver v1.07
    >>
    >> RTC is back for good!
    >>
    >> This makes me so curios about the mysticals of linux time again:
    >>
    >> http://www.kernel.org/git/?p=linux/k...9aa867ecf3eea1
    >>
    >>
    >> After reading, re-reading and hopefully understanding i will try to
    >> find a solution, why 2.6.18-k7 decides to use "Programmable Interval
    >> Timer" of 1981(!) instead of our even younger and trusted friend
    >> "rtc" or even the fancy "acpi_pm" ..
    >>
    >> Once i find helpful information or even a solution, i will post it here.
    >>
    >>
    >> Thank you very much again!
    >>
    >>
    >> Alexander Schories
    >> Tuebingen, Germany
    >>
    >>
    >>> Sure, it could be, but I don't know anything about the architecture
    >>> of the
    >>> kernel's clocksource stuff.
    >>>
    >>> Good luck,
    >>> --Steve Langasek Give me a lever long enough and a
    >>> Free OS
    >>> Debian Developer to set it on, and I can move the
    >>> world.
    >>> vorlon@debian.org
    >>> http://www.debian.org/

    >>
    >>
    >>
    >> --To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
    >> with a subject of "unsubscribe". Trouble? Contact
    >> listmaster@lists.debian.org
    >>
    >>

    >
    >
    >
    > --
    > To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
    > with a subject of "unsubscribe". Trouble? Contact
    > listmaster@lists.debian.org
    >






    --
    To UNSUBSCRIBE, email to debian-bugs-dist-REQUEST@lists.debian.org
    with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

  6. Bug#414322: marked as done (linux-source-2.6.18: kernel freeze on disk i/o (regression))


    Your message dated Mon, 26 May 2008 13:07:36 +0200
    with message-id <20080526110736.GO9721@stro.at>
    and subject line Re: linux-source-2.6.18: kernel freeze on disk i/o (regression)
    has caused the Debian Bug report #414322,
    regarding linux-source-2.6.18: kernel freeze on disk i/o (regression)
    to be marked as done.

    This means that you claim that the problem has been dealt with.
    If this is not the case it is now your responsibility to reopen the
    Bug report if necessary, and/or fix the problem forthwith.

    (NB: If you are a system administrator and have no idea what this
    message is talking about, this may indicate a serious mail system
    misconfiguration somewhere. Please contact owner@bugs.debian.org
    immediately.)


    --
    414322: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414322
    Debian Bug Tracking System
    Contact owner@bugs.debian.org with problems


+ Reply to Thread