This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/16361] kernel built with gcc 3.4.1 don't read my partition on USB
- From: "gregoire dot favre at freesurf dot ch" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 12 Jul 2004 20:25:32 -0000
- Subject: [Bug c/16361] kernel built with gcc 3.4.1 don't read my partition on USB
- References: <20040704155415.16361.gregoire.favre@freesurf.ch>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From gregoire dot favre at freesurf dot ch 2004-07-12 20:25 -------
I am sorry to ask for more info, I explained that kernel I compiled with gcc
prior than 3.4.x works perfectly, and that the one with 3.4.0 and 3.4.1 don't
work, then what's the point in compiling again with 3.3.4 as I already know it
works ?
How should I give a testcase for this ?
Just take an Apacer Handy Steno 512Mb memory stick, and try to plug it in a
2.6.6 kernel : compiled with gcc 3.3.4 every thing works perfectly.
With gcc 3.4.1 :
usb 1-2: new high speed USB device using address 3
scsi3 : SCSI emulation for USB Mass Storage devices
Vendor: USB Model: Flash Drive Rev: 1.12
Type: Direct-Access ANSI SCSI revision: 02
SCSI device sdg: 1015805 512-byte hdwr sectors (520 MB)
sdg: assuming Write Enabled
sdg: assuming drive cache: write through
sdg: sdg1 sdg2 sdg3 sdg4
Attached scsi removable disk sdg at scsi3, channel 0, id 0, lun 0
Attached scsi generic sg9 at scsi3, channel 0, id 0, lun 0, type 0
udev[3817]: creating device node '/udev/sg9'
scsi.agent[3741]: disk at /devices/pci0000:00/0000:00:1d.7/usb1/1-2/1-2:1.0/h
ost3/3:0:0:0
creating device node '/udev/sdg2'
creating device node '/udev/sdg4'
udev[3759]: creating device node '/udev/sdg1'
udev[3753]: creating device node '/udev/sdg'
udev[3771]: creating device node '/udev/sdg3'
kernel: FAT: unable to read boot sector
And of course I can't mount it (sdg4).
With 2.6.7-rc2 and gcc 3.3.4 everything is perfect, but compiled with 3.4.1 the
partition isn't read at all by the kernel (as reported under
http://lkml.org/lkml/2004/6/12/29 ).
Please forgive my difficulty in understanding what I should do, I really will do
everything needed as soon as I understand what I should do :-)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16361