* Re: Linux 2.4.24-rc1
From: Mihai RUSU @ 2004-01-05 13:13 UTC (permalink / raw)
To: linux-kernel
In-Reply-To: <Pine.LNX.4.58L.0401051003341.1188@logos.cnet>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
On Mon, 5 Jan 2004, Marcelo Tosatti wrote:
>
>
> This release fixes a few critical problems in 2.4.23, including fixes
> for two security bugs.
>
> Upgrade is recommended.
Indeed!
I have noticed that 2.6.0 seems to have the same codes for mremap.c,
shouldnt 2.6.1 merge the following patch before release ?
- --- linux-2.4.23/mm/mremap.c 2003-08-25 11:44:44.000000000 +0000
+++ linux-2.4.24-rc1/mm/mremap.c 2004-01-04 20:52:19.000000000 +0000
@@ -241,6 +241,13 @@
if (new_len > TASK_SIZE || new_addr > TASK_SIZE - new_len)
goto out;
+ /*
+ * Allow new_len == 0 only if new_addr == addr
+ * to preserve truncation in place (that was working
+ * safe and some app may depend on it).
+ */
+ if (unlikely(!new_len && new_addr != addr))
+ goto out;
/* Check if the location we're moving into overlaps the
* old location at all, and fail if it does.
PS: I have also downloaded 2.6.1 bk6 snapshot patch and I have not seen
any diff for mremap.c.
- --
Mihai RUSU Email: dizzy@roedu.net
GPG : http://dizzy.roedu.net/dizzy-gpg.txt WWW: http://dizzy.roedu.net
"Linux is obsolete" -- AST
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQE/+WMJPZzOzrZY/1QRAhv0AKDkgqimVpAMwBWavfKN+WjEU8SF+gCdHUiC
XBbcRzJA5zfsUboMK0N5jKs=
=eBik
-----END PGP SIGNATURE-----
^ permalink raw reply
* Re: [parisc-linux] Sun JVM on linux HPPA
From: Randolph Chung @ 2004-01-05 13:14 UTC (permalink / raw)
To: Michel Weynants; +Cc: parisc-linux
In-Reply-To: <1073308114.2718.7.camel@dev3>
> However, I wonder if a Java virtual machine has been ported for that
> environment. I checked several sites but did not found any info,
> sentence, reference,... of a JSDK1.4 for linux on HPPA (well, thousands
> references for JSDK on linux on intel).
>
> Do you know if such version exist and where it could be found?
The Sun JDK is not open-source so we cannot port it to hppa-linux. There
are several efforts under way to get other JVMs to work on hppa. SableVM
is close to working. kaffe can probably also be made to work with some
effort.
Search the mail archives for more info; this has been asked several
times in the past.
randolph
--
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/
^ permalink raw reply
* Re: [netfilter-core] asymptotic complexity when creating new chains and rules
From: Andre Uratsuka Manoel @ 2004-01-05 13:11 UTC (permalink / raw)
To: Rusty Russell; +Cc: Stefan Winter, netfilter-devel@lists.netfilter.org
In-Reply-To: <20040104043038.16CC32C2C1@lists.samba.org>
On Sun, 4 Jan 2004, Rusty Russell wrote:
> In message <200401031636.11291.mail@stefan-winter.de> you write:
> > But, if you iterate this process a hundred times (with increasing "N" in the
> > chain name, so that you get 200 chains with 200*62 rules altogether), adding
> > the chains slows down with every new chain (first chain: 20 ms, all chains
> > together 150 SECONDS). This seems to imply that adding a chain (or rule) is
> > of complexity O(n) with n being the number of rules/chains already in the
> > table, where one would expect O(1). Is that right?
>
> Yes. In particular, the userspace is theoretically O(1), in that if
> you read the chains once, kept that copy, and every time updated it
> and committed it to the kernel, that would be O(1). But most uses of
> libiptc do "read all rules, insert new one, repeat". Secondly, the
> kernel isn't O(1): it checks for loops, and actually calls all the
> rules' matches and targets to check they like where they are.
>
> This is why Harald is working on pkttables, which abandons the whole
> "flip the whole table into the kernel approach".
Yeah, userspace should be O(1), but it is O(n). So,
iptables-restore is currently O(n^2), or better put, it is Theta(n^2).
I resumed working on that (again) last week, based on the cvs
version of iptables, but I later noticed that on iptables-1.2.9 there is a
directory called libiptc2. I have a lot of work done on iptables cvs. What
is the status of libiptc2? I would like to keep on working on current line
of work (libiptc2 seems to use the same approach as I do).
My personal take is that it is more or less easy to make iptables
more well behaved. The major problems are fallthrough rules (that have to
be identified, but after that, they are dealt with trivially) and the
different ways targets are expressed in different places (by offsets or by
names). After dealing with those, most of the complexity of the libiptc
package is gone. No more correct_verdict, alloc_handle, target_name,
entry2offset, etc, etc, etc. Appends become O(log n). With a hash table,
appends may become O(1). I think I can get something out this week.
Happy new year to all,
Andre
^ permalink raw reply
* [parisc-linux] Sun JVM on linux HPPA
From: Michel Weynants @ 2004-01-05 13:08 UTC (permalink / raw)
To: parisc-linux
Hi,
I just received an 'old' (just 10 years) 755 and successfully installed
Linux on it and all runs fine (thanks to all for that porting).
However, I wonder if a Java virtual machine has been ported for that
environment. I checked several sites but did not found any info,
sentence, reference,... of a JSDK1.4 for linux on HPPA (well, thousands
references for JSDK on linux on intel).
Do you know if such version exist and where it could be found?
Many thanks in advance,
Cheers,
Michel
^ permalink raw reply
* Deadlock in sungem/ip_auto_config/linkwatch
From: Michal Ostrowski @ 2004-01-05 13:07 UTC (permalink / raw)
To: netdev
[-- Attachment #1: Type: text/plain, Size: 849 bytes --]
I believe I've found a potential deadlock condition.
It occurs when we make the following sequence of calls:
ip_auto_config
ic_open_devs
dev_change_flags
dev_open
gem_open
flush_scheduled_work
ic_open_devs grabs rtnl_sem with an rtnl_shlock() call.
The sungem driver at some point calls gem_init_one, which calls
netif_carrier_*, which in turn calls schedule_work (linkwatch_event).
linkwatch_event in turn needs rtnl_sem.
If we enter the call sequence above and linkwatch_event is still
pending, we will deadlock since flush_scheduled_work will wait for
completion of linkwatch_event, which is blocked since it cannot get
rtnl_sem.
In general when can one call flush_scheduled_work? It seems that one
can't unless you know your callers aren't holding any locks.
--
Michal Ostrowski <mostrows@watson.ibm.com>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply
* usb-storage && iRIVER flash player problem
From: Javier Marcet @ 2004-01-05 12:59 UTC (permalink / raw)
To: linux-kernel; +Cc: mdharm-usb, usb-storage, linux-usb-users
[-- Attachment #1: Type: text/plain, Size: 985 bytes --]
I'm trying to get an iRIVER iFP-599T aduio player, with the Universal
Mass Storage firmware.
I've tried with 2.6.1-rc1-mm1 & 2.4.22.
The device is seen, but there is no way to mount it, nor re-partition
the thing.
I have it working from Windows and MacOS (I tried once on this). At
first look, it seems there is only one whole partition, but fdisk
reports 4 mangled ones, and some users who said they got it to work
under 2.4, explain that the mountable vfat partition under linux is the
fourth one (/dev/sda4 on my system).
There is no way here. I've recompiled with USBm usb-storage && scsi
debugging enabled and not as modules, directly into the kernel. For your
info I'm using udev.
See the attached dmesg, and some info from /proc, if there is anything
else which could come in handy to find where the problem might be,
please ask :)
P.S Other than the linux-kernel, please cross-post to my e-mail address
since I'm not subscribed.
--
Javier Marcet <javier@marcet.info>
[-- Attachment #2: dmesg --]
[-- Type: text/plain, Size: 15397 bytes --]
cted: Hauppauge WinTV [card=10], PCI subsystem ID is 0070:13eb
bttv0: using: Hauppauge (bt878) [card=10,autodetected]
bttv0: Hauppauge/Voodoo msp34xx: reset line init [5]
bttv0: Hauppauge eeprom: model=44354, tuner=Temic 4009FR5 (20), radio=yes
bttv0: using tuner=20
bttv0: i2c: checking for MSP34xx @ 0x80... found
msp34xx: init: chip=MSP3415D-B3 +nicam +simple
msp3410: daemon started
registering 0-0040
bttv0: i2c: checking for TDA9875 @ 0xb0... not found
bttv0: i2c: checking for TDA7432 @ 0x8a... not found
tvaudio: TV audio decoder + audio/video mux driver
tvaudio: known chips: tda9840,tda9873h,tda9874h/a,tda9850,tda9855,tea6300,tea6420,tda8425,pic16c54 (PV951),ta8874z
tuner: chip found @ 0xc2
tuner: type set to 20 (Temic PAL_BG (4009 FR5) or PAL_I (4069 FR5))
registering 0-0061
bttv0: registered device video0
bttv0: registered device vbi0
bttv0: registered device radio0
bttv0: PLL: 28636363 => 35468950 .. ok
registering 1-002d
registering 1-0049
registering 1-0048
found reiserfs format "3.6" with standard journal
Reiserfs journal params: device hda8, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
reiserfs: checking transaction log (hda8) for (hda8)
Using r5 hash to sort names
found reiserfs format "3.6" with standard journal
Reiserfs journal params: device hda9, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
reiserfs: checking transaction log (hda9) for (hda9)
b44: eth0: Link is down.
Using r5 hash to sort names
found reiserfs format "3.6" with standard journal
Reiserfs journal params: device hda10, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
reiserfs: checking transaction log (hda10) for (hda10)
Using r5 hash to sort names
found reiserfs format "3.6" with standard journal
Reiserfs journal params: device hda11, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
reiserfs: checking transaction log (hda11) for (hda11)
Using r5 hash to sort names
found reiserfs format "3.6" with standard journal
b44: eth0: Link is up at 100 Mbps, full duplex.
b44: eth0: Flow control is on for TX and on for RX.
Reiserfs journal params: device hda13, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30
reiserfs: checking transaction log (hda13) for (hda13)
Using r5 hash to sort names
PCI: Found IRQ 4 for device 0000:00:11.5
PCI: Setting latency timer of device 0000:00:11.5 to 64
tvmixer: MSP3415D-B3 (bt878 #0 [sw]) registered with minor 16
btaudio: driver version 0.7 loaded [digital+analog]
PCI: Enabling device 0000:00:0c.1 (0004 -> 0006)
PCI: Found IRQ 11 for device 0000:00:0c.1
PCI: Sharing IRQ 11 with 0000:00:0c.0
btaudio: Bt878 (rev 17) at 00:0c.1, irq: 11, latency: 64, mmio: 0xd6800000
btaudio: using card config "default"
btaudio: registered device dsp2 [digital]
btaudio: registered device dsp3 [analog]
btaudio: registered device mixer2
Disabled Privacy Extensions on device c0377a40(lo)
eth0: no IPv6 routers present
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
nfs warning: mount version older than kernel
request_module: failed /sbin/modprobe -- char-major-226-0. error = 256
[drm] Initialized radeon 1.9.0 20020828 on minor 0
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0.
agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode
agpgart: Putting AGP V2 device at 0000:01:00.1 into 4x mode
[drm] Loading R200 Microcode
PCI: Found IRQ 11 for device 0000:01:00.0
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
atkbd.c: Unknown key released (translated set 2, code 0x7a on isa0060/serio0).
ehci_hcd 0000:00:10.3: GetStatus port 6 status 001803 POWER sig=j CSC CONNECT
hub 1-0:1.0: port 6, status 501, change 1, 480 Mb/s
hub 1-0:1.0: debounce: port 6: delay 100ms stable 4 status 0x501
ehci_hcd 0000:00:10.3: port 6 full speed --> companion
ehci_hcd 0000:00:10.3: GetStatus port 6 status 003801 POWER OWNER sig=j CONNECT
drivers/usb/host/uhci-hcd.c: 9800: wakeup_hc
hub 4-0:1.0: port 2, status 101, change 1, 12 Mb/s
hub 4-0:1.0: debounce: port 2: delay 100ms stable 4 status 0x101
hub 4-0:1.0: new USB device on port 2, assigned address 2
usb 4-2: new device strings: Mfr=0, Product=0, SerialNumber=0
drivers/usb/core/usb.c: usb_hotplug
usb 4-2: registering 4-2:1.0 (config #1, interface 0)
drivers/usb/core/usb.c: usb_hotplug
usb-storage 4-2:1.0: usb_probe_interface
usb-storage 4-2:1.0: usb_probe_interface - got id
usb-storage: USB Mass Storage device detected
usb-storage: act_altsetting is 0, id_index is 86
usb-storage: -- associate_dev
usb-storage: Transport: Bulk
usb-storage: Protocol: Transparent SCSI
usb-storage: Endpoints: In: 0xdd291c94 Out: 0xdd291c80 Int: 0x00000000 (Period 0)
usb-storage: usb_stor_control_msg: rq=fe rqtype=a1 value=0000 index=00 len=1
usb-storage: GetMaxLUN command result is -32, data is 0
usb-storage: *** thread sleeping.
scsi2 : SCSI emulation for USB Mass Storage devices
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command INQUIRY (6 bytes)
usb-storage: 12 00 00 00 24 00
usb-storage: Bulk Command S 0x43425355 T 0x41 L 36 F 128 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_buf: xfer 36 bytes
usb-storage: Status code 0; transferred 36/36
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x41 R 0 Stat 0x0
usb-storage: Fixing INQUIRY data to show SCSI rev 2 - was 0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command INQUIRY (6 bytes)
usb-storage: 12 00 00 00 7a 00
usb-storage: Bulk Command S 0x43425355 T 0x42 L 122 F 128 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_buf: xfer 122 bytes
usb-storage: Status code 0; transferred 122/122
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x42 R 0 Stat 0x0
usb-storage: Fixing INQUIRY data to show SCSI rev 2 - was 0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
Vendor: iRiver Model: iFP Mass Driver Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 02
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command TEST_UNIT_READY (6 bytes)
usb-storage: 00 00 00 00 00 00
usb-storage: Bulk Command S 0x43425355 T 0x43 L 0 F 0 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x43 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command READ_CAPACITY (10 bytes)
usb-storage: 25 00 00 00 00 00 00 00 00 00
usb-storage: Bulk Command S 0x43425355 T 0x44 L 8 F 128 Trg 0 LUN 0 CL 10
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_buf: xfer 8 bytes
usb-storage: Status code 0; transferred 8/8
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x44 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
SCSI device sda: 2048000 512-byte hdwr sectors (1049 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command TEST_UNIT_READY (6 bytes)
usb-storage: 00 00 00 00 00 00
usb-storage: Bulk Command S 0x43425355 T 0x45 L 0 F 0 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x45 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command ALLOW_MEDIUM_REMOVAL (6 bytes)
usb-storage: 1e 00 00 00 01 00
usb-storage: Bulk Command S 0x43425355 T 0x46 L 0 F 0 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x46 R 0 Stat 0x1
usb-storage: -- transport indicates command failure
usb-storage: Issuing auto-REQUEST_SENSE
usb-storage: Bulk Command S 0x43425355 T 0x80000046 L 18 F 128 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_buf: xfer 18 bytes
usb-storage: Status code 0; transferred 18/18
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x80000046 R 0 Stat 0x0
usb-storage: -- Result from auto-sense is 0
usb-storage: -- code: 0x70, key: 0x6, ASC: 0x29, ASCQ: 0x0
usb-storage: Unit Attention: Power on, reset, or bus device reset occurred
usb-storage: scsi cmd done, result=0x2
usb-storage: *** thread sleeping.
sda:<3>Buffer I/O error on device sda, logical block 0
Buffer I/O error on device sda, logical block 0
unable to read partition table
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command ALLOW_MEDIUM_REMOVAL (6 bytes)
usb-storage: 1e 00 00 00 00 00
usb-storage: Bulk Command S 0x43425355 T 0x47 L 0 F 0 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x47 R 0 Stat 0x1
usb-storage: -- transport indicates command failure
usb-storage: Issuing auto-REQUEST_SENSE
usb-storage: Bulk Command S 0x43425355 T 0x80000047 L 18 F 128 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_buf: xfer 18 bytes
usb-storage: Status code 0; transferred 18/18
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x80000047 R 0 Stat 0x0
usb-storage: -- Result from auto-sense is 0
usb-storage: -- code: 0x70, key: 0x6, ASC: 0x29, ASCQ: 0x0
usb-storage: Unit Attention: Power on, reset, or bus device reset occurred
usb-storage: scsi cmd done, result=0x2
usb-storage: *** thread sleeping.
Attached scsi removable disk sda at scsi2, channel 0, id 0, lun 0
Attached scsi generic sg0 at scsi2, channel 0, id 0, lun 0, type 0
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (1:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (2:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (3:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (4:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (5:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (6:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Bad target number (7:0)
usb-storage: scsi cmd done, result=0x40000
usb-storage: *** thread sleeping.
WARNING: USB Mass Storage data integrity not assured
USB Mass Storage device found at 2
[-- Attachment #3: dmesg2 --]
[-- Type: text/plain, Size: 15355 bytes --]
e 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x12e R 0 Stat 0x1
usb-storage: -- transport indicates command failure
usb-storage: Issuing auto-REQUEST_SENSE
usb-storage: Bulk Command S 0x43425355 T 0x8000012e L 18 F 128 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_buf: xfer 18 bytes
usb-storage: Status code 0; transferred 18/18
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x8000012e R 0 Stat 0x0
usb-storage: -- Result from auto-sense is 0
usb-storage: -- code: 0x70, key: 0x6, ASC: 0x29, ASCQ: 0x0
usb-storage: Unit Attention: Power on, reset, or bus device reset occurred
usb-storage: scsi cmd done, result=0x2
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command TEST_UNIT_READY (6 bytes)
usb-storage: 00 00 00 00 00 00
usb-storage: Bulk Command S 0x43425355 T 0x12f L 0 F 0 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x12f R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command TEST_UNIT_READY (6 bytes)
usb-storage: 00 00 00 00 00 00
usb-storage: Bulk Command S 0x43425355 T 0x130 L 0 F 0 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x130 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command READ_CAPACITY (10 bytes)
usb-storage: 25 00 00 00 00 00 00 00 00 00
usb-storage: Bulk Command S 0x43425355 T 0x131 L 8 F 128 Trg 0 LUN 0 CL 10
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_buf: xfer 8 bytes
usb-storage: Status code 0; transferred 8/8
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x131 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
SCSI device sda: 2048000 512-byte hdwr sectors (1049 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command ALLOW_MEDIUM_REMOVAL (6 bytes)
usb-storage: 1e 00 00 00 01 00
usb-storage: Bulk Command S 0x43425355 T 0x132 L 0 F 0 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x132 R 0 Stat 0x1
usb-storage: -- transport indicates command failure
usb-storage: Issuing auto-REQUEST_SENSE
usb-storage: Bulk Command S 0x43425355 T 0x80000132 L 18 F 128 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_buf: xfer 18 bytes
usb-storage: Status code 0; transferred 18/18
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x80000132 R 0 Stat 0x0
usb-storage: -- Result from auto-sense is 0
usb-storage: -- code: 0x70, key: 0x6, ASC: 0x29, ASCQ: 0x0
usb-storage: Unit Attention: Power on, reset, or bus device reset occurred
usb-storage: scsi cmd done, result=0x2
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command TEST_UNIT_READY (6 bytes)
usb-storage: 00 00 00 00 00 00
usb-storage: Bulk Command S 0x43425355 T 0x133 L 0 F 0 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x133 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command READ_CAPACITY (10 bytes)
usb-storage: 25 00 00 00 00 00 00 00 00 00
usb-storage: Bulk Command S 0x43425355 T 0x134 L 8 F 128 Trg 0 LUN 0 CL 10
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_buf: xfer 8 bytes
usb-storage: Status code 0; transferred 8/8
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x134 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
SCSI device sda: 2048000 512-byte hdwr sectors (1049 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
sda:<3>Buffer I/O error on device sda, logical block 0
Buffer I/O error on device sda, logical block 0
unable to read partition table
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command TEST_UNIT_READY (6 bytes)
usb-storage: 00 00 00 00 00 00
usb-storage: Bulk Command S 0x43425355 T 0x135 L 0 F 0 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x135 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command TEST_UNIT_READY (6 bytes)
usb-storage: 00 00 00 00 00 00
usb-storage: Bulk Command S 0x43425355 T 0x136 L 0 F 0 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x136 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command READ_CAPACITY (10 bytes)
usb-storage: 25 00 00 00 00 00 00 00 00 00
usb-storage: Bulk Command S 0x43425355 T 0x137 L 8 F 128 Trg 0 LUN 0 CL 10
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_buf: xfer 8 bytes
usb-storage: Status code 0; transferred 8/8
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x137 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
SCSI device sda: 2048000 512-byte hdwr sectors (1049 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command TEST_UNIT_READY (6 bytes)
usb-storage: 00 00 00 00 00 00
usb-storage: Bulk Command S 0x43425355 T 0x138 L 0 F 0 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x138 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command READ_CAPACITY (10 bytes)
usb-storage: 25 00 00 00 00 00 00 00 00 00
usb-storage: Bulk Command S 0x43425355 T 0x139 L 8 F 128 Trg 0 LUN 0 CL 10
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_buf: xfer 8 bytes
usb-storage: Status code 0; transferred 8/8
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x139 R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
SCSI device sda: 2048000 512-byte hdwr sectors (1049 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
sda:<7>usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command READ_10 (10 bytes)
usb-storage: 28 00 00 00 00 00 00 00 08 00
usb-storage: Bulk Command S 0x43425355 T 0x13a L 4096 F 128 Trg 0 LUN 0 CL 10
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_sglist: xfer 4096 bytes, 1 entries
usb-storage: Status code 0; transferred 4096/4096
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x13a R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
sda1 sda2 sda3 sda4
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command READ_10 (10 bytes)
usb-storage: 28 00 00 00 00 08 00 00 78 00
usb-storage: Bulk Command S 0x43425355 T 0x13b L 61440 F 128 Trg 0 LUN 0 CL 10
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_sglist: xfer 61440 bytes, 15 entries
usb-storage: Status code 0; transferred 61440/61440
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x13b R 0 Stat 0x0
usb-storage: scsi cmd done, result=0x0
usb-storage: *** thread sleeping.
usb-storage: queuecommand called
usb-storage: *** thread awakened.
usb-storage: Command ALLOW_MEDIUM_REMOVAL (6 bytes)
usb-storage: 1e 00 00 00 00 00
usb-storage: Bulk Command S 0x43425355 T 0x13c L 0 F 0 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x13c R 0 Stat 0x1
usb-storage: -- transport indicates command failure
usb-storage: Issuing auto-REQUEST_SENSE
usb-storage: Bulk Command S 0x43425355 T 0x8000013c L 18 F 128 Trg 0 LUN 0 CL 6
usb-storage: usb_stor_bulk_transfer_buf: xfer 31 bytes
usb-storage: Status code 0; transferred 31/31
usb-storage: -- transfer complete
usb-storage: Bulk command transfer result=0
usb-storage: usb_stor_bulk_transfer_buf: xfer 18 bytes
usb-storage: Status code 0; transferred 18/18
usb-storage: -- transfer complete
usb-storage: Bulk data transfer result 0x0
usb-storage: Attempting to get CSW...
usb-storage: usb_stor_bulk_transfer_buf: xfer 13 bytes
usb-storage: Status code 0; transferred 13/13
usb-storage: -- transfer complete
usb-storage: Bulk status result = 0
usb-storage: Bulk Status S 0x53425355 T 0x8000013c R 0 Stat 0x0
usb-storage: -- Result from auto-sense is 0
usb-storage: -- code: 0x70, key: 0x6, ASC: 0x29, ASCQ: 0x0
usb-storage: Unit Attention: Power on, reset, or bus device reset occurred
usb-storage: scsi cmd done, result=0x2
usb-storage: *** thread sleeping.
[-- Attachment #4: proc_bus_usb_devices --]
[-- Type: text/plain, Size: 2259 bytes --]
T: Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.1-rc1-mm1 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:10.2
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=04 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=4102 ProdID=1105 Rev= 1.00
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E: Ad=03(O) Atr=02(Bulk) MxPS= 64 Ivl=0ms
E: Ad=83(I) Atr=02(Bulk) MxPS= 64 Ivl=0ms
T: Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.1-rc1-mm1 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:10.1
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=12 MxCh= 2
B: Alloc= 0/900 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 1.10 Cls=09(hub ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.1-rc1-mm1 uhci_hcd
S: Product=UHCI Host Controller
S: SerialNumber=0000:00:10.0
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=255ms
T: Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#= 1 Spd=480 MxCh= 6
B: Alloc= 0/800 us ( 0%), #Int= 0, #Iso= 0
D: Ver= 2.00 Cls=09(hub ) Sub=00 Prot=01 MxPS= 8 #Cfgs= 1
P: Vendor=0000 ProdID=0000 Rev= 2.06
S: Manufacturer=Linux 2.6.1-rc1-mm1 ehci_hcd
S: Product=EHCI Host Controller
S: SerialNumber=0000:00:10.3
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr= 0mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=09(hub ) Sub=00 Prot=00 Driver=hub
E: Ad=81(I) Atr=03(Int.) MxPS= 2 Ivl=256ms
[-- Attachment #5: proc_scsi_scsi --]
[-- Type: text/plain, Size: 176 bytes --]
Attached devices:
Host: scsi2 Channel: 00 Id: 00 Lun: 00
Vendor: iRiver Model: iFP Mass Driver Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 02
[-- Attachment #6: proc_scsi_usb-storage_2 --]
[-- Type: text/plain, Size: 160 bytes --]
Host scsi2: usb-storage
Vendor: Unknown
Product: Unknown
Serial Number: None
Protocol: Transparent SCSI
Transport: Bulk
Quirks:
[-- Attachment #7: fdisk_list_devices --]
[-- Type: text/plain, Size: 1563 bytes --]
Disk /dev/sda: 1048 MB, 1048576000 bytes
33 heads, 61 sectors/track, 1017 cylinders
Units = cylinders of 2013 * 512 = 1030656 bytes
Device Boot Start End Blocks Id System
/dev/sda1 ? 386556 953625 570754815+ 72 Unknown
Partition 1 has different physical/logical beginnings (non-Linux?):
phys=(357, 116, 40) logical=(386555, 11, 23)
Partition 1 has different physical/logical endings:
phys=(357, 32, 45) logical=(953624, 6, 61)
Partition 1 does not end on cylinder boundary.
/dev/sda2 ? 83801 1045563 968014120 65 Novell Netware 386
Partition 2 has different physical/logical beginnings (non-Linux?):
phys=(288, 115, 43) logical=(83800, 2, 1)
Partition 2 has different physical/logical endings:
phys=(367, 114, 50) logical=(1045562, 23, 53)
Partition 2 does not end on cylinder boundary.
/dev/sda3 ? 928903 1890666 968014096 79 Unknown
Partition 3 has different physical/logical beginnings (non-Linux?):
phys=(366, 32, 33) logical=(928902, 28, 32)
Partition 3 has different physical/logical endings:
phys=(357, 32, 43) logical=(1890665, 16, 36)
Partition 3 does not end on cylinder boundary.
/dev/sda4 ? 1 1806869 1818613248 d Unknown
Partition 4 has different physical/logical beginnings (non-Linux?):
phys=(372, 97, 50) logical=(0, 0, 1)
Partition 4 has different physical/logical endings:
phys=(0, 10, 0) logical=(1806868, 19, 53)
Partition 4 does not end on cylinder boundary.
Partition table entries are not in disk order
^ permalink raw reply
* Re: forcedeth unknown events 0x21
From: madis @ 2004-01-05 12:58 UTC (permalink / raw)
To: Carl-Daniel Hailfinger; +Cc: Madis Janson, netdev
In-Reply-To: <3FE6678B.5070006@gmx.net>
On Mon, 22 Dec 2003, Carl-Daniel Hailfinger wrote:
> Madis Janson wrote:
> > When trying forcedeth_2_6_patch_v19.txt, i got the following message
> > fastly repeating after ifup eth0:
> >
> > "eth0: received irq with unknown events 0x21. Please report"
> >
> > and it didn't work eighter (ifup just stalled).
> >
> > kernel:
> >
> > 2.6.0 release + patches:
> > http://www.held.org.il/patches/patch-lirc-2.6.0-test9-oh.diff.bz2
> > http://www.hailfinger.org/carldani/linux/patches/forcedeth/forcedeth_2_6_patch_v19.txt
>
> Please try the attached patch on top of it and report back if it works.
>
the unknown events message disappeared,
but the network did not start to work...
========================================================
+ if (events & (NVREG_IRQ_RX_ERR)) {
+ dprintk(KERN_DEBUG "%s: received irq with events
0x%x.
Probably RX fail.\n",
+ dev->name, events);
here were '}' missing.
--
mzz
^ permalink raw reply
* [U-Boot-Users] Compatibility - Cogent CSB335 =?unknown-8bit?b?77+9?= ARM720T on Sharp LH79520
From: Himansu Doshi @ 2004-01-05 12:47 UTC (permalink / raw)
To: u-boot
Hi all,
Can U-boot be configured for the cogent csb335 board which has the ARM720T
core integrated on Sharp LH79520?
Thanks
_________________________________________________________________
Games, MMS cards, ringtones. Operator logos, picture messages & more.
http://server1.msn.co.in/sp03/mobilesms/ Jazz up your mobile!
^ permalink raw reply
* Re: Linux 2.4.24-rc1
From: Erik Andersen @ 2004-01-05 12:46 UTC (permalink / raw)
To: Marcelo Tosatti; +Cc: linux-kernel
In-Reply-To: <Pine.LNX.4.58L.0401051003341.1188@logos.cnet>
On Mon Jan 05, 2004 at 10:18:35AM -0200, Marcelo Tosatti wrote:
>
>
> This release fixes a few critical problems in 2.4.23, including fixes
> for two security bugs.
>
> Upgrade is recommended.
How about also fixing the rt_sigprocmask syscall?
http://www.ussg.iu.edu/hypermail/linux/kernel/0312.3/1247.html
-Erik
--
Erik B. Andersen http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--
^ permalink raw reply
* [LARTC] Cisco
From: Eddie @ 2004-01-05 12:46 UTC (permalink / raw)
To: lartc
Hi I know this does not have anything to do with the list
But I'm looking for books,doc's or anything on these Cisco exams
I looking to do them this year.Please
CCNP Exams &
Recommended
Training
Required Exam(s)
Recommended Training
642-801 BSCI
Building Scalable Cisco
Internetworks v2.0 (BSCI)
642-811 BCMSN
Building Cisco Multilayer Switched
Networks v2.0 (BCMSN)
642-821 BCRAN
Building Cisco Remote Access
Networks v2.0 (BCRAN)
642-831 CIT
Cisco Internetwork Troubleshooting
Support v5.0 (CIT)
Thanks
Eddie
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
^ permalink raw reply
* Re: Call for testing: patch-o-matic-ng
From: Jozsef Kadlecsik @ 2004-01-05 12:45 UTC (permalink / raw)
To: Herve Eychenne; +Cc: Harald Welte, Netfilter Development Mailinglist
In-Reply-To: <20040105115533.GK1133@eychenne.org>
Hi Herve,
On Mon, 5 Jan 2004, Herve Eychenne wrote:
> I think the convention of Debian Packages files with a line like
> Depends: zope, python2.1-popy (>= 2.0.8), python2.1-popy (<< 2.0.9)
> would just be perfect.
No, that's not so simple. I had just convinced Harald (:-) that we should
keep the different versions of the same patch in one directory, like:
foo/
foo/info # Common auxiliary files
foo/help
foo/linux-2.4.patch # 2.4 speficic patch and whole files
foo/linux-2.4/...
foo/linux-2.6.patch # 2.6 specific patch and whole files
foo/linux-2.6/...
The Requires (in your context: Depends) lines can be added to the info
file, which thus valid for all patch-versions. In Debian, you have one
specific package. Here we have multiple versions of the same patch.
Best regards,
Jozsef
-
E-mail : kadlec@blackhole.kfki.hu, kadlec@sunserv.kfki.hu
PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt
Address : KFKI Research Institute for Particle and Nuclear Physics
H-1525 Budapest 114, POB. 49, Hungary
^ permalink raw reply
* Re: udev and devfs - The final word
From: Nigel Cunningham @ 2004-01-05 12:39 UTC (permalink / raw)
To: Robin Rosenberg; +Cc: Linux Kernel Mailing List
In-Reply-To: <200401051201.58356.roro.l@dewire.com>
[-- Attachment #1: Type: text/plain, Size: 781 bytes --]
Hi.
The suspend to disk implementations all assume that devices are not
[dis]appearing under us while we're suspended. If you do go adding and
removing devices while the power is off, you can expect the same
problems you'd get if you removed them without suspending the machine.
It would be roughly equivalent to hot[un]plugging devices.
To return to the original point though, userspace may see a sudden big
jump in the time clock if it's looking, but it won't suddenly find major
& minor numbers are different.
Regards,
Nigel
On Tue, 2004-01-06 at 00:01, Robin Rosenberg wrote:
> > Yes. You end up running the original kernel.
>
> But not necessarily the same devices.
--
My work on Software Suspend is graciously brought to you by
LinuxFund.org.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply
* Hisax(Netjet) dysfunctional in 2.6.0
From: Peter Daum @ 2004-01-05 12:36 UTC (permalink / raw)
To: linux-kernel
Hi,
it looks like ISDN4L with the hisax driver does not work anymore
in kernel 2.6.0. On my machine, the driver gets loaded, prints a
couple of messages to the syslog (none of them look like errors)
and then unloads again without any apparent reason:
...: ISDN subsystem initialized
...: HiSax: Linux Driver for passive ISDN cards
...: HiSax: Version 3.5 (module)
...
...: HiSax: Total 1 card defined
...: get_drv 0: 0 -> 1
...: teles0: State ST_DRV_NULL Event EV_DRV_REGISTER
...: teles0: ChangeState ST_DRV_LOADED
...: HiSax: Card 1 Protocol EDSS1 Id=teles0 (0)
...: HiSax: Traverse Tech. NETjet-S driver Rev. 2.7.6.6
...: PCI: Found IRQ 10 for device 0000:02:0c.0
...: PCI: Sharing IRQ 10 with 0000:02:05.0
...: NETjet-S: PCI card configured at 0xa800 IRQ 10
...: HiSax: ISAC version (0): 2086/2186 V1.1
...: get_drv 0: 1 -> 2
...: teles0: State ST_DRV_LOADED Event EV_STAT_UNLOAD
...: put_drv 0: 2 -> 1
...: put_drv 0: 1 -> 0
...: HiSax: Card type 20 not installed !
With kernel 2.4.x everything works without any problems.
Any Ideas?
Regards,
Peter Daum
^ permalink raw reply
* Re: Kernel panic.. in 3.0 Enterprise Linux
From: Kresimir Sparavec @ 2004-01-05 12:43 UTC (permalink / raw)
To: Arjan van de Ven; +Cc: neel vanan, William Lee Irwin III, linux-kernel
In-Reply-To: <1073305477.4429.0.camel@laptop.fenrus.com>
On Mon, Jan 05, 2004 at 01:24:38PM +0100, Arjan van de Ven wrote:
> On Mon, 2004-01-05 at 12:56, neel vanan wrote:
> > Hi all,
> >
> > The kernel I have working is version 2.4.21-4.EL and I
> > can still boot up to that. I compiled a 2.6.0 version
> > and installed it in exactly the same way that the old
> > version is, just appending 2.6.0 to the end of the
> > file. so when I reboot I get a boot screen that shows:
> >
> > Red Hat Enterprise Linux AS (2.4.21-4.ELsmp)
> > Red Hat Enterprise Linux As-up (2.4.21-4.EL)
> > Red Hat linux (2.6.0)
>
> RHEL3 isn't quite 2.6 ready btw; you need to update quite a few packages
> to get it working right.
could you please summarize which ones? i upgraded modutils and modified
rc.sysinit for usb support. the rest works unmodified (except NVIDIA
proprietary kernel driver which does not have 2.6.x support yet, but XFree86
driver works fine for me) as far as i can tell. i got exactly 0 (zero)
kernel panics up to now. compared with 2.4.0 few years ago, 2.6.0 works
like charm
>
> Also if you use mount-by-label you do need to create an initrd (with a
> 2.6 capable mkinitrd)...
>
^ permalink raw reply
* Re: 2.6.0 performance problems
From: Samium Gromoff @ 2004-01-05 12:33 UTC (permalink / raw)
To: Ed Tomlinson; +Cc: Samium Gromoff, linux-kernel
In-Reply-To: <200312300855.00741.edt@aei.ca>
At Tue, 30 Dec 2003 08:55:00 -0500,
Ed Tomlinson wrote:
>
> On December 30, 2003 06:41 am, Samium Gromoff wrote:
> > Reality sucks.
> >
> > People are ignorant enough to turn blind eye to obvious vm regressions.
> >
> > No developers run 64M boxens anymore...
>
> No one is turning a blind eye. Notice Linus has reponded to and is interested in this
> thread. The vm is not perfect in all cases - in most cases it is faster though...
"in most cases it is faster" is a big lie.
The reality is: on all usual one-way boxes 2.6 goes slower than 2.4 once you start paging.
Ask Roger Luethi. (And yes, i have done tests myself)
One of the worst things i see about it is that people are so terribly misinformed.
> Ed Tomlinson
regards, Samium Gromoff
^ permalink raw reply
* Re: Kernel panic.. in 3.0 Enterprise Linux
From: Christophe Saout @ 2004-01-05 12:33 UTC (permalink / raw)
To: Rik van Riel; +Cc: neel vanan, William Lee Irwin III, linux-kernel
In-Reply-To: <Pine.LNX.4.44.0401050722520.23604-100000@chimarrao.boston.redhat.com>
Am Mo, den 05.01.2004 schrieb Rik van Riel um 13:23:
> On Mon, 5 Jan 2004, Christophe Saout wrote:
> >
> > LABEL= is a RedHat extension. Please use the normal root options that is
> > described in the Grub or kernel documentation.
>
> It's not even a Red Hat extension. The LABEL= stuff is
> done entirely in userspace, on the initrd.
I was misinformed then. Thanks.
> RAMDISK: Compressed image found at block 0
> RAMDISK: incomplete write (-1 !=32768) 4194304
> VFS cannot open root device "LABEL=/" or unknown block (0,0)
His initrd can't be correctly loaded. It seems the initrd is larger than
4MiB but he didn't increase the maximum size in the kernel
configuration.
^ permalink raw reply
* Re: UDP connections and Conntrack...
From: Jozsef Kadlecsik @ 2004-01-05 12:33 UTC (permalink / raw)
To: Eddahbi Karim; +Cc: netfilter
In-Reply-To: <1073106266.24037.13.camel@gamux>
On Sat, 3 Jan 2004, Eddahbi Karim wrote:
> When a client sends an UDP datagram to an UDP server, the connection is
> ESTABLISHED when the server sends back an UDP datagram and the client
> sends another UDP datagram or does the connection is ESTABLISHED when
> the server answer to the first UDP datagram ?
>
> For example, is it like that :
>
> Client -> DATA -> Server
> Client <- DATA <- Server
>
> Connection ESTABLISHED for the server !
This one happens in conntrack for UDP.
Best regards,
Jozsef
-
E-mail : kadlec@blackhole.kfki.hu, kadlec@sunserv.kfki.hu
PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt
Address : KFKI Research Institute for Particle and Nuclear Physics
H-1525 Budapest 114, POB. 49, Hungary
^ permalink raw reply
* Re: Any hope for HPT372/HPT374 IDE controller?
From: Job @ 2004-01-05 12:33 UTC (permalink / raw)
To: Andreas Steinmetz; +Cc: Andre Hedrick, tomwallard, linux-kernel
In-Reply-To: <3FF8B35E.1050704@domdv.de>
I use KT400 MoBo, my HD is at HighPoint IDE, I am not using RAID and
works fine with apic=off, but did not boot on 2.6 kernel series due the
lack of ataraid or some scripts.
Andreas Steinmetz wrote:
> Andre Hedrick wrote:
>
>>
>> Some of the problems appear with the APIC routing and interrupts being
>> lost and not begin processed.
>>
>
> Hopefully this will solve problems for X86-64 AMD chipset based MoBos
> too. I can run my Tyan S2885 only with IO-APIC disabled due to HPT302
> lockups (2.4)/lost interrupts (2.6).
^ permalink raw reply
* cdrom drive doens't answering
From: Giuliani Ivan @ 2004-01-05 12:31 UTC (permalink / raw)
To: linux-kernel
Hi,
today I was installing mutt from my own slack 9.1 cdrom. As soon as I wrote
installpkg mutt... the console seemed to be freezed. I killed then the
process from another console but the cdrom continued reading from the cd.
Trying to umount the device told me that the device was busy but I wasn't using
no more the device.
I tried to eject the cdrom manually and the cdrom went out also if it result
mounted. Looking at dmesg, I saw this:
hdc: timeout waiting for DMA
hdc: timeout waiting for DMA
hdc: (__ide_dma_test_irq) called while not waiting
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54
end_request: I/O error, dev 16:00 (hdc), sector 644968
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54
end_request: I/O error, dev 16:00 (hdc), sector 644972
hdc: timeout waiting for DMA
hdc: timeout waiting for DMA
hdc: (__ide_dma_test_irq) called while not waiting
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54
end_request: I/O error, dev 16:00 (hdc), sector 644976
hdc: command error: status=0x51 { DriveReady SeekComplete Error }
hdc: command error: error=0x54
end_request: I/O error, dev 16:00 (hdc), sector 644980
[repeated 4-5 times]
hdc: timeout waiting for DMA
hdc: timeout waiting for DMA
hdc: (__ide_dma_test_irq) called while not waiting
[again the previous errors]
hdc: irq timeout: status=0xd0 { Busy }
hdc: irq timeout: error=0x00
hdc: ATAPI reset complete
[again the previous errors]
hdc: irq timeout: status=0xd0 { Busy }
hdc: irq timeout: error=0x00
hdc: ATAPI reset complete
hdc: tray open
I suppose the at this point is when I ejected the cdrom manually. The log
continues:
end_request: I/O error, dev 16:00 (hdc), sector 645108
hdc: request sense failure: status=0x51 { DriveReady SeekComplete Error }
hdc: request sense failure: error=0x20LastFailedSense 0x02
hdc: tray open
[repeated 5-6 times]
hdc: tray open
end_request: I/O error, dev 16:00 (hdc), sector 671480
hdc: request sense failure: status=0x51 { DriveReady SeekComplete Error }
hdc: request sense failure: error=0x20LastFailedSense 0x02
And nothing more.
Umounting the device from the console now didn't give me any error.
Trying to mount some cd again give this:
root@malattia:~# mount /mnt/cdrom/
mount: No medium found
What's happened?
I have the kernel 2.4.22 with slackware 9.1 (default slackware kernel).
hdparm says this:
root@malattia:~# hdparm -i /dev/hdc
/dev/hdc:
Model=36X CD-ROM, FwRev=VER 2.F0, SerialNo=MT1102 Firmware
Config={ Fixed Removeable DTR<=5Mbs DTR>10Mbs nonMagnetic }
RawCHS=0/0/0, TrkSize=0, SectSize=0, ECCbytes=0
BuffType=unknown, BuffSize=0kB, MaxMultSect=0
(maybe): CurCHS=0/0/0, CurSects=0, LBA=yes, LBAsects=0
IORDY=yes, tPIO={min:227,w/IORDY:120}, tDMA={min:120,rec:150}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 *udma2
AdvancedPM=no
I never got problems with the cd drive, and rebooting the system everything
began to run again.
Is this a kernel problem or a my own fault?
Bye
--
Ivan "kratorius" Giuliani :: PGP Public Key ID:
http://kratorius.cjb.net :: 0x840F429D @ keyserver.linux.it
LUGBari Member ::
^ permalink raw reply
* RE: help needed: clogged console
From: Jozsef Kadlecsik @ 2004-01-05 12:31 UTC (permalink / raw)
To: John A. Sullivan III
Cc: bmcdowell, orlowscy, shrike-list, redhat-list, netfilter
In-Reply-To: <1073059221.2993.10.camel@jasiiitosh.nexusmgmt.com>
On Fri, 2 Jan 2004, John A. Sullivan III wrote:
> > Search for 'dmesg -n 1' - I think that's what you're after.
^^^^^
> I've been really confused by this issue. I am also running iptables on
> RedHat 9.0. /etc/syslog.conf shows nothing being logged to the
> console. Yet, ever since applying the netfilter patch-o-matic
> tcp-window patch, all of its messages appear on my console. The
> netfilter mail lists say this is a misconfiguration of syslog but it
> sure looks correctly configured to me. No other iptables messages go to
> the console - just the tcp-window messages. How do I stop them!!! Thanks
Default the tcp-window-tracking patch uses extensive kernel logging,
while the other parts of netfilter keeps mouth shut. You can easily
disable the logging by
echo 0 > /proc/sys/net/ipv4/netfilter/ip_conntrack_tcp_log_invalid
Back to the console logging: klogd uses the console to display the kernel
log messages. You can alter it's default behaviour by issuing dmesg like
above or setting the proper command line switches for klogd. If you want
to send the kernel logs to other places (file/remote machine etc.), *then*
you have to configure syslogd properly.
Best regards,
Jozsef
-
E-mail : kadlec@blackhole.kfki.hu, kadlec@sunserv.kfki.hu
PGP key : http://www.kfki.hu/~kadlec/pgp_public_key.txt
Address : KFKI Research Institute for Particle and Nuclear Physics
H-1525 Budapest 114, POB. 49, Hungary
^ permalink raw reply
* Linux 2.4.24-rc1
From: Marcelo Tosatti @ 2004-01-05 12:18 UTC (permalink / raw)
To: linux-kernel
This release fixes a few critical problems in 2.4.23, including fixes
for two security bugs.
Upgrade is recommended.
Detailed changelog follows
Summary of changes from v2.4.23 to v2.4.24-rc1
============================================
<bjorn.helgaas:hp.com>:
o Fix 2.4 EFI RTC oops
<marcelo.tosatti:cyclades.com>:
o Andrea Arcangeli: malicious users of mremap() syscall can gain priviledges
<marcelo:logos.cnet>:
o Harald Welte: Fix ipchains MASQUERADE oops
o Change EXTRAVERSION to 2.4.24-rc1
<trini:mvista.com>:
o /dev/rtc can leak parts of kernel memory to unpriviledged users
Jean Tourrilhes:
o IrDA kernel log buster
^ permalink raw reply
* Re: Kernel panic.. in 3.0 Enterprise Linux
From: Arjan van de Ven @ 2004-01-05 12:24 UTC (permalink / raw)
To: neel vanan; +Cc: William Lee Irwin III, linux-kernel
In-Reply-To: <20040105115610.49148.qmail@web9505.mail.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 676 bytes --]
On Mon, 2004-01-05 at 12:56, neel vanan wrote:
> Hi all,
>
> The kernel I have working is version 2.4.21-4.EL and I
> can still boot up to that. I compiled a 2.6.0 version
> and installed it in exactly the same way that the old
> version is, just appending 2.6.0 to the end of the
> file. so when I reboot I get a boot screen that shows:
>
> Red Hat Enterprise Linux AS (2.4.21-4.ELsmp)
> Red Hat Enterprise Linux As-up (2.4.21-4.EL)
> Red Hat linux (2.6.0)
RHEL3 isn't quite 2.6 ready btw; you need to update quite a few packages
to get it working right.
Also if you use mount-by-label you do need to create an initrd (with a
2.6 capable mkinitrd)...
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply
* Re: Kernel panic.. in 3.0 Enterprise Linux
From: Rik van Riel @ 2004-01-05 12:23 UTC (permalink / raw)
To: Christophe Saout; +Cc: neel vanan, William Lee Irwin III, linux-kernel
In-Reply-To: <1073304533.5562.7.camel@leto.cs.pocnet.net>
On Mon, 5 Jan 2004, Christophe Saout wrote:
> Am Mo, den 05.01.2004 schrieb neel vanan um 12:56:
>
> > VFS cannot open root device "LABEL=/" or unknown block
> > (0,0)
> > Please append a correct "root=" boot option
> > Kernel panic: VFS: Unable to mount root fs on
> > unknown-block(0,0)
>
> LABEL= is a RedHat extension. Please use the normal root options that is
> described in the Grub or kernel documentation.
It's not even a Red Hat extension. The LABEL= stuff is
done entirely in userspace, on the initrd.
If you do not want to use an initrd, you need to use the
normal root options instead, something like root=/dev/hda3
--
"Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it." - Brian W. Kernighan
^ permalink raw reply
* Re: Kernel panic.. in 3.0 Enterprise Linux
From: Andreas Unterkircher @ 2004-01-05 12:21 UTC (permalink / raw)
To: neel vanan; +Cc: linux-kernel
In-Reply-To: <20040105115610.49148.qmail@web9505.mail.yahoo.com>
have you rebuild your initrd? you have written you
have compile in all needed things - so do you still
need the initrd? if not - try to remove the line...
andreas
Am Mon, den 05.01.2004 schrieb neel vanan um 12:56:
> Hi all,
>
> The kernel I have working is version 2.4.21-4.EL and I
> can still boot up to that. I compiled a 2.6.0 version
> and installed it in exactly the same way that the old
> version is, just appending 2.6.0 to the end of the
> file. so when I reboot I get a boot screen that shows:
>
> Red Hat Enterprise Linux AS (2.4.21-4.ELsmp)
> Red Hat Enterprise Linux As-up (2.4.21-4.EL)
> Red Hat linux (2.6.0)
>
> Enterprise linux still boots up fine but when I try
> and boot up Red Hat linux (2.6.0) I get some ouput and
> then a kernel panic with this message:
>
> <snip>
> Software Suspend has malfunctioning SMP support.
> Disabled :(
> ACPI: (supports S0 S1 S4 S5)
> RAMDISK: Compressed image found at block 0
> RAMDISK: incomplete write (-1 !=32768) 4194304
> VFS cannot open root device "LABEL=/" or unknown block
> (0,0)
> Please append a correct "root=" boot option
> Kernel panic: VFS: Unable to mount root fs on
> unknown-block(0,0)
>
> I am running Linux Enterprise Edition version 3.0 on
> my server. It has 2 Xeon processors and 1 U360 scsi
> HD. The whole reason behind my compiling a kernel is
> trying to get support for high memory (this
> machine has 4 gigs of ram) and multi-processor
> support.
>
> I'm pretty sure I selected all scsi and driver support
> because when i run the same kernel with RedHat Linux
> 9.0 in same machine it works fine. Everything is
> compiled in and not as modules.
>
> This is snip of my grub.conf file:
> # grub.conf generated by anaconda
> #
> default=0
> timeout=10
> splashimage=(hd0,0)/grub/splash.xpm
> title RedHat Enterprise Linux AS (2.4.21-4.ELsmp)
> root (hd0,0)
> kernel /vmlinuz-2.4.21-4.EL ro root=LABEL=/
> initrd /initrd-2.4.21-4.EL.img
> title RedHat Linux (2.6.0)
> root (hd0,0)
> kernel /linux-2.6.0 ro root=LABEL=/
> initrd /initrd-2.6.0.img
>
> Any help would be greatly appreciated! Thanks in
> advance,
>
> Neel
>
>
> __________________________________
> Do you Yahoo!?
> Find out what made the Top Yahoo! Searches of 2003
> http://search.yahoo.com/top2003
> -
> 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/
>
^ permalink raw reply
* Re: File system cache corruption in 2.6?
From: Jens Axboe @ 2004-01-05 12:19 UTC (permalink / raw)
To: Nathaniel W. Filardo; +Cc: linux-kernel
In-Reply-To: <Pine.LNX.4.58-035.0401050014450.5565@unix49.andrew.cmu.edu>
On Mon, Jan 05 2004, Nathaniel W. Filardo wrote:
> Hi all,
> I'm trying to work out the cause of a series of issues I've seen
> on my 2.6 machine. It appears as though files (specifically libraries) in
> memory can get corrupted, resulting in strangeness like segfaults and
> things like "relocation error: can't find symbol ...-VOMD-POINTER" instead
> of "...-VOID-POINTER".
That's a single bit error.
> I don't believe it's actual hardware failure for a few reasons: memtest86
> passes all tests, GCC doesn't crash (it's a Gentoo system, so gcc and I
> are well acquainted - and before I get jumped on, I've installed udev ;)
> ), and most importantly, sometimes thrashing the file system or engaging a
> kernel compile will rectify the situation, as just happened with emacs.
> It crashed, I killed it, it wouldn't load - I started a kernel compile,
> waited a bit, and lo', it works again. No messages of relevance appear in
> dmesg.
It looks _extremely_ much like bad memory, or bad hardware. Sometimes
memtest just doesn't catch all errors (how long did you run it? needs
several days often).
--
Jens Axboe
^ 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.