linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "emmanuel\.fuste" <emmanuel.fuste@laposte.net>
To: "bunk" <bunk@stusta.de>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>,
	"James\.Bottomley" <James.Bottomley@SteelEye.com>,
	"linux-scsi" <linux-scsi@vger.kernel.org>
Subject: Re: panic with AIC7xxx
Date: Tue, 10 Jan 2006 22:41:08 +0100	[thread overview]
Message-ID: <ISWC8K$B14D076AABEAA715E4BC889EAAA17D8B@laposte.net> (raw)

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)




             reply	other threads:[~2006-01-10 21:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-10 21:41 emmanuel.fuste [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-10  9:33 panic with AIC7xxx emmanuel.fuste
2005-11-22 16:59 Panic with aic7xxx Robie Basak
2005-10-28 23:34 panic with AIC7xxx Emmanuel Fusté
2006-01-10  0:48 ` Adrian Bunk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='ISWC8K$B14D076AABEAA715E4BC889EAAA17D8B@laposte.net' \
    --to=emmanuel.fuste@laposte.net \
    --cc=James.Bottomley@SteelEye.com \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).