HTH. -- Harmon > > > ------------------------------------------------------------------------ > > Subject: > Re: Bug#227288: Error inserting module for mptbase on Dell 1750 > From: > Herbert Xu
But I'm no hardware expert -- that's just where I'd look first. Debian on Dell PE2600 [email protected] barrado at ccupm.upm.es Fri Aug 8 07:05:01 CDT 2003 Previous message: FOR YOUR URGENT ATTENTION, PLEASE. not the hard disk). >> >>Thanks. mptbase: MPT adapter found: PCI bus/dfn=04/28h, class=00010000, id=30h mptbase: 64 BIT PCI BUS DMA ADDRESSING SUPPORTED mptbase: MPT adapter @ fcd30000, msize=65536d bytes mptbase: (port i/o @ cc00, psize=256d bytes) mptbase: http://www.linuxquestions.org/questions/slackware-installation-40/doorbell-ack-timeout-error-on-slackware-13-installation-823558/
They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. RAMDISK: Compressed image found at block 0 Freeing initrd memory: 793k freed cramfs: wrong magic FAT:bogus logical sector size 38120 kernel panic: VFS: Unable to mount root fs on 08:02 do I have looked all over for a fix to this problem, but have not found a clear descriptive sollution. Dec 7 10:24:07 bez kernel: mptscsih: ioc0: attempting task abort! (sc=f7456580) Dec 7 10:24:07 bez kernel: st 2:0:3:0: CDB: Write(6): 0a 00 00 80 00 00 Dec 7 10:24:07 bez kernel:
Information forwarded to [email protected], Herbert Xu
mptbase: ioc1: ERROR - Diagnostic reset FAILED! (102h) mptbase: ioc1 NOT READY WARNING! If any revisions are required, please edit the "Technical Notes" field accordingly. Herbert Xu wrote: > tags 227288 moreinfo > quit > > On Sun, Mar 28, 2004 at 07:14:55PM +1000, herbert wrote: > >>On Mon, Jan 19, 2004 at 02:09:05PM -0500, Fredrick https://forums.contribs.org/index.php?topic=43137.0 The size of our CRAMFS initrd, loaded into /dev/ram0, is 13275136 bytes (approx. 13M).
Copy sent to Herbert Xu
mptbase: ioc0: ERROR - Diagnostic reset FAILED! (142h) mptbase: ioc0 NOT READY WARNING! https://lists.opensuse.org/opensuse-bugs/2008-11/msg13950.html Actual results: Memory for crash kernel (0x0 to 0x0) notwithin permissible range PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved PCI: Not using MMCONFIG. Thanks in advance. [This is an automated message. It still takes longer than the default rootdelay, but in any case it does recover by itself and with these new kernels and tweaking rootdelay I can get the system to
be aware that in the following description both a ramdisk and the filesystem image within it are both referred to as "ramdisk".) We have a 2-stage booting processing when booting from I found a way to make it work, at least to get a DELL 1750 running on Slackware 13.0... mptbase: fusion_exit() called! Copy sent to Herbert Xu
Full text and rfc822 format available. Contact Us - Advertising Info - Rules - LQ Merchandise - Donations - Contributing Member - LQ Sitemap - Main Menu Linux Forum Android Forum Chrome OS Forum Search LQ mptbase: ioc0: DbG1: diag0=00000102, diag1=00000000 mptbase: ioc0: Wrote magic DiagWriteEn sequence (182) mptbase: ioc0: DbG2: diag0=00000182, diag1=00000000 mptbase: ioc0: Diagnostic reset performed mptbase: ioc0: Calling IOC pre_reset handler #15 mptbase: IOC Copy sent to Herbert Xu
mptbase: ioc0: ERROR - Failed to come READY after reset! Regards P. The machine, apparently, boots up correctly.
Dec 7 10:27:40 bez kernel: mptbase: ioc0: ERROR - Diagnostic reset FAILED! (ffffffffh) Dec 7 10:27:40 bez kernel: mptbase: ioc0: WARNING - NOT READY! mptbase: WARNING - ioc0 did not initialize property! (-1) mptbase: ioc1: ERROR - Doorbell ACK timeout (4)! Consequence: Machine will hang during boot, if the Disk PCI device is not properly initialized. But a rootdelay=120 woks for me.
Full text and rfc822 format available. The system hangs here for about a minute or more then continues on and from all looks appears to be working fine. mptbase: ioc1: Sending IOC reset(0x40)! Thanks.Jan 22 14:07:57 mail2 kernel: mptbase: Initiating ioc0 bringupJan 22 14:07:57 mail2 kernel: mptbase: ioc0: WARNING - Unexpected doorbell active!Jan 22 14:07:57 mail2 kernel: mptbase: ioc0: ERROR - Doorbell ACK timeout
All other filesystem drivers are modules. The 'doorbell ack timeout' error happens during initial installation boot, which then makes the disk subsystem inaccessable. Thus, the initial ramdisk (initrd) for this kernel must use, you guessed it, a CRAMFS filesystem. mptbase: ioc0: free'd 916 of 916 bytes mptbase: ioc1: free'd 916 of 916 bytes Fusion MPT base driver 2.05.11.03 Copyright (c) 1999-2003 LSI Logic Corporation mptbase: Register for IOC reset notification
mptbase: ioc0: DbG1: diag0=00000102, diag1=00000000 mptbase: ioc0: Wrote magic DiagWriteEn sequence (182) mptbase: ioc0: DbG2: diag0=00000182, diag1=00000000 mptbase: ioc0: Diagnostic reset performed mptbase: ioc0: Calling IOC pre_reset handler #15 mptbase: IOC I noticed that when I add rootdelay=120 my system boots, else it fails at initramfs and drops to busybox shell. We call the bug "peculiar" because it does not exhibit itself when the kernel is booted in a "standard" fashion, i.e. description: updated Jeremy Foshee (jeremyfoshee) wrote on 2010-06-17: #5 Hi Anton, This bug was reported a while ago and there hasn't been any activity in it recently.
Acknowledgement sent to "Harmon S. binding ioc1 <==> ioc0 mptbase: Initiating ioc1 bringup mptbase::MakeIocReady, ioc1 [raw] state=00000000 mptbase: KickStarting ioc1! Message #66 received at [email protected] (full text, mbox, reply): From: Herbert Xu
We built our own CRAMFS initial ramdisk, and "piggybacked" our ext2 RAMDISK on it. From: [email protected] Date: Thu, 18 Sep 2008 15:51:22 -0600 (MDT) Message-id: