debian kernel bugs / or is it grub?
Richard van der Veen
I am not sure how to send a bug report about this because it seems to
be in several different kernels from Debian. (maybe it even is not
kernel specific but it's grub which is doing something wrong.)
When i replaced my ATA DVD writer with an SATA DVD writer and placed
another ATA harddisk on the connector, i got in my selfbuild kernel(*1
an OOPS. This made me decide to re-install debian. I downloaded a
daily-build netinstall CD from Lenny and wanted to convert that to Sid
- because that is my normal debian 'outfit' on the computer. With the
installation everything went smoothly, but when i rebooted the
computer crashed/hanged on booting the kernel. The message on the
screen was:
--
PCI:BIOS BUG: MCFG area at f0000000 is not E820-reserved
PCI: Not using MMCONFIG
PCI: Failed to allocate mem resource #6:20000@90000000 for 0000:01:00
Loading , please wait....
ide0: I/O resource 0x3F6-0x3F6 not free.
ide0: ports already in use, skipping probe
ide1: I/O resource 0x376-0x376 not free.
ide1: ports already in use, skipping probe
--
hang
So i tried an earlier netinstall CD which i had laying around. But
that one did not recognize my two ATA disks at all but only showed the
SATA disk. (maybe i had to include the generic_ide option or so).
But it seemed i could not use Debian anymore. I tried with other
distributions and there was nothing wrong with that. I could install
Fedora 7 (2.6.21 kernel) on the same disk and use, I can install
Ubuntu 7.10 (2.6.22 kernel) on the same disk and use. But only Debian
give me this strange error message. I even tried to download the
ubuntu kernel and in install this on debian (in a chroot; which i set
up like people do when they install Gentoo (- mounted /proc too)) ...
Also chrooted i build my own kernel again from pre-configured 2.6.22.6
sources which i used before which gave me the OOPS to begin with. But
also this kernel did not change the problem i was experiencing
(*1. I build my own kernel to remove the option of PARA_VIRT because
that did keep me from installing the NVIDIA driver which i wanted to
use to enable compiz.
I did read somewhere that the "only GPL modules can be loaded"
restriction was removed with the 2.6.6.22 kernel
thanks for reading and i hope some people can help me back on debian,
because this is and stays my favorite distribution.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Andrew Sackville-West
> Hi
> I am not sure how to send a bug report about this because it seems to
> be in several different kernels from Debian. (maybe it even is not
> kernel specific but it's grub which is doing something wrong.)
>
> When i replaced my ATA DVD writer with an SATA DVD writer and placed
> another ATA harddisk on the connector, i got in my selfbuild kernel(*1
> an OOPS. This made me decide to re-install debian. I downloaded a
> daily-build netinstall CD from Lenny and wanted to convert that to Sid
> - because that is my normal debian 'outfit' on the computer. With the
> installation everything went smoothly, but when i rebooted the
> computer crashed/hanged on booting the kernel. The message on the
> screen was:
> --
> PCI:BIOS BUG: MCFG area at f0000000 is not E820-reserved
> PCI: Not using MMCONFIG
> PCI: Failed to allocate mem resource #6:20000@90000000 for 0000:01:00
> Loading , please wait....
> ide0: I/O resource 0x3F6-0x3F6 not free.
> ide0: ports already in use, skipping probe
> ide1: I/O resource 0x376-0x376 not free.
> ide1: ports already in use, skipping probe
> --
> hang
what happens if you pull that dvd drive and boot? Looks to me like
you've got a nasty hardware conflict going on. I'd start with some
easy swaps like pulling that drive and then move up to futzing with
the bios.
its not much, but I hth.
A
Ben Evenweg
Well ... to me it does not seem like a conflict in my hardware because
as i said before Fedora 7, Opensuse 10.3 and Ubuntu Gutsy (BETA) seems
to work perfectly well with this hardware configuration. Only Debian has
trouble to work on it - can not even let the kernel boot. Then my
conclusion is that it is Debian related and not hardware related. But
strange because Ubuntu is for a big part also just Debian. Anyway thank
you for your response.
Andrew Sackville-West
whoops. I must have missed (and snipped) that. I assume the messages
above are from the kernel itself?
Is it possible that you've got a bad initrd and that's causing the
problem? You could boot with a live-cd, chroot in and rebuild your
initrd maybe.
A
Richard
Yes, the message i quoted comes almost instantly after the grub menu
when the kernel tries to load.
> Is it possible that you've got a bad initrd and that's causing the
> problem? You could boot with a live-cd, chroot in and rebuild your
> initrd maybe.
:-) As i also wrote in my first post, i tried several ways to get other
kernels to boot. From Ubuntu i chrooted into the fresh Debian
installation and loaded/installed the Ubuntu kernel (with no succes), i
build a custom kernel from 2.6.22.6 sources without initrd (with no
succes). All without the desired effect of me being able to boot into
Debian again. So in my view now grub also gets suspected because this
can't load the kernel.
I am now using Ubuntu and it looks very nice, maybe i try Debian a few
weeks later again or so, when my mood feels like it. And then i will try
lilo.
thanx
Richard
Andrew Sackville-West
> Andrew Sackville-West wrote:
...
>
> > whoops. I must have missed (and snipped) that. I assume the messages
> > above are from the kernel itself?
>
> Yes, the message i quoted comes almost instantly after the grub menu
> when the kernel tries to load.
>
have you tried loading the kernel by hand from the
grub>
prompt?
> > Is it possible that you've got a bad initrd and that's causing the
> > problem? You could boot with a live-cd, chroot in and rebuild your
> > initrd maybe.
>
> :-) As i also wrote in my first post, i tried several ways to get other
> kernels to boot. From Ubuntu i chrooted into the fresh Debian
> installation and loaded/installed the Ubuntu kernel (with no succes), i
> build a custom kernel from 2.6.22.6 sources without initrd (with no
> succes). All without the desired effect of me being able to boot into
> Debian again. So in my view now grub also gets suspected because this
> can't load the kernel.
yeah, I would say grub is suspect as well. You can reinstall grub from
within the chroot too, FWIW.
>
> I am now using Ubuntu and it looks very nice, maybe i try Debian a few
> weeks later again or so, when my mood feels like it. And then i will try
> lilo.
I was going to suggest trying lilo as well.
I find it hard to understand how ubuntu can boot when debian
can't. I'm willing to be that if you end up reinstalling debian again,
it just works. shrug.
A
Richard
....
> I find it hard to understand how ubuntu can boot when debian
> can't. I'm willing to be that if you end up reinstalling debian again,
> it just works. shrug.
>
> A
Back in Ubuntu again after another unsuccessful install-round with
Debian. Tried again, a little sooner as expected. Seems i like Debian
and really want it back on my system. What i tried is:
--------
daily netinstall and use lilo instead of grub ...
crash while loading the kernel an dropped in an initramfs prompt. Again
with the ide-0 and ide-1 are busy messages. A lot more text.
LILO 22.8 Loading
Linux.........................................................................
................................................................................................
BIOS data check successful
Uncompressing Linux... OK, booting the kernel.
PCI:BIOS BUG: MCFG area at f0000000 is not E820-reserved
PCI: Not using MMCONFIG
PCI: Failed to allocate mem resource #6:20000@90000000 for 0000:01:00.0
Loading , please wait....
ide0: I/O resource 0x3F6-0x3F6 not free.
ide0: ports already in use, skipping probe
ide1: I/O resource 0x376-0x376 not free.
ide1: ports already in use, skipping probe
mount: Mounting /dev/root on /root failed: No such device
mount: Mounting /root/dev/ on /dev/.static/dev failed: No such file or
directory
mount: Mounting /sys on /root/sys failed: No such file or directory
mount: Mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have /sbin/init
BusyBox v1.1.3 (Debian 1:1.1.3-5) Built-in shell (ash)
Enter 'help' for a list of built-in commands.
/bin/sh: can't access tty; job control turned off
(initramfs)
When i try to install Debian my two ATA hard disks are recognized as
/dev/sdf and /dev/sdg. When i use lilo udev makes only /dev/sda /dev/sdb
and /dev/sdc block-devices. Next time i will try to install Debian i
will try to use.
append="idebus=66 pci=routeirq libata.atapi_enabled=1 all-generic-ide"
----------
etch install ...
no ATA disk found.
----------
etch install generic.all_generic_ide=1
some kind of kernel OOPS when loading the installer; at least it looks a
lot like that, did not continue. Seems every device is recognized as ATA
device; also my SATA DVD writer and SATA hard disk. Here is the dmesg
output which i could catch:
Probing IDE interface ide0...
usb 7-5: new high speed USB device using ehci_hcd and address 2
hda: ST3250820AS, ATA DISK drive
usb 7-5: configuration #1 chosen from 1 choice
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
Unknown: IDE controller at PCI slot 0000:00:1f.5
ACPI: PCI Interrupt 0000:00:1f.5[A] -> GSI 19 (level, low) -> IRQ 193
Unknown: chipset revision 2
Unknown: 100% native mode on irq 193
ide2: BM-DMA at 0x30f0-0x30f7, BIOS settings: hde:DMA, hdf:pio
ide3: BM-DMA at 0x30f8-0x30ff, BIOS settings: hdg:pio, hdh:pio
Probing IDE interface ide2...
hde: LITE-ON DVDRW LH-20A1S, ATAPI CD/DVD-ROM drive
ide2 at 0x3428-0x342f,0x3446 on irq 193
Probing IDE interface ide3...
Unknown: IDE controller at PCI slot 0000:03:00.0
ACPI: PCI Interrupt 0000:03:00.0[A] -> GSI 17 (level, low) -> IRQ 177
Unknown: chipset revision 177
Unknown: 100% native mode on irq 177
ide4: BM-DMA at 0x1000-0x1007, BIOS settings: hdi:DMA, hdj:DMA
ide5: BM-DMA at 0x1008-0x100f, BIOS settings: hdk:DMA, hdl:DMA
Probing IDE interface ide4...
hdi: ST3200826A, ATA DISK drive
hdj: ST3320620A, ATA DISK drive
ide4 at 0x1018-0x101f,0x1026 on irq 177
Probing IDE interface ide5...
Vendor: Generic Model: USB SD Reader Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 00
Vendor: Generic Model: USB CF Reader Rev: 1.01
Type: Direct-Access ANSI SCSI revision: 00
Vendor: Generic Model: USB SM Reader Rev: 1.02
Type: Direct-Access ANSI SCSI revision: 00
Vendor: Generic Model: USB MS Reader Rev: 1.03
Type: Direct-Access ANSI SCSI revision: 00
sd 0:0:0:0: Attached scsi removable disk sda
sd 0:0:0:1: Attached scsi removable disk sdb
usb-storage: device scan complete
sd 0:0:0:2: Attached scsi removable disk sdc
sd 0:0:0:3: Attached scsi removable disk sdd
hda: max request size: 512KiB
hda: 488397168 sectors (250059 MB) w/8192KiB Cache, CHS=30401/255/63
hda: cache flushes supported
hda: hda1 hda2 < hda5 hda6 hda7 hda8 hda9 hda10 >
hdi: max request size: 512KiB
hdi: 390721968 sectors (200049 MB) w/8192KiB Cache, CHS=24321/255/63,
UDMA(33)
hdi: cache flushes supported
hdi:<6>hde: ATAPI 48X DVD-ROM DVD-R-RAM CD-R/RW drive, 2048kB Cache
Uniform CD-ROM driver Revision: 3.20
hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying
to recover by ending request.
hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying
to recover by ending request.
hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hde: drive not ready for command
hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hde: drive not ready for command
hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hde: drive not ready for command
hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hde: DMA disabled
hde: drive not ready for command
hdi1 hdi2 hdi3 < hdi5 hdi6 hdi7hde: ATAPI reset complete
hdi8<3>hde: cdrom_pc_intr: The drive appears confused (ireason =
0x01). Trying to recover by ending request.
hdi9 hdi10 >
hdj: max request size: 512KiB
hdj: 625142448 sectors (320072 MB) w/16384KiB Cache, CHS=38913/255/63,
UDMA(33)
hdj: cache flushes supported
hdj: hdj1 hdj2 hdj3 < hdj5 hdj6 hdj7 hdj8 hdj9 >
hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hde: drive not ready for command
hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hde: drive not ready for command
hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hde: drive not ready for command
hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hde: drive not ready for command
hde: ATAPI reset complete
hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying
to recover by ending request.
hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying
to recover by ending request.
hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying
to recover by ending request.
hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hde: drive not ready for command
hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hde: drive not ready for command
hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hde: drive not ready for command
hde: status error: status=0x58 { DriveReady SeekComplete DataRequest }
ide: failed opcode was: unknown
hde: drive not ready for command
hde: ATAPI reset complete
hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying
to recover by ending request.
hde: status error: status=0x48 { DriveReady DataRequest }
ide: failed opcode was: unknown
hde: drive not ready for command
hde: status error: status=0x48 { DriveReady DataRequest }
ide: failed opcode was: unknown
hde: drive not ready for command
hde: status error: status=0x48 { DriveReady DataRequest }
ide: failed opcode was: unknown
hde: drive not ready for command
hde: status error: status=0x48 { DriveReady DataRequest }
ide: failed opcode was: unknown
hde: drive not ready for command
hde: ATAPI reset complete
hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying
to recover by ending request.
hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying
to recover by ending request.
hde: cdrom_pc_intr: The drive appears confused (ireason = 0x01). Trying
to recover by ending request.
irq 193: nobody cared (try booting with the "irqpoll" option)
[<c0131ea7>] __report_bad_irq+0x2b/0x69
[<c013206d>] note_interrupt+0x188/0x1bf
[<c01317c3>] handle_IRQ_event+0x23/0x49
[<c013185b>] __do_IRQ+0x72/0xa1
[<c010506f>] do_IRQ+0x43/0x50
[<c0103a9a>] common_interrupt+0x1a/0x20
[<c011855a>] __do_softirq+0x2c/0x75
[<c01185c5>] do_softirq+0x22/0x26
[<c0105074>] do_IRQ+0x48/0x50
[<c0103a9a>] common_interrupt+0x1a/0x20
[<c013b635>] do_wp_page+0x116/0x303
[<c013c740>] __handle_mm_fault+0x585/0x620
[<c0121280>] __rcu_process_callbacks+0xce/0x128
[<c01108b7>] do_page_fault+0x18b/0x498
[<c011072c>] do_page_fault+0x0/0x498
[<c0103b79>] error_code+0x39/0x40
handlers:
[<f885129b>] (usb_hcd_irq+0x0/0x4a [usbcore])
[<f8a74d9b>] (ide_intr+0x0/0x171 [ide_core])
Disabling IRQ #193
ACPI: Processor [CPU0] (supports 8 throttling states)
ACPI: Getting cpuindex for acpiid 0x2
ACPI: Getting cpuindex for acpiid 0x3
ACPI: Getting cpuindex for acpiid 0x4
usbcore: registered new driver usbkbd
drivers/usb/input/usbkbd.c: :USB HID Boot Protocol keyboard driver
usbcore: registered new driver hiddev
usbcore: registered new driver usbhid
drivers/usb/input/hid-core.c: v2.6:USB HID core driver
usbcore: registered new driver usbserial
drivers/usb/serial/usb-serial.c: USB Serial support registered for generic
usbcore: registered new driver usbserial_generic
drivers/usb/serial/usb-serial.c: USB Serial Driver core
vga16fb: initializing
vga16fb: mapped to 0xc00a0000
fb1: VGA16 VGA frame buffer device
usbcore: registered new driver usbmouse
drivers/usb/input/usbmouse.c: v1.6:USB HID Boot Protocol mouse driver
As you can see in line 13 of this output, the IDE controller does not
get recognized.
=========Change setting in the BIOS -> Advanced -> ATA/IDE Mode ->
changed Legacy into Native
-----------
daily netinstall
no ATA disk found
-----------
daily netinstall generic.all_generic_ide=1
some kind of kernel OOPS when loading the installer; did not continue.
Very strange, because i am back on Ubuntu on the same disk with the same
BIOS disk settings as i used to try to install Debian.
Andrew Sackville-West
> Andrew Sackville-West wrote:
> ....
>
> > I find it hard to understand how ubuntu can boot when debian
> > can't. I'm willing to be that if you end up reinstalling debian again,
> > it just works. shrug.
> >
> > A
>
> Back in Ubuntu again after another unsuccessful install-round with
Debian.
Are you reinstalling ubuntu to the same drive you are trying for
debian? or using some other drive and swapping stuff around?
I ask because all those errors you posted make me still think you've
got some hardware problem. BUt I'm no expert by far.
So what, if any differences are there between the ubuntu install and
debian install. And I mean *any* differences: changed cables, changed
drive order on cables, swapped drives, anything.
Also, as an aside, you could try debian from the ubuntu install using
debootstrap. Instructions here:
http://www.debian.org/releases/stable/i386/apds03.html.en
good luck
A
David Brodbeck
On Oct 12, 2007, at 11:25 AM, Andrew Sackville-West wrote:
> I ask because all those errors you posted make me still think you've
> got some hardware problem. BUt I'm no expert by far.
Just as an aside, I've had occasional problems with Linux on machines
that had IDE hard drives set to "cable select" mode. Manually
jumpering them to master and slave fixed it. Windows worked fine on
the same systems.
Andrew Sackville-West
>
> On Oct 12, 2007, at 11:25 AM, Andrew Sackville-West wrote:
>
>> I ask because all those errors you posted make me still think you've
>> got some hardware problem. BUt I'm no expert by far.
>
> Just as an aside, I've had occasional problems with Linux on machines that
> had IDE hard drives set to "cable select" mode. Manually jumpering them to
> master and slave fixed it. Windows worked fine on the same systems.
that's an excellent point. I've seen that too.
A
Richard
> On Fri, Oct 12, 2007 at 02:03:05PM +0800, Richard wrote:
>> Andrew Sackville-West wrote:
>> ....
>>
>>> I find it hard to understand how ubuntu can boot when debian
>>> can't. I'm willing to be that if you end up reinstalling debian again,
>>> it just works. shrug.
>>>
>>> A
>> Back in Ubuntu again after another unsuccessful install-round with
>> Debian.
> Are you reinstalling ubuntu to the same drive you are trying for
> debian? or using some other drive and swapping stuff around?
Yes, Exact the same drive configuration. Just put the Ubuntu disk in the
DVD-drive after an unsuccessful Debian-session and install on the same
hard disk. Did not change anything in the BIOS or so. But Ubuntu and
other distributions see my 2 ATA + 1 SATA HD's as /dev/sda, /dev/sdb and
/dev/sdc. And Debian makes from my two ATA hd's /dev/sdf and /dev/sdg
> I ask because all those errors you posted make me still think you've
> got some hardware problem. BUt I'm no expert by far.
Well guess what: Because I also wanted to see what Mandriva 2008.0 looks
like, I installed that on the drive I wanted to use for Debian (again
also just the same BIOS settings). And ... as I expected there is no
problem at all to install it and to use it.
> So what, if any differences are there between the ubuntu install and
> debian install. And I mean *any* differences: changed cables, changed
> drive order on cables, swapped drives, anything.
No difference: no changed cables, no changed BIOS settings etc.
> Also, as an aside, you could try debian from the ubuntu install using
> debootstrap. Instructions here:
> http://www.debian.org/releases/stable/i386/apds03.html.en
Will think about it :-)
> good luck
Thanks
> A
Richard
PS Since I used Lilo last time to boot I guess I can say grub is not the
cause of the problem. Now I suspect it is udev and/or the lack of
support for the Intel P965 chipset. But it is only Debian related.
PPS I now installed Mandriva on the 'Debian drive' because I expect I
will not really use that a lot and will format the soon again to make
place for Debian. (If Debian let me)
Richard
>
> On Oct 12, 2007, at 11:25 AM, Andrew Sackville-West wrote:
>
>> got some hardware problem. BUt I'm no expert by far.
>
> that had IDE hard drives set to "cable select" mode. Manually jumpering
> them to master and slave fixed it. Windows worked fine on the same
> systems.
My two IDE drives are configured as Master and Slave by jumper settings.
Not by cable select. With my drive configuration already 4 other Linux
distributions work fine: Fedora 7 (no problem), Ubuntu 7.10 (no
problem), Mandriva 2008.0 (no problem), OpenSuse 10.3 (although on
another drive - no problem)
Andrew Sackville-West
...
>
> No difference: no changed cables, no changed BIOS settings etc.
>
>
>
> PS Since I used Lilo last time to boot I guess I can say grub is not the
> cause of the problem. Now I suspect it is udev and/or the lack of support
> for the Intel P965 chipset. But it is only Debian related.
is this that same chipset that has funky fake ide interfaces that are
emulated over SATA? if so, I think you are not alone at the
moment. either way, sorry to hear its not working and good luck in the
future.
A