I have booted from rescue disc, enabled networking, but when looking for
Fedora disc system hangs up. So I can't upgrade kernel or driver.
I have removed my HD MAXTOR ATLAS 15000 rpm and replacd it for a SEAGATE
10000 rpm and works fine. I can install Fedora core 5 x86_64 and boot from
HD. Does it confirm a problem with aic79xx driver?
Thanks,
Gonzalo.
----- Original Message -----
From: "Gilboa Davara" <gilboad@xxxxxxxxx>
To: "Users Fedora" <fedora-list@xxxxxxxxxx>
Sent: Thursday, April 06, 2006 2:39 PM
Subject: Re: BUG: spinlock recursion
> On Thu, 2006-04-06 at 14:27 +0200, Gonzalo Aguilera wrote:
> > I have an adaptec ultra 320 scsi, AIC-7902. My hard disc is a Maxtor
> > Atlas 15k. When installing Fedora loads aic-79xx driver, installation
finish
> > ok, but after reboot I got that BUG. It's reproducible every boot.
> > If I boot from a rescue disc usually hangs when attempt to find my
Linux
> > installation and mount it under /mnt/sysimage. Skipping it I got this
result
> > of lsmod (don't know if it is usefull).
> >
> > Module Size Used by Not tainted
> > dm_snapshot 48913 0 - Live 0xffffffff883b1000
> > dm_mirror 54593 0 - Live 0xffffffff883a2000
> > dm_zero 35393 0 - Live 0xffffffff88398000
> > dm_mod 90257 3 dm_snapshot,dm_mirror,dm_zero, Live 0xffffffff88380000
> > xfs 512225 0 - Live 0xffffffff88301000
> > exportfs 38977 1 xfs, Live 0xffffffff882f6000
> > jfs 198225 0 - Live 0xffffffff882c4000
> > reiserfs 270665 0 - Live 0xffffffff88280000
> > ext3 164945 0 - Live 0xffffffff88256000
> > jbd 93929 1 ext3, Live 0xffffffff8823e000
> > msdos 43201 0 - Live 0xffffffff88232000
> > raid6 136801 0 - Live 0xffffffff8820f000
> > raid5 58177 0 - Live 0xffffffff881ff000
> > xor 38865 2 raid6,raid5, Live 0xffffffff881f4000
> > raid1 54977 0 - Live 0xffffffff881e5000
> > raid0 40513 0 - Live 0xffffffff881da000
> > aic79xx 204061 0 - Live 0xffffffff881a7000
> > scsi_transport_spi 58177 1 aic79xx, Live 0xffffffff88197000
> > tg3 131525 0 - Live 0xffffffff88175000
> > ohci_hcd 54877 0 - Live 0xffffffff88166000
> > sr_mod 51045 0 - Live 0xffffffff88158000
> > sd_mod 51009 0 - Live 0xffffffff8814a000
> > scsi_mod 181905 4 aic79xx,scsi_transport_spi,sr_mod,sd_mod, Live
> > 0xffffffff8811c000
> > squashfs 63273 1 - Live 0xffffffff8810b000
> > pcspkr 36937 0 - Live 0xffffffff88100000
> > edd 43209 0 - Live 0xffffffff880f4000
> > floppy 100617 0 - Live 0xffffffff880da000
> > loop 49361 2 - Live 0xffffffff880cc000
> > nfs 251289 0 - Live 0xffffffff8808d000
> > nfs_acl 36801 1 nfs, Live 0xffffffff88083000
> > lockd 96977 1 nfs, Live 0xffffffff8806a000
> > sunrpc 192137 3 nfs,nfs_acl,lockd, Live 0xffffffff8803a000
> > vfat 47041 0 - Live 0xffffffff8802d000
> > fat 86385 2 msdos,vfat, Live 0xffffffff88016000
> > cramfs 76933 0 - Live 0xffffffff88002000
> >
> > Thanks,
> >
> > Gonzalo.
> >
> > ----- Original Message -----
>
> OK.
> In general, I'm using a number of comparable configuration both @home
> and @work.
> Home: Tyan Thunder K8WE, 2x270, Adaptec 29160.
> Work: (couple of) HP wx9300, 2x275, LSI 320.
> This alone should suggest a problem with the aic79xx driver and not the
> kernel itself.
> AFAICS by looking at the kernel change logs, 2.6.15/16 brought many
> changes to this driver.
>
> I'd suggest you do the following:
> Boot from rescue CD, -enable- networking, let it detect the Fedora disk.
> Chroot into it.
> Now, "yum update" to the latest kernel. Try booting.
>
> If it doesn't work:
> Boot again from the rescue CD, follow the procedure.
> -However-, this time enabled the update-testing repo in /etc/yum.repo.d.
> There's a new 2.6.16 kernel in -testing... hopefully it'll work.
>
> BTW, did FC4 work?
> Gilboa
>
>
> --
> fedora-list mailing list
> fedora-list@xxxxxxxxxx
> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
