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-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
