Re: panic with AIC7xxx

From: emmanuel.fuste
Date: Tue Jan 10 2006 - 16:41:37 EST


Somme good and somme bad news :

> Hello,
> > > I recently made the switch from 2.4.26 to 2.6.13 and
> 2.6.14rc5 on my old
> > > dual 586mmx 233mhz.
> >
> > are your problems still present in 2.6.15?
> >
> > > I've got many problems with SMP on 2.6.13 (bad irq
> balancing/routing
> > > very bad performance on IDE and SCSI) but I tried to use
> the long
> > > awaited CDRW support.
....
> > --
>
> I was waiting the merge of the patch serie from Hannes
> Reinecke <hare () suse ! de>, because of the sequencer fixes.
> I did'nt try this patch serie myself because the sequencer
> fixes one ([PATCH 5/6]] never reach lkml or linux-scsi.
>
> I will compile a clean 2.6.15 today and give it a try this
> evening.

So, good news, kernel boot and raw hardisk perfs (hdparm -t)
are event a little better.

Bad news :
- irq balancing/routing is one more time broken
rafale:~# cat /proc/interrupts
CPU0 CPU1
0: 209712 167 IO-APIC-edge timer
1: 861 10 IO-APIC-edge i8042
2: 0 0 XT-PIC cascade
5: 0 0 IO-APIC-edge SoundBlaster
7: 1 2 IO-APIC-edge parport0
8: 3 1 IO-APIC-edge rtc
12: 17770 3 IO-APIC-edge i8042
145: 2362 1 IO-APIC-level eth0
161: 24282 1 IO-APIC-level aic7xxx, uhci_hcd:usb1
NMI: 0 0
LOC: 209769 209768
ERR: 0
MIS: 0

- when I try to format my cdrw with cdrwtool -d /dev/sr0 -q,
the red led of the scsi bus activity ligth on, scsi bus lock
(I could switch console and try to log in but without succes
since hdd could not be reach), all without any message on the
console and few seconds later, the machine is killed with a
kernel panic : "Fatal exception in Interrupt" in
ahc_handle_seqint +0x371/0x1055 [aic7xxx]
If you want, I could send you a screen-shot of the panic taken
with my phone tomorow (I need a windows computer to get the
picture out of my phone).

Regards,
Emmanuel.

Accédez au courrier électronique de La Poste : www.laposte.net ;
3615 LAPOSTENET (0,34 ?/mn) ; tél : 08 92 68 13 50 (0,34?/mn)



-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/