3C905B module/builtin lockup on 2.4.6-pre3-5
After attempting different configurations for the past 3 hours, I am at a loss. I have attempted to successfully load the 3C59x driver with kernel 2.4.6-pre5 and pre3 with no luck. As soon as the module loads, I can switch consoles, but can type nothing into any of them. I can hit the Num Lock, which will turn on and off the light, same with Caps Lock. I can hit the return key in the terminal where the insmod command was given, and it will scroll the screen, nothing more. I tried loading the module with debug=7, per the vortex.txt file, but nothing is logged anywhere. I am at a loss as to what is the problem is here. Any help is appreciated. Attached is my .config file and output from dmesg. I can try to provide any more info that might help. I will also attache output from lspci, although, the TV card has been removed, as it was sharing an IRQ with the NIC, so I wanted to eliminate any possibility that this might be part of the problem. Glenn C. Hofmann # # Automatically generated by make menuconfig: don't edit # CONFIG_X86=y CONFIG_ISA=y # CONFIG_SBUS is not set CONFIG_UID16=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set CONFIG_MK7=y # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_X86_L1_CACHE_SHIFT=6 CONFIG_X86_TSC=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_USE_3DNOW=y CONFIG_X86_PGE=y CONFIG_X86_USE_PPRO_CHECKSUM=y # CONFIG_TOSHIBA is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set CONFIG_NOHIGHMEM=y # CONFIG_HIGHMEM4G is not set # CONFIG_HIGHMEM64G is not set # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y # CONFIG_SMP is not set CONFIG_X86_UP_IOAPIC=y CONFIG_X86_IO_APIC=y CONFIG_X86_LOCAL_APIC=y # # General setup # CONFIG_NET=y # CONFIG_VISWS is not set CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_PCI_NAMES=y # CONFIG_EISA is not set # CONFIG_MCA is not set CONFIG_HOTPLUG=y # # PCMCIA/CardBus support # # CONFIG_PCMCIA is not set CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set CONFIG_BINFMT_AOUT=y CONFIG_BINFMT_ELF=y CONFIG_BINFMT_MISC=y CONFIG_PM=y CONFIG_ACPI=y # CONFIG_ACPI_DEBUG is not set CONFIG_ACPI_BUSMGR=y CONFIG_ACPI_SYS=y CONFIG_ACPI_CPU=y CONFIG_ACPI_BUTTON=y # CONFIG_ACPI_AC is not set # CONFIG_ACPI_EC is not set # CONFIG_ACPI_CMBATT is not set # CONFIG_ACPI_THERMAL is not set # CONFIG_APM is not set # # Memory Technology Devices (MTD) # # CONFIG_MTD is not set # # RAM/ROM/Flash chip drivers # # CONFIG_MTD_CFI is not set # CONFIG_MTD_CFI_INTELEXT is not set # CONFIG_MTD_CFI_AMDSTD is not set # CONFIG_MTD_AMDSTD is not set # CONFIG_MTD_SHARP is not set # CONFIG_MTD_RAM is not set # CONFIG_MTD_ROM is not set # CONFIG_MTD_JEDEC is not set # # Mapping drivers for chip access # # CONFIG_MTD_PHYSMAP is not set # CONFIG_MTD_SUN_UFLASH is not set # CONFIG_MTD_NORA is not set # CONFIG_MTD_PNC2000 is not set # CONFIG_MTD_RPXLITE is not set # CONFIG_MTD_SC520CDP is not set # CONFIG_MTD_NETSC520 is not set # CONFIG_MTD_SBC_GXX is not set # CONFIG_MTD_ELAN_104NC is not set # CONFIG_MTD_SA1100 is not set # CONFIG_MTD_SA1100_REDBOOT_PARTITIONS is not set # CONFIG_MTD_SA1100_BOOTLDR_PARTITIONS is not set # CONFIG_MTD_DC21285 is not set # CONFIG_MTD_IQ80310 is not set # CONFIG_MTD_DBOX2 is not set # CONFIG_MTD_CSTM_MIPS_IXX is not set # CONFIG_MTD_CFI_FLAGADM is not set # CONFIG_MTD_MIXMEM is not set # CONFIG_MTD_OCTAGON is not set # CONFIG_MTD_VMAX is not set # CONFIG_MTD_OCELOT is not set # # Self-contained MTD device drivers # # CONFIG_MTD_PMC551 is not set # CONFIG_MTD_SLRAM is not set # CONFIG_MTD_MTDRAM is not set # CONFIG_MTD_DOC1000 is not set # CONFIG_MTD_DOC2000 is not set # CONFIG_MTD_DOC2001 is not set # CONFIG_MTD_DOCPROBE is not set # # NAND Flash Device Drivers # # CONFIG_MTD_NAND is not set # CONFIG_MTD_NAND_SPIA is not set # # Parallel port support # CONFIG_PARPORT=m CONFIG_PARPORT_PC=m # CONFIG_PARPORT_PC_FIFO is not set # CONFIG_PARPORT_PC_SUPERIO is not set # CONFIG_PARPORT_AMIGA is not set # CONFIG_PARPORT_MFC3 is not set # CONFIG_PARPORT_ATARI is not set # CONFIG_PARPORT_SUNBPP is not set # CONFIG_PARPORT_OTHER is not set # CONFIG_PARPORT_1284 is not set # # Plug and
Re: 3C905b partial lockup in 2.4.5-pre5 and up to 2.4.6-pre1
Andrew, Although I don't run Redhat, your response tells me that, even though I was feeling that it was a kernel problem, it could be a userspace issue, which I also suspected. Debian updated their nettools today, so I will see if that helps in any way. Thanks for your help. If you think of anything else that might be an issue, please let me know. Glenn C. Hofmann Andrew wrote: Date sent: Sun, 10 Jun 2001 11:35:53 +1000 From: Andrew Morton <[EMAIL PROTECTED]> Subject:Re: 3C905b partial lockup in 2.4.5-pre5 and up to 2.4.6-pre1 To: [EMAIL PROTECTED] Copies to: [EMAIL PROTECTED] > "Glenn C. Hofmann" wrote: > > > > I have tried 2.4.5-pre2 up to 2.4.6-pre1 with the same results. > > Everything boots great and I can login fine. When I try to assign > > an IP via DHCP or ifconfig, the system sits and stares at me > > indefinitely. 2.4.5-pre4 didn't compile for me, but pre3 works fine > > and pre5 locks. There is keyboard response, and Alt-SysRq will tell > > me that it knows I want it to sync the disks, but won't actually do > > it. It will reboot, though. I can switch between terminals, but > > cannot type anything at the login prompt. > > > > The board is a Abit KT7-RAID. I have waited to see if this issue > > has been resolved and will recompile the newer kernels (AC and Linus > > flavours) to see if it has cleared up, but wanted to see if maybe > > there is something else I should look at. I can provide any more > > information that might help, so please let me know. Thanks in > > advance. > > There's a problem in some versions of `pump' where it gets > confused and ends up spinning indefinitely. If you're using > pump could you please try the latest RPM? > > If that doesn't help, and if you're unable to kill pump > with ^C, and if other virtual consoles are not responding then > it could be a kernel problem - try hitting sysrq-T and feeding > the resulting logs through `ksymoops -m System.map' > - > To unsubscribe from this list: send the line "unsubscribe > linux-kernel" in the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 3C905b partial lockup in 2.4.5-pre5 and up to 2.4.6-pre1
Andrew, Although I don't run Redhat, your response tells me that, even though I was feeling that it was a kernel problem, it could be a userspace issue, which I also suspected. Debian updated their nettools today, so I will see if that helps in any way. Thanks for your help. Glenn C. Hofmann On Sunday, 10 June 2001 Andrew wrote: > "Glenn C. Hofmann" wrote: > > > > I have tried 2.4.5-pre2 up to 2.4.6-pre1 with the same results. > > Everything boots great and I can login fine. When I try to assign > > an IP via DHCP or ifconfig, the system sits and stares at me > > indefinitely. 2.4.5-pre4 didn't compile for me, but pre3 works fine > > and pre5 locks. There is keyboard response, and Alt-SysRq will tell > > me that it knows I want it to sync the disks, but won't actually do > > it. It will reboot, though. I can switch between terminals, but > > cannot type anything at the login prompt. > > > > The board is a Abit KT7-RAID. I have waited to see if this issue > > has been resolved and will recompile the newer kernels (AC and Linus > > flavours) to see if it has cleared up, but wanted to see if maybe > > there is something else I should look at. I can provide any more > > information that might help, so please let me know. Thanks in > > advance. > > There's a problem in some versions of `pump' where it gets > confused and ends up spinning indefinitely. If you're using > pump could you please try the latest RPM? > > If that doesn't help, and if you're unable to kill pump > with ^C, and if other virtual consoles are not responding then > it could be a kernel problem - try hitting sysrq-T and feeding > the resulting logs through `ksymoops -m System.map' > - > To unsubscribe from this list: send the line "unsubscribe > linux-kernel" in the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
3C905b partial lockup in 2.4.5-pre5 and up to 2.4.6-pre1
I have tried 2.4.5-pre2 up to 2.4.6-pre1 with the same results. Everything boots great and I can login fine. When I try to assign an IP via DHCP or ifconfig, the system sits and stares at me indefinitely. 2.4.5-pre4 didn't compile for me, but pre3 works fine and pre5 locks. There is keyboard response, and Alt-SysRq will tell me that it knows I want it to sync the disks, but won't actually do it. It will reboot, though. I can switch between terminals, but cannot type anything at the login prompt. The board is a Abit KT7-RAID. I have waited to see if this issue has been resolved and will recompile the newer kernels (AC and Linus flavours) to see if it has cleared up, but wanted to see if maybe there is something else I should look at. I can provide any more information that might help, so please let me know. Thanks in advance. Glenn C. Hofmann - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: VIA IDE driver status ?
It should support both, to my knowledge (which is very limited, mind
you). I also went out to the store and purchased a new cable, which
made the driver recognize the cable correctly, whereas it did not
before. I wonder if there is not a serious deficiency in the cables
sent out with motherboards, which is contributing to the problems a lot
of people are having in this area. Hope this helps some.
Chris
On 31 Mar 2001 15:14:47 -0300, Frédéric L. W. Meunier wrote:
> I'm not overclocking. It's an ASUS A7Pro with Athlon 1000. I
> had the same problem with an ASUS K7V with Athlon 700. But
> the processor died after my cooler failed for 20 minutes!
>
> BTW, how do I know if my cable is ATA100/ATA66, not only ATA66
> ? The manual from the A7Pro says it supports both, but at the
> site it says the cable shipped with this motherboard is ATA66.
>
> On Sat, Mar 31, 2001 at 12:00:41PM -0600, Glenn C. Hofmann wrote:
> > I am not sure if this applies in your case, but I was getting problems
> > such as this on my Abit KT7-RAID and had the correct cables, also. One
> > day, on a hunch after reading a post from Alan about overclocking, I
> > took my Athlon 750 down to 850 from 1.05 GHz and all is working great
> > now. If your overclocking, I would suggest not doing so (at least not
> > so much), based on my experience. I am also using the v4.0 driver.
> >
> > Chris
> >
> > On 31 Mar 2001 00:41:32 -0300, Frédéric L. W. Meunier wrote:
> > > Hi. I really can't get UDMA66 with the VIA driver. I tried
> > > everything, also a new motherboard (ASUS A7Pro) with a
> > > ATA100/ATA66 cable (using both ends...)!
> > >
> > > All I get are the usual CRC error messages.
> > >
> > > So, there's no UDMA66 for any vt82c686a ? I'm using 2.4.3.
> > >
> > > If there's no UDMA66, what are the advantages using this
> > > driver ?
> > >
> > > TIA.
>
> --
> 0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: VIA IDE driver status ?
I am not sure if this applies in your case, but I was getting problems
such as this on my Abit KT7-RAID and had the correct cables, also. One
day, on a hunch after reading a post from Alan about overclocking, I
took my Athlon 750 down to 850 from 1.05 GHz and all is working great
now. If your overclocking, I would suggest not doing so (at least not
so much), based on my experience. I am also using the v4.0 driver.
Chris
On 31 Mar 2001 00:41:32 -0300, Frédéric L. W. Meunier wrote:
> Hi. I really can't get UDMA66 with the VIA driver. I tried
> everything, also a new motherboard (ASUS A7Pro) with a
> ATA100/ATA66 cable (using both ends...)!
>
> All I get are the usual CRC error messages.
>
> So, there's no UDMA66 for any vt82c686a ? I'm using 2.4.3.
>
> If there's no UDMA66, what are the advantages using this
> driver ?
>
> TIA.
>
> --
> 0@pervalidus.{net, {dyndns.}org} Tel: 55-21-717-2399 (Niterói-RJ BR)
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [EMAIL PROTECTED]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: Kernel panic: Unable to handle kernel paging request
I have noticed this behaviour as well with any newer pre 2.4 kernels on a Compaq Proliant 3000 with a Smart2-DH controller and, just recently, with test9-pre7 on my home system. It always happens during high disk activity. The problem I have is that usually it starts scrolling several pages of errors (or plain garbage) and I cannot get enough to submit any useful information. One system is SCSI (the Proliant) and one is IDE, so I cannot even limit it to that. The only commonality that I can see is that there is always high disk I/O when the panic occurs. On 1 Oct 2000, at 19:03 Urban Widmark wrote: > On Sun, 1 Oct 2000, Niccolo Rigacci wrote: > > > I have a Debian GNU/Linux 2.2 (kernel 2.2.17) installed on a > > Cyrix 6x86, sometimes it panics. As far I can detect the panics > > occur when there is much disk activity (updatedb and > > checksecurity are in progress). I was able to get the log of the > > panic via the serial console. > > Do you have smbfs mounted when find/updatedb is running? 2.2.18pre fixes > an old bug where smbfs didn't check the length of the path it was building > vs the buffer used to store the path. Depending on what you have mounted > this can cause all sorts of fun things to happen. > > If you had not used smbfs since booting then that is not it, and then I > know nothing about it. > > /Urban > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: (Fwd) CD-ROM (SCSI and IDE) not mounting disk
Another interesting thing that I just noticed, I can still play music CD's in either drive. On 23 Sep 2000, at 20:10 Glenn C. Hofmann wrote: > I will try to recompile some older kernels and see where it breaks, but here is the >output in the > logs when I try to mount the CD. I enabled debugging, as well. > > Found in debug logfile: > > Sep 23 19:58:05 hofmann1 kernel: VFS: Disk change detected on device ide1(22,64) > Sep 23 19:58:05 hofmann1 last message repeated 2 times > Sep 23 20:01:07 hofmann1 kernel: VFS: Disk change detected on device ide1(22,64) > Sep 23 20:01:07 hofmann1 last message repeated 2 times > > And in messages logfile: > > Sep 23 20:06:52 hofmann1 kernel: cdrom: entering cdrom_open > Sep 23 20:06:52 hofmann1 kernel: cdrom: entering open_for_data > Sep 23 20:06:52 hofmann1 kernel: cdrom: drive_status=2 > Sep 23 20:06:52 hofmann1 kernel: cdrom: the tray is open... > Sep 23 20:06:52 hofmann1 kernel: cdrom: trying to close the tray. > Sep 23 20:06:52 hofmann1 kernel: cdrom: bummer. the tray is still not closed. > Sep 23 20:06:52 hofmann1 kernel: cdrom: tray might not contain a medium. > Sep 23 20:06:52 hofmann1 kernel: cdrom: open failed. > Sep 23 20:06:52 hofmann1 kernel: cdrom: door unlocked. > Sep 23 20:06:52 hofmann1 kernel: cdrom: Use count for "/dev/hdd" now 0 > Sep 23 20:06:52 hofmann1 kernel: cdrom: entering cdrom_open > Sep 23 20:06:52 hofmann1 kernel: cdrom: entering cdrom_open > Sep 23 20:06:52 hofmann1 kernel: cdrom: entering open_for_data > Sep 23 20:06:52 hofmann1 kernel: cdrom: drive_status=2 > Sep 23 20:06:52 hofmann1 kernel: cdrom: the tray is open... > Sep 23 20:06:52 hofmann1 kernel: cdrom: trying to close the tray. > Sep 23 20:06:52 hofmann1 kernel: cdrom: bummer. the tray is still not closed. > Sep 23 20:06:52 hofmann1 kernel: cdrom: tray might not contain a medium. > Sep 23 20:06:52 hofmann1 kernel: cdrom: open failed. > Sep 23 20:06:52 hofmann1 kernel: cdrom: door unlocked. > Sep 23 20:06:52 hofmann1 kernel: cdrom: Use count for "/dev/hdd" now 0 > Sep 23 20:06:52 hofmann1 kernel: cdrom: entering cdrom_open > Sep 23 20:06:52 hofmann1 kernel: cdrom: entering open_for_data > Sep 23 20:06:52 hofmann1 kernel: cdrom: drive_status=2 > Sep 23 20:06:52 hofmann1 kernel: cdrom: the tray is open... > Sep 23 20:06:52 hofmann1 kernel: cdrom: trying to close the tray. > Sep 23 20:06:52 hofmann1 kernel: cdrom: bummer. the tray is still not closed. > Sep 23 20:06:52 hofmann1 kernel: cdrom: tray might not contain a medium. > Sep 23 20:06:52 hofmann1 kernel: cdrom: open failed. > Sep 23 20:06:52 hofmann1 kernel: cdrom: door unlocked. > Sep 23 20:06:52 hofmann1 kernel: cdrom: Use count for "/dev/hdd" now 0 > > > On 24 Sep 2000, at 2:43 Jens Axboe wrote: > > > On Sat, Sep 23 2000, Glenn C. Hofmann wrote: > > > As of the more recent kernels (2.4.0-test8,7,6 for sure) both my IDE and > > > SCSI CD-ROM drives will not mount a disk. They fail and tell me that > > > there is no disk in the drive. I booted into an old 2.0.36 kernel just > > > to make sure it wasn't a strange hardware failure and the CD mounted fine. > > > I have attached my .config and dmesg, which shows that the drives are > > > recognised. If there is any further information that I can give, I would > > > be happy to. Thanks in advance for any help. > > > > Could you try and isolate the kernel that breaks this? It sounds very > > odd that both your ATAPI and SCSI drive is affected. Also, could you > > try and mount a drive with debugging enabled in the uniform cd layer? > > > > echo "1" > /proc/sys/dev/cdrom/debug > > > > -- > > * Jens Axboe <[EMAIL PROTECTED]> > > * SuSE Labs > > > - > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in > the body of a message to [EMAIL PROTECTED] > Please read the FAQ at http://www.tux.org/lkml/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: (Fwd) CD-ROM (SCSI and IDE) not mounting disk
I will try to recompile some older kernels and see where it breaks, but here is the output in the logs when I try to mount the CD. I enabled debugging, as well. Found in debug logfile: Sep 23 19:58:05 hofmann1 kernel: VFS: Disk change detected on device ide1(22,64) Sep 23 19:58:05 hofmann1 last message repeated 2 times Sep 23 20:01:07 hofmann1 kernel: VFS: Disk change detected on device ide1(22,64) Sep 23 20:01:07 hofmann1 last message repeated 2 times And in messages logfile: Sep 23 20:06:52 hofmann1 kernel: cdrom: entering cdrom_open Sep 23 20:06:52 hofmann1 kernel: cdrom: entering open_for_data Sep 23 20:06:52 hofmann1 kernel: cdrom: drive_status=2 Sep 23 20:06:52 hofmann1 kernel: cdrom: the tray is open... Sep 23 20:06:52 hofmann1 kernel: cdrom: trying to close the tray. Sep 23 20:06:52 hofmann1 kernel: cdrom: bummer. the tray is still not closed. Sep 23 20:06:52 hofmann1 kernel: cdrom: tray might not contain a medium. Sep 23 20:06:52 hofmann1 kernel: cdrom: open failed. Sep 23 20:06:52 hofmann1 kernel: cdrom: door unlocked. Sep 23 20:06:52 hofmann1 kernel: cdrom: Use count for "/dev/hdd" now 0 Sep 23 20:06:52 hofmann1 kernel: cdrom: entering cdrom_open Sep 23 20:06:52 hofmann1 kernel: cdrom: entering cdrom_open Sep 23 20:06:52 hofmann1 kernel: cdrom: entering open_for_data Sep 23 20:06:52 hofmann1 kernel: cdrom: drive_status=2 Sep 23 20:06:52 hofmann1 kernel: cdrom: the tray is open... Sep 23 20:06:52 hofmann1 kernel: cdrom: trying to close the tray. Sep 23 20:06:52 hofmann1 kernel: cdrom: bummer. the tray is still not closed. Sep 23 20:06:52 hofmann1 kernel: cdrom: tray might not contain a medium. Sep 23 20:06:52 hofmann1 kernel: cdrom: open failed. Sep 23 20:06:52 hofmann1 kernel: cdrom: door unlocked. Sep 23 20:06:52 hofmann1 kernel: cdrom: Use count for "/dev/hdd" now 0 Sep 23 20:06:52 hofmann1 kernel: cdrom: entering cdrom_open Sep 23 20:06:52 hofmann1 kernel: cdrom: entering open_for_data Sep 23 20:06:52 hofmann1 kernel: cdrom: drive_status=2 Sep 23 20:06:52 hofmann1 kernel: cdrom: the tray is open... Sep 23 20:06:52 hofmann1 kernel: cdrom: trying to close the tray. Sep 23 20:06:52 hofmann1 kernel: cdrom: bummer. the tray is still not closed. Sep 23 20:06:52 hofmann1 kernel: cdrom: tray might not contain a medium. Sep 23 20:06:52 hofmann1 kernel: cdrom: open failed. Sep 23 20:06:52 hofmann1 kernel: cdrom: door unlocked. Sep 23 20:06:52 hofmann1 kernel: cdrom: Use count for "/dev/hdd" now 0 On 24 Sep 2000, at 2:43 Jens Axboe wrote: > On Sat, Sep 23 2000, Glenn C. Hofmann wrote: > > As of the more recent kernels (2.4.0-test8,7,6 for sure) both my IDE and > > SCSI CD-ROM drives will not mount a disk. They fail and tell me that > > there is no disk in the drive. I booted into an old 2.0.36 kernel just > > to make sure it wasn't a strange hardware failure and the CD mounted fine. > > I have attached my .config and dmesg, which shows that the drives are > > recognised. If there is any further information that I can give, I would > > be happy to. Thanks in advance for any help. > > Could you try and isolate the kernel that breaks this? It sounds very > odd that both your ATAPI and SCSI drive is affected. Also, could you > try and mount a drive with debugging enabled in the uniform cd layer? > > echo "1" > /proc/sys/dev/cdrom/debug > > -- > * Jens Axboe <[EMAIL PROTECTED]> > * SuSE Labs - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
(Fwd) CD-ROM (SCSI and IDE) not mounting disk
Sorry, the files are attached this time... --- Forwarded message follows --- Date sent: Sun, 24 Sep 2000 00:35:57 + (GMT) From: "Glenn C. Hofmann" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Date sent: Sat, 23 Sep 2000 19:40:19 -0500 Subject:CD-ROM (SCSI and IDE) not mounting disk Send reply to: [EMAIL PROTECTED] As of the more recent kernels (2.4.0-test8,7,6 for sure) both my IDE and SCSI CD-ROM drives will not mount a disk. They fail and tell me that there is no disk in the drive. I booted into an old 2.0.36 kernel just to make sure it wasn't a strange hardware failure and the CD mounted fine. I have attached my .config and dmesg, which shows that the drives are recognised. If there is any further information that I can give, I would be happy to. Thanks in advance for any help. Chris Hofmann --==-- "Our scientific power has outrun our spiritual power. We have guided missiles and misguided men - Martin Luther King, Jr --==-- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/ --- End of forwarded message --- Chris Hofmann --==-- "An open mind, in questions that are not ultimate, is useful. But an open mind about ultimate foundations either of Theoretical or Practical Reason is idiocy. If a manÆs mind is open on these things, let his mouth at least be shut. " --C. S. Lewis "The Abolition Of Man" --==-- Linux version 2.4.0-test9 (root@hofmann1) (gcc version 2.95.2 2220 (Debian GNU/Linux)) #4 Sat Sep 23 14:27:57 CDT 2000 BIOS-provided physical RAM map: BIOS-e820: 0009fc00 @ (usable) BIOS-e820: 0400 @ 0009fc00 (reserved) BIOS-e820: 0002 @ 000e (reserved) BIOS-e820: 05ef @ 0010 (usable) BIOS-e820: 8000 @ 05ff (ACPI data) BIOS-e820: 8000 @ 05ff8000 (ACPI NVS) BIOS-e820: 1000 @ fec0 (reserved) BIOS-e820: 1000 @ fee0 (reserved) BIOS-e820: 0002 @ fffe (reserved) Scan SMP from c000 for 1024 bytes. Scan SMP from c009fc00 for 1024 bytes. Scan SMP from c00f for 65536 bytes. Scan SMP from c009fc00 for 4096 bytes. On node 0 totalpages: 24560 zone(0): 4096 pages. zone(1): 20464 pages. zone(2): 0 pages. mapped APIC to e000 (0119a000) Kernel command line: BOOT_IMAGE=test ro root=344 BOOT_FILE=/vm2.4b Initializing CPU#0 Detected 233.031 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 465.31 BogoMIPS Memory: 93632k/98240k available (1994k kernel code, 4220k reserved, 132k data, 228k init, 0k highmem) Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes) Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes) Page-cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 8192 (order: 4, 65536 bytes) CPU: L1 I Cache: 32K L1 D Cache: 32K (32 bytes/line) CPU: AMD-K6tm w/ multimedia extensions stepping 02 Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX PCI: PCI BIOS revision 2.10 entry at 0xfdba1, last bus=0 PCI: Using configuration type 1 PCI: Probing PCI hardware Limiting direct PCI/PCI transfers. Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. NET4: Linux TCP/IP 1.0 for NET4.0 IP Protocols: ICMP, UDP, TCP, IGMP IP: routing cache hash table of 512 buckets, 4Kbytes TCP: Hash tables configured (established 8192 bind 8192) GRE over IPv4 tunneling driver early initialization of device gre0 is deferred Linux IP multicast router 0.06 plus PIM-SM IPv6 v0.8 for NET4.0 IPv6 over IPv4 tunneling driver early initialization of device sit0 is deferred NET4: Linux IPX 0.38 for NET4.0 IPX Portions Copyright (c) 1995 Caldera, Inc. Registered PPPoX v0.5 Registered PPPoE v0.5 ACPI: "AMIINT" found at 0x000f71d0 Starting kswapd v1.8 Winbond Super-IO detection, now testing ports 3F0,370,250,4E,2E ... SMSC Super-IO detection, now testing Ports 2F0, 370 ... 0x378: FIFO is 16 bytes 0x378: writeIntrThreshold is 8 0x378: readIntrThreshold is 8 0x378: PWord is 8 bits 0x378: Interrupts are ISA-Pulses 0x378: possible IRQ conflict! 0x378: ECP port cfgA=0x14 cfgB=0x00 0x378: ECP settings irq= dma= parport0: PC-style at 0x378 (0x778) [PCSPP,TRISTATE,COMPAT,EPP,ECP] parport0: cpp_mux: aa55f00f52ad51(bf) parport0: cpp_daisy: aa5500ff87(b8) parport0: assign_addrs: aa5500ff87(b8) parport0: Printer, EPSON STYLUS COLOR II i2c-core.o: i2c core module i2c-dev.o: i2c /dev entries driver module i2c-core.o: driver i2c-dev dummy driver registered. piix4.o version 2.5.2 (2709) i2c-dev.o: Registered 'SMBus PIIX4 adapter
CD-ROM (SCSI and IDE) not mounting disk
As of the more recent kernels (2.4.0-test8,7,6 for sure) both my IDE and SCSI CD-ROM drives will not mount a disk. They fail and tell me that there is no disk in the drive. I booted into an old 2.0.36 kernel just to make sure it wasn't a strange hardware failure and the CD mounted fine. I have attached my .config and dmesg, which shows that the drives are recognised. If there is any further information that I can give, I would be happy to. Thanks in advance for any help. Chris Hofmann --==-- "Our scientific power has outrun our spiritual power. We have guided missiles and misguided men - Martin Luther King, Jr --==-- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
