Re: [Cooker] kernel panic debugging
Le Mardi 28 Janvier 2003 17:18, Chmouel Boudjnah a écrit : Pascal Cavy [EMAIL PROTECTED] writes: 6. reboot this time the boot stops (in harddrake ?) I absolutly cannot have a complete boot this time until I replugged the mouse and harddrake configures it. would you reproduce when removing completely hardrake ? OK I have done another test session :) 1. with kernel kernel-enterprise-2.4.21.0.pre3.2mdk-1-1mdk removing harddrake had no influence. The boot still hang if you have played with usb devices before rebooting (unplug replug at other usb ports etc) 2. with latest kernel kernel-enterprise-2.4.21.0.pre4.1mdk-1-1mdk NO MORE HANGS :) So now chmouel you can breathe again. seems the pre4 stuff has fixed the problem ? PS: latest kernel installation complained that the label 2421-1ent already exists :P another one to fix ;) I renamed my old lilo entries to get the new one automatically added by the rpm. -- Pascal Cavy - VMF __ Running 9 min, 3 users, load average: 0.11, 0.32, 0.24 (gcc version 3.2.1 (Mandrake Linux 9.1 3.2.1-4mdk)) Kernel Linux version 2.4.21pre4-1mdkenterprise
Re: [Cooker] kernel panic debugging
Pascal Cavy [EMAIL PROTECTED] writes: So now chmouel you can breathe again. seems the pre4 stuff has fixed the problem ? good to know ;) PS: latest kernel installation complained that the label 2421-1ent already exists :P another one to fix ;) I renamed my old lilo entries to get the new one automatically added by the rpm. oh sh!! that naming start to piss (no i don't speak british english why i say piss i say really pissed-off) me off :p
Re: [Cooker] kernel panic debugging
On Thursday 30 January 2003 11:13 am, Chmouel Boudjnah wrote: Pascal Cavy [EMAIL PROTECTED] writes: So now chmouel you can breathe again. seems the pre4 stuff has fixed the problem ? good to know ;) PS: latest kernel installation complained that the label 2421-1ent already exists :P another one to fix ;) I renamed my old lilo entries to get the new one automatically added by the rpm. oh sh!! that naming start to piss (no i don't speak british english why i say piss i say really pissed-off) me off :p Is there any reason that kernel-2.4.21.0.pre4.1mdk-1-1mdk is missing /boot/kernel.h-2.4.21pre4-1mdk? Thanks. -- Bret Baptist Systems and Technical Support Specialist [EMAIL PROTECTED] Internet Exposure, Inc. http://www.iexposure.com (612)676-1946 x17 Web Development-Web Marketing-ISP Services -- Today is the tomorrow you worried about yesterday.
Re: [Cooker] kernel panic debugging
Bret Baptist [EMAIL PROTECTED] writes: Is there any reason that kernel-2.4.21.0.pre4.1mdk-1-1mdk is missing /boot/kernel.h-2.4.21pre4-1mdk? not it should not what : service --debug kheader start output ? (try to get only the interessing stuff please)
Re: USB disk drive problems - was Re: [Cooker] kernel panic debugging
Can't locate the original URL but here is the patch file anyway:
Owen
John Danielson, II wrote:
Chmouel Boudjnah wrote:
Owen Savill [EMAIL PROTECTED] writes:
3) There is a kernel patch for the SanDisk USB disk caddies but this
does not appear to have been incorporated into the Mandrake kernel.
look weird, i don't have such beast to test, but if you point me to it
i will maybe integrated.
Might be very useful to look at the code for that-- SanDisk can use
memory cards as virtual disks. Some IBM Microdisks work on a similar
theme driver-wise, as there are both PCMCIA and memory card reader
adapters for same. Essentially, SanDisk has what they call\classify as a
virtual drive adapter, but it is mostly an IC memory module reader for
one of their module lines. Large IC cards with 256 MB and up were made
for high-density digital cameras, and it was convenient to have readers
that handled them as HDs for older PCs that were USB capable but not USB
2.0 capable. In the US, about 5 variants of this theme exist (IC card as
virtual HD, reversing the SWAP idea for portability of data
convenience). Take a pocket sized reader, floppy or CD with drivers, and
high capacity card to any USB capable box, install drivers, run and
carry decent sized chunks of data in tiny package about size of a CD
Business card to any box that will take the data and has USB capable
O/S. Some of these run at USB 2.0 rates.
John.
diff -u --recursive linux-2.4.18-pre3/drivers/usb/storage/transport.c
linux/drivers/usb/storage/transport.c
--- linux-2.4.18-pre3/drivers/usb/storage/transport.c Thu Jan 10 13:08:18 2002
+++ linux/drivers/usb/storage/transport.c Thu Jan 10 13:13:36 2002
@@ -1157,7 +1157,7 @@
le32_to_cpu(bcs.Signature), bcs.Tag,
bcs.Residue, bcs.Status);
if (bcs.Signature != cpu_to_le32(US_BULK_CS_SIGN) ||
- bcs.Tag != bcb.Tag ||
+ ((bcs.Tag != bcb.Tag ) (!(us-flags US_FL_SL_IDE_BUG))) ||
bcs.Status US_BULK_STAT_PHASE || partial != 13) {
US_DEBUGP(Bulk logical error\n);
return USB_STOR_TRANSPORT_ERROR;
diff -u --recursive linux-2.4.18-pre3/drivers/usb/storage/unusual_devs.h
linux/drivers/usb/storage/unusual_devs.h
--- linux-2.4.18-pre3/drivers/usb/storage/unusual_devs.hThu Jan 10 13:08:18
2002
+++ linux/drivers/usb/storage/unusual_devs.hThu Jan 10 13:13:36 2002
@@ -110,6 +110,28 @@
LS-120 Camera,
US_SC_UFI, US_PR_CBI, NULL, 0),
+/* Reported by Peter Wächtler [EMAIL PROTECTED] */
+UNUSUAL_DEV( 0x04ce, 0x0002, 0x0074, 0x0074,
+ ScanLogic,
+ SL11R-IDE 0049SQFP-1.2 A002,
+ US_SC_SCSI, US_PR_BULK, NULL,
+ US_FL_FIX_INQUIRY ),
+
+/* Reported by Leif Sawyer [EMAIL PROTECTED] */
+UNUSUAL_DEV( 0x04ce, 0x0002, 0x0240, 0x0240,
+ H45 ScanLogic,
+ SL11R-IDE 9951SQFP-1.2 K004,
+ US_SC_SCSI, US_PR_BULK, NULL,
+ US_FL_FIX_INQUIRY | US_FL_SL_IDE_BUG ),
+
+/* Reported by Rene Engelhard [EMAIL PROTECTED] and
+Dylan Egan [EMAIL PROTECTED] */
+UNUSUAL_DEV( 0x04ce, 0x0002, 0x0260, 0x0260,
+ ScanLogic,
+ SL11R-IDE unknown HW rev,
+ US_SC_SCSI, US_PR_BULK, NULL,
+ US_FL_SL_IDE_BUG ),
+
/* Most of the following entries were developed with the help of
* Shuttle/SCM directly.
*/
diff -u --recursive linux-2.4.18-pre3/drivers/usb/storage/usb.h
linux/drivers/usb/storage/usb.h
--- linux-2.4.18-pre3/drivers/usb/storage/usb.h Thu Nov 22 10:49:34 2001
+++ linux/drivers/usb/storage/usb.h Thu Jan 10 13:13:36 2002
@@ -101,6 +101,7 @@
#define US_FL_IGNORE_SER 0x0010 /* Ignore the serial number given */
#define US_FL_SCM_MULT_TARG 0x0020 /* supports multiple targets */
#define US_FL_FIX_INQUIRY 0x0040 /* INQUIRY response needs fixing */
+#define US_FL_SL_IDE_BUG 0x0100 /* ScanLogic usb-ide workaround */
#define USB_STOR_STRING_LEN 32
Re: [Cooker] kernel panic debugging
Pascal Cavy [EMAIL PROTECTED] writes: 6. reboot this time the boot stops (in harddrake ?) I absolutly cannot have a complete boot this time until I replugged the mouse and harddrake configures it. would you reproduce when removing completely hardrake ?
Re: USB disk drive problems - was Re: [Cooker] kernel panic debugging
Sounds exactly like what I have been seeing, but only on the second mount (if the unit can be persuaded to mount at all second time around at all !). The first time I mount the device everything works just fine. My old Dell only has 1.1 :-( Owen Todd Lyons wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Owen Savill wrote on Fri, Jan 24, 2003 at 04:17:22PM + : 1) Some USB disk drives will also cause a kernel panic if plugged in during a boot. These tend to be the `in caddy' type rather than the key snip If by any chance another disk drive does actually mount the system will always lock solid usually during a copy or move to the USB disc. I've got an Acom Data 80 GB external USB 2.0 drive. It works fine if I plug it into a USB 1.1 port at lower speeds. If I connect it to a USB 2.0 port, it will mount, but when I start transferring large amounts of data, it causes the computer to hang. This is with the 2.4.19-16mdk (ie a 9.0 install) kernel. The mobo is a Via P4MA. Are you connecting to a USB 2.0 port? Does any of what I have said above sound similar to what you're seeing? Blue skies... Todd - -- MandrakeSoft USA http://www.mandrakesoft.com cat /boot/vmlinuz /dev/dsp #for great justice Mandrake Cooker Devel Version, Kernel 2.4.20-2mdk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+MZt4lp7v05cW2woRAlMpAJ9fn24sVy+guw39pW8SHA4KhOcmCwCeN+wL nuO1se2oGSeZpgBNK5nwBhY= =stI0 -END PGP SIGNATURE-
Re: [Cooker] kernel panic debugging
Le Mercredi 22 Janvier 2003 19:50, Chmouel Boudjnah a écrit : Pascal Cavy [EMAIL PROTECTED] writes: weird, console debugging is possible ? this is the output humm let's try by each case, what if you remove the /etc/modules.conf and reboot does it do alway start ? what do you have in your /etc/modules.conf ? /etc/modules and /etc/modules.conf as I use them now (with the random boot lock) are attached. testing without these module will proceed shortly. I'll also test with the latest kernel. -- Pascal Cavy - VMF __ Running 1 day, 17:15, 8 users, load average: 1.14, 1.31, 1.22 (gcc version 3.2.1 (Mandrake Linux 9.1 3.2.1-2mdk)) Kernel Linux version 2.4.21-0.pre3.1mdkenterprise # /etc/modules: kernel modules to load at boot time. # # This file should contain the names of kernel modules that are # to be loaded at boot time, one per line. Comments begin with # a `#', and everything on the line after them are ignored. #i2c-proc #p4b_smbus #i810_audio #probeall scsi_hostadapter aic7xxx alias eth0 3c59x #alias sound-slot-0 i810_audio # ALSA portion #alias char-major-116 snd #alias snd-card-0 snd-intel8x0 #above snd-intel8x0 snd-pcm-oss # module options should go here # OSS/Free portion #alias char-major-14 soundcore #alias sound-slot-0 snd-card-0 # card #1 #alias sound-service-0-0 snd-mixer-oss #alias sound-service-0-1 snd-seq-oss #alias sound-service-0-3 snd-pcm-oss #alias sound-service-0-8 snd-seq-oss #alias sound-service-0-12 snd-pcm-oss options ov511 bandingfilter=1 lightfreq=50 remove_zeros=1 probeall usb-interface usb-uhci alias sound-slot-0 snd-intel8x0 above snd-intel8x0 snd-pcm-oss options 3c59x hw_checksums=1 flow_ctrl=1 full_duplex=1
Re: [Cooker] kernel panic debugging
Pascal Cavy [EMAIL PROTECTED] writes: Le Mercredi 22 Janvier 2003 19:50, Chmouel Boudjnah a écrit : Pascal Cavy [EMAIL PROTECTED] writes: weird, console debugging is possible ? this is the output humm let's try by each case, what if you remove the /etc/modules.conf and reboot does it do alway start ? what do you have in your /etc/modules.conf ? /etc/modules and /etc/modules.conf as I use them now (with the random boot lock) are attached. testing without these module will proceed shortly. I'll also test with the latest kernel. try to just disable ov511 and reboot...
Re: [Cooker] kernel panic debugging
Le Vendredi 24 Janvier 2003 12:25, Chmouel Boudjnah a écrit : humm let's try by each case, what if you remove the /etc/modules.conf and reboot does it do alway start ? what do you have in your /etc/modules.conf ? /etc/modules and /etc/modules.conf as I use them now (with the random boot lock) are attached. testing without these module will proceed shortly. I'll also test with the latest kernel. try to just disable ov511 and reboot... Well well I've done numerous reboots and tests, and dear people here are the results of the french jury : - latest kernel has the same behaviour (stuck somewhere in rc3.d/) as previous - removing ov511 (from modules.conf and physically) does not cure the problem - more interesting, maybe this manipulation can make you reproduce the behaviour: 1. get at least 2 usb devices connected and recognized at boot (I have intellimouse explorer usb, epson 1200u scanner and ov511 webcam) 2. boot and let harddrake configure all this 3. reboot several times maybe it will stuck 4. if not, just shutdown, remove the usb mouse (or ONE usb device) 5. reboot, let hardddrake complains and timeout and boot continuing 6. reboot this time the boot stops (in harddrake ?) I absolutly cannot have a complete boot this time until I replugged the mouse and harddrake configures it. - belgium 3 poyyyts -- Pascal Cavy - VMF __ Running 1:04, 9 users, load average: 0.01, 0.11, 0.15 (gcc version 3.2.1 (Mandrake Linux 9.1 3.2.1-2mdk)) Kernel Linux version 2.4.21pre3-2mdkenterprise
USB disk drive problems - was Re: [Cooker] kernel panic debugging
Here are some `funnies' that I have found with USB hard disks. Strictly off topic for `Re: [Cooker] kernel panic debugging' but it may help. 1) Some USB disk drives will also cause a kernel panic if plugged in during a boot. These tend to be the `in caddy' type rather than the key fob type. Solution in this case is only to plug them in after the boot has finished. Harddrake doesn't help with this one at all. 2) Take a PC with two USB ports and refer to them as A and B. Plug a USB disk drive (of any type) into A. Mount it, (do some accesses if you wish) and unmount it. Leave the PC for a while (no exact timings available) Plug ANOTHER USB disk into A and attempt to mount it. Error appears typically stating that /dev/sdaX is not a mountable volume Plug same drive into B and attempt to mount it. Success Plug the original drive into A and attempt to mount it. Success Result: Both USB ports are now hard wired to only accept specific hard discs! A reboot is required to use other disck drives. If by any chance another disk drive does actually mount the system will always lock solid usually during a copy or move to the USB disc. 3) There is a kernel patch for the SanDisk USB disk caddies but this does not appear to have been incoporated into the Mandrake kernel. Thanks, Owen Pascal Cavy wrote: Le Vendredi 24 Janvier 2003 12:25, Chmouel Boudjnah a écrit : humm let's try by each case, what if you remove the /etc/modules.conf and reboot does it do alway start ? what do you have in your /etc/modules.conf ? /etc/modules and /etc/modules.conf as I use them now (with the random boot lock) are attached. testing without these module will proceed shortly. I'll also test with the latest kernel. try to just disable ov511 and reboot... Well well I've done numerous reboots and tests, and dear people here are the results of the french jury : - latest kernel has the same behaviour (stuck somewhere in rc3.d/) as previous - removing ov511 (from modules.conf and physically) does not cure the problem - more interesting, maybe this manipulation can make you reproduce the behaviour: 1. get at least 2 usb devices connected and recognized at boot (I have intellimouse explorer usb, epson 1200u scanner and ov511 webcam) 2. boot and let harddrake configure all this 3. reboot several times maybe it will stuck 4. if not, just shutdown, remove the usb mouse (or ONE usb device) 5. reboot, let hardddrake complains and timeout and boot continuing 6. reboot this time the boot stops (in harddrake ?) I absolutly cannot have a complete boot this time until I replugged the mouse and harddrake configures it. - belgium 3 poyyyts
Re: USB disk drive problems - was Re: [Cooker] kernel panic debugging
Chmouel Boudjnah wrote: Owen Savill [EMAIL PROTECTED] writes: 3) There is a kernel patch for the SanDisk USB disk caddies but this does not appear to have been incorporated into the Mandrake kernel. look weird, i don't have such beast to test, but if you point me to it i will maybe integrated. Might be very useful to look at the code for that-- SanDisk can use memory cards as virtual disks. Some IBM Microdisks work on a similar theme driver-wise, as there are both PCMCIA and memory card reader adapters for same. Essentially, SanDisk has what they call\classify as a virtual drive adapter, but it is mostly an IC memory module reader for one of their module lines. Large IC cards with 256 MB and up were made for high-density digital cameras, and it was convenient to have readers that handled them as HDs for older PCs that were USB capable but not USB 2.0 capable. In the US, about 5 variants of this theme exist (IC card as virtual HD, reversing the SWAP idea for portability of data convenience). Take a pocket sized reader, floppy or CD with drivers, and high capacity card to any USB capable box, install drivers, run and carry decent sized chunks of data in tiny package about size of a CD Business card to any box that will take the data and has USB capable O/S. Some of these run at USB 2.0 rates. John. -- Your favorite stores, helpful shopping tools and great gift ideas. Experience the convenience of buying online with Shop@Netscape! http://shopnow.netscape.com/
Re: USB disk drive problems - was Re: [Cooker] kernel panic debugging
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Owen Savill wrote on Fri, Jan 24, 2003 at 04:17:22PM + : 1) Some USB disk drives will also cause a kernel panic if plugged in during a boot. These tend to be the `in caddy' type rather than the key snip If by any chance another disk drive does actually mount the system will always lock solid usually during a copy or move to the USB disc. I've got an Acom Data 80 GB external USB 2.0 drive. It works fine if I plug it into a USB 1.1 port at lower speeds. If I connect it to a USB 2.0 port, it will mount, but when I start transferring large amounts of data, it causes the computer to hang. This is with the 2.4.19-16mdk (ie a 9.0 install) kernel. The mobo is a Via P4MA. Are you connecting to a USB 2.0 port? Does any of what I have said above sound similar to what you're seeing? Blue skies... Todd - -- MandrakeSoft USA http://www.mandrakesoft.com cat /boot/vmlinuz /dev/dsp #for great justice Mandrake Cooker Devel Version, Kernel 2.4.20-2mdk -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+MZt4lp7v05cW2woRAlMpAJ9fn24sVy+guw39pW8SHA4KhOcmCwCeN+wL nuO1se2oGSeZpgBNK5nwBhY= =stI0 -END PGP SIGNATURE-
Re: [Cooker] kernel panic debugging
Le Mardi 21 Janvier 2003 23:03, Pascal a écrit : Le Mardi 21 Janvier 2003 19:32, Chmouel Boudjnah a écrit : Pascal Cavy [EMAIL PROTECTED] writes: Le Mardi 21 Janvier 2003 16:53, Chmouel Boudjnah a écrit : Pascal Cavy [EMAIL PROTECTED] writes: hum, the panic occurs in /etc/rc.sysinit during the mv of the ksyms.? files so I don't have any oops file available. and do you have any others information message or which process ? I've got the console output on a tty now. attached. look like he doen't like the optimisation of hard drive, what is that stuff ? humm could this trigger the kernel panic... I'll try tomorrow to remove this file at the office. I don't have it on my home machine. # cat /etc/sysconfig/harddisks # These options are used to tune the hard drives - # read the hdparm man page for more information # Set this to 1 to enable DMA. This might cause some # data corruption on certain chipset / hard drive # combinations. This is used with the -d option USE_DMA=1 # Multiple sector I/O. a feature of most modern IDE hard drives, # permitting the transfer of multiple sectors per I/O interrupt, # rather than the usual one sector per interrupt. When this feature # is enabled, it typically reduces operating system overhead for disk # I/O by 30-50%. On many systems, it also provides increased data # throughput of anywhere from 5% to 50%. Some drives, however (most # notably the WD Caviar series), seem to run slower with multiple mode # enabled. Under rare circumstances, such failures can result in # massive filesystem corruption. USE WITH CAUTION AND BACKUP. # This is the sector count for multiple sector I/O - the -m option # MULTIPLE_IO=16 # (E)IDE 32-bit I/O support (to interface card) # # EIDE_32BIT=3 # Enable drive read-lookahead # # LOOKAHEAD=1 # Add extra parameters here if wanted # On reasonably new hardware, you may want to try -X66, -X67 or -X68 # Other flags you might want to experiment with are -u1, -a and -m # See the hdparm manpage (man hdparm) for details and more options. # EXTRA_PARAMS= removing this script (harddisks) from /etc/sysinit solved the kernel panic problem. However, on my 2 machines (same motherboard and proc) I have to reboot sometimes 2 or 3 times for the boot to complete. It stops somewhere at random places after setting keytable (time dependent problem ?) -- Pascal Cavy - VMF __ Running 1:31, 9 users, load average: 0.24, 0.20, 0.16 (gcc version 3.2.1 (Mandrake Linux 9.1 3.2.1-2mdk)) Kernel Linux version 2.4.21-0.pre3.1mdkenterprise
Re: [Cooker] kernel panic debugging
Pascal Cavy [EMAIL PROTECTED] writes: However, on my 2 machines (same motherboard and proc) I have to reboot sometimes 2 or 3 times for the boot to complete. It stops somewhere at random places after setting keytable (time dependent problem ?) what do you meant stop, freeze ? oops ? or whatever ? can you do a serial on this again and spy /var/log/message Cheers, Chmouel.
Re: [Cooker] kernel panic debugging
Le Mercredi 22 Janvier 2003 15:58, Chmouel Boudjnah a écrit : what do you meant stop, freeze ? oops ? or whatever ? can you do a serial on this again and spy /var/log/message Cheers, Chmouel. ho sorry, I mean just a wait state : - Echo working on console - no hdisk activity - keyboard numlock light working - kernel sysrq working But getty are not yet launched nor network so I cannot access the system. Only tty console again... If I sysreq + sync then sysreq + reboot the nex boot will proceed without problems. -- Pascal Cavy - VMF __ Running 47 min, 9 users, load average: 0.15, 0.22, 0.33 (gcc version 3.2.1 (Mandrake Linux 9.1 3.2.1-2mdk)) Kernel Linux version 2.4.21-0.pre3.1mdkenterprise
Re: [Cooker] kernel panic debugging
Pascal Cavy [EMAIL PROTECTED] writes: ho sorry, I mean just a wait state : - Echo working on console - no hdisk activity - keyboard numlock light working - kernel sysrq working But getty are not yet launched nor network so I cannot access the system. Only tty console again... If I sysreq + sync then sysreq + reboot the nex boot will proceed without problems. weird, console debugging is possible ?
Re: [Cooker] kernel panic debugging
Le Mercredi 22 Janvier 2003 17:49, Chmouel Boudjnah a écrit : Pascal Cavy [EMAIL PROTECTED] writes: ho sorry, I mean just a wait state : - Echo working on console - no hdisk activity - keyboard numlock light working - kernel sysrq working But getty are not yet launched nor network so I cannot access the system. Only tty console again... If I sysreq + sync then sysreq + reboot the nex boot will proceed without problems. weird, console debugging is possible ? this is the output -- Pascal Cavy - VMF __ Running 8 min, 9 users, load average: 0.47, 1.17, 0.70 (gcc version 3.2.1 (Mandrake Linux 9.1 3.2.1-2mdk)) Kernel Linux version 2.4.21-0.pre3.1mdkenterprise Linux version 2.4.21-0.pre3.1mdkenterprise ([EMAIL PROTECTED]) (gcc version 3.2.1 (Mandrake Linux 9.1 3.2.1-2mdk)) #1 SMP Thu Jan 16 19:00:29 CET 2003 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 4fffc000 (usable) BIOS-e820: 4fffc000 - 4000 (ACPI data) BIOS-e820: 4000 - 5000 (ACPI NVS) BIOS-e820: fec0 - fec01000 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: - 0001 (reserved) 383MB HIGHMEM available. 896MB LOWMEM available. On node 0 totalpages: 327676 zone(0): 4096 pages. zone(1): 225280 pages. zone(2): 98300 pages. ACPI: RSDP (v000 ASUS ) @ 0x000f75e0 ACPI: RSDT (v001 ASUS P4B16944.11825) @ 0x4fffc000 ACPI: FADT (v001 ASUS P4B16944.11825) @ 0x4fffc100 ACPI: BOOT (v001 ASUS P4B16944.11825) @ 0x4fffc040 ACPI: MADT (v001 ASUS P4B16944.11825) @ 0x4fffc080 ACPI: DSDT (v001 ASUS P4B0.04096) @ 0x ACPI: BIOS passes blacklist ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 Unknown CPU [15:1] APIC version 16 ACPI: LAPIC_NMI (acpi_id[0x00] polarity[0x1] trigger[0x1] lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec0] global_irq_base[0x0]) IOAPIC[0]: Assigned apic_id 2 IOAPIC[0]: apic_id 2, version 32, address 0xfec0, IRQ 0-23 ACPI: INT_SRC_OVR (bus[0] irq[0x0] global_irq[0x2] polarity[0x0] trigger[0x1]) ACPI: INT_SRC_OVR (bus[0] irq[0x9] global_irq[0x16] polarity[0x3] trigger[0x3]) Using ACPI (MADT) for SMP configuration information Kernel command line: auto BOOT_IMAGE=2421-1ent ro root=305 devfs=mount hdc=ide-scsi console=ttyS0,9600 ide_setup: hdc=ide-scsi Initializing CPU#0 Detected 1715.319 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 3420.97 BogoMIPS Memory: 1291964k/1310704k available (1556k kernel code, 18352k reserved, 550k data, 160k init, 393200k highmem) Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) Inode cache hash table entries: 131072 (order: 8, 1048576 bytes) Mount-cache hash table entries: 32768 (order: 6, 262144 bytes) Buffer-cache hash table entries: 131072 (order: 7, 524288 bytes) Page-cache hash table entries: 524288 (order: 9, 2097152 bytes) CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 256K CPU: Hyper-Threading is disabled Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX mtrr: v1.40 (20010327) Richard Gooch ([EMAIL PROTECTED]) mtrr: detected mtrr type: Intel CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 256K CPU: Hyper-Threading is disabled Intel machine check reporting enabled on CPU#0. CPU0: Intel(R) Pentium(R) 4 CPU 1.70GHz stepping 02 per-CPU timeslice cutoff: 731.51 usecs. enabled ExtINT on CPU#0 ESR value before enabling vector: ESR value after enabling vector: Error: only one processor found. ENABLING IO-APIC IRQs ..TIMER: vector=0x31 pin1=2 pin2=0 testing the IO APIC... done. Using local APIC timer interrupts. calibrating APIC timer ... . CPU clock speed is 1715.2579 MHz. . host bus clock speed is 100.8974 MHz. cpu: 0, clocks: 1008974, slice: 504487 CPU0T0:1008960,T1:504464,D:9,S:504487,C:1008974 Waiting on wait_init_idle (map = 0x0) All processors have done init_idle ACPI: Subsystem revision 20021212 PCI: PCI BIOS revision 2.10 entry at 0xf11f0, last bus=2 PCI: Using configuration type 1 ACPI-0263: *** Info: GPE Block0 defined as GPE0 to GPE15 ACPI-0263: *** Info: GPE Block1 defined as GPE16 to GPE31 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: System [ACPI] (supports S0 S1 S4 S5) ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11
Re: [Cooker] kernel panic debugging
Pascal Cavy wrote: However, on my 2 machines (same motherboard and proc) I have to reboot sometimes 2 or 3 times for the boot to complete. It stops somewhere at random places after setting keytable (time dependent problem ?) I had this same symptom with the last cooker kernel that supported XFS (that was 2.4.20.2mdk, newest kernels don't have XFS compiled in) as well as filesystem corruption. Didn't report it since I'm not running cooker (just trying out kernels to see if 8.2 and 9.0 problems have been solved). Bye -- Luca Olivetti Note.- This message reached you today, it may not tomorrow if you are using MAPS or other RBL. They arbitrarily IP addresses not related in any way to spam, disrupting Internet connectivity. See http://slashdot.org/article.pl?sid=01/05/21/1944247 and http://theory.whirlycott.com/~phil/antispam/rbl-bad/rbl-bad.html msg87470/pgp0.pgp Description: PGP signature
Re: [Cooker] kernel panic debugging
Pascal Cavy [EMAIL PROTECTED] writes: weird, console debugging is possible ? this is the output humm let's try by each case, what if you remove the /etc/modules.conf and reboot does it do alway start ? what do you have in your /etc/modules.conf ?
Re: [Cooker] kernel panic debugging
I am experiencing a kernel panic with latest kernel-enterprise-2.4.21.0.pre3.1mdk-1-1mdk What kind of hardware first ?
Re: [Cooker] kernel panic debugging
Le Mardi 21 Janvier 2003 15:23, Chmouel Boudjnah a écrit : I am experiencing a kernel panic with latest kernel-enterprise-2.4.21.0.pre3.1mdk-1-1mdk What kind of hardware first ? Asustek p4b - pentium 4 1.7Ghz - sdram 1.5Gb # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 1 model name : Intel(R) Pentium(R) 4 CPU 1.70GHz stepping: 2 cpu MHz : 1715.326 cache size : 256 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm bogomips: 3420.97 # lspcidrake unknown : Intel Corporation|82845 845 (Brookdale) Chipset Host Bridge unknown : Intel Corporation|82845 845 (Brookdale) Chipset AGP Bridge i810_rng: Intel Corporation|82820 815e (Camino 2) Chipset PCI i810-tco: Intel Corporation|82820 815e (Camino 2) Chipset ISA Bridge (ICH2) unknown : Intel Corporation|82820 815e (Camino 2) Chipset IDE U100 usb-uhci: Intel Corporation|82820 815e (Camino 2) Chipset USB (Hub A) usb-uhci: Intel Corporation|82820 815e (Camino 2) Chipset USB (Hub B) i810_audio : Intel Corporation|ICH2 810 Chipset AC'97 Audio Controller Card:Matrox Millennium G550 DualHead: Matrox|MGA G550 AGP aic7xxx : Adaptec|AIC-7861 3c59x : 3Com Corporation|3c905C-TX [Fast Etherlink] unknown : Unknown|USB UHCI Root Hub [Hub|Root Hub] unknown : Unknown|USB UHCI Root Hub [Hub|Root Hub] unknown : Atmel Corp.|4-port Hub [Hub|Root Hub] ov511 : OmniVision Technologies, Inc.|OV511 WebCam [] unknown : unknown (045e/001c//) [Hub|Root Hub] Mouse:USB|Microsoft Explorer: Microsoft Corp.|IntelliMouse Explorer [Human Interface Devices|Boot Interface Subclass|Mouse] -- Pascal Cavy - VMF __ Running 1 day, 21 min, 5 users, load average: 0.31, 0.13, 0.20 (gcc version 3.2 (Mandrake Linux 9.1 3.2-4mdk)) Kernel Linux version 2.4.20-2mdkenterprise
Re: [Cooker] kernel panic debugging
Le Mardi 21 Janvier 2003 16:16, Pascal Cavy a écrit : Le Mardi 21 Janvier 2003 15:23, Chmouel Boudjnah a écrit : I am experiencing a kernel panic with latest kernel-enterprise-2.4.21.0.pre3.1mdk-1-1mdk What kind of hardware first ? Asustek p4b - pentium 4 1.7Ghz - sdram 1.5Gb # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 1 model name : Intel(R) Pentium(R) 4 CPU 1.70GHz stepping: 2 cpu MHz : 1715.326 cache size : 256 KB fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm bogomips: 3420.97 # lspcidrake unknown : Intel Corporation|82845 845 (Brookdale) Chipset Host Bridge unknown : Intel Corporation|82845 845 (Brookdale) Chipset AGP Bridge i810_rng: Intel Corporation|82820 815e (Camino 2) Chipset PCI i810-tco: Intel Corporation|82820 815e (Camino 2) Chipset ISA Bridge (ICH2) unknown : Intel Corporation|82820 815e (Camino 2) Chipset IDE U100 usb-uhci: Intel Corporation|82820 815e (Camino 2) Chipset USB (Hub A) usb-uhci: Intel Corporation|82820 815e (Camino 2) Chipset USB (Hub B) i810_audio : Intel Corporation|ICH2 810 Chipset AC'97 Audio Controller Card:Matrox Millennium G550 DualHead: Matrox|MGA G550 AGP aic7xxx : Adaptec|AIC-7861 3c59x : 3Com Corporation|3c905C-TX [Fast Etherlink] unknown : Unknown|USB UHCI Root Hub [Hub|Root Hub] unknown : Unknown|USB UHCI Root Hub [Hub|Root Hub] unknown : Atmel Corp.|4-port Hub [Hub|Root Hub] ov511 : OmniVision Technologies, Inc.|OV511 WebCam [] unknown : unknown (045e/001c//) [Hub|Root Hub] Mouse:USB|Microsoft Explorer: Microsoft Corp.|IntelliMouse Explorer [Human Interface Devices|Boot Interface Subclass|Mouse] I have another machine at home running this kernel without any problems. If I remember well, the kernel panics on an ext2 fs error. But I checked all FS successfully in mdk rescue mode and the kernel 2.4.20-2mdkenterprise runs without problems on this machine (I'm writing this email from it). -- Pascal Cavy - VMF __ Running 1 day, 28 min, 5 users, load average: 0.15, 0.12, 0.16 (gcc version 3.2 (Mandrake Linux 9.1 3.2-4mdk)) Kernel Linux version 2.4.20-2mdkenterprise
Re: [Cooker] kernel panic debugging
Pascal Cavy [EMAIL PROTECTED] writes: Le Mardi 21 Janvier 2003 15:23, Chmouel Boudjnah a écrit : I am experiencing a kernel panic with latest kernel-enterprise-2.4.21.0.pre3.1mdk-1-1mdk What kind of hardware first ? Asustek p4b - pentium 4 1.7Ghz - sdram 1.5Gb pretty much standard, after the oops are you able to pass that via the ksymoops util ? (see: /usr/src/linux/Documentation/oops-tracing.txt)
Re: [Cooker] kernel panic debugging
Pascal Cavy [EMAIL PROTECTED] writes: I have another machine at home running this kernel without any problems. If I remember well, the kernel panics on an ext2 fs error. But I checked all FS successfully in mdk rescue mode and the kernel 2.4.20-2mdkenterprise runs without problems on this machine (I'm writing this email from it). only with ext2, can you reproduce with a other file system ?
Re: [Cooker] kernel panic debugging
Le Mardi 21 Janvier 2003 16:22, Chmouel Boudjnah a écrit : Pascal Cavy [EMAIL PROTECTED] writes: Le Mardi 21 Janvier 2003 15:23, Chmouel Boudjnah a écrit : I am experiencing a kernel panic with latest kernel-enterprise-2.4.21.0.pre3.1mdk-1-1mdk What kind of hardware first ? Asustek p4b - pentium 4 1.7Ghz - sdram 1.5Gb pretty much standard, after the oops are you able to pass that via the ksymoops util ? (see: /usr/src/linux/Documentation/oops-tracing.txt) hum, the panic occurs in /etc/rc.sysinit during the mv of the ksyms.? files so I don't have any oops file available. are mdk kernels patched like described in : Patch the kernel with one of the crash dump patches. These save data to a floppy disk or video rom or a swap partition. None of these are standard kernel patches so you have to find and apply them yourself. Search kernel archives for kmsgdump, lkcd and oops+smram. if not I'll try the serial console then on another mdk machine to capture the output. -- Pascal Cavy - VMF __ Running 1 day, 49 min, 5 users, load average: 0.05, 0.40, 0.43 (gcc version 3.2 (Mandrake Linux 9.1 3.2-4mdk)) Kernel Linux version 2.4.20-2mdkenterprise
Re: [Cooker] kernel panic debugging
Pascal Cavy [EMAIL PROTECTED] writes: hum, the panic occurs in /etc/rc.sysinit during the mv of the ksyms.? files so I don't have any oops file available. and do you have any others information message or which process ?
Re: [Cooker] kernel panic debugging
Le Mardi 21 Janvier 2003 16:53, Chmouel Boudjnah a écrit : Pascal Cavy [EMAIL PROTECTED] writes: hum, the panic occurs in /etc/rc.sysinit during the mv of the ksyms.? files so I don't have any oops file available. and do you have any others information message or which process ? I've got the console output on a tty now. attached. -- Pascal Cavy - VMF __ Running 14 min, 8 users, load average: 0.26, 0.43, 0.38 (gcc version 3.2 (Mandrake Linux 9.1 3.2-4mdk)) Kernel Linux version 2.4.20-2mdkenterprise Linux version 2.4.21-0.pre3.1mdkenterprise ([EMAIL PROTECTED]) (gcc version 3.2.1 (Mandrake Linux 9.1 3.2.1-2mdk)) #1 SMP Thu Jan 16 19:00:29 CET 2003 BIOS-provided physical RAM map: BIOS-e820: - 0009fc00 (usable) BIOS-e820: 0009fc00 - 000a (reserved) BIOS-e820: 000f - 0010 (reserved) BIOS-e820: 0010 - 4fffc000 (usable) BIOS-e820: 4fffc000 - 4000 (ACPI data) BIOS-e820: 4000 - 5000 (ACPI NVS) BIOS-e820: fec0 - fec01000 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: - 0001 (reserved) 383MB HIGHMEM available. 896MB LOWMEM available. On node 0 totalpages: 327676 zone(0): 4096 pages. zone(1): 225280 pages. zone(2): 98300 pages. ACPI: RSDP (v000 ASUS ) @ 0x000f75e0 ACPI: RSDT (v001 ASUS P4B16944.11825) @ 0x4fffc000 ACPI: FADT (v001 ASUS P4B16944.11825) @ 0x4fffc100 ACPI: BOOT (v001 ASUS P4B16944.11825) @ 0x4fffc040 ACPI: MADT (v001 ASUS P4B16944.11825) @ 0x4fffc080 ACPI: DSDT (v001 ASUS P4B0.04096) @ 0x ACPI: BIOS passes blacklist ACPI: Local APIC address 0xfee0 ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) Processor #0 Unknown CPU [15:1] APIC version 16 ACPI: LAPIC_NMI (acpi_id[0x00] polarity[0x1] trigger[0x1] lint[0x1]) ACPI: IOAPIC (id[0x02] address[0xfec0] global_irq_base[0x0]) IOAPIC[0]: Assigned apic_id 2 IOAPIC[0]: apic_id 2, version 32, address 0xfec0, IRQ 0-23 ACPI: INT_SRC_OVR (bus[0] irq[0x0] global_irq[0x2] polarity[0x0] trigger[0x1]) ACPI: INT_SRC_OVR (bus[0] irq[0x9] global_irq[0x16] polarity[0x3] trigger[0x3]) Using ACPI (MADT) for SMP configuration information Kernel command line: BOOT_IMAGE=2421-1ent ro root=305 devfs=mount hdc=ide-scsi console=ttyS0,9600 ide_setup: hdc=ide-scsi Initializing CPU#0 Detected 1715.302 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 3420.97 BogoMIPS Memory: 1291964k/1310704k available (1556k kernel code, 18352k reserved, 550k data, 160k init, 393200k highmem) Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes) Inode cache hash table entries: 131072 (order: 8, 1048576 bytes) Mount-cache hash table entries: 32768 (order: 6, 262144 bytes) Buffer-cache hash table entries: 131072 (order: 7, 524288 bytes) Page-cache hash table entries: 524288 (order: 9, 2097152 bytes) CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 256K CPU: Hyper-Threading is disabled Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. Enabling fast FPU save and restore... done. Enabling unmasked SIMD FPU exception support... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX mtrr: v1.40 (20010327) Richard Gooch ([EMAIL PROTECTED]) mtrr: detected mtrr type: Intel CPU: Trace cache: 12K uops, L1 D cache: 8K CPU: L2 cache: 256K CPU: Hyper-Threading is disabled Intel machine check reporting enabled on CPU#0. CPU0: Intel(R) Pentium(R) 4 CPU 1.70GHz stepping 02 per-CPU timeslice cutoff: 731.51 usecs. enabled ExtINT on CPU#0 ESR value before enabling vector: ESR value after enabling vector: Error: only one processor found. ENABLING IO-APIC IRQs ..TIMER: vector=0x31 pin1=2 pin2=0 testing the IO APIC... done. Using local APIC timer interrupts. calibrating APIC timer ... . CPU clock speed is 1715.3931 MHz. . host bus clock speed is 100.9052 MHz. cpu: 0, clocks: 1009052, slice: 504526 CPU0T0:1009040,T1:504512,D:2,S:504526,C:1009052 Waiting on wait_init_idle (map = 0x0) All processors have done init_idle ACPI: Subsystem revision 20021212 PCI: PCI BIOS revision 2.10 entry at 0xf11f0, last bus=2 PCI: Using configuration type 1 ACPI-0263: *** Info: GPE Block0 defined as GPE0 to GPE15 ACPI-0263: *** Info: GPE Block1 defined as GPE16 to GPE31 ACPI: Interpreter enabled ACPI: Using IOAPIC for interrupt routing ACPI: System [ACPI] (supports S0 S1 S4 S5) ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15) ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 9 *10 11 12 14 15) ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 *5 6 7 9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 *9 10 11 12 14 15) ACPI: PCI Interrupt Link [LNKE] (IRQs 3
Re: [Cooker] kernel panic debugging
Pascal Cavy [EMAIL PROTECTED] writes: Le Mardi 21 Janvier 2003 16:53, Chmouel Boudjnah a écrit : Pascal Cavy [EMAIL PROTECTED] writes: hum, the panic occurs in /etc/rc.sysinit during the mv of the ksyms.? files so I don't have any oops file available. and do you have any others information message or which process ? I've got the console output on a tty now. attached. look like he doen't like the optimisation of hard drive, what is that stuff ?
Re: [Cooker] kernel panic debugging
Le Mardi 21 Janvier 2003 19:32, Chmouel Boudjnah a écrit : Pascal Cavy [EMAIL PROTECTED] writes: Le Mardi 21 Janvier 2003 16:53, Chmouel Boudjnah a écrit : Pascal Cavy [EMAIL PROTECTED] writes: hum, the panic occurs in /etc/rc.sysinit during the mv of the ksyms.? files so I don't have any oops file available. and do you have any others information message or which process ? I've got the console output on a tty now. attached. look like he doen't like the optimisation of hard drive, what is that stuff ? humm could this trigger the kernel panic... I'll try tomorrow to remove this file at the office. I don't have it on my home machine. # cat /etc/sysconfig/harddisks # These options are used to tune the hard drives - # read the hdparm man page for more information # Set this to 1 to enable DMA. This might cause some # data corruption on certain chipset / hard drive # combinations. This is used with the -d option USE_DMA=1 # Multiple sector I/O. a feature of most modern IDE hard drives, # permitting the transfer of multiple sectors per I/O interrupt, # rather than the usual one sector per interrupt. When this feature # is enabled, it typically reduces operating system overhead for disk # I/O by 30-50%. On many systems, it also provides increased data # throughput of anywhere from 5% to 50%. Some drives, however (most # notably the WD Caviar series), seem to run slower with multiple mode # enabled. Under rare circumstances, such failures can result in # massive filesystem corruption. USE WITH CAUTION AND BACKUP. # This is the sector count for multiple sector I/O - the -m option # MULTIPLE_IO=16 # (E)IDE 32-bit I/O support (to interface card) # # EIDE_32BIT=3 # Enable drive read-lookahead # # LOOKAHEAD=1 # Add extra parameters here if wanted # On reasonably new hardware, you may want to try -X66, -X67 or -X68 # Other flags you might want to experiment with are -u1, -a and -m # See the hdparm manpage (man hdparm) for details and more options. # EXTRA_PARAMS=
