-- Package-specific info:
** Version:
Linux version 2.6.32-3-powerpc (Debian 2.6.32-9) (maks@debian.org) (gcc version 4.3.4 (Debian 4.3.4-8) ) #1 Thu Feb 25 05:58:05 UTC 2010
** USB devices:
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 040b:6533 Weltrend Semiconductor Speed-Link Competition Pro
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 046d:c505 Logitech, Inc. Cordless Mouse+Keyboard Receiver
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 0930:0b09 Toshiba Corp. PX1396E-3T01 External hard drive
Bus 001 Device 003: ID 13d3:3206 IMC Networks DNTV Live! Tiny USB2 BDA (No Remote)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Kernel: Linux 2.6.32-3-powerpc
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-2.6.32-3-powerpc depends on:
ii debconf [debconf-2.0] 1.5.32 Debian configuration management sy
ii initramfs-tools [linux-initr 0.94.4 tools for generating an initramfs
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii module-init-tools 3.12~pre2-3 tools for managing Linux kernel mo
Versions of packages linux-image-2.6.32-3-powerpc recommends:
ii firmware-linux-free 2.6.32-11 Binary firmware for various driver
Versions of packages linux-image-2.6.32-3-powerpc suggests:
pn linux-doc-2.6.32 <none> (no description available)
ii mkvmlinuz 35 create a kernel to boot a PowerPC
Versions of packages linux-image-2.6.32-3-powerpc is related to:
pn firmware-bnx2 <none> (no description available)
pn firmware-bnx2x <none> (no description available)
pn firmware-ipw2x00 <none> (no description available)
pn firmware-ivtv <none> (no description available)
pn firmware-iwlwifi <none> (no description available)
ii firmware-linux 0.23 Binary firmware for various driver
ii firmware-linux-nonfree 0.23 Binary firmware for various driver
pn firmware-qlogic <none> (no description available)
pn firmware-ralink <none> (no description available)
-- debconf information excluded
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100420072101.32573.69717.reportbug@honey.hogyros .de">http://lists.debian.org/20100420072101.32573.69717.reportbug@honey.hogyros .de
04-22-2011, 09:35 PM
Moritz Mühlenhoff
Bug#578477: crashes after several days of use
tags 578477 moreinfo
thanks
On Tue, Apr 20, 2010 at 09:21:02AM +0200, Simon Richter wrote:
> Package: linux-2.6
> Version: 2.6.32-9
> Severity: important
> Tags: sid
>
> Hi,
>
> I am experiencing strange crashes after a few days of use. These appear
> to be related to LVM.
>
> Serial console output from the crash looks like this:
Does this still occur with more recent kernels?
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110422213511.GA3049@pisco.westfalen.local">http://lists.debian.org/20110422213511.GA3049@pisco.westfalen.local
07-28-2011, 01:02 AM
Jonathan Nieder
Bug#578477: crashes after several days of use
# not needed in presence of found/fixed information
tags 578477 - sid
retitle 578477 [powerpc] crashes in block code after several days of use
quit
Hi Simon,
Simon Richter wrote:
> I am experiencing strange crashes after a few days of use. These appear
> to be related to LVM.
>
> Serial console output from the crash looks like this:
Sorry we took so long to get to this. Basic questions:
- have you experienced the crashes on more than one machine? Do you
know of anyone else having experienced it?
- do only a few lists of functions show up in such backtraces or do
they seem arbitrary?
- did the problems start after an upgrade? If so, what was the last
working and first nonworking version?
- how have you been coping since then? Is there a workaround that could
shed light on this?
- if you're able to boot with some version, could you attach a full
kernel log and bugscript output (which includes lspci info, etc)?
- any other observations?
Thanks for reporting,
Jonathan
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20110728010225.GA31118@elie">http://lists.debian.org/20110728010225.GA31118@elie
07-28-2011, 12:33 PM
Simon Richter
Bug#578477: crashes after several days of use
Hi Jonathan,
Am 28.07.2011 03:02, schrieb Jonathan Nieder:
> Sorry we took so long to get to this. Basic questions:
>From memory, as the machine in question is currently mothballed.
> - have you experienced the crashes on more than one machine? Do you
> know of anyone else having experienced it?
No, I only have a single PagasosII machine.
> - do only a few lists of functions show up in such backtraces or do
> they seem arbitrary?
The top of the stack is always the same; entry into the block/LVM code
comes from different paths.
> - did the problems start after an upgrade? If so, what was the last
> working and first nonworking version?
That is difficult to tell, as several versions prior to this one would
panic in the Marvell Ethernet driver.
> - how have you been coping since then? Is there a workaround that could
> shed light on this?
I have switched to another machine. Given sufficient time, I might get
around to retrying it on the PegasosII; if there is a motivated
developer who might want such a box, I'd also be prepared to give the
machine away to good hands.
> - if you're able to boot with some version, could you attach a full
> kernel log and bugscript output (which includes lspci info, etc)?
Difficult right now.
The machine is a standard PegasosII, with Radeon 9200SE graphics, an
Exsys EX-1065 USB expander card (NEC chipset) and a Cologne Chip ISDN card.
Simon
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4E315717.2050901@debian.org">http://lists.debian.org/4E315717.2050901@debian.org
07-28-2011, 12:33 PM
Simon Richter
Bug#578477: crashes after several days of use
Hi Jonathan,
Am 28.07.2011 03:02, schrieb Jonathan Nieder:
> Sorry we took so long to get to this. Basic questions:
>From memory, as the machine in question is currently mothballed.
> - have you experienced the crashes on more than one machine? Do you
> know of anyone else having experienced it?
No, I only have a single PagasosII machine.
> - do only a few lists of functions show up in such backtraces or do
> they seem arbitrary?
The top of the stack is always the same; entry into the block/LVM code
comes from different paths.
> - did the problems start after an upgrade? If so, what was the last
> working and first nonworking version?
That is difficult to tell, as several versions prior to this one would
panic in the Marvell Ethernet driver.
> - how have you been coping since then? Is there a workaround that could
> shed light on this?
I have switched to another machine. Given sufficient time, I might get
around to retrying it on the PegasosII; if there is a motivated
developer who might want such a box, I'd also be prepared to give the
machine away to good hands.
> - if you're able to boot with some version, could you attach a full
> kernel log and bugscript output (which includes lspci info, etc)?
Difficult right now.
The machine is a standard PegasosII, with Radeon 9200SE graphics, an
Exsys EX-1065 USB expander card (NEC chipset) and a Cologne Chip ISDN card.
Simon
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4E315717.2050901@debian.org">http://lists.debian.org/4E315717.2050901@debian.org
07-28-2011, 12:33 PM
Simon Richter
Bug#578477: crashes after several days of use
Hi Jonathan,
Am 28.07.2011 03:02, schrieb Jonathan Nieder:
> Sorry we took so long to get to this. Basic questions:
>From memory, as the machine in question is currently mothballed.
> - have you experienced the crashes on more than one machine? Do you
> know of anyone else having experienced it?
No, I only have a single PagasosII machine.
> - do only a few lists of functions show up in such backtraces or do
> they seem arbitrary?
The top of the stack is always the same; entry into the block/LVM code
comes from different paths.
> - did the problems start after an upgrade? If so, what was the last
> working and first nonworking version?
That is difficult to tell, as several versions prior to this one would
panic in the Marvell Ethernet driver.
> - how have you been coping since then? Is there a workaround that could
> shed light on this?
I have switched to another machine. Given sufficient time, I might get
around to retrying it on the PegasosII; if there is a motivated
developer who might want such a box, I'd also be prepared to give the
machine away to good hands.
> - if you're able to boot with some version, could you attach a full
> kernel log and bugscript output (which includes lspci info, etc)?
Difficult right now.
The machine is a standard PegasosII, with Radeon 9200SE graphics, an
Exsys EX-1065 USB expander card (NEC chipset) and a Cologne Chip ISDN card.
Simon
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4E315717.2050901@debian.org">http://lists.debian.org/4E315717.2050901@debian.org
04-04-2012, 09:39 PM
Jonathan Nieder
Bug#578477: crashes after several days of use
Hi Simon,
Simon Richter wrote:
> I have switched to another machine. Given sufficient time, I might get
> around to retrying it on the PegasosII; if there is a motivated
> developer who might want such a box, I'd also be prepared to give the
> machine away to good hands.
Did the PegasosII end up finding a new owner?
Curious,
Jonathan
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20120404213902.GA18581@burratino">http://lists.debian.org/20120404213902.GA18581@burratino