Hi. Thanks for the reply. I'll do some further investigation as you suggest and report back in a couple of days.
On 27 June 2012 00:10, Jonathan Nieder <jrnie...@gmail.com> wrote: > Which upstream version have you tested? I've not used upstream kernels in a long time (many years). The custom-built 2.6.33 I referred to is still a Debian make-kpkg build with Debian patches. In terms of kernel versions, I cannot remember the 2.6.x versions which failed. However, I've had crashes with 3.0, 3.1 and 3.2. > . What other kernels have you tried? Does the 3.4.y kernel from > experimental reproduce this? I'll try this. > . How reproducible is this? 80%? 100%? I'll do 10 normal boots and 10 recovery boots and let you know. > . How heavy is the crash? E.g., can you still toggle the caps lock LED or > use the magic sysrq key? Neither work. Looks like a PCI or IRQ lockup. > . Do you have a log or photo of the crash? netconsole[1] or serial > console[2] > may be useful for this. I'll give netconsole a go. I may have to plug a laptop into the same switch. > Any other hints or strange symptoms? Just a comment. Ever since I built my first Debian machine (in about 1996), I've used underdog hardware, rather than Intel. Cyrix then AMD processors, VIA chipsets, Cirrus then VIA (integrated) graphics, 3com NICs. I finally switched to an AMD chipset but the motherboard still has a VIA firewire controller that I cannot get to work with a DV camera, and this PATA controller that's causing grief. VIA hardware just appears to be cursed. Regards, Giuliano. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
