* Re: rotation.
From: Antonino Daplas @ 2003-01-08 16:56 UTC (permalink / raw)
To: James Simmons
Cc: Linux Fbdev development list, Linux Kernel Mailing List,
Geert Uytterhoeven
In-Reply-To: <Pine.LNX.4.44.0301072240530.17129-100000@phoenix.infradead.org>
On Wed, 2003-01-08 at 06:44, James Simmons wrote:
>
> I'm about to implement rotation which is needed for devices like the ipaq.
> The question is do we flip the xres and yres values depending on the
> rotation or do we just alter the data that will be drawn to make the
> screen appear to rotate. How does hardware rotate view the x and y axis?
> Are they rotated or does just the data get rotated?
>
If the graphics card has hardware support for rotation, then there is
nothing to be done. It's the job of the driver if it wants to rotate
the display or not. This is similar to video overlay mirroring. What
the user app sees is the framebuffer in "normal" orientation, but what
gets displayed is mirrored.
However, as Geert mentioned, if you want to support rotation
generically, then you have to do it in the fbcon level. The driver need
not know if the display is rotated or not. All it needs to do is fill a
region with color, color expand a bitmap and move blocks of data, and
optionally 'pan' the window. Fbcon will pass the correct (ie, oriented)
information for the driver.
This will not be too processor intensive as long as some data is
prepared beforehand, like a rotated fontdata.
The main difficulty with this approach is how do you tell the console to
rotate the display? We cannot use fbset because the changes will not be
visible to fbcon.
I submitted a patch before (see fbdev archives for "Console Rotation"
thread) that rotates the console this way. I had vga16fb, vesafb, and
i810fb rotate the display without any driver code change. Display
panning was also supported.
However, because we use mmap to expose the framebuffer memory, we will
not be able to completely support rotation for user applications. They
have to do it on their own.
Tony
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
^ permalink raw reply
* RE: Quantum disk firmware update
From: Cress, Andrew R @ 2003-01-08 17:08 UTC (permalink / raw)
To: 'Shanker Balan'
Cc: Linux-SCSI,
'scsirastools-developers@lists.sourceforge.net.'
Shanu,
The sense key message shows "Illegal Request" for the Write Buffer command.
This could be one of several things:
1) The device cannot handle SCSI commands this large (377k).
or
2) The command was truncated or malformed so that it appeared incomplete.
or
3) Some devices return this sense code if the model number in the image
does not match the device model number.
For (1) it would be an issue to take back to Quantum, asking how does this
disk device expect to download firmware? Most disks use one big buffer like
this, but some require a fragmented, iterative download algorithm. I've
downloaded firmware images as large as 600k with this tool, so it is within
a normal range.
For (2), it could be a software bug, but the fact that the DOS Quantum tool
provided gets the same error would weigh against this. It could be a
cabling/termination problem, or it could be an issue with the adapter
handling large SCSI commands. Which SCSI adapter was involved?
For (3), this seems like the most likely case. You can also do a "strings"
on the image file to see if there is a model string there that matches. You
can check with Quantum/Maxtor to verify the image. The sgdskfl should also
explictly check this, but I just noticed that Quantum wasn't in my list of
vendors that support this. This will be changed in the next cut.
RE "servo image":
Some disk devices have the capability to download a servo image as well as a
firmware image.
The servo controls the mechanical/physical operation of the disk (comparable
to BIOS on a PC), while the firmware handles higher level logic, including
the SCSI protocol.
-----Original Message-----
From: Shanker Balan [mailto:shanu@exocore.com]
Sent: Wednesday, January 08, 2003 3:15 AM
To: Linux-SCSI
Subject: Re: Seagate Cheetah: Firmware, Bugs, Compatibility?
[...]
I got a similar sense error while trying to flash using the Quantum supplied
"DL_scsi.exe" under DOS.
Andrew, any idea what might be the problem here? Also whats a "Servo
image"?
Here is paste from "sgdskfl" run:
Log file /var/log/sgdskfl.log is open, debug=0
Num Name [bus:ch:id:lun] Type Vendor Device_Model FW__ Serial#_
Servo___
0 /dev/sg0 [0:0:0:0] Disk QUANTUM ATLAS10K3_18_SCA 020W 34220894
1 /dev/sg1 [0:0:1:0] Disk QUANTUM ATLAS10K3_73_SCA 020W 34820965
2 /dev/sg2 [0:0:2:0] Disk QUANTUM ATLAS10K3_73_SCA 020W 34820635
Enter Selection ('d' to download, 'q' to quit) : d
Device Num (0 to 2) : 2
Selected 2: [0:2] QUANTUM ATLAS10K3_73_SCA020W34820635
Reading image file atlas10k.lod, size = 377167
No servo image
Device [2] is ready for download
Starting download process for 1 disk.
Downloading Firmware image to disk 2 Wed Jan 8 13:40:52 2003
Current sg_cmd_done_bh00:00: sense key Illegal Request
write_buffer: Check Condition Driver_status=0x08 (DRIVER_SENSE,SUGGEST_OK)
sense error, key=05 asc=26 ascq=80 Illegal Request
Info valid=0, Current
[2] Error -2 in writing buffer
Press ENTER to continue
-- Shanu
http://shankerbalan.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply
* Re: [linux-lvm] problem
From: Alasdair G Kergon @ 2003-01-08 17:09 UTC (permalink / raw)
To: linux-lvm
In-Reply-To: <20030108225455.H28021@uk.sistina.com>
Procedure to follow:
vgcfgbackup -P -f /tmp/vgbackup rootvg
Edit the backup file as follows:
Add "WRITE" to the status line and remove "PARTIAL"
e.g.
status = ["RESIZEABLE", "PARTIAL", "READ"]
becomes
status = ["RESIZEABLE", "READ", "WRITE"]
Remove the whole PV section for your "unknown device"
- referenced as "pv1" in this example.
pv1 {
id = "TBCgjx-ne5X-4fHP-aHqe-dKJR-Vwnb-kjDhWQ"
device = "unknown device" # Hint only
status = ["ALLOCATABLE"]
pe_start = 128
pe_count = 5 # 20 Megabytes
}
Remove the whole LV section for any LVs that refer to the pv you
removed above (pv1 here referenced inside "stripes") e.g.
tmp {
id = "4eTLYv-PTDr-FXvv-58Xk-Q4Th-p8yi-GeKCHr"
status = ["READ", "WRITE", "VISIBLE"]
segment_count = 1
segment1 {
start_extent = 0
extent_count = 3 # 12 Megabytes
type = "striped"
stripe_count = 1 # linear
stripes = [
"pv1", 0
]
}
}
Write the metadata back to disk:
vgcfgrestore -f /tmp/vgbackup rootvg
Alasdair
--
agk@uk.sistina.com
^ permalink raw reply
* Re: Making this list more readable
From: Athan @ 2003-01-08 17:09 UTC (permalink / raw)
To: netfilter
In-Reply-To: <OF86C0DB41.716D3A1B-ON88256CA8.005CC9AB-88256CA8.005D516A@deepwoods.com>
[-- Attachment #1: Type: text/plain, Size: 911 bytes --]
On Wed, Jan 08, 2003 at 08:59:16AM -0800, Carol Anne Ogdin wrote:
> Is there any way to change the listserv so it doesn't convert control
> characters (e.g., tabs, quotes and spaces at ends of lines) to '=xx'
> form of hex characters. It's hard to read. (I read the digest, so
> perhaps the problem lies there, and not in the main listserv?)
> Does your listserv software have a conversion table you can set that
> will make things more readable?
I don't see this, and I'm getting the list direct. The =XX thing is
"Quoted Printable" encoding. Probably an option on the listserv to turn
it on/off for the digest.
-Ath
--
- Athanasius = Athanasius(at)miggy.org / http://www.miggy.org/
Finger athan(at)fysh.org for PGP key
"And it's me who is my enemy. Me who beats me up.
Me who makes the monsters. Me who strips my confidence." Paula Cole - ME
[-- Attachment #2: Type: application/pgp-signature, Size: 240 bytes --]
^ permalink raw reply
* [2.5.54][PATCH] SB16 convertation to new PnP layer.
From: Ruslan U. Zakirov @ 2003-01-08 17:20 UTC (permalink / raw)
To: linux-kernel; +Cc: ambx1
Hello Adam and All.
Here is patch to sb16.c that makes it posible to compile and use this
driver under 2.5.54-vanilla.
It working for me as module and built in kernel, but it's need testing.
Ruslan.
--- sound/isa/sb/sb16.c~ 2003-01-04 17:32:00.000000000 +0300
+++ sound/isa/sb/sb16.c 2003-01-09 19:25:50.000000000 +0300
@@ -23,11 +23,7 @@
#include <asm/dma.h>
#include <linux/init.h>
#include <linux/slab.h>
-#ifndef LINUX_ISAPNP_H
-#include <linux/isapnp.h>
-#define isapnp_card pci_bus
-#define isapnp_dev pci_dev
-#endif
+#include <linux/pnp.h>
#include <sound/core.h>
#include <sound/sb.h>
#include <sound/sb16_csp.h>
@@ -77,7 +73,7 @@
static int index[SNDRV_CARDS] = SNDRV_DEFAULT_IDX; /* Index 0-MAX */
static char *id[SNDRV_CARDS] = SNDRV_DEFAULT_STR; /* ID for this card */
static int enable[SNDRV_CARDS] = SNDRV_DEFAULT_ENABLE_ISAPNP; /* Enable this card */
-#ifdef __ISAPNP__
+#ifdef CONFIG_PNP
static int isapnp[SNDRV_CARDS] = {[0 ... (SNDRV_CARDS - 1)] = 1};
#endif
static long port[SNDRV_CARDS] = SNDRV_DEFAULT_PORT; /* 0x220,0x240,0x260,0x280 */
@@ -106,7 +102,7 @@
MODULE_PARM(enable, "1-" __MODULE_STRING(SNDRV_CARDS) "i");
MODULE_PARM_DESC(enable, "Enable SoundBlaster 16 soundcard.");
MODULE_PARM_SYNTAX(enable, SNDRV_ENABLE_DESC);
-#ifdef __ISAPNP__
+#ifdef CONFIG_PNP
MODULE_PARM(isapnp, "1-" __MODULE_STRING(SNDRV_CARDS) "i");
MODULE_PARM_DESC(isapnp, "ISA PnP detection for specified soundcard.");
MODULE_PARM_SYNTAX(isapnp, SNDRV_ISAPNP_DESC);
@@ -150,161 +146,130 @@
struct snd_sb16 {
struct resource *fm_res; /* used to block FM i/o region for legacy cards */
-#ifdef __ISAPNP__
- struct isapnp_dev *dev;
+#ifdef CONFIG_PNP
+ struct pnp_dev *dev;
#ifdef SNDRV_SBAWE_EMU8000
- struct isapnp_dev *devwt;
+ struct pnp_dev *devwt;
#endif
#endif
};
static snd_card_t *snd_sb16_cards[SNDRV_CARDS] = SNDRV_DEFAULT_PTR;
-#ifdef __ISAPNP__
-
-static struct isapnp_card *snd_sb16_isapnp_cards[SNDRV_CARDS] = SNDRV_DEFAULT_PTR;
-static const struct isapnp_card_id *snd_sb16_isapnp_id[SNDRV_CARDS] = SNDRV_DEFAULT_PTR;
+#ifdef CONFIG_PNP
-#define ISAPNP_SB16(_va, _vb, _vc, _device, _audio) \
- { \
- ISAPNP_CARD_ID(_va, _vb, _vc, _device), \
- devs : { ISAPNP_DEVICE_ID(_va, _vb, _vc, _audio), } \
- }
-#define ISAPNP_SBAWE(_va, _vb, _vc, _device, _audio, _awe) \
- { \
- ISAPNP_CARD_ID(_va, _vb, _vc, _device), \
- devs : { ISAPNP_DEVICE_ID(_va, _vb, _vc, _audio), \
- ISAPNP_DEVICE_ID(_va, _vb, _vc, _awe), } \
- }
+static struct pnp_card *snd_sb16_isapnp_cards[SNDRV_CARDS] = SNDRV_DEFAULT_PTR;
+static const struct pnp_card_id *snd_sb16_isapnp_id[SNDRV_CARDS] = SNDRV_DEFAULT_PTR;
-static struct isapnp_card_id snd_sb16_pnpids[] __devinitdata = {
+static struct pnp_card_id snd_sb16_pnpids[] = {
#ifndef SNDRV_SBAWE
/* Sound Blaster 16 PnP */
- ISAPNP_SB16('C','T','L',0x0024,0x0031),
+ {.id = "CTL0024", .driver_data=0, devs: { {.id="CTL0031"}, }},
/* Sound Blaster 16 PnP */
- ISAPNP_SB16('C','T','L',0x0025,0x0031),
+ {.id = "CTL0025", .driver_data=0, devs: { {.id="CTL0031"}, }},
/* Sound Blaster 16 PnP */
- ISAPNP_SB16('C','T','L',0x0026,0x0031),
+ {.id = "CTL0026", .driver_data=0, devs: { {.id="CTL0031"}, }},
/* Sound Blaster 16 PnP */
- ISAPNP_SB16('C','T','L',0x0027,0x0031),
+ {.id = "CTL0027", .driver_data=0, devs: { {.id="CTL0031"}, }},
/* Sound Blaster 16 PnP */
- ISAPNP_SB16('C','T','L',0x0028,0x0031),
+ {.id = "CTL0028", .driver_data=0, devs: { {.id="CTL0031"}, }},
/* Sound Blaster 16 PnP */
- ISAPNP_SB16('C','T','L',0x0029,0x0031),
+ {.id = "CTL0029", .driver_data=0, devs: { {.id="CTL0031"}, }},
/* Sound Blaster 16 PnP */
- ISAPNP_SB16('C','T','L',0x002a,0x0031),
+ {.id = "CTL002a", .driver_data=0, devs: { {.id="CTL0031"}, }},
/* Sound Blaster 16 PnP */
/* Note: This card has also a CTL0051:StereoEnhance device!!! */
- ISAPNP_SB16('C','T','L',0x002b,0x0031),
+ {.id = "CTL002b", .driver_data=0, devs: { {.id="CTL0031"}, }},
/* Sound Blaster 16 PnP */
- ISAPNP_SB16('C','T','L',0x002c,0x0031),
+ {.id = "CTL002c", .driver_data=0, devs: { {.id="CTL0031"}, }},
/* Sound Blaster Vibra16S */
- ISAPNP_SB16('C','T','L',0x0051,0x0001),
+ {.id = "CTL0051", .driver_data=0, devs: { {.id="CTL0001"}, }},
/* Sound Blaster Vibra16C */
- ISAPNP_SB16('C','T','L',0x0070,0x0001),
+ {.id = "CTL0070", .driver_data=0, devs: { {.id="CTL0001"}, }},
/* Sound Blaster Vibra16CL - added by ctm@ardi.com */
- ISAPNP_SB16('C','T','L',0x0080,0x0041),
+ {.id = "CTL0080", .driver_data=0, devs: { {.id="CTL0041"}, }},
/* Sound Blaster Vibra16X */
- ISAPNP_SB16('C','T','L',0x00f0,0x0043),
+ {.id = "CTL00f0", .driver_data=0, devs: { {.id="CTL0043"}, }}
#else /* SNDRV_SBAWE defined */
/* Sound Blaster AWE 32 PnP */
- ISAPNP_SBAWE('C','T','L',0x0035,0x0031,0x0021),
+ {.id = "CTL0035", .driver_data=0, devs: { {.id="CTL0031"}, {.id="CTL0021"}, }},
/* Sound Blaster AWE 32 PnP */
- ISAPNP_SBAWE('C','T','L',0x0039,0x0031,0x0021),
+ {.id = "CTL0039", .driver_data=0, devs: { {.id="CTL0031"}, {.id="CTL0021"}, }},
/* Sound Blaster AWE 32 PnP */
- ISAPNP_SBAWE('C','T','L',0x0042,0x0031,0x0021),
+ {.id = "CTL0042", .driver_data=0, devs: { {.id="CTL0031"}, {.id="CTL0021"}, }},
/* Sound Blaster AWE 32 PnP */
- ISAPNP_SBAWE('C','T','L',0x0043,0x0031,0x0021),
+ {.id = "CTL0043", .driver_data=0, devs: { {.id="CTL0031"}, {.id="CTL0021"}, }},
/* Sound Blaster AWE 32 PnP */
/* Note: This card has also a CTL0051:StereoEnhance device!!! */
- ISAPNP_SBAWE('C','T','L',0x0044,0x0031,0x0021),
+ {.id = "CTL0044", .driver_data=0, devs: { {.id="CTL0031"}, {.id="CTL0021"}, }},
/* Sound Blaster AWE 32 PnP */
/* Note: This card has also a CTL0051:StereoEnhance device!!! */
- ISAPNP_SBAWE('C','T','L',0x0045,0x0031,0x0021),
+ {.id = "CTL0045", .driver_data=0, devs: { {.id="CTL0031"}, {.id="CTL0021"}, }},
/* Sound Blaster AWE 32 PnP */
- ISAPNP_SBAWE('C','T','L',0x0046,0x0031,0x0021),
+ {.id = "CTL0046", .driver_data=0, devs: { {.id="CTL0031"}, {.id="CTL0021"}, }},
/* Sound Blaster AWE 32 PnP */
- ISAPNP_SBAWE('C','T','L',0x0047,0x0031,0x0021),
+ {.id = "CTL0047", .driver_data=0, devs: { {.id="CTL0031"}, {.id="CTL0021"}, }},
/* Sound Blaster AWE 32 PnP */
- ISAPNP_SBAWE('C','T','L',0x0048,0x0031,0x0021),
+ {.id = "CTL0048", .driver_data=0, devs: { {.id="CTL0031"}, {.id="CTL0021"}, }},
/* Sound Blaster AWE 32 PnP */
- ISAPNP_SBAWE('C','T','L',0x0054,0x0031,0x0021),
+ {.id = "CTL0054", .driver_data=0, devs: { {.id="CTL0031"}, {.id="CTL0021"}, }},
/* Sound Blaster AWE 32 PnP */
- ISAPNP_SBAWE('C','T','L',0x009a,0x0041,0x0021),
+ {.id = "CTL009a", .driver_data=0, devs: { {.id="CTL0041"}, {.id="CTL0021"}, }},
/* Sound Blaster AWE 32 PnP */
- ISAPNP_SBAWE('C','T','L',0x009c,0x0041,0x0021),
+ {.id = "CTL009c", .driver_data=0, devs: { {.id="CTL0041"}, {.id="CTL0021"}, }},
/* Sound Blaster 32 PnP */
- ISAPNP_SBAWE('C','T','L',0x009f,0x0041,0x0021),
+ {.id = "CTL009f", .driver_data=0, devs: { {.id="CTL0041"}, {.id="CTL0021"}, }},
/* Sound Blaster AWE 64 PnP */
- ISAPNP_SBAWE('C','T','L',0x009d,0x0042,0x0022),
+ {.id = "CTL009d", .driver_data=0, devs: { {.id="CTL0042"}, {.id="CTL0022"}, }},
/* Sound Blaster AWE 64 PnP Gold */
- ISAPNP_SBAWE('C','T','L',0x009e,0x0044,0x0023),
+ {.id = "CTL009e", .driver_data=0, devs: { {.id="CTL0044"}, {.id="CTL0023"}, }},
/* Sound Blaster AWE 64 PnP Gold */
- ISAPNP_SBAWE('C','T','L',0x00b2,0x0044,0x0023),
+ {.id = "CTL00b2", .driver_data=0, devs: { {.id="CTL0044"}, {.id="CTL0023"}, }},
/* Sound Blaster AWE 64 PnP */
- ISAPNP_SBAWE('C','T','L',0x00c1,0x0042,0x0022),
+ {.id = "CTL00c1", .driver_data=0, devs: { {.id="CTL0042"}, {.id="CTL0022"}, }},
/* Sound Blaster AWE 64 PnP */
- ISAPNP_SBAWE('C','T','L',0x00c3,0x0045,0x0022),
+ {.id = "CTL00c3", .driver_data=0, devs: { {.id="CTL0045"}, {.id="CTL0022"}, }},
/* Sound Blaster AWE 64 PnP */
- ISAPNP_SBAWE('C','T','L',0x00c5,0x0045,0x0022),
+ {.id = "CTL00c5", .driver_data=0, devs: { {.id="CTL0045"}, {.id="CTL0022"}, }},
/* Sound Blaster AWE 64 PnP */
- ISAPNP_SBAWE('C','T','L',0x00c7,0x0045,0x0022),
+ {.id = "CTL00c7", .driver_data=0, devs: { {.id="CTL0045"}, {.id="CTL0022"}, }},
/* Sound Blaster AWE 64 PnP */
- ISAPNP_SBAWE('C','T','L',0x00e4,0x0045,0x0022),
+ {.id = "CTL00e4", .driver_data=0, devs: { {.id="CTL0045"}, {.id="CTL0022"}, }},
/* Sound Blaster AWE 64 PnP */
- ISAPNP_SBAWE('C','T','L',0x00e9,0x0045,0x0022),
- /* Sound Blaster 16 PnP (AWE) */
- ISAPNP_SBAWE('C','T','L',0x00ed,0x0041,0x0070),
+ {.id = "CTL00e9", .driver_data=0, devs: { {.id="CTL0045"}, {.id="CTL0022"}, }},
+ /* Sound Blaster 16 PnP (AWE} */
+ {.id = "CTL00ed", .driver_data=0, devs: { {.id="CTL0041"}, {.id="CTL0070"}, }},
/* Generic entries */
- ISAPNP_SBAWE('C','T','L',ISAPNP_ANY_ID,0x0031,0x0021),
- ISAPNP_SBAWE('C','T','L',ISAPNP_ANY_ID,0x0041,0x0021),
- ISAPNP_SBAWE('C','T','L',ISAPNP_ANY_ID,0x0042,0x0022),
- ISAPNP_SBAWE('C','T','L',ISAPNP_ANY_ID,0x0044,0x0023),
- ISAPNP_SBAWE('C','T','L',ISAPNP_ANY_ID,0x0045,0x0022),
+ {.id = "CTLXXXX", .driver_data=0, devs: { {.id="CTL0031"}, {.id="CTL0021"}, }},
+ {.id = "CTLXXXX", .driver_data=0, devs: { {.id="CTL0041"}, {.id="CTL0021"}, }},
+ {.id = "CTLXXXX", .driver_data=0, devs: { {.id="CTL0042"}, {.id="CTL0022"}, }},
+ {.id = "CTLXXXX", .driver_data=0, devs: { {.id="CTL0044"}, {.id="CTL0023"}, }},
+ {.id = "CTLXXXX", .driver_data=0, devs: { {.id="CTL0045"}, {.id="CTL0022"}, }},
#endif /* SNDRV_SBAWE */
- { ISAPNP_CARD_END, }
+ {.id="", }
};
-ISAPNP_CARD_TABLE(snd_sb16_pnpids);
+/*ISAPNP_CARD_TABLE(snd_sb16_pnpids);*/
static int __init snd_sb16_isapnp(int dev, struct snd_sb16 *acard)
{
- const struct isapnp_card_id *id = snd_sb16_isapnp_id[dev];
- struct isapnp_card *card = snd_sb16_isapnp_cards[dev];
- struct isapnp_dev *pdev;
-
- acard->dev = isapnp_find_dev(card, id->devs[0].vendor, id->devs[0].function, NULL);
- if (acard->dev->active) {
- acard->dev = NULL;
- return -EBUSY;
+ const struct pnp_card_id *id = snd_sb16_isapnp_id[dev];
+ struct pnp_card *card = snd_sb16_isapnp_cards[dev];
+ struct pnp_dev *pdev;
+
+ acard->dev = pnp_request_card_device(card, id->devs[0].id, NULL);
+ if (!acard->dev) {
+ printk(KERN_ERR PFX "isapnp configure failure (no device or busy)\n");
+ return -ENODEV;
}
#ifdef SNDRV_SBAWE_EMU8000
- acard->devwt = isapnp_find_dev(card, id->devs[1].vendor, id->devs[1].function, NULL);
- if (acard->devwt->active) {
- acard->dev = acard->devwt = NULL;
- return -EBUSY;
+ acard->devwt = pnp_request_card_device(card, id->devs[1].id, NULL);
+ if (!acard->devwt) {
+ printk(KERN_ERR PFX "isapnp configure failure (no device or busy)\n");
+ return -ENODEV;
}
#endif
- /* Audio initialization */
pdev = acard->dev;
- if (pdev->prepare(pdev) < 0)
- return -EAGAIN;
- if (port[dev] != SNDRV_AUTO_PORT)
- isapnp_resource_change(&pdev->resource[0], port[dev], 16);
- if (mpu_port[dev] != SNDRV_AUTO_PORT)
- isapnp_resource_change(&pdev->resource[1], mpu_port[dev], 2);
- if (fm_port[dev] != SNDRV_AUTO_PORT)
- isapnp_resource_change(&pdev->resource[2], fm_port[dev], 4);
- if (dma8[dev] != SNDRV_AUTO_DMA)
- isapnp_resource_change(&pdev->dma_resource[0], dma8[dev], 1);
- if (dma16[dev] != SNDRV_AUTO_DMA)
- isapnp_resource_change(&pdev->dma_resource[1], dma16[dev], 1);
- if (irq[dev] != SNDRV_AUTO_IRQ)
- isapnp_resource_change(&pdev->irq_resource[0], irq[dev], 1);
- if (pdev->activate(pdev) < 0) {
- printk(KERN_ERR PFX "isapnp configure failure (out of resources?)\n");
- return -EBUSY;
- }
port[dev] = pdev->resource[0].start;
mpu_port[dev] = pdev->resource[1].start;
fm_port[dev] = pdev->resource[2].start;
@@ -318,7 +283,7 @@
#ifdef SNDRV_SBAWE_EMU8000
/* WaveTable initialization */
pdev = acard->devwt;
- if (pdev->prepare(pdev)<0) {
+/* if (pdev->prepare(pdev)<0) {
acard->dev->deactivate(acard->dev);
return -EAGAIN;
}
@@ -331,28 +296,13 @@
printk(KERN_ERR PFX "WaveTable isapnp configure failure (out of resources?)\n");
acard->dev->deactivate(acard->dev);
return -EBUSY;
- }
+ }*/
awe_port[dev] = pdev->resource[0].start;
snd_printdd("isapnp SB16: wavetable port=0x%lx\n", pdev->resource[0].start);
#endif
return 0;
}
-
-static void snd_sb16_deactivate(struct snd_sb16 *acard)
-{
- if (acard->dev) {
- acard->dev->deactivate(acard->dev);
- acard->dev = NULL;
- }
-#ifdef SNDRV_SBAWE_EMU8000
- if (acard->devwt) {
- acard->devwt->deactivate(acard->devwt);
- acard->devwt = NULL;
- }
-#endif
-}
-
-#endif /* __ISAPNP__ */
+#endif /* CONFIG_PNP */
static void snd_sb16_free(snd_card_t *card)
{
@@ -364,8 +314,9 @@
release_resource(acard->fm_res);
kfree_nocheck(acard->fm_res);
}
-#ifdef __ISAPNP__
- snd_sb16_deactivate(acard);
+#ifdef CONFIG_PNP
+ acard->devwt=NULL;
+ acard->dev=NULL;
#endif
}
@@ -392,7 +343,7 @@
return -ENOMEM;
acard = (struct snd_sb16 *) card->private_data;
card->private_free = snd_sb16_free;
-#ifdef __ISAPNP__
+#ifdef CONFIG_PNP
if (isapnp[dev] && snd_sb16_isapnp(dev, acard) < 0) {
snd_card_free(card);
return -EBUSY;
@@ -402,7 +353,7 @@
xirq = irq[dev];
xdma8 = dma8[dev];
xdma16 = dma16[dev];
-#ifdef __ISAPNP__
+#ifdef CONFIG_PNP
if (!isapnp[dev]) {
#endif
if (xirq == SNDRV_AUTO_IRQ) {
@@ -434,7 +385,7 @@
/* non-PnP AWE port address is hardwired with base port address */
awe_port[dev] = port[dev] + 0x400;
#endif
-#ifdef __ISAPNP__
+#ifdef CONFIG_PNP
}
#endif
@@ -455,7 +406,7 @@
return -ENODEV;
}
chip->mpu_port = mpu_port[dev];
-#ifdef __ISAPNP__
+#ifdef CONFIG_PNP
if (!isapnp[dev] && (err = snd_sb16dsp_configure(chip)) < 0) {
#else
if ((err = snd_sb16dsp_configure(chip)) < 0) {
@@ -563,7 +514,7 @@
for ( ; dev < SNDRV_CARDS; dev++) {
if (!enable[dev] || port[dev] != SNDRV_AUTO_PORT)
continue;
-#ifdef __ISAPNP__
+#ifdef CONFIG_PNP
if (isapnp[dev])
continue;
#endif
@@ -576,10 +527,10 @@
return -ENODEV;
}
-#ifdef __ISAPNP__
+#ifdef CONFIG_PNP
-static int __init snd_sb16_isapnp_detect(struct isapnp_card *card,
- const struct isapnp_card_id *id)
+static int __init snd_sb16_isapnp_detect(struct pnp_card *card,
+ const struct pnp_card_id *id)
{
static int dev;
int res;
@@ -599,7 +550,22 @@
return -ENODEV;
}
-#endif /* __ISAPNP__ */
+static void snd_sb16_isapnp_remove(struct pnp_card * card)
+{
+ /*FIX ME*/
+}
+
+static struct pnpc_driver sb16_pnpc_driver = {
+#ifndef SNDRV_SBAWE
+ .name = "sb16",
+#else
+ .name = "sbawe",
+#endif
+ .id_table = snd_sb16_pnpids,
+ .probe = snd_sb16_isapnp_detect,
+ .remove = snd_sb16_isapnp_remove
+};
+#endif /* CONFIG_PNP */
static int __init alsa_card_sb16_init(void)
{
@@ -610,7 +576,7 @@
for (dev = 0; dev < SNDRV_CARDS; dev++) {
if (!enable[dev] || port[dev] == SNDRV_AUTO_PORT)
continue;
-#ifdef __ISAPNP__
+#ifdef CONFIG_PNP
if (isapnp[dev])
continue;
#endif
@@ -624,9 +590,9 @@
}
/* legacy auto configured cards */
cards += snd_legacy_auto_probe(possible_ports, snd_sb16_probe_legacy_port);
-#ifdef __ISAPNP__
+#ifdef CONFIG_PNP
/* ISA PnP cards at last */
- cards += isapnp_probe_cards(snd_sb16_pnpids, snd_sb16_isapnp_detect);
+ cards += pnpc_register_driver(&sb16_pnpc_driver);
#endif
if (!cards) {
@@ -691,7 +657,7 @@
get_option(&str,&seq_ports[nr_dev]) == 2
#endif
);
-#ifdef __ISAPNP__
+#ifdef CONFIG_PNP
if (pnp != INT_MAX)
isapnp[nr_dev] = pnp;
#endif
-----------
^ permalink raw reply
* Re: SNAT in OUTPUT chain of the nat table question?
From: Ranjeet Shetye @ 2003-01-08 17:11 UTC (permalink / raw)
To: netfilter
In-Reply-To: <20030109003721.GA26207@mit.edu>
On Thu, 2003-01-09 at 01:37, bauer@mit.edu wrote:
> Is there a good reason that I am unable to conceive of at the
> moment why SNAT is not a valid target in the OUTPUT chain of the
> nat table?
>
> Thanks,
> Steve
>
>
The OUTPUT chain is only for outgoing packets from the linux box itself.
The POSTROUTING chain is the one that contains all packets being
routed/forwarded.
--
Ranjeet Shetye
Senior Software Engineer
Zultys Technologies
Ranjeet dot Shetye2 at Zultys dot com
http://www.zultys.com/
^ permalink raw reply
* [BUG] 2.5.54-mm3 OOPS in apm
From: root @ 2003-01-08 17:21 UTC (permalink / raw)
To: Linux Kernel Mailing List
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1781 bytes --]
dmesg, config and lsmod attached.
ksymoops 2.4.4 on i686 2.5.54-mm3. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.5.54-mm3/ (default)
-m /boot/System.map-2.5.54-mm3 (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
Error (regular_file): read_ksyms stat /proc/ksyms failed
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
e100: selftest OK.
e100: eth0: Intel(R) 82558-based Integrated Ethernet with Wake on LAN*
e100: eth0 NIC Link is Up 10 Mbps Half duplex
Unable to handle kernel paging request at virtual address c685b000
c685b000
*pde = 04083067
Oops: 0000
CPU: 0
EIP: 0060:[<c685b000>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000102 ebx: c68463a0 ecx: c43c58c0 edx: c52ca000
esi: ffffffff edi: ffffffff ebp: 00000000 esp: c52cbfc8
ds: 007b es: 007b ss: 0068
Stack: c6846428 c037ebd4 00000000 00000000 00000000 00000000 0000007b 0000007b
00000000 00000000 c0108ac1 00000000 00000000 00000000
[<c6846428>] apm+0x88/0x2b0 [apm]
[<c0108ac1>] show_regs+0x5/0x14
Code: Bad EIP value.
>>EIP; c685b000 <END_OF_CODE+64b5c0c/????> <=====
<6>warning: process `update' used the obsolete bdflush system call
warning: process `update' used the obsolete bdflush system call
1 warning and 1 error issued. Results may not be reliable.
[-- Attachment #2: Type: APPLICATION/octet-stream, Size: 4128 bytes --]
[-- Attachment #3: Type: APPLICATION/x-gzip, Size: 5617 bytes --]
[-- Attachment #4: Type: TEXT/PLAIN, Size: 129 bytes --]
Module Size Used by
apm 15140
parport_pc 33320
parport 34496
^ permalink raw reply
* Re: [linux-lvm] problem
From: Alasdair G Kergon @ 2003-01-08 17:14 UTC (permalink / raw)
To: linux-lvm
In-Reply-To: <20030108231014.I28021@uk.sistina.com>
On Wed, Jan 08, 2003 at 11:10:14PM +0000, Alasdair Kergon wrote:
> Write the metadata back to disk:
> vgcfgrestore -f /tmp/vgbackup rootvg
Add -M1 there to make sure it uses LVM1 format metadata!
vgcfgrestore -M1 -f /tmp/vgbackup rootvg
Alasdair
--
agk@uk.sistina.com
^ permalink raw reply
* Re: [PATCH] 2.4.20 IDE for 2.4.21-pre3
From: Michael Madore @ 2003-01-08 17:25 UTC (permalink / raw)
To: linux-kernel
I get the following oops when running 2.4.21-pre3 +
2.4.21-pre3-2420ide-1. The oops occurred after running the Cerberus
stress test for about 5 hours. The machine uses an ASUS A7N8X single
AMD Athlon XP motherboard with the Nvidia nforce2 chipset. I had to
pass ide0=ata66 ide1=ata66 to the kernel in order to use DMA.
Mike
ksymoops 2.4.4 on i686 2.4.21-1. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.21-1/ (default)
-m /boot/System.map-2.4.21-1 (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
ide_dmaproc: chipset supported ide_dma_timeout func
hda: status error: status=0x58 {driveReady Seekcomplete DataRequeset}
hda: drive not ready for command
Unable to handle kernel NULL pointer dereference at virtual address 00000018
c013cf60
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c013cf60>] Not Tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010007
eax: 00000001 ebx: cd999d40 ecx: 00000000 edx: 00000000
esi: 00000002 edi: c11f3070 ebp: 00000001 esp: c1c1bedc
ds: 0018 es: 0018 ss: 0018
Stack: cd999d40 cff1d640 00000002 00000001 c0203d4c cd999d40 00000001
cff1d640 c1330d80 00000001 00000046 c020ed3f cff1d640 00000001 c03ac68c
0000007a cff1d640 00000001 ca657a00 c02205ef 00000001 c1330d80 c1c1bf3c
00000000
Call Trace: [<c0203d4c>] [<c020ed3f>] [<c02205ef>] [<c0122879>]
[<c0210a07>] [<c0220460>] [<c010a55c>] [<c010a773>]
Code: 8b 42 18 89 c1 83 e1 04 74 16 83 e0 40 74 17 c6 05 84 5e 2f
>>EIP; c013cf60 <end_buffer_io_async+60/c0> <=====
Trace; c0203d4c <end_that_request_first+5c/b0>
Trace; c020ed3f <ide_end_request+5f/b0>
Trace; c02205ef <read_intr+18f/1d0>
Trace; c0122879 <timer_bh+2a9/3f0>
Trace; c0210a07 <ide_intr+e7/160>
Trace; c0220460 <read_intr+0/1d0>
Trace; c010a55c <handle_IRQ_event+5c/90>
Trace; c010a773 <do_IRQ+a3/f0>
Code; c013cf60 <end_buffer_io_async+60/c0>
00000000 <_EIP>:
Code; c013cf60 <end_buffer_io_async+60/c0> <=====
0: 8b 42 18 mov 0x18(%edx),%eax <=====
Code; c013cf63 <end_buffer_io_async+63/c0>
3: 89 c1 mov %eax,%ecx
Code; c013cf65 <end_buffer_io_async+65/c0>
5: 83 e1 04 and $0x4,%ecx
Code; c013cf68 <end_buffer_io_async+68/c0>
8: 74 16 je 20 <_EIP+0x20> c013cf80
<end_buffer_io_async+80/c0>
Code; c013cf6a <end_buffer_io_async+6a/c0>
a: 83 e0 40 and $0x40,%eax
Code; c013cf6d <end_buffer_io_async+6d/c0>
d: 74 17 je 26 <_EIP+0x26> c013cf86
<end_buffer_io_async+86/c0>
Code; c013cf6f <end_buffer_io_async+6f/c0>
f: c6 05 84 5e 2f 00 00 movb $0x0,0x2f5e84
<0> Kernel panic: Aiee, killing interrupt handler!
1 warning issued. Results may not be reliable.
^ permalink raw reply
* 2.4.20 make install glitch...
From: Rob Landley @ 2003-01-06 23:26 UTC (permalink / raw)
To: linux-kernel
Installing 2.4.20 on a fresh red hat 8 system, doing the standard:
make dep clean bzImage modules install modules_install:
Barfs with the following error:
---
blah blah blah...
Root device is (3, 4)
Boot sector 512 bytes.
Setup is 2645 bytes.
System is 893 kB
sh -x ./install.sh 2.4.20 bzImage /home/landley/linux-2.4.20/System.map ""
+ '[' -x /root/bin/installkernel ']'
+ '[' -x /sbin/installkernel ']'
+ exec /sbin/installkernel 2.4.20 bzImage
/home/landley/linux-2.4.20/System.map ''
/lib/modules/2.4.20 is not a directory.
make[1]: *** [install] Error 1
make[1]: Leaving directory `/home/landley/linux-2.4.20/arch/i386/boot'
make: *** [install] Error 2
---
I.E. make install tries to drop System.map into /lib/modules/`uname -a`, but
doesn't create it first.
I guess modules_install also installs the bzImage?
Rob
--
penguicon.sf.net - A combination Linux Expo and Science Fiction Convention
with GOHs Terry Pratchett, Eric Raymond, Pete Abrams, Illiad & CmdrTaco.
^ permalink raw reply
* Re: [BENCHMARK] 2.5.53 with contest
From: Rob Landley @ 2003-01-07 19:44 UTC (permalink / raw)
To: conman, linux kernel mailing list
In-Reply-To: <200212261038.04015.conman@kolivas.net>
On Wednesday 25 December 2002 23:37, Con Kolivas wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Here are some contest results using osdl hardware:
>
> Uniprocessor:
> process_load:
> Kernel [runs] Time CPU% Loads LCPU% Ratio
> 2.5.49 [5] 85.2 79 17 20 1.28
> 2.5.50 [5] 84.8 79 17 19 1.27
> 2.5.51 [2] 85.2 79 17 20 1.28
> 2.5.52 [3] 84.4 79 17 19 1.26
> 2.5.53 [7] 86.9 77 18 21 1.30
Could you add a time per load metric? (I.E. 86.9/21=4.14 seconds. Yeah, I
could do the math myself, but that and total time are usually what I'm trying
to compare when I look at these. Maybe it's just me...)
Rob
--
penguicon.sf.net - A combination Linux Expo and Science Fiction Convention
with GOHs Terry Pratchett, Eric Raymond, Pete Abrams, Illiad & CmdrTaco.
^ permalink raw reply
* Re: BDI-2000
From: Marius Groeger @ 2003-01-08 17:21 UTC (permalink / raw)
To: Wells, Charles; +Cc: 'linuxppc-embedded@lists.linuxppc.org'
In-Reply-To: <DF2B720CF774D21189EE00805FA7FA22051782FD@nmrusdunsx3.nielsenmedia.com>
On Wed, 8 Jan 2003, Wells, Charles wrote:
> When I read Cecilia's post, I assumed what the statement "proven hardware
> platform" meant was that the vxworks O/S and user tasks exercised all the
> peripheral hardware; i.e., the SDRAM works, the ROM works, the FLASH works,
> the console works, etc. So, that statement made sense to me. While Linux
vxWorks doesn't use the MMU as much as Linux does. On Linux, the kernel and
all processes run in their own address space. The memory accesses involved
for cache or tlb refills are quite different to what's happening in a
vxWorks setup. Again, I'm probably overly pessimistic here, but we _have_
seen HW problems that just didn't show up when running vxWorks (AFAIR it was
a burst access on some early G4 based system.)
On a related matter, the following might also be interesting, especially
regarding the question of what firmware to use. The vxWorks boot-loader
tends to initialise _a lot_ of things you don't necessarily need. For
instance, on IBM405 based systems it sets up the on-chip RAM at address
0x70000000. Not a good idea when switching to user-mode the first time. Took
me quite some time to find this one... ;-)
Regards,
Marius
-----------------------------------------------------------------------------
Marius Groeger SYSGO Real-Time Solutions AG mgroeger@sysgo.de
Software Engineering Embedded and Real-Time Software www.sysgo.de
Voice: +49-6136-9948-0 Am Pfaffenstein 14 www.osek.de
FAX: +49-6136-9948-10 55270 Klein-Winternheim, Germany www.elinos.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply
* Re: [BUG] 2.5.54 sb16.c compile fails
From: Ruslan U. Zakirov @ 2003-01-08 17:28 UTC (permalink / raw)
To: Bill Davidsen; +Cc: Linux Kernel Mailing List
In-Reply-To: <Pine.LNX.4.44.0301081123100.19953-100000@oddball.prodigy.com>
On Wed, 8 Jan 2003, Bill Davidsen wrote:
> gcc -Wp,-MD,sound/isa/sb/.sb16_main.o.d -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -Iinclude/asm-i386/mach-default -nostdinc -iwithprefix include -DMODULE -DKBUILD_BASENAME=sb16_main -DKBUILD_MODNAME=snd_sb16_dsp -DEXPORT_SYMTAB -c -o sound/isa/sb/sb16_main.o sound/isa/sb/sb16_main.c
> gcc -Wp,-MD,sound/isa/sb/.sb16.o.d -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i686 -Iinclude/asm-i386/mach-default -nostdinc -iwithprefix include -DMODULE -DKBUILD_BASENAME=sb16 -DKBUILD_MODNAME=snd_sb16 -c -o sound/isa/sb/sb16.o sound/isa/sb/sb16.c
> sound/isa/sb/sb16.c: In function `snd_sb16_isapnp':
> sound/isa/sb/sb16.c:276: warning: implicit declaration of function `isapnp_find_dev'
> sound/isa/sb/sb16.c:276: warning: assignment makes pointer from integer without a cast
> sound/isa/sb/sb16.c:277: structure has no member named `active'
> sound/isa/sb/sb16.c:290: structure has no member named `prepare'
> sound/isa/sb/sb16.c:293: warning: implicit declaration of function `isapnp_resource_change'
> sound/isa/sb/sb16.c:304: structure has no member named `activate'
> sound/isa/sb/sb16.c: In function `snd_sb16_deactivate':
> sound/isa/sb/sb16.c:344: structure has no member named `deactivate'
> sound/isa/sb/sb16.c: In function `alsa_card_sb16_init':
> sound/isa/sb/sb16.c:629: warning: implicit declaration of function `isapnp_probe_cards'
> make[3]: *** [sound/isa/sb/sb16.o] Error 1
> make[2]: *** [sound/isa/sb] Error 2
> make[1]: *** [sound/isa] Error 2
> make: *** [sound] Error 2
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
Hello!
All this errors relay to new PnP layer implementation.
I've send PATCH to SB16/AWE32 card just now.
If you have this card, can you test it and send me results?
Ruslan.
^ permalink raw reply
* Re: BUILD PROBLEM - Linux 2.5 BK - smpboot.c
From: Andrew Walrond @ 2003-01-08 17:30 UTC (permalink / raw)
To: Sam Ravnborg; +Cc: linux-kernel
In-Reply-To: <20030108162844.GA1025@mars.ravnborg.org>
Sam Ravnborg wrote:
> In BK recent mach_acpi is included on line 55.
> Sure you have a clean tree?
>
> Sam
>
Please disregard. My Stupidity alarm has just gone off, along with the
Newbie BK user detector :(
^ permalink raw reply
* Re: USB CF reader reboots PC
From: Murray J. Root @ 2003-01-08 17:33 UTC (permalink / raw)
To: linux-kernel
In-Reply-To: <20030108165130.GA1181@Master.Wizards>
Ooops - kernel 2.5.5[234]
On Wed, Jan 08, 2003 at 11:51:30AM -0500, Murray J. Root wrote:
> ASUS P4S533 (SiS645DX chipset)
> P4 2GHz
> 1G PC2700 RAM
> SanDisk SDDR-77 ImageMate Dual Card Reader (using only CF cards)
>
> ----------------------------
> devfs compiled in to kernel, devfs=nomount in lilo.conf
>
> Insert CF card. mount it. cd to it, do reads and/or writes
> umount card. remove card.
> insert a different card (does not happen if the same card is used)
> mount it. system reboots. logs are corrupted
>
> Doesn't happen every time for read - sometimes I can read 2 or 3 cards first
> Happens every time for write - if I write to a card then changing cards
> causes a reboot
>
> ----------------------------
> devfs=mount in lilo.conf
>
> Insert CF card.
> ls /dev shows sda and sda1
> mount it.
> ls /dev shows sda - no sda1
> cd to mounted CF card
> process hangs, sd-mod & usb-storage "busy"
> rmmod -f usb-storage or sd-mod causes PC to stop
> (keyboard & mouse unresponsive, wmfire frozen, net disconnects)
>
> reboot
> Insert CF card.
> ls /dev shows sda & sda1
> mount it.
> ls /dev shows sda - no sda1
> umount it
> ls /dev shows sda - no sda1
> modprobe -r sd-mod && modprobe sd-mod
> ls /dev shows sda & sda1
>
> --
> Murray J. Root
> ------------------------------------------------
> DISCLAIMER: http://www.goldmark.org/jeff/stupid-disclaimers/
> ------------------------------------------------
> Mandrake on irc.freenode.net:
> #mandrake & #mandrake-linux = help for newbies
> #mdk-cooker = Mandrake Cooker
> #cooker = moderated Mandrake Cooker
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Murray J. Root
------------------------------------------------
DISCLAIMER: http://www.goldmark.org/jeff/stupid-disclaimers/
------------------------------------------------
Mandrake on irc.freenode.net:
#mandrake & #mandrake-linux = help for newbies
#mdk-cooker = Mandrake Cooker
#cooker = moderated Mandrake Cooker
^ permalink raw reply
* Problem running SMP on IBM xSeries 360
From: Michael.Kropinack @ 2003-01-08 17:27 UTC (permalink / raw)
To: linux-smp
Hi,
I'm running an IBM xSeries 360 Server with 2 Xeon CPU's. The server
has 4 cpu
slots, but only 2 cpu's. The server boots up fine, but has been crashing
frequently,
with uptimes between 2 hours and 3 days. During these crashes, there has
been no
message on the CRT, nor any in the logs.
Can someone tell me why the kernel is seeing 4 CPU's when there are
only 2?
I've been through all of the FAQ's/HOWTO's and through IBM's support site
and I can't
find any mention of the issue. Also, any suggestions on how to fix this
would be
appreciated. I've included all of the kernel messages from the latest boot.
Thanks in advance,
Mike Kropinack
Aventis Pharmaceuticals
Jan 8 06:13:20 brwslnx02 kernel: klogd 1.4.1, log source = /proc/kmsg
started.
Jan 8 06:13:20 brwslnx02 kernel: Linux version 2.4.18-18.7.xsmp
(bhcompile@bugs.devel.redhat.com) (gcc version 2.96 20000731 (Red Hat Linux
7.3 2.96-112)) #1 SMP Wed Nov 13 19:01:42 EST 2002
Jan 8 06:13:20 brwslnx02 kernel: BIOS-provided physical RAM map:
Jan 8 06:13:20 brwslnx02 kernel: BIOS-e820: 0000000000000000 -
000000000009d000 (usable)
Jan 8 06:13:20 brwslnx02 kernel: BIOS-e820: 000000000009d000 -
00000000000a0000 (reserved)
Jan 8 06:13:20 brwslnx02 kernel: BIOS-e820: 00000000000e0000 -
0000000000100000 (reserved)
Jan 8 06:13:20 brwslnx02 kernel: BIOS-e820: 0000000000100000 -
000000007f0ea400 (usable)
Jan 8 06:13:20 brwslnx02 kernel: BIOS-e820: 000000007f0ea400 -
000000007f0f0000 (ACPI data)
Jan 8 06:13:20 brwslnx02 kernel: BIOS-e820: 000000007f0f0000 -
0000000080000000 (reserved)
Jan 8 06:13:20 brwslnx02 kernel: BIOS-e820: 00000000fec00000 -
00000000fec01000 (reserved)
Jan 8 06:13:20 brwslnx02 kernel: BIOS-e820: 00000000fee00000 -
00000000fee01000 (reserved)
Jan 8 06:13:20 brwslnx02 kernel: BIOS-e820: 00000000fff00000 -
0000000100000000 (reserved)
Jan 8 06:13:20 brwslnx02 kernel: 1136MB HIGHMEM available.
Jan 8 06:13:20 brwslnx02 kernel: 896MB LOWMEM available.
Jan 8 06:13:20 brwslnx02 kernel: found SMP MP-table at 0009e1d0
Jan 8 06:13:21 brwslnx02 kernel: hm, page 0009e000 reserved twice.
Jan 8 06:13:21 brwslnx02 kernel: hm, page 0009f000 reserved twice.
Jan 8 06:13:21 brwslnx02 kernel: hm, page 0009e000 reserved twice.
Jan 8 06:13:21 brwslnx02 kernel: hm, page 0009f000 reserved twice.
Jan 8 06:13:21 brwslnx02 kernel: WARNING: MP table in the EBDA can be
UNSAFE, contact linux-smp@vger.kernel.org if you experience SMP problems!
Jan 8 06:13:21 brwslnx02 kernel: On node 0 totalpages: 520426
Jan 8 06:13:21 brwslnx02 kernel: zone(0): 4096 pages.
Jan 8 06:13:21 brwslnx02 kernel: zone(1): 225280 pages.
Jan 8 06:13:21 brwslnx02 kernel: zone(2): 291050 pages.
Jan 8 06:13:21 brwslnx02 kernel: ACPI: Searched entire block, no RSDP was
found.
Jan 8 06:13:21 brwslnx02 kernel: ACPI: RSDP located at physical address
c00fdfe0
Jan 8 06:13:21 brwslnx02 kernel: RSD PTR v0 [IBM ]
Jan 8 06:13:21 brwslnx02 kernel: __va_range(0x7f0eff80, 0x68): idx=8 mapped
at ffff6000
Jan 8 06:13:21 brwslnx02 kernel: ACPI table found: RSDT v1 [IBM SERCRSDR
0.4098]
Jan 8 06:13:21 brwslnx02 kernel: __va_range(0x7f0eff00, 0x24): idx=8 mapped
at ffff6000
Jan 8 06:13:21 brwslnx02 kernel: __va_range(0x7f0eff00, 0x74): idx=8 mapped
at ffff6000
Jan 8 06:13:21 brwslnx02 kernel: ACPI table found: FACP v1 [IBM SERCRSDR
0.4098]
Jan 8 06:13:21 brwslnx02 kernel: __va_range(0x7f0efe80, 0x24): idx=8 mapped
at ffff6000
Jan 8 06:13:21 brwslnx02 kernel: __va_range(0x7f0efe80, 0x7c): idx=8 mapped
at ffff6000
Jan 8 06:13:21 brwslnx02 kernel: ACPI table found: APIC v1 [IBM SERCRSDR
0.4098]
Jan 8 06:13:21 brwslnx02 kernel: __va_range(0x7f0efe80, 0x7c): idx=8 mapped
at ffff6000
Jan 8 06:13:21 brwslnx02 kernel: LAPIC (acpi_id[0x0000] id[0x0] enabled[1])
Jan 8 06:13:21 brwslnx02 kernel: CPU 0 (0x0000) enabledProcessor #0 Unknown
CPU [15:1] APIC version 16
Jan 8 06:13:21 brwslnx02 kernel:
Jan 8 06:13:21 brwslnx02 kernel: LAPIC (acpi_id[0x0001] id[0x4] enabled[1])
Jan 8 06:13:21 brwslnx02 kernel: CPU 1 (0x0400) enabledProcessor #4 Unknown
CPU [15:1] APIC version 16
Jan 8 06:13:21 brwslnx02 kernel:
Jan 8 06:13:21 brwslnx02 kernel: LAPIC (acpi_id[0x0002] id[0x1] enabled[1])
Jan 8 06:13:21 brwslnx02 kernel: CPU 2 (0x0100) enabledProcessor #1 Unknown
CPU [15:1] APIC version 16
Jan 8 06:13:21 brwslnx02 kernel:
Jan 8 06:13:21 brwslnx02 kernel: LAPIC (acpi_id[0x0003] id[0x5] enabled[1])
Jan 8 06:13:21 brwslnx02 kernel: CPU 3 (0x0500) enabledProcessor #5 Unknown
CPU [15:1] APIC version 16
Jan 8 06:13:21 brwslnx02 kernel:
Jan 8 06:13:21 brwslnx02 kernel: IOAPIC (id[0xe] address[0xfec00000]
global_irq_base[0x0])
Jan 8 06:13:21 brwslnx02 kernel: INT_SRC_OVR (bus[0] irq[0x0]
global_irq[0x2] polarity[0x0] trigger[0x0])
Jan 8 06:13:21 brwslnx02 kernel: INT_SRC_OVR (bus[0] irq[0x8]
global_irq[0x8] polarity[0x3] trigger[0x1])
Jan 8 06:13:22 brwslnx02 kernel: INT_SRC_OVR (bus[0] irq[0x9]
global_irq[0x24] polarity[0x3] trigger[0x3])
Jan 8 06:13:22 brwslnx02 kernel: LAPIC_NMI (acpi_id[0x00ff] polarity[0x1]
trigger[0x1] lint[0x1])
Jan 8 06:13:22 brwslnx02 kernel: 4 CPUs total
Jan 8 06:13:22 brwslnx02 kernel: Local APIC address fee00000
Jan 8 06:13:22 brwslnx02 kernel: Enabling the CPU's according to the ACPI
table
Jan 8 06:13:22 brwslnx02 kernel: Intel MultiProcessor Specification v1.4
Jan 8 06:13:22 brwslnx02 kernel: Virtual Wire compatibility mode.
Jan 8 06:13:22 brwslnx02 kernel: OEM ID: IBM ENSW Product ID: NF 6000R SMP
APIC at: 0xFEE00000
Jan 8 06:13:22 brwslnx02 kernel: I/O APIC #14 Version 17 at 0xFEC00000.
Jan 8 06:13:22 brwslnx02 kernel: Processors: 4
Jan 8 06:13:22 brwslnx02 kernel: IBM machine detected. Enabling interrupts
during APM calls.
Jan 8 06:13:22 brwslnx02 kernel: Kernel command line: auto
BOOT_IMAGE=linux-newkernel ro root=806
BOOT_FILE=/boot/vmlinuz-2.4.18-18.7.xsmp
Jan 8 06:13:22 brwslnx02 kernel: Initializing CPU#0
Jan 8 06:13:22 brwslnx02 kernel: Detected 1500.596 MHz processor.
Jan 8 06:13:22 brwslnx02 kernel: Speakup v-1.00 CVS: Tue Jun 11 14:22:53
EDT 2002 : initialized
Jan 8 06:13:22 brwslnx02 kernel: Console: colour VGA+ 80x25
Jan 8 06:13:22 brwslnx02 kernel: Calibrating delay loop... 2971.18 BogoMIPS
Jan 8 06:13:22 brwslnx02 kernel: Memory: 2045028k/2081704k available (1280k
kernel code, 32056k reserved, 1051k data, 188k init, 1164200k highmem)
Jan 8 06:13:22 brwslnx02 kernel: Dentry cache hash table entries: 262144
(order: 9, 2097152 bytes)
Jan 8 06:13:22 brwslnx02 kernel: Inode cache hash table entries: 131072
(order: 8, 1048576 bytes)
Jan 8 06:13:22 brwslnx02 kernel: Mount cache hash table entries: 32768
(order: 6, 262144 bytes)
Jan 8 06:13:22 brwslnx02 kernel: Buffer cache hash table entries: 131072
(order: 7, 524288 bytes)
Jan 8 06:13:22 brwslnx02 kernel: Page-cache hash table entries: 524288
(order: 9, 2097152 bytes)
Jan 8 06:13:22 brwslnx02 kernel: CPU: L1 I cache: 0K, L1 D cache: 8K
Jan 8 06:13:22 brwslnx02 kernel: CPU: L2 cache: 256K
Jan 8 06:13:22 brwslnx02 kernel: CPU: L3 cache: 512K
Jan 8 06:13:22 brwslnx02 kernel: CPU: Physical Processor ID: 0
Jan 8 06:13:22 brwslnx02 kernel: Intel machine check architecture
supported.
Jan 8 06:13:22 brwslnx02 kernel: Intel machine check reporting enabled on
CPU#0.
Jan 8 06:13:22 brwslnx02 kernel: Enabling fast FPU save and restore...
done.
Jan 8 06:13:22 brwslnx02 kernel: Enabling unmasked SIMD FPU exception
support... done.
Jan 8 06:13:22 brwslnx02 kernel: Checking 'hlt' instruction... OK.
Jan 8 06:13:22 brwslnx02 kernel: POSIX conformance testing by UNIFIX
Jan 8 06:13:22 brwslnx02 kernel: mtrr: v1.40 (20010327) Richard Gooch
(rgooch@atnf.csiro.au)
Jan 8 06:13:22 brwslnx02 kernel: mtrr: detected mtrr type: Intel
Jan 8 06:13:22 brwslnx02 kernel: CPU: L1 I cache: 0K, L1 D cache: 8K
Jan 8 06:13:22 brwslnx02 kernel: CPU: L2 cache: 256K
Jan 8 06:13:22 brwslnx02 kernel: CPU: L3 cache: 512K
Jan 8 06:13:22 brwslnx02 kernel: CPU: Physical Processor ID: 0
Jan 8 06:13:22 brwslnx02 kernel: Intel machine check reporting enabled on
CPU#0.
Jan 8 06:13:22 brwslnx02 kernel: CPU0: Intel(R) Xeon(TM) CPU 1.50GHz
stepping 01
Jan 8 06:13:22 brwslnx02 kernel: per-CPU timeslice cutoff: 731.50 usecs.
Jan 8 06:13:22 brwslnx02 kernel: task migration cache decay timeout: 1
msecs.
Jan 8 06:13:22 brwslnx02 kernel: enabled ExtINT on CPU#0
Jan 8 06:13:22 brwslnx02 kernel: ESR value before enabling vector: 00000000
Jan 8 06:13:22 brwslnx02 kernel: ESR value after enabling vector: 00000000
Jan 8 06:13:22 brwslnx02 kernel: Booting processor 1/1 eip 2000
Jan 8 06:13:22 brwslnx02 kernel: Initializing CPU#1
Jan 8 06:13:22 brwslnx02 kernel: masked ExtINT on CPU#1
Jan 8 06:13:22 brwslnx02 kernel: ESR value before enabling vector: 00000000
Jan 8 06:13:22 brwslnx02 kernel: ESR value after enabling vector: 00000000
Jan 8 06:13:22 brwslnx02 kernel: Calibrating delay loop... 2996.49 BogoMIPS
Jan 8 06:13:22 brwslnx02 kernel: CPU: L1 I cache: 0K, L1 D cache: 8K
Jan 8 06:13:22 brwslnx02 kernel: CPU: L2 cache: 256K
Jan 8 06:13:22 brwslnx02 kernel: CPU: L3 cache: 512K
Jan 8 06:13:22 brwslnx02 kernel: CPU: Physical Processor ID: 0
Jan 8 06:13:22 brwslnx02 kernel: Intel machine check reporting enabled on
CPU#1.
Jan 8 06:13:22 brwslnx02 kernel: CPU1: Intel(R) Xeon(TM) CPU 1.50GHz
stepping 01
Jan 8 06:13:22 brwslnx02 kernel: Booting processor 2/4 eip 2000
Jan 8 06:13:22 brwslnx02 kernel: Initializing CPU#2
Jan 8 06:13:22 brwslnx02 kernel: masked ExtINT on CPU#2
Jan 8 06:13:22 brwslnx02 kernel: ESR value before enabling vector: 00000000
Jan 8 06:12:11 brwslnx02 sysctl: kernel.sysrq = 0
Jan 8 06:13:22 brwslnx02 kernel: ESR value after enabling vector: 00000000
Jan 8 06:12:11 brwslnx02 sysctl: kernel.core_uses_pid = 1
Jan 8 06:13:23 brwslnx02 kernel: Calibrating delay loop... 2996.49 BogoMIPS
Jan 8 06:12:11 brwslnx02 rc.sysinit: Configuring kernel parameters:
succeeded
Jan 8 06:13:23 brwslnx02 kernel: CPU: L1 I cache: 0K, L1 D cache: 8K
Jan 8 06:13:23 brwslnx02 kernel: CPU: L2 cache: 256K
Jan 8 06:13:23 brwslnx02 kernel: CPU: L3 cache: 512K
Jan 8 06:13:23 brwslnx02 kernel: CPU: Physical Processor ID: 2
Jan 8 06:13:23 brwslnx02 kernel: Intel machine check reporting enabled on
CPU#2.
Jan 8 06:12:11 brwslnx02 modprobe:
/lib/modules/2.4.18-18.7.xsmp/kernel/drivers/usb/usb-ohci.o:
Jan 8 06:13:23 brwslnx02 kernel: CPU2: Intel(R) Xeon(TM) CPU 1.50GHz
stepping 01
Jan 8 06:13:23 brwslnx02 kernel: Booting processor 3/5 eip 2000
Jan 8 06:13:23 brwslnx02 kernel: Initializing CPU#3
Jan 8 06:12:11 brwslnx02 modprobe:
/lib/modules/2.4.18-18.7.xsmp/kernel/drivers/usb/usb-ohci.o: insmod
/lib/modules/2.4.18-18.7.xsmp/kernel/drivers/usb/usb-ohci.o failed
Jan 8 06:13:23 brwslnx02 kernel: masked ExtINT on CPU#3
Jan 8 06:12:11 brwslnx02 modprobe:
/lib/modules/2.4.18-18.7.xsmp/kernel/drivers/usb/usb-ohci.o: insmod usb-ohci
failed
Jan 8 06:13:23 brwslnx02 kernel: ESR value before enabling vector: 00000000
Jan 8 06:13:23 brwslnx02 kernel: ESR value after enabling vector: 00000000
Jan 8 06:13:23 brwslnx02 kernel: Calibrating delay loop... 2996.49 BogoMIPS
Jan 8 06:13:24 brwslnx02 kernel: CPU: L1 I cache: 0K, L1 D cache: 8K
Jan 8 06:13:24 brwslnx02 kernel: CPU: L2 cache: 256K
Jan 8 06:13:24 brwslnx02 kernel: CPU: L3 cache: 512K
Jan 8 06:13:24 brwslnx02 kernel: CPU: Physical Processor ID: 2
Jan 8 06:13:24 brwslnx02 kernel: Intel machine check reporting enabled on
CPU#3.
Jan 8 06:13:24 brwslnx02 kernel: CPU3: Intel(R) Xeon(TM) CPU 1.50GHz
stepping 01
Jan 8 06:13:24 brwslnx02 kernel: Total of 4 processors activated (11960.66
BogoMIPS).
Jan 8 06:13:24 brwslnx02 kernel: cpu_sibling_map[0] = 1
Jan 8 06:13:24 brwslnx02 kernel: cpu_sibling_map[1] = 0
Jan 8 06:13:24 brwslnx02 kernel: cpu_sibling_map[2] = 3
Jan 8 06:13:24 brwslnx02 kernel: cpu_sibling_map[3] = 2
Jan 8 06:13:24 brwslnx02 kernel: ENABLING IO-APIC IRQs
Jan 8 06:13:24 brwslnx02 kernel: Setting 14 in the phys_id_present_map
Jan 8 06:13:24 brwslnx02 kernel: ...changing IO-APIC physical APIC ID to 14
... ok.
Jan 8 06:13:25 brwslnx02 kernel: ..TIMER: vector=0x31 pin1=2 pin2=-1
Jan 8 06:13:25 brwslnx02 kernel: testing the IO APIC.......................
Jan 8 06:13:17 brwslnx02 sysctl: kernel.sysrq = 0
Jan 8 06:13:17 brwslnx02 sysctl: kernel.core_uses_pid = 1
Jan 8 06:13:25 brwslnx02 kernel:
Jan 8 06:13:25 brwslnx02 kernel: WARNING: unexpected IO-APIC, please mail
Jan 8 06:13:26 brwslnx02 kernel: to linux-smp@vger.kernel.org
Jan 8 06:13:26 brwslnx02 kernel: .................................... done.
Jan 8 06:13:26 brwslnx02 kernel: Using local APIC timer interrupts.
Jan 8 06:13:26 brwslnx02 kernel: calibrating APIC timer ...
Jan 8 06:13:26 brwslnx02 kernel: ..... CPU clock speed is 1499.1899 MHz.
Jan 8 06:13:26 brwslnx02 kernel: ..... host bus clock speed is 99.1949 MHz.
Jan 8 06:13:26 brwslnx02 kernel: cpu: 0, clocks: 195296, slice: 39059
Jan 8 06:13:26 brwslnx02 kernel:
CPU0<T0:195296,T1:156224,D:13,S:39059,C:195296>
Jan 8 06:13:26 brwslnx02 kernel: cpu: 2, clocks: 195296, slice: 39059
Jan 8 06:13:26 brwslnx02 kernel: cpu: 1, clocks: 195296, slice: 39059
Jan 8 06:13:26 brwslnx02 kernel: cpu: 3, clocks: 195296, slice: 39059
Jan 8 06:13:26 brwslnx02 kernel:
CPU1<T0:195296,T1:117168,D:10,S:39059,C:195296>
Jan 8 06:13:26 brwslnx02 kernel:
CPU2<T0:195296,T1:78096,D:23,S:39059,C:195296>
Jan 8 06:13:26 brwslnx02 kernel:
CPU3<T0:195296,T1:39040,D:20,S:39059,C:195296>
Jan 8 06:13:26 brwslnx02 kernel: checking TSC synchronization across CPUs:
passed.
Jan 8 06:13:26 brwslnx02 kernel: migration_task 0 on cpu=0
Jan 8 06:13:26 brwslnx02 kernel: migration_task 1 on cpu=1
Jan 8 06:13:26 brwslnx02 kernel: migration_task 2 on cpu=2
Jan 8 06:13:26 brwslnx02 kernel: migration_task 3 on cpu=3
Jan 8 06:13:26 brwslnx02 kernel: PCI: PCI BIOS revision 2.10 entry at
0xfd31c, last bus=14
Jan 8 06:13:26 brwslnx02 kernel: PCI: Using configuration type 1
Jan 8 06:13:26 brwslnx02 kernel: PCI: Probing PCI hardware
Jan 8 06:13:26 brwslnx02 kernel: PCI: Discovered peer bus 01
Jan 8 06:13:26 brwslnx02 kernel: PCI: Discovered peer bus 0a
Jan 8 06:13:26 brwslnx02 kernel: PCI->APIC IRQ transform: (B0,I2,P0) -> 17
Jan 8 06:13:26 brwslnx02 kernel: PCI->APIC IRQ transform: (B0,I3,P0) -> 42
Jan 8 06:13:26 brwslnx02 kernel: PCI->APIC IRQ transform: (B0,I15,P0) -> 16
Jan 8 06:13:26 brwslnx02 kernel: PCI->APIC IRQ transform: (B1,I4,P0) -> 20
Jan 8 06:13:26 brwslnx02 kernel: PCI->APIC IRQ transform: (B10,I1,P0) -> 29
Jan 8 06:13:26 brwslnx02 kernel: isapnp: Scanning for PnP cards...
Jan 8 06:13:26 brwslnx02 kernel: isapnp: No Plug & Play device found
Jan 8 06:13:26 brwslnx02 kernel: speakup: initialized device: /dev/synth,
node (MAJOR 10, MINOR 25)
Jan 8 06:13:26 brwslnx02 kernel: Linux NET4.0 for Linux 2.4
Jan 8 06:13:26 brwslnx02 kernel: Based upon Swansea University Computer
Society NET3.039
Jan 8 06:13:26 brwslnx02 kernel: Initializing RT netlink socket
Jan 8 06:13:26 brwslnx02 kernel: apm: BIOS not found.
Jan 8 06:13:26 brwslnx02 kernel: Starting kswapd
Jan 8 06:13:26 brwslnx02 kernel: allocated 64 pages and 64 bhs reserved for
the highmem bounces
Jan 8 06:13:26 brwslnx02 kernel: VFS: Diskquotas version dquot_6.5.0
initialized
Jan 8 06:13:26 brwslnx02 kernel: Detected PS/2 Mouse Port.
Jan 8 06:13:26 brwslnx02 kernel: pty: 2048 Unix98 ptys configured
Jan 8 06:13:26 brwslnx02 kernel: Serial driver version 5.05c (2001-07-08)
with MANY_PORTS MULTIPORT SHARE_IRQ SERIAL_PCI ISAPNP enabled
Jan 8 06:13:27 brwslnx02 kernel: Real Time Clock Driver v1.10e
Jan 8 06:13:27 brwslnx02 kernel: oprofile: can't get RTC I/O Ports
Jan 8 06:13:27 brwslnx02 kernel: block: 1024 slots per queue, batch=256
Jan 8 06:13:27 brwslnx02 kernel: Uniform Multi-Platform E-IDE driver
Revision: 6.31
Jan 8 06:13:27 brwslnx02 kernel: ide: Assuming 33MHz system bus speed for
PIO modes; override with idebus=xx
Jan 8 06:13:27 brwslnx02 kernel: SvrWks OSB4: IDE controller on PCI bus 00
dev 79
Jan 8 06:13:27 brwslnx02 kernel: SvrWks OSB4: chipset revision 0
Jan 8 06:13:27 brwslnx02 kernel: SvrWks OSB4: not 100%% native mode: will
probe irqs later
Jan 8 06:13:27 brwslnx02 kernel: ide0: BM-DMA at 0x0700-0x0707, BIOS
settings: hda:DMA, hdb:DMA
Jan 8 06:13:27 brwslnx02 kernel: ide1: BM-DMA at 0x0708-0x070f, BIOS
settings: hdc:pio, hdd:pio
Jan 8 06:13:27 brwslnx02 kernel: hda: LG CD-ROM CRN-8245B, ATAPI CD/DVD-ROM
drive
Jan 8 06:13:27 brwslnx02 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Jan 8 06:13:27 brwslnx02 kernel: ide-floppy driver 0.99.newide
Jan 8 06:13:27 brwslnx02 kernel: Floppy drive(s): fd0 is 1.44M
Jan 8 06:13:27 brwslnx02 kernel: FDC 0 is a National Semiconductor PC87306
Jan 8 06:13:27 brwslnx02 kernel: NET4: Frame Diverter 0.46
Jan 8 06:13:27 brwslnx02 kernel: RAMDISK driver initialized: 16 RAM disks
of 4096K size 1024 blocksize
Jan 8 06:13:27 brwslnx02 kernel: ide-floppy driver 0.99.newide
Jan 8 06:13:27 brwslnx02 kernel: md: md driver 0.90.0 MAX_MD_DEVS=256,
MD_SB_DISKS=27
Jan 8 06:13:27 brwslnx02 kernel: md: Autodetecting RAID arrays.
Jan 8 06:13:27 brwslnx02 kernel: md: autorun ...
Jan 8 06:13:27 brwslnx02 kernel: md: ... autorun DONE.
Jan 8 06:13:27 brwslnx02 kernel: pci_hotplug: PCI Hot Plug PCI Core
version: 0.4
Jan 8 06:13:27 brwslnx02 kernel: NET4: Linux TCP/IP 1.0 for NET4.0
Jan 8 06:13:27 brwslnx02 kernel: IP Protocols: ICMP, UDP, TCP, IGMP
Jan 8 06:13:27 brwslnx02 kernel: IP: routing cache hash table of 16384
buckets, 128Kbytes
Jan 8 06:13:27 brwslnx02 kernel: TCP: Hash tables configured (established
262144 bind 65536)
Jan 8 06:13:27 brwslnx02 kernel: Linux IP multicast router 0.06 plus PIM-SM
Jan 8 06:13:28 brwslnx02 kernel: NET4: Unix domain sockets 1.0/SMP for
Linux NET4.0.
Jan 8 06:13:28 brwslnx02 kernel: RAMDISK: Compressed image found at block 0
Jan 8 06:13:28 brwslnx02 kernel: Freeing initrd memory: 208k freed
Jan 8 06:13:28 brwslnx02 kernel: VFS: Mounted root (ext2 filesystem).
Jan 8 06:13:28 brwslnx02 kernel: SCSI subsystem driver Revision: 1.00
Jan 8 06:13:28 brwslnx02 kernel: kmod: failed to exec /sbin/modprobe -s -k
scsi_hostadapter, errno = 2
Jan 8 06:13:28 brwslnx02 kernel: Warning: Adapter 0 Firmware Compatible
Version is 4.84.01, but should be SA510
Jan 8 06:13:28 brwslnx02 kernel: Warning: Adapter 0 BIOS Compatible Version
is , but should be SA510
Jan 8 06:13:28 brwslnx02 kernel: Warning ! ! ! ServeRAID Version Mismatch
Jan 8 06:13:28 brwslnx02 kernel: scsi0 : IBM PCI ServeRAID 5.10.21
<ServeRAID 4Mx>
Jan 8 06:13:28 brwslnx02 kernel: Vendor: IBM Model: SERVERAID
Rev: 1.00
Jan 8 06:13:28 brwslnx02 kernel: Type: Direct-Access
ANSI SCSI revision: 02
Jan 8 06:13:28 brwslnx02 kernel: Vendor: IBM Model: SERVERAID
Rev: 1.00
Jan 8 06:13:28 brwslnx02 kernel: Type: Direct-Access
ANSI SCSI revision: 02
Jan 8 06:13:28 brwslnx02 kernel: Vendor: IBM Model: SERVERAID
Rev: 1.00
Jan 8 06:13:28 brwslnx02 kernel: Type: Processor
ANSI SCSI revision: 02
Jan 8 06:13:28 brwslnx02 kernel: Vendor: IBM Model: YGHv3 S2
Rev: 0
Jan 8 06:13:28 brwslnx02 kernel: Type: Processor
ANSI SCSI revision: 02
Jan 8 06:13:28 brwslnx02 kernel: Attached scsi disk sda at scsi0, channel
0, id 0, lun 0
Jan 8 06:13:28 brwslnx02 kernel: Attached scsi disk sdb at scsi0, channel
0, id 1, lun 0
Jan 8 06:13:28 brwslnx02 kernel: SCSI device sda: 16384000 512-byte hdwr
sectors (8389 MB)
Jan 8 06:13:28 brwslnx02 kernel: Partition check:
Jan 8 06:13:28 brwslnx02 kernel: sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7
>
Jan 8 06:13:28 brwslnx02 kernel: SCSI device sdb: 125808640 512-byte hdwr
sectors (64414 MB)
Jan 8 06:13:28 brwslnx02 kernel: sdb: sdb1
Jan 8 06:13:28 brwslnx02 kernel: Journalled Block Device driver loaded
Jan 8 06:13:28 brwslnx02 kernel: EXT3-fs: INFO: recovery required on
readonly filesystem.
Jan 8 06:13:28 brwslnx02 kernel: EXT3-fs: write access will be enabled
during recovery.
Jan 8 06:13:29 brwslnx02 kernel: kjournald starting. Commit interval 5
seconds
Jan 8 06:13:29 brwslnx02 kernel: EXT3-fs: recovery complete.
Jan 8 06:13:29 brwslnx02 kernel: EXT3-fs: mounted filesystem with ordered
data mode.
Jan 8 06:13:29 brwslnx02 kernel: Freeing unused kernel memory: 188k freed
Jan 8 06:13:29 brwslnx02 kernel: Adding Swap: 2096252k swap-space (priority
-1)
Jan 8 06:13:29 brwslnx02 kernel: usb.c: registered new driver usbdevfs
Jan 8 06:13:29 brwslnx02 kernel: usb.c: registered new driver hub
Jan 8 06:13:29 brwslnx02 kernel: usb-ohci.c: USB OHCI at membase
0xf8978000, IRQ 16
Jan 8 06:13:29 brwslnx02 kernel: usb-ohci.c: usb-00:0f.2, ServerWorks
OSB4/CSB5 OHCI USB Controller
Jan 8 06:13:29 brwslnx02 kernel: usb-ohci.c: USB HC TakeOver failed!
Jan 8 06:13:29 brwslnx02 kernel: Trying to vfree() nonexistent vm area
(f8978000)
Jan 8 06:13:29 brwslnx02 kernel: f7a7bec4 00001000 f897570c f8976160
c4676c00 00000000 c01c762c c4676c00
Jan 8 06:13:29 brwslnx02 kernel: f897570c c4676c00 f8976160 00000000
00000001 c01c7692 f8976160 c4676c00
Jan 8 06:13:29 brwslnx02 kernel: 00000000 00000001 00000001 f8974eff
f8976160 0001b539 f8971000 00000001
Jan 8 06:13:29 brwslnx02 kernel: Call Trace: [<f897570c>] ohci_pci_ids
[usb-ohci] 0x1c (0xf7a7becc))
Jan 8 06:13:29 brwslnx02 kernel: [<f8976160>] ohci_pci_driver [usb-ohci]
0x0 (0xf7a7bed0))
Jan 8 06:13:29 brwslnx02 kernel: [<c01c762c>] pci_announce_device [kernel]
0x3c (0xf7a7bedc))
Jan 8 06:13:29 brwslnx02 kernel: [<f897570c>] ohci_pci_ids [usb-ohci] 0x1c
(0xf7a7bee4))
Jan 8 06:13:29 brwslnx02 kernel: [<f8976160>] ohci_pci_driver [usb-ohci]
0x0 (0xf7a7beec))
Jan 8 06:13:29 brwslnx02 kernel: [<c01c7692>] pci_register_driver [kernel]
0x42 (0xf7a7bef8))
Jan 8 06:13:29 brwslnx02 kernel: [<f8976160>] ohci_pci_driver [usb-ohci]
0x0 (0xf7a7befc))
Jan 8 06:13:29 brwslnx02 kernel: [<f8974eff>] ohci_hcd_init [usb-ohci] 0x1f
(0xf7a7bf10))
Jan 8 06:13:29 brwslnx02 kernel: [<f8976160>] ohci_pci_driver [usb-ohci]
0x0 (0xf7a7bf14))
Jan 8 06:13:29 brwslnx02 kernel: [<c011eba5>] sys_init_module [kernel]
0x555 (0xf7a7bf2c))
Jan 8 06:13:29 brwslnx02 kernel: [<f8975830>] .kmodtab [usb-ohci] 0x0
(0xf7a7bf30))
Jan 8 06:13:29 brwslnx02 kernel: [<f8971060>] ohci_mem_init [usb-ohci] 0x0
(0xf7a7bf58))
Jan 8 06:13:29 brwslnx02 kernel: [<c0108c83>] system_call [kernel] 0x33
(0xf7a7bfc0))
Jan 8 06:13:29 brwslnx02 kernel:
Jan 8 06:13:30 brwslnx02 kernel: EXT3 FS 2.4-0.9.18, 14 May 2002 on
sd(8,6), internal journal
Jan 8 06:13:30 brwslnx02 kernel: kjournald starting. Commit interval 5
seconds
Jan 8 06:13:30 brwslnx02 kernel: EXT3 FS 2.4-0.9.18, 14 May 2002 on
sd(8,17), internal journal
Jan 8 06:13:30 brwslnx02 kernel: EXT3-fs: mounted filesystem with ordered
data mode.
Jan 8 06:13:30 brwslnx02 kernel: kjournald starting. Commit interval 5
seconds
Jan 8 06:13:30 brwslnx02 kernel: EXT3 FS 2.4-0.9.18, 14 May 2002 on
sd(8,7), internal journal
Jan 8 06:13:30 brwslnx02 kernel: EXT3-fs: mounted filesystem with ordered
data mode.
Jan 8 06:13:30 brwslnx02 kernel: kjournald starting. Commit interval 5
seconds
Jan 8 06:13:30 brwslnx02 kernel: EXT3 FS 2.4-0.9.18, 14 May 2002 on
sd(8,3), internal journal
Jan 8 06:13:30 brwslnx02 kernel: EXT3-fs: mounted filesystem with ordered
data mode.
Jan 8 06:13:30 brwslnx02 kernel: kjournald starting. Commit interval 5
seconds
Jan 8 06:13:30 brwslnx02 kernel: EXT3 FS 2.4-0.9.18, 14 May 2002 on
sd(8,5), internal journal
Jan 8 06:13:30 brwslnx02 kernel: EXT3-fs: mounted filesystem with ordered
data mode.
Jan 8 06:13:30 brwslnx02 kernel: PCI: Enabling device 00:0f.2 (0000 ->
0002)
Jan 8 06:13:30 brwslnx02 kernel: usb-ohci.c: USB OHCI at membase
0xf8978000, IRQ 16
Jan 8 06:13:30 brwslnx02 kernel: usb-ohci.c: usb-00:0f.2, ServerWorks
OSB4/CSB5 OHCI USB Controller
Jan 8 06:13:30 brwslnx02 kernel: usb.c: new USB bus registered, assigned
bus number 1
Jan 8 06:13:30 brwslnx02 kernel: hub.c: USB hub found
Jan 8 06:13:30 brwslnx02 kernel: hub.c: 4 ports detected
Jan 8 06:13:30 brwslnx02 kernel: usb.c: USB disconnect on device 1
Jan 8 06:13:30 brwslnx02 kernel: usb.c: USB bus 1 deregistered
Jan 8 06:13:30 brwslnx02 kernel: eepro100.c:v1.09j-t 9/29/99 Donald Becker
http://www.scyld.com/network/eepro100.html
Jan 8 06:13:30 brwslnx02 kernel: eepro100.c: $Revision: 1.36 $ 2000/11/17
Modified by Andrey V. Savochkin <saw@saw.sw.com.sg> and others
Jan 8 06:13:30 brwslnx02 kernel: eth0: OEM i82557/i82558 10/100 Ethernet,
00:02:55:AC:08:5B, IRQ 42.
Jan 8 06:13:30 brwslnx02 kernel: Board assembly 352509-003, Physical
connectors present: RJ45
Jan 8 06:13:30 brwslnx02 kernel: Primary interface chip i82555 PHY #1.
Jan 8 06:13:30 brwslnx02 kernel: General self-test: passed.
Jan 8 06:13:31 brwslnx02 kernel: Serial sub-system self-test: passed.
Jan 8 06:13:31 brwslnx02 kernel: Internal registers self-test: passed.
Jan 8 06:13:31 brwslnx02 kernel: ROM checksum self-test: passed
(0x04f4518b).
Jan 8 06:13:31 brwslnx02 kernel: Intel(R) PRO/1000 Network Driver - version
4.3.2-k1 NAPI (020618)
Jan 8 06:13:31 brwslnx02 kernel: Copyright (c) 1999-2002 Intel Corporation.
Jan 8 06:13:31 brwslnx02 kernel: eth1: Intel(R) PRO/1000 Network Connection
Jan 8 06:13:31 brwslnx02 kernel: Installing knfsd (copyright (C) 1996
okir@monad.swb.de).
^ permalink raw reply
* Re: status of ntfs write-support in 2.4.20
From: Joshua M. Kwan @ 2003-01-08 17:36 UTC (permalink / raw)
To: folkert; +Cc: linux-kernel
In-Reply-To: <Pine.LNX.4.33.0301081507490.13070-100000@muur.intranet.vanheusden.com>
[-- Attachment #1: Type: text/plain, Size: 892 bytes --]
I believe it is still very unsafe. It *can* be done but you have to mess with
scandisk everytime you reboot back to windows...it's very very dirty and quite
hackish. I wouldn't think about risking data on an NTFS partition through the
limited NTFS driver in Linux 2.4 (even 2.5.)
And windows NT/2000/XP partitions are all the same NTFS anyway.
Regards
Josh
On Wed, Jan 08, 2003 at 03:08:54PM +0100, folkert@vanheusden.com wrote:
> Hi,
>
> What is the status of NTFS WRITE(!)-support in 2.4.20?
> Is there any kernel which can do safely writing to windows nt(! not 2000
> or xp) partitions?
>
>
> Folkert
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply
* Re: Status of linuxppc_2.5
From: Boris Bezlaj @ 2003-01-08 17:32 UTC (permalink / raw)
To: Pantelis Antoniou; +Cc: linuxppc-dev
In-Reply-To: <3E1BECD2.9060909@intracom.gr>
On Wed, Jan 08, 2003 at 11:18:10AM +0200, Pantelis Antoniou wrote:
> BTW, are there any gotchas, or anything
> I should pay attention moving
> from 2.4 -> 2.5?
AFAIK, you need the new module-init-tools for loading/unloading modules.
I see there is a little patch for swim3 driver. Do you have any problems
with swim3 driver in 2.4 kernel when writing to floppy? What is the status
in v2.5?
--
With best regards,
Boris B.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply
* Re: [PATCH] SCSI Core patches
From: Luben Tuikov @ 2003-01-08 17:33 UTC (permalink / raw)
To: Patrick Mansfield, linux-scsi
In-Reply-To: <20030107145300.A16954@beaverton.ibm.com>
Patrick Mansfield wrote:
>
> The hard part is making sure all of the references to scsi_device values
> are OK - that we correctly use and set the values across all of the
> scsi_devices that represent a single scsi device. It would be easy for a
> LLDD to screw this up, unless we have some sort of interface to get/set
> every value in scsi_device.
An LLDD cannot screw up. It will be fixed in the testing phase and
given that so many eyes will check it out before it is even considered.
Plus, vendors usually test LLDDs long before they are considered
into a test tree.
> Plus we have the overhead of redundant data for the fields: type,
> scsi_level, inquiry, vendor, etc.
Implementation issue.
> And the atomic device_active might have to be re-done with SMP locking.
Implementation issue.
> I'm arguing for a linked list of structs that hold the minimum data we
> need to use them as a path - much like a scsi_device with the redundant
> fields removed (and if needed it can also point to the actual
> scsi_device). And then plugging this data (or a pointer) into a scsi_cmnd
> for use by the LLDD.
This may be an easier approach, but a scsi_cmnd stands for SCSI command.
Its a good thing to have multipathing represented as an ADT (abstract
data type). Say something like a linked list of structs with
cost/weight member and a pointer to an actual low-level device (the infrastructure
will be more involved since multipathing will need to be notified
when a device goes away, but read further...). Now this ADT may be embeded
into a block device and char device structs -- i.e. highest hierarchy.
(The assumption is that there won't be a device which will present
a char and block interface at the same time.)
Now since this ADT is embeded into the block/char device, we do get
notification when it goes away. So this should be ok.
The effect is that when write(fd, buf, count) is done, somewhere along
the way *before* the actual physical device (ide,scsi,etc) is referenced
multipathing has already been accomplished. This preserves as much as possible
the current infrastructure of the kernel.
So when a low-level device (LLD) says that it cannot satisfy the request,
you *may* try another path.
In effect a low-level device *as seen from the multipath code* is the tuple
(PATH, DEVICE), and this is where a request is sent, i.e. to the tuple
(PATH, DEVICE). Where for each PATH, there can be exactly one DEVICE, since
a PATH describes a device (or access to it), but the opposite is not necessarily
true. I.e. for each DEVICE there can be zero/one to many PATHs.
> As long as we have an interface (function or macro), I'm not strongly
> opposed to the above. We can keep the scsi_allocate_device (in dire need
> of a new name), and just have it allocate and init (or not) any fields as
> needed, so there is only one place to change the init of the allocated
> scsi_cmnd.
The SCSI Core has a well-defined funtion. I'm not so sure that we
should muck it up with other well-defined functions, like multipathing.
> Adding a new interface to get the host/channel/target/lun is not so easy,
> but IMO worthwhile.
Changing all LLDD, SCSI Core, usb storage, message/fusion to use
cmd->device->{lun, id, channel, host} and scsi_get_command(),
scsi_put_command(), scsi_getset_command() was also not easy, but
doable.
There, you have a project. Please note, that this is only worthwhile
if multipathing is to go into SCSI Core.
It is *inevitable* that multipathing will be moved up into the
generic device char and block structs; sooner or later.
--
Luben
^ permalink raw reply
* [BUG - HRT patch] nanosleep returns 0 on failure
From: Fleischer, Julie N @ 2003-01-08 16:41 UTC (permalink / raw)
To: 'george@mvista.com'; +Cc: high-res-timers-discourse, linux-kernel
George -
In the latest 2.5.54-bk1 high-res-timers patches, it appears that
nanosleep() is returning 0 (success) and not setting errno when an rqtp
argument is sent that specifies a nsec value < 0 or >= 1000 million. In
this instance, the POSIX System Interfaces doc states that errno is supposed
to be set to EINVAL, and nanosleep should return -1.
In the 2.5.50 high-res-timers patches, behavior was as expected (i.e.,
returned -1 and set errno=EINVAL). Unfortunately, I haven't looked at any
patches since then to know exactly which patch stopped behaving as expected.
A plain 2.5.54-bk1 kernel also behaves as expected (returns -1, sets
errno=EINVAL).
The tests I am using to reproduce this issue are part of the POSIX Test
Suite at http://posixtest.sf.net under
posixtestsuite/conformance/interfaces/nanosleep. 5-1.c (sending -1 nsec),
6-1.c (sending multiple nsec values < 0 and >= 1,000 million), and 10000-1.c
(sending other nsec values < 0 and >= 1,000 million) are failing. I've
included 5-1.c below.
Additional information is below:
kernel used = 2.5.54-bk1
HRT patches applied =
hrtimers-core-2.5.54-bk1-1.0.patch
hrtimers-hrposix-2.5.54-bk1-1.0.patch
hrtimers-i386-2.5.54-bk1-1.0.patch
hrtimers-posix-2.5.54-bk1-1.0.patch
hrtimers-support-2.5.52-1.0.patch
Thanks.
- Julie Fleischer
----
test 5-1.c below
(Output was: nanosleep() did not return -1 on failure)
/*
* Copyright (c) 2002, Intel Corporation. All rights reserved.
* Created by: julie.n.fleischer REMOVE-THIS AT intel DOT com
* This file is licensed under the GPL license. For the full content
* of this license, see the COPYING file at the top level of this
* source tree.
* Test that nanosleep() returns -1 on failure.
* Simulate failure condition by sending -1 as the nsec to sleep for.
*/
#include <stdio.h>
#include <time.h>
#define PTS_PASS 0
#define PTS_FAIL 1
#define PTS_UNRESOLVED 2
int main(int argc, char *argv[])
{
struct timespec tssleepfor, tsstorage;
int sleepnsec = -1;
tssleepfor.tv_sec=0;
tssleepfor.tv_nsec=sleepnsec;
if (nanosleep(&tssleepfor, &tsstorage) == -1) {
printf("Test PASSED\n");
return PTS_PASS;
} else {
printf("nanosleep() did not return -1 on failure\n");
return PTS_FAIL;
}
printf("This code should not be executed.\n");
return PTS_UNRESOLVED;
}
**These views are not necessarily those of my employer.**
^ permalink raw reply
* Re: ipv6 stack seems to forget to send ACKs
From: Maciej Soltysiak @ 2003-01-08 17:43 UTC (permalink / raw)
To: Wichert Akkerman; +Cc: linux-kernel, netdev
In-Reply-To: <20030108170139.GL22951@wiggy.net>
> Actually, I don't follow this. How could any kind of traffic shaping
> result in my client not sending ACKs, which is what the tcpdump
> seems to indicate?
Well, i think i made a mistake, writing about routers dropping the
packets, it's not the case here, you are right.
Maciej
^ permalink raw reply
* Re: [parisc-linux] Re: do_page_fault() infinite loop running 2.4.20-pa18 #9 SMP
From: John David Anglin @ 2003-01-08 17:35 UTC (permalink / raw)
To: Matt.Foster; +Cc: parisc-linux
In-Reply-To: <003001c2b6f9$693c0bd0$211def9f@teatime>
> saturn:/usr/local/src# dmesg | more
> Linux version 2.4.20-pa18 (bame@dsl2) (gcc version 3.0.3) #1 Tue Jan 7
> 06:44:31
> MST 2003
> FP[0] enabled: Rev 1 Model 15
> The 32-bit Kernel has started...
> Determining PDC firmware type: System Map.
> [*SNIP*]
> Adding Swap: 249232k swap-space (priority -1)
> eth0: link ok.
>
> do_page_fault() pid=266 command='sendmail' type=6 address=0x00000003
>
> YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
> PSW: 00000000000001001111111100001111 Not tainted
> r00-03 00000000 400c78f0 40315e07 00000000
> r04-07 40326bec 40316230 00000010 00000001
> r08-11 00000000 402d3c98 0008df50 0008df54
> r12-15 00000076 00000073 00000006 00000000
> r16-19 000b3348 ffffffff 000bc248 40326bec
> r20-23 00000000 faf02a58 00000000 00000001
> r24-27 00000000 40316230 000f6dd0 000b3348
> r28-31 00000016 400e19dc faf029c0 40315e07
> sr0-3 00000000 0000016e 00000000 0000016e
> sr4-7 0000016e 0000016e 0000016e 0000016e
>
> IASQ: 0000016e 0000016e IAOQ: 00000003 00000007
The code has branched to address 0. If there is a core dump,
you might get some idea what happened by disassembling the
code just before and after $rp (0x40315e04). Branches to address
0 can occur if the code tries to call an undefined weak function
or if there is a problem with function pointers. I suspect an
indirect call since $r22 is 0 (this register contains the address
of the callee in an indireect call).
Page faults often occur when there is a problem in user code.
In the SMP case, certain page faults cause an infinite loop
in do_page_fault(). Do you see the above repeated indefinitely?
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)
^ permalink raw reply
* Re: status of ntfs write-support in 2.4.20
From: Pawel Kot @ 2003-01-08 17:44 UTC (permalink / raw)
To: Joshua M. Kwan; +Cc: folkert, linux-kernel
In-Reply-To: <20030108173645.GA27118@kanoe.ludicrus.net>
On Wed, 8 Jan 2003, Joshua M. Kwan wrote:
> On Wed, Jan 08, 2003 at 03:08:54PM +0100, folkert@vanheusden.com wrote:
> > Hi,
> >
> > What is the status of NTFS WRITE(!)-support in 2.4.20?
> > Is there any kernel which can do safely writing to windows nt(! not 2000
> > or xp) partitions?
>
> I believe it is still very unsafe. It *can* be done but you have to mess with
> scandisk everytime you reboot back to windows...it's very very dirty and quite
> hackish. I wouldn't think about risking data on an NTFS partition through the
> limited NTFS driver in Linux 2.4 (even 2.5.)
Well, the ntfs driver from the 2.4.20 vanilla kernel has really dangerous
write support for the ntfs partitions. It is strongly discouraged to use
it.
You can use though the backport driver from the 2.5 kernel series (aka
ntfs-tng). It allows you to overwrite the files using mmap() and write().
So, neither size changes, nor attribute changes. You'll find mode detailes
along with the driver itself at http://linux-ntfs.sf.net/.
> And windows NT/2000/XP partitions are all the same NTFS anyway.
Not really. See http://linux-ntfs.sourceforge.net/info/ntfs.html#1.4
pkot
--
mailto:pkot@linuxnews.pl :: mailto:pkot@slackware.pl
http://kt.linuxnews.pl/ :: Kernel Traffic po polsku
^ permalink raw reply
* Re: [apache-modules] Best HTML Parser
From: Charles Reitzel @ 2003-01-08 17:53 UTC (permalink / raw)
To: apache-modules
Cc: apache-modules, DCOM, Linux Kernel, modssl-users, netfilter,
TEAMICE
In-Reply-To: <5.2.0.9.0.20030108124223.009f3e00@mail.SoftHome.net>
I am partial to HTML Tidy for a few reasons:
1) cross-platform, reentrant C library
2) very forgiving of sloppy, malformed markup
3) produces clean markup - XHTML if requested
4) C++, Perl, Pascal, COM and .NET bindings available,
others easily done with SWIG
But I must admit, as one of the primary developers, I am probably
biased. But if you need to get your markup cleaned up so that you can
apply XML tools to it, it is probably the best game in town.
For more info: http://tidy.sourceforge.net/
take it easy,
Charlie
At 12:43 PM 1/8/2003 +0530, Blesson Paul wrote:
>Hi all
> Which is the Best HTML Parser in C/C++
>
>regards
>Blesson Paul
^ permalink raw reply
* Re: USB CF reader reboots PC
From: Eli Carter @ 2003-01-08 17:50 UTC (permalink / raw)
To: Murray J. Root; +Cc: linux-kernel
In-Reply-To: <20030108173356.GA1189@Master.Wizards>
Murray J. Root wrote:
> Ooops - kernel 2.5.5[234]
>
> On Wed, Jan 08, 2003 at 11:51:30AM -0500, Murray J. Root wrote:
>
>>ASUS P4S533 (SiS645DX chipset)
>>P4 2GHz
>>1G PC2700 RAM
>>SanDisk SDDR-77 ImageMate Dual Card Reader (using only CF cards)
>>
>>----------------------------
>>devfs compiled in to kernel, devfs=nomount in lilo.conf
>>
>>Insert CF card. mount it. cd to it, do reads and/or writes
>>umount card. remove card.
>>insert a different card (does not happen if the same card is used)
>>mount it. system reboots. logs are corrupted
>>
>>Doesn't happen every time for read - sometimes I can read 2 or 3 cards first
>>Happens every time for write - if I write to a card then changing cards
>>causes a reboot
>>
[snip]
Somewhat similar vein, but a different set of symptoms, I've seen a
RedHat box not see that the CF card changed...
(USB SanDisk CF & SD reader, also using only CF cards.)
insert 128MB CF card.
everything is ok.
remove 128MB CF card, still see 128MB partition
insert 256MB CF card.
see 128MB partition.
(based on /proc/partitions)
I've not followed this up to figure out why yet.
You might check that situation to see if yours is related at all.
Eli
--------------------. "If it ain't broke now,
Eli Carter \ it will be soon." -- crypto-gram
eli.carter(a)inet.com `-------------------------------------------------
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.